Chris123

I tried dumping three mixed mode CDs and one audio CD, and while the audio CD's ISRCs were correct and caused no issues, all three CUEs of the mixed mode CDs contained an invalid ISRC that starts with TC and ends with a question mark (it was the same ISRC for all tracks), which prevented the images from mounting in Alcohol 52%. If I change the ? to a digit, or remove the ISRC lines entirely, the images can be mounted correctly. So this seems to be an issue with mixed mode CDs (at least), and while it might be the drive's fault, the solution can be to not include ISRC in CUE files if they contain an illegal character such as a question mark.

I've updated the firmware to the older 1.03 from 2014 (it turns out there are two 1.03 updates on the LG website - the newer one you've mention above from 2018 (N1.03), and an older one from 2014 (1.03-A0) which I didn't notice before), and it didn't solve the problem. You wrote above that LG drives aren't good readers, so what drives ARE recommended as good readers? I'm considering creating images of a lot of my old CDs, but there's no point in such a project if my drive isn't a good reader (I'm already scared that a lot of those old CDs will anyway be problematic reading-wise, so a good reader is crucial). Side-note - UltraHD Blu-Ray is a new format from 2015, which is not compatible with older Blu-Ray drives, so I don't think it's possible for my drive to read it at all. The closest model that can read these discs is WH16NS40, but my drive is WH14NS40.

Nah, I'm done with it. Nice story though!

Indeed IsoBuster lets me view the tracks, and it appears that there are 3 empty data track in addition to the "real" one. When using IsoBuster to search for missing files and folders in the redundant tracks, it just finds more instances of the same files as on track 1. So the answer is most likely disc deterioration, which brings me back to what I was wondering about to begin with - how can disc deterioration trigger the appearance of 3 additional tracks, instead of just the usual read errors? I guess it'll remain a mystery

What I'd really like to know is, assuming there are 4 tracks on the CD, how can I check what's on each track?

Corruptions I understand, but causing a detection of non-existing tracks is new to me I remember, but I don't have to, since the data on the CD is still readable and I copied most of it to my harddrive and opened some files, which worked fine. It's just some files that I burned on a CD to clear some HD space back then. AFAIK, a single-session data CD with more than one track means that the first track contains data, and the other tracks are redbook audio, and I don't think that's the case here. Daemon Tools can indeed create disc images, in several formats. I've tried using the ISO format, but it failed, and the error message said it's because it's a multisession disc, even though Daemon Tools itself detected only a single session! So, I tried creating MDX and MDF+MDS images and they both worked, and I was able to mount them with Daemon Tools just fine. And this is despite the fact that Daemon Tools also detected four tracks. I then tried to create an image from the mounted image using ImgBurn, but it never got past the analyzing tracks process so I closed it...

LG actually recently released a firmware update for a 6 year old drive, wow... And yes, the disc is 18 years old, but I don't understand how that would cause a drive to falsely detect four tracks... When I burned this CD, I don't think that I knew how to burn a multi-track CD, but perhaps I somehow did it by mistake... how can I verify whether it has 4 tracks or not? And if it does have 4 tracks, how can I check what's on each track? But the most important part is, if the CD does contain 4 tracks, why would DAEMON Tools fail to load the image that ImgBurn creates?

Have you ever encountered a situation where a drive reports several tracks for a single-track data CD? The CD was burned long ago but the data is readable, I was able to manually copy the data that I needed from the CD, which was about 2/3 of all data. It did take about 30 minutes though. Here it is: HL-DT-ST BD-RE WH14NS40 1.00 (SATA) Current Profile: CD-ROM Disc Information: Status: Complete State of Last Session: Complete Erasable: No Sessions: 1 Sectors: 298,133 Size: 610,576,384 bytes Time: 66:17:08 (MM:SS:FF) Supported Read Speeds: 4x, 8x, 10x, 16x, 24x, 32x, 40x, 48x TOC Information: Session 1... (LBA: 0 / 00:02:00) -> Track 01 (Mode 2, Form 1, LBA: 0 / 00:02:00) -> Track 02 (Mode 2, Form 1, LBA: 512 / 00:08:62) -> Track 03 (Mode 2, Form 1, LBA: 297216 / 66:04:66) -> Track 04 (Mode 2, Form 1, LBA: 297826 / 66:13:01) -> LeadOut (LBA: 298135 / 66:17:10) Track Information: Session 1... -> Track 01 (LTSA: 0, LTS: 360, LRA: 0) -> Track 02 (LTSA: 512, LTS: 296552, LRA: 0) -> Track 03 (LTSA: 297216, LTS: 458, LRA: 0) -> Track 04 (LTSA: 297826, LTS: 307, LRA: 0) ATIP Information: Disc ID: 97m32s00f Manufacturer: TDK Corp. Start Time of LeadIn: 97m32s00f Last Possible Start Time of LeadOut: 74m15s00f

Hi, I've tried to create an image of a CD that was burned more than 18 years ago, and ImgBurn detected four tracks on the CD for some reason, even though there doesn't seem to be a reason for this CD to have more than one data track. Although ImgBurn didn't report any read errors when creating the image, the process took a long time (about half an hour), and DAEMON Tools failed to mount it. Is it possible that ImgBurn detected four tracks on a single-track data CD? Is there a way to see what's in each track? Thanks

I got the drive, here is a screenshot of its capabilities: I knew it won't support HD DVD at all, but I was surprised to find out it doesn't support DVD+RW DL... not that I ever even seen on of those. It can read a CD-R90 just fine. Regarding CD-I, I don't know, I think a simulator is needed or something.

Fair enough. Just seemed like a fun and unique feature to me

Thanks for replying spinningwheel. I understand that the drive is not related to ImgBurn, but I was basically making a feature suggestion - detect more legacy formats in Device Capabilities (other than CD-Text which is already detected)... And I tried that support page, it forces you to choose a device model, and, even though I reached it through the specs page of the drive, I couldn't find the specific model in the options given in the form, so I couldn't file a request...

Hi, I'm considering buying a new burner, LG WH14NS40, and I'd like to know what "oldschool" CD formats it supports, in addition to the basics (I was actually going to post this in the Drives forum but it's locked). The most detailed official specs I could find are here, but many old formats\features are omitted. Specifically, I'm referring to: 1. Mixed-Mode CD (data+audio) read/write 2. Multisession mode 2 CD read/write 3. Overburn CDs (CD-R90, CD-R99, etc.) read/write 4. CD-I read (I actually have a movie in this format ) 5. CD-ROM XA-ready (not sure what this is) 6. Photo-CD (Single & Multi-session) (not sure what this is) 7. CD-Extra (not sure what this is) 8. CD-Text read/write 9. SVCD read (not sure about write) 10. SecurDisc (not sure what this is, but my old LG DVD burner has it) (note - the formats I'm not familiar with were taken from a spec of an older LG drive, seen here) I was thinking of using ImgBurn's Device Capabilities screen (on a PC with this drive installed) to find out what is supported and what is not, but except for CD-Text, Device Capabilities doesn't detect any of these formats... to me, Mixed-Mode read\write and multisession read are very important, and overburn read is also somewhat important... So my questions are: 1. Is there a chance this drive supports these formats despite not being advertised? Especially the ones important to me? 2. If I have access to a computer that has this drive installed, is there some way to verify whether the drive supports these features (without individually testing everything)? 3. The main reason I posted here - can these formats be detected in Device Capabilities of future versions of ImgBurn? 4. Is there a chance this drive will read HD DVD despite not being advertised? 5. Regarding BD-R\RE versions - according to Wikipedia, the last versions of BD-R\RE (3 and 4 respectively) were defined in June 2010 - how do I know this drive fully supports the latest versions (plus backwards compatibility with older versions)? This perhaps should also be detected by future Device Capabilities screen... Thanks!

Hi, I also have a question regarding the necessity of MDS files - I've created an ISO image out of an original game disc. The game comes on a single-layer pressed (I assume) DVD with around 3GB of data. It seems completely unprotected. After extracting the ISO image, an MDS file appeared, which usually doesn't appear when creating ISO images of such DVDs (single-layer, no protection, data-only). The File Sys on this DVD is ISO9660, UDF (1.02). Note: If I create an image from the mounted ISO, the MDS file is created regardless of whether I use the MDS for mounting or the ISO file directly. Also, the ISO\MDS pair in both instances is completely identical to each other and to the original pair created from the physical disc (I used MD5 for comparison).

I also saw this (ImgBurn as the Imp ID) in an original game DVD that I bought, and I actually thought I bought a fake! How is it possible that this Imp ID will be on a pressed original DVD?

Didn't know this fact until right now. Thanks for the info. That's what I needed to know. So I guess if the ISO image that ImgBurn created didn't completely preserve the layout of my disc, nothing will. I still don't know what property Win98 'attached' to the long-named folders that made them accessible under DOS, but I hope it's something that can be transferred to an image. Yep, that's me. Too old to change that. It has its benefits though.

Thanks for replying. Odd, I'm sure I created BIN\CUE images out of MODE1 CDs. I think I was using CDRWIN. Yes, I know that the image formats are not related to file name lengths, that was an off-topic question. My main concern is whether the ISO image is accurate enough to preserve whatever made the CD work properly on DOS, and if it will transfer to a CD when I reburn the image.

Hi, Many years ago I made a compilation of DOS games and burned it on a CD-ROM which was designed to work on an actual DOS machine. The only Windows-y thing about the CD was long directory names. For some reason, this caused a problem, and the long-named directories were inaccessible under DOS. I eventually found out that the problem was that I built the directories of the compilation under WinXP. So, I rebuilt the compilation under Win98, changed some Nero settings to make the CD more DOS compatible, burned another copy, and this time it worked fine. Note that MD5-wise, the data was identical on both discs. Luckily, the disc hasn't deteriorated yet, so I wanted to make an image out of it for safe keeping, until I build a DOS machine again. My question is this - I used ImgBurn to create the image, and I was surprised to find that the image format that ImgBurn chose for this CD is ISO rather than BIN/CUE. The data was preserved perfectly, of course, but that's irrelevant to whether this image will properly work on a DOS machine once reburned onto a disc - is an ISO image accurate enough for preserving whatever enabled this disc to work on a DOS machine back in the day? Wouldn't a binary image be the correct choice? Thanks P.S. Off-topic - will ImgBurn notify if file\folder names are getting truncated during burning? And what about file\folder name change due to unicode characters?

Thanks Cynthia. But I did see some Close\finalize options which suggested that this can be done manually as opposed to automatically, so I assume they're only meant for burns that failed in the middle and discs with open sessions that were authored in a program that does support multi-session? Didn't see a specific explanation in your guide.

Ok, I guess it's fine for a data DVD... By the way, is there a way to leave a session open in ImgBurn, or you have to always close (or finalize) the disc?

Thanks for the info. I'll go ahead and use it then, I think it'll be fine (even though I can't test MacOS X right now). I read about the partition types here, seems that each of the three types was meant for a different type of burning media...

That's what I assumed. However, I don't understand why a "normal" English character would take up 2 bytes even when unicode is enabled, it seems illogical. I guess what I meant was to ask if this is a standard UDF feature, and to verify if it lowers the compatibility of the DVD or not. I didn't see the "use with care" warning in the ImgBurn guide (that Level X Joliet has, for example). And, also, since ImgBurn doesn't have the partition type selection, what type does it use?

Thanks, this method worked, the very long file names weren't truncated. I'm now really happy that I decided not to use unicode characters in my file names, or else no solution would have been available. I used UDF 1.02 by the way since I assume it'll be supported on more systems, cause I would like Mac OS X machines to be able to read it. Can you explain why it worked? My assumption is that when allowing unicode, some bytes are reserved for the support of the unicode characters, but why would it truncate standard English-only file names? Also, is that a standard feature? I looked in Nero that I have installed (Nero 7), and no such option exists there. They do have a selection for "UDF partition type", which ImgBurn lacks, but I don't know what it's used for.

Thanks. Read about this extension a little, and I have a feeling it too will transform the semicolons to underscores. I think I simply won't use semicolons then, and burn using ISO9660:1999, as the length of the file names is more important to me. Problem is, I've just found out that you can't search for a semicolon in a file's name using Windows' search, so I'll have to locate them manually :S Damn... I obviously used Google before posting, but for some reason the only result I got was this. Now Google has fixed their bug, so I got the info I needed

I'm trying to burn a data DVD that contains some files with very long names (which are nested within long-named folders and subfolders to boot), and some files that contain a semicolon ( ; ) in their names as well. ISO9660:1999 works fine for the long names, but turns the semicolon into an underscore. UDF allows the semicolon, but truncates the long names. Combining the two had the same effect as using UDF alone. Is there some way to burn such a compilation as it appears on the harddrive, or must I change the file names? Thanks! By the way, upon loading, the ImgBurn log gives this error: "Duplex Secure's SPTD driver can have a detrimental effect on drive performance." Not sure what it means, searched for it but got nothing.