Hey folks,

I've tried it many times, and in very much ways, looked every where on msfn.org and still can't get ERD commander 2005 working at my AIODVD.

I did succesfully made a bootcd from ERDC05. I did succesfully changed the i386 folder 2 1ERD and also managed to change the bootsecter to 1ERD.bin. Edited ERDC.bin, SETUPLDR.bin etc.... Made a stand alone ISO of it, with the new boot file ERDC.bin. >> working

made a new complication where I my cdshell [boot] folder added and >> changed bootsector and >>working.

Now I unpacked the ERD iso in my AIODVD folder made a new iso of AIODVD and the stupid ERD is not working [i did not changed any files of ERD]

it says Can't find CD, or NTLDR. something like that. (problem with .bin file I suppose?)

i made iso's with cdimage, nero, ultraiso nothing works

please help...

do someone know how to fix it??

thnx

Edited November 18, 200520 yr by 5128

Normally it shoud work with BCDW 2.01 look this FAQ: http://www.wolfgang-brinkmann.de

Made a nice iso with BartPE, but there i also get the message cannot find NTDLR. cd cannot boot.

I have same problem. Modifing like guide says, it load operative system, but after it catch an error on Isass.exe and reboot.

There is another method for boot Erd commander 2005. Copy the entire CD contents of Erd Commander 2005 in your AIO-DVD and extract the boot sector with UltraISO.

In your AIO-DVD there isn't a i386 so you copy erd commander's cd you get an i386 folder in your AIO-DVD root that contains ONLY Erd Commander 2005 files.

After setup CDShell for boot bootsector image you have extract before.

Remember that you HAVEN'T modify setupldr.bin and txtseup.sif like guide says.

how stupid as it sounds, but it works now. I just added all my folders in AIODVD to my ERDCommander iso, changed bootloader file. changed ERD's (i386>ER86, setupldr, BIN-file) and everything is working now

doesn't sound stupid at all.

ERD follows a very strict ISO 9660 based name format.

If you extract ERD to add to a multiboot distro, the names need to remain in uppercase (except for firefox) or it won't work. I'm guessing when you extracted ERD to a folder, either the names became lowercase or you edited items and saved the names in lowercase. Also, some ISO editors will save files when building a ISO in lowercase or with other oddities (esp. if you enable relaxed restrictions).

Windows install folders all follow the basic ISO format when using files for booting so it's easy to add them to the ERD ISO. Even adding joliet based items is easy because ERD keeps it's proper name format. At least that is the case if you edit a ERD iso in UltraISO. UltraISO retains the proper settings for files in an ISO when you open it or alter ISO properties and save.

Just remember to always recompile the entire ISO when you edit.

Edited November 19, 200520 yr by LiquidSage

hey one question, the working iso i made, isn't optimized so it's now about 3,5 gig. Does it make difference to ERD if i optimize the iso with ultraiso, I mean if i do that, wouldn't it work anymore? (erd)

I often make my iso's the same way you stumbled upon (adding aiwil's Bart is easier and overall it is quicker if you already have cdshell and such ready to add).

I have never had any issues using UltraISO's optimize feature on ERD. I've noticed overall file size is usually a tad less with cdimage or mkisofs though. Not big enough to warrant a switch though