View Full Version : 1394 unable to start
zipp51
July 5th, 2003, 07:10 AM
I have the Asus A7N8X Deluxe mobo.It has 1394 firewire add on header supplied by manufacturer.From the day I set this system up my device manager had all working hardware.For some reason which I haven't worked out and can't seem to figure out, a yellow asterik appears next to my 1394 entree.Says that this device cannot start.I have uninstalled and let windows reinstall the drivers.Have installed the latest 4 in 1 N Vidia drivers in case an update was in there.Still have the asterik.I shouldn't worry too much because I don't have any firewire hardware to use,but still it puzzles me that it becomes unable to start.Anyone have a hunch.:confused:
zErO
July 5th, 2003, 07:32 AM
First of all check your cmos settings to ensure that you have this device enabled.
And zipp51 as you have a NForce board you require the NForce driver installation, its not called 4 in 1...thats for VIA chipsets. Either go to ASUS and get version 2.xx or even try Nvidia for a more up to date chipset drivers
zipp51
July 5th, 2003, 07:49 AM
Originally posted by zErO
First of all check your cmos settings to ensure that you have this device enabled.
And zipp51 as you have a NForce board you require the NForce driver installation, its not called 4 in 1...thats for VIA chipsets. Either go to ASUS and get version 2.xx or even try Nvidia for a more up to date chipset drivers
Actually Zero they are called all in one sorry for the confusion.Got the latest and installed but still nada.I'll check the setting in bios thanks.
FastGame
July 5th, 2003, 15:04 PM
You can try this ASUS firewire patch (ftp://ftp.asuscom.de/pub/ASUSCOM/TREIBER/CHIPSATZ/NVIDIA/1394_filter.zip), if that doesn't work then maybe this Guide (http://www.nforcershq.com/forum/viewtopic.php?p=150240) will help.
Big Booger
July 5th, 2003, 16:57 PM
FG,
Do you own stock in Asus?
:D
FastGame
July 5th, 2003, 17:50 PM
Originally posted by Big Booger
FG,
Do you own stock in Asus?
:D
No, phishhead & Stripe bought me out :p
ABIT for now :D
zipp51
July 5th, 2003, 20:26 PM
Originally posted by FastGame
You can try this ASUS firewire patch (ftp://ftp.asuscom.de/pub/ASUSCOM/TREIBER/CHIPSATZ/NVIDIA/1394_filter.zip), if that doesn't work then maybe this Guide (http://www.nforcershq.com/forum/viewtopic.php?p=150240) will help.
The firewire patch would not start.Is this patch for Linux?Probably will flash to 1004 latest bios flash.Why would it work for a while then quit?(the firewire)
FastGame
July 6th, 2003, 02:32 AM
No the patch is suppose to be for Win XP, are you running Linux ?
zipp51
July 6th, 2003, 11:42 AM
Originally posted by FastGame
No the patch is suppose to be for Win XP, are you running Linux ?
Running XP exe file might be corrupted.Also flashed my bios to 1004 version and still get code 10.
Edit; Problem solved.Flash bios to latest version,shut down,unplug power supply,remove battery,clear cmos,reinstall battery,reset parameters,plug in fire up and she works again.:rolleyes: I forgot that after a bios flash always do this.Thanks for everyones input.
Devil2000
July 16th, 2003, 18:17 PM
I had the same error, the battery removal and replace also fixed my problem thx.
Thor
July 16th, 2003, 18:22 PM
Does this have to be done every time the/any bios get flashed?
zipp51
July 16th, 2003, 20:59 PM
Originally posted by Thor
Does this have to be done every time the/any bios get flashed?
It has been my experience that at least the power cord and jumper has to be removed and then replaced in order to clear the cmos setup.But I have been removing the battery for extra measure because it was stressed in a recent article on bios flashing.
cash_site
July 17th, 2003, 01:28 AM
Yep, it is highly recommend to clear the CMOS after flashing to completely remove traces of the old BIOS.
As per Zipp, its a good idea to remove cord and clear battery jumper.
Thor
July 17th, 2003, 15:49 PM
Thank you. I had not known that. I've flashed the bios many times and never had a problem but I will do this in the future.
phishhead
August 23rd, 2003, 19:32 PM
hey guys having the same issues as zip had...getting error unable to start...so far this is what I've did:
removed in device manager and tried to reinstall manually
clear cmos reboot no go
shutdown and disabled it the bios and unplugged from mobo then restarted and shut down again enabled and restarted
tried the toggle app get error could not start.
I'm at a lost and yes I need it gonna have some upset soccer parents if I cant burn these videos.
tried the xp drivers and the nvidia still get error that it can not start. shows in device manage but with the yellow exclaimnation point.
I have the 1004 uber bios so thats up to date. can remember when I last used it but havent really tweaked anything for a while. do you guys know of a service that needs to be running for firewire, because I checked the services and none seem to be related.
zipp51
August 24th, 2003, 00:47 AM
Did you take the battery completely out,clear cmos with jumper,reinstall battery,plug in fire up,reset parameters?If not try that in that order.
If this doesn't work you can reflash the bios if it will let you and then do those steps.Sorry to hear about the pickle your in,hope that helps.
phishhead
October 24th, 2003, 13:19 PM
well it happened again, went to pull some more movies off the camera and low and behold damn firewire will not start. tried the pull the plug suggestion didnt work. and not gonna flash the bios again...was out of pc for to long. So this was my fix. I went into the bios disabled the firewire, went to the local pc store and bought a pci firewire card. This should take care of the asus firewire problem for good. :D
zipp51
October 25th, 2003, 06:37 AM
I wonder if Asus fixed this in rev. 2.o? I didn't even have a peripheral plugged in for mine to not start.Well at least I know what you did phish,I am going to get a dig camcorder and I'll be prepared.
|
|