The activation is very similar. It is just that the lions share of determining validity has now been shifted to hard drive identification.
--
Regards,
Richard Urban Microsoft MVP Windows Shell/User (For email, remove the obvious from my address)
"nrms" <nrms[ at ]discussions.microsoft.com> wrote in message news:E46D880A-73E9-4004-A016-C92EF59ECF8E[ at ]microsoft.com...
[Quoted Text] > Well I am now 100% positive that it was updating the RAID "SOFTWARE" > driver, > because I returned my system to a pre-update Ghost image, and it was still > activated. I then reinstalled the Intel Raid driver and after reboot the > activation was gone. > > Clearly this gives the lie to the MS$ claim that Vista was similar to XP > in > its activation "rules" - I NEVER once had to re-activate XP due to changes > in > software drivers (or even genuine hardware changes, come to that). I can > understand the need for Vista to detect TRUE hardware changes; but it > NEEDS > to be KEYED to hardware ID's in a way that changing driver support does > not > trigger a re-activation event. > > My beef is this. The Raid software driver had to be updated because the > one > that shipped with Vista is (frankly) not fit for service. Many > manufacturers > are currently revising their hardware drivers on a regular basis. If I > have > to go through the hassle of convincing Microsoft that I am not a pirate > every > few weeks until the software base matures, then I will NOT be best > pleased. > > As it happens I am advising my client base NOT to buy, install or upgrade > to > Vista for at least a year, until the software driver support matures. > > I have bought 3 Vista licenses for 3 PC's (2 OEM & 1 Full Retail; all > Ultimate). For this I shelled out the US$ equivalent of nearly $1100 (as I > live in rip off Britain); I *shouldn't* have to go through all this > hassle. > If Microsoft does not improve this situation with Vista SP1; my next OS > will > be Linux for sure. > > "Richard Urban" wrote: > >> Updating the Raid drivers will do this (in some instances). After the >> upgrade and a subsequent reboot, the operating system detects the hard >> drive >> as being different (new). To the O/S - it is. >
|