|
|
 asMessageBox in ashlog.log
#31633
12 Sep 19 10:27 AM
|
Joined: Sep 2003
Posts: 4,135
Steve - Caliq
OP
Member
|
|
OP
Member
Joined: Sep 2003
Posts: 4,135 |
I've noticed at one (may more?) customers that XCALL MESAG are going to ashlog.log but dam if I can spot what's set to do this? miame.ini has just TRACE=BASERR,SIGHUP
12-Sep-19 10:24:43 [p29526-9]<OETINV:MADQST:0x22d1> asMessageBox(Accept serials and continue?,,292)
12-Sep-19 10:25:04 [p29526-9]<OETINV:MADQST:0x22d1> asMessageBox(Accept serials and continue?,,292)
Any clues be appreciated....  Ta.
Last edited by Steve - Caliq; 12 Sep 19 10:51 AM.
|
|
|
|
Re: asMessageBox in ashlog.log
[Re: Steve - Caliq]
#31644
12 Sep 19 05:27 PM
|
Joined: Jun 2001
Posts: 11,645
Jack McGregor
Member
|
|
Member
Joined: Jun 2001
Posts: 11,645 |
At one point (several years ago), I thought it would be a good idea to log all such message boxes. (It sure comes in handy when trying to research a reported problem to see that the user actually did get a message box, which of course they neglected to included in the initial report.)
But, after some complaints about it being too much, I decided on a compromise: as of 6.1.1335 (on Linux) it only logs the message if they contain a flag suggesting a warning or error, i.e., any of the following will do it:
MB_ICONSTOP
MB_ICONEXCLAMATION
Your trace above however suggests otherwise: the flags value 292 is 256+32+4 or MB_DFLT2 + MBICON_QUESTION + MBTN_YES_NO.
Which makes me think this is either an old AIX system, or maybe a standalone Windows system?
|
|
|
|
Re: asMessageBox in ashlog.log
[Re: Steve - Caliq]
#31648
12 Sep 19 06:53 PM
|
Joined: Sep 2003
Posts: 4,135
Steve - Caliq
OP
Member
|
|
OP
Member
Joined: Sep 2003
Posts: 4,135 |
It’s actually a fairly upto date (last 6 months?) Linux Ashell.. maybe it’s the question mark in the caption?
|
|
|
|
Re: asMessageBox in ashlog.log
[Re: Steve - Caliq]
#31649
12 Sep 19 09:07 PM
|
Joined: Jun 2001
Posts: 11,645
Jack McGregor
Member
|
|
Member
Joined: Jun 2001
Posts: 11,645 |
Ahhh - I see the problem. Microsoft lured me into thinking that the various MBICON_xxx bits (which A-Shell shares with the standard Windows MessageBox) were exclusive, when in fact they're not:
define MBICON_STOP = &h0010 ! 16 ICONS
define MBICON_QUESTION = &h0020 ! 32
define MBICON_EXCLAMATION = &h0030 ! 48
define MBICON_ICON = &h0040 ! 64
It was checking for (MBICONFLAGS and (MBICON_STOP or MBICON_EXCLAMATION)), but as you can see, MBICON_QUESTION overlaps with MBICON_EXCLAMATION. That will be fixed in the 6.5.1667.2 update ...
|
|
|
|
Re: asMessageBox in ashlog.log
[Re: Steve - Caliq]
#31650
12 Sep 19 09:13 PM
|
Joined: Sep 2003
Posts: 4,135
Steve - Caliq
OP
Member
|
|
OP
Member
Joined: Sep 2003
Posts: 4,135 |
Microsoft lured us into a lot of things .... thanks
|
|
|
|
|
|
|
