Device Manager doesn't work

Since installing FlyakiteOSX I have had numerous dll problems. Most are easily fixed by copying the dll from one computer to the other (I have two PCs available to me).

However, I have a problem with Device Manager that I can't seem to figure out. If I try to open Device Manager through the System Properties screen, I receive the following error message:

"System Control Panel Applet

Unable to load the Device manager program file, devmgr.dll"

When I tried to copy a working version from my other computer to this one, I received an error message:

"Error Copying File or Folder

Cannot copy devmgr: Data error (cyclic redundancy check)"

Any ideas?????

Thanks for your help.

I really like the look and feel of FlyakiteOSX and I would hate to have to go back to POW (Plain Old Windows).

#383164

Hmm, I'm not sure if it's the greatest idea to simply copy the dll from one computer to another...

However, if you want to go ahead, try using Task Manager to shut down explorer.exe. Then go to

File-->New Task-->Browse, locate devmgr.dll, and use the right-click context menu to Copy it to your preferred destination.

Hope this helps,

-NC

#383326

Thanks nightcrawler, that let me copy the devmgr.dll file where it needs to be, but I still get the error when I try to open Device Manager, it keeps saying that it cannot load the file. I say it is where it needs to be (c:windowssystem32) because that is where the file resides on my other XP computer...

I noticed that FOSX makes a 1K text file named devmgr.dll in it's Logs folder and that there is a file folder by the same name under windowsflyakiteosxresources and that another version of the text file devmgr.dll (also 1K) is located there. I say that it is a different version because the file dates are different.

Any thoughts as to how to resolve this.

#383459

Well, thank all the digital gods for back-ups with system state. After restoring my system state from about a month ago, I have everything--including FlyakiteOSX--working beautifully.

I have no idea how this got started, but the moral of the story is always do back-ups with system state.

:-)

#383852

Glad to see it got resolved, even if we're still clueless as to how to fix it properly .

-NC

#383909