Comments

Jayster wrote on 5/4/2006, 2:34 PM
This is quite odd. I have an Asus 1608-P2S which is a reselling of the Pioneer-110. DVD Architect (version 3) does see my drive and works with it. My mobo is an Asus A8N32-SLI Deluxe which also uses nVidia chipsets. Not sure if it's the same chipsets, though. If you haven't already, you should probably update the firmware on all your hardware (mb and burner).
Yoyodyne wrote on 5/4/2006, 3:26 PM
Thanks a ton jayster - I will give it a shot as soon as I can.
Wes C. Attle wrote on 5/4/2006, 4:49 PM
I am on an nForce 4 Pro chipset. I had the same problem at one time. It was resolved by updating to the later DVDA 3.0c version and/or installing newer chipset drivers from nvidia.com. I can't remember which solved the problem. The problem and solution are documented somewhere in the forums!
rmack350 wrote on 5/5/2006, 9:11 AM
I'd expect it to be the firmware on the burner before linking it to your chipset.

DVDa has been a little spotty in it's burner support in the past.

Rob Mack
JohnnyRoy wrote on 5/5/2006, 11:59 AM
> I'd expect it to be the firmware on the burner before linking it to your chipset.

Nope. It has nothing to do with the burner. It has to do with Sony applications not working with the nForce4 chipset. None of my Sony applications could see any of my three DVD/CD drives whether they were burners or not. I could not rip from CD or anything.

It was resolved by contacting Sony and getting new DLL’s for all of the Sony products (since none of my other burning applications had a problem with this chipset). Since then I believe Vegas 6.0d has the fix. The latest DVD Architect might not. So make sure you have the latest versions of all the Sony products and if any of them still don’t work, contact Sony for new DLL’s.

~jr
rmack350 wrote on 5/5/2006, 2:28 PM
Wow. Didn't know that was the reason.

You're forced to learn something new every day! ;-)

Rob