I don't have an ETA and I apologize for the delay. I'm currently very busy with other projects, so I don't know when I will return to this, but I do plan to because the current RD Tabs is getting pretty long in the tooth. 🙂

This is a known issue in Windows ... and has always been a problem for, like, ever. DO NOT CHANGE YOUR DPI SETTINGS TO ANYTHING OTHER THAN 100%. IF YOU SUFFER FROM POOR EYESIGHT, CHANGE THE RESOLUTION, NOT THE DPI.

This is a mistake that a lot of people make. They either don't realize what "resolution" means (or what it affects) or simply do not see it in the settings. Eventually, they find the "DPI" settings and start adjusting that to "fix" their problem. Next, they realize that various other windows settings "look wrong", so they start adjusting fonts and/or font sizes, and other settings found withint their applications. Before you know it, they have totally screwed up their display settings.

Installing the proper Video Card and Monitor drivers, and then adjusting the resolution to the proper aspect ratio IS the ONLY way to adjust the display properties. Using the correct (latest) monitor drivers not only gives you access to Native resolutions that are not possible/found in the Windows default settings, but it also allows you to use display timings that may not be available with the Windows defaults. In addition, using a higher refresh rate will usually improve overall response time and improve brightness and clarity. This means displayed text is more readable, graphics are sharper and games/applications run faster.

Recommendations are to use the highest resolutions that your display supports (that is still comfortable on your eyes), 72 Hertz or greater for Analog monitor displays, 60 hertz for LCDs (when using Digital connections), 32 bit color. The higher hertz settings will provide less eye fatigue and/or flicker (LCDs do not produce flicker). To avoid skewing on wide screen monitors, use resolutions such as 1280x800, 1400x900, 1680x1050, depending on the aspect ratio (see your display manual for further help on this).

I keep catching clients fiddling with the DPI setting, not realizing that it changes much more than they realize. For instance, icon text becomes cut off, window titles AND buttons are cut off or impossible to read due to incorrect font sizing, web browsers do not show/print the pages properly, etc. I am not sure why this affects the network connections but adjusting the DPI settings has just always been a bad idea.

I hope this helps someone.

Thank you for this post - for weeks I have not been able to get RDTabs working and had dozens of Microsoft connections on my desktop.

THANK YOU!!!!

I am running Win 7 64 as well and my RD Tabs will not work on any DPI setting except 100%, as my screen res is so high it is difficult to use at 100%. As a note the default setting on my machine states it is 125%. Thanks, I love the product!

I too found RD Tabs to fail in Windows 7 64-bit as my company's display setting is automatically set to 125%. The funny thing is that Microsoft's RDP sessions are not impacted by this same setting. I think there is something being missed by RD Tabs, but don't know what it is. I, like everyone else here, have relegated to the fact that I must set my screen to 100% rather than the more appealing 125% to get RD Tabs to function. I really love the product, so I'll continue to run at 100%. But I sure wish this could be resolved so it doesn't require me to run my screen at 100% (a bit too small for me)....

Sorry for the pains this is causing. I have a fix in queue and hope to release it soon.

Any ETA on a fix for the 125% display problem ?
For Reading text on a 30' Display in 2560x1600 125% is a Must !


-Thanks

Okay, so I finally got off my lazy ass and back-ported a couple bug fixes and one new feature (better NLA and SSO), including this long overdue bug fix, from the very unfinished 3.0 code base to the 2.1 code base!

Just run RD Tabs Update, or wait 24 hours, and it will be yours. :-)

Note: RD Tabs 2.1 will no longer crash in 125%, but it will look kinda crappy because so much of the old UI wasn't designed for non-100% DPI. It is 100% functional, though, it just looks bad. I hope this can hold you all over until 3.0 comes out. The connection properties UI layer was partially redesigned so it will handle all DPIs.

I feel like its X-Mast ,Diablo 3 and Rd Tabs working in 125% in the Same Week ! /:d/

You Are my Santa !

Thanks Alot T