httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Braund" <>
Subject RE: [patch 1.3.13-dev] Win9x Services
Date Mon, 12 Jun 2000 05:58:44 GMT
> -----Original Message-----
> From: William Rowe []On Behalf Of William A.
> Rowe, Jr.
> Sent: Monday, 12 June 2000 13:06
> To:
> Subject: RE: [patch 1.3.13-dev] Win9x Services
> Interesting...
> I'm really unclear about the Ctrl+C problem in W2K.  First off, does
> it make a difference in select mode if you hit Ctrl+break instead?

Yes, apache terminates normally with ctrl+break.
If you are in select mode a ctrl+c takes you back
to "edit Mode", a second ctrl+c terminates apache normally.

> Second, is the select mode the *default*?


>  Or is it only a problem
> if you accidently *trip* it?

You trip it by clicking in the command prompt window when it already had the
If the window didn't have the focus, a click gives it the focus but it stays
in "edit mode".
It seems that a left click on a command prompt that has focus will get you into
"select mode". Subsequent left clicks have no effect. A right click will put
the command prompt back to "edit mode".
Typing normal characters, escape, arrow keys (but not ctrl, shift or alt keys)
also gets you back into "edit mode".

>  Or is this ctrl+c the copy command,
> without any option to bypass it?

Ctrl+c when in select mode puts the command prompt window back to "edit mode"
clears any highlight you had dragged but doesn't seem to do anything useful
ie the clipboard is left unchanged.
ctrl+insert also exhibits the same useless behaviour.
In order to copy you need to select the text with mouse drag, then hit the
enter key.

>  Try using mode 0x87 and see if that
> solves the problem.

Left click in the window no longer has any effect. ctrl+c always gives CTRL+C

0x0087 - no select, no mouse move events
0x008f - same, no mouse move events
0x003f - same and you get mouse move events
0x001f - same and you get mouse move events
0x009f - same and you get mouse move events
0x00af - same, no mouse move events

0x00cf - select behaviour, no mouse move events
0x006f - select behaviour, no mouse move events
0x004f - select behaviour, no mouse move events
0x00bf - select behaviour, no mouse move events

When in select mode the X (window close) gives "win can not shut this window",
I click
cancel, then when command prompt goes back into edit mode ie press a key or
right click in the window, then the window gets the close and testconsole
but command prompt window does not close as it usually does.

> Perhaps we just tell them to use ctrl+break and not mention ctrl+c.
> I've noticed win95 is even stranger, mouse events are selected by
> default :-/  No *extra* flags can be toggled (any from mast 0xffc0)
> so there are no legal undocumented flags.  And no flag affects the
> shutdown/close button bug.
> One major problem in 95/98 is the lack of any progress message on
> startup/shutdown.  I'm thinking of a timeout'ed wait even on the
> child process, and using the window to determine if the service is
> started.
> Basically, we would use the send_signal_to_service call for both
> platform types, but use window enumeration for service control.
> I suppose I can even fix your issue with -k restart not having
> the same side-effect.  And I can stop the service without reading
> the config for the pid file.  This is a MAJOR problem if the user
> tries to start console apache with the service running, since the
> pid file is trashed and the service can't be -k stop'ped.
> I've left the hole in the ap_start_console_monitor()'s atexit handler
> so we can pause the console for feedback (direct from the api - can't
> trust the clib at that stage.)  Ideally, that input is the close
> button.  That obviously will not work for 9x.
> Those are my thoughts for tonight... perhaps we should take this to
> IRC and hack for a while.  But not tonight :-)
> Bill

View raw message