M766LRT MB with PIII600E Slot 1

[NickName]

Have a old PIII600E on a PC Chips M766LRT motherboard, hoop up a hard
drive with pre-installed WN2000, the system keep rebooting itself after
power up. The WN2000 starting bar graph shows up, then system went
into reboot.

Quesiton:

1) will pre-installed wn2000 normally work with M766lrt MB?

2) How to update the bios of M766lrt? (went to the PC chips site and
found bios for M766LMRT, will this bios work for M766LRT board? the
file is a type ".rom" file, how do one load it into the bios?)

Any suggestion is high appreciated.

 

[nobody]

Have a old PIII600E on a PC Chips M766LRT motherboard, hoop up a hard
drive with pre-installed WN2000, the system keep rebooting itself after
power up. The WN2000 starting bar graph shows up, then system went
into reboot.

Quesiton:

1) will pre-installed wn2000 normally work with M766lrt MB?

It's drivers. You'll be better off installing Win2k from scratch. If
that is not an option, try booting into safe mode, delete all devices
in device manager, and let Windows find and install whatever devices
you have. You might have to search the Web for the drivers.

2) How to update the bios of M766lrt? (went to the PC chips site and

Follow the instructions on the PCchips site. If you have never done
it, you better stay away, unless you *must* do it to make things work.
There are too many ways to screw things up, most of the time beyond
recovery (ordering new BIOS chip for the board is always an option,
but costs more than this old board is worth).

found bios for M766LMRT, will this bios work for M766LRT board? the
file is a type ".rom" file, how do one load it into the bios?)

Once again, if in doubt, don't even think of it.

Any suggestion is high appreciated.

NNN

 

[George Macdonald]

Have a old PIII600E on a PC Chips M766LRT motherboard, hoop up a hard
drive with pre-installed WN2000, the system keep rebooting itself after
power up. The WN2000 starting bar graph shows up, then system went
into reboot.

Quesiton:

1) will pre-installed wn2000 normally work with M766lrt MB?

Win2K doesn't like having drivers which don't match the chipset, especially
for IDE - the reboot cycling is a symptom. Do you have the original mbrd
that Win2K worked with?... you'd need to boot with that and uninstall any
chipset specific drivers, replacing with generic Win2K drivers. Start with
IDE but there may be more. Even Safe Mode will not let you remove a
"device" which is not present.

I gather there are also people who have had success doing a repair with
custom driver install (F6 option) from the Win2K CD but I didn't.:-(

2) How to update the bios of M766lrt? (went to the PC chips site and
found bios for M766LMRT, will this bios work for M766LRT board? the
file is a type ".rom" file, how do one load it into the bios?)

I dunno anything about PCChips mbrds or their BIOS.

 

[George Macdonald]

It's drivers. You'll be better off installing Win2k from scratch. If
that is not an option, try booting into safe mode, delete all devices
in device manager, and let Windows find and install whatever devices
you have. You might have to search the Web for the drivers.

Win2K will not allow devices to be removed which are not currently present.

 

[hackbox.info]

normally work with M766lrt MB?

that is impossible, nothing "normally work"s with PCChips boards, they are
CRAP

 

[Gary L.]

Win2K will not allow devices to be removed which are not currently present.

Actually it will, through the "Add or Remove Hardware" applet in the
Control Panel. I don't recall the exact sequence off hand, but you
select "remove a device" and then check "show all devices" (or
something like that). It will show *all* hardware registry entries and
you can delete a device that is not present in the system, but for
which there is a registry entry. Of course, you can always edit the
registry hardware keys directly, but that takes some knowledge of what
the keys represent.

In Win XP, the applet was renamed to "Add Hardware" and the ability to
remove inactive hardware keys was removed. I guess it gave users too
much control over their systems. But in all fairness, if you deleted
the wrong thing using the applet in Windows 2000, it really made a
mess of things.

Of course, the O.P. should simply do a clean install of the OS. Just
wanted to share this piece of computer trivia.
- -
Gary L.
Reply to the newsgroup only

 

[George Macdonald]

Actually it will, through the "Add or Remove Hardware" applet in the
Control Panel. I don't recall the exact sequence off hand, but you
select "remove a device" and then check "show all devices" (or
something like that). It will show *all* hardware registry entries and
you can delete a device that is not present in the system, but for
which there is a registry entry.

I'd suggest you try it - it does *NOT* work in Win2K SP4 if the device is
not present. I don't need to "recall" on this - I see it every time I mess
with the network settings on our server.

Of course, you can always edit the
registry hardware keys directly, but that takes some knowledge of what
the keys represent.

Good luck.

 

[Gary L.]

I'd suggest you try it - it does *NOT* work in Win2K SP4 if the device is
not present. I don't need to "recall" on this - I see it every time I mess
with the network settings on our server.

Ah, Monsieur, I have been challenged? I have been slapped in the face
with a glove, no? Well, well, let us select our seconds and pick out our
dueling pistols! My honor is at stake.

