"Error loading KERNEL" message

[Olin K. McDaniel]

Hopefully this won't get too longwinded, but as a bit of background, I
recently upgraded my hardware and wanted to keep all the software as
before. I installed a new M.B. and CPU to go from a 600MHz Pentium 3
unit to a 2.6 GHz Celeron unit. Also I cloned over the multiboot
OS's from drive 1 to another HD, since the older one was showing signs
of failing. The program used for cloning was Acronis True Image.
There were 3 OS's on Drive 1, and they also are now on the newly
installed HDD. The heart of the multiboot system is Powerquest's Boot
Magic, that has worked wonderfully for years. The 3 OS's are DOS 6.22
(rarely used anymore), Windows 98SE (most heavily used) and Windows
2000 Pro (used somewhat).

The problem developed subsequent to several days of allowing the new
M.B. and CPU to install all its drivers, etc.

Essentially, I cannot boot up (on the NEW Hard Disk 1) into Win98SE in
Normal mode - I get an error message that says "Error loading KERNEL.
You must reinstall Windows". BUT - much to my annoyance, it WILL
boot up fully in SAFE mode. Nothing that I've tried has cleared up
this anomaly. I've followed the procedure found on MS's web site
which tells me to "extract Kernel32.dll" from my installation CD and
copy it to the folder Windows\System\, all to no avail, after multiple
efforts. In addition, I've copied it over from the presumed "failing"
hard drive, again with no success. I'm about ready to throw in the
towel - hopefully, someone can give me an out. Before someone asks,
there is NO problem booting up in Win2000 on this drive.

Finally, as a further frustating fact, I can still do the multiboot if
I swap out the new HD 1 to the old failing one. But I don't trust it
lasting much longer.

I'm admittedly out of ideas - and if it should be a problem with the
MBR, then I don't know how to repair it.

Sorry it got this long - and it may not have all the useful info
someone might think would lead to a clue. If so, please tell me what
to check.

Thanks, Olin McDaniel

To reply by email, please remove "abcd" from Return address
-----------------------------------------------------
"Ignorance is treatable, Stupidity is incurable. Sometimes
the difference is hardly distinguishable, however."

 

[MEB]

Hmm, no responses.. so to help the group to help you

How about some information related to:

What motherboard - make/model.

What make and model hard drive, and is it SATA.or PATA, etc.. What is the
old drive, make and model, SATA/PATA

What had you [both recent and just] installed when the error first occurred
[driver,application, etc.]

The exact error message.

Safe mode runs just base system drivers so likely the issue relates to
something that was installed, hence the reason for the above. Kernel errors
can be caused by numerous things from: other corrupted files, corrupted
registry, to even a corrupted swap file, so we have to back-track through
what occurred prior to the issue.
Also, what system did you FIRST attempt to use after the change over [98 or
2000]...

--

MEB
http://peoplescounsel.orgfree.com
_________


"Olin K. McDaniel" <mcdanielo.abcd@bellsouth.net> wrote in message
news:47a3a6c2.4965099@newsgroups.bellsouth.net...
| Hopefully this won't get too longwinded, but as a bit of background, I
| recently upgraded my hardware and wanted to keep all the software as
| before. I installed a new M.B. and CPU to go from a 600MHz Pentium 3
| unit to a 2.6 GHz Celeron unit. Also I cloned over the multiboot
| OS's from drive 1 to another HD, since the older one was showing signs
| of failing. The program used for cloning was Acronis True Image.
| There were 3 OS's on Drive 1, and they also are now on the newly
| installed HDD. The heart of the multiboot system is Powerquest's Boot
| Magic, that has worked wonderfully for years. The 3 OS's are DOS 6.22
| (rarely used anymore), Windows 98SE (most heavily used) and Windows
| 2000 Pro (used somewhat).
|
| The problem developed subsequent to several days of allowing the new
| M.B. and CPU to install all its drivers, etc.
|
| Essentially, I cannot boot up (on the NEW Hard Disk 1) into Win98SE in
| Normal mode - I get an error message that says "Error loading KERNEL.
| You must reinstall Windows". BUT - much to my annoyance, it WILL
| boot up fully in SAFE mode. Nothing that I've tried has cleared up
| this anomaly. I've followed the procedure found on MS's web site
| which tells me to "extract Kernel32.dll" from my installation CD and
| copy it to the folder Windows\System\, all to no avail, after multiple
| efforts. In addition, I've copied it over from the presumed "failing"
| hard drive, again with no success. I'm about ready to throw in the
| towel - hopefully, someone can give me an out. Before someone asks,
| there is NO problem booting up in Win2000 on this drive.
|
| Finally, as a further frustating fact, I can still do the multiboot if
| I swap out the new HD 1 to the old failing one. But I don't trust it
| lasting much longer.
|
| I'm admittedly out of ideas - and if it should be a problem with the
| MBR, then I don't know how to repair it.
|
| Sorry it got this long - and it may not have all the useful info
| someone might think would lead to a clue. If so, please tell me what
| to check.
|
| Thanks, Olin McDaniel
|
| To reply by email, please remove "abcd" from Return address
| -----------------------------------------------------
| "Ignorance is treatable, Stupidity is incurable. Sometimes
| the difference is hardly distinguishable, however."

 

[glee]

When you are going to change major hardware such as the motherboard and processor,
you first need to remove the drivers for everything that is part of that
hardware.....chipset drivers, onboard audio and video, onboard LAN, floppy
controller, hard drive controllers, and so forth. If you did not do that before
changing the hardware, you should do it now from Safe Mode in Win98, as that is the
OS giving you trouble.

Click Start>Run, type: scanregw
|click OK|
When prompted, say Yes to backing up the Registry.

Next, if your old or new motherboard uses onmboard video rather than a dedicated
video card, uninstall any display software and drivers, allowing Windows to change
your display adapter to Standard VGA 640x480, and reboot if prompted. Then
uninstall any audio software and drivers that are not part of the new system.

Now restart in Safe Mode, open Device Manager, expand all categories and start
removing devices.
You pretty much need to remove everything except the keyboard/mouse/monitor,
including all the items in the System section of Device Manager as well as in the
Other section, the USB Controllers section, all other drives and controllers,
display adapters, audio controllers, network adapter.

Click OK to close, then start in normal mode. Windows will begin detecting
hardware....when it finds the primary IDE controller and wants to reboot, say no and
let it find the secondary IDE controller too, then reboot at that prompt.
The next restart should find the rest of the current hardware, while the remnants of
the old hardware will no longer be present.

Be sure to then install the chipset drivers from the disc that came with your new
motherboard, reboot, then install the drivers for your display, audio and so forth.

An alternative to deleting individual items in Safe Mode Device Manager, is to open
the Registry Editor and delete the entire Enum key at this location:
HKEY_LOCAL_MACHINE\Enum
Then, shutdown, move the hard drive to the new system, and follow the suggestions
above.
The Safe Mode method is usually safer.
--
Glen Ventura, MS MVP Shell/User, A+
http://dts-l.net/
http://dts-l.net/goodpost.htm


"Olin K. McDaniel" <mcdanielo.abcd@bellsouth.net> wrote in message
news:47a3a6c2.4965099@newsgroups.bellsouth.net...
> Hopefully this won't get too longwinded, but as a bit of background, I
> recently upgraded my hardware and wanted to keep all the software as
> before. I installed a new M.B. and CPU to go from a 600MHz Pentium 3
> unit to a 2.6 GHz Celeron unit. Also I cloned over the multiboot
> OS's from drive 1 to another HD, since the older one was showing signs
> of failing. The program used for cloning was Acronis True Image.
> There were 3 OS's on Drive 1, and they also are now on the newly
> installed HDD. The heart of the multiboot system is Powerquest's Boot
> Magic, that has worked wonderfully for years. The 3 OS's are DOS 6.22
> (rarely used anymore), Windows 98SE (most heavily used) and Windows
> 2000 Pro (used somewhat).
>
> The problem developed subsequent to several days of allowing the new
> M.B. and CPU to install all its drivers, etc.
>
> Essentially, I cannot boot up (on the NEW Hard Disk 1) into Win98SE in
> Normal mode - I get an error message that says "Error loading KERNEL.
> You must reinstall Windows". BUT - much to my annoyance, it WILL
> boot up fully in SAFE mode. Nothing that I've tried has cleared up
> this anomaly. I've followed the procedure found on MS's web site
> which tells me to "extract Kernel32.dll" from my installation CD and
> copy it to the folder Windows\System\, all to no avail, after multiple
> efforts. In addition, I've copied it over from the presumed "failing"
> hard drive, again with no success. I'm about ready to throw in the
> towel - hopefully, someone can give me an out. Before someone asks,
> there is NO problem booting up in Win2000 on this drive.
>
> Finally, as a further frustating fact, I can still do the multiboot if
> I swap out the new HD 1 to the old failing one. But I don't trust it
> lasting much longer.
>
> I'm admittedly out of ideas - and if it should be a problem with the
> MBR, then I don't know how to repair it.
>
> Sorry it got this long - and it may not have all the useful info
> someone might think would lead to a clue. If so, please tell me what
> to check.
>
> Thanks, Olin McDaniel
>
> To reply by email, please remove "abcd" from Return address
> -----------------------------------------------------
> "Ignorance is treatable, Stupidity is incurable. Sometimes
> the difference is hardly distinguishable, however."

 

[Olin K. McDaniel]

OK, I'll provide what I can, but it will be impossible to remember all
the things you asked, since this has been an ongoing problem for over
3 weeks.

First - the exact message was stated in my original post, i.e. "Error
loading KERNEL. You must reinstall Windows". That's it, no more, no
less.

The newly installed motherboard is a Biostar P4M80-M4. I can provide
lots more details if needed here.

The NEW hard drive is a Seagate 160 GB "Barracuda" ATA HD, 7200 RPM,
which I used approx. 6 months in another computer, and removed it to
install a 500 GB SATA in that unit. This 160 GB was then reformatted
and used as the destination disk for cloning from the failing 160 GB
ATA, 7200 Maxtor drive which is at least 3 years old now.

Now, your next 2 questions are not easy ones to answer with any
certainty, since getting this entire system to work in all aspects has
forced me to try many, many things - some of which might have added to
my woes, admittedly. But as said in my original post, the new
motherboard demanded that it go through a complete setup where it
looked for drivers that I never expected. And it required my
inserting the CD provided with it, to get its own drivers. I failed
to keep record of what all this was. HOWEVER, when things got really
screwed up, I actually pulled out the new drive and stuck the old
failing one back in to check it out. The motherboard forced me to go
thru the same setup of looking for drivers that suited it, etc. And
it had a few problems also, but I got lucky and overcame them - all
but one! That one concerns Boot Magic, which does not come up
automatically, BUT if I use the Boot Magic 8.0 Rescue Disk, I can
choose which system to boot under. And then all 3 OS's run just as
they did earlier. SO, the "old failing" drive boots ok in Win 98 as
well as Win 2K and DOS. That's when I tried cloning over from that
old one (ONLY the W98 partition, though) to the new one. I did this
many different ways, and many different selected files from the backup
of the old drive's partition. So far, none of this has solved the
problem with the ERROR message on the New drive, as far as W98 is
concerned. Again, BOTH drives boot up and run fine in Win2K.

Remember, the above answer is partially related to the New drive, and
partially related to the Old drive. Both currently have a problem,
but the problem with the Old one is easy to live with - stick in the
BM Rescue disk. But that problem with the New one is intolerable, I
cannot use W98 on the New drive.

Now, let me ask a question out of total frustration. Is it possible
the Master Boot Record (MBR) got screwed up on the New one? And if
so, how to check and/or repair?

Finally, if I have a complete backup of both Win98 partitions off both
these drives - as they exist now, would it be useful to reformat the
New drive and do a New installation from the original factory CD, then
Restore from one of these backups? Or would I be right back where I
am now?

After all this time, I'm willing to try the above, just groping for
straws if it has a chance of working.

Olin McDaniel


On Sat, 2 Feb 2008 15:04:56 -0500, "MEB" <meb@not here@hotmail.com>
wrote:

