7 replies to this topic

[laemel]

I've been using Autopatcher for a while, and it works very well, but I've run into a problem on a computer here that I can't find any info on.

The computer runs a special-purpose video card which has a weird aspect ratio and only black and white color, and this causes the Autopatcher crash handler to pop up a message saying "Error while Autopatcher was trying to resizing window". If I enable /devmode and click "Ignore" for those video-related errors, it works fine.

The problem is that I need this to run totally automated, since it's being bundled as part of a larger installer. No clicking "Ignore". So the logical choice is to use /nocrashhandler. But when I do this, as soon as I start it a window pops up titled "AutoPatcher" with the following error: "Run-time error '-2147208422 (8004331a): Message already handled by another class". After this it just quits.

This only happens on one system, I have another with the same video card and same video-related error, and /nocrashhandler work fine. I think it must be something to do with the environment, but I have no idea what. I can't find anything on google or the forums here about this... Anyone seen this, or know how to repress/get past the error?

Attached Files

•  err.gif   5.89K   6 downloads

[Cristiano]

in deed, autopatcher has an issue with weird aspect ratio that was pointed some time ago. it's pretty rare and only happens in certain scenarios and i don't remember anymore the resolution of that screen. if you can, please state the exact resolution. without reproduce the bug, it's pretty hard fix something and i remember that this issue is related to that

thanks in advance

[]s

[laemel]

Cristiano, on 12 March 2010 - 06:37 PM, said:

in deed, autopatcher has an issue with weird aspect ratio that was pointed some time ago. it's pretty rare and only happens in certain scenarios and i don't remember anymore the resolution of that screen. if you can, please state the exact resolution. without reproduce the bug, it's pretty hard fix something and i remember that this issue is related to that

thanks in advance

[]s

Thanks for the reply. I've got a couple systems I've been able to reproduce this on. The video cards they use are Barco Nios (they're used for reading mammograms). One system is running at 2048x2560, and the other is running 1536x2048, both 8-bit black-and-white color. In both cases this is the only available video mode. There aren't any errors in c:\windows\autopatcher.log or anywhere else I can find. I also attached the crash handler message here (if I repress with /nocrashhandler I get the "Message already handled" error from my first post).

[laemel]

Attached is the crash handler error.

Attached Files

•  crashhandler.gif   10.47K   12 downloads

[laemel]

I haven't made an progress on this... Looks like I am switching to WSUSOffline

[Cristiano]

well, our developers may not have seen your message. i will made an bump about it

[]s

Edited by Cristiano, 16 March 2010 - 07:10 PM.

[Antony]

Hmmm. Now I see this bug)))
But that's the only one good news..
Bad news are - that I do not think that I can fix such rare error without physical access to this computer.

I will try to add some log messages - which will show to us where exactly in code we have such problem..
And if they will be useful-then we can fix it))))

[laemel]

Antony, on 17 March 2010 - 06:35 AM, said:

Hmmm. Now I see this bug)))
But that's the only one good news..
Bad news are - that I do not think that I can fix such rare error without physical access to this computer.

I will try to add some log messages - which will show to us where exactly in code we have such problem..
And if they will be useful-then we can fix it))))

I'd be willing to test whatever changes you put in.