Rhinox

First off: I do not see any problem with my language, maybe except that f-word used for StarForce (which I starred-out), especially if I consider myself being (let me say it politely) "incorrectly and/or insufficiently informed" by ED. Now, to the problem: no offence, but from what you wrote it is clear to me, you are not expert in this area (emulators). Just to bring a little light on the subject: 1. VMWare is not system emulator. It is a virtualization software, but what it creates is "virtual machine", or virtual computer, but definitely not system! The system, which you install afterwards, is in NO WAY changed! The same installation CD is used, the very same installation procedure... 2. Virtual computer can not defeat your protection system more, than any other computer. As I wrote, it is not virtual system, it is just virtual hardware. Of course, I could create more virtual computers and try to install & run LockOn on many of them, but: a) I would need different activation code for each of them (virtual hardware has random-generated serials for disks/eth, etc) b) I doubt there is some computer which could run 5-6 instances of LockOn in parallel. 3. I do not have contacts on software developers so I can not find those supporting guest-computers (again, it is NOT guest-OS!), but I could send you a list of games, which run without a problem. Some of them even with various software-protection. 4. I'm using WindowsXP, without any modification, installed with original unmodified installation CD. With this, your requirement for OS is fulfilled. Period. Your license says nothing about running LO on virtual hardware being prohibited, so I expect ED helps me to fix this problem. _________________ Just under the line: You know, what drives me mad? Not this problem, but the fact, that as with all software-protection systems, the paying customer has been once again punished for his stupidity of being paying customer. I could make LO run in VMware, and I will make it run if you do not help me to fix this problem. But I wanted to stay on legal side. But as we all know, being honest does not pay-off these days...

My problem is following: I installed LO:FC2, started some mission and wanted to activate it as usual. To my surprise, following message showed on the screen: ---------------------------- Flaming Cliffs 2 - Error An attempt to use a virtual PC is detected. Please close all PC emulators and try again. If the problem recurs, press "Error report" and send the report to product technical support. ---------------------------- Well, I can not close PC emulator, because I'm trying to run LO in emulator. I installed LO in virtual guest of VMware Workstation (guest system WindowsXP, host system is linux). But why can't I activate it? I have a legal & valid license of VMware, and I also bought 2 licenses of LO (download version, and platinum). So why can I not use one of them to run LockOn2.x in VMware-guest? I checked license.txt file in LO home folder, but I do not see anything illegal in what I am trying to do. More exactly, I did not find anything about running LockOn in virtual environment there. If it is not explicitely prohibited, it is allowed... BTW, do *not* tell me LO can not technically run in VMWare-guest, because I know it can (and I bet you know it too)! The only problem is some check-routine in that f***ing StarForce, which finds somewhere something about vmware and does not allow LO to start...

By "going ballistic" you probably mean inertial drive. Because if a missile goes really ballistics (it exhausted its engine and bleeded energy so much it can not maneuver), you do not need to worry about it anymore. Only if you accidentally fly close enough to trigger its proximity fuse... btw, under certain circumstances you can see missiles with your radar as very fast "planes". Easy with big ones (like kh58 or kh41) but you can detect 27er too if you are on its 3-9 line. I remember one mission where we succesfully defended our radar by taking 3x kh58 down with r27er...

I'm probably not the right person to announce it, but I can not resist sharing this great news: There is already DCS:BlackShark compatibility patch version 1.0.2 on DCS website! So hurry up and download, it is ~1GB: Patch 1.0.2 for "DCS: Black Shark" (English) This patch adds multiplayer compatibility between the Black Shark and Flaming Cliffs 2. As such, either game can host a multiplayer mission that both products can fly in. Several additions and a few bugfixes have also been included in this patch. (forum admin: feel free to remove this post after someone from ED writes an official announcement with ReadMe) ---------------------- Official 1.0.2 release topic http://forums.eagle.ru/showthread.php?t=54012

Hm, this looks to me too real for "entirely fictional" weapon... http://www.ausairpower.net/APA-Maritime-Flanker-D.html