>Hmm, no responses.. so to help the group to help you
>
> How about some information related to:
>
> What motherboard - make/model.
>
> What make and model hard drive, and is it SATA.or PATA, etc.. What is the
>old drive, make and model, SATA/PATA
>
> What had you [both recent and just] installed when the error first occurred
>[driver,application, etc.]
>
> The exact error message.
>
> Safe mode runs just base system drivers so likely the issue relates to
>something that was installed, hence the reason for the above. Kernel errors
>can be caused by numerous things from: other corrupted files, corrupted
>registry, to even a corrupted swap file, so we have to back-track through
>what occurred prior to the issue.
> Also, what system did you FIRST attempt to use after the change over [98 or
>2000]...
>
>--
>
>MEB
>http://peoplescounsel.orgfree.com
>_________
>
>
>"Olin K. McDaniel" <mcdanielo.abcd@bellsouth.net> wrote in message
>news:47a3a6c2.4965099@newsgroups.bellsouth.net...
>| Hopefully this won't get too longwinded, but as a bit of background, I
>| recently upgraded my hardware and wanted to keep all the software as
>| before. I installed a new M.B. and CPU to go from a 600MHz Pentium 3
>| unit to a 2.6 GHz Celeron unit. Also I cloned over the multiboot
>| OS's from drive 1 to another HD, since the older one was showing signs
>| of failing. The program used for cloning was Acronis True Image.
>| There were 3 OS's on Drive 1, and they also are now on the newly
>| installed HDD. The heart of the multiboot system is Powerquest's Boot
>| Magic, that has worked wonderfully for years. The 3 OS's are DOS 6.22
>| (rarely used anymore), Windows 98SE (most heavily used) and Windows
>| 2000 Pro (used somewhat).
>|
>| The problem developed subsequent to several days of allowing the new
>| M.B. and CPU to install all its drivers, etc.
>|
>| Essentially, I cannot boot up (on the NEW Hard Disk 1) into Win98SE in
>| Normal mode - I get an error message that says "Error loading KERNEL.
>| You must reinstall Windows". BUT - much to my annoyance, it WILL
>| boot up fully in SAFE mode. Nothing that I've tried has cleared up
>| this anomaly. I've followed the procedure found on MS's web site
>| which tells me to "extract Kernel32.dll" from my installation CD and
>| copy it to the folder Windows\System\, all to no avail, after multiple
>| efforts. In addition, I've copied it over from the presumed "failing"
>| hard drive, again with no success. I'm about ready to throw in the
>| towel - hopefully, someone can give me an out. Before someone asks,
>| there is NO problem booting up in Win2000 on this drive.
>|
>| Finally, as a further frustating fact, I can still do the multiboot if
>| I swap out the new HD 1 to the old failing one. But I don't trust it
>| lasting much longer.
>|
>| I'm admittedly out of ideas - and if it should be a problem with the
>| MBR, then I don't know how to repair it.
>|
>| Sorry it got this long - and it may not have all the useful info
>| someone might think would lead to a clue. If so, please tell me what
>| to check.
>|
>| Thanks, Olin McDaniel
>|
>| To reply by email, please remove "abcd" from Return address
>| -----------------------------------------------------
>| "Ignorance is treatable, Stupidity is incurable. Sometimes
>| the difference is hardly distinguishable, however."
>
>
>

To reply by email, please remove "abcd" from Return address
-----------------------------------------------------
"Ignorance is treatable, Stupidity is incurable. Sometimes
the difference is hardly distinguishable, however."

 

[PCR]

Olin K. McDaniel wrote:
| Hopefully this won't get too longwinded, but as a bit of background, I
| recently upgraded my hardware and wanted to keep all the software as
| before. I installed a new M.B. and CPU to go from a 600MHz Pentium 3
| unit to a 2.6 GHz Celeron unit.

Are you saying that only one machine is involved, & you replaced its MB
& CPU? So-- you now have a single machine that is 2.6 GHz? There is this
article to consider...

http://support.microsoft.com/default.aspx?scid=kben-us312108&Product=w98
Windows protection error in NDIS with a CPU that is faster than 2.1 GHz

HOWEVER... I think thankfully it does not apply to you, because you are
Win98SE (Second Edition). Also, you do not report that same error.
Finally, I believe you may have said the old HDD still will work on the
faster machine.

| Also I cloned over the multiboot
| OS's from drive 1 to another HD, since the older one was showing signs
| of failing.

The machine had only one HDD? Then, it is called HDD0-- they start
counting them at zero.

| The program used for cloning was Acronis True Image.
| There were 3 OS's on Drive 1, and they also are now on the newly
| installed HDD.

You cloned HDD0 to a new HDD. Yea, as MEB requested-- describe the two
HDD. What are their size & type?

| The heart of the multiboot system is Powerquest's Boot
| Magic, that has worked wonderfully for years. The 3 OS's are DOS 6.22
| (rarely used anymore), Windows 98SE (most heavily used) and Windows
| 2000 Pro (used somewhat).

