🚀 go-pugleaf

Thank you for answering!

Albert <me@somewhere.nl> wrote in message
news:89b6dp$bl5$1@weber.a2000.nl...
> Hi Sander,
>
> I think we still need more specifications about your configuration,
> otherwise it would be a *guessing* game to find out the issue.
> Which build of W2K are you running at the moment, and did you experienced
> this also with other builds?

I run Windows 2000 build 2195. The problem appeared after W2000-RC2. When
Windows was still NT5 the problem did not happen.

> What happens after the hanging? Does it then permits you to go into W2K or
> is it a complete hang, waiting for a reboot?

It permits me to do everything. It just takes way too long to boot and after
supplying the log-in password it takes 4-5 minutes again until windows
actually starts up. When using Windows there is no problem, but on shut-down
I have the same long waiting period. It looks like Windows is actually
waiting for something and continues after a time-out.

> You said: <<"I tried using W2K with no other peripherals at all (only
> VGA-card) and still it hangs for 5 minutes on detecting network
settings.">>
>
> As you related the problem to your VGA card, did you checked the
> manufacturer website on their statement about this card and W2K, maybe it
is
> a non-supported card. Did you check that the card is on the HCL?
Eventually
> try with a different VGA card just to see what happens.

I think of two possible causes. One is my AGP slot. In previous Windows
versions I always needed a special driver, otherwise it was not possible to
even install Windows. For Windows 2000 Viatech (my mainboard) claims that
special drivers aren't neccessary anymore. But on DejaNews I did see several
people ask for new Viatech drivers, so I suppose that I'm not the only one
with problems.

My graphics card (Diamond Viper 330) seems to be 100% compaitable, according
to HCL. I use the build in Windows drivers.

> Are you using the latest BIOS on your machine? Remember that W2K has
control
> over ACPI and maybe your BIOS does not understands that W2K is taking
> control over all P&P devices, etc. on booting. If your BIOS does not want
to
> give control to W2K, then you might have an *internal war* in your
machine.
> The BIOS says "I am in control" and the OS says "no way I am in control".

I downloaded the latest BIOS for my mainboard. But how can I know whether
this version is W2K compaitable? Is is better to make the BIOS "Plug & Play
Aware"?

I think I already tried all settings in the BIOS...

Hardware troubleshooting is really difficult if the only device in your
computer is your graphics card ;-)

Grtz,


Sander

"Sander" <sander@speed.a2000.nl> wrote in message
news:89f6kd$ekp$1@tesla.a2000.nl...
> Thank you for answering!
>
> Albert <me@somewhere.nl> wrote in message
> news:89b6dp$bl5$1@weber.a2000.nl...
> > Hi Sander,
> >
> > I think we still need more specifications about your configuration,
> > otherwise it would be a *guessing* game to find out the issue.
> > Which build of W2K are you running at the moment, and did you
experienced
> > this also with other builds?
>
> I run Windows 2000 build 2195. The problem appeared after W2000-RC2. When
> Windows was still NT5 the problem did not happen.

Okay, that means that the earlier betas were running normal, so it can still
be that ACPI stuff I was talking about, because that was enhanced in the
newer builds.

> > What happens after the hanging? Does it then permits you to go into W2K
or
> > is it a complete hang, waiting for a reboot?
>
> It permits me to do everything. It just takes way too long to boot and
after
> supplying the log-in password it takes 4-5 minutes again until windows
> actually starts up. When using Windows there is no problem, but on
shut-down
> I have the same long waiting period. It looks like Windows is actually
> waiting for something and continues after a time-out.

It looks that one of the services, drivers, etc. being loaded takes too much
time. I thought that you could not go into the system, but you manage to go
into it after 5 minutes.
Do the following, boot your machine into Safe mode, and check if it also
takes this long, in this mode W2K uses only the basic files and drivers.
After that try Safe mode with networking and check how much time it takes.

> > You said: <<"I tried using W2K with no other peripherals at all (only
> > VGA-card) and still it hangs for 5 minutes on detecting network
> settings.">>
> >
> > As you related the problem to your VGA card, did you checked the
> > manufacturer website on their statement about this card and W2K, maybe
it
> is
> > a non-supported card. Did you check that the card is on the HCL?
> Eventually
> > try with a different VGA card just to see what happens.
>
> I think of two possible causes. One is my AGP slot. In previous Windows
> versions I always needed a special driver, otherwise it was not possible
to
> even install Windows. For Windows 2000 Viatech (my mainboard) claims that
> special drivers aren't neccessary anymore. But on DejaNews I did see
several
> people ask for new Viatech drivers, so I suppose that I'm not the only one
> with problems.

It seems that if more people are complaining, it looks to be common, but did
you checked that theire complaint is the same also in combination with W2K
or with other OS'ses.

> My graphics card (Diamond Viper 330) seems to be 100% compaitable,
according
> to HCL. I use the build in Windows drivers.
>
> > Are you using the latest BIOS on your machine? Remember that W2K has
> control
> > over ACPI and maybe your BIOS does not understands that W2K is taking
> > control over all P&P devices, etc. on booting. If your BIOS does not
want
> to
> > give control to W2K, then you might have an *internal war* in your
> machine.
> > The BIOS says "I am in control" and the OS says "no way I am in
control".
>
> I downloaded the latest BIOS for my mainboard. But how can I know whether
> this version is W2K compaitable? Is is better to make the BIOS "Plug &
Play
> Aware"?

Normally on the site where you downloaded the latest BIOS they put a
statement if it is W2K compatible, or in the Readme files before you flash.

> I think I already tried all settings in the BIOS...
>
> Hardware troubleshooting is really difficult if the only device in your
> computer is your graphics card ;-)

In that case try an other graphics card, and if you have other results that
it goes faster then you know that the only solution is an other card.

Grtz. Albert
**I'm a volunteer expert for TechNet (Windows 2000) Forum**
http://listen.to/sabroso [Die beste RealAudiosite, die MP3 schl�gt.]
Reggae, S@lsa, Merengue, K@seko, Soul, D@nce, and a lot of more hot Sounds.
Listen *online* in CD quality, just follow the instructions on the page.