I am now firing up my only Windows 2000 machine (a ThinkPad 600) running
Windows 2000 Pro SP4. It does not have any build-in network cards, so I
use either a Siemens Ethernet card and a LinkSys 802.11g wireless card
in the PC Card slots. The Siemens card is NOT installed as I boot up the
machine.

I open the Control Panel. I then start Add/Remove Hardware applet,
select Uninstall/Unplug a device, then Uninstall a device, then check
"Show hidden devices." A list of "installed devices" appears. On that
list is an entry for "Siemens SpeedStream CardBus 10/100" with the
Ethernet adapter icon preceding it. Actually, there are *two* entries,
with the second one suffixed as "#2" (as a result of putting the PC
Card in the other PC Card slot on one occasion). I can delete the entry
from this dialog box. There are also many entries for absent devices,
including USB keyboards, USB mice, USB mass storage devices, the printer
at the office, USB hubs, the PC Card USB 2 adapter I sometimes use, etc.
In fact, it lists just about everything I've ever plugged into the computer.

You mentioned your *server* at work. It is possible that Windows 2000
Server does not work the same way. But Windows 2000 *Pro* definitely
does provide a method for removing the configuration for at least some
of the absent devices.

 

[Rob Stow]

I'd suggest you try it - it does *NOT* work in Win2K SP4 if the device is
not present.

It *does* work with W2K SP4. Not only have I done it repeatedly
in the past, I just verified it for myself again two minutes ago
by deleting a wireless NIC that I removed last fall and an AGP
video card that was replaced in December.

 

[nobody]

I'd suggest you try it - it does *NOT* work in Win2K SP4 if the device is
not present. I don't need to "recall" on this - I see it every time I mess
with the network settings on our server.


Good luck.

Have not done it for long time, but I remember removing a 10base ISA
NIC and replacing it with 100 PCI - totally different manufacturer,
driver, etc. There was no issue with the old card not being present
anymore (it was replaced because it died). The driver was removed, I
just don't remember what tool I used - device manager, or "Add or
Remove Hardware applet". It was win2k adv. server, but not up to SP4
- probably SP2 or 3.

Having said all that, I still think that clean install is the best
solution for the OP.

NNN

 

[Tony Hill]

Have a old PIII600E on a PC Chips M766LRT motherboard, hoop up a hard
drive with pre-installed WN2000, the system keep rebooting itself after
power up. The WN2000 starting bar graph shows up, then system went
into reboot.

Quesiton:

1) will pre-installed wn2000 normally work with M766lrt MB?

Nope. Nor is a pre-installed Win2K likely to work on ANY motherboard
except one nearly identical to the one where you made the image.

2) How to update the bios of M766lrt? (went to the PC chips site and
found bios for M766LMRT, will this bios work for M766LRT board? the
file is a type ".rom" file, how do one load it into the bios?)

The M766LMRT BIOS might work, or it might not. I'm not really sure.
As for the .rom file, there is probably a program on PC Chips website
to update the BIOS. Or alternatively you could try the BIOS
manufacturer's website (probably Phoenix, Award or AMI). it's
probably going to be a DOS based utility, though they have a Windows
based utility as well.

Either way though, the chances of this fixing your probably are
EXTREMELY slim. You're issue is almost certainly drivers and not BIOS
related.

Any suggestion is high appreciated.

You can TRY booting into Safe Mode and see if you can uninstall all
the drivers and have them redetected, but almost certainly you're
going to need to do a fresh install.

 

[George Macdonald]

Have not done it for long time, but I remember removing a 10base ISA
NIC and replacing it with 100 PCI - totally different manufacturer,
driver, etc. There was no issue with the old card not being present
anymore (it was replaced because it died). The driver was removed, I
just don't remember what tool I used - device manager, or "Add or
Remove Hardware applet". It was win2k adv. server, but not up to SP4
- probably SP2 or 3.

All I can tell you is that Device Manager does not work (reliably) for
devices I've tried, in particular a NIC. This was an Intel NIC with
installed software and the software uninstall which would normally remove
the drivers did not. Note also that the OP is looking at a different
mbrd/chipset.

Having said all that, I still think that clean install is the best
solution for the OP.

Yeah well that can depend on how much work it is to get back to where
things were with the total installation. If you have a single Domain
Controller, e.g., it can be a *lot* of work to get back to where you were
and even then you need to have everything documented... user names and
privileges, group security, file system security and access privileges
etc., before you do the switch. This could run into days of work.

 

[George Macdonald]

It *does* work with W2K SP4. Not only have I done it repeatedly
in the past, I just verified it for myself again two minutes ago
by deleting a wireless NIC that I removed last fall and an AGP
video card that was replaced in December.

