Threaded Mode | Linear Mode

m45t3r · 03-26-2013, 01:03 AM

(03-25-2013 11:39 PM)[Unknown] Wrote: Hmm. That is strange.

Windows handles 64 bit a bit strange:
C:\Windows\system32 <-- normally holds 64 bit dlls.
C:\Windows\SysWOW64 <-- normally holds 32 bit dlls. (WOW64 actually stands for "Windows [32] on Windows 64")

Well, this much I know. Thanks Microsoft for all their legacy shit Confused

.

(03-25-2013 11:39 PM)[Unknown] Wrote: 32 bit programs that try to access system32 are automatically redirected to SysWOW64. It's possible that you've got some 32-bit dlls inside system32 somehow, which could be linking in. I would also check:

* Are these dlls anywhere on your path (if you have gnu tools installed, which.exe should answer that.)
* Are they in the directory PPSSPP is being run from?
* Are they in C:\Windows or C:\Windows\system32?

Anyway, it's possible the second one is at least being loaded for the file open dialog, maybe. It's also possible that anything could be loaded for a context menu handler or file preview, etc.

I haven't used Dependency Walker in a while, does it give you the path? If so, I would try renaming the files temporarily to "COMCTRL32.DLL.BAK" or something. If that helps, then the next step would be to either move them into SysWOW64 or find the program that's responsible for putting them in the wrong place.

-[Unknown]

A while a got I had to manually register some DLL files for a program that I was trying to run. It was MSCOMCTL.OCX, but I did put it on SysWOW64 instead System32. It still didn't work, since it seems Windows just resolved to make a backup of it (on Winsxs) without no reason. And I can't simple delete it. God, this is why I hate Windows sometimes.