Hacking Ewes ("easy" wad editing software) issue

[LeafAce]

When I try to extract everything from a WAD, it gives me an error saying that comdlg32.ocx or one of its dependencies is missing.
My computer environment is Windows 10 Professional using Surface Pro 4. I think that is all that matters unless if the path in the environment variables should be changed. The path I have is: %SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\

I looked in C:\Windows\System32 and SysWOW64 and 'comdlg32.dll' are in both of them, so I don't know the issue, but what I have been wondering is whether 'comdlg32.dll' is different or the same as 'comdlg32.ocx'?

So what should I do to get EWES working? The ReadMii that came with it didn't help.

 

[portugeek]

I had a similar problem while trying to run an unrelated software. I don't remember how I fixed it, but I do remember it being a pain. Comdlg32.dll and comdlg32.ocx are related files that perform unique operations.

.ocx files are associated with ActiveX controls, and the comdlg32 is associated with Microsoft Visual Basic.

Like I mentioned earlier, I did end up fixing my issue, although I don't remember exactly how I did it. But what I know for sure is that I didn't download a copy of the .dll file from some shady site promising to fix your problem by replacing your missing file. I feel like I updated ActiveX and MVB and then had to re-register the files.

.
.
.
.
... I just did some searching before submitting my reply to your post and found this link... https://answers.microsoft.com/en-us...s/36bb66d8-d7ba-475d-a2af-9aa4852e1c8e?auth=1

I believe this quote below was the specific reply that helped me...

Here is how to resolve comdlg32.ocx missing error.

1. Download comdlg32.ocx (I suggest using the VB file below for security reasons, use WinZip, WinRar, or 7zip to open the VB file like a Zip file rather than running as an Exe)
2. Move comdlg32.ocx (and anyothers you feel might be missing) to c:\Windows\system32 folder. For 64bit Vista/Win7, move comdlg32.ocx to c:\Windows\SysWOW64
3. Open a command line window and run following command:
   regsvr32 c:\Windows\system32\comdlg32.ocx (this will have to be done for EACH file you install)
   
   Note: a) On 64bit Vista/Win7, run this command instead:
   
   regsvr32 c:\Windows\SysWOW64\comdlg32.ocx
   
   b) For Vista/Win7 with UAC turn on, the above command needs to be run from elevated command prompt.
   
4. Once comdlg32 is registered successfully, following message will prompt, DllRegisterServer in C:\WINDOWS\System32\comdlg32.ocx succeeded.
5. Now launch the application again you should not see file missing error.

Update: Important note if you use WIN7: when registering comdlg32.ocx, it must be done as administrator, or regsvr32.exe will fail with error 0x8002801c.

To do this as administrator, Go to ‘All Programs -> Accessories -> Command Prompt’, right click on ‘Command Prompt’ icon, and click on ‘Run as administrator’ to start a command prompt, then run the regsvr32 command

Immediately afterwards, I had additional issues, all related to VB OCX files missing. So I downloaded them all from here: http://www.microsoft.com/en-us/download/details.aspx?id=10019

 

[LeafAce]

I had a similar problem while trying to run an unrelated software. I don't remember how I fixed it, but I do remember it being a pain. Comdlg32.dll and comdlg32.ocx are related files that perform unique operations.

.ocx files are associated with ActiveX controls, and the comdlg32 is associated with Microsoft Visual Basic.

Like I mentioned earlier, I did end up fixing my issue, although I don't remember exactly how I did it. But what I know for sure is that I didn't download a copy of the .dll file from some shady site promising to fix your problem by replacing your missing file. I feel like I updated ActiveX and MVB and then had to re-register the files.

.
.
.
.
... I just did some searching before submitting my reply to your post and found this link... https://answers.microsoft.com/en-us...s/36bb66d8-d7ba-475d-a2af-9aa4852e1c8e?auth=1

I believe this quote below was the specific reply that helped me...

I suppose this is safe for my windows 10?

 

[SaulFabre]

I suppose this is safe for my windows 10?

Yes this is so safe