LIGHTNING UK!

For copies, if it's less than 1, it becomes 1. If it's greater than 100 it becomes 100. IBQ via CLI is actually a 'no-no' at the moment. The code that initialises the file passed via CLI is called before the code that initialises the devices - this was never an issue before as the file didn't rely on knowing about the drives. With IBQ2 files, it does. Because no devices exist, you'll never be able to use anything other than '-1' for a device number. I'm not sure why the /start thing isn't working for you though. I can only guess it's due to some race condition where it tries to start the burn before the files are initialised or something. That said, when I just tried: ImgBurn /src "E:\ImgBurn.ibq" /start it worked fine, as did the same but with /waitformedia shoved on the end!

Try just changing your E:\FOLDER~2\..... etc to "C:\Program Files\Internet Explorer\iexplore.exe" -nohome copy + paste the entire thing - including the quotes. If that doesn't work, I'll export my reg entire 'http' key

double click that 'default' entry and then copy its value into the clipboard. Try clicking start -> run and then pasting it in and clicking ok. Does it work? Paste it here too so I can see what it's doing. Mine says: "C:\Program Files\Internet Explorer\iexplore.exe" -nohome You could always just open IE and tell it to make itself default again via the 'Internet Options' dialog. It's on the 'Programs' tab.

Ejecting / reinserting can sometimes fix the problem - it's just when the drive hasn't / can't initialise the disc properly. Failing that, if you can't find a firmware update for it, you'll have to use some different discs.

It's 'http', not '.http' ! Look down a little more

Shame you have all that messing around where you are shamus. Here in the uk things just tend to work right out of the box! ADSL2 is supported by current hardware, it just might be that the router needs a firmware update. I know for sure that's the case with netgear ones.

I assume you've tried it just on 2.4x too? Your best bet for help with this kind of stuff is over on the BenQ forum at cdfreaks. There's a whole bunch of people who do nothing but talk BenQ. I'm sure someone there will tell you the best settings / firmware etc for burning those discs.

Your drive is an OEM BenQ, it's not a LiteOn model. So try the BenQ tab and see if that works. Most drives now default to DVDROM for DL media anyway so you might not need to do anything at all. btw, 1.0e is the latest firmware. http://forum.rpc1.org/dl_firmware.php?download_id=2179

Well I can't think for the life of me what it could be, that's why I'm hoping the log will give us more info. Don't forget about the verify part too please.

Happy one, please explain why you're calling these discs coasters. Do you have a log to show us or anything? Do you get the program to verify what it burns? If not, now might be a good time to start doing so.

please don't forget to use the 'verify' function within ImgBurn. It will tell you there and then if the disc is readable. DVD Decrypter was pretty dumb when it came to DL burns. The only thing I can think of that really happens DURING the write that's different though is that DVD Decrypter would/could burn across the LB break, whereas ImgBurn will burn upto it, mention in the log that it's burning layer 2 now, and then start layer 2. ie. if L0 and L1 are 16 sectors each (32 in total) DVD Decrypter would just burn all 32 sectors in 1 go. ImgBurn will burn 16 and then 16 again. If there is a problem with this, the fault is the drives firmware. It certainly wouldn't be the first fault either. I reported odd happenings with DVD-R DL burning a few weeks ago to LiteOn and they reproduced the problem their end and fixed it.

Welcome to the world of Ritek DL media.

Yeah, that's what I'm thinking.

and please.... ensure you have ImgBurn do the 'Verify' part.

Your drive is just having trouble finding correct laser power setting for burning that media. I assume you've tried burning at 8x too? Same issue? TYG02 are good discs and you've got the latest firmware. As such, you're pretty much out of luck. Search google if you want to learn more about 'Power Calibration' errors.

in that case, it looks like something has messed up your url opening capabilities. probably because IE isn't your default browser anymore. The api function (ShellExecute) is supposed to invoke the default browser if an URL is passed to it - which is what I'm doing. You need to look at the registry, at 'hkey_classes_root\http\shell\open' and see what it says. As a side note, the links have never (nor the way they're called) been changed since the day they were added.

You assume correctly.

What exactly does it do when you click the link/button? Does it open up Internet Explorer and attempt to go to the page?

look in the log when burning. If it says 'layer break method: copied from original', that's the best it can get. There must be another problem somewhere else.

Just an update... I've sorted the icons thing.

No, 'complete' is the correct terminology. Glad that one works better for you... I did tweak some of the code when I realised pioneer didn't return the status in a nice fashion.

lol silly compacting utils! I never expected them to kill basic functionality of the app icons. I will look at sorting that out. I guess the log history thing is where it's supposed to remember the last folder. lol the code is there for it to do that but it appears if the filename field contains a path, the open/save dialog box uses that path rather than the 'initialdir' path. Whilst I'm fixing things, do you think it would be better to fill out the 'file name' bit with the last name you used, or just default to ImgBurn.log as it has been doing. Maybe a different answer for the individual open / save boxes would apply here. i.e. open defaults to last folder + last name save defaults to last folder + 'ImgBurn.log' name. Take your pick

You guess correctly

I could probably improve the udf parsing code to try and automate that bit a little further. I'll look towards doing it for the next version. It's actually nice to know there are problems with the images sometimes though - rather than shielding the user from them.

Please show us your log file.