I'm not sure about the significance of Visual C but what version of XP is this and what service pack and I assume it's the 32-bit version of XP?
It should run normally on 32-bit (x86) XP SP3.
Am running on Windows XP (2002) Home Edition with Service Pack 3 on a 32-bit (x86) Dell Dimension E510 desktop. The exact message reads: "Unrecognized packer or compiler." "Compiled by signature: 1024 Microsoft Visual C++ 6.0."
The exact message reads: "Unrecognized packer or compiler." "Compiled by signature: 1024 Microsoft Visual C++ 6.0."
Well, you're the only person I can find who's ever asked about those messages. Are they messages from Stinger?
You might need to check the state of your .NET installation - see
and if you need to repair your .NET installation see http://support.microsoft.com/kb/306160
1 of 1 people found this helpful
As you needed Stinger I'm assuming an infection is suspect. Any clues as to a name?
Certain infections can upset Windows File Associations. Stinger is a .exe file so you need to re-associate .exe files and there is a way here:
To fix file associations in XP run the file association fix on Doug Knox’s site http://www.dougknox.com/. Go to Win XP Fixes section, then look for File Association Fixes.
Try downloading, installing, updating and running the FREE version of THIS tool.
If the infection stops you doing that, try doing it in 'Safe Mode with Networking' reached by tapping F8 repeatedly while booting up.
That particular software will do all that in that mode.
Deleted Stinger 10.2.0.541 and downloaded 10.2.0.557 today and the problem I had disappeared. Suspect a bad download, but system does not appear to be infected. I use McAfee Stinger as a preventive security measure
monitoring tool and enjoy its security. Problem solved but root cause not id'd.
Strange, but probably simply a case of needing the latest version of Stinger. It's updated frequently, unfortunately that means you should download again it every time you need it.