![]() Perhaps more importantly, we regularly use Answer Files (unattend.xml and autounattend.xml) to support custom Windows 7 and Windows 8 installation. Since Windows Virtual PC and XP mode are important alternatives for supporting legacy applications and compatibility solutions, the use of floppy media is rather important. The functionality is still available via the COM object. The functionality is not removed, though the interface was removed by design. There is no hidden menu or settings screen either before or after a virtual image is mounted. Under Windows 7, the graphic interface for Windows Virtual PC does not include support for virtual floppy drives. If you install Windows XP mode using Windows Virtual PC, host integration enables the use of host based floppy drives (as well as USB and other removable storage alternatives). In fact, one of the major complaints regarding Windows Virtual PC limits is the inability to support virtual floppy drives. One of the advantages of Hyper-V over Windows Virtual PC is expanded hardware support. In fact, Microsoft continues to redirect Windows 8 Client Hyper-V queries to the technet articles referencing the 2012 server version of Hyper-V: Install the Hyper-V Role and Configure a Virtual Machine. Hyper-V is a far more robust solution that Windows Virtual PC. We reviewed the related requirements in a prior blog post: How to enable and Use Windows 8 Client Hyper-V. ![]() Microsoft supports virtualization on the Windows 8 Client solely through Client Hyper-V, on slat enabled systems. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |