Hi,<br><br>do you know if using DirectDraw and not using it makes any diffences in performance? We use NX also to open big EDA Layouts and for this the maximum in performance is very important. For "normal" work I can't see any differnce (this means, browser, mail, terminals, eclipse, ...).<br>
<br>Cheers,<br>Florian<br><br><div class="gmail_quote">2009/11/10 Jeremy Wilkins <span dir="ltr"><<a href="mailto:wjeremy@shaw.ca">wjeremy@shaw.ca</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
This is a problem with the way the NX client utilizes DirectDraw and cannot<br>
be resolved except by disabling DirectDraw in the client as you have done<br>
already, or for the windows cygwin X sources to be updated to support the<br>
new DirectDraw/Direct3D layer. Vista and Windows 7 both use a new<br>
DirextDraw layer which has limited compatibility with the old DirectDraw<br>
methods via a 3D buffer redirect in Aero mode (direct indirect if you will).<br>
The problem comes up when the screen is locked because Aero shuts down<br>
temporarily (resuming legacy DirectDraw/Direct3D mode to save resouces I<br>
think) and NX should relinquish its hold on the DirectDraw buffer at this<br>
time. It doesn't because the cygwin X server would fail if it did, leading<br>
to a disconnect. Windows 7 detecting that DirectDraw is active in legacy<br>
mode doesn't enable Aero again until the DirectDraw buffer is closed.<br>
Rightly so, as some legacy programs (Mostly 3D ones) might crash or corrupt<br>
the framebuffer possibly leading to a system halt otherwise. This also<br>
might be resolved if cygwin X could release its DirectDraw buffer when the<br>
screen is locked or unlocked without losing the X server entirely. Kind of<br>
running the X server into a memory buffer temporarily instead of the screen<br>
until after. Windows 7 could also be smarter about what kind of DirectDraw<br>
buffer is being used since there is no 3D used in the buffer it would likely<br>
be safe for Windows to resume Aero. I'm pretty sure you would get the same<br>
results if you shut down Aero while NX is running, but that is worth a try<br>
to see. If it starts again successfully it is a Windows 7 bug with regards<br>
to legacy DirectDraw treatment during screen lock, otherwise what I said<br>
stands true.<br>
<div><div></div><div class="h5"><br>
<br>
Florian Schmidt-4 wrote:<br>
><br>
> Hi,<br>
><br>
> currently I have some minor problems with NX Client for Windows 3.4.0-5<br>
> and<br>
> Windows 7 and I haven't found any webpages addressing the problem.<br>
><br>
> First: everything works (basically) no crashes, no display problems, ...<br>
><br>
> The problem I found with Win 7 and NX Client 3.4.0-5 (latest) was that<br>
> after<br>
> locking the screen and unlocking again Windows Aero doesn't work anymore.<br>
> After closing the NX Client Windows switches back from Windows Basic View<br>
> to<br>
> Windows Aero View. At least for my Notebook this workaround fixed the<br>
> problem.<br>
><br>
> I replaced in the bin directory the cygwin .dll files with the files from<br>
> the newest version 1.7 (currently an beta release) but this was only half<br>
> of<br>
> the way. As a second step I choosed in the nx session file the following<br>
> option in the Advanced Tab:<br>
> Disable DirectDraw for screen rendering<br>
><br>
> After theese changes/settings Windows 7 Aero also stays after locking and<br>
> unlocking.<br>
><br>
> If anybody knows this problem or even knows a better workaround or even<br>
> fix<br>
> it would be great when you could reply to this mail on the list.<br>
><br>
> Cheers,<br>
> Florian<br>
><br>
</div></div><div class="im">> ________________________________________________________________<br>
> Were you helped on this list with your FreeNX problem?<br>
> Then please write up the solution in the FreeNX Wiki/FAQ:<br>
><br>
> <a href="http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ" target="_blank">http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ</a><br>
><br>
> Don't forget to check the NX Knowledge Base:<br>
> <a href="http://www.nomachine.com/kb/" target="_blank">http://www.nomachine.com/kb/</a><br>
><br>
> ________________________________________________________________<br>
> FreeNX-kNX mailing list --- <a href="mailto:FreeNX-kNX@kde.org">FreeNX-kNX@kde.org</a><br>
> <a href="https://mail.kde.org/mailman/listinfo/freenx-knx" target="_blank">https://mail.kde.org/mailman/listinfo/freenx-knx</a><br>
> ________________________________________________________________<br>
><br>
<br>
--<br>
</div>View this message in context: <a href="http://old.nabble.com/NX-Client-with-Windows-7-tp26265886p26275439.html" target="_blank">http://old.nabble.com/NX-Client-with-Windows-7-tp26265886p26275439.html</a><br>
<div><div></div><div class="h5">Sent from the freenx-knx mailing list archive at Nabble.com.<br>
<br>
________________________________________________________________<br>
Were you helped on this list with your FreeNX problem?<br>
Then please write up the solution in the FreeNX Wiki/FAQ:<br>
<br>
<a href="http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ" target="_blank">http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ</a><br>
<br>
Don't forget to check the NX Knowledge Base:<br>
<a href="http://www.nomachine.com/kb/" target="_blank">http://www.nomachine.com/kb/</a><br>
<br>
________________________________________________________________<br>
FreeNX-kNX mailing list --- <a href="mailto:FreeNX-kNX@kde.org">FreeNX-kNX@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/freenx-knx" target="_blank">https://mail.kde.org/mailman/listinfo/freenx-knx</a><br>
________________________________________________________________<br>
</div></div></blockquote></div><br>