Hi,

I am attempting to get the XP checked build onto an IBM NetVista system that is
completely clean, thus I am booting from the checked build CD.

At any rate, it bugchecks right at the start of setup, after the drivers are
loaded, and it appears to be hitting a breakpoint since the first parameter
after the 0x0000007e stop code is 0x80000003.

It would be nice if I could just tell the thing to continue, but how does one
attach a kernel debugger to it at that point during setup? Seems impossible to
me unless setup just automatically is set to go through COM1 or something. So,
shooting in the dark, I hooked up through COM1 and COM2 on the machine during
startup, and neither worked. So, setup on the CD does not appear to be running
in debug mode.

Any clues on how I can get around this problem?

Please cc me directly at my email addy above, sans the rudimentary spam guard.
:-)

Thanks!

-Trey

How to enable text-mode debugging during setup in Windows Server 2003 and
Windows Small Business Server 2003
http://support.microsoft.com/default...b;en-us;814334

--
http://www.firestreamer.com - NTBackup to DVD and DV


"Trey Nash" <tnash@spammenot.macromedia.com> wrote in message
news:ct16pu017bn@drn.newsguy.com...

Trey,

The Intel ethernet driver fails an OS assert and so that is why you
have the problems. Take a look at my article Driver Installation During
Windows Setup at http://www.osronline.com/article.cfm?article=264. It tells
you how to connect a debugger so you can get around this. You want the
section "What to do when things go wrong" about two thirds of the way
through the artice.


--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply

"Trey Nash" <tnash@spammenot.macromedia.com> wrote in message
news:ct16pu017bn@drn.newsguy.com...

Hi Don,

Thanks for the info. This apparently does not work on my XP checked build
install CD. I could abandon it and just use the 2003 checked build. But,
there's actually a good reason why I need to get the XP checked build on this
machine and it has to do with my company's VPN setup.

I will attempt to disable the NIC in the bios and see if I can get around this
issue. Is there no way to get the F8 style sequence to work for the install of
the XP checked build?

Thanks,

-Trey

In article <jSVId.12271$dR2.8695@fe06.lga>, Don Burn says...

Trey,

Unfortunately no, the only way I can think of getting around the problem is
to install the free build, then use the Win32 install approach I described.
A lot of extra work, unfortunately Intel has had the bug for close to 10
years that I know of! F8 was only win2k3.



--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply



"Trey Nash" <tnash@spammenot.digitrix.com> wrote in message
news:ct1e9u01vap@drn.newsguy.com...