[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: DOS 3.3 for 1.40 MB disk, for a system with non-working 80-column code?
Shouldn't be that hard.
You might try to just use one of the patched versions of DOS3.3 for 800k
disks.
Whether it uses ProDOS block calls or smartport calls, it's a good chance it
would work
on a 1.44 disk (even though it would just use the first 800k)
But those 800k would be readable on an IBM
"Dosius" <steve@dosius.zzn.com> wrote in message
9307085f.0212070857.3d1bcb53@posting.google.com">news:9307085f.0212070857.3d1bcb53@posting.google.com...
> I'd like to know if anyone has a way to run DOS 3.3 programs off a
> 1.40 MB disk, so I can use a single floppy to store a number of games
> and not have to use the emulator's menu, and many of them (i.e., Hard
> Hat Mack) don't work in ProDOS. The emulator I use (Dapple 0.99a)
> doesn't yet do 80-column, so ProSel might be out of the question as a
> launcher. Perhaps there is a way to make DOS 3.x read 3 segments of
> the disk (1200 KB, most of the disk) through the ProDOS block device,
> and boot from it...?
Why waste 240k?
Do 3 400k disks and 1 240k or do 4 360k disks.
The question is-do you map the extra pseudo-disks as other slots and drives
or use the volume parameter?
Using V or drives 3+4 gives you more flexibility (like running on multiple
FDHD drives simultaneously) if you're doing custom programming.
Do you want to be able to access all of the disk at once, or is it ok to be
effectvely swapping disks, having only the volume you select active at a
time, ll appearing in the same slot and drive,
But if you want greatest compatibility w/ old programs , most didn't use V,
most will limit you to drives 1+2, and some may not even allow all of slots
1-7.
And of course some stuff is hardcoded for 140k disks.
>