Re: W2K "ntoskrnl.exe"
From: Michael (anonymous_at_discussions.microsoft.com)
Date: 07/27/04
- Next message: Marin: "Update white box and grey box"
- Previous message: Mercury: "Re: error running windows update INNT\system32\advpack.dll"
- In reply to: Mercury: "Re: W2K "ntoskrnl.exe""
- Next in thread: Mercury: "Re: W2K "ntoskrnl.exe""
- Reply: Mercury: "Re: W2K "ntoskrnl.exe""
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 26 Jul 2004 20:08:37 -0700
Thank you Chuck and Mercury
I have taken a look at the articles suggested and I am
convinced that I have to do something, however when I
read...
"Edit the Boot.ini file and change the partition number
for Windows. In most cases, you need to increase the
partition number by one. A typical Windows line in the
Boot.ini file looks similar to the following, where x is
the partition number and <ntdir> is the name of the folder
into which Windows is installed:
multi(0)disk(0)rdisk(0)partition(x)\<ntdir>="Windows NT
Workstation Version 4.00"".....
I am totally confused!
As I have said I managed to get Win2K to load a second
WINNT so I am able to get the data that was not backed up.
However the number of apps and app upgrades means that I
am in for a long day. I have tried loading some software
but the installer finds the old app and cannot uninstall
it as it was not installed by the new WINNT!!
I did copy the ntoskrnl file to the old WINNT however it
did not allow me to boot.
Is it possible to copy the registry across to the new
system 32 file so that the new system thinks that it knows
about all the software!! Or would the registry have been
affected by the missing file/files?
Thanks for your help
Michael
>-----Original Message-----
>Michael --
>
>You should completely ignore what Alan has told you. Not
only is it very
>foolish, but it is also incorrect, as well as a big waste
of time. It is
>something akin to suggesting amputation to heal a broken
arm! Alan
>stubbornly persists in giving this useless advice to
people here, despite
>the fact that a quick examination will show it has helped
no one on this
>board. Sometimes a little knowledge is a dangerous thing
and Alan's advice
>is typical of what you get from some large consumer
computer companies'
>telephone help lines when they don't want to be bothered
to address the
>underlying problem, that is they tell you -- reformat,
reinstall the OS, and
>then reinstall the software, which is likely to be a very
painful and
>unnecessary process, as well as causing you in certain
cases to lose user
>data. If you are a masochist, and have large amounts of
time to waste; with
>no guarantee that your time will be rewarded following
his advice -- with no
>guarantee that the problem will not reoccur -- otherwise
read on:
>
>The vast majority of people who have upgraded to SP4 have
done a direct
>install with no problem, otherwise you would the outrage
cries of millions
>of users, as they have upgraded, which obviously has not
happened. Indeed
>SP4 has proved to be very stable.
>
>However, the few people who have had a problem generally
find that they need
>to get a driver for a specific hardware device, such as
an IDE card, etc. I
>have found in certain cases that was true for SP3 as
well. If you follow
>Alan's advice and wipe the disk and try to due a fresh
install you are
>likely to still have the same situation, since you
haven't addressed the
>underlying problem, most likely a hardware driver or a
software conflict. I
>would start by checking hardware drivers and software for
updates to make
>sure everything is up to date, and if no bringing the
system up to date and
>then try to reinstall SP4 again, which you are likely
going to need for
>security reasons in the future.
>
>"Chuck" <yadayada@blah.blah> wrote in message
>news:f_ydnThJysfSp5jcRVn-gw@comcast.com...
>> Did you read:
>>
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;124550&Product=win2000
>> and/or
>>
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;103673&Product=win2000
>>
>> to see if it helps?
>>
>> --
>> Chuck
>>
>> "Michael" <anonymous@discussions.microsoft.com> wrote
in message
>> news:390601c471f3$7b2f3720$a501280a@phx.gbl...
>> > After installing the SP4 I restarted the computer and
got
>> > the message that I should reinstall the ntoskrnl.exe.
>> > This seemed to be a problem as the emergency disks
just
>> > wanted to reinstall W2K
>> > I have the Win CD but when I booted from the CD there
was
>> > no way of getting at the CD files. I read Microsoft
>> > Knowlege based article 119467! Who are these articles
>> > written for? I am only a fluid power engineer! I have
no
>> > idea what to do based on this article.
>> > I eventually installed the OS on the computer again
>> > although I did not want to over write the data.
>> > I have been able to salvage the data. I would now
like to
>> > get the system up and running again preferrably
without
>> > having to reinstall all the applications.
>> > I have tried copying the file from the new
WINNT/system32/
>> > to the old WINNT/system32/ folder but it did not
work. It
>> > has been suggested that the SP4 "ntoskrnl.exe" is
diferent
>> > from the old one OR that I will have to rewrite
>> > the "boot.ini"
>> > Well now I am really lost. Can you help? One step at
a time
>> > Thank you
>> > Michael
>> > The machine is a Sony PCG XG29 it has 13gig 526 RAM
and
>> > should be running Windows 2000
>> >
>>
>>
>
>
>.
>
- Next message: Marin: "Update white box and grey box"
- Previous message: Mercury: "Re: error running windows update INNT\system32\advpack.dll"
- In reply to: Mercury: "Re: W2K "ntoskrnl.exe""
- Next in thread: Mercury: "Re: W2K "ntoskrnl.exe""
- Reply: Mercury: "Re: W2K "ntoskrnl.exe""
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
