Terry, Justin, thanks for the advice.
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.
Thanks for your time guys. John