Sign up Calendar Latest Topics
 
 
 


Reply
  Author   Comment  
BzDan

Avatar / Picture

Registered:
Posts: 9
Reply with quote  #1 
Hello,
I upgraded yesterday to Artemis 2.4.0 and a window pops up now when I start it up and it's loading the .dxs files with the message: "C:\Windows\system32\HID.dll is either not designed to run on Windows or it contains an error". It did not happen before, only after I upgraded it.

If I click the OK button on the message window, the Artemis launch screen comes up immediately, without seeing any other .dxs files being loaded. Then the game seems to run OK.

I get this message when trying to run Artemis 2.4.0 stock, extended or TNG mod. I run it on a PC, Win 7 64Bit, 3 monitors on 2 video cards. Thus, I run simultaneous 3 instances of Artemis and the message pops up when I start each one of them.

Anyone had this problem before? Any suggestions?
Thanks,
Dan
LawsonThompson

Registered:
Posts: 587
Reply with quote  #2 
Got good news and bad news for you.

The bad news: C:\Windows\System32\HID.dll is not an Artemis file (Artemis doesn't touch the Windows or System32 folders during install.) That's part of Windows' own code for handling USB devices.

The good news (maybe): Should be fixable via Windows System File Checker. See https://support.microsoft.com/en-us/kb/929833 for details.


__________________
----
Visit us at http://www.ltebridge.com
BzDan

Avatar / Picture

Registered:
Posts: 9
Reply with quote  #3 
Hello,
Thank you for your prompt reply and information.
You probably are right as I tried same version of Artemis on another computer running Win 7 64bit and didn't get the message anymore (actually it's not a second computer, it's another hard drive with its own Win 7 64bit from which I can boot and on which I also have Artemis).

Also, my Logitech Wingman 3D Force joystick became active on the 2nd "computer", although it was useless because it was too sensitive and unstable (even after calibration) and it was controlling simultaneously both the ship and the fighter, although I was in the fighter. Probably something wrong with this old joystick for which I cannot find  a Logitech Win 7 64bit driver anymore, it uses whatever Windows has.

I tried the System File Checker (thanks for information) but it didn't work. But the log shows the hid.dll file is corrupted and it cannot repair it.  I cannot restore it to a previous restore point because I couldn't find one although the system creates one every time it is updated. Thus, I do not know what to do anymore. Anything else seems to work OK. Checked for viruses and found none. Probably something got corrupted somehow. Don't know how to repair the system and do not want to reinstall it, have to much stuff on it including engineering software. Probably I have to live with it.

Something else I noticed when playing the extended Artemis 2.4.0 and the TNG mod. After connecting the clients (2 monitors in addition to the server monitor, thus 3 monitors on one computer), the cursors becomes practically invisible (just 1 or 2 pixels) on the client monitors. The same happens on the 2nd "computer" I tried. Has anyone else encountered this problem? Any solution to it? I couldn't find anywhere being mentioned.

Sorry for the long message and thank you again for your prompt reply and info.
Dan


User McUser

Registered:
Posts: 118
Reply with quote  #4 
Quote:
Originally Posted by BzDan
I tried the System File Checker (thanks for information) but it didn't work. But the log shows the hid.dll file is corrupted and it cannot repair it.  I cannot restore it to a previous restore point because I couldn't find one although the system creates one every time it is updated. Thus, I do not know what to do anymore.


Copy the hid.dll file from a computer where you don't get that error to the one where you do and then reboot (make a backup copy of the original "Just-In-Case.") You might need to boot the "bad" computer into Safe Mode to do this.
BzDan

Avatar / Picture

Registered:
Posts: 9
Reply with quote  #5 
Thank you for suggestion. I tried this and it didn't work. Actually I did this before I posted the first message but forgot to mention it, sorry. Of course, I had to reset all kind of permissions, but I managed to get access to the files in System32 folder, although it was a pain...

Dan
User McUser

Registered:
Posts: 118
Reply with quote  #6 
Quote:
Originally Posted by BzDan
Thank you for suggestion. I tried this and it didn't work. Actually I did this before I posted the first message but forgot to mention it, sorry. Of course, I had to reset all kind of permissions, but I managed to get access to the files in System32 folder, although it was a pain...

Dan


There may be something on your computer (anti-virus software, actual virus, or windows' own integrity control software) that is silently undoing your change after you copy the DLL over. Compare the file size and file version on the "bad" and working computers to make sure they're identical.

If you can manage to get the hard drive from the "bad" PC into a working PC - either by use of a USB adapter or by connecting the drive internally - try replacing the file again anyways with a known-good copy. You could also boot from a WinPE or Linux "Live" CD or USB drive and access the drive that way.

It is also possible that you might also have a bad USB controller or device. Try moving all your USB HID (Human-Interface Devices; eg: keyboards, mice, joysticks, touch-screens, etc) to different USB ports, if you have enough unused ones, or to another computer to see if the problem follows a device.
BzDan

Avatar / Picture

Registered:
Posts: 9
Reply with quote  #7 
Thank you for your suggestions, I'll try them.
Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Easily create a Forum Website with Website Toolbox.