LIGHTNING UK!

You can't. The media we buy is OTP and you cannot change that.

Yep it's in there for the next release (v2.2.0.0). Out of interest, why aren't you just using hd2iso.exe ? It comes with XPe and lives in some utilities folder somewhere.

I was just messing But it is worth remembering that I/O errors are almost never anything to do with the application, they're just where the drive errors out due to a drive/firmware/media issue. If it's an app issue, THEN I may require the F8 debug log.

That's not the final v2.2, just a beta before it.

So now the log correctly shows Windows XP yeah?

So in that log, you just burnt the file on it's own via build mode yeah? Rename that file to something else and then burn it again (on a rewritable of course). Does it verify ok then? What if you build an ISO from that file and mount in DAEMON Tools. Can you then verify the mounted drive (uncheck the 'verify against image file' box) ? It could either be the content of the file that's the problem, the name of it or some combination of the two. If everything you've said about your testing is true, it certainly looks like something fishy is going on... it's almost 'rootkit' like. There's no way I know of to burn anything in mode 1 using tao/sao/dao write modes that then cannot be read back - so it's like some other driver (hence the rootkit part) is reading some signature in the file and returning the seek error.

Software is only as good as the hardware it's running on. For all we know you've ordered the worst burner in the world and are running the oldest firmware....and that really isn't my problem, that's yours. If the burn fails for any reason, you only have the hardware to blame. I/O Errors are not ImgBurn errors, they're drive errors. So if you're getting an I/O Error with the message 'Write Error' (which you say you are), I would have to say you've either got a duff batch of Verbatims (fake ones maybe) or your drive just can't even burn to the best DL media they make.

Yeah it's toast.

You'd think the warning message that pops up saying it won't fit would give people a bit of a clue too wouldn't you?!

As far as I'm concerned, the limit for a file in the ISO9660 / Joliet file systems is 4GB. That's why ImgBurn supports files of that size. To be honest, I've no idea why Nero limits it to 2GB when the specifications for the filesystem mention nothing about a 2GB limit. So basically, ignore Nero and just go along with what ImgBurn says!

Yes, if you're in 'Build' mode instead of 'Write' mode. For burning images you want to be in 'Write' mode.

...and that wasn't the only broken link Thanks, all fixed now.

There's just no beating Burnout Revenge!

Right click the ImgBurn.exe file and click on 'Properties'. Then click the 'Compatibility' tab. Uncheck the 'run this program in compatibility mode for' option. God knows how/why you ever did that in the first place!

If you have an ISO file then it's down to the content of that ISO as to whether or not it's bootable. It's nothing to do with ImgBurn. Burning a bootable ISO is no different to burning a normal ISO. If you're BUILDING an ISO in ImgBurn (from random files on your hdd), THEN you have do check a couple of boxes here and there to make the resulting ISO bootable. As for the 'Write Mode' stuff, you should always leave it on auto. If for some reason it doesn't detect the media correctly, then you should manually force it. The options being CD, DVD, HD DVD and BD (BluRay).

For whatever reason, it doesn't appear to like them now. Try some with a different dye.

Burrrn is good freeware for audio. http://www.burrrn.net/?page_id=4

Yes a chapter can span multiple cells but maybe there's some reason for VobBlanker doing what it did... I dunno. Someone who's done it before might be able to help you a bit more. It might be worth checking out the Doom9 forums too.

About the only thing I remember from CloneCD is that is reads / writes 16 sectors at a time where I default to 32 if the driver says it supports it. Try changing the 'I/O Transfer Length' option in ImgBurn to 'Manual' and '32K'. Other than that (especially if you're using ElbyCDIO as the I/O Interface) there's no reason for it to just stop like that. As I've proved, this is not a general problem with the program because on my machine, that OS / drive / media combo works fine. If you really wanted to know where it was dying you'd need a bus sniffing tool. I believe you can find a free one on the net for capturing SPTI calls.

Ah hhaaaa! Sussed it! My XPe image works properly now from the partition I copied it to. After running 'etprep -all', using ImgBurn to create a boot image of that partition and finally a bootable ISO, I now have XPe on CD and it boots fine No 3rd party tools involved in the build at all

Google is your friend, use it There are a million and one tools you can use for that.

I've been messing around with bootable hdd emulation stuff for hours now and I've added 'Local Disks' to the drop down box where you can select what you want to make the bootable image from. It'll create a file containing a MBR (with 1 partition, marked 'active') and then the given hard disk partition - so really the image looks like a proper physical disc. This image CAN be used with the normal hdd emulation option in ImgBurn, so it saves you messing around with WinImage etc - which I could never get to work anyway! All you have to do is ensure the partition you're reading is small enough to fit on your destination media. i.e. I made a FAT32 partition of 625MB - as told to do in the xp embedded docs I read. So the ImgBurn bit is now working ok but I can't get xp embedded to boot up! Too much pissing around with whatever the hell EWF is! I just get a BSOD with stop error 0x0000007B Once I can get it working on (copied over to) my 2nd pc I'll go through the El Tortio build steps properly. I just don't want shut this PC down and boot into my test XPe image!

The only issue here is that you're getting a 'Write Error' from your drive on the discs you're using. Only go by the FIRST error you see, not the ones that come up when you Retry (or the program retries automattically).

The drive is overburning that media to 8x. Whilst it *thinks* that's ok, I would advise you to stick with 2.4x - at least until you've got it burning full stop.

lol that doesn't make a whole lot of sense to me db! If it's a bootable disc image, you just burn it?! If you're talking about extracting the bootable bit, that's not easy if they're using custom (none) or hdd emulation.