OSS Cannot find Second OS
I have WindowsXP sp3 installed on Disk 1 set as Master.
I have Windows2000 sp4 installed on Disk 2 set as Slave.
Acronis DD 11 home and OSS installed on Disk 1
On boot-up, OSS shows Windows and floppy as expected and I can boot WindowsXP.
In My Computer I see Disk 2 as Drive D:
DD shows disks as:
Disk 1(MBR) primary MBR healthy(active, system, boot)
Disk 2(MBR) primary MBR healthy(active, system, boot)
Starting OSS and try to detect second OS but unsucessful. Look in both MBR and partition.
boot.ini, NTDETECT.COM and ntldr on root of Disk 2.
What step am I missing?
I current swap disks between WinXP and Win2000 in my system. I was hoping to be able to use AOSS to accomplish the same thing. Ideally having both OS on a single disk.
Problem Solved!
MudCrab, your question about the BIOS Boot Menu prompted me to look at the BIOS. Never questioned the settings as WindowsXP could see the slave drive. However, BIOS had the primary slave turned off. I turned it on and although BIOS didn't recognize it as a hard drive, on re-boot, OSS could see the Windows2000 OS and I am now able to boot either OS as required.
Getting both OS on the same drive seems to be more of a problem. Windows2000 installer sees all partitions on the drive as unformatted/corrupted although both WindowsXP and ADD see them as formated NTSF. Windows2000 installer also sees 250GB drive as only 130GB although it sees individual partitions as corrected size, namely 200GB/10GB/33GB.
Windows 2000 may only see @130GB if you haven't modifed it. You might want to take a look at this Microsoft KB article. Corruption may occur if it doesn't see the drive correctly.
Windows 2000 also sees standard hidden partitions. You would need to super-hide them to avoid this. Note that this option is somewhat risky because it removes the partitions from the partition table.
MudCrab,
That KB applies to sp2. I'm at sp4 so it's not an issue. Windows2000 sees the 250gb drive correctly if Windows2000 is installed on it. It also sees it correctly as Drive D when Windows2000 is booted off the slave drive. Also note that the installer sees the drive as 150GB but sees the partition as 200GB.
Anyways, all academic as the computer works properly now that the BIOS recognizes the slave, even if it's an unknown device.
You said the Windows 2000 installer wasn't seeing the drive correctly. Is the installer SP4? The KB article makes it sound like the fix needs to be applied even if using SP3 or later. This makes me think that the installer may not see the drive correctly. You also said it sees the drive as 130GB in post #3, not 150GB.
===QUOTE======
Important: Although support for 48-bit LBA is included in Windows 2000 Service Pack 3 (SP3) and later, it is still necessary to create the registry change that is described in the "Resolution" section of this article.
===QUOTE======
I don't have Windows 2000 and never used it so I'm just passing on info. From experience, I know that there are quite a few problems with using larger drives and older versions of Windows. Throw in older hardware and the problems increase.
Windows2000 install disk I have is labeled "Windows2000 SP4" so I can only presume that the installer is also updated to SP4. In addition, if I use the install disk to install Windows2000 on a 250GB disk that has been totally wiped, it sees the entire disk with no issues.
I did notice when experimenting to try and understand what was going on that if a disk had AOSS installed on it, than Windows2000 wouldn't install. After trying to format the drive I would get a message that the drive was damaged. I noticed that the available space on the partition was about 68MB smaller than the partition. Deleting the partition at the start of the install and then re-creating it reduced the hidden files to 7.8MB so I conclude that AOSS had put some hidden files on the partition that aren't removed just by re-formating. Windows2000 isn't able to handle this and declares the disk damaged.