These are just more of your uniformed "opinions", db. Having the
operating systems on different partitions on the same disk causes no
more inherent HAL corruption risks or problems by than having them on
different hard disks. As I said earlier, if you setup a multiboot
system using the standard Microsoft method the operating systems will
all share the same system partition and they will all use the same
boot.ini, NTDETECT.COM & ntldr system files, it doesn't matter where the
operating systems reside, they will still all use the same shared system
files mentioned above.
What you might think of a possible HAL problem is not a HAL problem at
all. If the boot.ini file is damaged or removed you may get a
misleading HAL is missing or corrupt message. It doesn't matter where
the operating systems are located, if the boot.ini file is missing or
damaged the same error message will be given when you try to boot
Windows. This is a very well known problem which, amongst other places,
is documented here:
http://support.microsoft.com/kb/330184
As for the corrupt HAL problem that might occur if you install Windows
2000 after Windows XP is installed that is yet another thing that you do
not understand about multibooting these operating systems and it is
something that would happen regardless of where the operating systems
are installed. This is caused by the same shared system files issue as
mentioned above. When you install Windows NT/2000/XP the setup program
installs its versions of the ntldr and NTDETECT.COM files, if those
files are already present they will be replaced by the version belonging
to the operating system being installed. If you install Windows 2000
after Windows XP is installed the Windows 2000 setup program will
replace the XP versions of the ntldr and NTDETECT.COM files, it doesn't
matter if you install Windows 2000 on a different disk or on a different
partition on the same disk as Windows XP, the files will be replaced.
The so called "corrupt HAL" problem here is that the older Windows 2000
versions of these files are not fully aware of Windows XP and they
cannot properly boot the newer Windows XP, once again this is a
misleading error message, when this happens there is absolutely nothing
wrong with the HAL in question. The fix to this also very well known
problem is to simply replace the Windows 2000 ntldr and NTDETECT.COM
files with the XP ones, it is so simple to fix that even an 8 year old
child could fix it. The Windows XP versions of those files are fully
aware of the earlier Windows NT/2000 and they can properly boot the
older operating systems.
As to your comments that "... when the o.p. posts a new issue regarding
a crash because of hal, you guys are as silent as empty space when it
comes to helping." then have a look here and see for yourself how silent
we are:
http://groups.google.com/groups/sea...q=audetweld+shared+ntldr&safe=off&qt_s=Search
The only empty space around here is between your ears so please spare us
from more of your ill informed opinions and advice!
John