Comments

Kanst wrote on 3/14/2005, 1:40 PM
I'm use m/b on nVidia nForce 2 (ASUS A7N8X) and burn DVDs from Architect 2 on NEC 2500, 2510, now on 3520 without mistakes.
But at the last time I prefer NERO (now 6.6.0.8), because it now has a feature of change bittsetting of recordable DVDs to DVD-ROM.
jabloomf1230 wrote on 3/24/2005, 4:13 PM
DVDA 2.0 either recognizes a burner or it doesn't. Using the built-in Windows XP IDE driver to replace the NVidia IDE driver will not help unless you are extremely lucky. The only other thing you can try is to turn go to Options/Preferences/General and click on "Skip drive database; autodetect drive capabilities."

I wouldn't bother with the burning part anyway because it's not as good as Nero. I hope that this is all fixed in DVDA 3. We'll see in April.
jphouser wrote on 3/24/2005, 4:54 PM
Thanks for the reply - good idea - however alas it did not work.

Since my original post, I have switched to WindowsXP64 Beta - Build 3790.

Although I do not have empiracle data, my quess is that editing is about 25% to maybe even 40% faster in 64 bit.

My hardware is a MSI Neo Platinum MB, AMD64 3500, Gigabyte 6800GT AGP videocard, 2 GB of Corsair Pro memory and 4 WD Raptor drives striped in RAiD 0 which gives me 2 - 138 GB virtual drives.

I tried burning Using Nero 6.6 once, but lost my chapter markers. I haven't tried anything further - I can wait for the new Vegas 6 and the new DVD Architect 3, I quess.

Thanks again for the post.

Jay Houser
jabloomf1230 wrote on 3/25/2005, 3:16 PM
I'm sorry that it didn't work, but I'm not surprised, since that's been pretty much my experience with both recent Pioneer, NEC and LiteOn DVD burners.

I've been toying with installing Win64 in a double boot config (I have an AMD FX-55 based system), but I haven't read much about possible speed increases (either yeah or nay) with video software. I'm glad to see that you are getting good results with Win 64. I might work up my courage and install the most recent release candidate.

WedVidMan wrote on 3/26/2005, 4:29 AM
May be a silly question. How are your drives installed? As slaves or as master on the secondary IDE? I'm also running an Nvidia MB (A7N8X deluxe) with two DVD burners, both on the secondary IDE, one master, one slave. Both are recognized by V5 and DVDA2. Other data: AMD 2600+, WIN XP, RAID 0 with WD Raptor 70GB Drives, and 120GB HD on the Primary IDE.
jphouser wrote on 4/11/2005, 6:59 PM
Thanks for the info - I tried installing a fresh IDE hard drive along with my Sony DRU720 in both master and slave configurations - didn't recognise the DVD in any combination.

The only thing I haven't tried is reinstalling the Sony Vegas + Architect software.

I hope this is fixed in Vegas 6 - Architect 3.
goboo wrote on 4/12/2005, 7:21 AM
I have latest nVidia video card. Not recognizing the burner happened ONCE. I rebooted, came back into Architect2, and the burner (Sony 510) was shown! Loaded the file and burned ok. Rebooting did it !!??
jabloomf1230 wrote on 4/18/2005, 4:07 PM
Not that I use DVDA for burning, but DVDA3 doesn't fix this problem, at least on my NForce 4 computer. It doesn't matter whether I use my Pioneer DVR-A09 or my LiteOn 1633. I have the Microsoft IDE driver installed.
jorgensen wrote on 4/19/2005, 5:22 AM
You need to delete/rename all nvraid.sys files on the Windows drive.

I have found the nvraid driver also is loaded in Windows Safe Mode, as can be seen during boot.

Have also found SpectraLab doesn't like nForce RAID drives, so it is now time to goto back to a non-RAID system.
jabloomf1230 wrote on 5/2/2005, 2:43 PM
Well, here's something new. I just downloaded and installed a new firmware for my Pioneer DVR-A09 and now when I try to burn with DVDA3 I get this error:

