Users

All Posts (10)

avatar

a178235

New beta version available

avatar
avatar
avatar
avatar
avatar

RDM 5.8.3.16 worked fine but 5.8.3.19 does not work correctly with PutTY GSSAPI. Under 5.8.3.16 I was not prompted for a password, but under 5.8.3.19 I am. I haven't tried 5.8.3.17/18, but went back to 5.8.3.16 and am not prompted.

Different Icons 3.8.3.10

avatar
avatar
avatar

It appears that the program icon has changed since it looks differenton the taskbar from the previous version, but it still looks the same as theprevious version in the notification area of the taskbar.

Version 5.8 Beta

avatar
avatar
avatar
avatar
avatar

Works great, thanks.

Hi,

The RC2 is now available, I fixed the bug with pinned taskbar in Windows 7 and also the add in group bug.

http://remotedesktopmanager.com/download/Devolutions.RemoteDesktopManager.Bin.5.8.0.10.zip

Thank you all for your help.

edited by a178235 on 7/1/2010

Version 5.8 Beta

avatar
avatar
avatar
avatar
avatar

Works great, thanks.

Hi,

The RC2 is now available, I fixed the bug with pinned taskbar in Windows 7 and also the add in group bug.

http://remotedesktopmanager.com/download/Devolutions.RemoteDesktopManager.Bin.5.8.0.10.zip

Thank you all for your help.

edited by a178235 on 7/1/2010

Version 5.8 Beta

avatar
avatar
avatar
avatar
avatar

Ah, "Command Line" Session Type.

Version 5.8 Beta

avatar
avatar
avatar
avatar
avatar

What do the following additions mean?

- Added support for 64 bits application in command line

- Added support for 64 bits in session events

edited by a178235 on 7/1/2010

64-Bit Version

avatar
avatar
avatar
avatar

Since 64-bit OS and applications are becoming the standard, it would be nice to have a 64-bit version of Remote Desktop Manager. While you could argue that there’s no benefit with a 64-bit version, from my testing I see a 5% to 15% speed increase in 64-bit builds vs. their 32-bit builds, which adds up to a perceivable amount using all 64-bit applications. With Remote Desktop Manager being written in .NET, a 64-bit version is easy, as I have already gotten it to work in 64-bit mode. There are a few things that will need to be done:

First, the 32BIT .NET flag must be set from 1 to 0. Use the CorFlags.exe found in the Microsoft Windows SDK for Windows 7 and .NET Framework 4, http://www.microsoft.com/downloads/details.aspx?familyid=C06B8369-60DD-4B64-A44B-84B371EDE16D&displaylang=en. Execute “corflags RemoteDesktopManager.exe /32BIT-“ and “corflags RemoteDesktopManager.AddOn.dll /32BIT-“.

Microsoft (R) .NET Framework CorFlags Conversion Tool. Version 4.0.30319.1

Copyright (c) Microsoft Corporation. All rights reserved.

Version : v2.0.50727

CLR Header: 2.5

PE : PE32

CorFlags : 1

ILONLY : 1

32BIT : 0

Signed : 0

The second issue is with using an Access, mdb, data source. You will receive the following error:

The current datasource is unavailable.

The ‘Microsoft.Jet.OLEDB.4.0’ provider is not registered on the local machine.

This is because there isn’t a 64-bit version of the Microsoft.Jet.OLEDB.4.0 provider. There is a 64-bit version available in the Microsoft Access Database Engine 2010 Redistributable, http://www.microsoft.com/downloads/details.aspx?familyid=C06B8369-60DD-4B64-A44B-84B371EDE16D&displaylang=en. Using ‘Microsoft.ACE.OLEDB.12.0’ to connect should work, but this would require changing the source code, which obviously I don’t have access to. Using an XML data source works fine.

When running in 64-bit mode, I did have to reenter the installation path of WinSCP one time, but this was a minor issue and probably due to a Wow6432Node issue, but that’s just a guess.

Another minor issue is that the software should be installed in “Program Files” instead of “Program Files (x86)” on a 64-bit version of Windows when the software is native 64-bit.

Hopefully my initial research will be appreciated and these relatively minor changes can be made so that Remote Desktop Manager will be 64-bit.

64-Bit Build

avatar
avatar
avatar

Since the majority of common applications now have x64editions, it would be nice to have a x64 build of Remote Desktop Manager.

Version 5.8 Beta

avatar
avatar
avatar
avatar
avatar

Thank you for fixing the notification icon issue. I also forgot to mention that when Remote Desktop Manager is pinned to the task bar and is running, while it can be minimized, it can’t be restored except via the notification icon area. An application pinned to the taskbar should start one instance of the application and thereafter minimize/restore the application. I’m using Windows 7 x64.

Version 5.8 Beta

avatar
avatar
avatar
avatar
avatar

When using 5.8.0.7, and a few versions previous to that, after exiting the program it leaves a copy of the icon in the Windows 7, I’m using x64, notification area. That’s the list on the bottom right when expanding the <. If I start, exit, start, exit, Remote Desktop Manager, I will have multiple copies of the Remote Desktop Manager icon showing. Hovering over the icons makes them disappear.

1 - 10 of 10 items