46 replies to this topic

[Genore]

Windows 7 Ultimate SP1 32-bit (US English) fully updated, apup.exe 1.4.0.5 (download updated from the ZIP version 1.4.0.0) & autopatcher.exe 5.7.0.5 (downloaded).

Both the earlier & current versions of apup work without issues. Can download everything I select: currently "APUP 1.4.5", "Autopatcher Engine 5.7.5", "AutoPatcher Common Modules" & "AutoPatcher for Windows 7 SP1 (x86)". The MD5 checks go smoothly. Can exit without issues and the apup.log shows no errors.

However, doubleclick autopatcher.exe and it crashes. The Windows "crash box" (with error details) appears. Close it and it appears a second time. Close the second box and it doesn't reappear until I doubleclick autopatcher.exe again.

Here is the autopatcher.log file out of C:\Windows (it remains with the same data after every crash):

Spoiler

AutoPatcher 5.6 loaded the filesystem.

Analysing obtained commandline arguments...

Obtaining list of all supported by Autopatcher and installed on this machine programs...
Detected
English (1033) Windows 7 Ultimate 32-bit
System Components:
Internet Explorer: 9.0.8112.16457
Windows Media Player: 12.0.7601.17514
.NET Framework: 2.0.50727.5420|2.0SP2|3.0.30729.5420.5420|3.0SP2|3.5|3.5SP1
Windows Installer: 5.0.7601.17514
DirectX: 4.09.00.0904
MSN/Live Messenger:

Office Components:
Microsoft Word:
Microsoft Excel:
Microsoft PowerPoint:
Microsoft Outlook:
Microsoft Access:
Microsoft Project:
Microsoft Publisher:
Microsoft OneNote:
Microsoft FrontPage:
Microsoft InfoPath:
Microsoft Visio:
Microsoft SharePoint Designer:
Microsoft Groove:

Checking existing of all needed spec.files like aamd532.dll, COMCTL32.OCX etc...
Checking file: C:\apup\bin\aamd532.dll
Checking file: C:\apup\bin\COMCTL32.OCX
Checking file: C:\apup\bin\MSCOMCTL.OCX
Checking file: C:\apup\bin\COMDLG32.OCX
Checking file: C:\apup\bin\FM20.DLL
Checking file: C:\apup\bin\FM20ENU.DLL
Checking file: C:\apup\bin\REBOOT.EXE
Checking file: C:\apup\bin\RICHTX32.OCX
Checking file: C:\apup\bin\SSUBTMR6.DLL
Now all is done - we can start Main-form loading procudere.

Here is the Windows error data:

Spoiler

Fault bucket , type 0
Event Name: BEX
Response: Not available
Cab Id: 0

Problem signature:
P1: autopatcher.exe
P2: 5.7.0.5
P3: 51030cb4
P4: StackHash_81b7
P5: 0.0.0.0
P6: 00000000
P7: 030626d0
P8: c0000005
P9: 00000008
P10:

I've tried unregistering and reregistering all the VB6 files this thing uses (with regsvr32) in both the above folders and \Windows\System (that for some reason the program decides to arbitrarily insert) to no success. I've tried updating starting from scratch not downloading anything except Autopatcher.exe with no success. And I've tried using a circa-2010 autopatcher.exe I had backed up (version 5.6.0.100) to no success (same error & log messages).

The last item above points to not having all the VB6 files this thing needs on my system (but as mentioned, all the VB6 files that are downloaded are registered properly). Why do I say this? Because besides the above, autopatcher.exe (an older version than 5.7.0.5) always worked without issues a few weeks ago & prior when I still had MS Office 2010 installed on this system.

I hve since totally uninstalled Office 2010 (as seen in the autopatcher.log file). After doing so, autopatcher.exe has always crashed before starting. Which likely means AutoPatcher's reliance on the outdated VB6 language & files are missing a few files the program actually needs and doesn't include.

