Jump to content

Recommended Posts

Posted

Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2)

PIONEER DVD-RW DVR-111D 1.23 (D:) (SCSI)

 

Burns regular dvd images just fine.. but trying to get a dual-layer burned properly just doesn't work anymore.

 

I have made 12 successful burns (DVD+DL) in a row using this burner on the hardware, then all of a sudden it won't complete a burn. The burner stops writing, and the speeds drop to 0. No error messages, no flashing on the burner, it just stops.

 

Using Memorex AND Verbatim media (So don't tell me it is a media problem).

 

===============================================

Filter Driver Load Order - ImgBurn v2.2.0.0

===============================================

 

Upper Device Filter: redbook

Upper Class Filter: [None Found]

Device: CD/DVD-ROM Device

Lower Class Filter: PxHelp20

Lower Class Filter: pfc

Lower Device Filter: imapi

 

Filter Name: redbook

File Name: C:\WINDOWS\system32\DRIVERS\redbook.sys

File Version: 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)

File Description: Redbook Audio Filter Driver

Product Name: Microsoft? Windows? Operating System

Product Version: 5.1.2600.2180

Company Name: Microsoft Corporation

Copyright: ? Microsoft Corporation. All rights reserved.

 

Filter Name: PxHelp20

File Name: C:\WINDOWS\System32\Drivers\PxHelp20.sys

File Version: 3.00.41a [3.0.41.0]

File Description: Px Engine Device Driver for Windows 2000/XP

Product Name: PxHelp20

Product Version: [2.0.0.0]

Company Name: Sonic Solutions

Copyright: Copyright ? Sonic Solutions

 

Filter Name: pfc

File Name: C:\WINDOWS\system32\drivers\pfc.sys

File Version: 2, 5, 0, 204 [2.5.0.204]

File Description: Padus® ASPI Shell

Product Name: Padus® ASPI Shell

Product Version: 2, 5, 0, 204 [2.5.0.204]

Company Name: Padus, Inc.

Copyright: © Padus, Inc. 1999-2001. All rights reserved.

 

Filter Name: imapi

File Name: C:\WINDOWS\system32\DRIVERS\imapi.sys

File Version: 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)

File Description: IMAPI Kernel Driver

Product Name: Microsoft? Windows? Operating System

Product Version: 5.1.2600.2180

Company Name: Microsoft Corporation

Copyright: ? Microsoft Corporation. All rights reserved.

 

Guess I should just say HELP!

Posted

Quiky, Since you have had good burns I would say its not a filter driver, although you could ditch the pfc ( padus) driver with no harm done. Memorex medium is iffy, but the Verbs are great medium.

 

Can you post a complete log of the failed burns...... Img>help>imglogs. This will help us see whats going on thats making the burns fail all of a sudden. :)

 

There is also a firmware update for your drive.......... 1.29...... your using 1.23. www.rpc1.org

Posted (edited)
Can you post a complete log of the failed burns...... Img>help>imglogs. This will help us see whats going on thats making the burns fail all of a sudden. :)

The logs don't get written for the failed burns.. imgburn acknowledges the cancel, but nothing happens. Program wont close, it just sits there waiting for the burner to stop. I have to hard-reset the system to recover, but no log for the burn is there.

 

Updating the drive firmware now..

Edited by Quiky
Posted

after the firmware update, burn the same image again using the verbatim discs......... just a hunch that the failed burns started when you switched to the memorex media. Force of habit asking for logs as they show the media MID code and other pertinent info........ >_<

Posted

This time it completely crashed- imgburn locked up 20 seconds after the burner stopped writing (still spinning though). 1:10 through the burning. No other applications will launch after imgburn hangs.

 

(ran out of verbatims making coasters, but I did 15 memorex discs in a row with 100% success before)

 

