Hello all,
Question in a nuttshell: Does any one know working hw-setup to run
Windows XP checked build?
I got a “nice” debug request to do for Windows XP. Problem is that
rndis-driver usage causes total USB-death for windows xp, which is not
even able to do clean shutdown after USB-jam. When USB-jam is on,
windows is not able to detect any USB-device.
With rndis debug drivers I am not getting any special behaviour compared
to working case, so I assume that something goes wrong in USB-layer or
in HAL.
So to get more information of the problem I installed windows XP checked
build. I tried many different laptops&desktops and only Dell Precision
330 was able to run checked build without BSOD. With this Dell I have
that problem, that I am not able to get any kernel debug traces out via
serial cable or from local connection. With serial cable windows bootup
halts to agp440.sys loading, when WinDBG hostmachine is trying to
connect to the target. When WinDBG on hostmachine is not trying to
connect, windows is able to bootup. I disabled that agp440.sys boottime
startup and after that booting stopped to MUP.sys loading. After
disabling bootup stopped to ndis and after that to ntfs.sys
When I try to run windebug on target machine, whole windows will freeze.
So I assume that these is some hw-issue with this Dell Precission.
-Mikko
As you’ve discovered, getting the entire checked build to install and work
is pretty much a crap shoot. It’s generally recommended to just replace the
pieces that you’re working with, so the entire USB stack and the kernel/HAL
in your case.
-scott
–
Scott Noone
Consulting Associate
OSR Open Systems Resources, Inc.
http://www.osronline.com
“Mikko Manninen” wrote in message
news:xxxxx@windbg…
> Hello all,
>
> Question in a nuttshell: Does any one know working hw-setup to run Windows
> XP checked build?
>
> I got a “nice” debug request to do for Windows XP. Problem is that
> rndis-driver usage causes total USB-death for windows xp, which is not
> even able to do clean shutdown after USB-jam. When USB-jam is on, windows
> is not able to detect any USB-device.
> With rndis debug drivers I am not getting any special behaviour compared
> to working case, so I assume that something goes wrong in USB-layer or in
> HAL.
>
> So to get more information of the problem I installed windows XP checked
> build. I tried many different laptops&desktops and only Dell Precision 330
> was able to run checked build without BSOD. With this Dell I have that
> problem, that I am not able to get any kernel debug traces out via serial
> cable or from local connection. With serial cable windows bootup halts to
> agp440.sys loading, when WinDBG hostmachine is trying to connect to the
> target. When WinDBG on hostmachine is not trying to connect, windows is
> able to bootup. I disabled that agp440.sys boottime startup and after that
> booting stopped to MUP.sys loading. After disabling bootup stopped to ndis
> and after that to ntfs.sys
>
> When I try to run windebug on target machine, whole windows will freeze.
>
> So I assume that these is some hw-issue with this Dell Precission.
>
>
> -Mikko
>
For that matter, even just getting the CHK build of XP is something of crap shoot these days.
mm
I wonder why?
I couldn’t say “Checked Build” enough in the 90’s. They are very, very helpful as we all know. Make them readily available and easily installable, MS!!!
Paul
----- Original Message -----
From: xxxxx@evitechnology.com
To: “Kernel Debugging Interest List”
Sent: Wednesday, November 11, 2009 9:28:15 AM GMT -05:00 US/Canada Eastern
Subject: RE:[windbg] Working hw-setup for Windows Xp checked
For that matter, even just getting the CHK build of XP is something of crap shoot these days.
mm
—
WINDBG is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
I like the sentiment, but I’d settle just for ‘available at all’ these days.
They are the Dodo of MSDN.
mm
Hmm … Dodo as in extinct bird, or mispelled and really doodoo as in
defecation? 
Either one would apply.
Gary G. Little
H (952) 223-1349
C (952) 454-4629
xxxxx@comcast.net
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@evitechnology.com
Sent: Wednesday, November 11, 2009 9:00 AM
To: Kernel Debugging Interest List
Subject: RE:[windbg] Working hw-setup for Windows Xp checked
I like the sentiment, but I’d settle just for ‘available at all’ these days.
They are the Dodo of MSDN.
mm
WINDBG is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
__________ Information from ESET Smart Security, version of virus signature
database 4594 (20091111) __________
The message was checked by ESET Smart Security.
http://www.eset.com
__________ Information from ESET Smart Security, version of virus signature
database 4594 (20091111) __________
The message was checked by ESET Smart Security.
http://www.eset.com
Part of the problem with the XP checked build is that when Microsoft issued
XP SP2 there were some legal dealings with Sun that meant that most people
got XP SP2 merged on the disk, and the old original XP disks went away.
What they overlooked was the checked build, and AFAIK they never build a
merged XP SP2 checked to replace the full checked build disk.
Of course as I wrote almost 5 years ago
http://www.microsoft.com/whdc/resources/mvp/xtremeMVP_giveup.mspx most
people in Redmond don’t care about the checked build. Thanks to the
“improvements” for Vista on wards the checked build is pretty much worthless
outside of Microsoft, and even prior to that some subsystems such as USB had
logging but it was encoded to make it useless without the sources.
–
Don Burn (MVP, Windows DKD)
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
wrote in message news:xxxxx@windbg…
>I like the sentiment, but I’d settle just for ‘available at all’ these
>days.
>
> They are the Dodo of MSDN.
>
>
> mm
>
>
> Information from ESET NOD32 Antivirus, version of virus
> signature database 4596 (20091111)
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
Information from ESET NOD32 Antivirus, version of virus signature database 4596 (20091111)
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
The XP CHK build is the reason that I can’t quite bring myself to throw out all the old MSDN disks that I have all over the place. I’ll likely never use any of them, and probably wouldn’t be able to find them if I need them, but still.
mm