Hi Paul,
This probably doesn't solve your immediate problem, but there is
a 'nice' way to shut down a Win4Lin Windows session that isn't
responding. Rather than killing the processes from an xterm,
hit 'shift-F12' while the Windows window is active. This should
bring up the Win4Lin menus on the window. You can then close down
Win4Lin from one of the menubar menus. It will not shut down Windows
nicely, but it will shut down Win4Lin nicely, which does not
happen if you just click on the 'X' on the window, or try to
kill the processes from an xterm. Closing a non-responding
Windows window in this manner should prevent your problem
from occuring.
Regards,
Amanda Owens
"Paul W. Abrahams" wrote:
>
> I've encountered this problem several times. I'm forced to
> shut down Win4Lin because of some kind of unrecoverable
> error. Then, when I attempt to start it, the restart is
> blocked because Win4Lin thinks there's already a session
> going. Even shutting down X and logging in again doesn't
> cure the blockage, although a total system reboot does clear
> it.
>
> How can I clear this blockage without having to resort to a
> full reboot?
>
> Paul Abrahams
>
> _______________________________________________
> Win4Lin-users mailing list
> [EMAIL PROTECTED]
> https://lists.netraverse.com/mailman/listinfo/win4lin-users
--
Amanda Owens
Support Engineer
NeTraverse, Inc.
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
