neal

Hi David,

The new version did not make any different with regards to the scaling issue. I've had to resort to the production release for day to day use. I will keep testing the Beta's as they are released and report back.

Regards,

Neal

The scaling is set at 150% on the 4K monitor and 100% on the monitor I run RDM. I am not familiar with an Auto scaling setting in windows 10.

The diagnostics show font scaling at 100% regardless of which monitor the app is running on. I sent screen shots of this in a prior post and you can see how the diagnostic screen is distorted and small in the beta.

Regards,

Neal

Hi David,

I tried launching the app without the second monitor connected. The symptom is unchanged. The splash screen show normal at first, then shifts to 50% smaller, then the main window opens with miniscule font sizes. The issue appears to be happening during the initialization of the app.

Regards,

Neal

@Neal,

Do you get the display good if you disconnect your external monitor?

Regards

Hi David,

I tried it without the second monitor connected and the results were unchanged. It appears to be something in the initialization of the app as the logo starts at the normal size (same as production version) but then shifts to about 50% normal size, then the main window opens.

Regards,

Neal

I get the splash on the 4k monitor but yes, they both open on the 2nd monitor by default. One thing I did notice is on the Beta, the splash first appears normal size, same as the production release, but then it shifts up and to the left on the 4k monitor and appears about 50% smaller. Then the main window opens on the 2nd monitor.

Regards,

Neal

Hi David,

Both appear to show 100% on scaling but note the screen shots below. Both were done on the 1920x1200 second monitor and you can see how the beta is distorted. First image is Production, then Beta.

Regards,

Neal

Hi David,

The production release looks good. Fonts are back to a readable size on the second monitor. It also works fine on the 4k monitor. Note that on the 4k monitor the DPI scaling is set to 150%. RDM works fine on either monitor and everything is back to normal. When I connect to a remote session, I now see a session resolution of 1666x964 on the second monitor (1920x1200) which is what I was getting prior to the beta.

Regards,

Neal

Hi David,

Happy to try it but I will need some help with installing it. I have the EXE installer, not the zip file and it complains there is a newer version installed and ends.

Regards,

Neal

Hi David,

I have already tried the "Disable display scaling on high DPI settings" option and it does not change the symptom. Note that I had no problem with the current release (11.7.6.0) using the same monitor setup.

Regards,

Neal

Using 11.9.1.0, I'm still having an issue with DPI scaling. My setup has a primary 4k monitor (3840x2160) and a secondary monitor at 1920x1200. I typically run RDM on the secondary monitor. DPI scaling setting on or off appears to have no affect. OS is Windows 10 Pro x64 using an Nvidia Geforce GTX 1080 using the latest driver.

RDM appears to be scaled at 100% as if it is on the 4k monitor. Moving the app between monitors does not change the font size in the tree list. On the 1920x1200 monitor, fonts look to be around 4 points and text is extremely small.

When I connect to a Remote Desktop session, I get 2444x1636 on the remote session on the 1920x1200 monitor, regardless of how I set the Display tab. I have tried forcing the Display to a lower resolution but it does not change the Remote.

Thanks for the help!

Neal

It takes longer for it to crash than it did before, but it still crashes.

Faulting application name: RemoteDesktopManager64.exe, version: 10.5.0.0, time stamp: 0x5519e4cf

Faulting module name: mscorlib.ni.dll, version: 4.0.30319.34209, time stamp: 0x53489fcf

Exception code: 0xc0000005

Fault offset: 0x00000000004ae294

Faulting process id: 0x2768

Faulting application start time: 0x01d06d0d49db667c

Faulting application path: C:\Program Files (x86)\Devolutions\Remote Desktop Manager\RemoteDesktopManager64.exe

Faulting module path: C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\mscorlib\fc9860df7e7c03efd26ad5311301dfcb\mscorlib.ni.dll

Report Id: 50f8a4c6-d90d-11e4-8145-60a44c5226b2

Faulting package full name:

