Hi jaclaz, I hope you still are around here somewhere, or I'll have to look around for you
As you know, I am crazy and always looking for things to do with my computer. The latest fad is to install a SSD drive with the hope of making some operations a little faster.
I have three drives/three systems but will go for two drives and two systems: Win XP and Win7
My current boot.ini on the first drive, XP, is:
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect
C:\Windows7.bin="Windows 7 disk"
I got a 128GB SSD drive, made two equal partitions, with XP on one and Win7 on the other partition. One or two of my old drives will be assigned as D, E, Ö drives as required.
I did however realize that only one partition could be active on the SSD so for the time being, I will keep my existing Win7 drive as it is, with no changes.
I start with the SSD as disk(0) partition(1) XP,
Old Win7 disk as disk(1) partition(1)
(BIOS boot order also is disk 0 before disk 1)
The boot.ini is activated, selecting XP works as it should.
But when I select Win7 I get msg about missing file:
Windows root > system32\hal.dll
But hal.dll is of course resident on C:\Windows\system32\
I havenít tried putting a copy on the root, donít know if that would be a good idea.
Donít want to experiment too much in fear of creating further problems and disrupt system, I want to have 100% uptime available on email and google access.
Can you solve the problem for me?
(I have the BOOTMGR file and the boot directory and files in the XP root.) But donít know If they are needed.
What I suspect is I may need to run bootpart. But I would prefer some input on how to do it.
I have saved all or most of oour earlier exchanges and have studied them but I have to admit, I feel like I am in deep water. Is there a limit to how far my brain is willing to go? I honeslty don't know, will be 83 on thursday so some deterioration is possible.
I have taken a look at http://thestarman.narod.ru/asm/mbr/
but I donít find anything of use there.
BTW, The Starman wrote in a old document: Iv'e saved "After initially using "Startup and Recovery to" view a certain BOOT.INI file under Win2k, I changed the "Active" partition with a disk editor and the nexxt time i used this feature (without rebooting!) it opened a completely different BOOT.INI from the root directory af the other partition."
Could that be used to allow me to actually have boh t XP C. and WIn7 C: volumes on the SSD, and make one or the other active from a startup script or something?