CompuServe Messages

Don't forget, at boot time…what you see after bootup as drive H: is drive C: at boot time. Part of the boot procedure is that DoubleSpace "swaps" drive letters. Basically, the boot procedure is as follows: Power on Self Test (POST) ROM code goes out and looks for a boot disk in A: If found, boots from the floppy ROM then looks for first HD and if it finds it, looks in CMOS for what type of drive it is. Based on CMOS parameters, looks in partition table for active partition..and if found looks on active partition for io.sys and msdos.sys Presuming it finds them, loads them up and turns control over to them. And this is where the magic occurs…msdos.sys goes out and looks for dblspace.bin on that same drive. If found, it's loaded and then dblspace.bin goes out and looks for dblspace.ini and if it's found, it looks in it and mounts the drives that are described in it. In your case, it would see that the file DBLSPACE.000 should be mounted as drive C: and the .INI file also says that what is currently you C: drive…should now be called H:…so it does it's magic and changes the name of C: to H: and then mounts the compressed volumn as C: It now reverts back to the "normal" boot code and continues with the bootup looking on what is now C: for config.sys, then autoexec.bat and so forth. If you'll look on your H: drive, you'll see all those files there if you use the DIR /A command at the H: prompt. You should see the following files: io.sys msdos.sys dblspace.bin dblspace.ini dblspace.000 [and if you've got a windows permanent swap file] 386spart.par and any other files you may have copied to H: So on bootup…what you now see as H: is what the ROM sees as the first HD and that's what must be described in CMOS so the ROM code knows where to find things. It's only after you're past the ROM code (when you see the Starting MS-DOS… line) that drive names change. If SETUP is poping up, it is probably for some reason other than it doesn't understand the HD's configuration. It may have to do with the way you (or DOS 6's setup programs) reconfigured memory. For example, on my DOS machine…I moved some of the memory around so that a different memory configuration than was in CMOS…so the first bootup "yelled" at me until I reconfigured it. Let me know how things work out if you reset SETUP's HD parameters backto the way it was before you installed DOS 6. Don