(typed by hand because copy+paste doesn't work when the program crashes)

Burner has 1.29 firmware on it now..

Media Type: DVD+R DL (Disc ID: RITEK-D01-01) (Speeds: 2.4x)

Destination Media Sectors: 4,173,824

Write Mode: DVD

Write Type: DAO

Write Speed: 2.4x

Link Size: Auto

Test Mode: No

BURN-Proof: Enabled

Optimal L0 Data Zone Capacity: 1,913,760

Optimal L0 Data Zone Method: Copied From Original Disc

Filling Buffer... (20MB)

Writing LeadIn...

Writing Image...

Writing Layer 0... (LBA: 0-1913759)

<end>

Posted

Media info for the memorex;

 

PIONEER DVD-RW DVR-111D 1.29 (SCSI)

Current Profile: DVD+R DL

 

Disc Information:

Status: Empty

Erasable: No

Free Sectors: 4,173,824

Free Space: 8,547,991,552 bytes

Free Time: 927:32:74 (MM:SS:FF)

Supported Write Speeds: 2.4x

 

DVD?R DL Boundary Information:

L0 Data Zone Capacity: 2,086,912

Changeable: Yes

 

Physical Format Information (ADIP):

Disc ID: RITEK-D01-01

Book Type: DVD+R DL

Part Version: 1

Disc Size: 120mm

Maximum Read Rate: Not Specified

Number of Layers: 2

Track Path: Opposite Track Path (OTP)

Linear Density: 0.293 um/bit

Track Density: 0.74 um/track

First Physical Sector of Data Area: 196,608

Last Physical Sector of Data Area: 16,580,607

Last Physical Sector in Layer 0: 2,283,519

 

Physical Format Information (Last Recorded):

Disc ID: RITEK-D01-01

Book Type: DVD+R DL

Part Version: 1

Disc Size: 120mm

Maximum Read Rate: Not Specified

Number of Layers: 2

Track Path: Opposite Track Path (OTP)

Linear Density: 0.293 um/bit

Track Density: 0.74 um/track

First Physical Sector of Data Area: 196,608

Last Physical Sector of Data Area: 16,580,607

Last Physical Sector in Layer 0: 2,283,519

Posted

I'm still thinking its those damn Riteks, even though you did say you've had successful burns with them. Did you delete that pfc filter? On a hunch, try deleting Imgburn and re-downloading a fresh copy from the site here. I'm sure one of the other guys will be along and have other thoughts on your problem. :)

Posted
I'm still thinking its those damn Riteks, even though you did say you've had successful burns with them. Did you delete that pfc filter? On a hunch, try deleting Imgburn and re-downloading a fresh copy from the site here. I'm sure one of the other guys will be along and have other thoughts on your problem. :)

I have had wonderful burns with the riteks... I did delete the pfc filter, and tried both 2.1.0.0 and 2.2.0.0.

Posted

I don't rate the Ritek DL's I am afraid they are too inconsistent for me, check out Drives/Media forums for scans with that media. That said if you have been problems with the Verbs as well that sounds odd - did you manage to burn a new Verb DL after the firmware update to 1.29 ? I have a Pioneer DVR-111 with 1.29 and it loves the Verbs...

Posted

The lockups are due to I/O problems lower down the chain. ImgBurn only ever waits for the I/O call to complete. If it doesn't it just sits there waiting. That's the nature of the 'DeviceIoControl' windows API and is out of my hands.

 

Even if you could force ImgBurn to close, the I/O subsystem is still going to be in the waiting/hung state, so it wouldn't do you any good and you'll still have to reboot.

 

Ritek DL media, regardless of what you think, is still useless compared to Verbatim DL media.

 

I also noticed your drive is showing up as a 'SCSI' device, which obviously it's not.

 

It usually does that for 1 of 2 reasons:

 

1. It's on a 3rd party IDE controller, not the proper chipset one.

2. You've got weird drivers installed.

 

You want to avoid both of those. The only 3rd party controllers that work properly are ones that use a Silicon Image 680 chipset or an ITE8212 chipset (with appropriate firmware). With anything else, you're taking risks every time you try and access the drive.

Posted
1. It's on a 3rd party IDE controller, not the proper chipset one.

2. You've got weird drivers installed.

 

You want to avoid both of those. The only 3rd party controllers that work properly are ones that use a Silicon Image 680 chipset or an ITE8212 chipset (with appropriate firmware). With anything else, you're taking risks every time you try and access the drive.

Using the onboard IDE channel(only one) on my Gigabyte GA-965G-DS3, which has the ide ports set to ide mode.

 

I removed the "raid controller", which actually turns out to be a JMicron IDE controller for the system(which is required to use the ide devices).. but it worked fine for numerous burns before.

 

Trying to update the drivers now, but if it fails, then I guess I need to use a IDE->USB or stick the drive in another system.

Posted

Yeah, Intel were far too quick to get rid of IDE. Fair enough people haven't really used IDE for HDDs in a while, but SATA optical drives are still pretty rare and never seem to work as well as PATA ones.

 

That's one of the reasons I went for the 975 chipset rather than 965. That way, even if my new SI680 or ITE8212 cards didn't work properly, I'd at least be able to run 2 drives. As it turns out, I can now have 6 in my PC at the same time! Makes my life much easier :)

Posted

Thanks for those chewy.. cd-r test burn was successful... testing +DL now;

 

I 19:59:03 ImgBurn Version 2.2.0.0 started!

I 19:59:03 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2)

