Using Dongles for Rainbow Technologies' Sentinel Software

RoyATokeshi
March 26, 2004 4:42 pm

Citrix states in their article: CTX638413

CTX638413 - Using Dongles for Rainbow Technologies' Sentinel Software

This document was published at: http://support.citrix.com/kb/entry.jspa?externalID=CTX638413

Document ID: CTX638413, Created on: Jul 13, 2000, Updated: Apr 23, 2003

Products: Citrix WinFrame 1.8

Legacy dongle applications have always attempted to access the system hardware directly, which prevented their use on WinFrame and Windows NT systems. Rainbow Technologies has recently created an updated Windows NT driver that intercepts the direct hardware access attempts with a virtual device driver. Updating the WinFrame system with the driver allows the use of dongles on Windows NT-based systems.

The following was abstracted from www.rainbow.com/ on 1/27/98.

Sentinel System Driver Information Sheet

Non-retrofit versions of our software interface (P-20.1, Spro-2.1, C-10.x, K-4.2, NS-4.23) normally communicate with the key by using direct I/O communication. Due to the fact that today's operating systems have grown more complicated and tend to use more third party drivers, direct I/O communication has become less reliable.

To alleviate this problem, we created Retrofit Code. To be considered retrofit, your interface code must be the following versions or later: P-22.1,SP-4.1Post C-10.1.1,Post K-4.2, NS-5.0. In most cases, the library files are dated 4/95 or greater for retrofit code. This retrofit code can
communicate to the I/O two ways: 1) directly or 2) through the system drivers. When installed, the
driver provides increased reliability and compatibility. Port contention issues are often solved by simply having these drivers installed.

The only time that it is absolutely necessary to use the system drivers (also called portable
drivers) is when you are using Windows NT. Windows NT has a Hardware Abstraction Layer
(HAL) that intercepts any direct I/O communication. Without the system drivers loaded, the application would not be able to communicate with the key. You may be wondering how Non-retrofit code communicates with the key in Windows NT. After all, it can only perform direct I/O. That is where our RAINPORT drivers come into play.

The RAINPORT drivers intercept the API function calls from the application, and as far as the non-retrofit code is concerned, it is still communicating direct I/O. The RAINPORT drivers in turn send the calls into Windows NT using Windows NT APIs. These Windows NT APIs are what finally allow our calls to get through the HAL.

The latest version of our system drivers is PD-5.33. The latest version of RAINPORT is 2.0.
Both files can be found on the Sentinel System Drivers page on our Website
(www.rainbow.com/) or our BBS at (714) 450-7485 (8,1,N).



Primary links

Custom Search

User login

Who's new

  • Preatercelepe
  • Kxtuzjgv
  • Maitacewwisat
  • abnonsoks
  • themopoty

Who's online

There are currently 0 users and 5 guests online.

KrissysCorner.com RuthSwensonLaw.com CreativeLizardProductions.com

DISCLAIMER:

None of this has anything to do with us, someone else is responsible for the entire thing, and we have no idea who or why. We do not know anything about it. It may be alien life forms for all we know: we haven't a clue. You cannot blame us for anything that may result from your visit. That was entirely your own personal choice, made by you of your own volition, and without our knowledge. We do not, after all, have any control over you and cannot by any stretch of the imagination be expected to accept or acknowledge, be it legally or morally, any accountability for decisions made by you on an independent basis, utilizing your own free will, and without our intervention. We are therefore in no way, shape, or form answerable to anyone for any consequences arising from the aforementioned or indeed any other actions, similar or otherwise, because it was not us that did, or did not do anything. It is not even remotely our fault, and we are in no way prepared or willing to accept any liability, not even slightly, ever. We are, in fact completely and utterly blameless, in that it is definitely not our concern, and no blame can possibly be laid at our doorstep, even if we had one, the possession of which we hereby reserve as being entirely our own free choice. The onus is not on us at all, and furthermore, never has been. The entire matter is wholly beyond our control, and completely out of our hands, each of which are washed scrupulously clean of the whole business. We are not accountable for anything at all, and we hereby categorically deny all responsibility for all that has ever, or will ever happen. Our innocence is therefore wholly beyond doubt and absolutely unimpeachable, and so cannot, under even the remotest or unlikeliest circumstances, be brought into question. By clicking either on a link on this site, clicking on a link that leads to this site, or by arriving at this site by natural or supernatural means, you are in effect accepting responsibility for the fact that it is all entirely your own fault, down to the most miniscule detail, and that you are wholly accountable for whatever outcome may arise as a consequence of the aforementioned action or actions insofar as they were undertaken personally by you on an entirely voluntary basis and without any persuasion, coercion or influence from any party or parties other than yourself. Don't come sniveling to us, we are only figments of your imagination. I also agree that if I am ever with a contributor to this website during mealtimes I agree to pay for any super-sizing of their meal, or at least a nice dessert or one of those foo-foo drinks with an umbrella or a monkey. By admitting to have seen the worthless spineless drivel on this website (also known as content)

I Agree Wholeheartedly and Without Reservation to the above. (Except maybe for that part about the monkey.)

All Your Base Are Belong To Us.

Soylent Green Is People!

Never make a bet with a Sicilian when Death is on the Line!

No. Really, I do agree.