|
|
|
Not another burn process failed thread...
|
|
|
layeggs
Suspended due to non-functional email address
|
12. April 2004 @ 14:54 |
Link to this message
|
|
Hi folks, this will be my first post but in need of some advice and help on my current problem.
To cut to the chase, I'm getting errors using DVD Shrink & Nero (all latest versions) when backing to DVD-R (using Princo X4) - under Windows XP. At first I thought it was a media fault but have tried a different batch since and still getting the errors. Then I thought it was a software conflict but have reformatted the HD since and still fails. I've even tried the 'DMA select' option and still no go.
Having read the failed log, I'm thinking it could be an ASPI conflict of some sort.
So what's up with my LG-GSA-4081B-A101 DVD burner? How can I correct it?
Any help would be much appreciated. Thanks in advance.
See the burned failed below:
Using Nero
6:29:43 AM #27 SCSI -1039 File Cdrdrv.cpp, Line 1437
SCSI Exec, HA 1, TA 0, LUN 0, buffer 0x035D0000
Status: 0x04 (0x01, SCSI_ERR)
HA-Status 0x00 (0x00, OK)
TA-Status 0x02 (0x01, SCSI_TASTATUS_CHKCOND)
Sense Key: 0x04 (KEY_HARDWARE_ERROR)
Sense Code: 0x09
Sense Qual: 0x01
CDB Data: 0x2A 0x00 0x00 0x21 0x26 0x80 0x00 0x00 0x20 0x00 0x00 0x00
Sense Data: 0x71 0x00 0x04 0x00 0x00 0x00 0x00 0x10
0x32 0x34 0x04 0x0C 0x09 0x01
6:29:43 AM #28 CDR -1039 File Writer.cpp, Line 304
Focus or tracking error
6:29:43 AM #29 Text 0 File ThreadedTransfer.cpp, Line 229
all writers idle, stopping conversion
6:29:44 AM #30 Text 0 File ThreadedTransfer.cpp, Line 223
conversion idle, stopping reader
6:29:44 AM #31 Text 0 File DVDR.cpp, Line 1970
EndDAO: Last written address was 2172543
6:29:45 AM #32 Text 0 File dlgbrnst.cpp, Line 1699
Set remaining time: 0:00,000 (0ms) -> OK
6:29:45 AM #33 Text 0 File dlgbrnst.cpp, Line 1699
Set remaining time: 0:00,000 (0ms) -> OK
6:29:45 AM #34 Phase 38 File dlgbrnst.cpp, Line 1841
Burn process failed at 4x (5,520 KB/s)
Using DVD Shrink
6:04:15 AM #24 SCSI -1039 File Cdrdrv.cpp, Line 1437
SCSI Exec, HA 1, TA 0, LUN 0, buffer 0x013F0000
Status: 0x04 (0x01, SCSI_ERR)
HA-Status 0x00 (0x00, OK)
TA-Status 0x02 (0x01, SCSI_TASTATUS_CHKCOND)
Sense Key: 0x04 (KEY_HARDWARE_ERROR)
Sense Code: 0x09
Sense Qual: 0x01
CDB Data: 0x2A 0x00 0x00 0x1D 0x42 0x20 0x00 0x00 0x20 0x00 0x00 0x00
Sense Data: 0x71 0x00 0x04 0x00 0x00 0x00 0x00 0x10
0x32 0x34 0x04 0x0C 0x09 0x01
6:04:15 AM #25 CDR -1039 File Writer.cpp, Line 304
Focus or tracking error
6:04:15 AM #26 Text 0 File ThreadedTransfer.cpp, Line 229
all writers idle, stopping conversion
6:04:15 AM #27 Text 0 File ThreadedTransfer.cpp, Line 223
conversion idle, stopping reader
6:04:15 AM #28 Text 0 File DVDR.cpp, Line 1970
EndDAO: Last written address was 1917471
6:04:16 AM #29 Phase 38 File APIProgress.cpp, Line 266
Burn process failed at 4x (5,540 KB/s)
6:04:16 AM #30 Text 0 File AudioCompilationImpl.cpp, Line 828
DRM: DRM burn session terminated.
6:04:16 AM #31 Text 0 File AudioCompilationImpl.cpp, Line 857
DRM: Closing entire DRM handling. Bye.
This message has been edited since posting. Last time this message was edited on 12. April 2004 @ 14:57
|
|
Advertisement
|
|
|
|
Moderator
|
12. April 2004 @ 16:53 |
Link to this message
|
Quote:
At first I thought it was a media fault but have tried a different batch since
Just to clarify, you used a different batch of Princos, correct? A focus or tracking error may mean your burner doesn't like the Princos.
I'd highly suggest giving good media such as Ritek G04 or Verbatim Metal AZO a try.
If you insist on the Princos then try burning them at 2X.
Hope this helps :)
My killer sig came courtesy of bb "El Jefe" mayo.
The Forum Rules You Agreed To! http://forums.afterdawn.com/thread_view.cfm/2487
"And there we saw the giants, and we were in our own sight as grasshoppers, and so we were in their sight" - Numbers 13:33 This message has been edited since posting. Last time this message was edited on 12. April 2004 @ 16:55
|
|
layeggs
Suspended due to non-functional email address
|
12. April 2004 @ 23:12 |
Link to this message
|
Quote:
If you insist on the Princos then try burning them at 2X.
Thanks for that suggestion. I'll give it a go.
|
|
layeggs
Suspended due to non-functional email address
|
12. April 2004 @ 23:43 |
Link to this message
|
|
Tried burining @ 2X with the Princo media and problem still persists. This happens not on just movies but also when I'm backing up data.
Getting very frustrated at the moment.
|
|
layeggs
Suspended due to non-functional email address
|
13. April 2004 @ 06:18 |
Link to this message
|
|
Just had another thought to my possible problem:
I'd recently upgraded and flashed my burner to disable the RPC firmware. Could this have somehow casued all this to function improperly?
I'm in desperate need of a solution for this.
This message has been edited since posting. Last time this message was edited on 13. April 2004 @ 06:19
|
Moderator
|
13. April 2004 @ 07:49 |
Link to this message
|
Quote:
I'd recently upgraded and flashed my burner to disable the RPC firmware.
Did your problem start right after the flash or were the probelms there before? When using "hacked" firmwares you run the risk of getting one that will end up hosing your burner.
And now to the Princos - they are a low-grade media that many, many people have problems with. At this point, my best suggestion would be to go to the store and pick up a few Verbatim discs and test them out in order to rule out the Princos as the cause of your problems. If the Verbatims run through with fine results then we can safely say the Princos are to blame. If the problem persists then we know to start looking at other factors.
Just to cover the basics, here are a couple links to verify that your ASPI and DMA settings are in good order:
ASPI
http://cd-rw.org/articles/archive/aspisetup.cfm
DMA
http://www.microsoft.com/whdc/hwdev/tech/storage/ide-dma.mspx
We'll get to the bottom of this and get ya burnin" :)
My killer sig came courtesy of bb "El Jefe" mayo.
The Forum Rules You Agreed To! http://forums.afterdawn.com/thread_view.cfm/2487
"And there we saw the giants, and we were in our own sight as grasshoppers, and so we were in their sight" - Numbers 13:33
|
|
layeggs
Suspended due to non-functional email address
|
13. April 2004 @ 12:46 |
Link to this message
|
Quote:
We'll get to the bottom of this and get ya burnin" :)
Nephilim, I appreciate your continued help on this matter.
Quote:
Did your problem start right after the flash or were the probelms there before?
IIRC, it may have started after I'd flashed the drive. Though I did make a couple of coasters before but not as frequent as this instance - where all have been incomplete with errors. So now I'm starting to think that it must've been the flash firmware. Well, I am in the process of isolating it and signs are against the 'hacked' firmware.
I'm pretty sure my DMA settings are in good order and confident (not entirely sure though) that the ASPI is not in conflict with the burn process.
So now comes the investigation of the Princo media. I tested a batch of the Princos at a friend's setup (same OS, same LG DVD-RAM, same applications such as Nero & DVD Shrink, and who by the way has yet to flash his drive) and WHAMMO!! No problemo whatsoever. My princo media seems to comply (which is a relief since I have about 40-odd blanks left).
Moreover, I tested burning a CDR and it got the all clear. Now I'm gonna have to fix the DVDR bit. Is it using the same laser (or burning function) to imprint onto the media?
This message has been edited since posting. Last time this message was edited on 13. April 2004 @ 13:02
|
|
layeggs
Suspended due to non-functional email address
|
13. April 2004 @ 12:58 |
Link to this message
|
|
Okay, here's my latest attempt with DVD Shrink (see below). I'd installed the bare minimum in order to isolate the problem, ie. Windows XP SR1, then installed Nero (which failed to burn), then DVD Shrink (which also failed, see log below).
Has anyone ever had any problems with the RPC flash firmware for the LG-GSA-4081B-A101 DVD burner?
Just to recap; CDR backup seems to work, DVD playback seems to work (with region protection disabled), CDROM & DVDROM playback is fully functional.
Damn! I'm losing sleep over this matter ;)
BTW, anyone have any comments on the Liteon LDW812S (8x)? Thinking of a replacement already :)
Using DVD Shrink
1:57:10 AM #14 Phase 24 File APIProgress.cpp, Line 266
Caching of files started
1:57:10 AM #15 Text 0 File Burncd.cpp, Line 4214
Cache writing successful.
1:57:10 AM #16 Phase 25 File APIProgress.cpp, Line 266
Caching of files completed
1:57:10 AM #17 Phase 36 File APIProgress.cpp, Line 266
Burn process started at 4x (5,540 KB/s)
1:57:10 AM #18 Text 0 File ThreadedTransferInterface.cpp, Line 2342
Verifying disc position of item 0 (relocatable, disc pos, no patch infos, orig at #0): write at #0
1:57:10 AM #19 Text 0 File DVDR.cpp, Line 1619
Recording mode: Sequential Recording Mode
1:57:10 AM #20 Text 0 File Mmc.cpp, Line 19864
Set BUFE: supported -> ON
1:57:10 AM #21 Text 0 File DVDR.cpp, Line 1760
Start write address at LBA 0
DVD high compatibility mode: Yes
1:57:11 AM #22 Text 0 File Cdrdrv.cpp, Line 8002
---- 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
Data in Burst Cutting Area (BCA) does not exist
Start sector number of the current Border-Out: 2FE10 h
Start sector number of the next Border-In: 2FFA0 h
Media Specific [16..63]:
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
00 02 FE 10 00 02 FF A0 - 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
1:57:42 AM #23 SCSI -1135 File Cdrdrv.cpp, Line 1437
SCSI Exec, HA 1, TA 0, LUN 0, buffer 0x012B0000
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 0x00 0x00 0x00 0x00 0x00 0x20 0x00 0x00 0x00
Sense Data: 0x70 0x00 0x03 0x00 0x00 0x00 0x00 0x10
0x32 0x4D 0x03 0x0C 0x0C 0x00
1:57:42 AM #24 CDR -1135 File Writer.cpp, Line 304
Write error
1:57:42 AM #25 Text 0 File ThreadedTransfer.cpp, Line 229
all writers idle, stopping conversion
1:57:42 AM #26 Text 0 File ThreadedTransfer.cpp, Line 223
conversion idle, stopping reader
1:57:42 AM #27 Text 0 File DVDR.cpp, Line 1970
EndDAO: Last written address was -1
1:57:44 AM #28 Phase 38 File APIProgress.cpp, Line 266
Burn process failed at 4x (5,540 KB/s)
1:57:44 AM #29 Text 0 File AudioCompilationImpl.cpp, Line 828
DRM: DRM burn session terminated.
1:57:44 AM #30 Text 0 File AudioCompilationImpl.cpp, Line 857
DRM: Closing entire DRM handling. Bye.
This message has been edited since posting. Last time this message was edited on 13. April 2004 @ 13:06
|
Moderator
|
13. April 2004 @ 16:11 |
Link to this message
|
|
My best guess is that the RPC firmware is mucking things up if your friend has the same model and that batch of Princos burn alright coupled with the fact that you had far less problems before the flash.
I know very little about swapping firmwares (because I'm a pansy when it comes to hacked firmwares ) but it may be possible to reflash it to an earlier firmware - don't quote me on it though :)
The LiteOn is a good drive but for not much more you can get a Pioneer 107 which is arguably the best drive available.
My killer sig came courtesy of bb "El Jefe" mayo.
The Forum Rules You Agreed To! http://forums.afterdawn.com/thread_view.cfm/2487
"And there we saw the giants, and we were in our own sight as grasshoppers, and so we were in their sight" - Numbers 13:33
This message has been edited since posting. Last time this message was edited on 13. April 2004 @ 16:12
|
|
layeggs
Suspended due to non-functional email address
|
13. April 2004 @ 22:28 |
Link to this message
|
Quote:
it may be possible to reflash it to an earlier firmware
I'll look into this one.
|
|
layeggs
Suspended due to non-functional email address
|
14. April 2004 @ 08:15 |
Link to this message
|
Quote:
(because I'm a pansy when it comes to hacked firmwares )
Nephilim, it seems to me that RPC does not concern you when it comes to using your DVD-burner. So my question is that does the RPC affect the drive when it comes to encoding/ripping with Nero/DVDShrink/DVDDecrypter/CloneDVD2? If the case is no then I really did not need to go to the trouble of flashing my drive to rid of the RPC device then, did I?
|
Moderator
|
14. April 2004 @ 08:32 |
Link to this message
|
Hiya,
Making a drive region free is useful if you deal with movies from different regions. For example, movies in the States are Region 1 and movies in Europe are Region 2 etc.The studios do this so they can basically fix prices for different regions - greedy b@stards!
I'm in the States and all the movies I deal with are Region 1 so I've never had the need to bypass RPC. If you are in a situation like me, where you only deal with one region, then you're flash wasn't needed. You're burner should come from the factory already set for the region you bought it in and if you're ripping discs from the same region that the burner is set to, then no, the region coding will have no effect on the rip/burning process.
Here's a great link that explains the hows and whys of region coding:
http://www.dvddemystified.com/dvdfaq.html#1.10
Seeya :)
My killer sig came courtesy of bb "El Jefe" mayo.
The Forum Rules You Agreed To! http://forums.afterdawn.com/thread_view.cfm/2487
"And there we saw the giants, and we were in our own sight as grasshoppers, and so we were in their sight" - Numbers 13:33
|
|
layeggs
Suspended due to non-functional email address
|
14. April 2004 @ 10:12 |
Link to this message
|
|
Hey Nephilim, thanks for swift reply.
It wasn't really the answer to the question I was asking but nevertheless thanks for the link and quick guide. I'm in the region 4 zone and am fully aware of DVD regioning. Ocassionally, I import DVDs from region 1 land.
However, the question I'd like an answer to was if the region coding will take effect if I deploy one of the encoding/burning program to backup my DVDs. That is, if it subtracts one out of five attempts?
BTW, it seems now that CDR burning is giving me issues and that Windows is giving me DVD-Drive for the LG burner instead of DVD-RAM. All signs now are pointing to a bad flash firmware, no?
This message has been edited since posting. Last time this message was edited on 14. April 2004 @ 10:41
|
Moderator
|
14. April 2004 @ 11:48 |
Link to this message
|
Gotcha!
Quote:
However, the question I'd like an answer to was if the region coding will take effect if I deploy one of the encoding/burning program to backup my DVDs. That is, if it subtracts one out of five attempts?
I don't think so, but not having run into this myself, I can't say for sure - I imagine it might give some sort of "region conflict" or "unable to continue" error. If you deal with different region discs frequently there is a software app that I hear is quite good for bypassing region coding and allowing backup apps to do their thing without any firmware tweaks. Here's the link:
http://www.dvd-idle.com/dvd-region-free.htm
Sure sounds like a bad flash :(
My killer sig came courtesy of bb "El Jefe" mayo.
The Forum Rules You Agreed To! http://forums.afterdawn.com/thread_view.cfm/2487
"And there we saw the giants, and we were in our own sight as grasshoppers, and so we were in their sight" - Numbers 13:33
This message has been edited since posting. Last time this message was edited on 14. April 2004 @ 11:50
|
|
doseyclwn
Newbie
|
14. April 2004 @ 11:56 |
Link to this message
|
|
Guys, I had the same problem as the person who started the thread. I solved it by changing the size of the disc I was burning to (settings in DVD shrink) to 4450 instead of 4464). Since thne I have burned no coasters. It's a hell of a lot less hassle than screwing with firmware and all that other crap.
|
|
layeggs
Suspended due to non-functional email address
|
14. April 2004 @ 12:18 |
Link to this message
|
Quote:
Sure sounds like a bad flash :(
Further to my investigation into this matter, I'd tried "reflashing" the drive back to its previous firware before the 'hacked' FW using the 'official' LG GSA-4081B Version A101 Firmware Update.
Well, after reloading it the program tells me that it was successful and to reboot to which I obeyed. For the life of me it still seems the same. CDR is failing now!
Option now is for a new burner :( - and I will consider the Pioneer as suggested.
|
|
layeggs
Suspended due to non-functional email address
|
14. April 2004 @ 12:28 |
Link to this message
|
Quote:
I solved it by changing the size of the disc I was burning to (settings in DVD shrink) to 4450 instead of 4464).
I give this a try but I doubt that is the case since I cannot seem to fully burn CDRs too now.
Okay, another thought; could a corrupt HDD or a virus present cause burning failure?
|
|
doseyclwn
Newbie
|
14. April 2004 @ 16:39 |
Link to this message
|
Quote:
kay, another thought; could a corrupt HDD or a virus present cause burning failure?
Certainly, it could. Before all else fails, I would try a clean wipe and re-install of everything. Then try to burn. See what happens.
|
|
Advertisement
|
|
|
|
layeggs
Suspended due to non-functional email address
|
15. April 2004 @ 11:14 |
Link to this message
|
|
Glory, glory, glory!!! My problem has been resolved.
Okay, here's how I fixed it. BOUGHT a new DVD burner! :)
Yep, purchased the Pioneer 107D as recommended by Nephilim and others I knew who also swore by this great drive.
Burned the discs that was giving me grieve without any problems and backed up the files from the what was thought a corrupt and virus-infected HDD without rebuttle. Used the same media that I'd thought that was not cooperating with ease.
Have I flashed the new Pioneer drive yet? hmmmmm... taking the lead from Nephilim me thinks that "if it ain't broke then why try to fix it" with the 'hacked' firmware. That's the lesson (although costly) I learned from all this debacle.
So thanks to all those (Nephilim & doseyclwn) replied.
I'm now sure its the 'hacked' firmware (still in denial mode) :)
This message has been edited since posting. Last time this message was edited on 15. April 2004 @ 11:52
|
|
