LIGHTNING UK!

ImgBurn cannot be used to backup your DVD collection.

The log shows you didn't infact press F8 (or at least not when ImgBurn was the active application). If you had, it would say 'I/O Debug Mode Enabled!' in the log - and it doesn't. Give it another go

lol well that's 200 from the people at imgburn.com today alone!

I think you mean there WILL BE.... (it's not out yet!) It's just a very basic one that'll let you read DATA CDs and DVDs to an ISO image.

I believe lmao2k used ebay. I have word from SVP that the Verbs are expected back in next week.

Even once you've configured ImgBurn to force the 'video' files to the start of the new image, you'll still run into layer break problems unless you add an identical amount of 'data' files. This is because the program will attempt to burn equal amounts of data on each layer (a dvd is most 'compatible' when it's written that way). It's actually kinda funny that storage space means more to you than the difference in cost between single layer and double layer media! (in the UK that's about ?1.50 per disc!). Just buy a DJ case that holds 1000 discs or something - if you burn more than that, you may like to re-evaluate things anyway!

To be honest, I've never even thought about it... and I've certainly never measured its usage. I put controls on the various forms via the Borland development environment and just get on with the actual coding. ImgBurn pretty much runs from 1 form with multiple 'panels' on it - one for each mode. Panels get hidden when not in use and made visible when they are (I'm sure you get the idea). Looking at the app under XP etc shows it to start with about 750 ~ 800 GDI objects. I guess that's a handle for every edit box/label etc on every panel of every form - so it looks about right to me. As I've no intention of changing anything (unless it'll take 5 mins and someone tells me exactly what to do!), I guess you'll have to find another solution. Sorry!

No idea, that's down to DVD Styler by the sounds of it - that's the authoring program, right? When you've added your video + audio and laid everything out properly, just get it to 'compile' the disc - but not 'build' it. Hopefully the compile bit will mean it make a VIDEO_TS folder with VOB/IFO/BUP files in it, rather than 'building' an ISO file.

I'm not sure that's what Drakkenson meant. If it was, my apologies... I'd have just recommended DAEMON Tools. Mount your ISO in the DT virtual drive and view it as you would do any normal CD / DVD via explorer. On the other hand, if I understood the initial post correctly, Drakkenson wants to add folders to the 'File' mode from all over the place (multiple drives etc) and then have ImgBurn create a kind of root folder in 1 single place on the hdd with all those random files combined. i.e. take C:\Folder1 and D:\Folder2, then output C:\Root\Folder1 and C:\Root\Folder2. It just seems like a bit of a tidy up exercise to me!

Your image contains info that the drive is 'correcting' on-the-fly as it burns - whether you want it to or not. ImgBurn cannot help you with this disc. MODE2 images are fine... IF the data in them is correct in the first place - i.e. the EDC / ECC regions must be correct/valid for the associated 'User Data' area of the sector.

Didn't think to get any???!!! lfc, I think we have a dbminter impostor on the forum!

Yes that's right, the help files (guides) tell you how to burn stuff - because that's all ImgBurn does. Sorry but we cannot help you with anything other than burning.

Add a new DWORD type registry entry to HKCU\Software\ImgBurn called 'OVERRIDE_DeviceBufferWithLogging'. Set it with a value of 1. Then press F8 before the burn starts - i.e. before you press the 'start' button. Save the log once it's finished and attach that in your next post. NOTE: I can't remember if that option is only in this next version of ImgBurn (v2.2.0.0) but it's worth a try anyway!

Don't you just want to backup your documents?! i.e. the 'Documents' folder within your user area? There's a whole load of other cr@p in the 'Document and settings\[username]' folder that you really don't need. The one you're stuck on there is a file that your registry maps to - as such, it's always in use and no other program can read it. If you want to backup that stuff, use a proper backup program.

The whole SPTI thing is a synchronous process. Once the API function has been called, the thread that called it is stuck until it returns - you can't even forcefully terminate the process. Being that it's I/O, it basically pauses the entire system and no others (or at least not many) will get processed until is works / errors out. So basically, once it's hung, it's hung - reboot the pc! As mentioned in my previous post, it's pretty simple for me to just not issue that 'mode sense (6)' command - depending on error codes returned by the previous 'mode sense (10)' failure - the 'mode sense (6)' command is just a fallback anyway (for old drives). I've already implemented a workaround ready for the next imgburn but you still run the risk of any program that just so happens to issue the same command, hanging in the same way. It's hard to say exactly where the problem lies. You'd have to put the drive in a real Windows based PC and see if it does the same thing. It could be the drive, the drivers, the OS, the virtual machine.... anything!

I believe these are borland errors from their own memory manager so MS's help isn't really relevant. (Thanks for trying though dirio49 ) It would help to know when it's popping up and what the error box looks like! (hint hint screenshot!)

Something doesn't like the 'Mode Sense (6)' call and isn't playing nicely. It should either work, or it should error out. On your system, it's doing nothing... and hence ImgBurn just sits there waiting patiently for a reply. As soon as it gets one, it'll continue - but of course, that's obviously never going to happen! I can tweak ImgBurn so it never makes that call (it just gives up after the 'Mode Sense (10)' command fails) but that's a workaround an not a global fix.

Happy birthday mate, I wondered who this thread was for when I first saw it.... your name wasn't in the 'Today's Birthdays' list (stupid timezones!)

2.4x is the lowest speed for DVD+ format media anyway. Not that I've looked very hard but I've never seen a drive supporting anything less than that. One of the orignal benefits of the plus format media was that it burnt quicker than any available minus format media. (i.e. 2.4x Vs 1x or 2x). Obviously that doesn't apply now though

This is certainly not something to implement in ImgBurn.

Actually the files and the dvds can be region coded. Blank discs do not have a region code associated with them.

Do you know what you're burning? Is it an AVI file? At 701MB, it doesn't sound like it's a DVD Video image. If so, do you know for sure that your player even supports playing AVI files?

A full log with F6 debug info should also tell you (me) why the device MD5 could not be calculated - i.e. where a call to the API's failed. That said, there were glitches in the MD5 code that have now been fixed. Maybe you're just hitting one of those.

That's what's in the drives firmware, this is nothing to do with ImgBurn. The drives are idential, Sony just brand/sell it as 'UL' (rather than 'A') because they've stuck it in an external enclosure. Thanks for the donation btw

bin/cue images can be complex - i.e. more than 1 track / session. ImgBurn doesn't support that. If the bin is just a simple image, it should burn it fine - but you'd need to open the cue file in notepad to be sure it's a basic bin file.