russg, on Mon Jun 18, 2012 4:49 PM, said:
Have you tried APE unregistered? With an ATR loaded in D8: in APE for windows 3.0.6, registered, if you load a RAMDisk in D8: with 'RD.COM D8:' the Atari sees only the RD, the D8: in APE disappears, it still shows up in the APE menu, but the Atari can't see it. I think you say if you do that with Aspeqt, you can't access either drive. I'm using SP 3.2g FTe and RD.COM ver 2.3 7-14-86 1986 ICD.
edit: AspeQT Win32 0.6 does the same as APE. RD.COM is recognized, the D8: in AspeQT is ignored.
Actually I was saying the same thing as you are saying now. If DOS sets up a ramdisk, say on D8:, the Atari will access the ramdisk at D8: and not the mounted image in AspeQt on D8:. I didn't try that on APE, but I was assuming the same thing would happen.
So if one uses a ramdisk on a given drive, APE or AspeQt will not know about this, and they will still allow you to mount a disk image on the same drive number that DOS have setup a ramdisk.
The effect of this is not really serious, it may however confuse a user of APE/AspeQt if somehow the user is not aware or forgets that a ramdisk was setup on that same drive.
For example Atari DOS 2.5 which came with the 1050 drive, automatically set up a ramdisk on D8: (if the booting computer was a 130XE or a compatible memory upgraded Atari 8 bit)
In such a case it's possible that the user may forget that the DOS already set up a ramdisk on D8: and may mount a disk image in AspeQt using the same drive number. When a request is made to access drive D8:, the DOS will access the ramdisk and not the mounted disk image in AspeQt.
So I am thinking of adding a command line option to AspeQt to "reserve" a drive # as a ramdisk, so AspeQt won't enable that drive for image mounting to prevent possible confusion.
Edited by atari8warez, Mon Jun 18, 2012 9:24 PM.