ImgBurn won't recognize drive changes in Build Mode

[rajmahid]

I've been using this wonderful s/w since Day One with success, not a single glitch. UNTIL now!

 

After I create a DVD backup image in Build mode, ImgBurn gives me the message "continue, retry, cancel" if I try to build an image of another disc using a different drive (I have 4) and proceeds to tell me "There is no disk in the drive. Please insert a disk into drive x:" and locks up -- no browsing or searching -- I have to manually shut it down. Only rebooting "refreshes" the process, allowing me do use a drive different than the one I recently used. It's never happened before.

 

I'm running XP-SP3 (a new install on a new SATA pc...old one was vanilla IDE with windows 2000). I've rechecked ImgBurn's settings and everything seems fine. My only options when building multiple images with different drives are to reboot or use the same drive.

 

Edit...almost forgot to mention, one dvd drive is sata the other three are ide.

 

Is there something obvious I've overlooked?? Would appreciate some assistance.

 

Regards,

Raj

Edited November 23, 2009 by rajmahid

[LIGHTNING UK!]

If they're the source drive, it's a Windows thing - as is that error message.

 

Do you have autoinsert enabled? The OS uses that to detect new discs in drives.

 

If the OS can see them all when ImgBurn is started then there's no reason you wouldn't be able to use them as the 'source'.

[rajmahid]

If they're the source drive, it's a Windows thing - as is that error message.

 

Do you have autoinsert enabled? The OS uses that to detect new discs in drives.

 

If the OS can see them all when ImgBurn is started then there's no reason you wouldn't be able to use them as the 'source'.

 

As far as I can determine, it's not a Windows thing because I have autoinsert disabled on every drive. The first thing I do when installing an o/s is tweak everything, ESPECIALLY autoplay, via Tweakui and manual methods. I even tried disabling it in all my drives via the registry. Rebooted and created an image file in drive "I", closed ImgBurn and moved the same disc over to drive "J" -- still the same message errors and lock-up, despite having all my source drives readily read. It's a real puzzle because every other image & burn program I have behaves normally, regardless of how many different drives I use.

 

I'll keep searching for a solution...and let you know when/if I find one. In the meantime, rebooting or using the same drive for multiple DVDs is my only option.

Edited November 23, 2009 by rajmahid

[LIGHTNING UK!]

Well that message isn't one from within ImgBurn.

 

If you can 'explore' the drive in My Computer or via the 'open file'/'browse for folder' boxes you can bring up inside ImgBurn, there's no reason for it not to work as a source drive.

 

ImgBurn is only using standard API commands (findfirstfile etc) to obtain a list of files/folders on said drive.

 

Of course without knowing exactly what you're doing and how you're using ImgBurn, it's impossible to say for sure.

 

Perhaps you could provide a screenshot or two showing what you're doing and when/where the error boxes pop?

[rajmahid]

Well that message isn't one from within ImgBurn.

 

If you can 'explore' the drive in My Computer or via the 'open file'/'browse for folder' boxes you can bring up inside ImgBurn, there's no reason for it not to work as a source drive.

 

ImgBurn is only using standard API commands (findfirstfile etc) to obtain a list of files/folders on said drive.

 

Of course without knowing exactly what you're doing and how you're using ImgBurn, it's impossible to say for sure.

 

Perhaps you could provide a screenshot or two showing what you're doing and when/where the error boxes pop?

 

Yes, I can explore all my drives, but when I open ImgBurn ("most recently used" option selected) after the first rip, the attached pic shows what happens when I reopen it with disc in another drive.

 

ADDENDUM: And when I insert the disc into the previous drive I ripped it with, see 2nd attached pic.

Edited November 24, 2009 by rajmahid

[LIGHTNING UK!]

Ok, that's happening because the dialog box has its default directory set to a location (the MRU one) that you've removed the disc from. (So if you leave the disc in it, you won't have this problem)

 

The dialog box doesn't behave like that for everyone (could be related to a certain shell extension?) and Windows really shouldn't moan so much when the path doesn't exist anyway. I've no idea why their 'cancel' or 'continue' buttons don't actually do what you'd expect them to.

 

I have already worked around the issue (a few months ago now) by double checking that the default folder actually exists before atempting to open the dialog box starting at that location. That workaround will be available in the next release.

 

P.S. Get with the times and re-enable themes!

[rajmahid]

Ok, that's happening because the dialog box has its default directory set to a location (the MRU one) that you've removed the disc from. (So if you leave the disc in it, you won't have this problem)

 

The dialog box doesn't behave like that for everyone (could be related to a certain shell extension?) and Windows really shouldn't moan so much when the path doesn't exist anyway. I've no idea why their 'cancel' or 'continue' buttons don't actually do what you'd expect them to.

 

I have already worked around the issue (a few months ago now) by double checking that the default folder actually exists before atempting to open the dialog box starting at that location. That workaround will be available in the next release.

 

P.S. Get with the times and re-enable themes!

 

You're correct, windows still "sees" the disc in the first drive, even though I moved it to another one! I'll puzzle over your "workaround" until I get it...or just keep ripping my discs in the same drive until your next fix emerges. In the interim I'll click until my fingers get blue, but the damned disc will continue to appear as a ghost in the original burner. And perhaps...someday...I'll enable themes to no productive end...despite being a strict minimalist :P

 

I almost wish I'd kept Win2K instead of moving a wee bit into the "future" with XP

[LIGHTNING UK!]

All it wants is *something* to make the MRU path valid so the dialog box can use it as a starting point for browsing.

 

If you say you have 4 drives, each with a disc in them, what's the issue with building from drive 1, leaving the disc in drive 1 and building from drive 2, leaving the disc in drive 2 and building from drive 3 etc etc? When you've done all 4, switch the discs in all 4 drives.

 

Of course the other option is just to type the drive name into the box and click the '+'. Then there's no browsing involved and Windows never gets the chance to throw a hissy fit.