I have the NeroCmd version 188.8.131.52 that came with Nero version 184.108.40.206 OEM, and the NeroAPI.dll that came with it is 220.127.116.11.
I entered the following in a .bat file:
erocmd --write --error_log neroerr.lst --drivename D --create_iso_fs --iso My_CD c:\subdir*.*
With a blank CR-R (48X) in the Ikebana 24-10-40 drive, I ran the .bat file in a command window. The thing seemed to check out the parameters ok (no errors reported), but then asked for a writable CD to be inserted and ejected the one I had loaded. Reloading the CD just gives the same message.
I then fired up Nero itself, brought up the .NRI I had saved from a previous session, and successfully burned the files onto the same CD that NeroCmd wouldn’t use.
What is NeroCmd telling me - what doesn’t it like about a CD that the GUI successfully writes onto?
I have downloaded the newest Nero (18.104.22.168 I think it is), but haven’t yet tried that; I presume it will update the 22.214.171.124 OEM I have, won’t it?). Is the upgrade needed, so I can use arg --media_type media_cdr to be specific about what I have in the drive? That option doesn’t seem to be in the version I have; when I include it, NeroCmd does complain about the invalid switch.