From: Jasen Betts on 7 May 2010 05:14 On 2010-05-06, Andrew Smallshaw <andrews(a)sdf.lonestar.org> wrote: > On 2010-05-05, Stuart Longland <redhatter(a)gentoo.org> wrote: >> On Apr 27, 9:07?pm, John Tserkezis >><j...(a)techniciansyndrome.org.invalid> wrote: >>> >>> ?No idea about Vista, but have installed Win7 several times so far, and >>> yes, your only option is F6 to look at drive A:. >> >> Good grief, and here I was thinking Microsoft _finally_ got around to >> fixing that. (I mean, cripes... at least look at a flaming CD >> fellas?!) > > That can create problems in the truly general case. Think about > it: you are loading drivers for an HBA and want to get them from > a CD-ROM, potentially attached to that very same HBA... There is a way to merge drivers ioto a windows install CD image, ( obviously this required writing a new CDR) AIUI microsoft calls it "slipstream" > Of course the most elegant way would be to place basic get-you-home > drivers on the device itself. Sun managed this twenty years ago > with their OpenPROM system, and that didn't even depend on the CPU > since they were written in architecture-independent Forth. However > that probably requires the kind of centralised planning and > authoritative "this is the way it is going to be done" assertion > that is difficult to enforce for commodity x86 hardware. The only > time I can see you doing it is with a new bus standard: if e.g. > PCIe had demanded it manufacturers would have little wriggle room. I think ACPI is something like that. --- news://freenews.netfront.net/ - complaints: news(a)netfront.net --- |