AutoPatcher Forum

Thank you for the reply.

I'm not at a computer where I can check this, so I'll come back to you later.

In the meantime, it is not unusual for the date on downloaded files to be wrong. In fact none of AutoPatcher's support files have an internal date of 12/03/2007. As I said in an earlier post, this is not important, it's the file version that matters.

--

Are you sure you have the right version for comcat.dll?

You have posted 6.0.2800.1106, which is a common version for Internet Explorer DLLs.

However, on every Win2000 computer I have looked at, comcat.dll has the following details:
Date: 19-06-2003
Size: 3,856 bytes
Version: 5,0,2195,1

--

Oops. Sorry. I must have been getting tired. I transcribed the versions from a sheet of paper and two of them are incorrect because I copied from the line above when I got to the details:

advpack.dll 6.0.2800.1106 24/08/2002
comcat.dll 5.0.2195.1 19/06/2003


I also missed out SSubTmr6.dll which is 1.1.0.3 12.03.2007

Sorry again.

Paul B

Thanks for the corrections, that makes a lot more sense!

In the meantime, I have been checking what shows up on various Win2000 computers. I have a variety of configurations, but whatever I try I cannot reproduce your Divide by Zero error.

--

Is my configuration among the ones you have come across?

Paul B

No, I haven't found a system with exactly the same combination of files as yours, but that's usually because mine are more fully patched. It looks as if, at one time, one or more was almost the same as yours -- which just adds to the frustration because I still cannot get AutoPatcher to crash with or without a Division by Zero error. (Division by Zero = error code '11' decimal = error code '0xB' hexadecimal.)

However, I do have more recent versions of COMCTL32.OCX and/or MSCOMCTL.OCX on several systems. You don't have the defective version of MSCOMCTL.OCX, but you can try downloading and installing a patch that will update these two components:
[indent]VisualBasic6-KB896559-v1-ENU.exe (DOWNLOAD PAGE)[/indent]This will give you:
COMCTL32.OCX version 6.0.81.6
MSCOMCTL.OCX version 6.1.97.86

I also have older versions of just about every file listed on some older hardware that is normally kept foe emergencies, so it looks as if the problem lies elsewhere. At this moment I just don't know where else to look because, as I said earlier, it is almost impossible to diagnose this over a forum.

--

I tried your suggestion, but it made no difference. Autopatcher still produced the same error as before.

I have now been able to look at a much older version of the system that is causing the problem, a sort of restore point, where Autpoatcher still works. It tells me that three files are different in the working version:

comdlg32.ocx 6.1.97.82 12/03/2007
mscomctl.ocx 6.1.95.45 12/03/2007

and

msvbvm60.dll 6.0.96.90 19/06/2007

All the other files are exaclty the same in both versions. Clearly something has changed files after autopatcher installed them. What, I have no idea.

There doesn't seem to be any obvious way of solving this, other than by a reinstall. I may have time for that in the near future.

Thanks for your help in trying to find a solution.

Paul B

I don't believe it!

Well I do, of course because I've seen it with my own eyes. I have just been reinstalling Windows 2000 in order, among other things to try and resolve the problem with Autopatcher. Everything looked fine and I thought I'd installed all the programs likely to cause trouble, with Autopatcher still working. So I continued to install the last few, without testing Autopatcher each time. When I tried it next, the old problem resurfaced.

I still had an old installation that worked so I compared the two and installed all the software that was not yet present on the instalationl that worked. Autopatcher still worked. So then I did one last thing. Using the software already installed, I rotated into portrait mode, which is how I normally work. That was the problem. In portrait mode Autopatcher produces the divide by zero error. Back into landscape mode and it works fine again.

I don't think this is particular to the rotation software. Previously I was using the rotation facility in ATI Catalyst. Now, however, I don't have Catalyst installed, just the ATI driver and I'm using a little utility called iRotate which does the job with much less overhead. Both produce the same error in Portrait.

So that appears to be my problem.

Paul B

Words fail me!

Thanks for both tracking down and letting me know the cause of the problem.

Actually, the worst part is that I should have thought of this, because it has happened before. See this thread: Autopatcher confused by monitor. I know I was off ill in April, but I remember reading that thread later on. If you look at the log PortraitMode has posted, the similarities are obvious. By comparison, the fault definitely lies with AutoPatcher, because your drivers are ATI, whereas his are NVidia.

I don't know when this will be fixed. Short-term plans are focussed on APUP at the moment. Meanwhile, I'll add "Which way round is your monitor?" to the long list of questions I have to ask.

Thanks again.

--

I can Verify the rotate issue on XP SP3 as well.
I'm using iRotate from entechtaiwan.com.

0�° works
90° doesn't
180° works
270° doesn't

Had quit using apup for months until finding these posts. Nice find PaulB!

James, on Sep 9 2008, 12:30 PM, said:

Thanks for the report.

I found this bit amusing:

woodchuk, on Feb 17 2009, 05:09 PM, said:

For the benefit of other users, I have amended the topic title to add "in portrait mode" at the end.

--

Also happens with current AutoPatcher in XP sp3 in Virtual box when the window is taller than it is wide.

Workaround, resize the window so that it's shorter and try again.