> I recently purchased Win4Lin 2.0 and installed it on my Red Hat 6.2 system.
> On the whole it works fine but if it's left unattended for more than about
> half an hour it freezes completely.
This seems really odd Matt. It's hard to even begin to understand why
it might be happening as you haven't said anything about what sort of
system, which version of Windows, etc. you're using. Which ports (com
& lpt) are you grabbing with Win4lin. Any chance that some Linux
process is conflicting? I've found, for instance, that if I have com
ports active in Win4lin, gPhoto can't access them from Linux. Could
be that some sort of interaction like this is freezing things if
you're actively using those ports in Win4Lin. For what it's worth, I
have Win4Lin running most of the time under Mandrake and have never
had the problem you describe.
> It also appears to be impossible to kill the two "dosexec" processes that are still
>running. I've tried closing the Win4Lin "Windows" window; kill; kill -9; and kill
>-15, both as normal
> and superuser.
Now that seems REALLY wierd. Aren't those processes owned by you? I
just checked mine and they're owned by me and a simple "kill pid" did
them in. This really smacks of something interacting with those
processes that shouldn't.
> Even worse, the only way I've found to clear it is to reboot my machine,
Oooo...yuck.
> which in turn fails to cleanly unmount my filesystem because it is "in use"
> (presumably by Win4Lin), which then results in having to run fsck on reboot.
Something really wrong with the installation here Matt. This is the
only explanation for these sorts of results.
Cheers --- Larry
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
