Registered: Jul 2000
Location: Minneapolis, MN
Posts: 10178

hardware conflict

Device type: 1394 Bus Controller
Manufacturer: Texas Instruments
Hardware version: 000

Device Status:
This device is not working properly because Windows cannot find the file (wn1394.vxd) that loads drivers for this device (Code 8.)


My first thought was to search for wn1394.vxd on yahoo. All the matches i found were for video devices. I cant reinstall the device because i dont know what it is. what to do?

Report this post to a moderator | IP: Logged

Registered: Aug 2000
Location: b0ulder
Posts: 5126

98/ME/2k

search through the cab files (ie: win98 dir on the cd) using the "containing text:" field instead of "Named:." if this is too general lemme know.

NT/95 doesn't have that cool containing text option.

------------------------
Titleist

Report this post to a moderator | IP: Logged

Registered: Aug 2000
Location: b0ulder
Posts: 5126

oh, and when you find the cab it's in open it and copy the file to the system dir.

------------------------
Titleist

Report this post to a moderator | IP: Logged

Registered: Jul 2000
Location:
Posts: 5526

quote:

---

Originally posted by memdink:
NT/95 doesn't have that cool containing text option.

---

NT does. I even looked to make sure. Fairly good options in "find"

Report this post to a moderator | IP: Logged

Registered: Aug 2000
Location: 54.60°N 5.70°W
Posts: 1950

The file you need is linked from this page and this is the direct link to the .zip file. I think it is only meant for Win95 use, but you may want to give it a try if you are stuck.

As for why a bus controller needs a video driver ... no clue. 'Microsoft' should suffice as an answer.

------------------------
and so on ...

Report this post to a moderator | IP: Logged

Registered: Nov 2000
Location:
Posts: 5131

That be a firewire controller hoss.

As to why it uses a video file, well...Pangloss is right. I'm still trying to figure out why the Win95.950B USB update uses scandisk as an engine for the Serial Bus drivers.

Should be as simple as finding the correct drivers for your IEEE 1394 controller and reinstalling them.

How about some more info. Did it work before, and this just suddenly appeared? Did you just notice this after a fresh install of Windows? Did you just install a new M/B? Does the PC even have a firewire port? (I've seen stranger things happen) What's the whole deal?

------------------------
Sanity is the playground for the unimaginative.

[This message has been edited by BnB (edited 11-15-2000).]

Report this post to a moderator | IP: Logged

Registered: Jul 2000
Location: Minneapolis, MN
Posts: 10178

Bnb, my computer recently started freezing alot so i went and checked the device manager and found the error detailed above. I dont know when this happened, how the file got deleted, how long its been this way, or if its even causing the problems. I also dont know what a 'firewire' port is.

Im an imbucile when it comes to hardware. memdinks suggestion didnt work, but i didnt spend a whole lot of time on it and im gonna try panglosses suggestions when i get home.

Report this post to a moderator | IP: Logged

Registered: Jul 2000
Location: Minneapolis, MN
Posts: 10178

memdink that file is not on the win98 disk. i searched for files named *.cab conatining wn1394.vxd and got no results.

Pangloss, i copied that file to my system directory and rebooted. obviously its the wrong file:

Windows stopped responding while attempting to start this device, and tehrefore will never attempt to start this device again (Code 11.)

Im willing to entertain more suggestions...


(i also searched microsofts site and msdrivers.com)

[This message has been edited by Dingle (edited 11-15-2000).]

Report this post to a moderator | IP: Logged

Registered: Nov 2000
Location:
Posts: 5131

Dingle.

Is this a PC you built or bought? Either way somewhere in the software you recieved with the PC should be those drivers.

First, Look, see if you can find the drivers...keep an eye out for IEEE, 1394, or firewire. If you can't find them you can still try these things.

Also I'm assuming your using a Win9x op system.

Win98
Start tapping the F8 key during bootup. You should see a Win98 Startup Menu.
Select the option that says Command Prompt Only. Type "scanreg /restore"
and press enter. Select a date prior to the problem occurring and press
Enter.

If that doesn't work, or you have Win95 for some weird fucking reason.

Start tapping the F8 key during bootup. You should see a Win98 Startup Menu. Select #3 Safe Mode. Go to Device Mangler and rip out the offending device. Reboot and let windows redetect it by itself. It may POSSIBLY find the correct INF file and drivers and reinstall itself properly.

Either way, let me know the results.


------------------------
Sanity is the playground for the unimaginative.

Report this post to a moderator | IP: Logged

Registered: Jul 2000
Location:
Posts: 7236

I may be a mod, but I am shit with hardware. I have no idea.

As a guess though, have you tried booting in safe mode, this should ignore video drivers etc. Try reinstalling all of your devices one at a time from there maybe.

------------------------
sp00ky
---------------------------
'everyone I've loved or hated always seems to leave'

I quote, therefore I am - Spooky

Report this post to a moderator | IP: Logged