udaller's Posts

Thanks! Actually, I now see that they have both been installed. FWIW, the problem was that Windows 10 normally puts "Recently Added" applications at the top of the list and all I saw was the Player. I'd assumed that either the installation or the app itself made a decision about which interface to present depending on whether it was licenced or not. So I have now launched the Pro version, provided the licence nuoo/. and all is OK.

FWIW I still cannot get my WFWG3.11 VMs to work on VMWare 6 (release version) on Vista Ultimate 64-bit. However, a. before the release version I couldn't get them to work on WinXP either, but on WinXP with VMWare 5.5 everything worked fine. b. the people at VMWare clearly are not experiencing this problem. I have successfully created a WFWG3.11 VM that works fine under MS Virtual PC v7 on Vista Ultimate 64-bit, but when I tried to use the VMWare converter to convert that VM to VMWare format (to see if /that/ VM would work in VMWare), the process failed. I think the converter may only work with earlier versions of Virtual PC. But in any case, the virtual hardware in the MS product is sufficiently different that a VM created with the MS product would probably not work well, if at all, in VMWare. I tried to think about what might be different about /my/ systems, and because the WInXP system is really ordinary, the only likely difference seems to me to be that my /host/ machines are both running as workstations in a Windows 2003 server domain. Since it's quite likely that VMWare is not testing in that specific environment, maybe that's the problem - I wonder if your hosts are also in a Win2003 domain (and perhaps more importantly, whether they have security constraints imposed by the domain, or whether the script that runs during domain logon is significant. I haven't got back to VMWare on this one yet, primarily because I have no new information. But maybe we can compare notes. Peter Jamieson