Quantcast
Channel: VMware Communities : All Content - VMware vCenter™
Viewing all articles
Browse latest Browse all 24426

"hw.model" flag in .vmx files not taking effect. Need a windows VM to see a specifc model of PC... help.

$
0
0

This is my first post in the VMWare forum, though I have been using VMWare products since their version 1 was released so long ago.

My problem may be fairly obscure, however the underlying mechanism that is failing for me affects a wide scope of users.

I am designing a custom FPGA-based tablet human interface device. Sort of similar to a WACOM Cintiq display/drawing tablet...

In this project I am using tablet digitizer boards originally designed for the HP Elitebook 2740p.

This matters because I have received an updated firmware from WACOM designed for these digitizers, which enables UART among

other things.

 

The problem is that the firmware updates are hardcoded to detect the system-id and board-id using the "wmic CSPRODUCT" command.

This means that unless I can modify the SMBIOS of a system to fool the firmware updater, using a VM to masquerade these identifiers

is the only solution other than purchasing a very expensive tablet PC just to update the digitizers.

 

Using VMWare workstation 10 to create a new Windows XP Virtual machine, and adding to VM's .vmx file as follows:

 

board-id.reflectHost ="FALSE"
board
-id ="0x7007"
hw
.model.reflectHost ="FALSE"
hw
.model ="HP Elitebook 2740p Tablet PC"
smbios.reflectHost ="FALSE"


NONE OF THESE FLAGS ARE TAKING EFFECT WITHIN THE VM!


I have performed at least a dozen installs and edited the config file. I have tried using a friend's private cloud with VSphere,

VMWare Workstation 10, and VMWare fusion 5 on a friend's mac. None of them seem to interpret those flags.


When I query the board-id or system-id from within the VM itself (wmic CSPRODUCT), I receive the following:

Board ID: 440BX-Desktop

Model: VMware Virtual Platform

System ID: VMware-56

etc.etc.etc


It's not using the values I specifed or giving me any failure errors when I start the VM. Help.


Why bother providing documentation on these .vmx flags if they aren't going to be active?!?!?!?!?!

I understand most folks are using it to passthrough/spoof Apple system ID's to get OSX discs running in VM's.

This is a much more useful and legitimate application of those flags, and I cannot comprehend why they are not making a shred of difference

here. Please advise, and thanks for the very useful product in the first place


Viewing all articles
Browse latest Browse all 24426

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>