ERD Commander 2005 + BCDW requests Windows 2003 Server CD

[Neokjames]

Hi guys,

I am trying to create a multi-boot CD using BCDW V2.01, I can get most of my software working, however I am having difficulty with ERD Commander 2005.

It keeps asking for the Windows Server 2003, Standard Edition CD-ROM whenever I load it up.

This is what I have done:

Extracted the I386 folder from the ERD Commander 2005 Boot CD.

Renamed the "I386" folder to "ERDC".

Used a utility to make all of the file names UPPERCASE (this was a previous problem, files werent being found due to not being uppercase).

Modified SETUPLDR.BIN and replaced all instances of I386 to ERDC using WinHex.

Added the entry into bcdw.ini below-

\ERDC\SETUPLDR.BIN ; Winternals ERD Commander 2005

I sourced the modified SETUPLDR.BIN from here:

http://www.msfn.org/board/Solution-for-mul...-64-t58410.html

Image creation is being done by the following syntax using MKISOFS, if there is any issue with this - please say so, because it could be causing the problem.

"C:\mkisofs.exe" -N -iso-level 4 -volid "EntacomBoot" -relaxed-filenames -b bcdw/loader.bin -no-emul-boot -boot-load-size 4 -o "C:\EntacomBoot.iso" .

Even if I don't use the SETUPLDR.BIN from that URL and keep my I386 folder the same name, it still does not work.

Any help would be greatly appreciated.

Thanks

Edited August 24, 2008 by Neokjames

[cdob]

It keeps asking for the Windows Server 2003, Standard Edition CD-ROM whenever I load it up.

Do you use uppercased tagfiles \WIN51 and \WIN51* ?

[Neokjames]

Yes, every file and directory in my ERCD folder is uppercased.

[cdob]

every file and directory in my ERCD folder is uppercased.

What about root directory?

Tag files \WIN51* are at root directory. Did you add tag files at all?