Here is my system specs:
ASUS P2B-D Rev. 1.06 (D01)
BIOS 1014 Beta 002 (dated 4/1/2002)
250W Power Supply
Two (2) Pentium III 850Mhz CPU's (both cpu's are the same)
512MB RAM (2x256MB SDRAM PC-133 chips)
Adaptec-HA 2940U2 OEM SCSI BIOS v2.01.0S2 (dated 1998)
Seagate ST318275LW Ultra2-LVD (18.2GB HD)
Plextor PX-32TS Fast/Ultra-SE CD-ROM
ATI All-in-Wonder 128 AGP (16MB)
Creative SB Live Value
3com 3c905-C
I have tried *numerous times* to install Windows XP Professional
(corporate edition) only to have it fail with that lovely bsod!! What I do
is pop in the cd, and have the computer boot into the win xp installation.
I have tried both fat32, and ntfs. Has anyone with a similar setup like
mine successfully installed win xp pro??? preferrably someone with a P2B-D
Maybe one of my bios options is set incorrectly?? I have 'MPS 1.4 Support'
set for Enabled, but that didn't seem to help?
I also Disabled 'CPU Level 1 Cache', 'CPU Level 2 Cache', and 'Video ROM
BIOS Shadow' which only seemed to make my computer *extremely* slow. I
have 'PNP OS Installed' set to No.
Whatever I try, the result is the same... damn bsod! This is what one of
the screens showed:
-----snip here-----
A problem has been detected and windows has been shut down to prevent damage
to your computer.
MEMORY_MANAGEMENT
If this is the first time you've seen this Stop error screen,
restart your computer. If this screen appears again, follow
these steps:
Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any windows updates you might need.
If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use Safe Mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.
Technical information:
*** STOP: 0x0000001A (0x00041284,0x02BB6000,0x00000000,0xC0503000)
-----snip there-----
I have also gotten an IRQL_NOT_LESS_OR_EQUAL message in another bsod
during installation. A couple of times, the bsod occurred at 27% of
copying files (at the driver.cab file).
For some strange reason I think my Plextor cd-rom has something to do with
it?? can that be or is my 6th sense not working? lol
Anyway, can someone please help me get xp pro installed? I'm pretty sure
the P2B-D supports it, eh? Someone out there must have some insight into
this.
Thank you very much! TIA!
--
William D. Katz "a good skier"
Internet: dr...@dorsai.org
Internet: wk...@nyx.net
"William Katz" <dr...@dorsai.org> wrote in message
news:aa8ds...@enews2.newsguy.com...
Regards Thomas
"William Katz" <dr...@dorsai.org> skrev i en meddelelse
news:aa8ds...@enews2.newsguy.com...
"William Katz" <dr...@dorsai.org> wrote in message
news:aa8ds...@enews2.newsguy.com...
> I should have posted this a couple of months ago when I had problems
> trying to install XP, but anyway I thought I would try the install again.
>
I have a P2B-D 2xP3-550's running .NET Server Build 3504 for the last 49
days. The last time I rebooted was the day I installed this build.
Previous to that I ran XP from Beta 1, right through the beta test program
and installed final code in it.
XP should not be a problem with this board.
>
> MEMORY_MANAGEMENT
>
You've got some hardware out of spec or your BIOS revision has configured
the chipset incorrectly. My kid's PC kept getting all these spooky BSOD's
and I tested the crap out of the system. Three weeks ago Abit released a
new BIOS, flashed the system and the system's been rock solid since.
Test your memory, remove peripherals to minium needed to run. Try the
previous BIOS revision. That's all I can suggest.
cheers.
I think I would concur with you and the previous reply by BigJim
(woody...@hotmail.com) about it being a SCSI problem. I also read
Pinchbeck's post as well.
I'm pretty sure this is the problem:
Adaptec-HA 2940U2 OEM SCSI BIOS v2.01.0S2 (dated 1998)
I called Adaptec today to find out if I can update the BIOS on my
controller. The woman on the phone said that this specific scsi controller
(according to the TSID) could not be updated, due to it being an OEM. On
top of that, she said it was meant to be installed in a Micron computer!
Obviously I do not have a Micron. I then went to Adaptec's web site, and
it seems like the 2940U2W (the retail version, non-oem) is not made
anymore, and Win XP is *not* on the supported operating system's list for
this controller. the link is:
http://www.adaptec.com/worldwide/support/techspecs.html?prodkey=AHA-2940U2W&cat=%2fProduct%2fAHA-2940U2W#suppOS
What I will do is probably get the Adaptec 29160N and a new scsi cd-rom as
well. This should work, right?
It's funny that Win XP Pro is the only o/s that has ever given me trouble
with my system. I have installed win 98se, win nt4, slackware linux, and a
few other unix variant with no trouble. oh well.. I will just try to find
the best price for an Adaptec 29160N & a good scsi cd-rw now unless I have
a better option? and no, I don't want to dump scsi and go with all ide :)
The only thing I can suggest is trying a different power supply. 250
Watts seems a little small. I had no problems installing XP on a P2B-S
which uses the same chipset as your SCSI card (just built into the
board). XP has native support for Ultra2 SCSI, unlike NT which required
a driver install during the installation.
You might also remove the NIC to see if that is causing a conflict
during the installation process.
Good luck.
Well, I got Win XP Pro installed!!! It turns out the the problem all
along was the memory!! I guess I should have paid more attention to the
'memory_management' description of the bsod! Apparently XP is very fussy
about hardware, and the pc-133 sdram chips were not to xp's liking. I
took out the 512mb, and put back my old 128mb pc-100 sdram chip back in...
no problem whatsoever for the Win XP Pro install.
I will get pc-100 non-ecc sdram now. 2x256mb chips again. Does anyone
have any suggestions on what memory I should get for my P2B-D? I want to
get back to 512MB again. I might get Micron memory?
As for my SCSI devices, I took them out (the adaptec 2940u2w OEM, seagate
18.2 gb scsi drive, and plextor scsi cd-rom), and bought a 100gb ide hard
drive, and a plextor cd-rw ide drive. I think the problem with scsi was
that my md68 cable was faulty! ugh! oh well..
I even moved around my nic card and sound card to different pci slots.
Hey, those of you with Windows XP Professional, is it just me or is there
a serious bug with the screen/monitor refresh rate being *stuck* at *60
Hertz*?!?? Even though I have the latest video drivers for my aiw128 agp,
my monitor inf file, and did a 'Windows Update', I set the refresh rate to
75 Hertz, but I am really at 60 Hertz (the monitor shows this). Whatever
refresh rate I set, it seems like XP stays at 60. Come on micro$oft!!
> Hey, those of you with Windows XP Professional, is it just me or is there
> a serious bug with the screen/monitor refresh rate being *stuck* at *60
> Hertz*?!?? Even though I have the latest video drivers for my aiw128 agp,
> my monitor inf file, and did a 'Windows Update', I set the refresh rate to
> 75 Hertz, but I am really at 60 Hertz (the monitor shows this). Whatever
> refresh rate I set, it seems like XP stays at 60. Come on micro$oft!!
I also got an ATI AIW128 agp.. 32Mb.... look for the DDC setting in
the advanced bit of 'Desktop Properties.' / settings / er.. somwhere
here.
and you'll see probably that your monitor isn't ddc compatible and the
max refresh rate is defaulted to 60hz.. bump it up and your life will
be flicker free!!
Yep, I figured that out. Thanks! Now I just need to get *good* RAM for my
P2B-D. It should be PC-100. I want to get up to 512MB again (2x256MB
chips).
Do you have any suggestions as to what memory I can get and where? I heard
Micron memory is good?
P.S. I have PC-133 512MB of RAM (2x256MB) for sale if anyone is
interested :)
It could be due to the extreme fussiness of win xp and/or the strict
timing differences with pc133 memory in pc100 ram slots?? I am now back up
to 512mb of ram (pc-100) and everything seems fine now.