Faulting package-relative application ID:

AND:

Application: RemoteDesktopManager64.exe

Framework Version: v4.0.30319

Description: The process was terminated due to an unhandled exception.

Exception Info: System.AccessViolationException

Stack:

at System.String.wcslen(Char*)

at System.String.CtorCharPtr(Char*)

at System.Runtime.InteropServices.Marshal.PtrToStringUni(IntPtr)

at Devolutions.RemoteDesktopManager.Managers.WindowsCredentialManager.GetTarget(System.String)

at Devolutions.RemoteDesktopManager.Managers.WindowsCredentialManager.TargetNameExists(System.String)

at Devolutions.RemoteDesktopManager.Frames.ConnectionSettings.FreRemoteDesktopConnectionSettings.c561d8b199603e13e89e94afdba14a2c1()

at Devolutions.RemoteDesktopManager.Frames.ConnectionSettings.FreRemoteDesktopConnectionSettings.SetControlStates()

at System.Windows.Forms.ComboBox.OnSelectedIndexChanged(System.EventArgs)

at System.Windows.Forms.ComboBox.set_SelectedIndex(Int32)

at Devolutions.RemoteDesktopManager.Business.ComboBoxEnumHelper.SetValue[[Devolutions.RemoteDesktopManager.ScreenSize, RemoteDesktopManager.Business, Version=10.5.0.0, Culture=neutral, PublicKeyToken=null]](System.Windows.Forms.ComboBox, Devolutions.RemoteDesktopManager.ScreenSize)

at Devolutions.RemoteDesktopManager.Business.ComboBoxEnumHelper.Load[[Devolutions.RemoteDesktopManager.ScreenSize, RemoteDesktopManager.Business, Version=10.5.0.0, Culture=neutral, PublicKeyToken=null]](System.Windows.Forms.ComboBox, Devolutions.RemoteDesktopManager.ScreenSize, Devolutions.RemoteDesktopManager.ScreenSize[])

at Devolutions.RemoteDesktopManager.Frames.ConnectionSettings.FreRemoteDesktopConnectionSettings.c0b11b8d406681aa28c93a8b42b9945f1()

at Devolutions.RemoteDesktopManager.Frames.ConnectionSettings.FreRemoteDesktopConnectionSettings.DoInitializeComponent()

at Devolutions.RemoteDesktopManager.Frames.FreBase.c86d934d755ca13d69271faed35eef974()

at Devolutions.RemoteDesktopManager.Frames.ConnectionSettings.FreBaseConnectionSettings..ctor(Devolutions.RemoteDesktopManager.ConnectionEditMode, Devolutions.RemoteDesktopManager.Business.ConnectionTypeDescriptor)

at Devolutions.RemoteDesktopManager.Business.RDPConnectionTypeDescriptor.CreateFrameConnectionSettings(Devolutions.RemoteDesktopManager.ConnectionEditMode)

at Devolutions.RemoteDesktopManager.Forms.FrmConnection.c7e9911698d4a5e79a26cd09891d405d0(Devolutions.RemoteDesktopManager.ConnectionType, System.String, Devolutions.RemoteDesktopManager.Frames.FreConnectionTypeSelection)

at Devolutions.RemoteDesktopManager.Forms.FrmConnection.LoadConnectionInControls(Devolutions.RemoteDesktopManager.Business.Connection)

at Devolutions.RemoteDesktopManager.Forms.FrmConnection.cd010602130da8ffa095e72f712cf3d19(System.Object, System.EventArgs)

at System.Windows.Forms.Form.OnLoad(System.EventArgs)

at Devolutions.RemoteDesktopManager.Forms.FrmBase.OnLoad(System.EventArgs)

at System.Windows.Forms.Control.CreateControl(Boolean)

at System.Windows.Forms.Control.CreateControl()

at System.Windows.Forms.Control.WmShowWindow(System.Windows.Forms.Message ByRef)

at System.Windows.Forms.Control.WndProc(System.Windows.Forms.Message ByRef)