I 19:59:03 Total Physical Memory: 1,046,956 KB - Available: 734,832 KB

I 19:59:03 Initialising SPTI...

I 19:59:03 Searching for SCSI / ATAPI devices...

I 19:59:03 Found 1 DVD?RW!

I 19:59:31 Operation Started!

I 19:59:31 Source File: C:\rc22.dvd

I 19:59:31 Source File Sectors: 3,697,696 (MODE1/2048)

I 19:59:31 Source File Size: 7,572,881,408 bytes

I 19:59:31 Source File Volume Identifier: rc22

I 19:59:31 Source File Implementation Identifier: Daikin U.S. Comtec Lab

I 19:59:31 Source File File System(s): ISO9660, UDF (1.02)

I 19:59:31 Destination Device: [0:0:0] PIONEER DVD-RW DVR-111D 1.29 (D:) (ATA)

I 19:59:31 Destination Media Type: DVD+R DL (Disc ID: RITEK-D01-01) (Speeds: 2.4x)

I 19:59:31 Destination Media Sectors: 4,173,824

I 19:59:31 Write Mode: DVD

I 19:59:31 Write Type: DAO

I 19:59:31 Write Speed: 2.4x

I 19:59:31 Link Size: Auto

I 19:59:31 Test Mode: No

I 19:59:31 BURN-Proof: Enabled

I 19:59:31 Optimal L0 Data Zone Capacity: 1,913,760

I 19:59:31 Optimal L0 Data Zone Method: Copied From Original Disc

I 19:59:54 Filling Buffer... (20 MB)

I 19:59:58 Writing LeadIn...

I 20:00:00 Writing Image...

I 20:00:00 Writing Layer 0... (LBA: 0 - 1913759)

I 20:19:54 Writing Layer 1... (LBA: 1913760 - 3697695)

I 20:38:35 Synchronising Cache...

I 20:38:36 Closing Track...

I 20:38:42 Finalising Disc...

I 20:41:00 Image MD5: 5e9b579fe663d9d9c30b23d24c936d02

I 20:41:00 Operation Successfully Completed! - Duration: 00:41:29

I 20:41:00 Average Write Rate: 3,195 KB/s (2.3x) - Maximum Write Rate: 3,385 KB/s (2.4x)

 

It worked! Fuck Gigabyte and their non-working drivers! Hooray!

Posted

I would have killed off the sonic while I was at it but one step at a time

 

at least you didn't have any more good disks to waste

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.