TheTechGuide Forum

General Category => Software => Topic started by: Cunami on August 27, 2002, 02:06:10 PM

Title: Multi boot ERD commander and Disk command and ...
Post by: Cunami on August 27, 2002, 02:06:10 PM
How I can create a multi bootable cd with:
*) ERD commander
*) Disk commander
*) PQ Magic for DOS
*) Other DOS Utilities
*) Windows 9x Startup Disk
and NO windows??? There was some examples earlier, but there are with Windows 2000 Pro, Server or Advanced Server. Well I don\'t need them, so how to create cd without them?

Thanks,
Cunami
Title: Multi boot ERD commander and Disk command and ...
Post by: Twinkie on August 28, 2002, 07:11:00 PM
The instructions at my site will do what you want.  Problem is you would have read most of the site to really get it working.  Basically edit ERD and Disk commander\'s .bin file into a DAT file like the hexedits I list under Windows 2000.  Then use the edits for a DOS boot image under my ME & 9X page to use Power Quest or whatever other dos bootdisks you want.  I list Power Quest as an example on the 9X page.

The good news is it can be done.

Hope this helps,
Title: Multi boot ERD commander and Disk command and ...
Post by: Anonymous on September 04, 2002, 03:24:07 PM
Twinkie, please can you explain how do that?
Title: Multi boot ERD commander and Disk command and ...
Post by: Fjellu on September 05, 2002, 05:27:20 AM
Yes, please explain. Or put it on your \"soon to come\" All Windows 2000 page.
Title: Multi boot ERD commander and Disk command and ...
Post by: Space Between on September 05, 2002, 10:45:48 AM
I know im not Twinkie but i think (but ieve never done it) you would have to...

create a .dat file for both the ERD and the other.
then open each .dat file for ERD and the other and edit the location of the files

like in win2k you have to edit the .dat so it looks for the files
in the WPRO dir instead of the i386...example

orginally the 2k.dat looks like at the end of the .dat file in a hex editor like

SETUPLDR.BINBOOTFIX.BINI386
after editing to make it work in a multi os it has to look like
SETUPLDR.BINBOOTFIX.BINWPRO

that is assuming you boot the boot files in a dir named WPRO in the root of the dir