I've run FrameMaker 6 in Windows 7 using Windows XP Mode, which is a feature of Windows Virtual PC. No need to install the operating system.
I use Virtualbox all the time and it has its quirks. I don't think Microsoft is to blame for Adobe's ancient code base having problems in Windows. On Mon, Sep 10, 2018 at 4:10 PM, Frank Stearns <fra...@pacifier.com> wrote: > I don't remember the issues now, but at least in Win 7 for my needs at the > time there were some show-stoppers with the built-in virtual system from > Microsoft. In contrast, Virtualbox simply installed and ran, no fuss, no > muss, with just the right set of user controls and operating options. > > The built-in "Hyper-V" might be worth a try under Win10, but to be honest, I > don't entirely trust MS. Remember, they're the ones who through their OS > issues for Framers effectively started this conversation in the first place! > YMMV. > On Mon, 10 Sep 2018, Robert Lauriston wrote: > >> Windows has its own virtual PC system. In Windows 7 it's Windows >> Virtual PC, which has to be installed. In Windows 10 it's Hyper-V, >> which is built in. > > _______________________________________________ This message is from the Framers mailing list Send messages to email@example.com Visit the list's homepage at http://www.frameusers.com Archives located at http://www.mail-archive.com/framers%40lists.frameusers.com/ Subscribe and unsubscribe at http://lists.frameusers.com/listinfo.cgi/framers-frameusers.com Send administrative questions to listad...@frameusers.com