LIGHTNING UK!

The only way to be 100% accurate is to show things in bytes (or sectors), that's kinda why I do it that way.

You don't need to donate for us providing support. Besides, it's unfair that I should get them when I'm not the only one helping!

I'll happily pay up to £30 for little software tools like that (and by that I don't mean decrypters, I mean any little tools) if they do their job well. At the moment, 49 euros is about 38 pounds.

ImgBurn doesn't crash your PC, your drivers do. (or some external factor such as dodgy psu or overclocking) It doesn't work at a low enough level to cause a system crash.

I honestly doubt nero would format a brand new disc (i.e. just unwrapped). You simply cannot issue a 'write' command until you've issued a 'format' one - and so unless it's somehow bypassing the dodgy driver, I don't see how it would work. Also, you say you've got a 965 chipset board so I guess you're using a 3rd party controller (I don't think Intel included one in the southbridge). That's where the problem lies. When I asked for the 'controller' info from device manager I did actually mean controller (as in the ide controller) and not drive. Could you please check again for me.

You have to fix your drivers so that the command is acutally passed onto the drive and not terminated early. What motherboard do you have? Which controller is the drive connected to? Which device name do you see for the controller when you look at it in Device Manager? Have you tried a motherboard bios update? Have you tried an INF/IDE driver update? The thing is, ImgBurn likes a disc that shows up as 'Formatted: Yes' in the info panel on the right. Until it does, I don't consider it to be formatted properly and ImgBurn will attempt to get it that way. Yes, you can get around that by changing the option in the settings but you should really fix the issue with your controller/drivers and not just bodge your way around it.

It does all those things. No limit on disc size... just comes down to whatever the drive says is available on the media you're using.

Done.

The disc burnt and verified ok, the rest is down to your drive making decent burns on that media and (I guess) the Wii liking them. Usual things apply... check for firmware updates (might improve burn quality), try other write speeds, try different discs. Failing that, get yourself a drive / media combo that you know works.

Looks like exactly what mmalves said. (Before anyone asks...ImgBurn works that way on purpose - so it can try and erase discs when the drive is messed up and reporting bogus info). User error.

Nero is probably just writing zeroes to the sectors. That's not the same thing as sending the proper erase/format command.

Discs are based around sectors - ie. there are a set number of them available on the disc to which you can write data. A sector is 2048 bytes (for DVDs, HD DVD, Blu-ray). So calculations are based around the idea of 'number of sectors * 2048 = size in bytes'.

You're missing off 3 significant digits if that's in byes. Even if it's in KB, as you can see a disc only has room for 4,595,776 KB, not 4,707,319 KB. You've got to compare like for like with these things and get the whole idea of dividing by 1000 out of your head - that's not how the computer world works.

Nowhere does it say 4706 mb. You don't divide by 1000 to go to the next unit, you use 1024. (Manufactuers use 1000 on the disc packaging though, that's why they list them as 4.7GB) So it's: 2,297,888 Sectors = 4706074624 Bytes = 4595776 KB = 4488.0625 MB = 4.38287353515625 GB

If you included the jacket_p folder in the source list or just added the root drive, it should have been there. So did you perhaps just add the video_ts folder?

Happy Birthday mate, hope you have a good one You share birthdays with my brother in law... just thought you'd like to know that

Please start your own thread berrybananaz. It makes life easier and you don't end up hijacking someone elses thread that way.

Read the FAQ, it explains what to do when you see that message (it involves using Process Explorer).

Treat yourself to a new drive.

Indeed, I'm not fussed about translations being 100% ready for when 2.4.0.0 is released. The idea was just that I gave them a head start. For the most part they can see how long the English strings are and how much space there is within the GUI. So if I've allowed room for 10 letters and theirs is 50, clearly we're going to run into problems

Your drive doesn't support those discs. See if you can find any firmware updates for it - that could fix it. Failing that, buy some better media. Taiyo Yuden or Verbatim.

copy + paste everything from the log copy + paste everything from the info panel on the right when you're in write mode (and that disc is in the drive).

When you create the bootimage using ImgBurn, it tells you all the important stuff in the log window (which should always be kept open). It's just down to you to feed that info back into the program.

Everything in write mode is based around the write queue. Even when you only have 1 image in it. The one you see on the main page is just the first one in the queue. Queue up a couple of images and then move one above the other - you'll notice the text on the front window then changes to match

mount the iso as a virtual drive using DAEMON Tools and then view that virtual drive just as you would do any normal one via explorer.