I don't know BootMagic. Does it seem to have been copied over to the new
HDD by TrueImage? (I don't know TrueImage, either.) Or do you think you
might need to install it separately? Did you copy the 3 partitions over
to the new HDD in the same order they are on the old drive?

| The problem developed subsequent to several days of allowing the new
| M.B. and CPU to install all its drivers, etc.

Describe what you did to accomplish that? How do things look in Device
Manager in Safe Mode-- any red/yellow ?/!'s on any devices?

| Essentially, I cannot boot up (on the NEW Hard Disk 1) into Win98SE in
| Normal mode - I get an error message that says "Error loading KERNEL.
| You must reinstall Windows". BUT - much to my annoyance, it WILL
| boot up fully in SAFE mode. Nothing that I've tried has cleared up
| this anomaly. I've followed the procedure found on MS's web site
| which tells me to "extract Kernel32.dll" from my installation CD and
| copy it to the folder Windows\System\, all to no avail, after multiple
| efforts.

Yea. I see that article...
http://support.microsoft.com/kb/146419
Error Loading Kernel. You Must Reinstall Windows

You did it right! Too bad it didn't work!

http://www.google.com/search?hl=en&q=Error+Loading+Kernel&btnG=Google+Search
Google finds about 138,000 for Error Loading Kernel

| In addition, I've copied it over from the presumed "failing"
| hard drive, again with no success. I'm about ready to throw in the
| towel - hopefully, someone can give me an out. Before someone asks,
| there is NO problem booting up in Win2000 on this drive.
|
| Finally, as a further frustating fact, I can still do the multiboot if
| I swap out the new HD 1 to the old failing one. But I don't trust it
| lasting much longer.

What are you saying-- just that you get a menu from BootMagic? Or can
you be saying Win98 will actually boot from the old drive? How did the
new drive boot to Win98SE Safe Mode-- through a BootMagic screen? How
did it boot to Win2K?

| I'm admittedly out of ideas - and if it should be a problem with the
| MBR, then I don't know how to repair it.

I don't know TrueImage or BootMagic. What does the process of copying a
partition to a new hard drive normally entail? Are there extra steps to
do in its instructions in order to make the drive bootable? Did you do
them? Looks like you do boot to Win98SE Safe Mode & fully to Win2K. SO--
something must be right. As far as BootMagic, what is it like to install
it? Maybe try that on the new drive, just in case TrueImage didn't get
all of it.

| Sorry it got this long - and it may not have all the useful info
| someone might think would lead to a clue. If so, please tell me what
| to check.

Keep at it. I think you are close, if you get to Safe Mode. But how are
you getting there?

| Thanks, Olin McDaniel

You are welcome.

| To reply by email, please remove "abcd" from Return address
| -----------------------------------------------------
| "Ignorance is treatable, Stupidity is incurable. Sometimes
| the difference is hardly distinguishable, however."

--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
Should things get worse after this,
PCR
pcrrcp@netzero.net

 

[MEB]

"Olin K. McDaniel" <mcdanielo.abcd@bellsouth.net> wrote in message
news:47a4ecf2.283194@newsgroups.bellsouth.net...
| OK, I'll provide what I can, but it will be impossible to remember all
| the things you asked, since this has been an ongoing problem for over
| 3 weeks.
|
| First - the exact message was stated in my original post, i.e. "Error
| loading KERNEL. You must reinstall Windows". That's it, no more, no
| less.

Okay, I have had that occur more than once...

|
| The newly installed motherboard is a Biostar P4M80-M4. I can provide
| lots more details if needed here.

Not a the moment, this will allow background review of drivers/etc..

OS support - Win98SE/ME/NT4/2K/XP/64 - onsite drivers seem to be
2004/5-7[XP/64]

http://www.biostar-usa.com/mbdetails.asp?model=p4m80-m4 - general
description
ftp://ftp.biostar-usa.com/manuals/P4M80-M4/P4M80M4manual.pdf - manual

Looks like a nice board for 98. Not thrilled with the S3 on-board video
though.. but that's just me..

To clarify for the group, BootMagic is/was part of PartionMagic.

|
| The NEW hard drive is a Seagate 160 GB "Barracuda" ATA HD, 7200 RPM,
| which I used approx. 6 months in another computer, and removed it to
| install a 500 GB SATA in that unit. This 160 GB was then reformatted
| and used as the destination disk for cloning from the failing 160 GB
| ATA, 7200 Maxtor drive which is at least 3 years old now.

Okay, just to clarify, though you mention a 500gig drive we are NOT talking
about it as part of the issues.

The two drives at issue are 160 gig. One was apparently failing and relaced
by the Seagate. Was that drive 'cut" to the 137 gig barrier or is it full
capacity?

Was the Maxtor "cut" or was it allowed to remain at full capacity?

Also, was the machine the Seagate was pulled from XP or VISTA?

These questions are to determine potentials.

|
| Now, your next 2 questions are not easy ones to answer with any
| certainty, since getting this entire system to work in all aspects has
| forced me to try many, many things - some of which might have added to
| my woes, admittedly. But as said in my original post, the new
| motherboard demanded that it go through a complete setup where it
| looked for drivers that I never expected. And it required my
| inserting the CD provided with it, to get its own drivers. I failed
| to keep record of what all this was. HOWEVER, when things got really
| screwed up, I actually pulled out the new drive and stuck the old
| failing one back in to check it out. The motherboard forced me to go
| thru the same setup of looking for drivers that suited it, etc. And
| it had a few problems also, but I got lucky and overcame them - all
| but one! That one concerns Boot Magic, which does not come up
| automatically, BUT if I use the Boot Magic 8.0 Rescue Disk, I can
| choose which system to boot under. And then all 3 OS's run just as
| they did earlier. SO, the "old failing" drive boots ok in Win 98 as
| well as Win 2K and DOS. That's when I tried cloning over from that
| old one (ONLY the W98 partition, though) to the new one. I did this
| many different ways, and many different selected files from the backup
| of the old drive's partition. So far, none of this has solved the
| problem with the ERROR message on the New drive, as far as W98 is
| concerned. Again, BOTH drives boot up and run fine in Win2K.

Okay, two others have provided suggestions, Glen [and PCR] directs to some
viable issues [cleaning old drivers] to attempt to start with. Perhaps he
will again place the Registry entries suggested at removal when making major
changes in the 9X OS due to hardware changes. This will mean re-installing
the MB drivers and other AGAIN.

PCR caught the issues with the Boot, and I'll add that depending upon how
the drive was cloned [what you chose to image], and formatted, the Boot
partition [BootMagic] may not be properly setup [clusters/sectors may be off
or other]. Manufactures use differring adapter chips and routines, and the
BIOS will translate somewhat differently, BootMagic may be having
difficulties. Reinstalling/reconfiguring the boot manager, if possible
without destroying the data/files, might help though Scandisk will
sometimes correct those issues if not to drastic [you have all
OSs/partitions as either Fat16 or 32 correct?]. 2K can better handle
cluster/sector issues [self-repair], but that leaves DOS and 98 out in the
cold.

|
| Remember, the above answer is partially related to the New drive, and
| partially related to the Old drive. Both currently have a problem,
| but the problem with the Old one is easy to live with - stick in the
| BM Rescue disk. But that problem with the New one is intolerable, I
| cannot use W98 on the New drive.

I certainly hope you changed/checked the BIOS when you installed the new
drive. If the drives are set to AUTO detect then you can negate that issue,
though hopefully you also checked the other settings.as well.

|
| Now, let me ask a question out of total frustration. Is it possible
| the Master Boot Record (MBR) got screwed up on the New one? And if
| so, how to check and/or repair?

Possible, but let's deal with these other potential fixes first.

|
| Finally, if I have a complete backup of both Win98 partitions off both
| these drives - as they exist now, would it be useful to reformat the
| New drive and do a New installation from the original factory CD, then
| Restore from one of these backups? Or would I be right back where I
| am now?

The clean install would be the best recourse, but once you over-install
[copying the old over the new], you're right back here again. The issues
seem to relate to the drive layout and the registry. Work through the
suggestions and Post back with issues or results.

|
| After all this time, I'm willing to try the above, just groping for
| straws if it has a chance of working.
|
| Olin McDaniel
|

--

MEB
http://peoplescounsel.orgfree.com
_________

| >"Olin K. McDaniel" <mcdanielo.abcd@bellsouth.net> wrote in message
| >news:47a3a6c2.4965099@newsgroups.bellsouth.net...
| >| Hopefully this won't get too longwinded, but as a bit of background, I
| >| recently upgraded my hardware and wanted to keep all the software as
| >| before. I installed a new M.B. and CPU to go from a 600MHz Pentium 3
| >| unit to a 2.6 GHz Celeron unit. Also I cloned over the multiboot
| >| OS's from drive 1 to another HD, since the older one was showing signs
| >| of failing. The program used for cloning was Acronis True Image.
| >| There were 3 OS's on Drive 1, and they also are now on the newly
| >| installed HDD. The heart of the multiboot system is Powerquest's Boot
| >| Magic, that has worked wonderfully for years. The 3 OS's are DOS 6.22
| >| (rarely used anymore), Windows 98SE (most heavily used) and Windows
| >| 2000 Pro (used somewhat).
| >|
| >| The problem developed subsequent to several days of allowing the new
| >| M.B. and CPU to install all its drivers, etc.
| >|
| >| Essentially, I cannot boot up (on the NEW Hard Disk 1) into Win98SE in
| >| Normal mode - I get an error message that says "Error loading KERNEL.
| >| You must reinstall Windows". BUT - much to my annoyance, it WILL
| >| boot up fully in SAFE mode. Nothing that I've tried has cleared up
| >| this anomaly. I've followed the procedure found on MS's web site
| >| which tells me to "extract Kernel32.dll" from my installation CD and
| >| copy it to the folder Windows\System\, all to no avail, after multiple
| >| efforts. In addition, I've copied it over from the presumed "failing"
| >| hard drive, again with no success. I'm about ready to throw in the
| >| towel - hopefully, someone can give me an out. Before someone asks,
| >| there is NO problem booting up in Win2000 on this drive.
| >|
| >| Finally, as a further frustating fact, I can still do the multiboot if
| >| I swap out the new HD 1 to the old failing one. But I don't trust it
| >| lasting much longer.
| >|
| >| I'm admittedly out of ideas - and if it should be a problem with the
| >| MBR, then I don't know how to repair it.
| >|
| >| Sorry it got this long - and it may not have all the useful info
| >| someone might think would lead to a clue. If so, please tell me what
| >| to check.
| >|
| >| Thanks, Olin McDaniel
| >|
| >| To reply by email, please remove "abcd" from Return address
| >| -----------------------------------------------------
| >| "Ignorance is treatable, Stupidity is incurable. Sometimes
| >| the difference is hardly distinguishable, however."
| >
| >
| >
|
| To reply by email, please remove "abcd" from Return address
| -----------------------------------------------------
| "Ignorance is treatable, Stupidity is incurable. Sometimes
| the difference is hardly distinguishable, however."

 

[Olin K. McDaniel]

On Sat, 2 Feb 2008 18:43:41 -0500, "PCR" <pcrrcp@netzero.net> wrote:

>Olin K. McDaniel wrote:
>| Hopefully this won't get too longwinded, but as a bit of background, I
>| recently upgraded my hardware and wanted to keep all the software as
>| before. I installed a new M.B. and CPU to go from a 600MHz Pentium 3
>| unit to a 2.6 GHz Celeron unit.
>
>Are you saying that only one machine is involved, & you replaced its MB
>& CPU? So-- you now have a single machine that is 2.6 GHz? There is this
>article to consider...
>
>http://support.microsoft.com/default.aspx?scid=kben-us312108&Product=w98
>Windows protection error in NDIS with a CPU that is faster than 2.1 GHz
>
>HOWEVER... I think thankfully it does not apply to you, because you are
>Win98SE (Second Edition). Also, you do not report that same error.
>Finally, I believe you may have said the old HDD still will work on the
>faster machine.
>
>| Also I cloned over the multiboot
>| OS's from drive 1 to another HD, since the older one was showing signs
>| of failing.
>
>The machine had only one HDD?

NO! I thought I said it had a total of 3 hard drives, but maybe not.
Regardless, the problem only exists with the boot drive with all 3
OS's on it.

>Then, it is called HDD0-- they start
>counting them at zero.

Yep, I know about that, in one context. However in the context that's
used by Partition Magic, they do not use that system. They number
them Drive 1, Drive 2, etc. I've simply become more comfortable with
Partition Magic and thus chose their system.

>
>| The program used for cloning was Acronis True Image.
>| There were 3 OS's on Drive 1, and they also are now on the newly
>| installed HDD.
>
>You cloned HDD0 to a new HDD. Yea, as MEB requested-- describe the two
>HDD. What are their size & type?

See my earlier post for answer to this
>
>| The heart of the multiboot system is Powerquest's Boot
>| Magic, that has worked wonderfully for years. The 3 OS's are DOS 6.22
>| (rarely used anymore), Windows 98SE (most heavily used) and Windows
>| 2000 Pro (used somewhat).
>
>I don't know BootMagic. Does it seem to have been copied over to the new
>HDD by TrueImage? (I don't know TrueImage, either.) Or do you think you
>might need to install it separately? Did you copy the 3 partitions over
>to the new HDD in the same order they are on the old drive?

Let's clarify this. Boot Magic is a subset of PowerQuest's Partition
Magic, at least the version I use. Some one else bought them out, and
it's now sold under a different Brand, maybe like Syquest (?), I'm not
sure. Boot Magic is specific for installing onto one
partition/Operating system to allow selection of a current choice of
which OS to use. (I believe it only worked when I put it on Win2000).
However I do have Partition Magic installed in both W98 and W2K.

Further, Partition Magic allows a lot of copying over, etc. but it has
its limitations. When I found this new Acronis TrueImage, I found it
had managed to overcome those limitations. SO, when I copied all 3 of
the hard drives, I did so with Acronis. There are several modes for
doing so, some can cause grief - so I was careful to use the Manual
mode and tell it to copy everything exactly as it was on the original,
and to not "expand" the partitions, even if more space was available.
(Then later I could, and did, go back and use Partition Magic to do
that expansion as desired/needed. All of this manipulation went
without problems, as proven by the success with the other two hard
drives which are fully accessible - IF the OS can boot properly!!!!

>| The problem developed subsequent to several days of allowing the new
>| M.B. and CPU to install all its drivers, etc.
>
>Describe what you did to accomplish that? How do things look in Device
>Manager in Safe Mode-- any red/yellow ?/!'s on any devices?
>
>| Essentially, I cannot boot up (on the NEW Hard Disk 1) into Win98SE in
>| Normal mode - I get an error message that says "Error loading KERNEL.
>| You must reinstall Windows". BUT - much to my annoyance, it WILL
>| boot up fully in SAFE mode. Nothing that I've tried has cleared up
>| this anomaly. I've followed the procedure found on MS's web site
>| which tells me to "extract Kernel32.dll" from my installation CD and
>| copy it to the folder Windows\System\, all to no avail, after multiple
>| efforts.
>
>Yea. I see that article...
>http://support.microsoft.com/kb/146419
>Error Loading Kernel. You Must Reinstall Windows
>
>You did it right! Too bad it didn't work!
>
>http://www.google.com/search?hl=en&q=Error+Loading+Kernel&btnG=Google+Search
>Google finds about 138,000 for Error Loading Kernel
>
>| In addition, I've copied it over from the presumed "failing"
>| hard drive, again with no success. I'm about ready to throw in the
>| towel - hopefully, someone can give me an out. Before someone asks,
>| there is NO problem booting up in Win2000 on this drive.
>|
>| Finally, as a further frustating fact, I can still do the multiboot if
>| I swap out the new HD 1 to the old failing one. But I don't trust it
>| lasting much longer.
>
>What are you saying-- just that you get a menu from BootMagic? Or can
>you be saying Win98 will actually boot from the old drive? How did the
>new drive boot to Win98SE Safe Mode-- through a BootMagic screen? How
>did it boot to Win2K?

Let's elaborate a little bit here, if you insist. With the New drive
in #1 (or call it #0 if you wish), I get the correct menu after going
thru the POST steps. This menu is that provided by Boot Magic. It
gives me 3 choices from which to Boot. DOS, W98 and W2000. I have
set it up for W98 as the Default, but that's simple to change. Also I
can Disable Boot Magic very simply, if desired. (Remember, all this
is on drive #1 and presumably exists on both the Old and the New
drives, but it only works FULLY on the New.) If I then choose W98 to
boot, that's when it gives the Error message, and insists on
restarting in Safe mode.

Again, to restate, the Old drive does not give me this menu choice,
but I think that's readily fixable. I've chosen not to screw with it
yet, rather just use the BM rescue disk to make my choice, and then I
can boot successfully on either of the OS's. SO - my Main effort is
in trying to fix the New drive in the #1 spot. Any other effort ahead
of that is a waste of time and probably counterproductive.

>
>| I'm admittedly out of ideas - and if it should be a problem with the
>| MBR, then I don't know how to repair it.
>
>I don't know TrueImage or BootMagic. What does the process of copying a
>partition to a new hard drive normally entail? Are there extra steps to
>do in its instructions in order to make the drive bootable? Did you do
>them? Looks like you do boot to Win98SE Safe Mode & fully to Win2K. SO--
>something must be right. As far as BootMagic, what is it like to install
>it? Maybe try that on the new drive, just in case TrueImage didn't get
>all of it.

Hopefully the above 2 answers covers most of these questions also.
Although I've never successfully used GHOST, my understanding is that
True Image does much the same thing, and even more simply and with
less complications. I assure you that careful reading of its
instructions at each step of the way SHOULD allow most people to do it
without messing up. The fact that I successfully cloned over the
other 2 hard drives with it, should attest to the fact that I followed
their instructions correctly.
>
>| Sorry it got this long - and it may not have all the useful info
>| someone might think would lead to a clue. If so, please tell me what
>| to check.
>
>Keep at it. I think you are close, if you get to Safe Mode. But how are
>you getting there?

Should be adequately answered above.

>
>| Thanks, Olin McDaniel
>
>You are welcome.
>
>--
>Thanks or Good Luck,
>There may be humor in this post, and,
>Naturally, you will not sue,
>Should things get worse after this,
>PCR
>pcrrcp@netzero.net
>
>
Olin McDaniel

To reply by email, please remove "abcd" from Return address
-----------------------------------------------------
"Ignorance is treatable, Stupidity is incurable. Sometimes
the difference is hardly distinguishable, however."

 

[Olin K. McDaniel]

On Sat, 2 Feb 2008 17:43:32 -0500, "glee" <glee29@spamindspring.com>
wrote:

>When you are going to change major hardware such as the motherboard and processor,
>you first need to remove the drivers for everything that is part of that
>hardware.....chipset drivers, onboard audio and video, onboard LAN, floppy
>controller, hard drive controllers, and so forth. If you did not do that before
>changing the hardware, you should do it now from Safe Mode in Win98, as that is the
>OS giving you trouble.
>
>Click Start>Run, type: scanregw
>|click OK|
>When prompted, say Yes to backing up the Registry.
>
>Next, if your old or new motherboard uses onmboard video rather than a dedicated
>video card, uninstall any display software and drivers, allowing Windows to change
>your display adapter to Standard VGA 640x480, and reboot if prompted. Then
>uninstall any audio software and drivers that are not part of the new system.
>
>Now restart in Safe Mode, open Device Manager, expand all categories and start
>removing devices.
>You pretty much need to remove everything except the keyboard/mouse/monitor,
>including all the items in the System section of Device Manager as well as in the
>Other section, the USB Controllers section, all other drives and controllers,
>display adapters, audio controllers, network adapter.
>
>Click OK to close, then start in normal mode. Windows will begin detecting
>hardware....when it finds the primary IDE controller and wants to reboot, say no and
>let it find the secondary IDE controller too, then reboot at that prompt.
>The next restart should find the rest of the current hardware, while the remnants of
>the old hardware will no longer be present.
>
>Be sure to then install the chipset drivers from the disc that came with your new
>motherboard, reboot, then install the drivers for your display, audio and so forth.
>
>An alternative to deleting individual items in Safe Mode Device Manager, is to open
>the Registry Editor and delete the entire Enum key at this location:
>HKEY_LOCAL_MACHINE\Enum
>Then, shutdown, move the hard drive to the new system, and follow the suggestions
>above.
>The Safe Mode method is usually safer.
>--
>Glen Ventura, MS MVP Shell/User, A+
>http://dts-l.net/
>http://dts-l.net/goodpost.htm
>
>
Thanks Glen. But as I read your suggestions, I have to wonder how
they apply to what I posted. The replacement of the motherboard and
CPU was done weeks before the problem I was trying to fix ever showed
its head. SO, maybe I didn't do the "replacement" or "upgrade"
properly, it's nice to know how to do it the next time (assuming there
will be a next time), but that doesn't fix the current problem. Does
it?

Olin



>"Olin K. McDaniel" <mcdanielo.abcd@bellsouth.net> wrote in message
>news:47a3a6c2.4965099@newsgroups.bellsouth.net...
>> Hopefully this won't get too longwinded, but as a bit of background, I
>> recently upgraded my hardware and wanted to keep all the software as
>> before. I installed a new M.B. and CPU to go from a 600MHz Pentium 3
>> unit to a 2.6 GHz Celeron unit. Also I cloned over the multiboot
>> OS's from drive 1 to another HD, since the older one was showing signs
>> of failing. The program used for cloning was Acronis True Image.
>> There were 3 OS's on Drive 1, and they also are now on the newly
>> installed HDD. The heart of the multiboot system is Powerquest's Boot
>> Magic, that has worked wonderfully for years. The 3 OS's are DOS 6.22
>> (rarely used anymore), Windows 98SE (most heavily used) and Windows
>> 2000 Pro (used somewhat).
>>
>> The problem developed subsequent to several days of allowing the new
>> M.B. and CPU to install all its drivers, etc.
>>
>> Essentially, I cannot boot up (on the NEW Hard Disk 1) into Win98SE in
>> Normal mode - I get an error message that says "Error loading KERNEL.
>> You must reinstall Windows". BUT - much to my annoyance, it WILL
>> boot up fully in SAFE mode. Nothing that I've tried has cleared up
>> this anomaly. I've followed the procedure found on MS's web site
>> which tells me to "extract Kernel32.dll" from my installation CD and
>> copy it to the folder Windows\System\, all to no avail, after multiple
>> efforts. In addition, I've copied it over from the presumed "failing"
>> hard drive, again with no success. I'm about ready to throw in the
>> towel - hopefully, someone can give me an out. Before someone asks,
>> there is NO problem booting up in Win2000 on this drive.
>>
>> Finally, as a further frustating fact, I can still do the multiboot if
>> I swap out the new HD 1 to the old failing one. But I don't trust it
>> lasting much longer.
>>
>> I'm admittedly out of ideas - and if it should be a problem with the
>> MBR, then I don't know how to repair it.
>>
>> Sorry it got this long - and it may not have all the useful info
>> someone might think would lead to a clue. If so, please tell me what
>> to check.
>>
>> Thanks, Olin McDaniel
>>
>> To reply by email, please remove "abcd" from Return address
>> -----------------------------------------------------
>> "Ignorance is treatable, Stupidity is incurable. Sometimes
>> the difference is hardly distinguishable, however."
>

To reply by email, please remove "abcd" from Return address
-----------------------------------------------------
"Ignorance is treatable, Stupidity is incurable. Sometimes
the difference is hardly distinguishable, however."

 

[Olin K. McDaniel]

On Sun, 3 Feb 2008 03:39:49 -0500, "MEB" <meb@not here@hotmail.com>
wrote:

>
>
>"Olin K. McDaniel" <mcdanielo.abcd@bellsouth.net> wrote in message
>news:47a4ecf2.283194@newsgroups.bellsouth.net...
>| OK, I'll provide what I can, but it will be impossible to remember all
>| the things you asked, since this has been an ongoing problem for over
>| 3 weeks.
>|
>| First - the exact message was stated in my original post, i.e. "Error
>| loading KERNEL. You must reinstall Windows". That's it, no more, no
>| less.
>
> Okay, I have had that occur more than once...
>
>|
>| The newly installed motherboard is a Biostar P4M80-M4. I can provide
>| lots more details if needed here.
>
> Not a the moment, this will allow background review of drivers/etc..
>
>OS support - Win98SE/ME/NT4/2K/XP/64 - onsite drivers seem to be
>2004/5-7[XP/64]
>
>http://www.biostar-usa.com/mbdetails.asp?model=p4m80-m4 - general
>description
>ftp://ftp.biostar-usa.com/manuals/P4M80-M4/P4M80M4manual.pdf - manual
>
> Looks like a nice board for 98. Not thrilled with the S3 on-board video
>though.. but that's just me..

I do not currently use the on-board video nor the sound. I do use the
on-board LAN for DSL though, as opposed to a PCI card before upgrading
motherboards.

> To clarify for the group, BootMagic is/was part of PartionMagic.
>
>|
>| The NEW hard drive is a Seagate 160 GB "Barracuda" ATA HD, 7200 RPM,
>| which I used approx. 6 months in another computer, and removed it to
>| install a 500 GB SATA in that unit. This 160 GB was then reformatted
>| and used as the destination disk for cloning from the failing 160 GB
>| ATA, 7200 Maxtor drive which is at least 3 years old now.
>
> Okay, just to clarify, though you mention a 500gig drive we are NOT talking
>about it as part of the issues.

That is correct. The 500 GB SATA drive was installed in another
computer that I use for different purposes.
>
> The two drives at issue are 160 gig. One was apparently failing and relaced
>by the Seagate. Was that drive 'cut" to the 137 gig barrier or is it full
>capacity?
>
Let's go back thru how things had to be done. First of all, the old
motherboard DID have the 137 GB limit, so - the "old" 160 GB drive
(which was the Maxtor, incidentally) was limited by the motherboard's
137 limit.

Then after upgrading the motherboard, that Maxtor drive was still
unexpanded, even though I could have. That's when I used Acronis True
Image to clone that drive, plus the other 2 drives. I cloned that
Maxtor "EXACTLY" as it existed to the new Seagate - all this being
done under Windows 2000 since that's where I installed Acronis.

Next, I swapped the 160 GB drives, and at some point (no longer am
able to remember exactly when) I used Partition Magic to expand the
top partition of the drive containing Win2000 (but the NEW DRIVE
ONLY) to fill up the Unallocated space. All this may or may not be
important, but at the present time, the "Old" drive is still
unexpanded, and the "New" drive is expanded. That's exactly why I
keep asking if that expansion is what screwed up the "New" drive, by
messing up the MBR or something else. So far, no one has answered
that question for me.

> Was the Maxtor "cut" or was it allowed to remain at full capacity?

See above answers.
>
> Also, was the machine the Seagate was pulled from XP or VISTA?
>
NEGATIVE! I refuse to use either of those. It was pulled from a
machine using Windows 2000 Professional.

> These questions are to determine potentials.

Hope my answers suffice.
>
>|
>| Now, your next 2 questions are not easy ones to answer with any
>| certainty, since getting this entire system to work in all aspects has
>| forced me to try many, many things - some of which might have added to
>| my woes, admittedly. But as said in my original post, the new
>| motherboard demanded that it go through a complete setup where it
>| looked for drivers that I never expected. And it required my
>| inserting the CD provided with it, to get its own drivers. I failed
>| to keep record of what all this was. HOWEVER, when things got really
>| screwed up, I actually pulled out the new drive and stuck the old
>| failing one back in to check it out. The motherboard forced me to go
>| thru the same setup of looking for drivers that suited it, etc. And
>| it had a few problems also, but I got lucky and overcame them - all
>| but one! That one concerns Boot Magic, which does not come up
>| automatically, BUT if I use the Boot Magic 8.0 Rescue Disk, I can
>| choose which system to boot under. And then all 3 OS's run just as
>| they did earlier. SO, the "old failing" drive boots ok in Win 98 as
>| well as Win 2K and DOS. That's when I tried cloning over from that
>| old one (ONLY the W98 partition, though) to the new one. I did this
>| many different ways, and many different selected files from the backup
>| of the old drive's partition. So far, none of this has solved the
>| problem with the ERROR message on the New drive, as far as W98 is
>| concerned. Again, BOTH drives boot up and run fine in Win2K.
>
> Okay, two others have provided suggestions, Glen [and PCR] directs to some
>viable issues [cleaning old drivers] to attempt to start with. Perhaps he
>will again place the Registry entries suggested at removal when making major
>changes in the 9X OS due to hardware changes. This will mean re-installing
>the MB drivers and other AGAIN.
>
> PCR caught the issues with the Boot, and I'll add that depending upon how
>the drive was cloned [what you chose to image], and formatted, the Boot
>partition [BootMagic] may not be properly setup [clusters/sectors may be off
>or other]. Manufactures use differring adapter chips and routines, and the
>BIOS will translate somewhat differently, BootMagic may be having
>difficulties. Reinstalling/reconfiguring the boot manager, if possible
>without destroying the data/files, might help though Scandisk will
>sometimes correct those issues if not to drastic [you have all
>OSs/partitions as either Fat16 or 32 correct?]. 2K can better handle
>cluster/sector issues [self-repair], but that leaves DOS and 98 out in the
>cold.
>
>|
>| Remember, the above answer is partially related to the New drive, and
>| partially related to the Old drive. Both currently have a problem,
>| but the problem with the Old one is easy to live with - stick in the
>| BM Rescue disk. But that problem with the New one is intolerable, I
>| cannot use W98 on the New drive.
>
> I certainly hope you changed/checked the BIOS when you installed the new
>drive. If the drives are set to AUTO detect then you can negate that issue,
>though hopefully you also checked the other settings.as well.
>
>|
>| Now, let me ask a question out of total frustration. Is it possible
>| the Master Boot Record (MBR) got screwed up on the New one? And if
>| so, how to check and/or repair?
>
> Possible, but let's deal with these other potential fixes first.
>
>|
>| Finally, if I have a complete backup of both Win98 partitions off both
>| these drives - as they exist now, would it be useful to reformat the
>| New drive and do a New installation from the original factory CD, then
>| Restore from one of these backups? Or would I be right back where I
>| am now?
>
> The clean install would be the best recourse, but once you over-install
>[copying the old over the new], you're right back here again. The issues
>seem to relate to the drive layout and the registry. Work through the
>suggestions and Post back with issues or results.
>
>|
>| After all this time, I'm willing to try the above, just groping for
>| straws if it has a chance of working.
>|
>| Olin McDaniel
>|
>
>--
>
>MEB
>http://peoplescounsel.orgfree.com
>_________
>
>| >"Olin K. McDaniel" <mcdanielo.abcd@bellsouth.net> wrote in message
>| >news:47a3a6c2.4965099@newsgroups.bellsouth.net...
>| >| Hopefully this won't get too longwinded, but as a bit of background, I
>| >| recently upgraded my hardware and wanted to keep all the software as
>| >| before. I installed a new M.B. and CPU to go from a 600MHz Pentium 3
>| >| unit to a 2.6 GHz Celeron unit. Also I cloned over the multiboot
>| >| OS's from drive 1 to another HD, since the older one was showing signs
>| >| of failing. The program used for cloning was Acronis True Image.
>| >| There were 3 OS's on Drive 1, and they also are now on the newly
>| >| installed HDD. The heart of the multiboot system is Powerquest's Boot
>| >| Magic, that has worked wonderfully for years. The 3 OS's are DOS 6.22
>| >| (rarely used anymore), Windows 98SE (most heavily used) and Windows
>| >| 2000 Pro (used somewhat).
>| >|
>| >| The problem developed subsequent to several days of allowing the new
>| >| M.B. and CPU to install all its drivers, etc.
>| >|
>| >| Essentially, I cannot boot up (on the NEW Hard Disk 1) into Win98SE in
>| >| Normal mode - I get an error message that says "Error loading KERNEL.
>| >| You must reinstall Windows". BUT - much to my annoyance, it WILL
>| >| boot up fully in SAFE mode. Nothing that I've tried has cleared up
>| >| this anomaly. I've followed the procedure found on MS's web site
>| >| which tells me to "extract Kernel32.dll" from my installation CD and
>| >| copy it to the folder Windows\System\, all to no avail, after multiple
>| >| efforts. In addition, I've copied it over from the presumed "failing"
>| >| hard drive, again with no success. I'm about ready to throw in the
>| >| towel - hopefully, someone can give me an out. Before someone asks,
>| >| there is NO problem booting up in Win2000 on this drive.
>| >|
>| >| Finally, as a further frustating fact, I can still do the multiboot if
>| >| I swap out the new HD 1 to the old failing one. But I don't trust it
>| >| lasting much longer.
>| >|
>| >| I'm admittedly out of ideas - and if it should be a problem with the
>| >| MBR, then I don't know how to repair it.
>| >|
>| >| Sorry it got this long - and it may not have all the useful info
>| >| someone might think would lead to a clue. If so, please tell me what
>| >| to check.
>| >|
>| >| Thanks, Olin McDaniel
>| >|

To reply by email, please remove "abcd" from Return address
-----------------------------------------------------
"Ignorance is treatable, Stupidity is incurable. Sometimes
the difference is hardly distinguishable, however."

 

[glee]

"Olin K. McDaniel" <mcdanielo.abcd@bellsouth.net> wrote in message
news:47a72f45.837275@newsgroups.bellsouth.net...
> On Sat, 2 Feb 2008 17:43:32 -0500, "glee" <glee29@spamindspring.com>
> wrote:
>
>>When you are going to change major hardware such as the motherboard and processor,
>>you first need to remove the drivers for everything that is part of that
>>hardware.....chipset drivers, onboard audio and video, onboard LAN, floppy
>>controller, hard drive controllers, and so forth. If you did not do that before
>>changing the hardware, you should do it now from Safe Mode in Win98, as that is
>>the
>>OS giving you trouble.
>>
>>Click Start>Run, type: scanregw
>>|click OK|
>>When prompted, say Yes to backing up the Registry.
>>
>>Next, if your old or new motherboard uses onmboard video rather than a dedicated
>>video card, uninstall any display software and drivers, allowing Windows to change
>>your display adapter to Standard VGA 640x480, and reboot if prompted. Then
>>uninstall any audio software and drivers that are not part of the new system.
>>
>>Now restart in Safe Mode, open Device Manager, expand all categories and start
>>removing devices.
>>You pretty much need to remove everything except the keyboard/mouse/monitor,
>>including all the items in the System section of Device Manager as well as in the
>>Other section, the USB Controllers section, all other drives and controllers,
>>display adapters, audio controllers, network adapter.
>>
>>Click OK to close, then start in normal mode. Windows will begin detecting
>>hardware....when it finds the primary IDE controller and wants to reboot, say no
>>and
>>let it find the secondary IDE controller too, then reboot at that prompt.
>>The next restart should find the rest of the current hardware, while the remnants
>>of
>>the old hardware will no longer be present.
>>
>>Be sure to then install the chipset drivers from the disc that came with your new
>>motherboard, reboot, then install the drivers for your display, audio and so
>>forth.
>>
>>An alternative to deleting individual items in Safe Mode Device Manager, is to
>>open
>>the Registry Editor and delete the entire Enum key at this location:
>>HKEY_LOCAL_MACHINE\Enum
>>Then, shutdown, move the hard drive to the new system, and follow the suggestions
>>above.
>>The Safe Mode method is usually safer.
>
> Thanks Glen. But as I read your suggestions, I have to wonder how
> they apply to what I posted. The replacement of the motherboard and
> CPU was done weeks before the problem I was trying to fix ever showed
> its head. SO, maybe I didn't do the "replacement" or "upgrade"
> properly, it's nice to know how to do it the next time (assuming there
> will be a next time), but that doesn't fix the current problem. Does
> it?
>
> Olin

Apparently you missed this sentence in my original reply:

"If you did not do that before changing the hardware, you should do it now from Safe
Mode in Win98, as that is the OS giving you trouble."

I am describing what needs to be tried NOW.
--
Glen Ventura, MS MVP Shell/User, A+
http://dts-l.net/
http://dts-l.net/goodpost.htm

 

[MEB]

"Olin K. McDaniel" <mcdanielo.abcd@bellsouth.net> wrote in message
news:47a7305e.1118393@newsgroups.bellsouth.net...
| On Sun, 3 Feb 2008 03:39:49 -0500, "MEB" <meb@not here@hotmail.com>
| wrote:
| >"Olin K. McDaniel" <mcdanielo.abcd@bellsouth.net> wrote in message
| >news:47a4ecf2.283194@newsgroups.bellsouth.net...
| >| OK, I'll provide what I can, but it will be impossible to remember all
| >| the things you asked, since this has been an ongoing problem for over
| >| 3 weeks.
| >|
| >| First - the exact message was stated in my original post, i.e. "Error
| >| loading KERNEL. You must reinstall Windows". That's it, no more, no
| >| less.
| >
| > Okay, I have had that occur more than once...
| >
| >|
| >| The newly installed motherboard is a Biostar P4M80-M4. I can provide
| >| lots more details if needed here.
| >
| > Not a the moment, this will allow background review of drivers/etc..
| >
| >OS support - Win98SE/ME/NT4/2K/XP/64 - onsite drivers seem to be
| >2004/5-7[XP/64]
| >
| >http://www.biostar-usa.com/mbdetails.asp?model=p4m80-m4 - general
| >description
| >ftp://ftp.biostar-usa.com/manuals/P4M80-M4/P4M80M4manual.pdf - manual
| >
| > Looks like a nice board for 98. Not thrilled with the S3 on-board video
| >though.. but that's just me..
|
| I do not currently use the on-board video nor the sound. I do use the
| on-board LAN for DSL though, as opposed to a PCI card before upgrading
| motherboards.

Okay, so there are also third party sound and video drivers to consider.
Anything else that might be non-standard/of interest?

|
| > To clarify for the group, BootMagic is/was part of PartionMagic.
| >
| >|
| >| The NEW hard drive is a Seagate 160 GB "Barracuda" ATA HD, 7200 RPM,
| >| which I used approx. 6 months in another computer, and removed it to
| >| install a 500 GB SATA in that unit. This 160 GB was then reformatted
| >| and used as the destination disk for cloning from the failing 160 GB
| >| ATA, 7200 Maxtor drive which is at least 3 years old now.
| >
| > Okay, just to clarify, though you mention a 500gig drive we are NOT
talking
| >about it as part of the issues.
|
| That is correct. The 500 GB SATA drive was installed in another
| computer that I use for different purposes.
| >
| > The two drives at issue are 160 gig. One was apparently failing and
relaced
| >by the Seagate. Was that drive 'cut" to the 137 gig barrier or is it full
| >capacity?
| >
| Let's go back thru how things had to be done. First of all, the old
| motherboard DID have the 137 GB limit, so - the "old" 160 GB drive
| (which was the Maxtor, incidentally) was limited by the motherboard's
| 137 limit.

Okay, here's part of an issue, as I indicated we are now contending with
two different BIOSes and different translation tables. As the drives were
never official "cut" by manufacturer software or via a pin, the 'old' drive
could never extend beyond that barrier "in 9X" WITHOUT error, though 2k
MIGHT have been using the extended area using HAL not the BIOS. This could
be part of why you thought the drive was failing in the first place, both
the BIOS and 98 were incapable of handling the larger drive. IF you used
PartitionMagic to setup the drive, you may have created a 160/'as modified'
drive [not talking partitions but total], which, if accessed via 98 would
have caused drive errors.
So the first partition was/is 2k, the next what? DOS or 9X? Or perhaps a
better question, what is the drive layout?

|
| Then after upgrading the motherboard, that Maxtor drive was still
| unexpanded, even though I could have. That's when I used Acronis True
| Image to clone that drive, plus the other 2 drives. I cloned that
| Maxtor "EXACTLY" as it existed to the new Seagate - all this being
| done under Windows 2000 since that's where I installed Acronis.

Okay. W2k was used as the 'master' OS to *exact* [sector by sector] clone
the drive, to the new UNCUT 160 gig drive using the NEW BIOS and translation
which supports larger drives. Most might think that's fine, but here's the
issue, the MBR, BPB, .FAT tables, and some other, ALL contain the old
drives' sectoring as WHERE everything is located. That's the old drive NOT
the new tranlation. 2k [if it can start] will make modifications to its
tables when first started, 9X and DOS won't until something like Scandisk is
used. For those who think otherwise: Oh, it may start and run for awhile,
but somewhere down the road things are going to break.

When changing actual drives and/or manufacturers, its best to just
transfer/mage used sectors and then run whatever tool to reset the
tables/sectoring.
EXACT imaging/transfering works best upon the original drive which was
cloned/imaged or an exact replacement on the SAME motherboard, at least with
the tools I have used. And always, as I have indicated, run some drive
'clarification/scan' tool PRIOR to attempting to start any OS. Doing this
also gives the opportunity to reset the various partitions/sectoring [hence
my prior comment on the boot manager].

|
| Next, I swapped the 160 GB drives, and at some point (no longer am
| able to remember exactly when) I used Partition Magic to expand the
| top partition of the drive containing Win2000 (but the NEW DRIVE
| ONLY) to fill up the Unallocated space. All this may or may not be
| important, but at the present time, the "Old" drive is still
| unexpanded, and the "New" drive is expanded. That's exactly why I
| keep asking if that expansion is what screwed up the "New" drive, by
| messing up the MBR or something else. So far, no one has answered
| that question for me.

DO NOT expand the old drive yet!

Well, we all know you expected us to give you a one or two message answer,
but that's not going to happen.
WHY? Because you failed to give us ALL the information we needed. Both Glen
and PCR pulled more necessary information, and that's WHY Glen says to do
what he suggested with the registry NOW. Removing the old motherboard
drivers and registry entries will VASTLY decrease errors and issues.
It should have been done to start with, but that's Okay, now will help.
NOTE SPECIFICALLY: you will need to re-install all the MB specific and other
drivers again in 9X.

As for the expansion:
98 is limited to a standard 137 gig or thereabouts [unless you want to use
DOS compatability mode {BIOS}] by its supplied driver. There MAY [emphasis]
be issues with the expanded drive depending upon a number of things.
IF the motherboard has drivers [modified esdi_506.pdr or special
application] for 9X for the larger drive capability you will likely be Okay,
but regretfully I have no personal knowledge of that particular board and
drivers, and did not pull those drivers to review.
The issue is:
IF the board did/does have drivers for 9X and large drives, then they MUST
be properly installed. As the 9X registry presently stands, there may be
conflicts between the old board drivers and the new, and the driver [if
supplied] will likely not work properly.
As the board was sold as supporting 9X, you might check the PDF/manual to
see if it did/does support [had/has drivers for] large drives in 9X or what
the limitation is. There are some modified 'drivers' available if the board
doesn't supply any, let us know.


|
| > Was the Maxtor "cut" or was it allowed to remain at full capacity?
|
| See above answers.
| >
| > Also, was the machine the Seagate was pulled from XP or VISTA?
| >
| NEGATIVE! I refuse to use either of those. It was pulled from a
| machine using Windows 2000 Professional.

Good, though are some disk issues with 2k, no where near those related to
the newer OSs.

|
| > These questions are to determine potentials.
|
| Hope my answers suffice.

We're getting there, now all you need to understand is that we ARE trying
to help you. Please do as Glen suggested and as I have indicated. BOTH
issues [OS and drive] are relevant. Believe it or not we'd like to see you
running a 'stable' multi-platform computer, that's hardware and OSs.

| >
| >|
| >| Now, your next 2 questions are not easy ones to answer with any
| >| certainty, since getting this entire system to work in all aspects has
| >| forced me to try many, many things - some of which might have added to
| >| my woes, admittedly. But as said in my original post, the new
| >| motherboard demanded that it go through a complete setup where it
| >| looked for drivers that I never expected. And it required my
| >| inserting the CD provided with it, to get its own drivers. I failed
| >| to keep record of what all this was. HOWEVER, when things got really
| >| screwed up, I actually pulled out the new drive and stuck the old
| >| failing one back in to check it out. The motherboard forced me to go
| >| thru the same setup of looking for drivers that suited it, etc. And
| >| it had a few problems also, but I got lucky and overcame them - all
| >| but one! That one concerns Boot Magic, which does not come up
| >| automatically, BUT if I use the Boot Magic 8.0 Rescue Disk, I can
| >| choose which system to boot under. And then all 3 OS's run just as
| >| they did earlier. SO, the "old failing" drive boots ok in Win 98 as
| >| well as Win 2K and DOS. That's when I tried cloning over from that
| >| old one (ONLY the W98 partition, though) to the new one. I did this
| >| many different ways, and many different selected files from the backup
| >| of the old drive's partition. So far, none of this has solved the
| >| problem with the ERROR message on the New drive, as far as W98 is
| >| concerned. Again, BOTH drives boot up and run fine in Win2K.
| >
| > Okay, two others have provided suggestions, Glen [and PCR] directs to
some
| >viable issues [cleaning old drivers] to attempt to start with. Perhaps he
| >will again place the Registry entries suggested at removal when making
major
| >changes in the 9X OS due to hardware changes. This will mean
re-installing
| >the MB drivers and other AGAIN.
| >
| > PCR caught the issues with the Boot, and I'll add that depending upon
how
| >the drive was cloned [what you chose to image], and formatted, the Boot
| >partition [BootMagic] may not be properly setup [clusters/sectors may be
off
| >or other]. Manufactures use differring adapter chips and routines, and
the
| >BIOS will translate somewhat differently, BootMagic may be having
| >difficulties. Reinstalling/reconfiguring the boot manager, if possible
| >without destroying the data/files, might help though Scandisk will
| >sometimes correct those issues if not to drastic [you have all
| >OSs/partitions as either Fat16 or 32 correct?]. 2K can better handle
| >cluster/sector issues [self-repair], but that leaves DOS and 98 out in
the
| >cold.
| >
| >|
| >| Remember, the above answer is partially related to the New drive, and
| >| partially related to the Old drive. Both currently have a problem,
| >| but the problem with the Old one is easy to live with - stick in the
| >| BM Rescue disk. But that problem with the New one is intolerable, I
| >| cannot use W98 on the New drive.
| >
| > I certainly hope you changed/checked the BIOS when you installed the new
| >drive. If the drives are set to AUTO detect then you can negate that
issue,
| >though hopefully you also checked the other settings.as well.
| >
| >|
| >| Now, let me ask a question out of total frustration. Is it possible
| >| the Master Boot Record (MBR) got screwed up on the New one? And if
| >| so, how to check and/or repair?
| >
| > Possible, but let's deal with these other potential fixes first.
| >
| >|
| >| Finally, if I have a complete backup of both Win98 partitions off both
| >| these drives - as they exist now, would it be useful to reformat the
| >| New drive and do a New installation from the original factory CD, then
| >| Restore from one of these backups? Or would I be right back where I
| >| am now?
| >
| > The clean install would be the best recourse, but once you over-install
| >[copying the old over the new], you're right back here again. The issues
| >seem to relate to the drive layout and the registry. Work through the
| >suggestions and Post back with issues or results.
| >
| >|
| >| After all this time, I'm willing to try the above, just groping for
| >| straws if it has a chance of working.
| >|
| >| Olin McDaniel
| >|
| >
| >--
| >
| >MEB
| >http://peoplescounsel.orgfree.com
| >_________
| >
| >| >"Olin K. McDaniel" <mcdanielo.abcd@bellsouth.net> wrote in message
| >| >news:47a3a6c2.4965099@newsgroups.bellsouth.net...
| >| >| Hopefully this won't get too longwinded, but as a bit of background,
I
| >| >| recently upgraded my hardware and wanted to keep all the software as
| >| >| before. I installed a new M.B. and CPU to go from a 600MHz Pentium
3
| >| >| unit to a 2.6 GHz Celeron unit. Also I cloned over the multiboot
| >| >| OS's from drive 1 to another HD, since the older one was showing
signs
| >| >| of failing. The program used for cloning was Acronis True Image.
| >| >| There were 3 OS's on Drive 1, and they also are now on the newly
| >| >| installed HDD. The heart of the multiboot system is Powerquest's
Boot
| >| >| Magic, that has worked wonderfully for years. The 3 OS's are DOS
6.22
| >| >| (rarely used anymore), Windows 98SE (most heavily used) and Windows
| >| >| 2000 Pro (used somewhat).
| >| >|
| >| >| The problem developed subsequent to several days of allowing the new
| >| >| M.B. and CPU to install all its drivers, etc.
| >| >|
| >| >| Essentially, I cannot boot up (on the NEW Hard Disk 1) into Win98SE
in
| >| >| Normal mode - I get an error message that says "Error loading
KERNEL.
| >| >| You must reinstall Windows". BUT - much to my annoyance, it WILL
| >| >| boot up fully in SAFE mode. Nothing that I've tried has cleared up
| >| >| this anomaly. I've followed the procedure found on MS's web site
| >| >| which tells me to "extract Kernel32.dll" from my installation CD and
| >| >| copy it to the folder Windows\System\, all to no avail, after
multiple
| >| >| efforts. In addition, I've copied it over from the presumed
"failing"
| >| >| hard drive, again with no success. I'm about ready to throw in the
| >| >| towel - hopefully, someone can give me an out. Before someone asks,
| >| >| there is NO problem booting up in Win2000 on this drive.
| >| >|
| >| >| Finally, as a further frustating fact, I can still do the multiboot
if
| >| >| I swap out the new HD 1 to the old failing one. But I don't trust
it
| >| >| lasting much longer.
| >| >|
| >| >| I'm admittedly out of ideas - and if it should be a problem with the
| >| >| MBR, then I don't know how to repair it.
| >| >|
| >| >| Sorry it got this long - and it may not have all the useful info
| >| >| someone might think would lead to a clue. If so, please tell me
what
| >| >| to check.
| >| >|
| >| >| Thanks, Olin McDaniel
| >| >|
|
| To reply by email, please remove "abcd" from Return address
| -----------------------------------------------------
| "Ignorance is treatable, Stupidity is incurable. Sometimes
| the difference is hardly distinguishable, however."

--

MEB
http://peoplescounsel.orgfree.com
_________

 

[PCR]

Olin K. McDaniel wrote:
| On Sat, 2 Feb 2008 18:43:41 -0500, "PCR" <pcrrcp@netzero.net> wrote:
|
|>Olin K. McDaniel wrote:
|>| Hopefully this won't get too longwinded, but as a bit of
|>| background, I recently upgraded my hardware and wanted to keep all
|>| the software as before. I installed a new M.B. and CPU to go from
|>| a 600MHz Pentium 3 unit to a 2.6 GHz Celeron unit.
|>

....snip...
|>| Also I cloned over the multiboot
|>| OS's from drive 1 to another HD, since the older one was showing
|>| signs of failing.
|>
|>The machine had only one HDD?
|
| NO! I thought I said it had a total of 3 hard drives, but maybe not.
| Regardless, the problem only exists with the boot drive with all 3
| OS's on it.

OK. You have 3 hard drives (HDDs). One of them has 3 bootable
partitions-- DOS, Win98SE, & Win2K. That is the one you are cloning to a
replacement HDD, after replacing the MB (to Biostar P4M80-M4) & CPU.
Both the new (Seagate Barracuda) & old HDD (Maxtor) are 160 GB in size.
The top partition is Win2K, which subsequently you have expanded in size
on the new hard drive.

I see you suspect that expanding the top partition could be the reason
you cannot boot the Win98SE partition. I'm looking at...

ftp://ftp.futurenet.co.uk/pub/pcanswers/tutorials/130.guide to PartitionMagic 8.pdf
PartitionMagic 8: Manage your hard drive efficiently by Mary Branscombe

There is something in there about an 8 GB limitation that I find
difficult to decipher. But, I think it's saying (for PM v.8) that the
partition which contains PM must begin within the 1st 8 GB of the hard
drive. Have you pushed it out? It goes on to say: "If anything goes
wrong, such as you move a partition past the 8Gb
or cylinder limit so you can’t boot from it...", which implies the whole
partition must lie within the 1st 8 GB of the hard drive. Also, I have
another URL (speaking of PM v.5) that said PM won't work in a partition
that is bigger than 8 GB.

HOWEVER, I'm not sure that applies to your case, because you can boot to
Win98SE Safe Mode through the PM menu. I would think you shouldn't be
able to boot at all, if a partition boundary or size were the problem!

STILL... I think you might try creating a 32 MB (that's "mega")
partition as Branscombe suggests in front of the Win2K partition-- &
install PartitionMagic into that. Try to do it from the rescue disk. I
suppose PM will automatically set the 32 MB partition to be the Active
one-- the one that will boot first. If not, make it so with FDISK or
some other utility.

Other than that...

(a) Do as glee said.
(b)
http://www.google.com/search?hl=en&q=Error+Loading+Kernel&btnG=Google+Search
Google finds about 138,000 for Error Loading Kernel

....snip...
|>| The heart of the multiboot system is Powerquest's Boot
|>| Magic, that has worked wonderfully for years. The 3 OS's are DOS
|>| 6.22 (rarely used anymore), Windows 98SE (most heavily used) and
|>| Windows 2000 Pro (used somewhat).
|>
|>I don't know BootMagic. Does it seem to have been copied over to the
|>new HDD by TrueImage? (I don't know TrueImage, either.) Or do you
|>think you might need to install it separately? Did you copy the 3
|>partitions over to the new HDD in the same order they are on the old
|>drive?
|
| Let's clarify this. Boot Magic is a subset of PowerQuest's Partition
| Magic, at least the version I use. Some one else bought them out, and
| it's now sold under a different Brand, maybe like Syquest (?), I'm not
| sure. Boot Magic is specific for installing onto one
| partition/Operating system to allow selection of a current choice of
| which OS to use. (I believe it only worked when I put it on Win2000).
| However I do have Partition Magic installed in both W98 and W2K.

If it isn't the one on W2K that was operative, you may have pushed it
beyond the 8 GB boundary.

| Further, Partition Magic allows a lot of copying over, etc. but it has
| its limitations. When I found this new Acronis TrueImage, I found it
| had managed to overcome those limitations. SO, when I copied all 3 of
| the hard drives, I did so with Acronis. There are several modes for
| doing so, some can cause grief - so I was careful to use the Manual
| mode and tell it to copy everything exactly as it was on the original,
| and to not "expand" the partitions, even if more space was available.
| (Then later I could, and did, go back and use Partition Magic to do
| that expansion as desired/needed. All of this manipulation went
| without problems, as proven by the success with the other two hard
| drives which are fully accessible - IF the OS can boot properly!!!!

The other 2 hard drives being accessible apparently is not a problem.
That's good, but it doesn't prove all went well with your manipulations.
You have to be able to boot Win98SE in Normal Mode to prove that!

I wonder-- did the new ever boot well to Win98SE Normal Mode, before you
expanded the Win2K partition?

....snip
|>| In addition, I've copied it over from the presumed "failing"
|>| hard drive, again with no success. I'm about ready to throw in the
|>| towel - hopefully, someone can give me an out. Before someone asks,
|>| there is NO problem booting up in Win2000 on this drive.
|>|
|>| Finally, as a further frustating fact, I can still do the multiboot
|>| if I swap out the new HD 1 to the old failing one. But I don't
|>| trust it lasting much longer.
|>
|>What are you saying-- just that you get a menu from BootMagic? Or can
|>you be saying Win98 will actually boot from the old drive? How did the
|>new drive boot to Win98SE Safe Mode-- through a BootMagic screen? How
|>did it boot to Win2K?
|
| Let's elaborate a little bit here, if you insist. With the New drive
| in #1 (or call it #0 if you wish), I get the correct menu after going
| thru the POST steps. This menu is that provided by Boot Magic. It
| gives me 3 choices from which to Boot. DOS, W98 and W2000. I have
| set it up for W98 as the Default, but that's simple to change. Also I
| can Disable Boot Magic very simply, if desired. (Remember, all this
| is on drive #1 and presumably exists on both the Old and the New
| drives, but it only works FULLY on the New.) If I then choose W98 to
| boot, that's when it gives the Error message, and insists on
| restarting in Safe mode.

The BootMagic boot menu works fully on the new drive. But, when Win98SE
is selected-- it will not boot to Normal Mode! I'm not sure whether that
fits the requirements of BootMagic being finicky with an 8 GB issue or
not. I haven't been able to find an URL that precisely says what that
would look like.

Therefore, maybe do as Branscombe said, if it is easy to do it
especially. Otherwise, do as glee said (which isn't easy) or click some
of that Google search or wait for me to click them.

| Again, to restate, the Old drive does not give me this menu choice,
| but I think that's readily fixable. I've chosen not to screw with it
| yet, rather just use the BM rescue disk to make my choice, and then I
| can boot successfully on either of the OS's. SO - my Main effort is
| in trying to fix the New drive in the #1 spot. Any other effort ahead
| of that is a waste of time and probably counterproductive.

I agree. Don't mess with the original yet. I wonder-- if you boot from
the PM Rescue disk, does the Win98SE partition on the new drive also
boot well? If so, that would prove there is nothing far amiss with the
installation itself. I even suppose you have copied the 3 partitions
over to the new drive in the same order that they appear on the old one,
since 2 of them are booting correctly.

|>
|>| I'm admittedly out of ideas - and if it should be a problem with the
|>| MBR, then I don't know how to repair it.
|>
|>I don't know TrueImage or BootMagic. What does the process of copying
|>a partition to a new hard drive normally entail? Are there extra
|>steps to do in its instructions in order to make the drive bootable?
|>Did you do them? Looks like you do boot to Win98SE Safe Mode & fully
|>to Win2K. SO-- something must be right. As far as BootMagic, what is
|>it like to install it? Maybe try that on the new drive, just in case
|>TrueImage didn't get all of it.
|
| Hopefully the above 2 answers covers most of these questions also.
| Although I've never successfully used GHOST, my understanding is that
| True Image does much the same thing, and even more simply and with
| less complications. I assure you that careful reading of its
| instructions at each step of the way SHOULD allow most people to do it
| without messing up. The fact that I successfully cloned over the
| other 2 hard drives with it, should attest to the fact that I followed
| their instructions correctly.

I didn't mean to be critical. I was just wondering whether something
more had to be done than just moving the partitions. However, since you
do get the PM boot menu on the new hard drive-- I guess all of its parts
(including anything in the MBR) have successfully been moved.

|>| Sorry it got this long - and it may not have all the useful info
|>| someone might think would lead to a clue. If so, please tell me
|>| what to check.
|>
|>Keep at it. I think you are close, if you get to Safe Mode. But how
|>are you getting there?
|
| Should be adequately answered above.
|
|>
|>| Thanks, Olin McDaniel
|>
|>You are welcome.
|>
|>--
|>Thanks or Good Luck,
|>There may be humor in this post, and,
|>Naturally, you will not sue,
|>Should things get worse after this,
|>PCR
|>pcrrcp@netzero.net
|>
|>
| Olin McDaniel
|
| To reply by email, please remove "abcd" from Return address
| -----------------------------------------------------
| "Ignorance is treatable, Stupidity is incurable. Sometimes
| the difference is hardly distinguishable, however."

--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
Should things get worse after this,
PCR
pcrrcp@netzero.net

 

[PCR]

Olin K. McDaniel wrote:
| On Sat, 2 Feb 2008 18:43:41 -0500, "PCR" <pcrrcp@netzero.net> wrote:
|
|>Olin K. McDaniel wrote:
|>| Hopefully this won't get too longwinded, but as a bit of
|>| background, I recently upgraded my hardware and wanted to keep all
|>| the software as before. I installed a new M.B. and CPU to go from
|>| a 600MHz Pentium 3 unit to a 2.6 GHz Celeron unit.
|>

....snip...
|>| Also I cloned over the multiboot
|>| OS's from drive 1 to another HD, since the older one was showing
|>| signs of failing.
|>
|>The machine had only one HDD?
|
| NO! I thought I said it had a total of 3 hard drives, but maybe not.
| Regardless, the problem only exists with the boot drive with all 3
| OS's on it.

OK. You have 3 hard drives (HDDs). One of them has 3 bootable
partitions-- DOS, Win98SE, & Win2K. That is the one you are cloning to a
replacement HDD, after replacing the MB (to Biostar P4M80-M4) & CPU.
Both the new (Seagate Barracuda) & old HDD (Maxtor) are 160 GB in size.
The top partition is Win2K, which subsequently you have expanded in size
on the new hard drive. What are its original & new sizes?

I see you suspect that expanding the top partition could be the reason
you cannot boot the Win98SE partition. I'm looking at...

ftp://ftp.futurenet.co.uk/pub/pcanswers/tutorials/130.guide to PartitionMagic 8.pdf
PartitionMagic 8: Manage your hard drive efficiently by Mary Branscombe

There is something in there about an 8 GB limitation that I find
difficult to decipher. But, I think it's saying (for PM v.8) that the
partition which contains PM must begin within the 1st 8 GB of the hard
drive. Have you pushed it out? It goes on to say: "If anything goes
wrong, such as you move a partition past the 8Gb
or cylinder limit so you can’t boot from it...", which implies the whole
partition must lie within the 1st 8 GB of the hard drive. Also, I have
another URL (speaking of PM v.5) that said PM won't work in a partition
that is bigger than 8 GB. That's even worse!

HOWEVER, I'm not sure that applies to your case, because you can boot to
Win98SE Safe Mode through the PM menu. I would think you shouldn't be
able to boot at all, if a partition boundary or size were the problem.
(But I don't know.)

SO... I think you might try creating a 32 MB (that's "mega")
partition as Branscombe suggests in front of the Win2K partition-- &
install PartitionMagic into that. Try to do it from the rescue disk. I
suppose PM will automatically set the 32 MB partition to be the Active
one-- the one that will boot first. If not, make it so with FDISK or
some other utility.

Other than that...

(a) Do as glee said.
(b)
http://www.google.com/search?hl=en&q=Error+Loading+Kernel&btnG=Google+Search
Google finds about 138,000 for Error Loading Kernel

....snip...
|>| The heart of the multiboot system is Powerquest's Boot
|>| Magic, that has worked wonderfully for years. The 3 OS's are DOS
|>| 6.22 (rarely used anymore), Windows 98SE (most heavily used) and
|>| Windows 2000 Pro (used somewhat).
|>
|>I don't know BootMagic. Does it seem to have been copied over to the
|>new HDD by TrueImage? (I don't know TrueImage, either.) Or do you
|>think you might need to install it separately? Did you copy the 3
|>partitions over to the new HDD in the same order they are on the old
|>drive?
|
| Let's clarify this. Boot Magic is a subset of PowerQuest's Partition
| Magic, at least the version I use. Some one else bought them out, and
| it's now sold under a different Brand, maybe like Syquest (?), I'm not
| sure. Boot Magic is specific for installing onto one
| partition/Operating system to allow selection of a current choice of
| which OS to use. (I believe it only worked when I put it on Win2000).
| However I do have Partition Magic installed in both W98 and W2K.

If it isn't the one on W2K that was operative, you may have pushed it
beyond the 8 GB boundary.

| Further, Partition Magic allows a lot of copying over, etc. but it has
| its limitations. When I found this new Acronis TrueImage, I found it
| had managed to overcome those limitations. SO, when I copied all 3 of
| the hard drives, I did so with Acronis. There are several modes for
| doing so, some can cause grief - so I was careful to use the Manual
| mode and tell it to copy everything exactly as it was on the original,
| and to not "expand" the partitions, even if more space was available.
| (Then later I could, and did, go back and use Partition Magic to do
| that expansion as desired/needed. All of this manipulation went
| without problems, as proven by the success with the other two hard
| drives which are fully accessible - IF the OS can boot properly!!!!

The other 2 hard drives being accessible apparently is not a problem.
That's good, but it doesn't prove all went well with your manipulations.
You have to be able to boot Win98SE in Normal Mode to prove that!

I wonder-- did the new ever boot well to Win98SE Normal Mode, before you
expanded the Win2K partition?

....snip
|>| In addition, I've copied it over from the presumed "failing"
|>| hard drive, again with no success. I'm about ready to throw in the
|>| towel - hopefully, someone can give me an out. Before someone asks,
|>| there is NO problem booting up in Win2000 on this drive.
|>|
|>| Finally, as a further frustating fact, I can still do the multiboot
|>| if I swap out the new HD 1 to the old failing one. But I don't
|>| trust it lasting much longer.
|>
|>What are you saying-- just that you get a menu from BootMagic? Or can
|>you be saying Win98 will actually boot from the old drive? How did the
|>new drive boot to Win98SE Safe Mode-- through a BootMagic screen? How
|>did it boot to Win2K?
|
| Let's elaborate a little bit here, if you insist. With the New drive
| in #1 (or call it #0 if you wish), I get the correct menu after going
| thru the POST steps. This menu is that provided by Boot Magic. It
| gives me 3 choices from which to Boot. DOS, W98 and W2000. I have
| set it up for W98 as the Default, but that's simple to change. Also I
| can Disable Boot Magic very simply, if desired. (Remember, all this
| is on drive #1 and presumably exists on both the Old and the New
| drives, but it only works FULLY on the New.) If I then choose W98 to
| boot, that's when it gives the Error message, and insists on
| restarting in Safe mode.

The BootMagic boot menu works fully on the new drive. But, when Win98SE
is selected-- it will not boot to Normal Mode! I'm not sure whether that
fits the requirements of BootMagic being finicky with an 8 GB issue or
not. I haven't been able to find an URL that precisely says what that
would look like.

Therefore, maybe do as Branscombe said, if it is easy to do it
especially. Otherwise, do as glee said (which isn't easy) or click some
of that Google search or wait for me to click them.

| Again, to restate, the Old drive does not give me this menu choice,
| but I think that's readily fixable. I've chosen not to screw with it
| yet, rather just use the BM rescue disk to make my choice, and then I
| can boot successfully on either of the OS's. SO - my Main effort is
| in trying to fix the New drive in the #1 spot. Any other effort ahead
| of that is a waste of time and probably counterproductive.

I agree. Don't mess with the original yet. I wonder-- if you boot from
the PM Rescue disk, does the Win98SE partition on the new drive also
boot well? If so, that would prove there is nothing far amiss with the
installation itself. I even suppose you have copied the 3 partitions
over to the new drive in the same order that they appear on the old one,
since 2 of them are booting correctly.

|>
|>| I'm admittedly out of ideas - and if it should be a problem with the
|>| MBR, then I don't know how to repair it.
|>
|>I don't know TrueImage or BootMagic. What does the process of copying
|>a partition to a new hard drive normally entail? Are there extra
|>steps to do in its instructions in order to make the drive bootable?
|>Did you do them? Looks like you do boot to Win98SE Safe Mode & fully
|>to Win2K. SO-- something must be right. As far as BootMagic, what is
|>it like to install it? Maybe try that on the new drive, just in case
|>TrueImage didn't get all of it.
|
| Hopefully the above 2 answers covers most of these questions also.
| Although I've never successfully used GHOST, my understanding is that
| True Image does much the same thing, and even more simply and with
| less complications. I assure you that careful reading of its
| instructions at each step of the way SHOULD allow most people to do it
| without messing up. The fact that I successfully cloned over the
| other 2 hard drives with it, should attest to the fact that I followed
| their instructions correctly.

I didn't mean to be critical. I was just wondering whether something
more had to be done than just moving the partitions. However, since you
do get the PM boot menu on the new hard drive-- I guess all of its parts
(including anything in the MBR) have successfully been moved.

|>| Sorry it got this long - and it may not have all the useful info
|>| someone might think would lead to a clue. If so, please tell me
|>| what to check.
|>
|>Keep at it. I think you are close, if you get to Safe Mode. But how
|>are you getting there?
|
| Should be adequately answered above.
|
|>
|>| Thanks, Olin McDaniel
|>
|>You are welcome.
|>
|>--
|>Thanks or Good Luck,
|>There may be humor in this post, and,
|>Naturally, you will not sue,
|>Should things get worse after this,
|>PCR
|>pcrrcp@netzero.net
|>
|>
| Olin McDaniel
|
| To reply by email, please remove "abcd" from Return address
| -----------------------------------------------------
| "Ignorance is treatable, Stupidity is incurable. Sometimes
| the difference is hardly distinguishable, however."

--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
Should things get worse after this,
PCR
pcrrcp@netzero.net

 

[PCR]

Ignore. Go to the next.

--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
Should things get worse after this,
PCR
pcrrcp@netzero.net

 

[MEB]

"Olin K. McDaniel" <mcdanielo.abcd@bellsouth.net> wrote in message
news:47aa4677.7720647@newsgroups.bellsouth.net...
| On Mon, 4 Feb 2008 22:46:14 -0500, "PCR" <pcrrcp@netzero.net> wrote:
|
| >Ignore. Go to the next.
| >
| >--
| >Thanks or Good Luck,
| >There may be humor in this post, and,
| >Naturally, you will not sue,
| >Should things get worse after this,
| >PCR
| >pcrrcp@netzero.net
|
|
| This may seem an odd one to reply to, but it's in good humor, and I*d
| like my reply to be taken the same way. Let's also consider this an
| update on my situation, and perhaps some insight into alternate
| approaches. To explain - I'm few weeks short of my 83rd birthday,
| and have worked in the field of science and engineering all my career
| until I retired a few years ago. So, I hate like hell to get into a
| corner that I can't get out of. I fight like the devil to find my way
| out, even though it may not be the way everyone points to me. With
| having said that, here is what I've done, and YES I did keep good
| notes along the way. Maybe, just maybe, this can be helpful to
| others, I'd like to hope so anyway.
|
| First thing, I decided to start from scratch, all over again. I did
| have a brand new Seagate 160 GB PATA hard drive stashed for another
| job, but decided to sacrifice it, if it came to that.
|
| I did another complete clone job with Acronis, from the unexpanded Old
| Maxtor hard drive. It took somewhat over 8 hours to complete, after
| I'd gone to bed, incidentally. But it reported a successful
| completion.
|
| The next day, I replaced the Old Maxtor unit with this newly cloned
| over (also unexpanded Seagate) drive. Then I used the Boot Magic
| Rescue disk to boot up into Windows 2000. It booted ok, but many of
| the partitions had incorrect letter IDs. I checked things with
| Partition Magic and found at least 2 partitions on one drive were
| Hidden, NOT the way they were on the source drive. After careful
| searching, I found an Option under Boot Magic that was checked, called
| "Hidden" or such. After unchecking this and making B.M. Active and
| telling it YES, to "create needed space at the beginning", or
| something close to this - I chose W98 as the next choice for booting.
|
| Win98 then booted up perfectly, all partitions were correctly arranged
| and labeled. I tried a couple of applications under W98 and they
| worked just fine. But I still needed to use the B.M. Rescue disk to
| specify the next boot into Win2K, and it worked. EXCEPT Explore
| failed to show all partitions! This was puzzling, since Partition
| Magic did not show them now as Hidden. Solving this came later, as
| I'll describe in a moment. However, I first wanted to get back the
| simple Menu to select which drive to boot into, instead of having to
| use the B.M. Rescue disk. Believe it or not, the answer again was in
| Boot Magic's setup screen, I just had never noticed it before. I had
| to set the "Time" feature to either Indefinite or Timed (30 secs.)
| instead of the other (apparently default) choice. Now I got the Menu
| at all Restarts!!!
|
| So, next I tackled the problem of missing partitions in Explore, that
| were perfectly revealed in Partition Magic. The answer was there in
| Partition Magic all the time, but just was NOT obvious. These
| unrevealed partitions were there, BUT they did not have a drive letter
| assigned in P.M. It had been assigned as NONE. Reassigning them the
| correct letters was an easy fix, just not something easily observed.
|
| Once all these changes were made, both operating systems booted up
| perfectly and were fully functional just as they were before this
| ordeal began several weeks ago. Plus the higher speed of this Mother
| board and CPU became very evident.
|
| NOW, remember both the source (Old drive) and destination (New drive)
| were still unexpanded, i.e. they both had the 137 GB upper limit.
| Since I now knew how to go thru this drill successfully again if
| needed, I decided What the Heck, let's expand this New one and see
| what happens. I even did it under Win98, which logic says would be
| the one most likely to have a problem. NO PROBLEM WHATSOEVER!!
| I now have essentially everything as I had hope to get it weeks ago!
| It even appears that all three of these new drives to which I cloned
| over, are of a faster design than those earlier ones. Just replacing
| this HDD 1 (or if you prefer HDD 0) seemed to be the final upgrade to
| make all three a later and faster variety.
|
| Having taken time to prepare this very wordy and possibly too long a
| post, I want to sincerely thank those of you who were desperately
| trying to help me out of the problem I got into. This is directed to
| the three of you, PCR, Glee and MEB with all sincerity.
|
| Not only have I learned a lot about my particular system and its
| potential pitfalls (and I'm sure there are many more), I've learned
| something else equally important. I've built many PC's from scratch
| without much trouble, but to try to upgrade an old one and retain all
| the programs and data on it, is a totally different task!!!!! BEWARE.
| Oh, before I forget it - Acronis True Image is not perfect, but it
| sure comes close. Yes it did miss a couple of features, which had to
| be repaired, but can anyone come up with a better Cloner?
|
| Thanks again,
|
| Olin McDaniel
| To reply by email, please remove "abcd" from Return address
| -----------------------------------------------------
| "Ignorance is treatable, Stupidity is incurable. Sometimes
| the difference is hardly distinguishable, however."


Olin, that was such a well written and simple to read explanation that I'll
quote it for posterity...

We are all glad that you figured it out, and I too was interested in the
BootManager/BootMagic aspect and hidden partitions. Perhaps we all sometimes
overlook the most obvious or presume too much. Again, thanks for posting
back with your success and how it was acheived.

And yes, Acronis is used by many of the users in this group and many 'swear
by it'. Good program, but so was/is PartitionMagic...
As an aside, if you would, monitor that over 137 gig aspect in 9X and let
us know if it ever funks out. Thanks.

--

MEB
http://peoplescounsel.orgfree.com
_________

 

[Olin K. McDaniel]

On Mon, 4 Feb 2008 22:46:14 -0500, "PCR" <pcrrcp@netzero.net> wrote:

>Ignore. Go to the next.
>
>--
>Thanks or Good Luck,
>There may be humor in this post, and,
>Naturally, you will not sue,
>Should things get worse after this,
>PCR
>pcrrcp@netzero.net


This may seem an odd one to reply to, but it's in good humor, and I*d
like my reply to be taken the same way. Let's also consider this an
update on my situation, and perhaps some insight into alternate
approaches. To explain - I'm few weeks short of my 83rd birthday,
and have worked in the field of science and engineering all my career
until I retired a few years ago. So, I hate like hell to get into a
corner that I can't get out of. I fight like the devil to find my way
out, even though it may not be the way everyone points to me. With
having said that, here is what I've done, and YES I did keep good
notes along the way. Maybe, just maybe, this can be helpful to
others, I'd like to hope so anyway.

First thing, I decided to start from scratch, all over again. I did
have a brand new Seagate 160 GB PATA hard drive stashed for another
job, but decided to sacrifice it, if it came to that.

I did another complete clone job with Acronis, from the unexpanded Old
Maxtor hard drive. It took somewhat over 8 hours to complete, after
I'd gone to bed, incidentally. But it reported a successful
completion.

The next day, I replaced the Old Maxtor unit with this newly cloned
over (also unexpanded Seagate) drive. Then I used the Boot Magic
Rescue disk to boot up into Windows 2000. It booted ok, but many of
the partitions had incorrect letter IDs. I checked things with
Partition Magic and found at least 2 partitions on one drive were
Hidden, NOT the way they were on the source drive. After careful
searching, I found an Option under Boot Magic that was checked, called
"Hidden" or such. After unchecking this and making B.M. Active and
telling it YES, to "create needed space at the beginning", or
something close to this - I chose W98 as the next choice for booting.

Win98 then booted up perfectly, all partitions were correctly arranged
and labeled. I tried a couple of applications under W98 and they
worked just fine. But I still needed to use the B.M. Rescue disk to
specify the next boot into Win2K, and it worked. EXCEPT Explore
failed to show all partitions! This was puzzling, since Partition
Magic did not show them now as Hidden. Solving this came later, as
I'll describe in a moment. However, I first wanted to get back the
simple Menu to select which drive to boot into, instead of having to
use the B.M. Rescue disk. Believe it or not, the answer again was in
Boot Magic's setup screen, I just had never noticed it before. I had
to set the "Time" feature to either Indefinite or Timed (30 secs.)
instead of the other (apparently default) choice. Now I got the Menu
at all Restarts!!!

So, next I tackled the problem of missing partitions in Explore, that
were perfectly revealed in Partition Magic. The answer was there in
Partition Magic all the time, but just was NOT obvious. These
unrevealed partitions were there, BUT they did not have a drive letter
assigned in P.M. It had been assigned as NONE. Reassigning them the
correct letters was an easy fix, just not something easily observed.

Once all these changes were made, both operating systems booted up
perfectly and were fully functional just as they were before this
ordeal began several weeks ago. Plus the higher speed of this Mother
board and CPU became very evident.

NOW, remember both the source (Old drive) and destination (New drive)
were still unexpanded, i.e. they both had the 137 GB upper limit.
Since I now knew how to go thru this drill successfully again if
needed, I decided What the Heck, let's expand this New one and see
what happens. I even did it under Win98, which logic says would be
the one most likely to have a problem. NO PROBLEM WHATSOEVER!!
I now have essentially everything as I had hope to get it weeks ago!
It even appears that all three of these new drives to which I cloned
over, are of a faster design than those earlier ones. Just replacing
this HDD 1 (or if you prefer HDD 0) seemed to be the final upgrade to
make all three a later and faster variety.

Having taken time to prepare this very wordy and possibly too long a
post, I want to sincerely thank those of you who were desperately
trying to help me out of the problem I got into. This is directed to
the three of you, PCR, Glee and MEB with all sincerity.

Not only have I learned a lot about my particular system and its
potential pitfalls (and I'm sure there are many more), I've learned
something else equally important. I've built many PC's from scratch
without much trouble, but to try to upgrade an old one and retain all
the programs and data on it, is a totally different task!!!!! BEWARE.
Oh, before I forget it - Acronis True Image is not perfect, but it
sure comes close. Yes it did miss a couple of features, which had to
be repaired, but can anyone come up with a better Cloner?

Thanks again,

Olin McDaniel
To reply by email, please remove "abcd" from Return address
-----------------------------------------------------
"Ignorance is treatable, Stupidity is incurable. Sometimes
the difference is hardly distinguishable, however."

 

[PCR]

Olin K. McDaniel wrote:
| On Mon, 4 Feb 2008 22:46:14 -0500, "PCR" <pcrrcp@netzero.net> wrote:
|
|>Ignore. Go to the next.
|>
|>--
|>Thanks or Good Luck,
|>There may be humor in this post, and,
|>Naturally, you will not sue,
|>Should things get worse after this,
|>PCR
|>pcrrcp@netzero.net
|
|
| This may seem an odd one to reply to, but it's in good humor, and I*d
| like my reply to be taken the same way. Let's also consider this an
| update on my situation, and perhaps some insight into alternate
| approaches. To explain - I'm few weeks short of my 83rd birthday,
| and have worked in the field of science and engineering all my career
| until I retired a few years ago. So, I hate like hell to get into a
| corner that I can't get out of. I fight like the devil to find my way
| out, even though it may not be the way everyone points to me. With
| having said that, here is what I've done, and YES I did keep good
| notes along the way. Maybe, just maybe, this can be helpful to
| others, I'd like to hope so anyway.
|
| First thing, I decided to start from scratch, all over again. I did
| have a brand new Seagate 160 GB PATA hard drive stashed for another
| job, but decided to sacrifice it, if it came to that.
|
| I did another complete clone job with Acronis, from the unexpanded Old
| Maxtor hard drive. It took somewhat over 8 hours to complete, after
| I'd gone to bed, incidentally. But it reported a successful
| completion.
|
| The next day, I replaced the Old Maxtor unit with this newly cloned
| over (also unexpanded Seagate) drive. Then I used the Boot Magic
| Rescue disk to boot up into Windows 2000. It booted ok,

OK. Glad you kept at it. (I have hopes I will be as industrious as you
at your age, because my genetically close uncle Nicky was feisty enough
to punch me in the jaw at 82!) And I presume you copied the partitions
in the same order in which they appeared on the original. But too bad
the original also had stopped booting in the normal way by now & could o
nly boot well with the PM Rescue disk. Therefore, we still don't know
definitively whether all its parts would normally have copied over
correctly using TrueImage. But I am inclined to think they would! After
all, you did get the BootMagic boot menu the first time. Also, it was
booting into Win98SE Safe Mode.

| but many of
| the partitions had incorrect letter IDs. I checked things with
| Partition Magic and found at least 2 partitions on one drive were
| Hidden, NOT the way they were on the source drive. After careful
| searching, I found an Option under Boot Magic that was checked, called
| "Hidden" or such. After unchecking this and making B.M. Active and
| telling it YES, to "create needed space at the beginning", or
| something close to this - I chose W98 as the next choice for booting.

I'm not sure what to make of that. Could be that booting from the rescue
disk does not use all the settings of a boot from a BM partition. It may
have reverted to default settings. Or, it could be those settings were
damaged in the earlier manipulations that now necessitated the use of
the rescue disk. (I don't know.)

| Win98 then booted up perfectly, all partitions were correctly arranged
| and labeled. I tried a couple of applications under W98 and they
| worked just fine.

Wonderful! Glad you kept at it!

| But I still needed to use the B.M. Rescue disk to
| specify the next boot into Win2K, and it worked. EXCEPT Explore
| failed to show all partitions! This was puzzling, since Partition
| Magic did not show them now as Hidden.

Hmm. It used to be BootMagic would boot into Win2K & show all the
partitions, IIRC, on the new hard drive. But that was after the first
cloning & before things went bad with BootMagic on the original hard
drive. It makes no sense to expect things could be perfect now.

| Solving this came later, as
| I'll describe in a moment. However, I first wanted to get back the
| simple Menu to select which drive to boot into, instead of having to
| use the B.M. Rescue disk. Believe it or not, the answer again was in
| Boot Magic's setup screen, I just had never noticed it before. I had
| to set the "Time" feature to either Indefinite or Timed (30 secs.)
| instead of the other (apparently default) choice. Now I got the Menu
| at all Restarts!!!

Excellent! I can only guess it may be a settings issue. Could be
settings revert to defaults when booting the PM Rescue Disk. Or, somehow
a settings file or hard drive area had become damaged one way or another
during the TrueImage clone process, during Windows's grueling hardware
discovery process, or during some other manipulation.

| So, next I tackled the problem of missing partitions in Explore, that
| were perfectly revealed in Partition Magic. The answer was there in
| Partition Magic all the time, but just was NOT obvious. These
| unrevealed partitions were there, BUT they did not have a drive letter
| assigned in P.M. It had been assigned as NONE. Reassigning them the
| correct letters was an easy fix, just not something easily observed.

Alright. Glad you caught it. Very good.

| Once all these changes were made, both operating systems booted up
| perfectly and were fully functional just as they were before this
| ordeal began several weeks ago. Plus the higher speed of this Mother
| board and CPU became very evident.

I am glad to hear it, & I pray I will as industrious when I am 83! Or
even 79!

| NOW, remember both the source (Old drive) and destination (New drive)
| were still unexpanded, i.e. they both had the 137 GB upper limit.

Expanding the drive is one thing you suspected to have caused the
problem on the new drive after the 1st clone attempt, (the other being
an MBR problem). And an URL/two I discovered seemed to suggest that
indeed expanding could have been it! But BM nevertheless did actually
work better on the new drive (you got the menu & could boot to Win98SE
Safe Mode & to the other OS) than on the old, unexpanded drive (you had
at some point to use the Rescue Disk, but it got all the way to Normal
Mode & saw the drives). You never did say whether Win98SE would boot all
the way to Normal Mode using the Rescue Disk on the new drive. But it
looks like two separate problems could possibly have been in play.

| Since I now knew how to go thru this drill successfully again if
| needed, I decided What the Heck, let's expand this New one and see
| what happens. I even did it under Win98, which logic says would be
| the one most likely to have a problem. NO PROBLEM WHATSOEVER!!

Well... what partition(s) did you expand this time & from what size to
what size? I'm not sure what you have done to get this all working well.
Have you reinstalled PM/BM or just changed settings? It could be you've
reinstalled BM to a 32 MB (that's mega-byte) partition of its own at the
front of the hard drive as suggested (I think) in the following...

ftp://ftp.futurenet.co.uk/pub/pcanswers/tutorials/130.guide to PartitionMagic 8.pdf
PartitionMagic 8: Manage your hard drive efficiently by Mary Branscombe

That would be a cure for any 8 GB issue, if I understand her correctly.

| I now have essentially everything as I had hope to get it weeks ago!
| It even appears that all three of these new drives to which I cloned
| over, are of a faster design than those earlier ones. Just replacing
| this HDD 1 (or if you prefer HDD 0) seemed to be the final upgrade to
| make all three a later and faster variety.

We are all pleased to hear it-- me & MEB & glee!

| Having taken time to prepare this very wordy and possibly too long a
| post, I want to sincerely thank those of you who were desperately
| trying to help me out of the problem I got into. This is directed to
| the three of you, PCR, Glee and MEB with all sincerity.

You are welcome. I think you did well to persist after almost giving up
on Win98SE!

| Not only have I learned a lot about my particular system and its
| potential pitfalls (and I'm sure there are many more), I've learned
| something else equally important. I've built many PC's from scratch
| without much trouble, but to try to upgrade an old one and retain all
| the programs and data on it, is a totally different task!!!!! BEWARE.

You did a big thing! I personally already was scared enough never to try
a MB & CPU replacement of my own, though. It seems you did that very
well & went through the big driver changes & multiple reboots twice (on
the old & new drives) & survived! That was really the big thing! After
that, it was a matter of PM/BM settings or a proper reinstall of it,
which really is minor by comparison.

| Oh, before I forget it - Acronis True Image is not perfect, but it
| sure comes close. Yes it did miss a couple of features, which had to
| be repaired, but can anyone come up with a better Cloner?

You know that one well now & probably shouldn't switch. I use...

http://www.bootitng.com/ 's BootIt NG, has a variety of backup
capabilities & works with all OS: Copy partition(s) to HDD, or Image to
HDD or to CD or DVD. Create, move, shrink or expand partitions without
data loss. Multi-boot too. To install & use beyond 30 days, $34.95.

| Thanks again,
|
| Olin McDaniel
| To reply by email, please remove "abcd" from Return address
| -----------------------------------------------------
| "Ignorance is treatable, Stupidity is incurable. Sometimes
| the difference is hardly distinguishable, however."

--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
Should things get worse after this,
PCR
pcrrcp@netzero.net