Hi guys,
I’m going to debug my driver using IEEE 1394 connection, but I cannot
make my target machine to boot up normally. I have two identical IEEE
1394 external PCI controllers based on the same VIA chip. On my host
machine this PCI controller works fine (I tested both of these
controllers, I tried to debug one of test machines with VIA integrated
IEEE 1394 controller). But my problem is that I cannot even start
Windows XP with SP2 on my target machine with this external VIA
controller when I try to load the operating system with IEEE 1394 debug
settings. Every time I do this the target machine immediately reboots,
I don’t even see the Windows XP startup screen. I tried to disable the
IEEE 1394 host controller on the target machine but it didn’t help, the
target machine constantly rebooted. Then I tried to load Windows Server
2003 SP1 with IEEE 1394 debug settings but it simply hung. Maybe I do
something wrong? I use simple settings, “/debug /debugport=1394”, but
it doesn’t work.
Many thanks beforehand, any clues and suggestions will be highly
appreciated. Perhaps some of you guys already faced this problem.
Konstantin Manurin
You have to specify channel ID, like in below line
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS=“Windows XP WinDbg”
/fastdetect /NoExecute=ALWAYSOFF /debug /debugport=1394 /channel=20
Regards,
Alex Greenberg
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Konstantin
Manurin
Sent: Tuesday, July 18, 2006 2:31 PM
To: Kernel Debugging Interest List
Subject: [windbg] WinDBG IEEE 1394 serious problem
Hi guys,
I’m going to debug my driver using IEEE 1394 connection, but I cannot
make my target machine to boot up normally. I have two identical IEEE
1394 external PCI controllers based on the same VIA chip. On my host
machine this PCI controller works fine (I tested both of these
controllers, I tried to debug one of test machines with VIA integrated
IEEE 1394 controller). But my problem is that I cannot even start
Windows XP with SP2 on my target machine with this external VIA
controller when I try to load the operating system with IEEE 1394 debug
settings. Every time I do this the target machine immediately reboots, I
don’t even see the Windows XP startup screen. I tried to disable the
IEEE 1394 host controller on the target machine but it didn’t help, the
target machine constantly rebooted. Then I tried to load Windows Server
2003 SP1 with IEEE 1394 debug settings but it simply hung. Maybe I do
something wrong? I use simple settings, “/debug /debugport=1394”, but it
doesn’t work.
Many thanks beforehand, any clues and suggestions will be highly
appreciated. Perhaps some of you guys already faced this problem.
Konstantin Manurin
You are currently subscribed to windbg as: xxxxx@intel.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
Alexander,
Thank you for quick reply, but I already tried these settings with
different channel ID’s and it didn’t help.
Konstantin Manurin
style=“font-size: 10pt; font-family: Arial; color: navy;”>You have to
specify channel ID, like in below
line<o:p></o:p>style=“font-size: 10pt; font-family: Arial; color: navy;”>multi(0)disk(0)rdisk(0)partition(1)\WINDOWS=“Windows
XP WinDbg” /fastdetect /NoExecute=ALWAYSOFF /debug /debugport=1394
/channel=20<o:p></o:p>style=“font-size: 10pt; font-family: Arial; color: navy;”><o:p> </o:p>
size=“2”> style=“font-size: 10pt; font-family: “Courier New”; color: green;”>Regards,<o:p></o:p>
size=“2”> style=“font-size: 10pt; font-family: “Courier New”; color: green;”>
Alex
Greenberg<o:p></o:p>size=“2”> style=“font-size: 10pt; font-family: “Courier New”; color: green;”> <o:p></o:p>
color=“black” face=“Times New Roman” size=“3”> style=“font-size: 12pt; color: windowtext;”>
style=“font-size: 10pt; font-family: Tahoma; color: windowtext; font-weight: bold;”>From: color=“black” face=“Tahoma” size=“2”> style=“font-size: 10pt; font-family: Tahoma; color: windowtext;”>
xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] style=“font-weight: bold;”>On
Behalf Of Konstantin Manurin
Sent: Tuesday, July
18, 2006 2:31
PM
To: Kernel Debugging
Interest List
Subject: [windbg]
WinDBG IEEE 1394
serious problem style=“color: windowtext;”><o:p></o:p>size=“3”><o:p> </o:p>
style=“font-size: 10pt; font-family: Arial;”>Hi guys,
I’m going to debug my driver using IEEE 1394 connection, but I cannot
make my
target machine to boot up normally. I have two identical IEEE 1394
external PCI
controllers based on the same VIA chip. On my host machine this PCI
controller
works fine (I tested both of these controllers, I tried to debug one of
test
machines with VIA integrated IEEE 1394 controller). But my problem is
that I
cannot even start Windows XP with SP2 on my target machine with this
external
VIA controller when I try to load the operating system with IEEE 1394
debug
settings. Every time I do this the target machine immediately reboots,
I don’t
even see the Windows XP startup screen. I tried to disable the IEEE
1394 host
controller on the target machine but it didn’t help, the target machine
constantly rebooted. Then I tried to load Windows Server 2003 SP1 with
IEEE
1394 debug settings but it simply hung. Maybe I do something wrong? I
use
simple settings, “/debug /debugport=1394”, but it doesn’t work.
Many thanks beforehand, any clues and suggestions will be highly
appreciated.
Perhaps some of you guys already faced this problem.
Konstantin Manurin
You are currently subscribed to windbg as:
xxxxx@intel.comTo unsubscribe send a blank email to xxxxx@lists.osr.com <o:p></o:p>
Have you disabled the driver for the 1394 controller on the test machine?
This is required for this stuff to work.
–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
http://www.windrvr.com
Remove StopSpam from the email to reply
“Konstantin Manurin” wrote in message
news:xxxxx@windbg…
> Hi guys,
>
>
> I’m going to debug my driver using IEEE 1394 connection, but I cannot make
> my target machine to boot up normally. I have two identical IEEE 1394
> external PCI controllers based on the same VIA chip. On my host machine
> this PCI controller works fine (I tested both of these controllers, I
> tried to debug one of test machines with VIA integrated IEEE 1394
> controller). But my problem is that I cannot even start Windows XP with
> SP2 on my target machine with this external VIA controller when I try to
> load the operating system with IEEE 1394 debug settings. Every time I do
> this the target machine immediately reboots, I don’t even see the Windows
> XP startup screen. I tried to disable the IEEE 1394 host controller on the
> target machine but it didn’t help, the target machine constantly rebooted.
> Then I tried to load Windows Server 2003 SP1 with IEEE 1394 debug settings
> but it simply hung. Maybe I do something wrong? I use simple settings,
> “/debug /debugport=1394”, but it doesn’t work.
>
>
> Many thanks beforehand, any clues and suggestions will be highly
> appreciated. Perhaps some of you guys already faced this problem.
>
>
>
> Konstantin Manurin
>
>
Yes, I tried to disable the 1394
host controller driver on my test (target) machine but it didn’t work
out.
I also figured out (using another test machine with integrated VIA
controller) that if I use 6-to-6 pins cable the connection is not
established, but if I use 6-to-4 pins cable (6 pins on the host machine
and 4 pins on the target machine) it works fine.
But nevertheless my basic test machine with external VIA controller
doesn’t even start :-(((
Konstantin Manurin
Have you disabled the driver for the 1394 controller on the test machine?
This is required for this stuff to work.
I have seen instances where some 1394 cards work fine on some machines, but are a hassle with others. I suggest investigating if other 1394 cards may help you on this specific set of hardware.
Jason
From: xxxxx@lists.osr.com on behalf of Konstantin Manurin
Sent: Tue 7/18/2006 6:16 AM
To: Kernel Debugging Interest List
Subject: Re:[windbg] WinDBG IEEE 1394 serious problem
Yes, I tried to disable the 1394 host controller driver on my test (target) machine but it didn’t work out.
I also figured out (using another test machine with integrated VIA controller) that if I use 6-to-6 pins cable the connection is not established, but if I use 6-to-4 pins cable (6 pins on the host machine and 4 pins on the target machine) it works fine.
But nevertheless my basic test machine with external VIA controller doesn’t even start :-(((
Konstantin Manurin
Have you disabled the driver for the 1394 controller on the test machine?
This is required for this stuff to work.
You are currently subscribed to windbg as: xxxxx@winse.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
Why don’t you try other connection, like RS232 (or even USB, which I
personally did not try).
Regards,
Alex Greenberg
(972)-4-8655627
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Konstantin
Manurin
Sent: Tuesday, July 18, 2006 3:10 PM
To: Kernel Debugging Interest List
Subject: Re:[windbg] WinDBG IEEE 1394 serious problem
Alexander,
Thank you for quick reply, but I already tried these settings with
different channel ID’s and it didn’t help.
Konstantin Manurin
You have to specify channel ID, like in below line
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS=“Windows XP WinDbg”
/fastdetect /NoExecute=ALWAYSOFF /debug /debugport=1394 /channel=20
Regards,
Alex Greenberg
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Konstantin
Manurin
Sent: Tuesday, July 18, 2006 2:31 PM
To: Kernel Debugging Interest List
Subject: [windbg] WinDBG IEEE 1394 serious problem
Hi guys,
I’m going to debug my driver using IEEE 1394 connection, but I cannot
make my target machine to boot up normally. I have two identical IEEE
1394 external PCI controllers based on the same VIA chip. On my host
machine this PCI controller works fine (I tested both of these
controllers, I tried to debug one of test machines with VIA integrated
IEEE 1394 controller). But my problem is that I cannot even start
Windows XP with SP2 on my target machine with this external VIA
controller when I try to load the operating system with IEEE 1394 debug
settings. Every time I do this the target machine immediately reboots, I
don’t even see the Windows XP startup screen. I tried to disable the
IEEE 1394 host controller on the target machine but it didn’t help, the
target machine constantly rebooted. Then I tried to load Windows Server
2003 SP1 with IEEE 1394 debug settings but it simply hung. Maybe I do
something wrong? I use simple settings, “/debug /debugport=1394”, but it
doesn’t work.
Many thanks beforehand, any clues and suggestions will be highly
appreciated. Perhaps some of you guys already faced this problem.
Konstantin Manurin
You are currently subscribed to windbg as: xxxxx@intel.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
You are currently subscribed to windbg as: xxxxx@intel.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
I used RS232 for a long time, but
it’s too slow for a whole lot of debug information.
style=“font-size: 10pt; font-family: Arial; color: navy;”>Why don’t
you try other connection,
like RS232 (or even USB, which I personally did not try).<o:p></o:p>style=“font-size: 10pt; font-family: Arial; color: navy;”><o:p> </o:p>
size=“2”> style=“font-size: 10pt; font-family: “Courier New”; color: green;”>Regards,<o:p></o:p>
size=“2”> style=“font-size: 10pt; font-family: “Courier New”; color: green;”>
Alex
Greenberg<o:p></o:p>size=“2”> style=“font-size: 10pt; font-family: “Courier New”; color: green;”>
(972)-4-8655627<o:p></o:p><o:p></o:p>color=“black” face=“Times New Roman” size=“3”> style=“font-size: 12pt; color: windowtext;”>
style=“font-size: 10pt; font-family: Tahoma; color: windowtext; font-weight: bold;”>From: color=“black” face=“Tahoma” size=“2”> style=“font-size: 10pt; font-family: Tahoma; color: windowtext;”>
xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] style=“font-weight: bold;”>On
Behalf Of Konstantin Manurin
Sent: Tuesday, July
18, 2006 3:10
PM
To: Kernel Debugging
Interest List
Subject: Re:[windbg]
WinDBG IEEE
1394 serious problem style=“color: windowtext;”><o:p></o:p>size=“3”><o:p> </o:p>
style=“font-size: 10pt; font-family: Arial;”>Alexander,
Thank you for quick reply, but I already tried these settings with
different
channel ID’s and it didn’t help.
Konstantin Manurin
<o:p></o:p>style=“font-size: 10pt; font-family: Arial; color: navy;”>You have to
specify channel ID, like in below lineu1:p</u1:p><o:p></o:p>style=“font-size: 10pt; font-family: Arial; color: navy;”>multi(0)disk(0)rdisk(0)partition(1)\WINDOWS=“Windows
XP
WinDbg” /fastdetect /NoExecute=ALWAYSOFF /debug /debugport=1394
/channel=20u1:p</u1:p><o:p></o:p>style=“font-size: 10pt; font-family: Arial; color: navy;”>u1:p </u1:p><o:p></o:p>
face=“Courier New” size=“2”> style=“font-size: 10pt; font-family: “Courier New”; color: green;”>Regards,u1:p</u1:p><o:p></o:p>
face=“Courier New” size=“2”> style=“font-size: 10pt; font-family: “Courier New”; color: green;”>
Alex Greenbergu1:p</u1:p><o:p></o:p>face=“Courier New” size=“2”> style=“font-size: 10pt; font-family: “Courier New”; color: green;”> u1:p</u1:p><o:p></o:p>
color=“black” face=“Times New Roman” size=“3”> style=“font-size: 12pt; color: windowtext;”>
size=“2”> style=“font-size: 10pt; font-family: Tahoma; color: windowtext; font-weight: bold;”>From: color=“black” face=“Tahoma” size=“2”> style=“font-size: 10pt; font-family: Tahoma; color: windowtext;”> href=“mailto:xxxxx@lists.osr.com”>xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]
On Behalf Of Konstantin
Manurin
Sent: Tuesday, July
18, 2006 2:31
PM
To: Kernel Debugging
Interest List
Subject: [windbg]
WinDBG IEEE 1394
serious problem<o:p></o:p>u1:p</u1:p>
face=“Times New Roman” size=“3”>u1:p </u1:p><o:p></o:p>
size=“2”>Hi
guys,
I’m going to debug my driver using IEEE 1394 connection, but I cannot
make my
target machine to boot up normally. I have two identical IEEE 1394
external PCI
controllers based on the same VIA chip. On my host machine this PCI
controller
works fine (I tested both of these controllers, I tried to debug one of
test
machines with VIA integrated IEEE 1394 controller). But my problem is
that I
cannot even start Windows XP with SP2 on my target machine with this
external
VIA controller when I try to load the operating system with IEEE 1394
debug
settings. Every time I do this the target machine immediately reboots,
I don’t
even see the Windows XP startup screen. I tried to disable the IEEE
1394 host
controller on the target machine but it didn’t help, the target machine
constantly rebooted. Then I tried to load Windows Server 2003 SP1 with
IEEE
1394 debug settings but it simply hung. Maybe I do something wrong? I
use
simple settings, “/debug /debugport=1394”, but it doesn’t work.
Many thanks beforehand, any clues and suggestions will be highly
appreciated.
Perhaps some of you guys already faced this problem.
Konstantin Manurin
You are currently subscribed to windbg as: href="mailto:xxxxx@intel.com">xxxxx@intel.com
To unsubscribe send a blank email to href="mailto:xxxxx@lists.osr.com">xxxxx@lists.osr.com
u1:p</u1:p><o:p></o:p>size=“3”>
—
You are currently subscribed to windbg as:
xxxxx@intel.com
To unsubscribe send a blank email to xxxxx@lists.osr.com <o:p></o:p>
Thank you for your advice. But now
I’m really stuck. Today in the morning I was able to establish
connection between the host machine with external VIA IEEE 1394
controller and the target machine with integrated VIA controller. But
now after all these manipulations and experiments I can’t. Though I’m
using the same settings as before. What could happen to these
controllers and WinDBG settings? And one more question. WinDBG
installed two 1394 Debugger Device drivers, “1394 Windows Debug
Driver(Kernel Mode)” and “1394 Windows XP Debug Driver”. As I
understood one of these drivers was installed when I tried to connect
to Windows XP target machine and the other was installed when I
connected to Windows Server 2003 machine. I tried to uninstall and then
to install WinDBG again, but these drivers were not removed. How can I
remove these virtual drivers from the host machine?
Thanks beforehand
Konstantin Manurin
I have seen instances where some 1394 cards work fine on some machines, but are a hassle with others. I suggest investigating if other 1394 cards may help you on this specific set of hardware.
Jason
From:xxxxx@lists.osr.comon behalf of Konstantin Manurin
Sent: Tue 7/18/2006 6:16 AM
To: Kernel Debugging Interest List
Subject: Re:[windbg] WinDBG IEEE 1394 serious problemYes, I tried to disable the 1394 host controller driver on my test (target) machine but it didn’t work out.
I also figured out (using another test machine with integrated VIA controller) that if I use 6-to-6 pins cable the connection is not established, but if I use 6-to-4 pins cable (6 pins on the host machine and 4 pins on the target machine) it works fine.
But nevertheless my basic test machine with external VIA controller doesn’t even start :-(((
Konstantin Manurin
Have you disabled the driver for the 1394 controller on the test machine?
This is required for this stuff to work.
You are currently subscribed to windbg as:xxxxx@winse.microsoft.com
To unsubscribe send a blank email toxxxxx@lists.osr.com
This sounds like a hardware problem, not a problem with WinDbg. Can you
try verifying that IEEE 1394 works between the computers, without using
WinDbg? Boot the target normally (no /debug), and check to see if
TCP/IP-over-1394 works. This will give you another data point – if
TCP/IP won’t work, then you likely have a hardware problem and WinDbg
has no hope of working.
I have had nothing but trouble with the VIA 1394 implementations. I
highly recommend the TI chipset. Since 1394 boards are treated as
commodities, it can be hard to know which kind you are buying. Which is
why OSR offers them at their store, at a reasonable price
(http://www.osronline.com). I am, of course, not an OSR shill. (I’m a
Microsoft shill!)
– arlie
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Konstantin
Manurin
Sent: Tuesday, July 18, 2006 10:18 AM
To: Kernel Debugging Interest List
Subject: Re:[windbg] WinDBG IEEE 1394 serious problem
Thank you for your advice. But now I’m really stuck. Today in the
morning I was able to establish connection between the host machine with
external VIA IEEE 1394 controller and the target machine with integrated
VIA controller. But now after all these manipulations and experiments I
can’t. Though I’m using the same settings as before. What could happen
to these controllers and WinDBG settings? And one more question. WinDBG
installed two 1394 Debugger Device drivers, “1394 Windows Debug
Driver(Kernel Mode)” and “1394 Windows XP Debug Driver”. As I understood
one of these drivers was installed when I tried to connect to Windows XP
target machine and the other was installed when I connected to Windows
Server 2003 machine. I tried to uninstall and then to install WinDBG
again, but these drivers were not removed. How can I remove these
virtual drivers from the host machine?
Thanks beforehand
Konstantin Manurin
I have seen instances where some 1394 cards work fine on some
machines, but are a hassle with others. I suggest investigating if
other 1394 cards may help you on this specific set of hardware.
Jason
From: xxxxx@lists.osr.com on behalf of Konstantin
Manurin
Sent: Tue 7/18/2006 6:16 AM
To: Kernel Debugging Interest List
Subject: Re:[windbg] WinDBG IEEE 1394 serious problem
Yes, I tried to disable the 1394 host controller driver on my
test (target) machine but it didn’t work out.
I also figured out (using another test machine with integrated
VIA controller) that if I use 6-to-6 pins cable the connection is not
established, but if I use 6-to-4 pins cable (6 pins on the host machine
and 4 pins on the target machine) it works fine.
But nevertheless my basic test machine with external VIA
controller doesn’t even start :-(((
Konstantin Manurin
Have you disabled the driver for the 1394 controller on
the test machine?
This is required for this stuff to work.
You are currently subscribed to windbg as:
xxxxx@winse.microsoft.com
To unsubscribe send a blank email to
xxxxx@lists.osr.com
You are currently subscribed to windbg as: xxxxx@microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
Thank you for this advice. I have
already checked TCP/IP-over-1394 connection between two machines using
6-to-4 pins cable and it was OK. But when I tried to use a 6-to-6 pins
cable it failed. I really don’t know why this happened. I guess that
the 6-to-6 pins cable has a bad shield or maybe doesn’t have it at all,
because this cable is quite thin and besides 2.5 - 3 meters long. I
think it doesn’t really matter which of IEEE 1394 controller connectors
to use for connection. So can this “badly shielded” cable be the cause
of connection failures? I must notice that I checked this cable and all
its internal wires are OK.
Konstantin Manurin
This sounds like a hardware problem, not a problem with WinDbg. Can you
try verifying that IEEE 1394 works between the computers, without using
WinDbg? Boot the target normally (no /debug), and check to see if
TCP/IP-over-1394 works. This will give you another data point – if
TCP/IP won’t work, then you likely have a hardware problem and WinDbg
has no hope of working.I have had nothing but trouble with the VIA 1394 implementations. I
highly recommend the TI chipset. Since 1394 boards are treated as
commodities, it can be hard to know which kind you are buying. Which is
why OSR offers them at their store, at a reasonable price
(http://www.osronline.com). I am, of course, not an OSR shill. (I’m a
Microsoft shill!)– arlie
From:xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Konstantin
Manurin
Sent: Tuesday, July 18, 2006 10:18 AM
To: Kernel Debugging Interest List
Subject: Re:[windbg] WinDBG IEEE 1394 serious problemThank you for your advice. But now I’m really stuck. Today in the
morning I was able to establish connection between the host machine with
external VIA IEEE 1394 controller and the target machine with integrated
VIA controller. But now after all these manipulations and experiments I
can’t. Though I’m using the same settings as before. What could happen
to these controllers and WinDBG settings? And one more question. WinDBG
installed two 1394 Debugger Device drivers, “1394 Windows Debug
Driver(Kernel Mode)” and “1394 Windows XP Debug Driver”. As I understood
one of these drivers was installed when I tried to connect to Windows XP
target machine and the other was installed when I connected to Windows
Server 2003 machine. I tried to uninstall and then to install WinDBG
again, but these drivers were not removed. How can I remove these
virtual drivers from the host machine?Thanks beforehand
Konstantin Manurin
I have seen instances where some 1394 cards work fine on some
machines, but are a hassle with others. I suggest investigating if
other 1394 cards may help you on this specific set of hardware.Jason
From:xxxxx@lists.osr.comon behalf of Konstantin
Manurin
Sent: Tue 7/18/2006 6:16 AM
To: Kernel Debugging Interest List
Subject: Re:[windbg] WinDBG IEEE 1394 serious problemYes, I tried to disable the 1394 host controller driver on my
test (target) machine but it didn’t work out.I also figured out (using another test machine with integrated
VIA controller) that if I use 6-to-6 pins cable the connection is not
established, but if I use 6-to-4 pins cable (6 pins on the host machine
and 4 pins on the target machine) it works fine.But nevertheless my basic test machine with external VIA
controller doesn’t even start :-(((Konstantin Manurin
Have you disabled the driver for the 1394 controller on
the test machine?
This is required for this stuff to work.
You are currently subscribed to windbg as:
xxxxx@winse.microsoft.com
To unsubscribe send a blank email to
xxxxx@lists.osr.com
You are currently subscribed to windbg as:xxxxx@microsoft.com
To unsubscribe send a blank email toxxxxx@lists.osr.com
Actually, for XPSP2 or Windows Server 2003 SP1 or later, disabling the 1394
controller is not required (and in fact supposedly breaks some debugging
scenarios). Since the OP is using XPSP2, there should be no need to disable
the controller on the target box.
–
Ken Johnson (Skywing)
Windows SDK MVP
“Don Burn” wrote in message news:xxxxx@windbg…
> Have you disabled the driver for the 1394 controller on the test machine?
> This is required for this stuff to work.
>
>
> –
> Don Burn (MVP, Windows DDK)
> Windows 2k/XP/2k3 Filesystem and Driver Consulting
> http://www.windrvr.com
> Remove StopSpam from the email to reply
>
>
>
> “Konstantin Manurin” wrote in message
> news:xxxxx@windbg…
>> Hi guys,
>>
>>
>> I’m going to debug my driver using IEEE 1394 connection, but I cannot
>> make my target machine to boot up normally. I have two identical IEEE
>> 1394 external PCI controllers based on the same VIA chip. On my host
>> machine this PCI controller works fine (I tested both of these
>> controllers, I tried to debug one of test machines with VIA integrated
>> IEEE 1394 controller). But my problem is that I cannot even start Windows
>> XP with SP2 on my target machine with this external VIA controller when I
>> try to load the operating system with IEEE 1394 debug settings. Every
>> time I do this the target machine immediately reboots, I don’t even see
>> the Windows XP startup screen. I tried to disable the IEEE 1394 host
>> controller on the target machine but it didn’t help, the target machine
>> constantly rebooted. Then I tried to load Windows Server 2003 SP1 with
>> IEEE 1394 debug settings but it simply hung. Maybe I do something wrong?
>> I use simple settings, “/debug /debugport=1394”, but it doesn’t work.
>>
>>
>> Many thanks beforehand, any clues and suggestions will be highly
>> appreciated. Perhaps some of you guys already faced this problem.
>>
>>
>>
>> Konstantin Manurin
>>
>>
>
>
>
Try the new 6675 release. It made things magically work for me suddenly both
with serial and firewire. Sometimes I still have to boot the target machine
with the debugger attached to get it rolling but it works.
/Daniel
“Konstantin Manurin” wrote in message
news:xxxxx@windbg…
> Hi guys,
>
> Many thanks beforehand, any clues and suggestions will be highly
> appreciated. Perhaps some of you guys already faced this problem.
>