Hi there -

I need to get this fixed by dawn - don't know how to approach fixing this.
I always knew that Windows was never really happy restarting, only to find
out it has a new motherboard installed. Win9x and ME seem to cope rather
well after recognizing and installing misc. drivers for the on-board
features.

Is Win2K Pro so finnicky it won't do this? I get to the point where
Windows is about to start, you get the 'movement' at the bottom of the
screen (broken bar solidifies, etc.) and then it reboots again, POSTs and
then over and over.

Is there a quick fix to this? It was a P3-750 processor that I just put
on a Trinity 400 mobo. I had it on an Asus board but it couldn't seem to
remember bios settings from one day to the next. I replaced the battery,
etc. and that didn't correct anything. All other components seem to be
working just fine.

Please - any tips would be appreciated at this point.

Mike

Repair install: boot from Win2K CD. Go through setup, as if a fresh
install. When it detects other install, choose to repair it. After this is
done, boot from Win2K CD, again. This time, go to repair console, first
thing, by hitting 'r'. Login with blank password to C:\ Type /fixmbr
<enter> Then, type /fixboot <enter> Type 'exit' <enter>.

Reboot, normally.

-
Michael Mason stood up at show-n-tell, in bjrdm8$6th$(E-Mail Removed),
and said:

> Hi there -
>
> I need to get this fixed by dawn - don't know how to approach fixing
> this. I always knew that Windows was never really happy restarting,
> only to find out it has a new motherboard installed. Win9x and ME
> seem to cope rather well after recognizing and installing misc.
> drivers for the on-board features.
>
> Is Win2K Pro so finnicky it won't do this? I get to the point where
> Windows is about to start, you get the 'movement' at the bottom of the
> screen (broken bar solidifies, etc.) and then it reboots again, POSTs
> and then over and over.
>
> Is there a quick fix to this? It was a P3-750 processor that I just
> put on a Trinity 400 mobo. I had it on an Asus board but it couldn't
> seem to remember bios settings from one day to the next. I replaced
> the battery, etc. and that didn't correct anything. All other
> components seem to be working just fine.
>
> Please - any tips would be appreciated at this point.
>
> Mike

--
Strontium

"It's no surprise, to me. I am my own worst enemy. `Cause every
now, and then, I kick the livin' **** `outta me." - Lit

Strony nailed it But why would you take the motor out of you dodge and drop in a Chevy motor and expect the darn thing to start
without SOME kind of maintenance? 9x vintage OS's will stutter a bit (like you said) but not on 2000..NT and its a real special
treat if you try it on XP pro...the same thing applies to fix it, except it is much more inconsistent. Hope it works.

"Michael Mason" <(E-Mail Removed)> wrote in message news:bjrdm8$6th$(E-Mail Removed)...
> Hi there -
>
> I need to get this fixed by dawn - don't know how to approach fixing this.
> I always knew that Windows was never really happy restarting, only to find
> out it has a new motherboard installed. Win9x and ME seem to cope rather
> well after recognizing and installing misc. drivers for the on-board
> features.
>
> Is Win2K Pro so finnicky it won't do this? I get to the point where
> Windows is about to start, you get the 'movement' at the bottom of the
> screen (broken bar solidifies, etc.) and then it reboots again, POSTs and
> then over and over.
>
> Is there a quick fix to this? It was a P3-750 processor that I just put
> on a Trinity 400 mobo. I had it on an Asus board but it couldn't seem to
> remember bios settings from one day to the next. I replaced the battery,
> etc. and that didn't correct anything. All other components seem to be
> working just fine.
>
> Please - any tips would be appreciated at this point.
>
> Mike

"Michael Mason" wrote:
>
> Is Win2K Pro so finnicky it won't do this? I get to the point where
> Windows is about to start, you get the 'movement' at the bottom of the
> screen (broken bar solidifies, etc.) and then it reboots again, POSTs and
> then over and over.

