> I get the error message at boot. I am setting a new computer.
>
> I have one HD which has Windows 98 on C: (FAT) and WINNT (NTFS)installed on D:
>
> Windows 98 boots fine. Windows 2000 used to boot fine too. After having
> installing Windows 2000 fine (it booted, worked fine) I downloaded Service Pack 4
> from microsoft. I haven't installed any other program.
>
> It installed fine. After rebooting I get the error. Emergency console see the
> directory WINNT fine and NTOSKRNL.EXE is there OK.
>
> What should I have in my BOOT.INI? I sure the files are fine (not missing or
> corrupt) but somehow Boot won't just see D: even though emergency repair does.
>
> The computer I am working has worked fine for years. I started the installation
> process just the start from scratch an do a clean reinstall.

>Post the contents of the boot.ini file here and someone will go over it
>with you and suggest possible changes or additions.
>
>John
>
>Op wrote:
>
>> I get the error message at boot. I am setting a new computer.
>>
>> I have one HD which has Windows 98 on C: (FAT) and WINNT (NTFS)installed on D:
>>
>> Windows 98 boots fine. Windows 2000 used to boot fine too. After having
>> installing Windows 2000 fine (it booted, worked fine) I downloaded Service Pack 4
>> from microsoft. I haven't installed any other program.
>>
>> It installed fine. After rebooting I get the error. Emergency console see the
>> directory WINNT fine and NTOSKRNL.EXE is there OK.
>>
>> What should I have in my BOOT.INI? I sure the files are fine (not missing or
>> corrupt) but somehow Boot won't just see D: even though emergency repair does.
>>
>> The computer I am working has worked fine for years. I started the installation
>> process just the start from scratch an do a clean reinstall.

"Op" <1@invalid.com> wrote in message
news:nqk9g39om77fopdktgm863h8copn6uguri@4ax.com...
> John John <audetw***@nbnet.nb.ca> wrote:
>
>>Post the contents of the boot.ini file here and someone will go over it
>>with you and suggest possible changes or additions.
>>
>>John
>>
>>Op wrote:
>>
>>> I get the error message at boot. I am setting a new computer.
>>>
>>> I have one HD which has Windows 98 on C: (FAT) and WINNT (NTFS)installed
>>> on D:
>>>
>>> Windows 98 boots fine. Windows 2000 used to boot fine too. After having
>>> installing Windows 2000 fine (it booted, worked fine) I downloaded
>>> Service Pack 4
>>> from microsoft. I haven't installed any other program.
>>>
>>> It installed fine. After rebooting I get the error. Emergency console
>>> see the
>>> directory WINNT fine and NTOSKRNL.EXE is there OK.
>>>
>>> What should I have in my BOOT.INI? I sure the files are fine (not
>>> missing or
>>> corrupt) but somehow Boot won't just see D: even though emergency repair
>>> does.
>>>
>>> The computer I am working has worked fine for years. I started the
>>> installation
>>> process just the start from scratch an do a clean reinstall.
>
>
> I decided to install Win2000 again. Now the installation process goes as
> far as
> "Saving settings" (the final page of installation process) and blue
> screens with
> "IRQL_NOT_LESS_OR_EQUAL" blah blah blah "ntoskrnl.exe"
>
> I've tried it like five or six times and same thing everytime. :(

> John John <audetw***@nbnet.nb.ca> wrote:
>
>
>>Post the contents of the boot.ini file here and someone will go over it
>>with you and suggest possible changes or additions.
>>
>>John
>>
>>Op wrote:
>>
>>
>>>I get the error message at boot. I am setting a new computer.
>>>
>>>I have one HD which has Windows 98 on C: (FAT) and WINNT (NTFS)installed on D:
>>>
>>>Windows 98 boots fine. Windows 2000 used to boot fine too. After having
>>>installing Windows 2000 fine (it booted, worked fine) I downloaded Service Pack 4
>>>from microsoft. I haven't installed any other program.
>>>
>>>It installed fine. After rebooting I get the error. Emergency console see the
>>>directory WINNT fine and NTOSKRNL.EXE is there OK.
>>>
>>>What should I have in my BOOT.INI? I sure the files are fine (not missing or
>>>corrupt) but somehow Boot won't just see D: even though emergency repair does.
>>>
>>>The computer I am working has worked fine for years. I started the installation
>>>process just the start from scratch an do a clean reinstall.
>
>
>
> I decided to install Win2000 again. Now the installation process goes as far as
> "Saving settings" (the final page of installation process) and blue screens with
> "IRQL_NOT_LESS_OR_EQUAL" blah blah blah "ntoskrnl.exe"
>
> I've tried it like five or six times and same thing everytime. :(

>> I decided to install Win2000 again. Now the installation process goes as far as
>> "Saving settings" (the final page of installation process) and blue screens with
>> "IRQL_NOT_LESS_OR_EQUAL" blah blah blah "ntoskrnl.exe"
>>
>> I've tried it like five or six times and same thing everytime. :(
>
>Did you disconnect all unnecessary external hardware before you
>reinstalled?  When you install an operating system the only external
>hardware that should be attached to the computer are the monitor,
>keyboard and mouse.
>
>John
>
>PS:  That blah blah blah stuff are important parameters in the bugcheck
>error message.  It may help someone find an answer to the problem if
>they know the 4 parameters.

> John John <audetw***@nbnet.nb.ca> wrote:
>
>
>>>I decided to install Win2000 again. Now the installation process goes as far as
>>>"Saving settings" (the final page of installation process) and blue screens with
>>>"IRQL_NOT_LESS_OR_EQUAL" blah blah blah "ntoskrnl.exe"
>>>
>>>I've tried it like five or six times and same thing everytime. :(
>>
>>Did you disconnect all unnecessary external hardware before you
>>reinstalled?  When you install an operating system the only external
>>hardware that should be attached to the computer are the monitor,
>>keyboard and mouse.
>>
>>John
>>
>>PS:  That blah blah blah stuff are important parameters in the bugcheck
>>error message.  It may help someone find an answer to the problem if
>>they know the 4 parameters.
>
>
> I managed to get Win2000 installed after numerous attempts but I believe some
> files were not installed properly. Now when I do something Windows generates some
> sort of error. For example if I bring up "control panel" I get a script error. I
> also get "Explorer has generated errors and will be closed ...".
>
> I tried doing an emergency repair procedure from the Win2000 installation CD. It
> dis it's job but I don't think it copied anything to the HD. It only seemed to
> check the HD and not copy any files.
>
> I can get to Internet but most pages including upgrade pages pop up a script
> error.
>
> Could I just copy the contents of SYSTEM32 from another computer to this computer
> if the problem is that a dll is bad or corrupt?

> I found the culprit: bad memory. Memtest reported lots of errors.
>
> Man did I put an effort: I disassembled three computers for parts, cables, hds! I
> should have tried memtest first! the computer in question used to work for years
> with no problems.