LIGHTNING UK!

Define 'multiple files' ? Multiple image files? - No, an image is a 1:1 of what the disc should look like. So you burn 1 image on 1 disc. Images are written in Write mode. Multiple documents / pictures / mp3's etc? Yes, use 'Build' mode. Add the files to the 'Source' box and then burn.

At least 'dvd' is an extension that's likely to just be for DVD images, 'ini' is a little too generic!

You need to get the machine into the state where it's doing a BSOD, then just examine the latest mini dump from the minidumps folder (i.e. C:\Windows\MiniDump). You might also have a C:\Windows\Memory.dmp file. You want the windows debugging tools from Microsoft for examining the dump file and you examine it via the (obvious) 'open crash dump' option on the 'File' menu.

Rewritable discs are never as good / reliable as write once ones. Get yourself some Verbatim or Taiyo Yuden DVD+R / DVD-R and you should be ok.

Yeah, the LB is only an issue for DVD Video discs and even then you can get around it by marking it as 'seamless'. If you want to find out which file spans the LB you need to look at the L0 data zone capacity value in the info panel on the right and then look at the filesystem structure of the burnt disc (or ISO image) in something like IsoBuster and compare the LBA numbers.

Are you sure the correct 'destination' drive is selected? If the drive isn't reporting that you've got media in it then that's not ImgBurn's problem I'm afraid. You'll need to update the drive's firmware so it supports the media you're using properly or get some different (better) media that it does support.

ImgBurn creates the file of the required size first and then fills it with the data - that way you cut down on fragmentation. So basically, if your machine crashes/reboots then the images will be useless beyond the point it got up to. You might like to examine the (mini)dump file from when the pc rebooted, it should contain info as to which driver bombed out.

With buffering etc the physical layerbreak on the disc shouldn't be a problem when playing avi files.

You have to run it with those switches every time if you want it to use them.

This entire thread is a bit

Post a log of you burning (with Verify enabled) a disc you then wish to play on the PS2. Does your PS2 actually display a message when you insert one of the burnt discs?

Ok, I'll look into it in a couple of days when I return from my holiday

ImgBurn would burn such a file 'as-is', so any problem with playback comes from your player. For help with other software, please visit their own forums.

Extract the files from that image and build it again with ImgBurn via Build mode.

I've run all the images / udf versions ImgBurn can create through that tool before and they're fine. It doesn't change the FSD File Set Identifier text because it's not a 'volume identifier' - the name kinda gives that away.

Sorry, I have no interest in supporting that technology.

Does it actually burn + verify ok? Post the full log please.

Are you using 2.4.2.0?

This is nothing to do with UDF or windows, it'll be because your drive has made a duff burn on the disc and now the drive can't read it back.

You have to tell it not to use runtimes or dynamic links.

yup, c++ builder and my two hands.

Don't enable debug mode until you're at the point (well, just before) where you know it's going to freeze. Keep an eye on the status bar in the main program too and tell us what it says when it gets stuck.

If ImgBurn finds the LB position in Write mode then you can just burn it without any messing around, it'll be fine.

If you can't see the file in the browse window then you've probably got the file extension set to something ImgBurn doesn't support. Try changing the 'file types' dropdown box to show all files (*.*) If that doesn't work, drag and drop the iso file onto the 'Source' groupbox when you're in write mode.

It probably means you've got a picky (old) drive.