> Try changing the Boot.ini of only one OS to read "disk(3)",,,,,leave
> everything else alone and then reboot and see if it will boot into that
> OS...........................if it does then you need to change the other
> OS Boot.ini .
> If it does not boot to the OS you have not changed and change the other
> OS's Boot.ini file back.
Your mention of multiple boot.ini files is interesting.
Initially I only had one boot.ini file--on the first SATA drive. It has
multiple partitions; the first two (C: and D

contain, respectively, XP
32-bit and XP 64-bit.
At some point in the past *something* decided to create another boot.ini
file on one of the IDE drives--XP's disk manager labels it "Disk 1" ("Disk
0" is another IDE drive).
This file contains the following:
[boot loader]
timeout=20
default=multi(0)disk(0)rdisk(1)partition(2)\WINDOW S
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Micro soft Windows XP
Professional x86 Edition (200GB IDE)" /noexecute=optin /fastdetect /PAE
/BOOTLOG
multi(0)disk(0)rdisk(1)partition(2)\WINDOWS="Micro soft Windows XP
Professional x64 Edition (200GB IDE)" /noexecute=optin /fastdetect
....which I find confusing if I compare it with the boot.ini file on C:.
Regardless, I've kept that file around and I've added the "200GB IDE" part
just so if that's ever used, I would be able to differentiate it from the
boot.ini file on C: (which would show "250GB SATA"). That's actually
happened once when I was trying to disconnect/reconnect various drives.
This partition also contains its own ntdetect.com and ntldr files. This
partition has never contained a bootable OS.
Right now I consider myself the machine boots at all, so I don't even dare
try to get rid of those files "just to see if it'll still boot". I'm not
particularly bothered by the presence of those files right now...