[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: UniDOS file copier



"Peter Watson" <paw77@NOhotmailSPAM.com> wrote in message
news:zoey8.54687$o66.165585@news-server.bigpond.net.au...

> > to access the first 400k and Drive 2 to access the second 400k.  UniDOS
> uses
> > Drive 1 for the first 400k and Drive 3 for the second 400k on an 800k
> disk.
> > Drive 2 and Drive 4 seem to be active but unused in an 800k disk.
>
> Drives 2 and 4 refer to the 400K "volumes" on a second physical drive. The
> intention was to make things easier for programs which (not unreasonably)
> assumed disks in drives 1 and 2 in a slot were phyically separate disks.

That makes sense.

> > It may have but I don't have the UniDOS "System" disk, only disk images
> that
> > supposedly are UniDOS.
>
> It may be worth doing some searching on the web. There were a number of
> patched FID versions around, in most cases they were originally done by
> poking some data into a BLOADed copy of FID then BSAVEing it again. I
would
> be surprised if you couldn't find an article describing this.

I have been doing a lot of reading of old articles from Google groups usenet
archives and there is much contradictory information about UniDOS and the
other 3.5" systems.  As you suggested I will look for a patched FID and try
it.  Hopefully, a FID patched for AmDOS, OzDOS or one of the others will
work with UniDOS (I never have that kind of luck).

Charlie