LIGHTNING UK!

Thanks, I know about the IBB problem. It's because it tries to change drives whilst it's busy doing something else and it hits deadlock. If the IBB specifies the same drives as the currently active one it shouldn't be an issue. This problem isn't limited to the command line either (or rather )

Creating a single layer disc is exactly the same as a double layer one, apart from the obvious lack of a need for the layerbreak box. So basically, it's the same guide but you miss the LB step.

There's an uninstall program / switch for removing the SPTD interface, but you're quite correct, it doesn't get removed when DT is uninstalled. I guess the idea is that other programs could be using it too as it's not specific to DT.

Yeah I know about the Nero interface issues, it doesn't like me using VirtualAlloc for the I/O buffers - and that's not really my problem. I think it's the SPTD interface that DT uses messing things up. Update to the 1.45 beta version and try again (the change log mentions a fix with ASPI layers that wrap SPTI - which is what the nero one does). btw, why not just use SPTI?

You really need to be posting logs when you ask questions/mention problems like this. Without the log there's far too much guessing involved. A 'write error' is exactly what it says - the drive was unable to complete a 'write' operation on the media. There's nothing software can do about that. Look for a firmware update for the drive and consider investing in a cleaning disc.

I just thought it was odd that I didn't see it happening under XP. In any case, I'm pretty sure that whatever it was has been fixed now. If you look at your last screenshot you'll see an empty bit of window where the listview doesn't reach the bottom of the actual form. Fix one thing, break something else... it's sod's law!

Getting back to the other problem... I've stuck a vmware session of XP into 120dpi and done some testing. I've made a few changes and hopefully it looks better to you now. I certainly have no issues with the log window shrinking, but to be honest I'm not sure I ever did! (perhaps that could be a win2k specific problem?) The log window lines and drive comboboxes now scale depending on the DPI selected - so the text isn't cut-off anymore. They are custom drawn, hence why they didn't just work by default like all the other controls.

That's the error, not the other one. Your drive can't write to the disc, hence the 'Write Error' status code it's returning to the software. You could try slowing the burn down to 2.4x, but really you need to stop using the cheapo DL discs and buy Verbatims. They're the only ones that seem to work reliably.

Again, all the 'Current Profile: Unknown (FAILED!)' bit means is that the 'Get Configuration' command isn't supported by the drive. This is true of many old CD drives. Sure, I could pretend it doesn't fail, but then that doesn't really help / tell me anything. As you can see, it doesn't really matter anyway. The program works around it when it needs to.

When I said 'mates standalone', I wasn't talking about a specific device, I meant do they work on any of your friends standalone players? If they play on your PC but not on your standalone, perhaps it's the standalone that has the issue?

The Plextor drive isn't MMC compliant and that's what ImgBurn is based on. It's the drive that's failing to report the current profile, not the program - the drive probably doesn't support the command used to get that info. That's also why the read command is failing, the drive just doesn't support it. I expect the log window issue is due to you using large fonts or something. It certainly doesn't do that if everything is 'normal'. The window jumps in stages so that the listview height is a multiple of the individual line height. If it's a few pixels off, it'll jump down to the next closest multiple.

I think this is just due to the way widestring -> ansistring conversion works. It makes a multi byte ansistring where I just want it to convert to straight forward single byte ansi. I've now changed the code to use the WideCharToMultiByte string API for the unicode -> ansi conversion and have told it to use the ANSI codepage via the CP_ACP flag as detailed here http://msdn2.microsoft.com/en-us/library/aa370284.aspx Hopefully that'll fix the issue. If you remember, please do pop back and let me know if it has! (I've no idea when the next version will be ready so it may be a while before you can test it)

Depending on what you mean here exactly, it could be 1 of 2 things. Either the 'close tray' command is failing (and so the tray stays open), or the drive just isn't able to initialise the disc after that first cycle. If it's the first option, press F8 before you do your next burn - or rather, just before it finishes the burn so the program will log the commands sent to open / close the drive tray. That should show me why it's failing. Post the log when you have it. If it's the second option, tell me exatly what it says in the statusbar once the program has ejected / reinserted the tray, and yet is still saying 'waiting for device to become ready...' in the log.

The device tab doesn't always apply and hence isn't always visible. The most useful settings (frequently changed) are those on the 'options' tab anyway!

As you're only burning an ISO, there is very little room for error. The thing that strikes me is that your PC seems unable to sustain a steady stream of data - even when you're only burning at 4x! You should NOT be seeing those buffer recovery messages if your machine was running correctly. Do the discs you're burning play on your PC? Do they play in a mates standalone?

Are you creating an image on the same hdd as the files? Obviously that would involve a lot of random accessing and hence take ages. Why not just burn on the fly? There won't be any difference in the final disc.

See LFC's comment above. CMC media is shite.

lol ImgBurn should NEVER be sold, it's Freeware. I've never given anyone permission to sell it and I certainly don't sell it myself!

What does it say in the info panel on the right? Copy + paste it all. If you can do Tools -> Drive -> Erase -> Full, and it still says the same thing, your drive doesn't fully support those discs. There is no specific 'format' option in the program, it's done automatically. To be honest, plextors are pretty useless with rewritable discs (well, my 760 is anyway). I always have to resort to using another of my drives for anything I want doing on a rewritable.

I doubt it's a joke, I get these all the time. People get conned into buying those crappy packages that bundle freeware. Then they realise they're stupid and just contact the first email address they find.

It definitely sends an eject / insert command combo, so why it's not closing is anyone's guess! Just press the button on the drive manually to insert the disc and it'll start verifying if it's been told to.

It's primarily a burning tool though, not really a 'reader'.

This is nothing to do with ImgBurn, it's simply a burning tool. You need to look at whatever program you're using for the authoring / conversion stuff. If you're actually just writing *.mpg / *.avi files to a disc using ONLY 'Build' mode, your player must have duff support for those files. Check to see if there's a firmware update for your player.

Yes, if you've not added one yourself, the computer would need to have had one inside it when you purchased it. Currently, yours does not - hence you cannot burn DVDs. They're only about

Yup, I think so! (well, it appears to anyway )