LIGHTNING UK!

You can always opt out of whatever OpenCandy offers you.

I'm afraid I can't do anything with that. Try booting into safe mode and see if you still have the same problem. It's probably caused by other software running on your machine.

That's nothing to do with ImgBurn. Your drive can't burn DVDs, it can only read them (and burn CDs).

Yeah, the drive thinks it's busy doing (writing) something. You'll have to power it off properly (and on again, obviously) to reset it and get your disc out.

Do you have any discs that aren't 'VERBAT-IMe-000' ? If you don't already have one, get yourself a BD-RE disc for additional testing. Can I please get you to right click the drive selection box and select 'family tree'. Close the prompt that comes up and then copy+paste everything from the log window. Thanks.

Yes, the OS the application is running on makes no difference.

Normally it's always preceded by a 'Write Error' or similar error. Then as the program attempts to retry sending the same 'Write' command again, *that's* when it would normally get the 'Invalid Address For Write' error. I'm wondering if something else installed on the machine (filter drivers etc.) are swallowing the *real* (first/initial) error message and ImgBurn isn't then seeing it. It basically means the program is asking the drive to write to somewhere it can't. Writes should be sequential and due to cache in the drive, the bit on the disc it's physically writing to doesn't match up with where the program thinks it's up to - hence you get an 'Invalid Address For Write' error when it retries. Did you try burning in Safe Mode?

Post the log of you burning the disc please. Also, if you go into Read mode when your burnt disc is in the drive and click the 'View Media Information' button in the 'Source' box, does the CD-TEXT show up in the window that opens?

I could, but where's the fun in that? Visit an xbox360 related site and do some reading.

You won't get a decent slim line one that'll do the job. Get an external enclosure and one of the drives recommended for burning that sort of stuff (the info you require is all over the Internet if you Google it).

ImgBurn-setup.exe isn't the name of the normal setup program. It should be 'SetupImgBurn_2.5.8.0.exe' for the current release and it shouldn't require internet access to install.

Forget ISO files, they aren't what you want. You make the image of your physical drive and use it as the basis for a virtual hdd within virtual box. Optical drives, ISO images etc don't even come into it. Once you have virtualbox up and running with the image of your real hdd, just delete the folders from the hdd image from within the virtual machine. Get it working and then clear it up later!

I just googled 'image of hdd for virtual machine' and came across this... http://www.makeuseof.com/tag/create-a-virtual-machine-image-of-your-existing-hard-drive-windows/

Procmon is also showing the failure to read from those files, with the result just saying 'Disconnected'. So I can only assume there's some issue with that source drive - i.e. X: or whatever. What you really need to capture is the point at which the file becomes unreadable (so a log entry showing the file was opened successfully, several successful read operations and then the one where it fails) and then try to find out the actual cause of what I assume is a network file, suddenly becoming unavailable. Solve that issue and you won't need ImgBurn to perform these extra retries etc. I know I'd prefer to have a stable system than a bit of software that may or may not be able to work around those system instabilities.

Thanks, I just wanted to double check the drive still sees the disc (it supposedly burnt) as still being blank... and it does.

Well, you could try burning in Safe Mode. Also try cleaning the drive with a cleaning disc. The initial error (before any retries take place) is the important one in these situations and it's weird that you're getting the one you are ("Invalid Address For Write") as the initial error... that's not what I'd call 'normal'.

What you'd do there is take a complete image of your hdd with a proper hdd program and then convert it into a format supported by VirtualBox. I'm sure if you Google it, you'll find a guide for getting a real OS install working in it. You're barking up the wrong tree by trying to use ImgBurn for it though.

It looks like your drive did a bad job of burning the disc. Have you tried burning at 4x or 6x rather than 3x? (Notice 2.4x isn't even an option for your drive/firmware/media combo) Put that disc back in the drive, load the program and put it back into 'Write' mode. Then copy + paste all of the disc info from the box on the right please.

1. You won't be able to boot from any image you create like that simply because an optical disc is a read only device and the OS will want to write to somewhere. Even if you did manage to make it bootable, it would just crash at some point as it loads. There must be clever tricks used by the likes of 'Hiren's Boot CD' (boots up Windows XP) etc. to get the system booting from a read only device (using a RAM disc or similar for the writes). 2. Not in 'Standard' input mode, switch to 'Advanced'.

Yes, it's a buffer in system memory. So it goes... Source (hdd or whatever) -> Buffer -> Destination (Optical drive - or rather its internal cache). Internally, the drive would then read from its internal cache and do the actual burning.

You should probably google for how to install XP from a USB stick and just do what it says. I've never seen a protected OS disc from Microsoft so ImgBurn's Read mode should work just fine if you need an ISO. If that isn't what you need, explorer shouldn't have any trouble copying the files off the disc.

It probably told you to push the tray in again if you have a laptop.

You aborted the verify stage, so I can't see if the disc is actually ok or not.

Post the log please.

I'm a little concerned that the 'Retry' option isn't working when you say you can manually browse to the file and open it yourself. The error is coming from the OS, so that really shouldn't be the case. Of course if that error pops up in the middle of trying to read the file (which I think it may well be doing), that could explain things. When it retries the read command, it won't be attempting to open the file handle again, it'll just be trying to read from it using the existing handle. The exact error message is really important here, so if/when it happens again, please try and provide a screenshot so I can see exactly what's going on and what it's saying. Should you be so inclined, it would be good to see the output of something like Process Monitor when ImgBurn issues the API call to read the file that then results in failure. Thank you for the donation and thank you for the heads up (actually, a reminder) about the on going PayPal address issue. I've actually emailed them now to see why changing the 'Country' drop down box doesn't change the remaining address type options to match whatever that country would use. Seems like a bug to me.