This same thing happened to me recently when changing my mainboard on an
existing W2K intallation. What fixed it for me was to load the "fail safe
option" in the BIOS menu for the first boot up. After that I returned it to the
normal boot option and it's been working fine ever since.

Jon

This did it beautifully. Thanks alot, Strontium!

Michael

"Strontium" ((E-Mail Removed)) writes:
> Repair install: boot from Win2K CD. Go through setup, as if a fresh
> install. When it detects other install, choose to repair it. After this is
> done, boot from Win2K CD, again. This time, go to repair console, first
> thing, by hitting 'r'. Login with blank password to C:\ Type /fixmbr
> <enter> Then, type /fixboot <enter> Type 'exit' <enter>.
>
> Reboot, normally.
>
> -
> Michael Mason stood up at show-n-tell, in bjrdm8$6th$(E-Mail Removed),
> and said:
>
>> Hi there -
>>
>> I need to get this fixed by dawn - don't know how to approach fixing
>> this. I always knew that Windows was never really happy restarting,
>> only to find out it has a new motherboard installed. Win9x and ME
>> seem to cope rather well after recognizing and installing misc.
>> drivers for the on-board features.
>>
>> Is Win2K Pro so finnicky it won't do this? I get to the point where
>> Windows is about to start, you get the 'movement' at the bottom of the
>> screen (broken bar solidifies, etc.) and then it reboots again, POSTs
>> and then over and over.
>>
>> Is there a quick fix to this? It was a P3-750 processor that I just
>> put on a Trinity 400 mobo. I had it on an Asus board but it couldn't
>> seem to remember bios settings from one day to the next. I replaced
>> the battery, etc. and that didn't correct anything. All other
>> components seem to be working just fine.
>>
>> Please - any tips would be appreciated at this point.
>>
>> Mike
>
> --
> Strontium
>
> "It's no surprise, to me. I am my own worst enemy. `Cause every
> now, and then, I kick the livin' **** `outta me." - Lit
>
>

Cool! Glad it worked out, for ya. If it hadn't, the only other thing I
would've suggested is a fresh install of OS. And, that can be a pain

-
Michael Mason stood up at show-n-tell, in bjsi2b$8vs$(E-Mail Removed),
and said:

> This did it beautifully. Thanks alot, Strontium!
>
> Michael
>
> "Strontium" ((E-Mail Removed)) writes:
>> Repair install: boot from Win2K CD. Go through setup, as if a fresh
>> install. When it detects other install, choose to repair it. After
>> this is done, boot from Win2K CD, again. This time, go to repair
>> console, first thing, by hitting 'r'. Login with blank password to
>> C:\ Type /fixmbr <enter> Then, type /fixboot <enter> Type 'exit'
>> <enter>.
>>
>> Reboot, normally.
>>
>> -
>> Michael Mason stood up at show-n-tell, in
>> bjrdm8$6th$(E-Mail Removed), and said:
>>
>>> Hi there -
>>>
>>> I need to get this fixed by dawn - don't know how to approach fixing
>>> this. I always knew that Windows was never really happy restarting,
>>> only to find out it has a new motherboard installed. Win9x and ME
>>> seem to cope rather well after recognizing and installing misc.
>>> drivers for the on-board features.
>>>
>>> Is Win2K Pro so finnicky it won't do this? I get to the point where
>>> Windows is about to start, you get the 'movement' at the bottom of
>>> the screen (broken bar solidifies, etc.) and then it reboots again,
>>> POSTs
>>> and then over and over.
>>>
>>> Is there a quick fix to this? It was a P3-750 processor that I just
>>> put on a Trinity 400 mobo. I had it on an Asus board but it
>>> couldn't
>>> seem to remember bios settings from one day to the next. I replaced
>>> the battery, etc. and that didn't correct anything. All other
>>> components seem to be working just fine.
>>>
>>> Please - any tips would be appreciated at this point.
>>>
>>> Mike
>>

--
Strontium

"It's no surprise, to me. I am my own worst enemy. `Cause every
now, and then, I kick the livin' **** `outta me." - Lit