|
|
|
Problems burning discs
|
|
|
jerle
Newbie
|
19. September 2007 @ 07:27 |
Link to this message
|
Hello all,
I'm quite new to this site. I've recently been having problems with burning discs once I've run dvdshrink. I assumed it was because of the discs I was using (Dynex DVD+R). Maybe 1 in 5 Dynex discs worked, so I bought a different pack (Memorex DVD-R). I'm still getting errors though. DMA is listed as "on." If someone could please help me out, I would really appreciate it. Here is the error report.
Windows XP 5.1
IA32
WinAspi: File 'Wnaspi32.dll': Ver=4.60 (1021), size=45056 bytes, created 9/10/1999 12:06:00 PM
ahead WinASPI: File 'C:\Program Files\Ahead\nero\Nero\Wnaspi32.dll': Ver=2.0.1.74, size=164112 bytes, created 10/26/2004 11:35:32 AM
Nero API version: 6.6.0.8
Using interface version: 6.3.1.4
Installed in: C:\Program Files\Ahead\nero\Nero\
Application: ahead\Nero - Burning Rom
Recorder: <Memorex DVD+-RAM 510L v1>Version: MWS7 - HA 1 TA 0 - 6.6.0.8
Adapter driver: <atapi> HA 1
Drive buffer : 2048kB
Bus Type : via Inquiry data (1) -> ATAPI, detected: ATAPI
Connected to MMC as unknown drive with class-nr : 1
Drive is autodetected - recorder class: Std. MMC recorder
=== Scsi-Device-Map ===
DiskPeripheral : ST380013A atapi Port 0 ID 0 DMA: On
CdRomPeripheral : Memorex DVD+-RAM 510L v1 atapi Port 1 ID 0 DMA: On
CdRomPeripheral : HL-DT-ST CD-RW GCE-8527B atapi Port 1 ID 1 DMA: On
=== CDRom-Device-Map ===
Memorex DVD+-RAM 510L v1 E: CDRom0
HL-DT-ST CD-RW GCE-8527B F: CDRom1
=======================
AutoRun : 1
Excluded drive IDs:
WriteBufferSize: 73400320 (0) Byte
ShowDrvBufStat : 0
BUFE : 0
Physical memory : 503MB (515604kB)
Free physical memory: 136MB (139580kB)
Memory in use : 72 %
Uncached PFiles: 0x0
Use Inquiry : 1
Global Bus Type: default (0)
Check supported media : Disabled (0)
19.9.2007
NeroAPI
11:07:28 AM #1 Phase 112 File APIProgress.cpp, Line 276
DVD-Video files reallocation started
11:07:28 AM #2 Phase 114 File APIProgress.cpp, Line 276
DVD-Video files reallocation completed (no file modified)
11:07:28 AM #3 Phase 111 File APIProgress.cpp, Line 276
DVD-Video files sorted
11:07:29 AM #4 Text 0 File Reader.cpp, Line 127
Reader running
11:07:29 AM #5 Text 0 File Writer.cpp, Line 122
Writer Memorex DVD+-RAM 510L v1 running
11:07:29 AM #6 Text 0 File AudioCompilationImpl.cpp, Line 842
DRM: StartDrmRecording(RealRec:1, ImageRec:0, Copies:1)
DRM: Beginning burn process.
11:07:29 AM #7 ISO9660GEN -11 File geniso.cpp, Line 3293
First writeable address = 0 (0x00000000)
11:07:29 AM #8 ISO9660GEN -11 File geniso.cpp, Line 3293
First writeable address = 0 (0x00000000)
11:07:29 AM #9 Text 0 File Burncd.cpp, Line 3153
Turn on Disc-At-Once, using DVD media
11:09:22 AM #10 Text 0 File DlgWaitCD.cpp, Line 260
Last possible write address on media: 2298495 (510:46.45, 4489MB)
Last address to be written: 2286127 (508:01.52, 4465MB)
11:09:22 AM #11 Text 0 File DlgWaitCD.cpp, Line 272
Write in overburning mode: NO
11:09:22 AM #12 Text 0 File DlgWaitCD.cpp, Line 2339
Recorder: Memorex DVD+-RAM 510L v1, Media type: DVD-R
Disc Manufacturer: RITEKF - 1
Disc Application Code: 64, Disc Physical Code: 193
11:09:22 AM #13 Text 0 File DlgWaitCD.cpp, Line 438
>>> Protocol of DlgWaitCD activities: <<<
=========================================
Insert empty disc to write to.
(Medium in drive: unknown. Medium required by compilation: DVD+R/RW, DVD-R/RW, DVD-RAM, DVD-R DL, DVD+R DL.)
11:09:22 AM #14 Text 0 File ThreadedTransferInterface.cpp, Line 830
Setup items (after recorder preparation)
0: TRM_DATA_MODE1 ()
2 indices, index0 (150) not provided
original disc pos #0 + 2286128 (2286128) = #2286128/508:1.53
relocatable, disc pos for caching/writing not required/ required, no patch infos
-> TRM_DATA_MODE1, 2048, config 0, wanted index0 0 blocks, length 2286128 blocks [Memorex DVD+-RAM 510L v1]
--------------------------------------------------------------
11:09:22 AM #15 Text 0 File ThreadedTransferInterface.cpp, Line 1043
Prepare recorder [Memorex DVD+-RAM 510L v1] 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 4681990144, ISRC ""
DAO layout:
===========
__Start_|____Track_|_Idx_|_CtrlAdr_|_RecDep__________
0 | lead-in | 0 | 0x41 | 0x00
0 | 1 | 0 | 0x41 | 0x00
0 | 1 | 1 | 0x41 | 0x00
2286128 | lead-out | 1 | 0x41 | 0x00
11:09:22 AM #16 Phase 24 File APIProgress.cpp, Line 276
Caching of files started
11:09:22 AM #17 Text 0 File Burncd.cpp, Line 4040
Cache writing successful.
11:09:22 AM #18 Phase 25 File APIProgress.cpp, Line 276
Caching of files completed
11:09:22 AM #19 Phase 36 File APIProgress.cpp, Line 276
Burn process started at 16x (22,160 KB/s)
11:09:22 AM #20 Text 0 File ThreadedTransferInterface.cpp, Line 2609
Verifying disc position of item 0 (relocatable, disc pos, no patch infos, orig at #0): write at #0
11:09:23 AM #21 Text 0 File DVDR.cpp, Line 2216
Recording mode: Sequential Recording Mode
11:09:23 AM #22 Text 0 File Mmc.cpp, Line 21241
Set BUFE: Buffer underrun protection -> ON , Adapt writespeed to disc : ON
11:09:23 AM #23 Text 0 File DVDR.cpp, Line 2362
Start write address at LBA 0
DVD high compatibility mode: Yes
11:09:23 AM #24 Text 0 File Cdrdrv.cpp, Line 8430
---- DVD Structure: Physical Format Information (00h) ----
Layer: 0, Address: 0 (0 h), AGID: 0; Length: 2050
Book Type: DVD-R (2), Part Version: 5
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:10:11 AM #25 Text 0 File Cdrdrv.cpp, Line 1287
11:10:11.265 - Memorex DVD+-RAM 510L v1\H1 T0 : Queue again later
11:15:37 AM #26 SCSI -1135 File Cdrdrv.cpp, Line 1435
SCSI Exec, HA 1, TA 0, LUN 0, buffer 0x00D00000
Status: 0x04 (0x01, SCSI_ERR)
HA-Status 0x00 (0x00, OK)
TA-Status 0x02 (0x01, SCSI_TASTATUS_CHKCOND)
Sense Key: 0x03 (KEY_MEDIUM_ERROR)
Sense Code: 0x0C
Sense Qual: 0x00
CDB Data: 0x2A 0x00 0x00 0x18 0x17 0x20 0x00 0x00 0x20 0x00 0x00 0x00
Sense Data: 0x70 0x00 0x03 0x00 0x00 0x00 0x00 0x0A
0x00 0x00 0x00 0x00 0x0C 0x00
11:15:37 AM #27 CDR -1135 File Writer.cpp, Line 311
Write error
11:15:37 AM #28 Text 0 File ThreadedTransfer.cpp, Line 228
all writers idle, stopping conversion
11:15:37 AM #29 Text 0 File ThreadedTransfer.cpp, Line 222
conversion idle, stopping reader
11:15:37 AM #30 Text 0 File DVDR.cpp, Line 2625
EndDAO: Last written address was 1578783
11:15:37 AM #31 Phase 38 File APIProgress.cpp, Line 276
Burn process failed at 16x (22,160 KB/s)
11:15:37 AM #32 Text 0 File AudioCompilationImpl.cpp, Line 867
DRM: DRM burn session terminated.
11:15:37 AM #33 Text 0 File AudioCompilationImpl.cpp, Line 896
DRM: Closing entire DRM handling. Bye.
Existing drivers:
File 'Drivers\CDRALW2K.SYS': Ver=8.0.0.212 , size=2560 bytes, created 8/24/2006 10:47:00 PM
File 'Drivers\ASPI32.SYS': Ver=4.60 (1021), size=25244 bytes, created 9/10/1999 12:06:00 PM
File 'Drivers\PXHELP20.SYS': Ver=3.00.33a, size=36528 bytes, created 8/24/2006 10:47:00 PM (Prassi/Veritas driver for win 2K)
Registry Keys:
HKLM\Software\Microsoft\Windows NT\CurrentVersion\WinLogon\AllocateCDROMs : 0 (Security Option
This message has been edited since posting. Last time this message was edited on 19. September 2007 @ 08:32
|
|
Advertisement
|
|
|
|
Senior Member
|
19. September 2007 @ 08:26 |
Link to this message
|
|
Edit out your serial numbers, they begin with 1A20
Get better Media (Verbatim)
Burn at 1/2 the rated speed of the disc
You could use more Memory
Don't surf the net while burning
Change the Target Size to 4300mb
This message has been edited since posting. Last time this message was edited on 19. September 2007 @ 08:28
|
|
laddyboy
AfterDawn Addict
|
19. September 2007 @ 10:26 |
Link to this message
|
|
|
|
JoeRyan
Senior Member
|
19. September 2007 @ 13:16 |
Link to this message
|
"Memorex may be a brand name but it uses lower quality media manufacturers for its product."
You are so right. Memorex uses Ritek; and Ritek makes Maxell and Ricoh, two other terrible brands. Oh, the "F" in the M-code refers to Fuji's Oxonol dye, and everyone knows Fuji sucks. And when Memorex isn't using Ritek, they use CMC. And CMC cannot make a good disc if it killed them. You really ought to use some good brands such as Maxell or Verbatim because they are made by Ritek and CMC, two very good manufacturers.
This message has been edited since posting. Last time this message was edited on 19. September 2007 @ 13:39
|
Senior Member
|
19. September 2007 @ 13:30 |
Link to this message
|
@laddyboy
Isn't this a Roxio Thingy CDRALW2K.SYS': Ver=8.0.0.212 ?? Wouldn't jerle have to run Roxiozap Before
re-installing Nero?
@jerle
A Great Site to Learn from. Lots of info, tips Programs....
http://www.dvdplusvideo.com
|
Moderator
1 product review
|
19. September 2007 @ 13:37 |
Link to this message
|
Originally posted by JoeRyan:
"Memorex may be a brand name but it uses lower quality media manufacturers for its product."
You are so right. Memorex uses Ritek; and Ritek makes Maxell and Ricoh, two other terrible brands. Oh, the "F" in the M-code refers to Fuji's Oxonol dye, and everyone knows Fuji sucks. And when Memorex isn't using Ritek, they use CMC. And CMC makes Verbatim so you know they stink. You ought to use other good brands such as Maxell or Verbatim because they are made by Ritek and CMC.
LOL Joe, don't stoop to our level please. I rather enjoy reading your usual posts and emplore you to fight the good fight. :)
|
|
JoeRyan
Senior Member
|
19. September 2007 @ 13:44 |
Link to this message
|
Sorry, LOCOENG. I apologize. Sometimes the logic gets so twisted in my head that my brain hurts.
Berryone is on to something with the Roxio/Nero conflict. Jerle may have had Roxio on his computer before installing the drive and then installed Nero from the installation disc that usually comes with the drive. I think the drive is the equivalent to a Lite-on 18X drive; so it is new enough to be up to the latest M-codes.
|
Moderator
1 product review
|
19. September 2007 @ 13:47 |
Link to this message
|
Yes indeed Joe, the Roxio cdral drivers are known to muck with Nero.
I quite enjoyed you tyrade BTW...very entertaining.
|
Senior Member
|
19. September 2007 @ 14:38 |
Link to this message
|
|
@JoeRyan
Didn't mean to offend you. I was only going by Brand. I only reccomend
Verbatim Brand Because I have had Great Luck with them. (0 Coasters in over 2000 burns)I did overlook the "Ritekf" code in the log. But in my defense I only Have one Eye. I also know that other Brands are Just as good. 90% of my Back-ups are On Ritek Media. I too enjoy and Learn from your Post.
|
|
laddyboy
AfterDawn Addict
|
19. September 2007 @ 19:05 |
Link to this message
|
The Roxio driver only seems to cause problems for some configurations. I have no idea what they are. Many of us have the Roxio driver installed without having any Roxio software since some other download sites use it for burning as well as some computer manufacturers for burning recovery DVDs/CDs. Quite a few of us have numerous burning programs installed including the Roxio suite and don't experience conflicts. Others do. Nero recommends it be removed or at least they used to. The Nero Driver Clean Tool usually locates it as well. If you don't need it, it doesn't hurt to zap it. Just google roxiozap for the zapper. I'm on another system and don't have the link available.
|
Member
|
20. September 2007 @ 04:10 |
Link to this message
|
Originally posted by LOCOENG:
Originally posted by JoeRyan:
"Memorex may be a brand name but it uses lower quality media manufacturers for its product."
You are so right. Memorex uses Ritek; and Ritek makes Maxell and Ricoh, two other terrible brands. Oh, the "F" in the M-code refers to Fuji's Oxonol dye, and everyone knows Fuji sucks. And when Memorex isn't using Ritek, they use CMC. And CMC makes Verbatim so you know they stink. You ought to use other good brands such as Maxell or Verbatim because they are made by Ritek and CMC.
LOL Joe, don't stoop to our level please. I rather enjoy reading your usual posts and emplore you to fight the good fight. :)
LOCO: I thought the same thing as I read his reply. This is the first time I can remember JoeRyan saying the media sucked, rather than a "compatability" issue. :)
|
|
JoeRyan
Senior Member
|
20. September 2007 @ 07:09 |
Link to this message
|
|
There are some factories and "brands" that can consistently be counted on for poor performance, but I won't name them. They don not often show up in this forum anyway. Whenever I might "attack" a brand, I'm being facetious. It's a joke. I prefer to defend good brands from accusations that are not supported by technical facts, and I refrain from demeaning any brand, even the bad ones.
|
Member
|
20. September 2007 @ 17:12 |
Link to this message
|
Originally posted by JoeRyan:
There are some factories and "brands" that can consistently be counted on for poor performance, but I won't name them. They don not often show up in this forum anyway. Whenever I might "attack" a brand, I'm being facetious. It's a joke. I prefer to defend good brands from accusations that are not supported by technical facts, and I refrain from demeaning any brand, even the bad ones.
Okee Dokee. You might try using a smiley face. After all, you don't exactly have a reputation on here for levity. :D
|
|
JoeRyan
Senior Member
|
21. September 2007 @ 06:01 |
Link to this message
|
|
|
Moderator
1 product review
|
21. September 2007 @ 06:06 |
Link to this message
|
|
LMAO....good one Joe. :D
|
|
Advertisement
|
|
|
Member
|
24. September 2007 @ 12:01 |
Link to this message
|
Originally posted by JoeRyan:
http://forums.afterdawn.com/thread_view.cfm/16/539722#3326677
:]
Sorry for the late reply, but I have been out of town.
My apologies, Mr. JoeRyan. It seems that you can indeed tickle the funnybone.
|
|
