LIGHTNING UK!

You shouldn't believe everything you read. Things change! No, your problems shouldn't be Vista related. The errors should be coming directly from the drive itself. The image / software being used / OS have nothing to do with anything. This is purely a hardware / media issue.

If you look at the log, you're actually on the x.57 firmware. http://forum.rpc1.org/dl_firmware.php?download_id=2017 Update to the x.58 one from the same family. (Probably this one http://www2.melcoinc.co.jp/pub/hd/dvmrdm16fb_fw858.exe )

Switch to Verbatims and your problems will go away. They cost a bit more, but at least they work Try the 1.21 firmware update too.

If you think you've messed up a setting, uninstall and reinstall. Your settings will get wiped out and you'll be back up and running again. However, if you want us to tell you which setting is killing things, you'll need to get us a screenshot of the 'Build' tab in the settings and probably one of the 'Options' tab when you're in build mode too. It could also just be a case of you hitting the wrong button when prompted on what you wanted to do with the files you'd put in the 'Source' box.

$700.... yeah ok!

No, that line doesn't mean what you think it does. It's simply a generic term. I can only assume one or more of your filter drivers are messing things up and making that API call fail in the way that it is. Obviously I don't know what software you actually use on your PC, but I'd be inclined to remove the following two filters: sscdbhk5 drvmcdb On the other hand, try turning off all the CD/DVD related tools you have running - they'll probably be sitting in the system tray.

Please feel free to email me any small (i.e. the 5k ones) .GI files. I'll examine them and tweak the .GI parsing code. The address can be found in the program's 'About' box.

Windows is erroring out so there must be something wrong with your setup. Do you have any odd programs running? Maybe some packet writing software? Can you please post your filter driver info (look in the 'Tools' menu).

The content of the image you're burning shouldn't even come into it. If the drive says it can't read a specific sector, it can't read a specific sector. Nothing I can do or say will change that. What you have here is a hardware issue - or if it's software, it's something working at a lower level than ImgBurn, making it seem like a hardware issue. As for reporting Shamus.... You started it by calling him a 'snob'. Don't give it out if you can't take it back.

Ok, I've had a quick look. Are you getting an error about opening a file? One where the filename just shows random characters? If so, I believe I've fixed that problem. I think I've located the actual byte in the 'header' that tells me how many 'file descriptors' are in the GI file. Previously it was a bodge of just dividing the size of the gi file (minus the header size) by the known size of the file descriptor. So for the one I just looked at, that came out to 5 but there were really only 3, hence the last 2 filenames came out as complete rubbish. That 'bodge' did seem to work with Prassi Ones files though so I guess they've stopped putting stuff after the file descriptors now. btw, the only .gi files supported are the ones where there's a tiny .gi file and then a bigger one (or more). i.e. image.gi (about 5k in size) image (11).gi (up to 2GB in size) image (12).gi (up to 2GB in size) etc.

You'd be better off asking these questions on a forum that deals with burning WMVHD discs for the XBOX! This forum is about ImgBurn and whilst a few people might dabble, you'd still be better off asking elsewhere.

If a simple 'Read' and 'Write' doesn't work, we can't help you. Sorry.

Nah it's ok, I used to use PrimoDVD too years ago. I'm sure I still have it floating around somewhere. If I don't, I'll get back to you.

New drive it is then.

Sorry mate, I don't know exactly what the problem is. Obviously your error is right there, but I don't know the REAL cause of the write error, especially if it happens to 10/10 of those CDR's on the 112 and yet the 111 can burn 10/10 just fine. I can only assume it's some rather large firmware glitch.

I've only tested it with basic DVD ones made by Prassi Ones. So if they're different to that or not DVD images, I've honestly no idea.

lol it's broken! We'll just have to wait and see when it'll get fixed. Keep an eye on that speedlabs forum.

Nero? Why are you on the ImgBurn forum?

Yeah, your drive is ancient and the media is new... that never really works out! Try the 2.18 firmware update. http://www.de.nec.de/software/1859_FW_ND-2510A_win218.zip

Update ImgBurn too or you'll not benefit from the various bug fixes.

If the drive is erroring out with a 'Write Error' error message, you can really only take it at face value - the drive failed to burn that/those sectors on the disc. Quite why that is, is anyone's guess! Try a few more and if you keep having the same problem, try switching the 'Write Type' in the setting to 'Packet / Incremental'.

Rewritables never work as well as write once discs... get used to it! Try a different make (dye) of DVD+RW, maybe the drive just doesn't like Sony ones. You don't need to touch the booktype stuff, just leave everything on the default settings. The problems you're having here are totally unrelated to that.

Buy yourself a new burner. If the one you have now won't even make decent burns on Verbatims, you've little choice!

An ISO is an image file. The program reads a bit from the ISO (image file) and writes it to the disc. Look again at the name of the program for a second... 'ImgBurn'....'ImageBurn'.....'Image Burn' - yes, the app is totally based around burning images. So if you want to burn an image file (ISO), you use 'Write' mode. If you want to make an image file (ISO) out of random files on your hdd (or just burn them directly to disc), you use 'Build' mode.

Ok, saying it's a 'dell' machine doesn't really help. Stick one of the blanks in the drive (when in write mode) and copy + paste everything from the info panel on the right.