It's not a lot of help to just say "it *does* work" without elaborating on
what "it" is -- and doing it 2mins ago does not help with the OP's
situation at hand of a different mbrd chipset and possible orphaned devices
relative to the new chipset driver chain. It would appear that possibly
Add/Remove Hardware Control Panel allows removal in some cases but my
experience with Device Manager is that is not reliable and will actually
tell you that the device cannot be removed because it is not present, even
in Safe Mode.

 

[George Macdonald]

Ah, Monsieur, I have been challenged? I have been slapped in the face
with a glove, no? Well, well, let us select our seconds and pick out our
dueling pistols! My honor is at stake.

Eh.. be-e... BOF!

I am now firing up my only Windows 2000 machine (a ThinkPad 600) running
Windows 2000 Pro SP4. It does not have any build-in network cards, so I
use either a Siemens Ethernet card and a LinkSys 802.11g wireless card
in the PC Card slots. The Siemens card is NOT installed as I boot up the
machine.

I open the Control Panel. I then start Add/Remove Hardware applet,
select Uninstall/Unplug a device, then Uninstall a device, then check
"Show hidden devices." A list of "installed devices" appears. On that
list is an entry for "Siemens SpeedStream CardBus 10/100" with the
Ethernet adapter icon preceding it. Actually, there are *two* entries,
with the second one suffixed as "#2" (as a result of putting the PC
Card in the other PC Card slot on one occasion). I can delete the entry
from this dialog box. There are also many entries for absent devices,
including USB keyboards, USB mice, USB mass storage devices, the printer
at the office, USB hubs, the PC Card USB 2 adapter I sometimes use, etc.
In fact, it lists just about everything I've ever plugged into the computer.

You mentioned your *server* at work. It is possible that Windows 2000
Server does not work the same way. But Windows 2000 *Pro* definitely
does provide a method for removing the configuration for at least some
of the absent devices.

Cardbus and those other devices are all hot dockable plug 'n' play devices
- not the same thing as a direct attached PCI device and the OP's situation
is with a completely different chipset/mbrd. "Issues" with this kind of
thing are welll documented/discussed all over the Internet - the
recommended path is to remove special device drivers *before* taking out
the old mbrd/chipset... which is not a lot of help if the damned thing is
broken.

It's possible that Add/Remove Hardware Control Panel -- which I believe is
a holdover from WinNT since it's not available in the Win9x or WinXP
systems -- allows things which Device Manager doesn't - if so, we're
looking at yet another M$ ****up.

 

[Gary L.]

Eh.. be-e... BOF!

Cardbus and those other devices are all hot dockable plug 'n' play devices
- not the same thing as a direct attached PCI device and the OP's situation
is with a completely different chipset/mbrd. "Issues" with this kind of
thing are welll documented/discussed all over the Internet - the
recommended path is to remove special device drivers *before* taking out
the old mbrd/chipset... which is not a lot of help if the damned thing is
broken.

It occurred to me that all of the "uninstalled" entries in the Remove
Hardware Applet were either CardBus or USB devices that have enhanced
hot plug capabilities. I do not have a desktop machine with Windows 2000
and I can't really remove any hardware form the notebook computer except
for CardBus, USB and UltraBay devices. So I cannot assert that absent
PCI devices will show up or can be effectively uninstalled from the
applet. And certainty it is better to uninstall the drivers before
removing the device, if possible.

It's possible that Add/Remove Hardware Control Panel -- which I believe is
a holdover from WinNT since it's not available in the Win9x or WinXP
systems -- allows things which Device Manager doesn't - if so, we're
looking at yet another M$ ****up.

The Control Panel Applet definitely shows things that Device Manager
doesn't. Whether that's a mistake or a feature is another question.

But, Monsieur, we both leave with our honor intact. C'est tres bien.
Bonsoir.

 

[hackbox.info]

Nor is a pre-installed Win2K likely to work on ANY motherboard
except one nearly identical to the one where you made the image.

myth, all you neet to do is to change IDE driver to generic one before
swap.
I run the same XP install for over 2 years now (>30 motherboards lifespan)

 

[Gary L.]

myth, all you neet to do is to change IDE driver to generic one before
swap.
I run the same XP install for over 2 years now (>30 motherboards lifespan)

You replaced your motherboard over 30 times in 2 years? You activated
the same copy more than once a month every month for 2 years?

 

[hackbox.info]

You replaced your motherboard over 30 times in 2 years? You activated
the same copy more than once a month every month for 2 years?

activated? you mean you pay for this crap?!?!

 

[chrisv]

activated? you mean you pay for this crap?!?!

Why did you ignore his first question?

 

[hackbox.info]

Why did you ignore his first question?

Yes I did. I like to try new things.

as for the

Hell no. And I cant imagine anybody would bother with the whole activation
mess. Everytime I install XP (client/friend/company computer) first thing
I do is to apply no_activation patch. There is no obligation or law to put
up with this inconvenience, at least not in my country. Last time I
checked Eula was only some piece of paper in the box, not a proper
contract that I signed.