-I-

sorry as im a bit late, BUT, you anyone had thought this over they would have pointed you to driverpacks.net ofcaurse its 'questionanbly to download drivers from a 3rd party website rather than from your OEM, Microsoft update or the cdrom at hand, but you could always pick a few files and compare them agains the real files.. what i did was randomly compare 1000 drivers *.sys files against the files that i downloaded from the OEM's website as expacted all md5 where correct - so no tempering was done - from that moment on i was allowed even to use those driverpacks (the exact versions i downloaded and tested) in a semi-public-service (gorvernment) workspace. what i mean to say is, there are ways to test them, and they DO save you alot of problems, i for one, since than allways include the dp_massstorage dp_lan and dp_wlan drivers in my windows xp iso's so that ... [A] i can allways install windows to the hdd (regardles of the mobo, the raid adaptor or the scsi-controller. i can allways connect the pc to either lan or wireless lan to go to windows update and install the remaining updates or drivers...

in my view if you want this badly enought, and you fear for legal issues, i would advice you to NOT use the microsoft tools ... instead you could just copy the whole ISO (win 7 installer) to a hidden partition and use a non windows bootloader, to be able to boot it if needed, some bios'es also support this kind of feature - but not verry many do (with non oem firmware). in my opionion 'we (the comunity) should focus on being able to installed windows without its boot loader' after that its not hard at all to either boot from a dvdrom iso (on the harddisk) or from a disk clone (norton ghost, or equivilant) so how do you 'patch' windows vista / windows 7 to not force itself into your Master Boot record.