Starforce has blocked any usage of VM's during protection execution. Because this could be used to create a key that would work everywere a VM with the same config is used.
Also here's a little update on Starforce
Quote:
anyway - i read this on reverse-egeneering.net forum from a developer working for ubisoft:
Starforce 3.5.00.08
*Fixed: USB2-Problems
*Fixed: A hole allowing "Mini-Images" again
*Fixed: Advanced Debugger-Protection
*Improved: Starforce Virtual Machine (tm) v2.7.98
*Added: Reactivate iDE-Channels on startup
*Added: Detection of StarFu**/SFN
*Added: Protection of Protection-Drivers
*Added: The exe isn't completely dumped to Memory now - a full dump is nearly impossible
|
Got this from another forum, if it is true the USB2 trick is gone...
But there's light in the tunnel, look at the "Reactivate iDE-channels on startup". This can be considered illegal in many eu countries as the end-user has decided to deactivate iDE channels. So Starforce changes settings for the end users... Let sue them bastards....
