| Windows XP/2000 - How do I get rid of Windows XP Setup? posted in the Operating Systems forums; Further experimentation: On the 98 drive I renamed that $WIN_NT$.~ls directory and then rebooted with that as the startup drive (via BIOS)- nothing bad happened, so clearly that's not a ... |
 |
|
|

11-19-2005
|
|
 |
Bronze Member
|
|
Join Date: Nov 2005
Posts: 38
|
|
Further experimentation: On the 98 drive I renamed that $WIN_NT$.~ls directory and then rebooted with that as the startup drive (via BIOS)- nothing bad happened, so clearly that's not a problem.
Then I renamed BOOTSECT.DOS. I still got the two options - Microsoft Windows and Windows (default), but now the former wouldn't boot into 98, giving the IO Error about BOOTSECT.DOS.
So clearly this file is needed for booting into 98.
But also clearly, there's something that gets read before BOOTSECT.DOS that makes the computer think there are two OSs on this drive.
And it isn't boot.ini
- Bob
|
|

11-19-2005
|
|
 |
Elite Member
|
|
Join Date: Jun 2005
Location: Netherlands
Posts: 9,044
|
|
You've been busy. lol
Try editing the XP's boot.ini to this below:
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOW S
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Micro soft Windows XP Home Edition" /fastdetect /NoExecute=OptIn
C:\="Microsoft Windows"
or:
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOW S
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Micro soft Windows XP Home Edition" /fastdetect /NoExecute=OptIn
multi(0)disk(1)rdisk(0)partition(1)\C:\="Microsoft Windows"
And if that also doesn't work:
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOW S
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Micro soft Windows XP Home Edition" /fastdetect /NoExecute=OptIn
multi(0)disk(1)rdisk(0)partition(1)\WINDOWS="Micro soft Windows"
You where on the right track i think , but you where using "rdisk" instead of "disk" to select the HD.
"rdisk" is the node address of this disk on the controller , not the HD.
ps , watch with copying and pasting , there are spaces where they shouldn't be!
sorry , i can't seem to remove them , they come back..
__________________
- PCHF Team. - (NL) - Mal-ware Eradicator! -
Last edited by joe5; 11-19-2005 at 07:10 AM.
|
|

11-19-2005
|
|
 |
Elite Member
|
|
Join Date: Jun 2005
Location: Netherlands
Posts: 9,044
|
|
Only with scsi controllers , not with ide. Here's some extra info:
Which hard disk will be used?
rdisk(0)
The next part of the naming convention will always be rdisk, as it provides the node address of this disk on the controller.
Only SCSI controllers have multiple nodes, therefore for a true multi (IDE or similar) controller, the number here will always be zero (0) . When a SCSI controller is involved, this number will be the SCSI ID number of the designated boot disk on that controller. Early SCSI controllers used SCSI ID numbers from 0 to 7, with ID# 0 (zero) normally reserved for the boot drive's address and ID# 7 reserved for the SCSI controller itself. You may want to make a mental note here that you can boot to any of the first 7 SCSI ID numbers: 0, 1, 2, 3, 4, 5 and 6.
Some of the SCSI controllers that have been manufactured over the last few years may have as many as 15 SCSI ID's, but again, ID# 0 (zero) is still reserved for the boot drive, and ID# 7 is still reserved for the controller. These SCSI ID's identify the disk's address on the SCSI controllers chain.
Where is the hard disk located?
disk(0)
The third part of the name, disk(0), identifies which disk, at the node address specified under rdisk. Here, the boot hard drive on the SCSI controller must be zero (0), since only IDE and related controllers support master/slave disk configurations. The hard drive configured as a master on an IDE controller will be disk(0) and the hard drive configured on the same IDE bus as a slave will be disk(1). On a dual-channel EIDE controller, this number could be anything from 0 to 3, and today with the number of specialty motherboards with dual IDE/EIDE controllers, as well as the number of add-on controllers with interfaces for several IDE/EIDE drives, this number can be as high as 7.
from:
http://www.dewassoc.com/kbase/multiboot/boot_ini.htm
__________________
- PCHF Team. - (NL) - Mal-ware Eradicator! -
|
|

11-19-2005
|
|
 |
Bronze Member
|
|
Join Date: Nov 2005
Posts: 38
|
|
Well, none of it worked. The first option was something I'd already tried. That's when I'd get the error message about needing bootsect.dos. I copied the bootsect.dos file over from the 98 drive and then no error message but just a blinking cursor.
The other two options gave me nothing. I got two boot choices, but when I selected the second option nothing happened, the computer just rebooted like it didn't find anything. I tried both these options with both disk(1)rdisk(0) and disk(0)rdisk(1), just to cover all the bases. Same results in all cases.
- Bob
|
|

11-19-2005
|
|
 |
Friend of PCHF
|
|
Join Date: Sep 2004
Location: Right here !
Posts: 2,150
|
|
You could try and replace the Windows 98 boot.ini with what you posted earlier on in the thread. (so basically putting it back to the way it was)
[Boot Loader]
Timeout=5
Default=C:\$WIN_NT$.~BT\BOOTSECT.DAT
[Operating Systems]
C:\$WIN_NT$.~BT\BOOTSECT.DAT="Microsoft Windows XP Setup"
C:\="Microsoft Windows"
And then delete the line with "C:\$WIN_NT$.~BT\BOOTSECT.DAT="Microsoft Windows XP Setup" in it.
|
 New! Norton Internet Security 2008 – Download Now Click Here |
|
| Thread Tools |
|
|
| Display Modes |
Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
|