Page 1 of 1

BenQ 1640 hangs DVD Identifier and DVDInfoPro

PostPosted: Thu Aug 04, 2005 4:55 pm
by mrslim
If I run DVD Identifier and try to identify a disc that's in the 1640, the program hangs. I can't even close it by shutting down the process in the Task Manager. I can click the button, but the program won't shut down. It even prevents me from opening other programs once this is happening.

So I downloaded DVDInfoPro to try that, but the results were the same.

I had a Plextor 2410 on the same IDE cable as the 1640. I disconnected it with no change in results. Interestingly, though, even as the only device on the chain, the BIOS identifies it as D1 at bootup. With both drives connected, the Plextor is D0 and with the Plextor disconnected, D0 is empty.

I should point out that I've yet to burn a DVD with this drive. Maybe it's time for a test burn just to see if it works as a burner at all. It reads fine.

Any thoughts on this?

PostPosted: Thu Aug 04, 2005 5:21 pm
by burninfool
1.Make sure to set it Master or Slave,don't use Cable Select.
2.Make sure the IDE connector is in all the way.
3.Update the firmware.
4.Buy a new IDE cable.
5.RMA the drive.

PostPosted: Thu Aug 04, 2005 5:48 pm
by mrslim
The drive didn't come with any documentation and I'm not seeing any on the BenQ website. There are three jumpers, the middle one is the current and factory selected one. Is that master, slave or cable select?

Another problem: I decided to use the Nero InfoTool to see what it came up with. As soon as I clicked to open the program, my computer rebooted.

PostPosted: Thu Aug 04, 2005 7:00 pm
by burninfool
Image

I thought of something else:
1.When booting up enter CMOS(delete,F12,etc) and make sure the drive is set to Auto for PIO and UDMA.
2.Download ForceASPI 1.7(search google).

PostPosted: Thu Aug 04, 2005 8:15 pm
by mrslim
Thanks, burninfool. A google search turned up a diagram that had the slave in the middle with the master to the right and CS at the left. In any case, I changed the jumper to the master setting at the right. This made the drive device 0 at boot, as might be expected.

Same problem, though.

Looking through the DVD Identifier menus, I switched on 'Only partially retrieve DVD + & - Media Code block.

That seems to have solved the problem.

I'll check the CMOS stuff. But I wonder what will happen because the 1640 is on a secondary controller that IDs the drive after the CMOS stuff has passed at boot. This suggests that I should try making the drive the slave on the controller where the hard drive is the master. I'll try that next.

PostPosted: Fri Aug 05, 2005 4:20 am
by RJW
Did you send a e-mail to dvd.identifier@scarlet.be.

Currenty there are some computer problems which delay current upgradeing.
Still we will try to see what we can do.

PostPosted: Fri Aug 05, 2005 10:46 pm
by mrslim
No, rjw, I didn't send a message, but at your urging, I will.

PostPosted: Wed Aug 10, 2005 7:15 pm
by mrslim
So it turns out that the source of the problems I mentioned above may be an incompatibility with Asus motherboards. I can't burn a DVD. It hangs Nero just like it did DVD Identifier.

I called BenQ support and they told me that the 1620 had compatibility problems with Asus motherboards that were never resolved and that this is likely the source of my problem here. That's disappointing.

I'll try getting and using a new IDE cable. Maybe the one I have isn't the 80 wire kind. I'll take a look.

Anyone have any knowledge of this incompatibility matter and suggestions other than to RMA the drive?

PostPosted: Wed Aug 10, 2005 7:25 pm
by Scour
Hello!

Maybe the IDE-driver is the problem. With Mainboard or which chipset have your MB?

PostPosted: Wed Aug 10, 2005 8:00 pm
by mrslim
motherboard: Asus A7V266-E
chipset: Via VT8366/A,VT8367 Apollo KT266/A,KT333 CPU to PCI Bridge

PostPosted: Wed Aug 10, 2005 8:26 pm
by Scour
mrslim wrote:motherboard: Asus A7V266-E
chipset: Via VT8366/A,VT8367 Apollo KT266/A,KT333 CPU to PCI Bridge


Have you tried to change the Via-IDE-drive to the windows-standard-ide-driver?

PostPosted: Thu Aug 11, 2005 2:12 pm
by mrslim
I changed the ide cable to an 80 wire one on a different controller and all is now well. At least it seems that way so far. Thanks for the help, everyone.