You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The patcher could not auto-find the activeX flash ocx files on my system because I installed latest version 465 and Patches.cs only knows 445. So I proceeded to manually select the files using the classic explorer file open dialog. However I could not access the 64bit one because both System32 and SysWoW64 led to the same 32bit macromedia folder. I assume this dialog needs wow64 redirection turned off. (As a workaround, I temporarily moved the file to a more convenient location for patching.)
The text was updated successfully, but these errors were encountered:
No noticeable difference, it still runs as a 32-bit windows executable. But now that the latest activex version is auto detected, this is no longer a big issue.
It is too bad that the behavior cannot be changed for the dialog. One additional workaround I found is that the dialog supports the 'SysNative' pseudo folder name.
The patcher could not auto-find the activeX flash ocx files on my system because I installed latest version 465 and Patches.cs only knows 445. So I proceeded to manually select the files using the classic explorer file open dialog. However I could not access the 64bit one because both System32 and SysWoW64 led to the same 32bit macromedia folder. I assume this dialog needs wow64 redirection turned off. (As a workaround, I temporarily moved the file to a more convenient location for patching.)
The text was updated successfully, but these errors were encountered: