LIGHTNING UK!

ImgTool Classic from http://www.coujo.de

Without seeing the suggested output from PgcEdit and the info from ImgBurn, I can't really say for sure where the problem is coming from. Obviously they should both say the same, or at least offer roughly the same options for potential layerbreak positions.

I'm guessing the problem is media related (spinningwheel's Number 2) Skipping / jumping is a sure sign the drive cant read the disc properly.

Stick the 1.03 firmware on the drive too. BTW, what does the program say in the info panel on the right when you put that disc in? 'Current Profile: None' is somewhat strange!

FYI Multiple copies + a queue system has now been implemented.

Indeed, a waste of time! There is no registry entry involved when going from PgcEdit to ImgBurn, it's done via CLI. As such, there would no way for ImgBurn to know where PgcEdit wanted the LB if you're rebooting and stuff. After that, when burning in ImgBurn, a dialog box should pop up offering choices of where you can burn. What info are you getting in that box? Right click on the 'Sectors' value on the main screen and you'll can get an idea of where ImgBurn thinks a layer break can go - without needing to actually burn anything.

LOL I like that one!!!

Sorry, it was always available for me so I assumed it was for everyone! It's enabled now and should be pretty obvious how it works

Why not go for a 4550 / 4551?

#39;( I do believe I fixed it

I know what you mean Moe but I don't think that would work too well in practice. It's obviously simpler from my point of view to just add another drop down box, but that then clutters up the GUI a bit. It also then brings in the possibilty of people accidently changing the wrong box for the media they're burning. If I was to combine them into 1 box via code and display the right box depending on the inserted media, people are bound to change the value with the wrong media in the drive, eject the disc and insert the right one, only to find the speed they'd selected had vanished and been replaced by whatever they last selected for that media type. The speed for the other media would then also be wrong. I hope you see where I'm going with this

A quick snoop of cdspeed shows that there's is no easy of doing it. By that I mean it's not like DVD which actually stores the ID (in a readable format) on the disc, it's just a bunch of numbers (Which is exactly what Wesociety said earlier). I'm not one for building databases into my programs as they always go out of date and I may not be around forever! lol

Maybe invision switched from using " to terminate strings, to using '. It is a different version of the forum software and I believe it was quite a big overhaul.

Incorrect naming on DVD Dec's part, that's all.

You may be better off talking to vso about this. Try to find out what they're doing their end that could be causing it to interrupt the burn process.

There are a couple of differences if you use NT4 and the SPTI I/O manager. Shouldn't be anything major though, and leaving it without that compatibility setting certainly shouldn't crash things! Turn that thing off again and try to start the program whilst pressing down the F7 key. That'll disable all the I/O stuff and it may offer more clues!

There are a couple of differences if you use NT4 and the SPTI I/O manager. Shouldn't be anything major though, and leaving it without that compatibility setting certainly shouldn't crash things!

NT4 SP6a, no problems here I'm afraid. If you can find a memory minidump or something, I could probably tell you which driver is causing the bluescreen. Apps themselves don't generally kill things in that way.

I shall check it under NT4 now!

Are you using the patin-couffin I/O manager? If it really does happen the second you close the app, I can only guess divxtodvd is doing something weird with the drives that interrupts the burn process in a way that the burner can't recover from.

To test if ImgBurn can find the layer break position properly, load the image up via the browse button or whatever. Then right click on the value of the 'sectors' info in the source box. You should get a context menu pop up mentioning something about layer breaks.

There's always a trade off with those smilies! If you put ' around the code, you can't use ' in the smilie - which that little crying fella does use. If you put " around the code, you can't use " in the smilie. Don't think there is anything I can do

Hiding my program so people don't know it's being run is not something I'd ever do.

lol thanks, I do try

You use the /SPEED CLI switch to set it at runtime, or don't specify that an it'll use the last one you selected.