Jump to content


Yikes! Crash Handler, Confused


7 replies to this topic

#1 WillEllen

    Member

  • Members
  • PipPip
  • 11 posts

Posted 22 March 2013 - 02:36 PM

I setup AutoPatcher on a Vista machine where it works just fine. I then transferred the whole thing to a flash drive. When attempting to update an XP system with it (AutoPatcher.exe) I get the crash handler Yikes! It will continue normally when the X in the top right corner in pressed. Log as follows:

Attempting to initialize common controls.
Accessing filesystem...
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 XP Professional Service Pack 3
System Components:
Internet Explorer: 8.0.6001.18702
Windows Media Player: 9.0.0.4503
.NET Framework: 1.1.4322|1.1SP1|2.0.50727.3053|2.0SP2|3.2.30730.01|3.2SP2|3.5|3.5SP1|4|4SP0|4.0|4.0SP0
Windows Installer: 4.5.6001.22159
DirectX: 4.09.00.0904
MSN/Live Messenger:

Office Components:
Microsoft Word: 11.0.8313.0
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_1_4_0\bin\aamd532.dll
Checking file: C:\Apup_1_4_0\bin\COMCTL32.OCX
Checking file: C:\Apup_1_4_0\bin\MSCOMCTL.OCX
Checking file: C:\Apup_1_4_0\bin\COMDLG32.OCX
Checking file: C:\Apup_1_4_0\bin\FM20.DLL
Checking file: C:\Apup_1_4_0\bin\FM20ENU.DLL
Checking file: C:\Apup_1_4_0\bin\REBOOT.EXE
Checking file: C:\Apup_1_4_0\bin\RICHTX32.OCX
Checking file: C:\Apup_1_4_0\bin\SSUBTMR6.DLL
Now all is done - we can start Main-form loading procudere.

Any correction for this?

WillEllen

#2 WillEllen

    Member

  • Members
  • PipPip
  • 11 posts

Posted 22 March 2013 - 07:50 PM

This just in! Same computer but with diffrent Windows xp hard drive that has not been upuated for several months; all works well (no Yikes!). Is there any reason for this?
WillEllen

#3 ViroMan

    Just an awesome guy.

  • Project Manager
  • PipPipPipPipPipPip
  • 1,189 posts
  • Gender:Male
  • Location:California, USA, Earth, SOL, Milkyway
  • Interests:Programming and being a know it all pest.

Posted 24 March 2013 - 08:09 AM

it would be helpful if you had a screenshot of the yikes or copy the error down, since it doesn't show in the log. The log does show that your using an older AP though.

#4 sirhc

    Member

  • Members
  • PipPip
  • 15 posts

Posted 24 March 2013 - 09:25 AM

I have the same problem. Until now Autopatcher has worked perfectly (many thanks!!!) although it's been a few months since I last ran it.
I d/l the latest Apup_1_4_0.zip and after cutting and pasting all of my old folders to the new AutoPatcher\Apup_1_4_0 folder, I ran apup.exe v1.4.0.5 and got the log (130324 apup1.txt). Everything seemed OK.
Attached File  130324 apup1.txt   4.37K   1 downloads
When I tried to run autopatcher.exe v5.7.0.5 I got the Crash Handler Yikes! (see 130324 Yikes!.gif and 130324 Crash Handler.txt)
Attached File  130324 Yikes!.gif   30.62K   7 downloads
Attached File  130324 Crash Handler.txt   1.55K   1 downloads
I ran apup.exe again and got the log (130324 apup2.txt). Again, everything seemed OK.
Attached File  130324 apup2.txt   1.98K   0 downloads
Trying to run autopatcher.exe just keeps crashing. Any thoughts?

Edited by sirhc, 24 March 2013 - 09:33 AM.


#5 ViroMan

    Just an awesome guy.

  • Project Manager
  • PipPipPipPipPipPip
  • 1,189 posts
  • Gender:Male
  • Location:California, USA, Earth, SOL, Milkyway
  • Interests:Programming and being a know it all pest.

Posted 24 March 2013 - 07:34 PM

OK for sirhc(and possibly WillEllen) your problem is probably a bad DLL file that got handed out a while ago. I am pretty sure I fixed that download to stop handing out the bad DLL but, I guess not. I will check it later after work when I have time.

Until then you can go to THIS POST and learn how to fix that problem yourself.

Edited by ViroMan, 24 March 2013 - 07:34 PM.


#6 sirhc

    Member

  • Members
  • PipPip
  • 15 posts

Posted 25 March 2013 - 03:24 AM

Problem solved!
I had SSubTmr6.dll v1.1.0.3 in \system32 and v2.0.0.0 in \bin.
I copied the v2 to \system32 as per your instructions and Autopatcher ran as smooth as silk again (almost).
Part way through the installation process I got a KB2809289 Setup dialog box and had to click OK for it to continue.
Attached File  KB2809289 Setup.gif   68.33K   3 downloads
I've never had that happen before, and don't know what it was about, but my system seems to be running OK again.
ViroMan, many thanks for your help and the excellent work you do!!!

#7 ViroMan

    Just an awesome guy.

  • Project Manager
  • PipPipPipPipPipPip
  • 1,189 posts
  • Gender:Male
  • Location:California, USA, Earth, SOL, Milkyway
  • Interests:Programming and being a know it all pest.

Posted 27 March 2013 - 08:39 AM

ok, Good that it was a simple fix for your problem. The box that poped up was the update saying we passed the wrong switches to it to get it to install. Usually we pass in /quiet /norestart but, it may have been misspelled or something. Nothing to be worried about except, that update didn't install.

#8 WillEllen

    Member

  • Members
  • PipPip
  • 11 posts

Posted 27 March 2013 - 02:29 PM

The SSubTmr6.dll was the cause of the problem.
Thanks all
WillEllen





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users