at System.Windows.Forms.Form.WndProc(System.Windows.Forms.Message ByRef)

at System.Windows.Forms.NativeWindow.Callback(IntPtr, Int32, IntPtr, IntPtr)

at System.Windows.Forms.SafeNativeMethods.ShowWindow(System.Runtime.InteropServices.HandleRef, Int32)

at System.Windows.Forms.SafeNativeMethods.ShowWindow(System.Runtime.InteropServices.HandleRef, Int32)

at System.Windows.Forms.Control.SetVisibleCore(Boolean)

at System.Windows.Forms.Form.SetVisibleCore(Boolean)

at System.Windows.Forms.Application+ThreadContext.RunMessageLoopInner(Int32, System.Windows.Forms.ApplicationContext)

at System.Windows.Forms.Application+ThreadContext.RunMessageLoop(Int32, System.Windows.Forms.ApplicationContext)

at System.Windows.Forms.Form.ShowDialog(System.Windows.Forms.IWin32Window)

at Devolutions.RemoteDesktopManager.Managers.ActionManager.EditConnection(Devolutions.RemoteDesktopManager.IConnectionSource)

at Devolutions.RemoteDesktopManager.Managers.SessionMenuManager.cd94813672b0ecea85dc17deccf3b307e(System.Object, System.EventArgs)

at System.Windows.Forms.ToolStripMenuItem.OnClick(System.EventArgs)

at System.Windows.Forms.ToolStripItem.HandleClick(System.EventArgs)

at System.Windows.Forms.ToolStripItem.HandleMouseUp(System.Windows.Forms.MouseEventArgs)

at System.Windows.Forms.ToolStrip.OnMouseUp(System.Windows.Forms.MouseEventArgs)

at System.Windows.Forms.ToolStripDropDown.OnMouseUp(System.Windows.Forms.MouseEventArgs)

at System.Windows.Forms.Control.WmMouseUp(System.Windows.Forms.Message ByRef, System.Windows.Forms.MouseButtons, Int32)

at System.Windows.Forms.Control.WndProc(System.Windows.Forms.Message ByRef)

at System.Windows.Forms.ToolStrip.WndProc(System.Windows.Forms.Message ByRef)

at System.Windows.Forms.ToolStripDropDown.WndProc(System.Windows.Forms.Message ByRef)

at System.Windows.Forms.NativeWindow.Callback(IntPtr, Int32, IntPtr, IntPtr)

at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG ByRef)

at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG ByRef)

at System.Windows.Forms.Application+ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr, Int32, Int32)

at System.Windows.Forms.Application+ThreadContext.RunMessageLoopInner(Int32, System.Windows.Forms.ApplicationContext)

at System.Windows.Forms.Application+ThreadContext.RunMessageLoop(Int32, System.Windows.Forms.ApplicationContext)

at Devolutions.RemoteDesktopManager.Program.Main(System.String[])

edited by neal@global411.com on 4/2/2015

If I have 6 or more sessions open and I try to look at the properties for a connection (open or not) the program crashes. The more sessions that are open, the more prone it is to crashing. I've experienced this with 32 and 64 bit versions of the software. This is what I find in the event logs:

Faulting application name: RemoteDesktopManager64.exe, version: 10.1.9.0, time stamp: 0x54d3c14b

Faulting module name: KERNELBASE.dll, version: 6.3.9600.17415, time stamp: 0x54505737

Exception code: 0xc000041d

Fault offset: 0x0000000000008b9c

Faulting process id: 0xcb4

Faulting application start time: 0x01d05e8dd34e10a5

Faulting application path: C:\Program Files (x86)\Devolutions\Remote Desktop Manager\RemoteDesktopManager64.exe

Faulting module path: C:\Windows\system32\KERNELBASE.dll

Report Id: a8e208e3-cb1f-11e4-80bb-0024e87541bf

Faulting package full name:

Faulting package-relative application ID: