Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

computer HAD win2k HAS Winxp pro sp3 installed


  • Please log in to reply
19 replies to this topic

#1 Llarik1

Llarik1

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:10:21 AM

Posted 16 July 2012 - 08:48 AM

This computer had Win2000 server on a 1 hard drive. Was dual boot capable to winxp(pro sp3)on a second disc drive.
Despite the rewriting of the boot.ini showing that the winxp pro is the only operating system on any partition. With the Disc drive that had win2000 (not even accessable) removed, I get the error that Windows 2000 can't boot due to a missing "WINNT\SYSTEM32\CONFIG\ SYSTEMced error (albeit it reads WINXP instead of WINNT). Have tried deleting and rewriting the boot.ini, and to fixMBR. Still getting same error. (These were done on winXP recovery console). I am not sure if I should be looking for a WIN2k recovery console or ?

BC AdBot (Login to Remove)

 


#2 AustrAlien

AustrAlien

    Inquisitor


  • BC Advisor
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:12:21 AM

Posted 16 July 2012 - 11:51 AM

Despite the rewriting of the boot.ini showing that the winxp pro is the only operating system on any partition.

May I please have a look at the content of the boot.ini file. Copy and paste into a reply.
  • Please also confirm the indication that currently there is just one hard drive attached to the system.

AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#3 Llarik1

Llarik1
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:10:21 AM

Posted 16 July 2012 - 12:59 PM

boot.ini file

[bootloader]
timeout=20
default=multi(0)disk(0)rdisk(0)partition(1)\WINXP

[Operating Systems]
multi(0)disk(0)rdisk(0)partition(1)\WINXP= "xp-pro sp3" /fastdetect
" " \winxp = "othernames I entered" [w/o the /fastdetect switch]

#4 AustrAlien

AustrAlien

    Inquisitor


  • BC Advisor
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:12:21 AM

Posted 16 July 2012 - 01:02 PM

Is that an exact and full copy of what is contained in the boot.ini file?
  • Have you altered the text in the file, before posting it here ... for some reason?

AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#5 Llarik1

Llarik1
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:10:21 AM

Posted 16 July 2012 - 01:03 PM

There is only one hard drive - was another that booted to xp home and had the vestige (not bootable) win2000 in a "old computer structure" folder.

#6 AustrAlien

AustrAlien

    Inquisitor


  • BC Advisor
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:12:21 AM

Posted 16 July 2012 - 01:09 PM

Yes, that is understood, but I need you to answer the question that I asked previously, please ...

Is that an exact and full copy of what is contained in the boot.ini file?
  • Have you altered the text in the file, before posting it here ... for some reason?

AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#7 Llarik1

Llarik1
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:10:21 AM

Posted 16 July 2012 - 01:11 PM

It is an exact copy of the first 5 lines, the remaining lines are exactly like the fifth line, but have added other names when I attempted to rebuild the boot.cfg. The multi(0)disk(0)rdisk(0)partition(1) are exactly the same in each one - just what I had named it differs slightly.

It is an exact copy of the first 5 lines, the remaining lines are exactly like the fifth line, but have added other names when I attempted to rebuild the boot.cfg. The multi(0)disk(0)rdisk(0)partition(1) are exactly the same in each one - just what I had named it differs slightly.

#8 Llarik1

Llarik1
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:10:21 AM

Posted 16 July 2012 - 01:15 PM

I believe I read somewhere, that WINNT loads something before boot.ini, and I suspect that something is flagging the system into thinking there is still and NT/2k operating system on it, and it is looking for it rather than reading my boot.ini.

#9 AustrAlien

AustrAlien

    Inquisitor


  • BC Advisor
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:12:21 AM

Posted 16 July 2012 - 01:25 PM

Please respond to this earlier request: "Please also confirm ... that currently there is just one hard drive attached to the system."

There should not be a problem posting the contents of boot.ini in its entirety: Is there?
AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#10 AustrAlien

AustrAlien

    Inquisitor


  • BC Advisor
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:12:21 AM

Posted 16 July 2012 - 01:46 PM

I need to get some sleep right now: I will post this ... and then I will check on you later.

This is what a good boot.ini file would look like:

[boot loader]
timeout=4
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect /NoExecute=OptIn

Note: the green colored text can vary, and may or may not be present.

I would have expected your boot.ini to point to the WINDOWS directory, and not to a directory WINXP as yours apparently does ... for some reason, which could be quite correct.
  • Could this be the problem??? I do not know ... it is merely a suggestion as a possibility for you to consider.
I will check back later. Good luck.

Edited by AustrAlien, 16 July 2012 - 01:48 PM.

AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#11 James Litten

James Litten

    Ԁǝǝ˥q


  • BC Advisor
  • 1,946 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:09:21 AM

Posted 16 July 2012 - 01:51 PM

Hi

I'm not sure about what your setup is. Here are my assumptions :)

You have a desktop computer
It has ONLY one hard drive in it with ONLY one partition.
The partition is the C: drive
Windows XP is installed in C:\WINXP
You have a Windows XP CD

If any of my assumptions are wrong, let me know what is different.

Also let me know the exact text of the error you get when you try to boot it.

Thanks
James

#12 Llarik1

Llarik1
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:10:21 AM

Posted 16 July 2012 - 03:24 PM

The assumptions are partially correct.
Desktop computer
Asus P4s333
the 'puter formerly was a server with windows 2000 server on it.
After a hard drive problem, a Windows 7 machine is being used as the server, and this machine was being made into a workstation.
When it last booted (yesterday) I had a windows xp home edition on drive C with the win2000 only being in "the old computer structure" folder and therefore not bootable to win2k. It also had windows xp professional on a second hard drive - also bootable at startup.
(I had to do a bootcfg /rebuild to allow it to boot to either the windows home or the xp, but was booting fine to either).
Since I wanted the WinXP professional to be the system used, I removed the C-drive that had the winxp home, and had had the windows 2000-server previously. When I attempted to reboot, I get the error that reads: "Windows2000 could not start because the following file is missing or corrupt: \WINXP\SYSTEM32\CONFIG\SYSTEMced starting options for windows 2000 press F8. (apparently the error message incompletely overwrites a previous line)

I tried rebuilding boot.ini (results again below:
boot.ini file

[bootloader]
timeout=20
default=multi(0)disk(0)rdisk(0)partition(1)\WINXP

[Operating Systems]
multi(0)disk(0)rdisk(0)partition(1)\WINXP= "xp-pro sp3" /fastdetect
multi(0)disk(0)rdisk(0)partition(1)\WINXP= "WinXP Professional SP3"
multi(0)disk(0)rdisk(0)partition(1)\WINXP= "y" WinXP professional
multi(0)disk(0)rdisk(0)partition(1)\WINXP= "winXP-professional Sp3"
multi(0)disk(0)rdisk(0)partition(1)\WINXP= "Winxp prof sp3 /fastdetect" /fastdetect

Also when it is asking me to pick a os above, it says that windows 2000 startup options press F8.

#13 James Litten

James Litten

    Ԁǝǝ˥q


  • BC Advisor
  • 1,946 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:09:21 AM

Posted 16 July 2012 - 04:16 PM

I apologize but I am still pretty confused so take this advice with that in mind :)

Use your Windows XP CD to boot the machine into recovery console.

Be sure to choose the operating system
C:\WINXP
(if it is something other than that it may point to what the problem is)

Enter the administrator password (or press enter if there is none)

You should be at a C:\WINXP prompt.

type
fixboot
and hit enter.

Answer y when asked if you are sure. Type exit to close and reboot the computer.

If it still has the error with
C:\WINXP\SYSTEM32\CONFIG\SYSTEM

Then it is probably another issue specific to that XP install.
(Though I recognize the error with the weird overwritten "SYSTEMced" part as a kind of common registry error with booting Windows 2000)

If you decide to try this, let us know how it turns out.

James

#14 Llarik1

Llarik1
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:10:21 AM

Posted 16 July 2012 - 04:41 PM

Already had done that with boot to recovery console,

Attrib -h-s-r c:\boot.ini
Del c:\boot.ini
BootCfg /Rebuild [That is where the variant names in boot.ini for the installation came about].
Fixboot

but didn't change the error.

#15 James Litten

James Litten

    Ԁǝǝ˥q


  • BC Advisor
  • 1,946 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:09:21 AM

Posted 16 July 2012 - 04:48 PM

You did that with an XP CD, with the prompt being C:\WINXP and fixboot's confirmation request said "Are you sure that you want to write a new bootsector the the partition C:" ?

If so, then I'm misunderstanding something about your setup. Maybe it is just corruption of the registry of that XP install. Can't say for sure :(

James




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users