Solving "Windows NT could not be started as configured..."
David Lumbers
>I've been getting the following message pretty much ever since I've installed
>windows NT 3.51 :
>"Windows NT could not be started as configured. A previous working
> configuration was used instead".
>Is there any way to determine WHY this message is being generated?? I've
>looked through the Event Viewer and there is nothing listed there.. I'm
>getting tired of seeing this message.. Any ideas??
I've been getting the exact same message - as a result, and change in
config is lost next time i boot. I've searched for any form of log
indicating what part of the config it doesn't like. I've re-installed
from scratch, but still get it. I'm starting to wonder if it might be
a motherboard problem, although, it worked ok for the past 4 months.
Let me know if you figure anything out.
David.
LGV Productions
Toronto.
Email: mik...@interlog.com or dy...@duts.ccc.amdahl.com
J or M prohs
>
> flo...@sdvax2.sp.trw.com (Richard E. Flower) wrote:
>
> >I've been getting the following message pretty much ever since I've installed
> >windows NT 3.51 :
>
> >"Windows NT could not be started as configured. A previous working
> > configuration was used instead".
>
I could not find the initial message by Richard, nor mine, but in the meantime I found
a solution that make work for you.
Check your BIOS. I learned this problem happens with computers using an Award Modular
BIOS version 4.50G or 4.50PG BIOS (the PG version supports plug-n-play).
You can correct this problem by changing the following CMOS settings:
DMACLOCK - SCLK-2
PRQ2detection - enabled
IDEHDDblockmode - disabled
Daylight Savings Time - disabled
If you are using the Award 4.50PG BIOS, as I was, you can correct this problem by
disabling the Daylight Savings Time setting.
2) After fixing the first problem, my "Domain Controller cannot be located" problem
was solved by manually starting Netlogon Services and setting it to start
automatically in the future.
M Prohs