LIGHTNING UK!

It doesn't need to be in multiple bin files... and that isn't how ImgBurn would have ripped it, you'd have still ended up with a single BIN / CUE file combo. Your disc is just unreadable, that's all.

The program asks the drive to return data for a range of sectors. If it returns an error, it then asks for 1 at a time. That then narrows down the problem sector. You can have it ignore the bad ones by clicking continue or whatever, where it’ll then move on to the next one and the bad one is zero filled. Once you have your image with as much of the data as you can get,, you can start looking at more aggressive disc cleaning techniques. I think it was Skip Dr. that made a disc resurfacing tool. Such tools were popular with the rental companies.

I was thinking more along the lines of a friend or family member that might have a computer. I wouldn't go spending money on it, as chances are, it still won't work. It's probably easier to just find an existing image online somewhere and use that.

I looked, but it wasn't really long enough. What I could see is that it was going ok until it tried to get the subchannel info for sector 107657, at which point your drive must have been struggling to read the disc and started returning info for totally different sectors. It was also taking 5 or so seconds to return said info. There was probably something else going on behind the scenes, but can't see that without an additional I/O Debug mode log. Not to worry now though... you know the disc is essentially unreadable. It might be worth trying it in another drive if you have access to one. Some are better readers than others.

Try some other discs, your drive doesn’t appear to like those.

This will be because your drive is returning some invalid subchannel data and it's causing a loop. If you take a look at post 5 onwards in this thread, you'll see the logs that can be helpful in me trying to diagnose your specific issue.

Oops, my bad! That pinned thread was on the old forum (from the DVD Decrypter days). I'm afraid it isn't available here.

Do you still see it changing size / going into that back box in the top left corner? Disable the screensaver.

I will just point out that the suggestions you tried prior to posting are all nonsense. Don’t believe the Internet. Reset to default settings and continue with dbminters advise. There’s a pinned thread for semaphore timeout issues.

That's where my initial link would come in handy. From what I could make out, it's just a reg key that holds the config of your monitor(s). You clear it out, get your physical monitor back in there, turn it off and leave it so the emulated one gets created, turn it back on and then copy over the physical one's settings to the emulated one. That way, when the emulated one kicks in, it's running at the same res and nothing gets moved around.

I have a question for you... as your email address seems to link back to the Foxburner SDK, can I ask why you are on here asking me questions about ImgBurn? Fair enough if you're actually using ImgBurn, but if you're trying to enhance your own product, you could at least be upfront about it.

Yes, this would be a feature request. Normally, you'd want to keep as close to the original name as possible - as permitted by the file system. Truncating the name when there's no real reason to just hadn't occurred to me - nor has it come up as a request from anyone else... until now

There's nothing to say you have to maximise on the directory name length. You've a directory name length limit, a file name length limit and an overall path limit. All other limits are still in place if you modify the 'Allow more than 255 characters in path' option. That option simply tells ImgBurn not to check for paths that might exceed that limit. Rather than mess around with ISO9660 options, why not just use a modern file system like UDF? Are you absolutely limited to using ISO9660 for something?

https://www.ecma-international.org/wp-content/uploads/ECMA-119_2nd_edition_december_1987.pdf 6.8.2.1 states 255 is the limit.

All drives behave differently. Standalones are typically better at skipping problem areas, but the PS3 is designed for playing games from pressed discs, so it's more like a standard optical drive (PC drive or whatever) in that respect.