LIGHTNING UK!

Well... I like the way it would tell you early on if the disc can be written to in full without error and I'd kinda always expect a full erase/format to actually erase what's on the disc and leave it looking empty/blank (zero filled). I guess it's just personal preference really.

It burnt / verified ok and the TV system is shown as NTSC which would be right for the US so in theory everything should work just fine in a player that can actually read the disc. Perhaps try again with some decent Verbatim / Taiyo Yuden discs. Obviously I have no way of knowing if the conversion from AVCHD to DVD Video format worked ok or which program you used for the job. If you have a home made disc that does play on those other players, copy it onto a new blank (like the one you just used) and see if the players can still play it. At least then you'll know if it's the source files that are the problem or the discs themselves.

Controllers and modes aren't something the program really knows or cares about. The API commands provided by Windows shield all that stuff from the software and it's the OS drivers that are supposed to do all the hard work. I can't comment on the activity led but a general freeze of the PC is probably where an I/O command isn't being processed nicely (at all). It should always get a success/failure message, never cause a system freeze - again, that's down to the drivers.

That's purely a cosmetic design decision within the program. If the cdtext info is listed, it's present on the disc.

When I implemented the BD-RE formatting code, I noticed that formatting the disc didn't (or doesn't - things may have changed in firmware) actually seem to wipe / zero it, hence why the program does it. I'm fairly sure that unchecking the 'prefer properly formatted discs' option does away with the zeroing phase.

2.5.7.0 -> 2.5.8.0 Language_File_2.5.8.0_Differences_Report.zip Language_File_2.5.8.0_Differences_UnifiedDiff.zip

Try bringing up the 'Family Tree' info on the drive - right click the destination drive box and you'll see it on the context menu. It may mention which chipset is being used. Feel free to copy + paste the info from the log.

Right well you need to allow access to remote desktop users. It's a group policy thing for your machine and nothing to do with ImgBurn itself. Within the installer there's an option called 'Enable SPTI access in Remote Sessions', just enable it. If you want to do it manually, try googling 'AllowRemoteDASD'. That's the registry setting the installer manipulates.

Why are you making new threads when you already had one that's attempting to deal with your issue?

I'm just checking it was written to the disc ok and that ImgBurn can at least read it. Sorry, I have no idea why your car CD player can't read it.

Why is your drive on a jmicron controller and not the proper chipset one? If you must use the jmicron controller, install the latest drivers from here... ftp://driver.jmicron.com.tw/SATA_Controller/Windows/ If it's a plug-in card, update the option rom on it too... ftp://driver.jmicron.com.tw/SATA_Controller/Option_ROM/

You shouldn't have to worry too much about buffer recovery kicking in just once. All it means is that your machine was too busy to supply a steady stream of data - but the program only needed 5MB a second so it really shouldn't have been taxing a modern PC! What should concern you more is the 'write error' you received on the burn prior to that one with the same 'RITEKF1' discs being used. They're just cheap ones and you may get lots of coaster and bad quality burns.

Personally, I'd try burning them at 24x and if there's a firmware update available, do it regardless of what the release notes say it addresses. If it still won't burn to those discs, either forget about using the drive with them and stick to using your newer one or try those drives again with some better (Taiyo Yuden) discs.

It's saying.... ... so the CD-TEXT info has been written to the disc. If you switch the program into Read mode, click the 'View Media Information' button down the bottom right of the 'Source' box. It should read the CD-TEXT info on the disc and display the track names in the box that pops up.

Why? That value is read from the .DVD file. Put the setting back on 'Calculate Optimal'. Use the recommended Verbatim discs, not RITEK ones. Even then, you'll be lucky if it works. Really you need a Lite-On drive with 'Force HyperTuning' enabled for the overburning stuff to work properly.

You shouldn't have to do anything when using Windows 7. Are you running the program as a normal 'locally' logged on user (not via remote desktop etc) ? And the account is what, a 'Standard' account or an 'Administrator' account? You shouldn't need to elevate either account type, it should just work.

Not without seeing a log file. Any chance you could post one from where you burnt that CD?

Update the firmware on the drive. http://www.firmwarehq.com/LG/GH24NS90/files.html Try burning at 8x. Try some better discs.

That's got the CD-TEXT info in it, so it'll be on the disc. Playback (it being visible somewhere) is down to your player I'm afraid.

Could you attach the CUE file you created please? Or open it in notepad and copy+paste everything. Obviously the player needs to support the reading of CD-TEXT in the first place or it won't display anything.

I wasn't going to do it, don't worry

Some discs are just rubbish and drives don't work properly with them. Even if the firmware does contain that media code, the quality of discs can vary a lot with the low quality ones and it throws things off - meaning the drive isn't as 'calibrated' for burning them as it should be. That then leaves you with a disc the drive can't burn nicely and will probably be unreadable once burnt.

Look at the Audio CD guide in the Guides forum.

It looks like your drive is having trouble with those discs, get some different ones (some made by Verbatim perhaps).

You'd need to add the CD-TEXT info and use a player that reads CD-TEXT.