Sony DVD Architect
Version 3.0 (Build 106)
Exception 0xC0000005 (access violation) READ:0x338 IP:0x59F75C
In Module 'dvdarch30.exe' at Address 0x400000 + 0x19F75C
Thread: Main ID=0xB88 Stack=0x12C000-0x130000
Registers:
EAX=0012c8b4 CS=001b EIP=0059f75c EFLGS=00010206
EBX=00000001 SS=0023 ESP=0012c6a0 EBP=0012c880
ECX=80004005 DS=0023 ESI=0012dfdc FS=003b
EDX=00000000 ES=0023 EDI=0012c87c GS=0000
Bytes at CS:EIP:
0059F75C: 8B 8A 38 03 00 00 89 08 ..8.....
0059F764: 8B 54 24 18 52 FF 15 F8 .TR...
Stack Dump:
0012C6A0: 000C02B2 00030000 + 902B2
0012C6A4: 77D54816 77D40000 + 14816 (USER32.dll)
0012C6A8: 00070318 00030000 + 40318
0012C6AC: 80004005
0012C6B0: 00000000
0012C6B4: 00000000
0012C6B8: 00010011 00010000 + 11
0012C6BC: 00000000
0012C6C0: 00000000
0012C6C4: 00000000
0012C6C8: 00000000
0012C6CC: 00000000
0012C6D0: 00000000
0012C6D4: 00000000
0012C6D8: 00000000
0012C6DC: 00000000
> 0012C884: 005A50A2 00400000 + 1A50A2 (dvdarch30.exe)
0012C888: 0012C8A8 00030000 + FC8A8
0012C88C: 0012C8B4 00030000 + FC8B4
0012C890: 0012C8A4 00030000 + FC8A4
0012C894: 000C02B2 00030000 + 902B2
> 0012C8C0: 77D48B26 77D40000 + 8B26 (USER32.dll)
> 0012C8DC: 77D488D1 77D40000 + 88D1 (USER32.dll)
> 0012C8E0: 005A5540 00400000 + 1A5540 (dvdarch30.exe)
0012C8E4: 000602C8 00030000 + 302C8
0012C8E8: 00000001
0012C8EC: 000C02B2 00030000 + 902B2
0012C8F0: 04D08FC8 049D0000 + 338FC8
> 0012C8F4: 005A0279 00400000 + 1A0279 (dvdarch30.exe)
0012C8F8: 000C02B2 00030000 + 902B2
0012C8FC: 04D08FC8 049D0000 + 338FC8
0012C900: 000C02B2 00030000 + 902B2
0012C904: 00000000
> 0012C908: 77D488A6 77D40000 + 88A6 (USER32.dll)
> 0012C90C: 005BB240 00400000 + 1BB240 (dvdarch30.exe)
0012C910: 000C02B2 00030000 + 902B2
0012C914: 0000004E
0012C918: 00000000
0012C91C: 0012CC08 00030000 + FCC08
> 0012C924: 005BB200 00400000 + 1BB200 (dvdarch30.exe)
> 0012C930: 77D48734 77D40000 + 8734 (USER32.dll)
> 0012C944: 005BB200 00400000 + 1BB200 (dvdarch30.exe)
- - -
0012FFF0: 00000000
0012FFF4: 00000000
0012FFF8: 0066BB18 00400000 + 26BB18 (dvdarch30.exe)
0012FFFC: 00000000

At least that's progress of some sort, since previously the burner was not recognized at all.
jabloomf1230 wrote on 5/25/2005, 11:40 AM
Just an update. If anyone with an NForce motherboard is still having trouble after disabling RAID or for some reason you cannot disable RAID, SONY will provide you with an update to the DVDA3 file sfspti.dll, which will at least allow you to write an ISO image to your hard drive.
tjburton wrote on 6/15/2005, 7:35 AM
Unfortunately this new .dll does not a fix for all. I have recieved the .dll and still have no drives on any of my Sony software. I'm told that the Sony developers are working on this issue, but have not heard anything in a week or so...

Tim
jabloomf1230 wrote on 6/15/2005, 2:53 PM
It is the same DLL that is included in DVDA version 3.0b (Build 117). It does not allow DVDA to recognize your drive. It only allows you to "burn" an ISO image to your hard disk. As it was stated previously in this thread, if you have an NForce motherboard, try disabling/removing all RAID-related drivers. That, of course, does you no good if you have any RAID hard drives.

BTW, the DLL appears to control the interface with the Windows XP built-in CD/DVD read/write routines, SPTI (SCSI Pass-Through Interface). The authors of DVDA must have had an interesting approach to writing the DLL, since I have yet to have any other DVD-burning software fail to recognize my DVD drives. DVDA is unique in that regard, at least on my PCs.