Does anyone have a suggestion on how I can solve this?
Fire Wire Oddity
Started by
philj200
, Sep 12 2008 08:09 AM
#1
Posted 12 September 2008 - 08:09 AM
Does anyone have a suggestion on how I can solve this?
#2
Posted 13 September 2008 - 03:29 AM
This is most likely caused by the presence of some sort of software on the previous installation that's now no longer there.
What were you using before, what were you doing before that you're now not using/doing?
What were you using before, what were you doing before that you're now not using/doing?
#3
Posted 14 September 2008 - 07:47 AM
When I installed the new hard drive, I put a fresh copy of XP on it, then ported over the entire previous hard drive. Some programs continued to worked as before. Some did not. I re-installed everything. I only use the IEEE card/connector with a camcorder for downloading video which is not a frequent event any longer. The drive switch over happened months ago and was chronicled here as it was the cure for a faulty drive.
I didn't have the need to import video until last week, when I saw that the computer could not find the camcorder.
Ancillary question: To see if the fire-wire card has failed (which I don't think is the case), could I attach the cable from the card to my laptop and see if either computer recognizes the other? It is the only other system I have that has an IEEE port.
I didn't have the need to import video until last week, when I saw that the computer could not find the camcorder.
Ancillary question: To see if the fire-wire card has failed (which I don't think is the case), could I attach the cable from the card to my laptop and see if either computer recognizes the other? It is the only other system I have that has an IEEE port.
#4
Posted 14 September 2008 - 01:18 PM
Worth trying, yes.
#5
Posted 16 September 2008 - 07:39 AM
It was a bad idea, cubed. I needed to enable a device driver for computer-to-computer communications. As soon as I did, the computer crashed. On rebooting, MS send me a message saying is was a USB problem. Odd since I connecter with a, IEEE cable. I went to the site they directed me to for an updated driver and got a 404.
So I'm back where I started.
However, while scanning the board I noticed someone having trouble with a Belkin adaptor for a Palm product. I also use thaat setup for an old Palm Pilot. Is it possible for the Belkin Serial to USB adaptor to be causing the promblem now. It did not, before I switched hard drives.
So I'm back where I started.
However, while scanning the board I noticed someone having trouble with a Belkin adaptor for a Palm product. I also use thaat setup for an old Palm Pilot. Is it possible for the Belkin Serial to USB adaptor to be causing the promblem now. It did not, before I switched hard drives.
Similar Topics
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users