Avian Waves
®
\
Forums
\
RD Tabs
\
RD Tabs General Discussion
\
RD Tabs 2.1.18 - More and more bug fixes
Register
Login
Search
Blog
About
Software
Tools
RD Tabs
Legacy
XS BAP
VSCMap
SCHANNEL ADM Template
XS EDB Limit Changer
RemovableStorageDevice ADM Template
Windows Mobile Classic
Music
Discography
Avian Waves
TCX - All We Can Do
Studio
The Black Room
Keyboards
Rack Synths
Effects Processors
Mixing
Monitoring
Interfaces
Sequencing & Editing
Instruments Plugins
Effects Plugins
Contact
Forums
Blog
About
Software
Tools
RD Tabs
Legacy
XS BAP
VSCMap
SCHANNEL ADM Template
XS EDB Limit Changer
RemovableStorageDevice ADM Template
Windows Mobile Classic
Music
Discography
Avian Waves
TCX - All We Can Do
Studio
The Black Room
Keyboards
Rack Synths
Effects Processors
Mixing
Monitoring
Interfaces
Sequencing & Editing
Instruments Plugins
Effects Plugins
Contact
Forums
Welcome Guest! To enable all features please try to register or login.
×
Avian Waves Forums
Search
Help
×
Avian Waves Forums
RD Tabs
RD Tabs General Discussion
RD Tabs 2.1.18 - More and more bug fixes
RD Tabs 2.1.18 - More and more bug fixes
Previous Topic
Next Topic
Tools
Watch this topic
Print this topic
Atom Feed
RSS Feed
Timothy
100% (Exalted)
Flock Leader
Topic Starter
2008-09-19T11:32:09Z
#1
My hopes were dashed that 2.1.17 would be the last in the 2.1.x codebase when several new bugs were discovered. 🙂 Maybe this will be the last 2.1.x version before 2.2 -- or am I just jinxing the whole thing?
Download links...
x86 MSI:
http://www.avianwaves.co...rdtabs/rdtabs_2.1.18.msi
x86 Zip:
http://www.avianwaves.co...rdtabs/rdtabs_2.1.18.zip
x64 MSI:
http://www.avianwaves.co...tabs/rdtabs64_2.1.18.msi
x64 Zip:
http://www.avianwaves.co...tabs/rdtabs64_2.1.18.zip
Changelog...
- Changed redial behavior slightly. Previously, it would only redial if the connection returned an error. Now, redial happens anytime the connection terminates while connecting. Once a connection is established, it will no longer redial. The reason for the change is primarily because Server 2008 tends to return error code 3 (user cancelled remote session) when it is not ready to receive remote connections because it is shutting down. So if you connect with redial while a server is shutting down, wanting it to just wait until the server is ready for you automatically, you were out of luck! The second reason is that it didn't really make sense to stop redialing on a non-error result like how it does for auto-reconnect on network issues. The user most likely wants RD Tabs to just keep trying until the server answers, regardless of the error code. Whereas with the network issues, you probably don't want it to reconnect after you intentionally disconnect.
- Changed the redial label as a result of the above. It now says "Redial on connection failure."
- The disconnection code mentioned above has been changed to say "Session was disconnected remotely by user or computer" since Server 2008 now uses it to inform a remote desktop client that it is not ready to receive connections. (In Server 2003 and older, you would only see this error if you disconnected intentionally.)
- Disconnection code 2825 was added. This value is returned when the remote computer requires NLA but NLA is not enabled. Brief instructions are also given on how to enable NLA in RD Tabs for a session.
- Fixed a bug where if you start RD Tabs from one command line and then issue commands from another command line after closing the first one, RD Tabs would no longer respond to commands from the command line. Additionally, you would see an exception in the View Console Output window under Help.
- Added a more detailed exception handler in the LightWeight StatusBar. There's some arithmetic overflow getting reported on a few computers out there. I'm trying to figure out why. I can't seem to find a common cause.
- Added an option to the error reporter that allows you to include your email address if you want feedback on the error or if I have additional questions about what you were doing that caused an error. This is a completely OPTIONAL section! Feel free to leave it out.
- Fixed a bug where if you set a custom screen resolution higher than Pre-RDP 6.0 maximum values, saved it as a favorite, and then tried to edit the favorite, RD Tabs would crash because the value would exceed the .Net bounds check for the NumericUpDown control. RD Tabs now sets the maximum bounds to RDP 6.0 value when you are in the favorites editor. However, if you are using a pre-RDP 6.0 control registration (which is not a default RD Tabs installation at this point), RD Tabs will use the highest value it can on connection, if the maximum value is beyond what the control is capable of displaying.
Edited by user
2008-09-25T18:16:24Z
|
Reason: Not specified
View All Posts by User
Atom Feed
Rss Feed
Similar Topics
RD Tabs 2.1.22 - Even more bug fixes...
(
RD Tabs General Discussion
) by
Timothy
2009-09-16T13:13:53Z
RD Tabs 2.1.21 - More bug fixes...
(
RD Tabs General Discussion
) by
Timothy
2009-04-14T07:59:21Z
RD Tabs 2.1.12 - More bug fixes thanks to error submissions!
(
RD Tabs General Discussion
) by
Timothy
2008-06-25T10:29:15Z
RD Tabs 1.1.2 just released (more bug fixes!)
(
RD Tabs General Discussion
) by
Timothy
2007-02-07T05:41:33Z
RD Tabs 2.1.25 - Better NLA (now with SSO) Plus More Bug Fixes
(
RD Tabs General Discussion
) by
Timothy
2012-05-17T14:59:53Z
Users browsing this topic
Avian Waves Forums
RD Tabs
RD Tabs General Discussion
RD Tabs 2.1.18 - More and more bug fixes
full film