Fang

May 19, 2010

Because that's what the driver is reporting. Haven't we been through this a million time already?! x64 OS's often report the BusType as RAID, SCSI, ATAPI (none of which are common on x86 - they typically just use ATA), I guess that's just how the drivers are designed/built.

The drivers are just a means of getting data from and sending data to the drive. They shouldn't have any effect on the actual outcome - apart from the commands being totally blocked - which is what normally happens with 'format' command and the advanced/vendor unique ones used for bitsetting.

No, we haven't been through this even once let alone a million times! I've not heard of this but thanks for the info anyway. It clears up a lot of things.

As for "The drivers are just a means of getting data from and sending data to the drive" if they are corrupt or incorrect from MS or the drive manufacturer couldn't that cause the problems I'm having? Maybe a FAQ on burners and OS's would be helpful?

May 19, 2010

Are you expecting Device Manager to list them in the 'RAID' section or something?

The value ImgBurn displays is just taken from the 'BusType' field in the STORAGE_ADAPTER_DESCRIPTOR descriptor which is returned by a call to DeviceIoControl(IOCTL_STORAGE_QUERY_PROPERTY).

The OS *shouldn't* make any difference, after all, the software is talking to the drive directly. If the software submits a 'write' command then I'd expect a 'write error' return code to have come from the drive itself, not the OS.

By all means boot up an Ubuntu Live CD or something and test the burner that way.

Donloading the Ubuntu Live CD now. It sounds like a good CD to have around. Thanks for the info on it.

Why would imageburn report the drives as RAID when RAID has never been enabled? I'm thinking that because the drives are reported as being RAID that is why I'm having problems burning.

May 19, 2010

I 15:07:42 -> Drive 1 - Info: AlViDrv BDDVDROM 3.2c (J:) (SCSI)
I 15:07:42 -> Drive 2 - Info: HL-DT-ST DVDRAM GH24LS50 YP01 (D:) (RAID)

I 15:07:42 -> Drive 3 - Info: Optiarc DVD+-RW AD-7200S 102A (F:) (RAID)

I 15:07:42 Found 2 DVD±RW/RAMs and 1 BD-ROM/HD DVD-ROM!

It certainly knows it's found 2 burners so I don't see why it wouldn't show up.

It just looks like the drive is having trouble burning to some of the discs. I never rate rewritables very highly, they often fail.

What I'd do is try with some decent Verbatim / Taiyo Yuden media. (If possible, DVD+R Verbs or DVD-R Taiyo Yuden)

For CD's, I'd only ever use Taiyo Yuden now.

This doesn't explain why the burner worked just fine with diff media brands for quite some time or why imageburn sees the burners as RAID while device manager doesn't report them as RAID. I've had the same problem with Verbatim disk, both DVD-R and CD-R. I really believe it's something in windows 7, posiably caused by a windows update?

May 18, 2010

Can you post a log from a DVD burn please?

Try as many different DVD formats as you own. (DVD-R, DVD-RW, DVD+R, DVD+RW etc)

You could try uninstalling everything nvidia related from 'programs and features' in control panel and then uninstalling the controllers (inc the driver if that's an option) from within Device Manager and rebooting.

Uninstalled everything Nvidia ask you suggested and it was reinstalled on boot. DVD drives still seen as RAID in imageburn but not in device manager.

Here are the logs from my burns with the disk that I have. I also tried a couple of imation DVD-RWs and a Sony DVD-RW but the optiarc drive wouldn't see them, although they work fine on my xp system. Another note of interest is that imageburn doesn't see the Drive 2 - Info: HL-DT-ST DVDRAM GH24LS50 YP01 (D:) (RAID) for writing noted in the log. Should imageburn be reinstalled to see it, as I just installed that drive.

OKay, here's the logs in order in burns:

CD-RW burn:

I 15:07:42 ImgBurn Version 2.5.1.0 started!

I 15:07:42 Microsoft Windows 7 Ultimate x64 Edition (6.1, Build 7600)

I 15:07:42 Total Physical Memory: 6,288,868 KB - Available: 4,747,908 KB

W 15:07:42 Duplex Secure's SPTD driver can have a detrimental effect on drive performance.

I 15:07:42 Initialising SPTI...

I 15:07:42 Searching for SCSI / ATAPI devices...

I 15:07:42 -> Drive 1 - Info: AlViDrv BDDVDROM 3.2c (J:) (SCSI)

I 15:07:42 -> Drive 2 - Info: HL-DT-ST DVDRAM GH24LS50 YP01 (D:) (RAID)

I 15:07:42 -> Drive 3 - Info: Optiarc DVD+-RW AD-7200S 102A (F:) (RAID)

I 15:07:42 Found 2 DVD±RW/RAMs and 1 BD-ROM/HD DVD-ROM!

I 15:10:56 Operation Started!

I 15:10:56 Source File: G:\Burn Test\memtest86-3.5.iso\Memtest86_3.5.iso

I 15:10:56 Source File Sectors: 556 (MODE1/2048)

I 15:10:56 Source File Size: 1,138,688 bytes

I 15:10:56 Source File Volume Identifier: CDROM

I 15:10:56 Source File File System(s): ISO9660 (Bootable)

I 15:10:56 Destination Device: [4:0:0] Optiarc DVD+-RW AD-7200S 102A (F:) (RAID)

I 15:10:56 Destination Media Type: CD-RW (Disc ID: 97m32s11f, Prodisc Technology Inc.) (Speeds: 4x)

I 15:10:56 Destination Media Sectors: 335,098

I 15:10:56 Write Mode: CD

I 15:10:56 Write Type: SAO

I 15:10:56 Write Speed: 4x

I 15:10:56 Lock Volume: Yes

I 15:10:56 Test Mode: No

I 15:10:56 OPC: No

I 15:10:56 BURN-Proof: Enabled

I 15:10:56 Write Speed Successfully Set! - Effective: 706 KB/s (4x)

I 15:10:57 Filling Buffer... (40 MB)

I 15:10:57 Writing LeadIn...

W 15:12:37 Failed to Write Sectors 288 - 319 - Reason: Write Error

W 15:12:37 Retrying (1 of 20)...