ImgBurn v2.1.0.0 Released!

[feedback]

Many improvements and bug fixes in this version.

Get it below.

http://www.imgburn.com

[blutach]

Huge thanks to LUK! and the team (except for one lazy blu sod :)).

A little bugfix has turned into a major update.

Regards

[Susana]

Great THX LuK

[Garambone]

Excellent! Thanks for this new release.
May the force be with you, LUK.

[manolito]

I cannot get IMGBurn 2.1.0.0 to work reliably in Build mode when called from the command line.

My system configuration:
Win XP SP2 German, 512 MB RAM, Burner Benq DVD DD W1620, Firmware B7W9, Windows Device Manager tells me that it operates in Ultra DMA Mode 1

I call IMGBurn from DVD2SVCD with the following command line parameters:
/MODE ISOBUILD /BUILDMODE DEVICE /SRC "I:\Movies\VIDEO_TS\" /FILESYSTEM "ISO9660 + UDF" /DEST h: /SPEED 8x /ERASE /START /CLOSE /VERIFY NO /NOIMAGEDETAILS /VOLUMELABEL "DVD" /WAITFORMEDIA

My settings for IMGBurn are basically the default settings. (Just turned off sounds)

Most of the time IMGBurn finishes the "Build" and then just hangs. The main window status line says "Terminating Build Thread...". In this state the program can only be closed by killing it with the task manager.

I already tried to disable drive locking, I checked "Ignore in Use files", I tried to use ASPI and ELBY instead of SPTI, but nothing helped.

Only right after rebooting Windows it will occasionally work. But when I cancel the burn process, reload the blank and start IMGBurn again with exactly the same parameters, it will hang again.

The funny thing is that IMGBurn 2.0.0.0 worked flawlessly, so it looks like version 2.1.0.0 communicates with my burner in a different way than 2.0.0.0


Any ideas?

Cheers
manolito

[LIGHTNING UK!]

Forget the /close bit and see if it finishes nicely. Then close it manually.

None of the things you've tried to get it working are releated to the actual problem. This is not a drive / settings issue by the sounds of it.

I do not spend much (any) time on CLI stuff. I see the program as a GUI app. The CLI stuff is just in there because too many people use it that way. It only complicates matters so far as I'm concerned.

[manolito]

Forget the /close bit and see if it finishes nicely. Then close it manually.
Did that, but no difference. Just one time I got a popup window saying: Drive not ready (Handle is not valid). So I assumed that maybe DirectCD was to blame. After uninstalling DirectCD and rebooting I got a different error message. This time the drive could not be locked. So I disabled drive locking only to get the same behavior as before (the program just hangs with the "Terminating Build Thread..." status line).

Seems to be pretty complicated. For the time being I am going back to version 2.0.0.0 which still works perfectly.

Cheers
manolito

[LIGHTNING UK!]

That's cool to go back a version but this will never get fixed unless you help me do it.

Totally ignore the CLI stuff for a second and do it the old fashion way (via the GUI) and see if you still get the error.

If that works, it will be easier. If it doesn't, it's totally down to you if it's ever fixed or not.

v2.1 solved some much bigger problems so you're well advised to get it working rather than being stuck on v2.0 for all eternity.

[manolito]

Hey, I'm sorry, I know that it is not a positive attitude to tell the author of some great software to just forget about the new version, I'm going back to the previous version.

So I just did a few tests in GUI mode, and there were no problems at all. With the default settings I got a couple of popup windows about volume label and not empty blank. To make sure that this was not connected to my CLI problems I checked all "Don't prompt" options, and still everything worked perfectly.

Going back to CLI mode I got the old problems again, so I believe that CLI mode is to blame.

Hope this helps,

Cheers
manolito

[LIGHTNING UK!]

I set up a batch file last night with the exact same option you had and had it burn the same folder 10 times in a row.

When I woke up this morning the batch file had finished processing an everything had worked perfectly.

So basically I can't find a fault (yet) this end.

When you see the 'terminating build thread' message in the status bar, what else is going on? What does the log say?

Have you tested again after a complete uninstall + reinstall without touching ANY settings / options and just using the CLI line you told me?

As I say, I just got 10/10 working fine when I tried it. Do I need to go for 100 ?

I'll pass on this info to the beta team and get them to do the same. I'll report back if anyone else has the same issue you're getting.

[r0lZ]

I don't know if it can help, but I've had a similar problem with an old version. (I don't remember which one, but that was before v2.)

When I started ImgBurn for the first time after a reboot, and changed my mind, ImgBurn refused to close itself, and the message "Terminating Auto-Insert thread" (or something similar) was displayed in the status bar. Finally, after 1 or 2 minutes, the program was successfully closed.
Repeating the same thing during the same Windoze session worked fine, without this long delay.

Seems there is something strange with the way the threads are terminated, but IMO it's probably a bug in Windoze rather than in ImgBurn. Anyway, I have not experienced this problem with v2.0 or 2.1 anymore.

[LIGHTNING UK!]

The autoinsert one could be different as that waits for certain drive I/O stuff to finish. So if the drive gets stuck doing something that one could get stuck too.

The build thread shouldn't really have that issue but it would help to know exactly which state the program is in when that build thread message appears and won't then go away.

[LIGHTNING UK!]

manolito,

Just in case this applies to you, ensure the 'Auto Calculate' option is NOT checked / enabled.

It causes problems when building from CLI. (It has been fixed ready for the next version though)

[manolito]

manolito,

Just in case this applies to you, ensure the 'Auto Calculate' option is NOT checked / enabled.

It causes problems when building from CLI. (It has been fixed ready for the next version though)
Bingo! This was it, with "Auto Calculate" off CLI mode works perfectly.

Thanks for looking into it,

Cheers
manolito