Thank you, Dokinik, for your assessment:
> > How would you judge its behavior concerning stability and side effects:
> > Would it be to risky to use it right away in a production system, aka
> > "testing under wild life conditions"?
>
> The worst that can happen is that different windows aren't
>
> A short update: Version 6.0.6 requires an old kernel, version
> 12.5 is downloading now (which is a matter of several hours given
> the local internet speed).
Sorry, I should have mentioned that this might be an issue.
Each version of Vmware Workstation or Player supports only very few
Thank you, Dominik, for your answer:
> On Thu, Nov 17, 2016 at 08:53:21PM +0000, Jürgen Hartmann wrote:
>> Previously, I mailed the output of xev for the Vmware's client and frame
>> windows while switching off fullscreen mode, as advised by Dominik Vogt.
>
> Please just
Previously, I mailed the output of xev for the Vmware's client and frame
windows while switching off fullscreen mode, as advised by Dominik Vogt.
Since therein there were UnmapNotify and MapNotify events on the client side
and a DestroyNotify event for the frame window, I thought that it might be
Thank you very much, Dominik, for your reply and the enlightening explanations.
> On the site you mentioned below there are only 64-bit Linux
> binaries available for download, and only for version 12. I'd
> like to help, but I need a 32 bit Linux version that shows the bug
> and that can
>> All of this is kind of a hack. VMWare wants 100% of the mouse and
>> keyboard events to go to the virtual machine without your host
>> environment getting in the way, even if what you're doing normally
>> has special meaning to the host.
>
> I see. However, if it does that, it cannot expect
In my last post, I described the creation of a virtual machine, saying that
most of the offered setting can be left on their defaults.
But when it is about to choose the guest operating system, it is better to
select "Windows 3.1" than the default "Windows 7": I encountered some driver
problems
> > What is the secret behind this move? How does it work?
>
> I have no idea, and I'd not even call that a workaround. It just
> seems that if you change random things, it starts to work.
I see. That obsoletes my next question in the queue addressing side effects.
What would you propose to
> Try commenting out only the body of the if-condition, i.e.
>
> --
> args.do_return_true_cr = False;
> if (
> FCheckIfEvent(
> dpy, , test_withdraw_request,
> (XPointer)))
>
> > What would you propose to proceed?
>
> 1) Don't panic. ;)
Truly a wise word... :)
> 2) Try the attached patch.
Done: It works great with respect to our issue. For Player and Workstation.
Concerning side effects, I can't say anything since I have no idea what
to look for.
> Now, if I'd
10 matches
Mail list logo