Problem i've ran into using CDImage (put it into a .cmd so i could see what was making it quit)

1. You know you have enough space

2. It always fails at the same %

3. The ISO is created, but then disapears on failure

Here is the contents of my .cmd

CLS
@echo off
TITLE Creating ISO of uA Multi-Boot DVD
ECHO.
ECHO Preparing Files
attrib -R -H E:\AIO-DVD /S /D
ECHO. 
ECHO Creating ISO...
cdimage.exe -lAIODVD -t08/23/2001,09:00:00 -b\AIO-DVD\BOOT\loader.bin -h -n -o -m \AIO-DVD C:\AIO-DVD.ISO
ECHO.
PAUSE
EXIT

So far i've figured out that it CANT handle funky characters that stupid people put in plugin packs that they send you IE: "MAELSTR๖.8BF"

If you want to hunt down the problem files, then go right ahead but you can also use the -k switch to skip over them

Edit: what i mean by all this is to use that .cmd (changing the path variables) in parallel with cdimage.exe instead of just tossing some switches at a command line so you dont get all frustrated for no reason!

Maybe you should add the -j1 option for those special caracters...

Here is my working CDIMAGE command file:

CLS
@echo off
TITLE Windows XP Professionel SP2
ECHO. 
ECHO Wait...
cdimage.exe -l"WXPSP2FR" -t08/23/2001,09:00:00 -h -j1 -b"D:\WinXP SP2 FR\DOS\loader.bin" -o -w1 -m "D:\WinXP SP2 FR" "D:\ISO\WinXP SP2 FR.iso"
ECHO.
PAUSE
EXIT

I had said that the file-system switch in the new updated guide be changed to "-j1" (because its the best one of the lot). But it wasn't done - and now see the problems its absence is causing.

No, no, don't add it to the guide... let's keep our little secrets!

I had said that the file-system switch in the new updated guide be changed to "-j1" (because its the best one of the lot).  But it wasn't done - and now see the problems its absence is causing.

<{POST_SNAPBACK}>

And who's fault is that? I told you to remind me

EDIT: It was changed when I switched to CDIMAGE GUI as the new tool to use (for the beginners). I should probally put up the commandline for those interested as well.