I would definitely consider that less-than-new for the purposes of Win7-x64 (in my experience)... however, the fact that you're trying to install on a VM may change that "less-than-new" status, for better OR worse (could make it act more "new"... or just plain "old"... or maybe it will retain "less-than-new" status like the hardware itself).
My work around was simply not to boot from those disks on those computers... this is in my work environment... I simply booted from those disks, as necessary, on computers that WOULD work... then used imaging tools (ghost, dd, etc.) to move the OS onto the computers that would not boot directly. So... the short answer is, yes I found a work around... but I don't know that it would be helpful in your circumstances - especially given that we don't even know whether you're having the same problem. Are you trying to boot from a 64-bit Win7 installation disk? I never had trouble with the 32-bit versions. I suspect the issue that I was running into was that, while the computers were fully 64-bit capable, there was something in the BIOS (or, perhaps other firmwares on the system) that were not quite up-to-snuff for the new 64-bit world. On Thu, Apr 19, 2012 at 3:40 PM, Rich Shepard <[email protected]>wrote: > On Thu, 19 Apr 2012, Rick wrote: > > > I have had trouble booting from Win7-x64 install disks on some (multiple) > > less than brand-new systems (never a problem with Win7-x86, though)... it > > wouldn't surprise me if a VM had similar problems. > > Rick, > > The Latitude was built June 2010. Does that qualify as "less than > brand-new"? Regardless, is there a work-around? > > Thanks, > > Rich > > _______________________________________________ > PLUG mailing list > [email protected] > http://lists.pdxlinux.org/mailman/listinfo/plug > _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
