Message-Id: <200010250327.XAA31053@xellos.bignet.net> MIME-Version: 1.0 To: From: "Mark at Cross+Road's" CC: , Date: Tue, 24 Oct 2000 23:27:33 +0400 X-Mailer: Net-Tamer 1.12.0 Subject: Drdos and Msdos on the same drive Reply-To: opendos AT delorie DOT com Isn't this the idea behind using a bootmanger like System Commandor? I would think that SC does the same thing and may be more protective of the associated files? Thanks, Mark On 2000-10-06 opendos AT delorie DOT com said: >----- Original Message ----- >Cc: >Sent: Monday, September 18, 2000 1:41 AM >> Does this mean then that if you had a drive with Drdos #703 >>operating and used a bootmanger to install msdos 6.22 the >partitions set-up by Drdos could >> likely become trashed when booting to msdos and read/write on >>those same shared drives? >I have never tried this method. When I fooll around with MS DOS or >other DOSes, I usually remove DDOS and install the new DOS from >scratch. I'll see if I can explain a few things. When using more >than one DPS, you usually put each version on it's own primary >partition. My experience is that when you do this, the other DOS >(the one not being used) is hidden and you cannot access that >partition. You boot the partition you want by changing the boot >partition with fdisk. >> Wanting to know because I am considering adding msdos 6.22 to >>my bootmanager menue but don't want to do so if this would be >>likely when working on the same drives. >You may be able to do this, however, I have never tried it. Be sure >to back up exverything before trying this. I would first install >DRDOS. Then I would copy the autoexec.bat ile to a file named >autodos7.bat and copy the config.sys file to dconfig.sys. I would >copy the COMMAND.COM file to the DRDOS directory. Then edit the >dconfig.sys file to show the COMMAND.COM is at d;/DRDOS/COMMAND.COM >on the COMSPEC line. This will allow you to have your DRDOS set up >separately from your MS DOS. Boot the system and make sure it boots >to DOS okay. Then delete the config.sys, autoexec.bat and command. >com files from the root directory. >Now, install MS DOS 6.22xxxx whatever it is. Now your system should >boot to MS DOS. run CHKDSK /V nad make sure that MSDOS can read the >drive okay (I have not had a problem, but seems like some people >have had problems if formatted with DRDOS.) If everything is okay, >then change to C:\DRDOS directory and run LOADER. This will now >make the system bootable to either DRDOS or MSDOS. The MSDOS will >use the COMMAND.COM in the root directory and the DRDOS will use >the one in the DRDOS directory. MSDOS will use the AUTOEXEC.BAT and >CONFIG.SYS files when booting. DRDOS will ignore these files and >use the DCONFIG.SYS and AUTODOS7.BAT files when booting. >As I have stated above, I have never tried this. I have no use for >MSDOS and have had no reason to try it. I may try it one of these >days just for reference purposes. >As far as having problems with DRDOS v7.0x FDISK, I have never run >into a problem with it. I have just seen several references to >people having problems with it and not recommend using it. Thus far. >in response to my message, all I have seen is a possible formatting >problem, but have doubts about that too. Someone else said they >have used it on small drives and had no problems. When I get more >responces and see an actuall problem that I can actually dupilicate >myself, I am not sure there is any problem. I have used >DR/Novell/Caldera OpenDOS for many, many years and have >ocassionally put MSDOS on my computer to check out things. Even IBM >DOS, RXDOS, FreeDOS, and many other things to check them out. I do >not recall re-formatting the drive with other than DRDOS except way >back when I was using MS DOS 3.3 and MSDOS 5.0. >Pat >_________________________________________________________ >Do You Yahoo!? >Get your free @yahoo.com address at http://mail.yahoo.com