So, glad that VM Player no longer screws up API calls to wininetdll
I admit, it was a useful distraction in not blaming microsoft for incompetent coding (at least for a while).
But, now, if an update to VM Player is performed, we have to re-register Windows??????????
WTF?
This is not to be tolerated.
As a developer, and one who has praised VM, I am now coming up short.
Last time it was the API issues, now, it's re-reg Windows. As we know, microsoft only allow so many.
I went out on a limb to advocate VMWare for MY CLIENTS.
Now, it is a stone around my neck.
Bullshit like this ---- re-authorizing Windows at every upgrade to VMPlayer --- IS NOT ACCEPTIBLE!
Besides Windows, any other software that ties its licencing to CPU, HDD, BIOS etc. will now fail !!!!!!!
This is exceptionally LAME, VM People!
Not to mention 'support' means calling some guy in India who thinks his job description is to hang up anytime he don't know the answer or gets pissed when you point out that he asked the same damn question 5 times over.
Way to go VMWARE!
I've recommended your product for some time, and now you make me look like a prat to my clients.
You behave more like microsoft or apple at every turn.
I still love the product, I'll still reccommend it, but for crying out loud, get rid of the dicks and children that masquerade as programmers. Or, at least employ coders with real world experience.
PLEASE!