Jump to content

Recommended Posts

Posted

This issue may be similar to that one http://forums.eagle.ru/showthread.php?t=38802&highlight=activation

 

Basicly I was forced to use another of my activations after doing some minor changes in the system. I did few of them between BS runs so I can't give you the element that triggered this problem.

 

I did the following:

- VMWare Player - disabled all of it's services that were running by default (set to disabled)

- VMWare Player - disabled its network adapter(s) *

- Hamachi - disabled its network adapter *

- Black Shark - started (SP mode)

 

* - in the Network and Sharing Center

 

Windows 7 x64

Windows UAC disabled

security software: Comodo Internet Security 4 (only SandBox disabled)

 

 

So, you might want to deactivate your copy of BS before doing any similar changes to your system and then activate again without using up even one of your activations.

Posted

It was VMplayer. I installed VMplayer before and was asked to activate DCS again. I simply uninstalled and DCS was fine.

 

It seems starforce views the dummy network adaptors as real hardware and triggers the activation accordingly.

 

Nate

 

Edit:- Disabling network adaptors does not remove them from the list of devices in device manager BTW

Posted
It seems starforce views the dummy network adaptors as real hardware and triggers the activation accordingly.

 

It's not starforce that "views" them as real hardware - it's Windows that reports them as real hardware. Since ED uses a StarForce ProActive implementation that does not have a driver there simply is no way for the protection system to distinguish between virtual and real hardware.

[sIGPIC][/sIGPIC]

Daniel "EtherealN" Agorander | Даниэль "эфирныйн" Агорандер

Intel i7 2600K @ 4.4GHz, ASUS Sabertooth P67, 8GB Corsair Vengeance @ 1600MHz, ASUS GTX 560Ti DirectCU II 1GB, Samsung 830series 512GB SSD, Corsair AX850w, two BENQ screens and TM HOTAS Warthog

DCS: A-10C Warthog FAQ | DCS: P-51D FAQ | Remember to read the Forum Rules |

|
| Life of a Game Tester
Posted
It's not starforce that "views" them as real hardware - it's Windows that reports them as real hardware. Since ED uses a StarForce ProActive implementation that does not have a driver there simply is no way for the protection system to distinguish between virtual and real hardware.

 

Good to know, but the end result is the same.

 

Nate

Posted

Yeah, with the small difference that it means there's nothing ED can do about it.

[sIGPIC][/sIGPIC]

Daniel "EtherealN" Agorander | Даниэль "эфирныйн" Агорандер

Intel i7 2600K @ 4.4GHz, ASUS Sabertooth P67, 8GB Corsair Vengeance @ 1600MHz, ASUS GTX 560Ti DirectCU II 1GB, Samsung 830series 512GB SSD, Corsair AX850w, two BENQ screens and TM HOTAS Warthog

DCS: A-10C Warthog FAQ | DCS: P-51D FAQ | Remember to read the Forum Rules |

|
| Life of a Game Tester
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...