They don't call him the Nero-nator for nothin'...LOL @GPL44 I did the new Potter movie yesterday...ripped to HDD using DVD Decrypter/AnyDVD and transcoded/burned with Nero Recode/Burning Rom. I think you definately have a conflict with the software somewhere.
I too just did HP movie using just Decrypter and Recode no problems at all. This is a WB flick and they never have anything funny on their releases.
Harry Potter's not out here 'til Monday however (as ever lol) i suspect there'll be nothing special about backing it up
"I did the new Potter movie yesterday...ripped to HDD using DVD Decrypter/AnyDVD and transcoded/burned with Nero Recode/Burning Rom. I think you definately have a conflict with the software somewhere." I agree, I'm about ready to pull the trigger on the format c: if uninstalling/reinstalling Norton doesn't help. GPL44
LOCOENG, Cutting to the chase, I uninstalled Music Match Jukebox Plus 10 and now everything seems to be working. Uninstalling Norton didn't help. Not wanting to waste my Verbatim DVDs I have been doing test burns with the old Memorex discs and not having issues. No one get excited, I will be using Verbatims for anything I consider of value. I will reinstall MMJB+10 and see what happens, MM was installed before the issues started but perhaps something got corrupted. I am using Nero 7.0.8.2 at the present. Stay tuned (Be a shame to let this nice long thread die)
Hi. Locoeng already helped me and it worked. But I found the problem was in trying to burn DVD-RW, because I used DVD-R and worked perfectly. I'm using TDK and Imation DVD-RW. I know here it's posted that the best DVD's are like vervabatim, sony, and others. But I want to know if the DVD's-RW are the ones that don't work or it's the DVD Burner that don't accepts it. Please help me and tell me if you need to see the log. Thanks
@pakman If I had to guess, which is what I'm forced to do I would say it is the DVD-RW media, maybe your standalone doesn't play that format????
LOCOENG, Burned about 6 DVDs at 16x using the Verbatims. Log to follow. Reinstalled Music Match Plus 10 and burns immediately started failing with the infamous "Illegal Disk". Found MIM.EXE and MMDIAG.EXE processes belonging to Music Match, killed the MIM process and the MMDIAG process disappeared on its own. With those two processes gone the burner worked fine again, burning at 16x. Started Music Match and the two processes showed up again and did not stop when I exited Music Match. Sent an email to them, waiting on a reply. Pretty much nails it I guess. But I would like to know why and have a fix. Up to MM at this point. 16x Log: 1C82- Windows XP 5.1 IA32 WinAspi: - ahead WinASPI: File 'C:\Program Files\Nero\Nero 7\Core\Wnaspi32.dll': Ver=2.0.1.74, size=164112 bytes, created 11/2/2004 12:54:32 PM NT-SPTI used Nero Version: 7.0.8.2 Internal Version: 7, 0, 8, 2 Recorder: <LITE-ON DVDRW SHW-160P6S>Version: PS08 - HA 1 TA 0 - 7.0.8.2 Adapter driver: <IDE> HA 1 Drive buffer : 2048kB Bus Type : default (0) -> ATAPI, detected: ? CD-ROM: <LITE-ON DVDRW SHW-160P6S>Version: PS08 - HA 1 TA 0 - 7.0.8.2 Adapter driver: <IDE> HA 1 === Scsi-Device-Map === DiskPeripheral : Maxtor 6Y250P0 atapi Port 0 ID 0 DMA: On DiskPeripheral : ST3300631A atapi Port 0 ID 1 DMA: On CdRomPeripheral : LITE-ON DVDRW SHW-160P6S atapi Port 1 ID 0 DMA: On DiskPeripheral : Promise Array 1.10 ftsata2 Port 2 ID 0 DMA: Off OtherPeripheral : Promise RAID Console 1.00 ftsata2 Port 2 ID 4 DMA: Off === CDRom-Device-Map === LITE-ON DVDRW SHW-160P6S E: CDRom0 ======================= AutoRun : 1 Excluded drive IDs: WriteBufferSize: 83886080 (0) Byte BUFE : 0 Physical memory : 1023MB (1047772kB) Free physical memory: 419MB (429356kB) Memory in use : 59 % Uncached PFiles: 0x0 Use Inquiry : 1 Global Bus Type: default (0) Check supported media : Disabled (0) 16.3.2006 Burn DVD Image 11:12:23 PM #1 Text 0 File ThreadedTransfer.cpp, Line 531 ReadBuffer-Pipe got 262144KB of Memory 11:12:23 PM #2 Text 0 File Reader.cpp, Line 124 Reader running 11:12:23 PM #3 Text 0 File Writer.cpp, Line 113 Writer E: LITE-ON DVDRW SHW-160P6S running 11:12:23 PM #4 Text 0 File Burncd.cpp, Line 3353 Turn on Disc-At-Once, using DVD media 11:12:23 PM #5 Text 0 File DlgWaitCD.cpp, Line 289 Last possible write address on media: 2298495 (510:46.45, 4489MB) Last address to be written: 2285998 (507:59.73, 4464MB) 11:12:23 PM #6 Text 0 File DlgWaitCD.cpp, Line 301 Write in overburning mode: NO (enabled: CD) 11:12:23 PM #7 Text 0 File DlgWaitCD.cpp, Line 2715 Recorder: LITE-ON DVDRW SHW-160P6S, Media type: DVD-R Disc Manufacturer: MCC 03 - RG20 Disc Application Code: 64, Disc Physical Code: 193 11:12:23 PM #8 Text 0 File DlgWaitCD.cpp, Line 473 >>> Protocol of DlgWaitCD activities: <<< ========================================= 11:12:23 PM #9 Text 0 File ThreadedTransferInterface.cpp, Line 847 Setup items (after recorder preparation) 0: TRM_DATA_MODE1 (2 - CD-ROM Mode 1, ISO 9660) 2 indices, index0 (150) not provided original disc pos #0 + 2285999 (2285999) = #2285999/507:59.74 not relocatable, disc pos for caching/writing not required/not required, no patch infos -> TRM_DATA_MODE1, 2048, config 0, wanted index0 0 blocks, length 2285999 blocks [E: LITE-ON DVDRW SHW-160P6S] -------------------------------------------------------------- 11:12:23 PM #10 Text 0 File ThreadedTransferInterface.cpp, Line 1059 Prepare recorder [E: LITE-ON DVDRW SHW-160P6S] for write in CUE-sheet-DAO DAO infos: ========== MCN: "" TOCType: 0x00; Session Closed, disc fixated Tracks 1 to 1: 1: TRM_DATA_MODE1, 2048/0x00, FilePos 0 0 4681725952, ISRC "" DAO layout: =========== __Start_|____Track_|_Idx_|_CtrlAdr_|_RecDep__________ 0 | lead-in | 0 | 0x41 | 0x00 0 | 1 | 0 | 0x41 | 0x00 0 | 1 | 1 | 0x41 | 0x00 2285999 | lead-out | 1 | 0x41 | 0x00 11:12:23 PM #11 Text 0 File SCSIPassThrough.cpp, Line 39 SPTILockVolume - completed successfully for FCTL_LOCK_VOLUME 11:12:23 PM #12 Text 0 File SCSIPassThrough.cpp, Line 84 SPTIDismountVolume - completed successfully for FSCTL_DISMOUNT_VOLUME 11:12:23 PM #13 Phase 24 File dlgbrnst.cpp, Line 1730 Caching of files started 11:12:23 PM #14 Text 0 File Burncd.cpp, Line 4187 Cache writing successful. 11:12:23 PM #15 Phase 25 File dlgbrnst.cpp, Line 1730 Caching of files completed 11:12:23 PM #16 Phase 36 File dlgbrnst.cpp, Line 1730 Burn process started at 16x (22,160 KB/s) 11:12:23 PM #17 Text 0 File ThreadedTransferInterface.cpp, Line 2707 Verifying disc position of item 0 (not relocatable, no disc pos, no patch infos, orig at #0): write at #0 11:12:23 PM #18 Text 0 File DVDR.cpp, Line 2760 Recording mode: Sequential Recording Mode 11:12:23 PM #19 Text 0 File DVDR.cpp, Line 2916 Start write address at LBA 0 DVD high compatibility mode: Yes 11:12:23 PM #20 Text 0 File Cdrdrv.cpp, Line 8661 ---- DVD Structure: Physical Format Information (00h) ---- Media Type: 0, Layer: 0, Address: 0 (0 h), AGID: 0; Length: 2050 Book Type: DVD-R (2), Part Version: 2.0x (5), Extended Part Version: 2.1 (33) Disc Size: 120 mm, Maximum Rate: <not specified> (F h) Number of Layers: 1, Track Path: Parallel Track Path (PTP), Layer Type: recordable Linear Density: 0,267 um/bit, Track Density: 0,74 um/track Starting Physical Sector Number of Data Area: 30000 h (DVD-ROM, DVD-R/-RW, DVD+R/+RW) End Physical Sector Number of Data Area: 26127F h End Sector Number in Layer 0: 0 h (LBN: FFFD0000 h, 4193920 MB) Data in Burst Cutting Area (BCA) does not exist Start sector number of the current Border-Out: 0 h Start sector number of the next Border-In: 0 h Media Specific [16..63]: 00 60 00 10 20 30 40 50 - 00 00 00 21 00 00 00 00 .`...0@P...!.... 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................ 11:13:09 PM #21 Text 0 File Cdrdrv.cpp, Line 1211 23:13:09.593 - E: LITE-ON DVDRW SHW-160P6S : Queue again later 11:18:20 PM #22 Text 0 File WriterStatus.cpp, Line 116 <E: LITE-ON DVDRW SHW-160P6S> start writing Lead-Out at LBA 2285999 (22E1AFh), length 0 blocks 11:18:21 PM #23 Text 0 File ThreadedTransfer.cpp, Line 228 all writers idle, stopping conversion 11:18:21 PM #24 Text 0 File DVDR.cpp, Line 3156 EndDAO: Last written address was 2285983 11:18:33 PM #25 Phase 37 File dlgbrnst.cpp, Line 1730 Burn process completed successfully at 16x (22,160 KB/s) 11:18:33 PM #26 Phase 78 File dlgbrnst.cpp, Line 1730 Data verification started 11:23:38 PM #27 Text 0 File ThreadedTransfer.cpp, Line 228 all writers idle, stopping conversion 11:23:38 PM #28 Phase 80 File dlgbrnst.cpp, Line 1730 Data verification completed successfully Existing drivers: Registry Keys: HKLM\Software\Microsoft\Windows NT\CurrentVersion\WinLogon\AllocateCDROMs : 0 (Security Option)
As gwen stated the obvious, it's all I see too. Dont know why Music Match would be creating a conflict, that's a new one on me...but each system is different.
You might want to adjust your target size a little as well to keep from burning too close to the edge. 16x is a little fast for my likes as well. Target size won't have anything to do with the MM though. Your log says that the burn completed successfully.
@9mmruger1 I think this is a burn log with the MM gone, and showing that the program works without MM present.
What is the downside of burning at 16x if it is reliable?? Or is it? I see the new Plextor 760 will burn Verbatims at 18x To be honest I normally burn at 8x-12x but 16x has been working out fine with the new Lite-on drive.
@GPL44 - here's my take on things relating to burn speeds....i have a post near the end that explains how i personally feel about speeds - http://forums.afterdawn.com/thread_view.cfm/1/316384#1842008
creaky, Thanks, read your post in that link. I will admit I have been doing verifies on those 16x burns and scanning the chapters in the movies. I am confident at 8x and do none of those things. I too have a bunch of those orange discs in my collection (not to mention a 'pot' load of Memorex). For those movies that I really care about I plan on reburning with collectors and/or extended versions. Definitely will be putting my digital still/mini DV backups on Verbatim. Again, thanks all ( I sure wish Music Match was a quick with replies as you guys, and gal! are )
Out of curiousity, did you kill those two MM utility files in your startup, as I believe both of those load on boot.
@ruger So nice of you to grace us with your presence...LOL Works been keeping you away too much lately.