Windows 10: vmware workstation 12 out now - built for W10

Wow read through this post from beginning to end, very interesting....

I have a Windows 10 Home PC which I want to run XP on also, the fact that XP is running on a W10 PC needs to be virtually transparent to the user....would like easy support for USB pens, so do I use Hyper-V , VMware, or try dual boot ( which doesn't look difficult ) would be ok not to have both OS available at the same time...

thanks

 

There's a vast contrast between how you go about seeing XP go on at this late date. One word of advice is on VM and not any dual boot on physical drives without unplugging the 10 host drive first to see XP as a stand alone install on a separate drive. And there's a very good reason for that.

Besides already having been dropped from MS support a year ago April you won't find any device drivers unless you are presently running 10 on an old boat anchor! Newer hardwares simply see no support for any physical install while the better option would be running the XP mode on one of those two options.

As for VM ware you can run multiple VMs at the exact same time as long as you have the extra memory available. Sometime back I would have XP Home, the XP mode, Vista, and 98SE all running simultaneously on four VMs until the 4gb simply wasn't enough back when first looking into the old VM Player free version no longer seen. That also had the Player Pro replaced as well now with the Workstation Player Pro simply adding "Workstation" which there has been all along a Workstation version as well as the Player.They simply put the two names together now seeing the option to buy the commercial license on the Player version as well as what you would find on the Player Pro to upgrade the Player to Pro.

With the Hyper-V feature enabled you will find quite a bit more as far as options and settings while you are only able to run one VM at a time. The Hyper-V Manager won't allow even a second vm to start up while you have to work with for the single vm. You would be better off there with the XP mode I was under the impression the XP mode was the vm form of XP Pro if not mistaken since that was mainly intended to get businesses to upgrade to 7 back when first released as a 90 day evaluation tool. That was so businesses could still keep their XP apps running on a vm instead.

 

At first it will take a bit in order to get familiar with how things go for each of the options referred to as well as other methods available. The Hyper-V is definitely a little bit more involved there but not too difficult to grasp. The Workstation Player and Virtual Box do tend to simplify things more so.

Reviewing the guides for VM Workstation and Hyper-V in the tutorial section is always a good place to start! But if you should get stumped for any reason you can start a new thread in the Virtualization section easy enough. *Smile

 

Any hypervisor would do. Whether you want to do that or dual boot depends on what you want to use XP for.

Are you wanting to run XP as some old hardware doesn't work or some old program?

Note that it would probably be unwise to connect a XP machine (real or virtual) to the internet as you'll not get security fixes any more.

 

XP is needed for some old software which refuses to run on any OS post XP.....dual boot would be fine, selecting which OS at startup..

Interesting, your comment on XP not being secure on the Internet, just visited my local branch of TSB bank while he was starting the PC up to check my account I notuced it was running XP not good for a major bank I would have thought...

 

XP by itself wouldn't be secure! But you have to also consider the additional layers of security banks as well as other commercial interests will see added on. They typically have professional software developers and security analysts on the payroll advising them on how to keep things secure, develop new firewalls, etc..

As for as not being able to run old XP apps on anything newer that would be have pertained to Vista which saw a gap especially when Fat support was removed entirely while XP could be installed on a Fat32 primary. When 7 came along however MS had to put the old support back in along with the new MinWin kernel where suddenly the 32bit side of 7 had not a problem running many older XP apps without the compatibility mode needed!

Have you ran the 32bit 7 at all? Try Metal of Honor: Allied Assault as one XP Only title that certainly wouldn't run on the 32bit Vista no matter what as well as any 64bit Windows but went right on the 32bit 7 while 7 was still in it's own beta to RC stages. 7 being a newer version to begin with will still be seeing support until 2020 being a preferred option as far as any physical install. You shouldn't have any problem locating any device drivers while XP as well as any other OS can be run on the virtual side without too much difficulty.

Here to find having both XP and 7 media still onhand I would see two VMs for finding just what will run on 7. Yet at this time another option still comes up depending on the type of app you have if that just happened to be something even older like Legacy/Dos compatible where you could use an extra like DOSBox. Speaking of old how about some old 8 bit stuff! *Eek*Biggrin





That was on the 64bit 7 RC at the time there. So "just imagine the possibilities" with the much more advanced options a program put out by VM ware will see in comparison to that basic emulator there. And what some don't want to hear but the way things are going Virtualization by itself is still a growing field.

 

thanks for the very informative reply

 

Well there's actually a number of options available. You can try each or just one. That will be strictly your choice there. All I could do was pass along what I had found years back when having XP titles as well as other things that wouldn't run on Vista or the 64bit 7 but on the 32bit 7 not one problem. And that still sees support as far as seeing any dual boot set up go for hardwares as well as regular updates.

You would need to disable the automatic upgrade to 10 factor however with any 7 install or simply not see SP1 installed! A monkey wrench tossed into the works? I keep finding the BT and WS folders on the 7 drive here despite disabling the registry even from allowing upgrades! Having those extra storage drives plugged in is another preventative to protect the 7 side of the dual boot here.

 

hi, guys, just some little questions about the free version:

does it work in a LUA (SUA)?
how many processes/services run at log-in?
is it fully compatible with TH2?
does it supports snapshots?


Txs in adv

 

If you have ever run VM Player in the past despite the additional features as well as the option to buy the full Pro license not seen in the previous Player you still select either iso for the OS you have onhand or select the D drive option for the physical optical drive. Once you go to "play" the new VM the Windows installer will run as always You can run the Threshold 2 release as well as a Linux distro.

Just don't assign too much to a VM. If you are only running with 4gb you can have four VMs running at once but could run out of resources quickly! When planning the present build still running 7 in a dual boot with 10 I went for the 16gb so I wouldn't ever run into that problem again as I did years back.





The XP Mode and another Windows XP vm at the time both saw 2gb assigned while only having 4gb of memory! But it was the four vm total with the others one wanting a 1gb and the other 512mb that made the day. There is one factor that will prevent the Workstation Player from even running however that being having the Hyper-V feature enabled which will automatically cancel VM ware out!

The Workstation 12 Player replaces the VM Player 7.2 being the last totally 100% for home use only release since the Workstation Player like VM Player can be upgraded to Workstation Player Pro as VM Player would see VM Player Pro with the Workstation Player including the purchase option for the commercial license. Otherwise one replaces the other but now includes the buy option.

 

Up ...

 

What are you referring to specifically? The task manager will show just under 23kb for the main gui before running any VM you have created. Then you have to go from there to figure things out depending on how much memory was allocated per vm as well as the cpu setting as for how many cores, etc.

 

Maybe my english is not so good so i'll try to explain me better...

does it work in a LUA (SUA)?
Yes/no

how many processes/services run at log-in?
1,2,...100?

is it fully compatible with TH2?
Yes/no (in particular, is win10 TH2 supported as host OS? Yes/no)

does it support snapshots?
Yes/no

 

What is LUA (SUA)> Programming language? That was what I came up with from a Bing search to find out just what you are referring to. The Lua site is for a scripting language with a multiple platform version since Linux and Mac come with the Lua option included it seems. LuaDist

You haven't specified just you mean there. As far as compatibility the latest Workstation 12 Player as well as the last VM Player 7.2 seen out on June 15th before 10's launch date a month a half later will run on 10 without a glitch! I had just gone for the June 7.2 release when the Workstation 12 Player was out on August 15th two months later.

As far as how many processes you will only see the main VMPlayer.exe listed in the Processes of the Task manager using just under the 23kb as I mentioned before. It's when you start up a VM depending on the OS and what you have on that which will add more weight as far as using more system memory and some cpu time as well depending on that is configured. That's when you can examine the processes but won't expect to see any larger number of them since the host OS 10 is seeing VM ware run while the other OS runs in a box isolated from the host.

 

LUA~SUA= Limited (Standard) User Account


What about snapshots?
Are they supported in the free version??

(i'm a Virtualbox user)