Can anyone suggest a way to disable AREV DOS session (I guess any session) window's "Close" (the infamous 'X' ) button. Users 'Xing' out of AREV application window's Title Bar is causing us a havoc.

Any suggestions would be greatly appreciated.

Raju T.

Dire threats and then severe beatings sometimes helps….

The best you can do is to right click on the properties to the ARev icon / shortcut, click on the "Misc" tab and check "Warn if still active"

It is already checked, and has not been able to prevent it.

Thanks for your input.

It's theoretically "do-able" by writing your own command shell which itself fires up the ARev DOS session, and intercepts any WM_CLOSE message addressed to it.

I've never actually tried it, though!

If you run it under full screen the user has to exit the dos session.

The employees where I work don't like it but it does eliminate some problems.

Can you run in "full screen" mode?

I think I did it in Arev 2.12. Basically found the verb that executes the DOS shell and shelled that verb with my own code. Also had to shell the debugger and disable TCL. Hmmmm…. maybe it was just the TCL disable. At one point Sprezzatura had a list of what verbs did what - maybe one of those will chime in here.

Check out:

http://www.ukwares.com/&assyicz24&

It seems possible to install a "remote hook" into another process, which may then enable you to write an event handler for WM_CLOSE. This could be an exe which, while running, absorbs the WM_CLOSE events of a specific Window. If said application had a command line parameter to uninstall itself, then AREV could be run by a batch file thus (assuming your program would be called "KILL_CLOSE.exe"):

@ECHO OFF

KILL_CLOSE /install

LHIPXTSR whatever

AREV whoever /X M4096

LHIPXTSR /u

KILL_CLOSE /uninstall

Therefore while AREV is running it would be impossible to close the running window, but as soon as the AREV.exe process is finished, the handler would not stop the window closing at the end of the batch file.

I'm already drifting dangerously out my depth here, though, so don't ask me for any more details!

I mentioned this in passing to Lee Dobson and Keith McKay here, and within 10 minutes they'd supplied a working solution in C++ !

Drop an email to [email protected] if you'd like a copy of KILL_CLS.EXE. This can sit in your AREV directory and be fired off by the .BAT file that runs ARev, without parameters.

Note that it doesn't disable an explicit process close from the Task Manager itself - but to me, this is the desirable behaviour anyway.

Cameron

Our users need to open a min of 4 sessions (different modules) all the

time. Full screen would not be an option at all. Cameron's EXE sounds good, and playing withe the VERBS may be another option. But, any new

suggestions are still appreciated.

Raju T.

Thanks for your suggestions, and I am still looking for more.

Raju

View this thread on the forum...