CPU Identification not working in VirtualBox

[gabster2]

I have had no luck getting this software to work with VirtualBox.
It works OK with Virtual PC 2007, VMware.
I have a Vista 32 bit Guest on a Windows 7 64bit Host.
Even when Itried it from my Windows XP host, same error.
I also tried a Windows XP Guest and same error.

It seems that the CPU Identification feature is not enabled.
Is this something that is done in the virtual bios?
Are there any other software with licensing issues with VirtualBox?

[gabster2]

OK, I have had no response so I guess the answer must be no.
Below are 2 pictures I snaged from Belarc Advisor. The first shows my Virtual PC 2007 ID numbers for the virtual motherboard there.

BelarcXPVPC2007.png (34.56 KiB) Viewed 6506 times

The other, VirtualBox 3.0.10. It is missing any form of ID that the software needs to be license.

BelarcXPVB3-0-10.png (9.68 KiB) Viewed 6506 times

Is this something that can be added to VB so that license sensitive software can be autenticated the way it was designed?
For now, there are no way for me to use VirtiualBox since the main issue is this software licensing path, which VB is not yet ready for.

Any feedback would be greatly appreciated from any experts in the field.

Thanks.

[MarkCranness]

Wikipedia: CPUID:

EAX=3: Processor Serial Number
This returns the processor's serial number. The processor serial number was introduced on Intel Pentium III, but due to privacy concern, this feature is no longer implemented on later models.

Have you tried adding a network card to your VM, as the software suggested?
(Settings>Network>Adapter 1>Check 'Enable Network Adapter')

[sej7278]

flexlm doesn't work with virtualbox if that's what you're trying to use, i got the official word from macrovision or whoever owns that piece of &%$£ these days.

[mpack]

flexlm doesn't work with virtualbox

There are many versions of flexLM kicking around. I have one embedded development tool that uses it, and both flexLM and that tool worked fine in VirtualBox after a P2V - which rather surprised me. Very weak protection, hardly seems worth having!

[sej7278]

flexlm doesn't work with virtualbox

There are many versions of flexLM kicking around. I have one embedded development tool that uses it, and both flexLM and that tool worked fine in VirtualBox after a P2V - which rather surprised me. Very weak protection, hardly seems worth having!

i remember talking to someone at macrovision after they bought it from whomever, and they said their customers loved it as it was so easy to get around, in the couple of years they owned it before selling it onto the current owners, he said they had not actually done any real work on it.

the current owners point blank said to me a few weeks back that the only way its supported under virtualisation is with a flex server (which itself cannot be a virtual machine) not node-locked license files. i just ditched the software.

[mpack]

Come to think of it, I recently bought a new home PC, and rather than reinstall everything from scratch I P2P'ed from my development PC at work and then installed a new XP Retail license. That meant that the OS license had changed, the motherboard was different, so was the CPU along with every other significant bit of hardware in the machine - and the flexLM protected dev tool still worked. I imagine its PC signature is a simple derivative of the signature of the HD partition its installed on, so if you use an imaging app like Acronis (which I did) then it doesn't notice a change. Either that or it has a hidden registry flag or something which records whether the signature has already been calculated or not, again no protection against imagers. Like I said before, weak!

In this case I'm not concerned about the legalities, because this devtool was already licensed for my work PC, my home PC, and my laptop. Not my fault flexLM can't tell the difference!

[gabster2]

Wikipedia: CPUID:

EAX=3: Processor Serial Number
This returns the processor's serial number. The processor serial number was introduced on Intel Pentium III, but due to privacy concern, this feature is no longer implemented on later models.

Have you tried adding a network card to your VM, as the software suggested?
(Settings>Network>Adapter 1>Check 'Enable Network Adapter')

Hello Mark, I have tried many combination and have confirmed that my network cards are enabled and working. I checked them out through ipconfig /all and they all showed up as well as their MAC address, so isolated that possibility. But I do know that this software needs the CPU Identification number as well to allow the licensing process to go on.
It may just be that there is no solution for this issue since it is not all software that work this way.
Beside this issue everything else seems stable and great.

[gabster2]

Unless there is a way for me to see theVirtualBox's 'innotek GmbH VirtualBox 1.2' Serial Number like Virtual PC or VMware do, I will have to keep on using those ones.
I have no issues whatsoever with licensing on those ones.
Too bad because VirtualBox is much better in many ways.

[ediaz]

Anybody has a way to solve this? I have the same problem with prefsuite . and virtualbox 5.0 on Linux Host

maybe a emulator or something?

Regards!

[scottgus1]

See your other bump.

[mpack]

This is a very old thread.

I just tested with an XP VM and it has no problem identifying the CPU type. I have no idea what the OPs problem was, but like I said, he had the problem in 2009, quite possibly on a PC that was ancient even then.

Perhaps you should start your own new topic and take the opportunity to explain your problem clearly.

[ediaz]

Sorry a lot for that, I have this exact problem. I will create a new treat.

Regards!