Autopatcher won"t start

Requests for help go in here.
DesertJerry
Posts: 181
Joined: Sat Feb 22, 2014 7:33 pm

Re: Autopatcher won"t start

Post by DesertJerry »

Downloaded and extracted the zip then exe files as mentioned - no luck, AP still fails to start when I'm running Win7 w/SP1.

File MSVBVM60.DLL dated 25-Mar-16 was found in \System32 and \SysWOW64 folders.
User avatar
TheAPGuy
Site Admin
Site Admin
Posts: 979
Joined: Sun Oct 27, 2013 12:38 am
Location: California
Contact:

Re: Autopatcher won"t start

Post by TheAPGuy »

OK... what about the ocx finder program? Does that start up? if that does not start up you have something going on since that program only needs scrrun.dll and MSVBVM60.dll... (well and the standard OS dlls any program needs) which you have both of. If that program does not run... you can not run ANY VB6 program.
DesertJerry
Posts: 181
Joined: Sat Feb 22, 2014 7:33 pm

Re: Autopatcher won"t start

Post by DesertJerry »

OCX Finder > OCX Checker:
Looking for COMCTL32.ocx - found
Looking for MSCOMCTL.OCX - found
Looking for RICHTX32.OCX - found
Looking for COMDLG32.OCX - found
User avatar
TheAPGuy
Site Admin
Site Admin
Posts: 979
Joined: Sun Oct 27, 2013 12:38 am
Location: California
Contact:

Re: Autopatcher won"t start

Post by TheAPGuy »

ok...weird... no wait... I have two ideas I would like to try.

First... MD5 hash your scrrun.dll files.. both of them...
412381B14E5BD8ECFE7FB2F7FC63DEEA <- Syswow64
42F96527D2924A316599CC731AA7B043 <- System32 <-- you might have to copy this out of the system32 onto your desktop to avoid the hasher from getting OS directed to hash the syswow64 dir file... it happened to me.

Second is... The difference between the two applications OCX checker/finder and the startup tester is the tester uses the OCX files as well as the scrrun.dll. I will create a workaround for the scrrun.dll. <-- pain in the ass but, I already have a side project I did that in... I have got to copy paste it into here and make it work.
DesertJerry
Posts: 181
Joined: Sat Feb 22, 2014 7:33 pm

Re: Autopatcher won"t start

Post by DesertJerry »

System32 version: 7CE3200D04D76D7BC903EE6B0B78A042
SysWOW64 version: 24187EAF59E2435A2D5801A36C8BC320
Obvious differences.
User avatar
TheAPGuy
Site Admin
Site Admin
Posts: 979
Joined: Sun Oct 27, 2013 12:38 am
Location: California
Contact:

Re: Autopatcher won"t start

Post by TheAPGuy »

indeed. Will check my other OS's for differences.
User avatar
TheAPGuy
Site Admin
Site Admin
Posts: 979
Joined: Sun Oct 27, 2013 12:38 am
Location: California
Contact:

Re: Autopatcher won"t start

Post by TheAPGuy »

My windows 7x64 ultimate
system32: 8771BEDEAD950014EEDF6EEFE4A68066
Syswow64: 69A1D7C29CFF256BECBD4E39E2159636
Windows XP x64
System32: EDA7986A8D0322C22C4EFA934A8B6C0B
Syswow64: 6C520F9CDE6D391591AC344F2FE4F574

So the results are... interesting. Had no idea MS was constantly updating a VB6 only dll file. Even though they discontinued support for vb6 ages ago. Also... interesting that my win7 files are different then yours.

Attached you will find my windows 7 versions... Back up yours and give mine a try.
Also attached is a modified version of OCX finder... this one uses scrrun.dll. It "should" bomb out like the other applications that use scrrun.dll if I am right about the problem.
Attachments
OCXFinder.7z
(4.93 KiB) Downloaded 855 times
Scrrun Files.7z
(124.15 KiB) Downloaded 840 times
DesertJerry
Posts: 181
Joined: Sat Feb 22, 2014 7:33 pm

Re: Autopatcher won"t start

Post by DesertJerry »

The newer OCX Finder/Checker you provided:

Looking for COMCTL32.OCX > Found > True
Looking for MSCOMCTL.OCX > Found > True
Looking for RICHTX32.OCX > Found > True
Looking for COMDLG32.OCX > Found > True

Renamed and tried to copy the scrrun.dll to \System32 as suggested > error message: Destination Folder Access Denied - You need permission to perform this access. Try again pressed multiple times - no luck.

As I am the the Administrator and only user who gives permission to who and how? I didn't bother to try the one for SysWOW64 folder.

More info:

Win10 v1607 Build 14393.447

System32: scrrun.dll 16 Jul 16 - MD5 = 42F96527D2924A316599CC731AA7B043
SysWOW64: scrrun.dll 16 Jul 16 - MD5 = 412381B14E5BD8ECFE7FB2F7FC63DEEA

Win10 v1607 Build 14971.1000

System32: scrrun.dll 12 Nov 16 - MD5 = 4E3476E1DFFC1519D4EBCCBD4196D333
SysWOW64: scrrun.dll 12 Nov 16 - MD5 = FBECEE9505C56B540810B8B58F2843B7
User avatar
TheAPGuy
Site Admin
Site Admin
Posts: 979
Joined: Sun Oct 27, 2013 12:38 am
Location: California
Contact:

Re: Autopatcher won"t start

Post by TheAPGuy »

ahh your Win10 v1607 Build 14393.447 matches mine above.
huh... your right... I tried to overwrite mine with a win10 version and it did not take. It would not even take in safe mode.

Also VERY strange that OCX finder worked for you. hmm.... so odd... very odd.
User avatar
TheAPGuy
Site Admin
Site Admin
Posts: 979
Joined: Sun Oct 27, 2013 12:38 am
Location: California
Contact:

Re: Autopatcher won"t start

Post by TheAPGuy »

ok DJ I have been doing a lot of digging around and this pops up a lot. InitCommonControlsEx issues causing the application to quit before it fully starts with 0 as an error return. That function (which is needed for default VB functionality in the GUI departmen) can cause this if its not run (which I do) or if its incorrectly done. That function links into ComCtl32.dll and and sets up the GUI properties of the form to work. Generally this automatically done by the application without programmer needing to call it... it does not usually matter in this case. Startup tester worked fine without needing to call it (but not for you...). This version WILL call it as well as use a built in manifest to call for the vb common controls.. We shall see if this makes a difference.
Attachments
StartupWManifest.7z
(17.28 KiB) Downloaded 839 times
Post Reply