LIGHTNING UK!

Unfortunately nothing last forever in this world and you might just find the drive is getting worse the older it gets. Media quality is also known to vary and although you've perhaps not had problems with that media before now, I would still advise you to hunt out some Verbatim (MCC dye) or Taiyo Yuden media and try those instead. EDIT: For what it's worth, the TTH02 discs tested in the 'Drives and Media' forum also turned out pretty awful when burnt with the Pioneer drives (110 and 111 models).

ok well the only one that could be causing the issue there is the 'siremfil.sys' one. Besides a slight difference in the version number of pxhelp20.sys (2.03.32a Vs 3.00.11B), I know the others all work ok from first hand experience. Try visiting http://www.siliconimage.com/support/ and see if there is an updated driver for whatever 'satalink' device you have installed in your pc. I'm sure Device Manager will tell you the model number of it and from there you can just select it in the drop down box on that support website.

Well yeah duh, it would be, but who says it's a 32bit signed integer?! I can see no mention of that anywhere. In fact, ECMA 119 specifically says the field, 9.1.4 - 'Data Length', is to be recorded according to 7.3.3 - 32bit numerical value. 7.3.3 - 32bit numerical value is defined as: Only for an 8bit field does it mention the word 'signed' or 'unsigned' - and they're the only 2 mentions of 'signed' in the entire document. So.... if you can tell me where you read it's a 32bit signed integer value (which, let's face it, would be pretty silly for a field they know would only hold a positive value!), I'd really like to see it for myself. (EDIT: Also, WinRar, IsoBuster, Windows 95 and Windows XP can all read ISO's with files > 2GB within them and report the full size correctly.)

IE7 Beta 3 Yes, for me, once I click the B it adds the bit and then moves the cursor to the right of what I'd selected and deselects what I'd selected. I'm not sure if you can call it a bug though, it might be by design. If you use the WYSIWIG editor, it might work differently.

Why would it be 2gb only? As far as I can remember, you're allowed to use 32bits for the file size, meaning 4GB is the largest. I certainly impose no 2GB limit.

maybe one day, yes.

lol well that setting only applies to Write mode, that's why it's under 'Write'. Some people just wanted write mode to verify the same way older versions did - i.e. just testing the disc was readable - hence the reason I added that option. Verify mode can't NOT compare against an image file - as the GUI forces you to select one. (in v2, that's now optional)

Yeah maybe the firmware is just fixed for the bitsetting stuff. Bit unusual for a Plextor drive though, I guess they got lazy! As for the verify stuff, it's on the 'Write' tab in the settings. 'Verify Against Image File'

lol I did say to look at the 'Last Recorded' one and not the 'ADIP' one! Easy mistake to make though Did you try looking at the BenQ tab for bitsetting stuff btw?

Plextor are pretty good like that, I had my replacement PX-716 within a couple of days after I sent my RMA request through to them. Hope the new one is better for you

Well it'll just mean that other programs will still get to see changes in the state (ready/not ready) of the media. If they react to quickly, they may stop ImgBurn from doing its job quite so easily - or at all. Back in the old days, if you burnt stuff, you were supposed to disable autorun on your pc. That's basically what that option did - it blocks autorun. There's no reason for the latest motherboard / chipset drivers from your chipset manufacturer not to work (be it intel, nvidia, via etc) so there's a chance that a filter driver is causing the issue. If you download the filter drive load order tool from the following page, load it, select your burner in the list and then hit the 'clipboard' button. Then paste that info in here. http://www.bustrace.com/downloads/free_utilities.htm

Either you have duff verbatims then or your drive just can't burn them properly. It's expensive to figure out which it is though!

lol not on the system tray icon it's not! I doubt that would happen because it's too much of a pain in the arse keeping track of when it should / shouldn't be allowed.

Nothing I can do I'm afraid. The drive sees them as DVD-RW. If it won't let you burn with them, you'll have to try some others or perhaps invest in a new (branded) drive.

Your drivers must have problems supporting the command then (this is not normal, nor a good thing). 2 choices. 1. Fix your drivers. 2. Uncheck the 'Disable Media Change Notification' option in the settings.

I think you may have to ditch the princo +RW's and get some Verbatim / Ricoh ones. Even with the new firmware, your drive still doesn't like them that much (hence the failure during the erase). EDIT: Hang on, a minute ago you were doing DVD+RW's! Now your drive thinks they're DVD-RW (or you changed discs). Either way, I can tell it doesn't like those much because you're missing extra info from the log in terms of supported write speeds and the disc manufacturer code.

Well if you've done a full format it's definitely doing it with the larger of the two sizes. I would have to say that the firmware is the issue here, so hopefully the new one chewy has found you will fix that. Have you actually tried burning that image and seeing if it works, or were you put off by the 'it won't fit' message?

Ah well there's your answer right there. Do a full format in ImgBurn and the 'Current' one should say the same as the 'Maximum' one.

Just stick that +rw in the drive and copy + paste the info from the panel on the right. It'll tell us what we need to know in terms of the space available on it (according to your drive).

Looks like you perhaps did a bit of overburning or something. Compare the size of your image against the size of the final disc. Did it burn the correct amount of data?

Hard to tell what you're talking about here exactly... ImgBurn can BURN/WRITE images of any size really - depending on the size of your blank media of course! The next version of ImgBurn (version 2) can BUILD images from files on your hdd... yes it can do UDF only, and will allow you to create big images by splitting them (if needed) on FAT32 drives etc.

If you've tried different media and are on the latest firmware, your drive is probably on its way out. Try cleaning the lens and perhaps think about returning the defective drive or buying a new one.

There's no reason for the problems you're having to actually be happening then. I could understand it if your new drive didn't burn as well as the last one, but not them both not working in the new pc but working ok in the old, it just doesn't make sense! Assuming they both burn + verify ok, take a look at the graphs via DVDInfoPro - use the 'Display Graph Data using DVDInfoPro' option off the File menu. Then you could also do a PIPO scan of the discs (one burnt from each pc) and compare the two. That is of course if your drive supports scanning!

Eject the drive tray (with the disc in it) and then insert it again. If it's saying 'Logical using in process of becoming ready' and then going to 'Medium not present' in the status bar, you've got discs your drive can't read. A firmware update is the only way to fix that. If it did work once upon a time, try cleaning the drive lens. These things don't work forever.

Yes it will uncheck it if not already unchecked - and the user doesn't specifically tell the program not to update the ifo's. (there's a checkbox for that now if it wasn't in 1.3.0.0, I can't remember).