LIGHTNING UK!

Yes, so long as you actually select the MDS file in the first place

if you add a single folder and turn off the prompt, it auto answers 'yes' to the box that would otherwise have come up. If you add more than one folder (folder or file), it's NOT the root and so you're not given the prompt.

You're using UDF for starters, and that's the one Explorer would show to the user, not ISO9660. If you need to test ISO9660 restrictions, you need to make sure ISO9660 is the only FS in the image. Take a look at the ISO in ISOBuster or something. See if the image looks ok in that. I would hope we did enough testing to at least see past errors like this! I frequently made ISO's from all my IBG graphs and they all have long names. I didn't notice any problem myself but maybe I was looking beyond the obvious stuff. Go into the options and turn on the logging of non compliant file/folder names. You should then some extra stuff in the log. and just one final thing...when you say explorer couldn't read it, what was the exact error message it was giving you? 'corrupt or unsupported file system' ? Something else?

Did you up the buffer to 100mb for ImgBurn too? Maybe a bigger buffer would help in these situation - I notice DVDShrink was using almost 100mb in the first screenshot Oh and regarding the folder deletion stuff, that's how DVD Dec always used to work and nobody said anything then! Since the release of ImgBurn, 2 people have pointed it out (it scared them!) so I've made it prompt for deleting empty folders too - it wouldn't delete them if they weren't empty.

It does a bit by bit comparison against the original image file. So at that point in time, the drive can read back exactly what has been written and the two match 100%. A PI/PO scan will then pretty much tell you how difficult is was for the drive to return that 'correct' (or if you're unlucky 'incorrect') data.

ok cool, had to ask, sorry

ImgBurn's is the latest... the others may need to 'mirror' again!

No, it was designed to build an image from an existing structure on your hdd. That's how I like to work and that's why I designed it like that

When doing these speed tests, you are making sure fragmentation isn't a factor yeah? The more random accessing the hdd has to do, the slower the transfer rate will be. I'd be amazed if drivers really made THAT much difference. After all, the slowest part (by far) is the hdd itself.

There's no room to have it on the main build screen, that's why it's not there Same goes for the other bits you mentioned really. To change one screen would mean to change them all - I like having things in the same layout / place in each 'mode'.

lol they've always had splashscreens. This one just looks pretty. It's not like in other programs though, it's ONLY on the screen whilst doing other stuff in the background. When that's done, it's removed - same as how it's always worked, right back to dvd dec days.

Yeah so it would work once (when empty) and never again for the duration of the time the program is open. That kinda thing would be a nightmare and that's why I chose not to do it. I even added the 'Volume Label: [Not Configured]' text to the image details message box that pops up so people wouldn't forget to set it. That dialog box is a constant reminder! Not my fault if you get click happy

No, I won't, sorry. At best, use the CLI stuff. use /source and point it to the video_ts folder or something.

It'll probably be the one with the highest rating! At the very least it would have SPLIP set to 'false'. The layerbreak is a physical thing on the media, you can't just look at IFO's and know for certain any one particular cell is THE one the authoring program intended to be use for the layerbreak. That's why you get the box where you can then choose from a list. So when you see that box, select the correct one in the list and click 'ok'.

According to your initial screenshot, you were always on ASPI. There is no reason to ever change from that, SPTI undergoes ALL the testing, I never even look at the others anymore now really. Besides, you're using Nero ASPI which is just an SPTI wrapper anyway - and hence slower! Do you by any chance have autoinsert disabled or something? It sounds to me as if your OS just isn't even attempting to look at the drive.

DVDShrink may use different buffering internally, and also on the 'ReadFile' API too. I don't tell the 'ReadFile' API to NOT use buffering, perhaps that's slowing things down for you when you use the same hdd for reading / writing. If you tell that API to not use buffering you have to read certain amount of data at a time. Because ImgBurn has to be able to read all sort/sizes of files, that makes things more complicated - hence I didn't bother with it.

I have to at least default the options to be inline with specs - even if the options are very annoying! lol Glads you're sorted now though.

Advanced -> Restrictions tab on the main gui.

I don't really. I take copies as I go along and my development environment has a 'history' feature built into it.

As imgburn locks the drive during a burn, the OS doesn't always see the changes. Eject the disc, close imgburn then put the disc back in. Explorer should then try and read the disc again properly.

I think denise means within the image itself rather than the files on the hdd. Files in the image are just made to look like 'normal' files even if they were readonly / system / hidden on the hdd.

Sorry but that isn't really appropriate in a tool that accepts multiple folders / files.

Easy one this, you can't.... or rather it doesn't.

I'm actually quite offended by this thread! Of course it doesn't contain spyware/malware....what kind of arsehole do you think I am?!

Yeah basically, your machine couldn't cope with running 2 versions off the same hdd or whatever (maybe 2 dvd drives on the same channel or a hddd + dvd on the same channel?). As such, the buffers weren't keeping full and so buffer recovery kicked in to stop multiple buffer underruns.