Same message as before. I pressed F8 immediately. The boot menu then offered the option to select Window 7 New and press the F8 button for extended settings. Same error message.
You have made a good point thought - as did load the Areca RAID 64bit drivers as part of the installation. I have checked their web site and I beleive they have been certified. Normally they issue a warning if they haven't.
The easiest way of circumventing Windows permissions, ownership etc, without needing to change everything (which would take me all night to remember then explain), is to get yourself a Live Linux distro, burn it to CD, boot it in "don't change my system" mode, and use it to drag the new copy into the W7 windows\system32 folder after renaming or deleting the old one. Linux doesn't give a fig for Windows permissions.
It's always a handy thing to have in your tool box, even if you don't install/dual-boot it. It's the easiest way of rescuing data from a broken system. You might even like it enough to create another partition for it and do a proper install.
Before I take any further action please can I clarify the following:
1) Linux: If I use Linux to modify copy/replace/rename the files, will this OS be able to access the Windows 7 Directory which is located on the RAID Volume without loading the associated RAID drivers?
2) Justin's solution appears more simple, but I must be absolutley clear on the syntax as I do not wish to amend the attributes of the Winload.exe on my Vista drive. Would the syntax be as follows 'attrib -r -s W:\%windir%\system32\winload.exe'
I am not sure why Window 7 is generating this error message in the first place. Could itbe because I mistakenly used the 32bit serial number when installing the 64bit version.
Would the following not work:
a) Disconnect all drives other than the RAID volumes.
b) boot from W7 DVD.
c) Reinstall the W7 64 bit OS on the W: drive (RAID 0 volume), intall the 64bit RAID drivers via custom install, and then reboot when completed
d) change the boot sequence so that this volume is 1st in the sequence (see query below)
e) Test if I can boot into W7
f) Connect all drives, change the boot sequence so that the Vista drive C: is 1st
g) boot into Vista via the Bootmng Menu to test load of OS
f) Boot into W7 via the Bootmng menu to test load.
The reason for disconnecting the drives is toa avoid the W7 Installation from screwing up the Vista/Bootmng configuration.
Query. Window 7 (W: is a partition one partion of two on the RAID 0 Volume,. To enable it to boot would the W: partition need to be the 1st partion on the RAID 0 Volume.
I can't say how Ubuntu reacts to RAID, I have never used it so have no experience.
Your idea of an independent re-install should work as outlined, unless the problem was RAID induced in the first place. Did you ever have W7 booted successfully ?
Having Installed W7, I remember having a good look around. However, when I shut down and tried to get back into Vista, which failed, my focus was to get this OS up and running. I don't think I ever booted into W7 from this point onward.
I think I will try my solution following your comments as I beleive this solution will offer me added flexibility. If I can boot to W7 successfully by changing the boot sequence; if my Vista drive ever failed, I could use W7 as my OS with very little downtime. All my data is stored on the Raid drives.
This exercise is going to take some time as I wish to take a number of backups along the way. Hopefully I will get back to you with a success story. Have a good weekend.
P.S. Am I correct in stating that W7 needs to be located in the 1st partion of a drive for the OS to boot from that drive.?