I have done some experiments:
When I start 'fwin &' from within a terminal emulation: After shutting down
windows, no error occures.
When I start 'fwin' or 'fwin &' with a starter (shortcut on my desktop) with
'Terminal=true' (or 'false'): After shutting down Windows, I get this
unreadable gnome-session/X.
BUT: when I open a terminal emulation OR some other window (will be
unreadable) AND I resize this window, THEN this window gets 'cured'. When I
move this 'cured' window over my desktop, everything gets 'cured' too, and I
have not to restart X.
Am Donnerstag 08 Februar 2001 09:59, schrieb ich:
> Hallo all.
>
> I have upgraded to W4L-2.0.1. Running fwin works fine (for both Win4Lin and
> Gnome). After shutting down W4L, the Gnome-environment (I have to test this
> with KDE) is scrambled resulting with unreadable text, etc. It looks very
> much as a problem with X. I have to restart X in order to resume using
> Gnome/X When I run 'win' (in a desktop within my Gnome-session), after
> shutting down w4l, this problem doesn't happen.
>
> Is this a problem of W4L-2.0.1 or do I have to adjust my XF86Config or
> upgrade to X-4.0.2 (I now use X-4.0.1)??
>
> Greetings from Utrecht (NL),
>
> Ulrich
--
Groeten uit Utrecht,
Ulrich
--
_________________________________________________________
*Linux: the choice of a GNU generation*
_________________________________________________________
Ulrich Grün
Amsterdamsestraatweg 609 BIS
3553 EJ UTRECHT
Tel:+31302467141
mail: [EMAIL PROTECTED], [EMAIL PROTECTED]
icq: 35629246
System: AMD-K6 350, 192MB. OS: RedHat 7, Kernel: 2.2.19pre3
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
