LIGHTNING UK!

Covered in the bugs forum (and has now been fixed). Sorry!

It's remembered your settings for ages. Previously, you must have been uninstalling then reinstalling - that of course would wipe out your settings.

I couldn't see such an attribute in the filesystem specs.

Oops, no, scrap that! At the level I was bodging the support for the old style shortcuts, the windows messages don't seem to differentiate between upper and lower case letters. That must come later or something. My 'case' statement however was checking for: case 'b': case 'B': { // do some stuff } break; But really, I only needed case 'B': { // do some stuff } break; The 'case 'b'#39; was the cause of the issues as 'b' as a value is the same a the numeric keypad '2' key. In any case, it's fixed now. Thanks

lol for some weird reason the numeric keypad keys have the same values as some normal letters on the keyboard! So, keypad '1' is actually 'a', keypad '2' is actually 'b', '3' is 'c', '4' is 'd' etc etc. In modes that don't generally accept keyboard input (for file names and a like) I let the old style 'mode' shortcuts still work - i.e. 'b' for build mode, 'l' for the log window etc. (rather than ctrl+alt+ So keypad 2 wont work because it switched to build mode. Keypad 4 won't work because it switches to discovery mode. I obviously need to use some other part of the windows message to find the difference between a real 'a' and keypad '1' etc. It's ordinal number clearly isn't enough! Alternatively I'll just ditch the old style shortcuts where people could switch modes with a single keypress.

Only old games tend to have multiple tracks. CDDA is a major waste of space so most would now use compressed audio formats (i.e. MP3 or their own version of it)

The program can't make bad burns like that, it's just not possible. All it does is supply the drive with data, the drive does the burning and has full control of the burn quality. If you get a read error during a verify, it means the drive failed to write to the disc / those sectors properly - again, there's nothing the program can do about that. It's a shame you don't have the logs... those and the IBG (Graph Data) files can really help in situations like this. It's odd that you say both buffers were emptying towards the end of the burn, that would indicate a problem reading from the hdd. If it was just the device buffer, I could perhaps understand it.

If it's estimating a burn time of 35 mins, that's about 2x speed. You should be burning at 8x so that's way to low. As such, I'd say you have DMA issue and should therefore checkout the post in the FAQ that tells you how to fix them.

It looks like the drive is producing duff burns and is unable to reinitialise the disc properly after ejecting / reinserting it. This sort of stuff is beyond the control of software. The drive just isn't doing what it's told.

Why don't you set the eeprom values, then you won't have to touch it again?!

Isn't it 'Normal (3)' ? I don't have the official specs for booktyping on LiteOn drives so I don't actually know what '3' means. I expect it to be a 0 or 1 I think, but 3 is typical of a drive where no setting has been configured.

Count the slashes, not the folder names. You don't see the 'Root' folder but it IS there! The original image breaks the specs in more ways than just directory depth. All of the options can be adjusted to get a working image though - including one to get around that initial problem.

It's probably too late now but I'd have like to see the info from the panel on the right within ImgBurn when the disc was booktyped to DVDROM. ImgBurn doesn't care about the booktype value, it's looking at the 'Current Profile' field most of the time - and that's what the drive thinks the disc is. I bet what actually happened here is that you've got Alcohol emulating DVDROM for writable media and so ImgBurn never sees the disc for what it is. Turn the option off in Alcohol and your problems will go away. Alcohol does this itself automatically when IT wants to burn a disc, that's why it works when nothing else will.

This is covered in the FAQ anyway. In vista, the sidebar is also known to use the drive and hence prevent ImgBurn from obtaining exclusive usage of it.

Only if you load a project with that info stored in it. You can manually edit the project file and remove anything you don't need / want to change.

your drive doesn't think there's a disc in it - or at least that's what it's reporting.

well i did just say it was a cosmetic issue and the button i made up was quite cute

Have you tried IsoBuster? It's designed for this type of thing.

yeah you can't convert it to an ISO because the disc is made up of 3 tracks and an ISO can only ever be 1 - unless there's some file with it that says differently. The thing is though, you've got almost no space left on the disc, why not just close it and then everything will read it fine - i.e. windows. You should then just be able to read the files off it without an issue.

Cool ok, thanks. Right now with ImgBurn how it is there, eject the disc. Then press the F8 key, then insert the disc. When it says 'ready' in the status bar again, press F8 a second time. Then save the log and attach that.

Still no chance of a screenshot then? You can obviously use Microsoft Word so you only need to press the 'Print Screen' button (up by the F12 key) and then select 'Paste' from within a blank Word document. Because basically, what you're saying doesn't make much sense. If DVD Dec can display the disc info, ImgBurn should be able to too. Only ImgBurn will give me more useful info, hence why I'm asking for it.

It amazes me when people question what ImgBurn is doing trying to connect to the internet after they've told it to check for updates. Where's it gonna get that update info from if not the internet?! 'But why those sites?', you might ask... well, surely how I have it check for updates is down to me? (corny already explained the reason - and it's been covered before if you search). All you, as a user, have to decide, is if it does it (full stop) or not.

This is a borland c++ builder application and language dlls are not something I've done before.

Details, downloads etc on the main website. http://www.imgburn.com

If you're using Verbatim discs and are on the 1.29 firmware, I'll pass. If you're not, start using them.