Its always been a great program in the past here up until this crashing started. So hopefully there is some way I can get autopatcher.exe to work properly, if you have any suggestions.

Edited by Whatacrock, 12 February 2013 - 03:56 AM.

[ViroMan]

The latest autopatcher creates log files in apup folder instead of the windows folder(which is why you log looks like the older log file type). Can you see if you have one there to look at?

I believe I put in more debug code for the latest AP(5.7.5) so if you run it in a batch file as "autopatcher.exe /verbose" without quotes. It should log errors directly to the log file if it can.

Also... for the error information you provided, is that the Standard windows error report or is that the AutoPatcher error report? It doesn't look like the one autopatcher generates in its error window. The one that autopatcher generates would be far more useful as it would tell me exactly where to look.

also... you said it tries to install the files into windows/system? It should be trying to put them into windows/system32. hmmm

Edited by ViroMan, 11 February 2013 - 08:22 AM.

[Genore]

Thanks very much for the reply.

 ViroMan, on 11 February 2013 - 08:20 AM, said:

The latest autopatcher creates log files in apup folder instead of the windows folder(which is why you log looks like the older log file type). Can you see if you have one there to look at?

Actually, 5.7.0.5 doesn't create a log in \apup. The only log file created there is apup.log, which has no information relating to autopatcher.exe. The only location for autopatcher.log is as mentioned: in \Windows. The modified date gets updated after every crash.

 ViroMan, on 11 February 2013 - 08:20 AM, said:

I believe I put in more debug code for the latest AP(5.7.5) so if you run it in a batch file as "autopatcher.exe /verbose" without quotes. It should log errors directly to the log file if it can.

I actually tried that prior. Running it as either autopatcher.exe /verbose, autopatcher.exe /log or autopatcher.exe /log /verbose, it also crashes, but the autopatcher.log created in \Windows is 100% identical to what's created when doubleclicking the EXE (I gave you in the last post), which is why I didn't report it here.

Running it from the command line with "/?" (autopatcher.exe /?), it actually pops up a command help frame without errors (much like Windows script programs do, but unexpected in a command program).

 ViroMan, on 11 February 2013 - 08:20 AM, said:

Also... for the error information you provided, is that the Standard windows error report or is that the AutoPatcher error report? It doesn't look like the one autopatcher generates in its error window. The one that autopatcher generates would be far more useful as it would tell me exactly where to look.

