Defenestration Posted July 30, 2006 Posted July 30, 2006 (edited) I get this error when exiting IB if I do the following: 1) Burn an ISO with my external drive, then turn off the drive. 2) Exit IB I believe you've added support to the new IB which can dynamically detect the addition/removal of drives, so there's no need to display this error. Edited July 30, 2006 by Defenestration
volvofl10 Posted July 30, 2006 Posted July 30, 2006 Its an info message . therefore its NOT a bug. as with anything to do with windows , close the program before removing the drive
LIGHTNING UK! Posted July 31, 2006 Posted July 31, 2006 Indeed, the detection of device arrival/removal probably won't help with that. If it's in the middle of something and you remove the drive, it will error out. If you'd done as you're supposed to and removed it via the system tray icon first, you would have been told it's not possible to do it.
Defenestration Posted July 31, 2006 Author Posted July 31, 2006 The message is displayed when IB is Terminating the Interface, but if IB can detect that a drive has been removed, couldn't this termination step just be skipped to avoid this message ? I realize that you're supposed to remove via the tray icon, and do this with my external hard drive to stop data loss occurring, but it's not really necessary with external CD/DVD drives since no data loss will occur if the drive isn't actually burning. Call me lazy, but it just saves me from an extra couple of clicks when turning my drive off. Just to clarify, I get this message after the burn and verify has completed followed by switching off the drive, so the drive isn't in the middle of doing anything.
LIGHTNING UK! Posted July 31, 2006 Posted July 31, 2006 Well it's no extra clicks to just close ImgBurn before turning off the drive. The next version might actually cope ok with it anyway. It has in my testing.
Defenestration Posted August 1, 2006 Author Posted August 1, 2006 Well it's no extra clicks to just close ImgBurn before turning off the drive. The next version might actually cope ok with it anyway. It has in my testing.OK, I'll check it myself and post back here.
Recommended Posts