Hi:
I had a working setup, then this error started happening.
I have tried searching for what the problem might be, seems like the
1394dbg.inf file can get deleted, I re-installed several times and tried
disabling the Firewire adapter.
Also see:
System can not find specified file
Win32 error 0n2
I flagged the 1394dbg.inf as read-only and that seem to prevent it from been
deleted.
FileMon show no other files access after 1394dbg.inf is opened.
Any ideals on what will restore my debugger.
Thanks
Phil Sikora
Seems like the motherboard 1394 controller is bad, disabled it in the BIOS
and plugged in a PCI 1394 adapter that got rid of the “System can not find
specified file” problem.
Now get “Waitting to reconnect”
But still can’t attach to the target.
Some progress …
P.S. Never really been happy with this MB.
“Phil Sikora” wrote in message news:xxxxx@windbg…
> Hi:
> I had a working setup, then this error started happening.
> I have tried searching for what the problem might be, seems like the
> 1394dbg.inf file can get deleted, I re-installed several times and tried
> disabling the Firewire adapter.
>
> Also see:
> System can not find specified file
> Win32 error 0n2
>
> I flagged the 1394dbg.inf as read-only and that seem to prevent it from
> been deleted.
> FileMon show no other files access after 1394dbg.inf is opened.
>
> Any ideals on what will restore my debugger.
>
> Thanks
> Phil Sikora
>
>
>
Thought I would update this issue.
Have two targets and a host system, seems like the Host 1394 controller on
the mother board was damaged, and the target 1394 adapter was also damaged
but to a lesser extent.
When I moved the target 1394 adapter to the host system, the 1394 driver
initialized but only showed the “Waiting for reconnect” message,
when connected to the second target system with an un-damaged 1394
controller.
Replace the 1394 adapter in the target and host and everything works fine.
The damage must have occured when I was adding and removing a PCI network
adapter, testing an INF file.
Didn’t realized 1394 could be destroyed this readly.
Couldn’t find any Ti based controllers locally, so forced try a LSI
L-FW323-06 contoller, which seems fine so far.
Phil
Glad to hear it worked out, but that is some amazingly bad luck you
have, at least when it comes to 1394 boards.
mm
Phil Sikora wrote:
Thought I would update this issue.
Have two targets and a host system, seems like the Host 1394 controller on
the mother board was damaged, and the target 1394 adapter was also damaged
but to a lesser extent.
When I moved the target 1394 adapter to the host system, the 1394 driver
initialized but only showed the “Waiting for reconnect” message,
when connected to the second target system with an un-damaged 1394
controller.
Replace the 1394 adapter in the target and host and everything works fine.
The damage must have occured when I was adding and removing a PCI network
adapter, testing an INF file.
Didn’t realized 1394 could be destroyed this readly.
Couldn’t find any Ti based controllers locally, so forced try a LSI
L-FW323-06 contoller, which seems fine so far.
Phil
Maybe that is why they were destroyed by static or mis-insertion. OSR sells
good TI chipset cards for about their cost. They carry CardBus ones for
notebooks to act as a host too.
“Phil Sikora” wrote in message news:xxxxx@windbg…
> Thought I would update this issue.
>
> Have two targets and a host system, seems like the Host 1394 controller on
> the mother board was damaged, and the target 1394 adapter was also damaged
> but to a lesser extent.
>
> When I moved the target 1394 adapter to the host system, the 1394 driver
> initialized but only showed the “Waiting for reconnect” message,
> when connected to the second target system with an un-damaged 1394
> controller.
>
> Replace the 1394 adapter in the target and host and everything works fine.
>
> The damage must have occured when I was adding and removing a PCI network
> adapter, testing an INF file.
>
> Didn’t realized 1394 could be destroyed this readly.
>
> Couldn’t find any Ti based controllers locally, so forced try a LSI
> L-FW323-06 contoller, which seems fine so far.
>
> Phil
>
>
“David Craig” wrote in message news:xxxxx@windbg…
> Maybe that is why they were destroyed by static or mis-insertion. OSR
> sells good TI chipset cards for about their cost. They carry CardBus ones
> for notebooks to act as a host too.
Just to be clear the orginal motherboard and target adapter controllers were
TI, the replacements were LSI.
Phil