LIGHTNING UK!

The day will come and words/hats will be eaten. I messed around with the code basically as soon as I read the 'bug' report, but it then became 12:30AM and I had to call it night. I'm not currently in a position to be able to test anything (I need such an image for a start), but once I have, the change will make it onto the changelog ready for the next release.

Are you using some sort of autoloader for doing all those discs? If not, just close the program occasionally and take a copy of the log file (give it a unique name each time). There's nothing you can do to change the log cut off point as it's all hardcoded.

One includes ISO9660 and Joliet file systems, the other doesn't.

Sometime they were authored/pressed in a way that can't be reproduced by a writer unless RAW mode is used - and ImgBurn doesn't do RAW. The drives do a bit of a 'sanity check' on what's being burnt and like to correct things. If the disc works, you probably don't need to worry about the issues if they're only in the sync/header areas.

If you include UDF, the stuff in ISO9660 will never get seen (by anything that supports UDF) - so there's almost no point in changing the ISO9660 options unless it's the only file system you're including on the disc. Well done for getting it semi working with turning off UDF unicode support.

Post the log please. If this is a repeat of your previous topic, the answers will probably still be the same!

It's not something you can do as an end user.

This thread/post may help... Basically, you need to be using the correct EFI boot file and set 'sector to load' to 1.

You probably need to build it as a UEFI bootable disc, not 80x86 - or make sure your vm supports the older style bios bootable discs (in vm options -> advanced -> firmware type = 'bios'). I'm afraid I've never updated the guides to cover that.

ImgBurn always instructs the drive to use the value you specify. It's down to the drive to actually support the speed and do as it's told.

Why would you want to join up to the forum and resurrect someone else's 14 year old topic? If you have a problem with the way the software is behaving for you, you should make a new thread... like you have done. Since 2008, Advanced input mode has been added. You have more control over the disc layout (via the 'disc layout editor' window), so just use that instead of trying to work around things with subst.

I still don’t see where IngBurn fits into the equation. What do you think you mean by ‘download’ ? Do you just want to install the games so you can play them? Didn’t the disc come with instructions?

No problem, I can add support for that. There are other fields that are meant to be set to a specific value when burning CD-I discs, and they wouldn't be set correctly even when you edit the CUE to say MODE2. A proper fix will enable the software to set the 'session format' correctly when setting the write parameters.

I’m not so sure this is anything to do with ImgBurn. Are you trying to copy a disc?

Mount the ISO in a virtual drive program (or Explorer) and then point ImgBurn's Build mode at that virtual drive. It'll then be able to shift things around so it complies with DVD Video specs.

And nothing written in the log window when you add the folder? Can’t do much more than check the share and ntfs permissions on the drive itself. Just double check the build mode options too and make sure you don’t have ‘archive files/folders only’ enabled.

Add the problem folder to the ‘disc layout editor’ (when in Advanced Input mode). Does it list all of the files in the folder correctly? Does anything get written to the Log window? Could just be a permissions problem and it doesn’t have access to the content.

Your drive probably doesn’t support those discs. A firmware update may fix that, but you’d need a patched flasher or whatever due to it being an oem drive. (From a Gateway pc possibly?)

Yes. It would then just be testing the disc is readable.

Yes, it would automatically verify against what has been written - and that applies to both Write mode and Build mode.

If it's a DVD-R, use Read mode to make an image of it and then burn it via Write mode. Is the source disc you're looking at actually a DVD Video disc? As ImgBurn only burn as-is, if you feed it an MP4 file, you'll end up with an MP4 file on the disc. You can probably skip Handbrake entirely.

I don’t know that either. If the model is in the ‘supported’ list I mentioned in my previous reply, it should work. If it isn’t, it won’t. If in doubt, ask Primera.

I've no idea. Going by the guide, mine was/is a Disc Publisher SE. You can get a newer PTRobot from here - https://www.primera.com/developersupport/ Supports Bravo SE,SE-3,II,Pro,Xi,XR,XRP,4100/4200 Series

Try the other filers listed at the bottom of the guide here: https://forum.imgburn.com/index.php?/topic/5555-How-to-write-an-Audio-CD-from-music-files-using-ImgBurn

I haven't done this stuff in like 10+ years, so please don't expect me to remember any of it! Look at an IFO in IfoEdit and you'll see how DVD Video files are broken down. Perhaps you recall the term PGC ? A PGC is a collection of Cells. They're the Cells I'm talking about. It all comes down to the DVD Video specs. A layer break is meant to be put in a certain position (a cell change) and that's the reason for the coloured starts on the layer break selection screen. The more boxes the position ticks, the higher up the star rating chart it goes. Pressed discs will have been designed and authored with a layer break position in mind. Unless of course they're 'seamless' ones and you're relying on the player working with a disc that doesn't really comply with the specs. They too may have some padding within the file system (invisible to you) so that a cell change falls in the correct place for burning to disc. Don't forget that pressed discs can be OTP or PTP. For burning, we only have the option of OTP. Different rules apply for each format in terms of layer sizes.