System lockup on capture card install?

[orion404]

Hello -
Am still trying to install the drivers for the ATI-TV Wonder VE card but still running into system freezes and lockups.

Have uninstalled all previous related drivers and tried the latest from ATI as posted here, the 'generic' drivers from SourceForge, MS DirectX upgrade and all to no avail.

Beginning to think there's an internal conflict on my system. Perhaps related to IRQs, DLLs, DRVs, or VXDs. But until my system can recognize the card that's installed, very difficult to eliminate the possibilities.

Suggestions of a methodical way to go thru the possibilities? Reinstall Wdws OS 'NOT' an option, thank you.
I'm running 733Mhz Celeron, WdwsME, 192Mb RAM, & GIGs of H/D.

Thank you.[/b]

[snowmoon]

Diag 101...

- Update all critical drivers ( VIA 4-1, MB firmware, raid controller, ... )

- Try ALL availible PCI slots

- Try removing unessesary PCI card and tyr it in their slot. Start with communications like modem or network, firewire, usb, sound.

If that didn't get you SOMEWHERE then it sounds like you are SOL, mabye even a bad card.

[fmctm1sw]

Try ALL availible PCI slots

That's what I think it is. I have a LONG explanation of what I had to do to get my wintv card to work. If you can't get it to work past back and I'll explain....

[orion404]

Have tried all 3 of my PCI slots and confirmed latest driver updates for system and still locking up at ATI driver install. Gets to the final screen and then it freezes.

[snowmoon] reports a long workaround that worked for him/her so if he/she would like to post that here, perhaps others could benefit.

Thanks !

[Nelson37]

over at rage3d.com they list a trick for putting a HWdetect flag in the install.ini file, this may solve your problem. They also have good detailed installation procedures.

[orion404]

The HWdetect 'ini tweak sounds intriguing and I'd like to give it a try for lack of anything better. Looked all thru the rage3d site but could not find a reference to the item mentioned by [Nelson37]. Perhaps you could give me a bit more info on the location?

Thank you.

[fmctm1sw]

Take a look your IRQ settingsfor each device. I am unfamiliar with windows ME but in 98 (like ME?) it's under:

START>SETTINGS>CONTROL PANEL>SYSTEM

Once there, go to device manager, highlight the "computer" entry and right click and click on "properties."

Your card should not share the same IRQ as anything else. My install program said my wintv shared an IRQ with the AC 97 integreated audio controllr and that was "OK since both are PCI devices." I say bullsh*t. IT DIDN'T WORK. That's a good starting point. Let us know what you see...

[fmctm1sw]

Your card should not share the same IRQ as anything else.

Of note (sorry), you may see "IRQ holder for PCI steering" assigned the same IRQ. Or entries regarding your disk drives and drive controllers.

[orion404]

Tried the IRQ conflict thing and that led me to Microsoft's Knowledge Base and to a topic on ACPI which is a Windows system setting that permits sharing of IRQs without causing lockups or freezes. Windows assigns the IRQs and in WinME, does not permit a 'manual' reassignment.

They're not very clear, however, on which devices, if any, will cause a lockup if sharing an IRQ or what the workaround would be.

But since my machine does not 'see' the ATI caputure card (drivers not installed), I'm not able to work with IRQs to any extent for purposes of troubleshooting this problem.

[fmctm1sw]

I think I disabled ACPI. I'll have to check when I get home. But yes, a lot is not very clear, especially in my motherboards manual (go figure).

[Nelson37]

The info on Rage3d is in the forums, they also had detailed how-to on the TV wonder.

[Bel]

Even if the drivers are not installed, the card should be "seen" in the control panel. I think it says something live multimedia video controller and there will be a yellow exclamation point indicating that it is not working and the drivers are not installed. If you do not see this, there is something wrong with the plug n' pray on the card or bios. Most likely the card. If this is happening exchange it and see if a new one helps.

The other thing to do, if you're up for it, is a fresh install with Windows. Never hurts, almost always helps. But if control panel doesn't see the card at all, most likely the card is shot.

[orion404]

Hmmmm......Control Panel applet? Never thought to look there. We'll sure give it a shot.

Also, will try to track down that web page with the HWDetect 'ini tweak and will post back here if found.

[orion404]

Finally got the card installed and I think, but not sure, the drivers as well. The device does show up under Device Mgr and there is no yellow exclamation mark or question mark.

But when I launch Virtual Dub and try to capture AVI file from VCR, Virtual Dub responds 'Cannot locate any capture device'. Similar responses from other editors I've got loaded.

Installed the latest drivers from ATI, the ones labeled
tvw-pci-ve-mmc-7-6-0-1-b
which includes the MMC program and latest drivers. Then tried loading the SourceForge drivers suggested in another forum and that went thru as well. Still, am unable to have the software recognize the 'capture device'.

Suggestions?

[Nelson37]

you need the WDM wrapper.

[Bel]

Virtualdub SHOULD recognize the Sourceforge drivers (at least it does with mine), if they're not I don't really have any advice... Did you make sure and uninstall the ATI Drivers before installing the Sourceforge drivers? Also, I would delete the entry of your capture card entirely from device manager as well. Just highlight and press delete. Uninstall all of the ATI Software, then install the Sourceforge drivers.

If you want to stick with the ATI drivers, you can go with the WDM Wrapper, but most people don't have great results with that from what I've read, personally I've never tried them.

[orion404]

Finally got rid of the system lockups. Went and exchanged for another card as suggested here. Go figure!

Installed with the bundled software/drivers on CD and went thru without a hitch. Now have different issues but will open a new thread for those.

Thanks to all who chipped in!