Autopatcher never launches, it crashes before it can provide its own error window. The second report is straight out of the Windows error window, the first one is out of autopatcher.log. Further info not shown in the Windows report window text above, but recorded in WER files generated by the crashes (I have group policy set to record them; I read them with Nirsoft's "AppCrashView" program):

Spoiler

Version=1
EventType=BEX
EventTime=130050500946785880
ReportType=2
Consent=1
ReportIdentifier=156e7bb8-7431-11e2-9e84-001b217ad55f
IntegratorReportIdentifier=156e7bb7-7431-11e2-9e84-001b217ad55f
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=autopatcher.exe
Sig[1].Name=Application Version
Sig[1].Value=5.7.0.5
Sig[2].Name=Application Timestamp
Sig[2].Value=51030cb4
Sig[3].Name=Fault Module Name
Sig[3].Value=StackHash_be65
Sig[4].Name=Fault Module Version
Sig[4].Value=0.0.0.0
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=00000000
Sig[6].Name=Exception Offset
Sig[6].Value=032e6cc8
Sig[7].Name=Exception Code
Sig[7].Value=c0000005
Sig[8].Name=Exception Data
Sig[8].Value=00000008
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.256.4
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=be65
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=be6568e3cf0d2efb174bc6c79afc3095
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=c499
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=c49981a9c95397c25bb9f5f024999e6b
UI[2]=C:\apup\autopatcher.exe
UI[3]=AutoPatcher main module has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=C:\apup\autopatcher.exe
LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\Windows\system32\kernel32.dll
LoadedModule[3]=C:\Windows\system32\KERNELBASE.dll
LoadedModule[4]=C:\Windows\system32\MSVBVM60.DLL
LoadedModule[5]=C:\Windows\system32\USER32.dll
LoadedModule[6]=C:\Windows\system32\GDI32.dll
LoadedModule[7]=C:\Windows\system32\LPK.dll
LoadedModule[8]=C:\Windows\system32\USP10.dll
LoadedModule[9]=C:\Windows\system32\msvcrt.dll
LoadedModule[10]=C:\Windows\system32\ADVAPI32.dll
LoadedModule[11]=C:\Windows\SYSTEM32\sechost.dll
LoadedModule[12]=C:\Windows\system32\RPCRT4.dll
LoadedModule[13]=C:\Windows\system32\ole32.dll
LoadedModule[14]=C:\Windows\system32\OLEAUT32.dll
LoadedModule[15]=C:\Windows\system32\apphelp.dll
LoadedModule[16]=C:\Windows\AppPatch\AcLayers.dll
LoadedModule[17]=C:\Windows\system32\SspiCli.dll
LoadedModule[18]=C:\Windows\system32\SHELL32.dll
LoadedModule[19]=C:\Windows\system32\SHLWAPI.dll
LoadedModule[20]=C:\Windows\system32\USERENV.dll
LoadedModule[21]=C:\Windows\system32\profapi.dll
LoadedModule[22]=C:\Windows\system32\WINSPOOL.DRV
LoadedModule[23]=C:\Windows\system32\MPR.dll
LoadedModule[24]=C:\Windows\AppPatch\AcGenral.DLL
LoadedModule[25]=C:\Windows\system32\UxTheme.dll
LoadedModule[26]=C:\Windows\system32\WINMM.dll
LoadedModule[27]=C:\Windows\system32\samcli.dll
LoadedModule[28]=C:\Windows\system32\MSACM32.dll
LoadedModule[29]=C:\Windows\system32\VERSION.dll
LoadedModule[30]=C:\Windows\system32\sfc.dll
LoadedModule[31]=C:\Windows\system32\sfc_os.DLL
LoadedModule[32]=C:\Windows\system32\dwmapi.dll
LoadedModule[33]=C:\Windows\system32\SETUPAPI.dll
LoadedModule[34]=C:\Windows\system32\CFGMGR32.dll
LoadedModule[35]=C:\Windows\system32\DEVOBJ.dll
LoadedModule[36]=C:\Windows\system32\urlmon.dll
LoadedModule[37]=C:\Windows\system32\iertutil.dll
LoadedModule[38]=C:\Windows\system32\WININET.dll
LoadedModule[39]=C:\Windows\system32\Normaliz.dll
LoadedModule[40]=C:\Windows\AppPatch\AcXtrnal.DLL
LoadedModule[41]=C:\Windows\system32\SHUNIMPL.DLL
LoadedModule[42]=C:\Windows\system32\SortServer2003Compat.dll
LoadedModule[43]=C:\Windows\system32\IMM32.DLL
LoadedModule[44]=C:\Windows\system32\MSCTF.dll
LoadedModule[45]=C:\Windows\system32\CRYPTBASE.dll
LoadedModule[46]=C:\Windows\system32\SXS.DLL
LoadedModule[47]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.17514_none_ec83dffa859149af\comctl32.dll
LoadedModule[48]=C:\Windows\system32\CLBCatQ.DLL
LoadedModule[49]=C:\Windows\system32\scrrun.dll
LoadedModule[50]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[51]=C:\Windows\system32\rsaenh.dll
LoadedModule[52]=C:\Windows\System32\FM20.DLL
LoadedModule[53]=C:\Windows\system32\RICHED20.DLL
LoadedModule[54]=C:\Windows\System32\fm20ENU.DLL
LoadedModule[55]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[56]=C:\Windows\System32\Mscomctl.ocx
LoadedModule[57]=C:\Windows\system32\comdlg32.dll
LoadedModule[58]=C:\Windows\System32\COMCTL32.OCX
LoadedModule[59]=C:\Windows\System32\COMDLG32.OCX
LoadedModule[60]=C:\Windows\system32\asycfilt.dll
LoadedModule[61]=C:\Windows\System32\RICHTX32.OCX
LoadedModule[62]=C:\Windows\System32\oledlg.dll
LoadedModule[63]=C:\Windows\system32\RichEd32.DLL
LoadedModule[64]=C:\Windows\system32\SSUBTMR6.DLL
FriendlyEventName=Stopped working
ConsentKey=BEX
AppName=AutoPatcher main module
AppPath=C:\apup\autopatcher.exe

And finally, the text out of Event Viewer (Windows Logs, Application Error):

Spoiler

Faulting application name: autopatcher.exe, version: 5.7.0.5, time stamp: 0x51030cb4
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x032e6cc8
Faulting process id: 0xa68
Faulting application start time: 0x01ce083dd6b293f7
Faulting application path: C:\apup\autopatcher.exe
Faulting module path: unknown
Report Id: 156e7bb7-7431-11e2-9e84-001b217ad55f

 ViroMan, on 11 February 2013 - 08:20 AM, said:

also... you said it tries to install the files into windows/system? It should be trying to put them into windows/system32. hmmm

Sorry, yes, I meant \Windows\System32. The program itself (excluding the MS updates, of course) really shouldn't be putting any files anywhere but its own folders, though .

Edited by Whatacrock, 12 February 2013 - 03:57 AM.

[_def_x_]

My friend reported to me a few days ago AP 5.7 crashes on his system too - XP Pro x86 SP3. So my crash I thought might be due to the SP level, 2, not 3, for XP Pro x86 may not be the issue?

The common? phrase popping up is main form or main module, seen above as main module, on my system and my friends it's main form. On both XP systems we were given the YIKES! dialog.

I tested /?, I can get the Help dialog but not AP on XP SP2.

On my XP SP3 VM where AP 5.7 starts up without a hitch I too have no log file. I tried nothing, /verbose, /log - no log file. I asked my friend as well, no log file created regardless of the switch used.

[Genore]

Hi, yep, I never receive that autopatcher "Yikes!" error frame or anything else from the program in Windows 7 SP1 32 bit. It always crashes before anything visual happens and the Windows error frame appear instead (with the as-noted exception of running the autopatcher.exe /? command).

I do, however, always receive an updated autopatcher.log file in C:\Windows after every crash with text as noted in my first post ("AutoPatcher 5.6 loaded the filesystem..." and so on). That autopatcher.log text is always the same after every crash here; the log file's modified time is the only thing that changes.

I can't edit my second post above, but wanted to clarify a statement I made in it that's bit unclear:

Quote

The second report is straight out of the Windows error window, the first one is out of autopatcher.log.

By "second report is straight out of the Windows error window", I meant the "Fault bucket , type 0 Event Name: BEX..." text in the first post. By "the first one is out of autopatcher.log", I meant the "AutoPatcher 5.6 loaded the filesystem. Analysing obtained commandline arguments..." text in the first post.

Finally, since this is getting too long to follow , the single system change done here that is aligned with autopatcher.exe continually crashing: totally uninstalling MS Office 2010. When that was installed, autopatcher.exe always worked fine. Now, it always crashes. I can't reinstall it because I transferred the license to a family member's new laptop.

Edited by Genore, 11 February 2013 - 05:26 PM.

[ViroMan]

Strange indeed. Well AP is set to create the log in the directory its run from but, if it can't create it there it defaults to the windows dir.

thankx def_x for the screenshot, that should help find the problem.

I will look into some things and I may post up a test version here for you to try shortly.

edit:
So I was wrong about the extra code I thought I put in for the /verbose giving more debug code. It must have been that version of the code that I somehow misplaced(or didn't save) a while ago. I am adding that now.

Edited by ViroMan, 11 February 2013 - 10:22 PM.

[ViroMan]

Ok so, I may have fixed the problem as well as adding some of the /verbose code back in.
AP version is 5.7.14(I was already adding more things before this so that is why the revision is so high)

edit: woops there was a minor error in that one.
here is 5.7.15

Attached Files

•  autopatcher.zip   171.47K   33 downloads

Edited by ViroMan, 11 February 2013 - 10:55 PM.

[DesertJerry]

I have XP Pro w/SP3, XP Pro x64 w/SP2, Win7 Ultimate 32bit w/SP1, and Win7 Ultimate 64bit w/SP1 installed in separate partitions. AutoPatcher itself is installed in a partition separate from the ones holding the operating system but common to all four when invoked from any of the OS's.
I just checked and I have one each APUP.LOG file in the one \AutoPatcher folder and four each AUTOPATCHER.LOG files; one each in each of the \Windows folders.
Odd - the APUP.Log is the same when I change Options from releases.list to releases2.list - it always says releases.list; tried three times to see a change - did not happen.
I did double-click AUTOPATCHER.EXE (located in the \AutoPatcher folder) and it started just fine - no error message. (WIn7 Ultimate 64bit w/SP1) No difference in response when shortcut is clicked.

[ViroMan]

DesertJerry, on 11 February 2013 - 10:37 PM, said:

it always says releases.list; tried three times to see a change - did not happen.

ya it was a generic message from the original code, it is on my todo list and I haven't gotten around to it yet.

I am running it on both XP SP3 and Win7 Ult x64 and it has always run just fine for me. So I am not 100% sure I fixed it but, I am 80% sure I did. Even if I didn't fix it, the extra debug code should point me directly to the line if it is run it with /verbose switch.

[_def_x_]

ViroMan, on 11 February 2013 - 11:01 PM, said:

I am running it on both XP SP3 and Win7 Ult x64 and it has always run just fine for me.

Technically it works for me too, my XP SP3 VM is my original SP2 disc slipstreamed with SP3. Once I can afford to build the system I want I will install Seven, but for now I will stick with SP2 for my main system, a few pieces of software I need crash with SP3.

ViroMan, on 11 February 2013 - 11:01 PM, said:

So I am not 100% sure I fixed it but, I am 80% sure I did. Even if I didn't fix it, the extra debug code should point me directly to the line if it is run it with /verbose switch.

I'll try now and see...?

[_def_x_]

Not much to report, AP's main form is still not starting. When AP is run without a switch I get the following error dialog, essentially the same message without the YIKES - see attached.

When using /log or /verbose the YIKES dialog appears with the same message I posted above - see attachment.

I do get a log file in \apup, here's the output of /verbose.

Spoiler

Attempting to initialize common controls.
Checking CPU.
Accessing Registry To Find Windows Directorys...
List Of Detected Directories:
Windows - - - - - I:\WINDOWS
Windows\System - - I:\WINDOWS\system32
Windows\System32 - I:\WINDOWS\system32
Program Files(x86) I:\Program Files
CommonFiles - - - I:\Program Files\Common Files

AutoPatcher v5.7.15 Loaded The Filesystem.

Parsing Detected Commandline Arguments...

Obtaining list of all supported by Autopatcher and installed on this machine...
Detected
English (1033) Windows XP Professional Service Pack 2

System Components:
Internet Explorer: 6.0.2900.3698
Windows Media Player: 9.0.0.3250
.NET Framework: 1.1.4322|1.1SP1|2.0.50727.3053|2.0SP2|3.2.30729.01|3.2SP2|3.5|3.5SP1
Windows Installer: 4.5.6001.22159
DirectX: 4.09.00.0904
MSN/Live Messenger:

Office Components:
** NONE **

Checking existance of all needed files like aamd532.dll, COMCTL32.OCX etc...
Checking file: C:\apup2\bin\aamd532.dll
Checking file: C:\apup2\bin\COMCTL32.OCX
Checking file: C:\apup2\bin\MSCOMCTL.OCX
Checking file: C:\apup2\bin\COMDLG32.OCX
Checking file: C:\apup2\bin\FM20.DLL
Checking file: C:\apup2\bin\FM20ENU.DLL
Checking file: C:\apup2\bin\REBOOT.EXE
Checking file: C:\apup2\bin\RICHTX32.OCX
Checking file: C:\apup2\bin\SSUBTMR6.DLL
Prepwork Done Bring Up Main Form...

I wonder if Dependency Walker would offer any ideas...?

[ViroMan]

... it crashes the moment the main window is told to show? huh.

The fact that it doesn't show the error in the log file tells me it might be happening beyond where I thought it was happening.

When I look up 430 errcodes it tells me that the dll files should be re-registered. huh. I am adding tons of debug code atm.

Edited by ViroMan, 12 February 2013 - 01:11 AM.

[_def_x_]

ViroMan, on 12 February 2013 - 12:23 AM, said:

... it crashes the moment the main window is told to show? huh.

I don't think crash (for my circumstance) is the best description, the main form or AutoPatcher never starts up, there's a pause when the executable is clicked and then the YIKES! dialog, or the standard dialog as seen from post #11.

NOTE: I just stumbled across something, when I click the quit button on any of the error messages, AP quits, BUT - if I click the red X, AutoPatcher starts up. Let me test the other exe see what I find...

[_def_x_]

Very strange, OK, this is what I'm getting...

... AP 5.7.0.5
As long as I click the RED X in the error dialog and not click QUIT - AP 5.7.0.5 will start up.

... AP 5.7.0.15
The error dialog I mentioned in post #11, which I get when AP runs without a switch, no matter what I do, click OK or RED X - AP 5.7.0.15 wont start, you simply exit the error dialog - BUT...

If I run AP 5.7.0.15 with /log, /verbose, which gives me the YIKES! and I click the RED X and not QUIT - AP 5.7.0.15 will start up.

[ViroMan]

wtf? Please examine the AP window thoroughly when you get it to show up and try everything out to see if it works normally after you get the error to go away.

ohh ya, the reason the you can resume after the error is that all the error calls have a resume call after each call to the crash handler. Presumably its a hidden secret that allowed them(testers) to keep checking for errors after the initial error popped up.

Edited by ViroMan, 12 February 2013 - 01:42 AM.

[_def_x_]

ViroMan, on 12 February 2013 - 01:12 AM, said:

wtf? Please examine the AP window thoroughly when you get it to show up and try everything out to see if it works normally after you get the error to go away.

Will do. I dropped the 2 manifest files and the nice buttons are drawn the way I like, instead of the ugly square things.

I'll move \apup over to my VM and install the latest Flash along with 2 or 3 of the C++ redists using 5.7.0.15, I'll report any issues.

Oh, and @Genore, if you read this, the thread is really long now...

See what happens when you click the RED X if given the opportunity, don't click QUIT, EXIT, CLOSE - just the RED X if there's one in the upper right corner of any pop-up, see what happens. You might need to run autopatcher.exe /log or /verbose...???

@ViroMan
Interesting about resume after error, might the error be more like a warning (about what I don't know) in my case, seeing the app actually appears to run fine. I did notice in Dependency Walker there were a couple of warnings about something missing, not sure if it was about my system or autopatcher.exe - let me see if I can reproduce it...

OK, these 2 warnings are written to the Dependency Walker log once autopatcher.exe loads, can't see any system files in RED, not sure.

Warning: At least one delay-load dependency module was not found.

Warning: At least one module has an unresolved import due to a missing export function in a delay-load dependent module.

Once I hit profile to run the exe the only additional warning is this???

GetProcAddress(0x7C800000 [i:\windows\system32\KERNEL32.DLL], "IsTNT") called from "i:\windows\system32\MSVBVM60.DLL" at address 0x73421BD1 and returned NULL by thread 1. Error: The specified procedure could not be found (127).

OK, last post to keep the confusion level down. After profiling autopatcher.exe, I did get these additional warnings about my system, does it apply to AP, not sure.

...MSJAVA.DLL - Error opening file. The system cannot find the specified file(2).
...MFC42LOC.DLL - Error opening file. The system cannot find the specified file(2).
...USER.EXE - No PE signature found. The file appears to be a 16-bit Windows module.

Edited by _def_x_, 12 February 2013 - 02:11 AM.

[ViroMan]

ohh I totally forgot about those. I looked around and found a way to generate proper manifests and include them into the exe's

Quote

Once I hit profile to run the exe the only additional warning is this???

Their FAQ http://www.dependenc...er.com/faq.html shows this...

Q: Why are some modules looking for a function named "IsTNT" in KERNEL32.DLL?
A: TNT is a 32-bit emulation layer written by Phar Lap. There are still some modules in use that have pieces of code that check to see if they are running on TNT by calling GetProcAddress("IsTNT") for KERNEL32.DLL. This warning can be ignored.

http://groups.google...nh0.news.uu.net
Says that TNT is a Win32 emulator for DOS. VB6 is pretty damn old.

I duno if the above affects anything really.

anyways... as I said above "When I look up 430 errcodes it tells me that the DLL files should be re-registered." but, you said you already tried that...I know that the way they set AP up it always tries to register

Edited by ViroMan, 12 February 2013 - 02:58 AM.

[ViroMan]

So... here is another version to test. <-- pretty manifest file built in so you "shouldn't" need that file anymore.

Attached Files

•  autopatcher.zip   172.94K   15 downloads

[Genore]

I seriously wouldn't try integrating MSJAVA.DLL into the EXE. Another quote from that Dependency Walker page:

Quote

The MSHTML.DLL module that was released with Windows XP SP2 and Windows 2003 SP1 has a delay-load dependency on MSJAVA.DLL. Missing delay-load dependencies are not a problem as long as the calling DLL is prepared to handle the missing module.

MSJAVA.DLL is long (long) obsolete, a potential security risk and so on.

 _def_x_, on 12 February 2013 - 12:18 AM, said:

See what happens when you click the RED X if given the opportunity, don't click QUIT, EXIT, CLOSE - just the RED X if there's one in the upper right corner of any pop-up, see what happens. You might need to run autopatcher.exe /log or /verbose...???

No opportunity is given. Windows 7 handles errors completely differently than XP (which I used to use up until recently).

The only UI I'm given--including now with the new AutoPatcher v5.7.15--is the same Windows error-close box I have always recieved since uninstalling Office 2010 (and I've now included in a screenshot). Whether clicking "Close the program" or the grey X in the upper right, the same results happen: the same UI box appears a second time, after which nothing further happens (either clicking "Close..." or the "X" again).

One change: autopatcher.log now appears in \Apup instead of \Windows. Running Autopatcher.exe /verbose, its similar to what I've posted before (and what _def_x_ posted above). It crashes after Prepwork Done Bring Up Main Form...:

Spoiler

Attempting to initialize common controls.
Checking CPU.
Accessing Registry To Find Windows Directorys...
List Of Detected Directories:
Windows - - - - - C:\Windows
Windows\System - - C:\Windows\System32
Windows\System32 - C:\Windows\System32
Program Files(x86) C:\Program Files
CommonFiles - - - C:\Program Files\Common Files

AutoPatcher v5.7.15 Loaded The Filesystem.

Parsing Detected Commandline Arguments...

Obtaining list of all supported by Autopatcher and installed on this machine...
Detected
English (1033) Windows 7 Ultimate 32-bit

System Components:
Internet Explorer: 9.0.8112.16457
Windows Media Player: 12.0.7601.17514
.NET Framework: 2.0.50727.5420|2.0SP2|3.0.30729.5420.5420|3.0SP2|3.5|3.5SP1
Windows Installer: 5.0.7601.17514
DirectX: 4.09.00.0904
MSN/Live Messenger:

Office Components:
** NONE **

Checking existance of all needed files like aamd532.dll, COMCTL32.OCX etc...
Checking file: C:\apup\bin\aamd532.dll
Checking file: C:\apup\bin\COMCTL32.OCX
Checking file: C:\apup\bin\MSCOMCTL.OCX
Checking file: C:\apup\bin\COMDLG32.OCX
Checking file: C:\apup\bin\FM20.DLL
Checking file: C:\apup\bin\FM20ENU.DLL
Checking file: C:\apup\bin\REBOOT.EXE
Checking file: C:\apup\bin\RICHTX32.OCX
Checking file: C:\apup\bin\SSUBTMR6.DLL
Prepwork Done Bring Up Main Form...

Next, running DependencyWalker 2.2.6000 here...

Profiled autopatcher.exe and the single red line in the profile (before autopatcher crashed) was slightly different from what _def_x_ posted:
GetProcAddress(0x76AA0000 [KERNEL32.DLL], "IsTNT") called from "MSVBVM60.DLL" at address 0x72941BE1 and returned NULL. Error: The specified procedure could not be found (127).

Prior to the profile:
Warning: At least one delay-load dependency module was not found.
Warning: At least one module has an unresolved import due to a missing export function in a delay-load dependent module.
The single missing file here is IESHIMS.DLL.

Attached Files

•  Clipboard01b.jpg   23.45K   13 downloads

Edited by Whatacrock, 12 February 2013 - 03:53 AM.

[Genore]

Sorry, I posted the above before you uploaded the autopatcher.exe v5.7.18. Nothing changes running it; the log is pretty much identical:

Spoiler

Attempting to initialize common controls.
Checking CPU.
Accessing Registry To Find Windows Directorys...
List Of Detected Directories:
Windows - - - - - C:\Windows
Windows\System - - C:\Windows\System32
Windows\System32 - C:\Windows\System32
Program Files(x86) C:\Program Files
CommonFiles - - - C:\Program Files\Common Files

AutoPatcher v5.7.18 Loaded The Filesystem.

Parsing Detected Commandline Arguments...

Obtaining list of all supported by Autopatcher and installed on this machine...
Detected
English (1033) Windows 7 Ultimate 32-bit

System Components:
Internet Explorer: 9.0.8112.16457
Windows Media Player: 12.0.7601.17514
.NET Framework: 2.0.50727.5420|2.0SP2|3.0.30729.5420.5420|3.0SP2|3.5|3.5SP1
Windows Installer: 5.0.7601.17514
DirectX: 4.09.00.0904
MSN/Live Messenger:

Office Components:
** NONE **

Checking existance of all needed files like aamd532.dll, COMCTL32.OCX etc...
Checking file: C:\apup\bin\aamd532.dll
Checking file: C:\apup\bin\COMCTL32.OCX
Checking file: C:\apup\bin\MSCOMCTL.OCX
Checking file: C:\apup\bin\COMDLG32.OCX
Checking file: C:\apup\bin\FM20.DLL
Checking file: C:\apup\bin\FM20ENU.DLL
Checking file: C:\apup\bin\REBOOT.EXE
Checking file: C:\apup\bin\RICHTX32.OCX
Checking file: C:\apup\bin\SSUBTMR6.DLL
Prepwork Done Bring Up Main Form...

The Windows error box is the same as in the screenshot posted above, but it references autopatcher.exe v5.7.18 in the "problem signature" instead of v 5.7.15.

Edited by Whatacrock, 12 February 2013 - 03:54 AM.