Hi Tim,

A bit of a long shot, but a copy that works on a Mac running OS X (Snow Leopard/10.6->) would be the icing on the cake!

There's already CoRD, but it's not quite a good as RD Tabs - it's not got Tabs in the name and therefore doesn't provide tabs as an easy way to select another remote session. The Hotkey is a pain as the Command Key+1 or 2 or session number etc. actually maps to the Windows key so you end up with the Windows key state stuck and have to press it a couple of times to release its state on the remote machine.

There's MS RDC, but it's not tabbed and stuck in the dark ages of the RDP protocol. It crashes too, would you believe it !

There's the Apple offering, but it costs money! and I'm not sure if it does tabs.

The other alternative is VNC, Chicken Of the VNC and Apples built in Screen Sharing based on VNC ... all impossible to use over the internet due to the rubbish VNC protocol or lack of compression by Apple. In fact RealVNC doesn't work to Mac's when you try to reduce the colour depth, but C.O.VNC does although it's still v.slow.

TeamViewer is the only usable app. I've found to remotely administer my parents Mac ... maybe it's their uplink speed, but then I was on their speed before using RDP to work and it was usable. Luckily I'm on 50Mb cable service with 1.65Mb uplink and can work from home just as well as being in the office except for the lack of 24" monitors !!!

Cheers
Mr A

Sorry, there will never be a Mac version. The APIs required by RD Tabs to work is tied to Windows APIs. Your best shot would be to run a VM of Windows and run RD Tabs in that. Not a good solution, but there's no way to port the RD Tabs code to Mac.

What version of dot net does RDTabs depend on? Are there any specific system dll files required for installation and running? I'm trying to get RDTabs to install and run under Wine via WineBottler on SnowLeopard. If I can figure out the dependencies WineBottler should be able to create a portable Application Package to run RDTabs in its own Wine instance.

RD Tabs uses the 2.0 .Net Framework. The next major release (3.0) will be built against whatever the latest is at that time (4.0 is the current latest). The upcoming (heavily delayed) 2.2 version will still be built against 2.0.

As for Windows DLLs, there is a lot of platform invocation for RD Tabs. The biggest one (obviously) is the remote desktop API. The DLL is mstscax.dll. However, I think that is just the ActiveX wrapper for other DLLs (remote desktop is interfaced via COM), so there might be more dependencies deeper than that. User32 is directly invoked a few times, but that should already work in WINE i would think as those are common window functions. GDI32 is invokved for a few things, such as the thumbnails view and remote desktop screen capture. Kernel32 is invoked for the command line mode (sending command line output from a window app is a bit of a hack). Advapi32 is invoked to send remote credentials for the Remote Computer Information module. The "autorepair" mode for RD Tabs uses Kernel32 and user32 too to register a missing RDP COM library. The Remote Computer Information module uses some undocumented functions in wtsapi32.dll and winsta.dll, to make life even more interesting for you. :-)

If you get it to work, that would be awesome. Please update me on your progress!

Whoa, MrAnderson69uk you're hardly "stuck" with CORD. I came to the internets to find a CORD alternative for Windows, actually. It does have tabs, it's just a drawer on Mac which actually provides more info and you can hide it at will.

The windows key mapping is really annoying, though.