Trying to bring this up on the KryoFlux support forums
tends to agitate
hostile responses.
Trying to ___ KryoFlux ___ tends to agitate hostile responses.
I wouldn't harp on this (this is, after all, something I encounter often in
the vintage software/hardware community) if the hostility wasn't
world-class.
On Tue, Jan 14, 2014 at 2:36 PM, Mark J. Blair <nf6x at nf6x.net> wrote:
>
> On Jan 14, 2014, at 09:25 , Al Kossow <aek at bitsavers.org> wrote:
> > and someone asked why all of this hardware is coming out of the
> Amiga/Commidore crowd and why it's all built to
> > run under Windows.
>
> My KryoFlux does work with my Mac under OSX, but its flaw is the lack of
> general write support without using the parent company's paid disk analysis
> services. Without having investigated it myself, I'm willing to accept that
> reading a funky write-protected format and then being able to write it to a
> new disk in a way that satisfies the copy protection is tricky and
> difficult or impossible to automate. But for my own selfish purposes, I
> would be quite satisfied to have a good solution to read regular
> non-copy-protected disks and write them back out in a way that satisfies
> stock DOSes, just for keeping old hardware alive and fed with operating
> systems and basic utilities.
>
> The public domain Disk-Utilities package looks promising in conjunction
> with KryoFlux, but I haven't gotten around to trying to adapt it for the
> non-PC formats that interest me.
>
Trying to bring this up on the KryoFlux support forums
tends to agitate
> hostile responses. It's quite frustrating. Almost
frustrating enough to
> motivate me to develop a competing product, but that would be a very large
> job to do well, and my darned day job ties up most of my time and gumption.
>
> --
> Mark J. Blair, NF6X <nf6x at nf6x.net>
>
http://www.nf6x.net/
>
>
>