LIGHTNING UK!

Does using the ISO only mean it uses the same layerbreak position? Thats the only potential difference between using the MDS or using the ISO directly. It looks to me as if your drive just bombed out on burning the last bit of the 2nd layer. Isn't there a 8.29 version of your firmware out? or can you not crossflash to 1.29? You might have more luck with it.

Actually it's not *exactly* as is.... I remove stuff like DVD+RW, DVDRW etc from the string. So really it's just make + model number. Normally when I search for drives going by what people have posted I just use the model number. Perhaps I should switch to that within the program too. It's been so long since it was implemented I'd kinda just forgotten all about it - it's such a minor thing (although very useful!).

So really you need to tell rpc1.org to update their database. I pass the name of the drive, as taken from the drive.

I think it makes sense to always have the LB at the start of an angle block and not in the middle, and duplicate the chosen LB type (seamless etc) to all cells in that block. If you put it in the middle (and didn't duplicate), all cells around it would be marked seamless. Whilst that would be correct for cells before the one you've selected, angles after it (in same block) would be wrong because they WOULD be non seamless. I guess the same then goes for the first cell played by the route taken by angles before the LB cell. That first cell should also probably be marked non seamless. So yeah, that complicates things far beyond what it needs to! Much easier / better to just display the first cell of angle blocks and automatically configure all cells in that block with identical SPLIP flags. (That's what I've now done) Do you know of any good DVD's I could test this on?! I can't remember many (any!) with angles on them throughout the PGC like in fordman's example.

That's for burning an existing image. Read the other guides that specifically mention burning DVD Video discs in the title!

Going by my cd, all the files are uppercase. I've just done a bit more messing around and it seems you need to turn on the 'Don't Add ';1' Version Number To Files' options. If you don't, it can't find ntldr. EDIT: Yup, that's it. Built + booted + fully installed without any issues.

Blu, assuming you come back to read this, should I even be listing anything other than the cell of the 1st angle in a block for a potential LB position? If all cells in an angle block are supposed to be on the same layer / marked in the same way with the SPLIP flag, I would guess not.

Messing with splashscreen config is made more complex because it's displayed before cli parameters are parsed and the settings are loaded (be it from the registry or the CLI configured INI file) etc. So yeah, I think I'll just leave it as it is.

I just meant that if you had 'Test Mode' enabled, you were much more likely to get a successful burn (because the drive isn't actually writing to the media) - but of course then the disc would still be blank (and no verify would take place). A normal burn + verify (without 'Test Mode') should complete just fine but yours seems unable to reinitialise the disc once it has burnt to it. Not much I can do about that I'm afraid.

You don't need to mess with the profile stuff unless you're doing dvd double layer (dvd video?) type burning. You're not so don't worry about it. Yes, ISO9660 + Joliet is fine for your everyday file backups onto CD.

The blacklisting is not about swearing etc, it's security stuff that the server itself blocks in all websites / scripts / forums running on it. It's nothing to do with the forum software - nor is it under my control. Glad the CLI thing is sorted and I'm glad I didn't spend toooooo much time looking into a non existent problem

Ok, these are the problem files: W 15:52:38 ISO9660 File: 'W:\WIN51' -> 'WIN51.' W 15:52:38 ISO9660 File: 'W:\WIN51IP' -> 'WIN51IP.' W 15:52:38 ISO9660 File: 'W:\I386\CYCLAD-Z.IN_' -> 'CYCLAD_Z.IN_' W 15:52:38 ISO9660 File: 'W:\I386\CYCLOM-Y.IN_' -> 'CYCLOM_Y.IN_' W 15:52:38 ISO9660 File: 'W:\I386\DISK1' -> 'DISK1.' W 15:52:39 ISO9660 File: 'W:\I386\HEADSP~1.WM_' -> 'HEADSP_1.WM_' W 15:52:39 ISO9660 File: 'W:\I386\HOSTS' -> 'HOSTS.' W 15:52:39 ISO9660 File: 'W:\I386\MINIPL~1.WM_' -> 'MINIPL_1.WM_' W 15:52:40 ISO9660 File: 'W:\I386\NTLDR' -> 'NTLDR.' W 15:52:42 ISO9660 File: 'W:\I386\SV-262E1.PN_' -> 'SV_262E1.PN_' W 15:52:42 ISO9660 File: 'W:\I386\SV-262E3.PN_' -> 'SV_262E3.PN_' W 15:52:42 ISO9660 File: 'W:\I386\SV-262E4.PN_' -> 'SV_262E4.PN_' W 15:52:42 ISO9660 File: 'W:\I386\UTOPIA~1.WA_' -> 'UTOPIA_1.WA_' W 15:52:42 ISO9660 File: 'W:\I386\UTOPIA~2.WA_' -> 'UTOPIA_2.WA_' W 15:52:42 ISO9660 File: 'W:\I386\UTOPIA~3.WA_' -> 'UTOPIA_3.WA_' W 15:52:42 ISO9660 File: 'W:\I386\UTOPIA~4.WA_' -> 'UTOPIA_4.WA_' W 15:52:44 ISO9660 File: 'W:\CMPNENTS\TABLETPC\I386\PT-BRKBC.DL_' -> 'PT_BRKBC.DL_' W 15:52:44 ISO9660 File: 'W:\CMPNENTS\TABLETPC\I386\PT-PTKBC.DL_' -> 'PT_PTKBC.DL_' W 15:52:44 ISO9660 File: 'W:\CMPNENTS\TABLETPC\I386\ZH-CHSKB.DL_' -> 'ZH_CHSKB.DL_' W 15:52:44 ISO9660 File: 'W:\CMPNENTS\TABLETPC\I386\ZH-CHTKB.DL_' -> 'ZH_CHTKB.DL_' W 15:52:44 ISO9660 Directory: 'W:\I386\WIN9XMIG\ICM\SYMBOLS.PRI\' -> 'SYMBOLS_PRI' W 15:52:44 ISO9660 Directory: 'W:\I386\WIN9XMIG\IEMIG\SYMBOLS.PRI\' -> 'SYMBOLS_PRI' W 15:52:44 ISO9660 Directory: 'W:\I386\WIN9XMIG\PWS\SYMBOLS.PRI\' -> 'SYMBOLS_PRI' W 15:52:44 ISO9660 File: 'W:\I386\WIN9XMIG\ACROBAT\FILES\FILE1' -> 'FILE1.' W 15:52:44 ISO9660 File: 'W:\I386\WIN9XMIG\ACROBAT\FILES\FILE10' -> 'FILE10.' W 15:52:44 ISO9660 File: 'W:\I386\WIN9XMIG\ACROBAT\FILES\FILE11' -> 'FILE11.' W 15:52:44 ISO9660 File: 'W:\I386\WIN9XMIG\ACROBAT\FILES\FILE12' -> 'FILE12.' W 15:52:44 ISO9660 File: 'W:\I386\WIN9XMIG\ACROBAT\FILES\FILE13' -> 'FILE13.' W 15:52:44 ISO9660 File: 'W:\I386\WIN9XMIG\ACROBAT\FILES\FILE2' -> 'FILE2.' W 15:52:44 ISO9660 File: 'W:\I386\WIN9XMIG\ACROBAT\FILES\FILE3' -> 'FILE3.' W 15:52:44 ISO9660 File: 'W:\I386\WIN9XMIG\ACROBAT\FILES\FILE4' -> 'FILE4.' W 15:52:44 ISO9660 File: 'W:\I386\WIN9XMIG\ACROBAT\FILES\FILE5' -> 'FILE5.' W 15:52:44 ISO9660 File: 'W:\I386\WIN9XMIG\ACROBAT\FILES\FILE6' -> 'FILE6.' W 15:52:44 ISO9660 File: 'W:\I386\WIN9XMIG\ACROBAT\FILES\FILE7' -> 'FILE7.' W 15:52:44 ISO9660 File: 'W:\I386\WIN9XMIG\ACROBAT\FILES\FILE8' -> 'FILE8.' W 15:52:44 ISO9660 File: 'W:\I386\WIN9XMIG\ACROBAT\FILES\FILE9' -> 'FILE9.' A few problems here (Microsofts, not ImgBurn's): ISO9660 filesystems cannot have folders with extensions. ISO9660 filesystems cannot have files without extensions. ISO9660 filesystems cannot have folder / files with characters in them that are anything except A-Z, 0-9 and _ So MS broke all the rules when naming the folder/files for this disc. There's nothing really for me to 'fix' as technically I'm doing nothing wrong. I could put another checkbox under ISO9660 restrictions to allow folders with extensions and files without them, but that's about it - and like I say, I shouldn't have to! EDIT: BTW, you can make an image that compares perfectly (file data content wise) to the original by using the following options: General -> File System = ISO9660 Advanced -> Restrictions -> ISO9660 -> Level 2 - 31 Characters Advanced -> Restrictions -> ISO9660 -> Allow More Than 8 Directory Levels Advanced -> Restrictions -> ISO9660 -> Allow Full ASCII Character Set

Nah, the time means nothing. It's purely cosmetic. The sector number is what's important and so you'd just select cell 39 and be done with it. I will work on fixing the time calculation for PGC's with cells for different angles

Was that using 'test mode' by any chance? Test mode doesn't burn anything.

That log clearly shows it's finding 2 drives on your PC. If it says medium not present in the status bar it means either you don't have a disc in the drive or the drive just doesn't support the media you've put in it.

You should probably enable the logging option in the 'Build' settings so you can see exactly what's being changed to fit with ISO9660 restrictions. Indeed though, a '-' character is not permitted under normal ISO9660 specs. I wouldn't have though filename case would be a problem as Microsoft stuff doesn't normally care about case. I try it myself in a bit and report my findings. Fail in copying the file could just mean the drive cant read the disc.

so you're saying something as simple as: ImgBurn.exe /SETTINGS "C:\ImgBurnSettings.ini" is not working? If the program isn't passed anything in /SETTINGS, it will automatically try and load from ImgBurn.ini in the same folder as the exe. After that it reverts to the normal registry methods.

lol you went to the trouble of getting a screenshot of notepad?! Why not just copy + paste the text? Anyway... http://forum.rpc1.org/dl_firmware.php?download_id=1911 Go there and update your drives firmware. My guess is you should be on GA04 now. Set the program up to verify the burn (tick the 'Verify' box on the front screen). If that then works, you know you at least have all the data on the disc and your PC can read it. Try some Verbatim (MCC dye) or Taiyo Yuden discs, they work far better than anything else.

At the end of the day, it's a TV show! They can say what they like and most people will know what they mean (are trying to get across). 0.01% who know the technical ins and outs will know they're talking bollocks

Either the drive is just producing bad burns on that media or the drive isn't working properly as it just can't re-initialise the disc - hence the 'Unable to Recover TOC' message. A firmware update might help - if there is one available? Are you sure those are real TYG02 discs and not fakes?

Borland applications (which is what ImgBurn is) are a bit weird in the way they work. I guess the newer version of vern worked around this fact. So basically, it was for them to fix and not something I could do even if I wanted to. So long as it's ok with the current version (which it is) it's not really of any interest to me - sorry!

1.29 is the latest yeah? If you're running that and it's not working, either the discs are duff or the drive is.

You need a bin/cue type setup for 'complex' images and ImgBurn doesn't support cue files.

Ok, I've looked and I think it's more of a problem with using just /SETTINGS "Settings.ini", rather than /SETTINGS "C:\Program Files\ImgBurn\Settings.ini". If it doesn't find/open the settings ini file it will just use the default program values. Basically it didn't like there not being a path mentioned in that CLI argument.

The settings are supposed to be the same no matter if you read from the registry or an ini file. There's certainly nothing I'm doing on purpose to stop log window ones from working. It's especially weird if the main window can be positioned ok but the log window not. I will look into it.