Jan 14, 1999
This newsletter / info-pack is generated by Tower Concepts, and is provided to our users and specific members of the net community. Concepts is generated and distributed every few weeks as necessary. Please send comments to firstname.lastname@example.org
What started as a casual question has grown significantly, in frequency and volume! From existing customers, new customers and many potential customers, the question has increasingly been the same... can Razor run on Linux?
The Tower Concepts Team considered the question (request), took the task at hand, and is now proud to answer this question with a resounding, YES...Razor RUNS ON Linux!
Razor 4.1d for Linux can NOW be downloaded from the Tower Concepts Web Site. It's fully functional, fully supported, and available to existing Razor customers or for demonstration. Here's what one user said of our Linux version, "...I've set up Linux at home, went as a dream, installed double boot through LILO to NT and Linux, installed the KDE desktop, and everything works like a charm!"
Download it, run it, and give us your feedback; as always, we're ready to listen.
Razor currently requires a UNIX host to run the Razor License Manager and Database Servers, and supports UNIX, PC and remote clients. Development has been progressing feverishly with the next generation Razor product, the NT Server, that will provide the Razor tool suite functionality strictly in a PC/NT environment!
Our evaluation of the new product and results from customer ALPHA-Test sites have been extremely encouraging! Our engineering team has decided that it's ready to proceed to the next phase of product development, BETA-Test. Here's where we could use your assistance.
Our engineering team is looking for a number of existing Razor customers to assist us with BETA-Testing the NT Server. Some qualifications that we're looking for in our volunteers are testers with:
- familiarity with the current Razor product
- time to set up and use the product
- willingness to provide feedback, positive and negative
and for the site:
- Windows NT/4.0 (service pack 3 or later)
- may only run with NEW databases (not existing ones)
- an endure some new product limited functionality (such as e-mail db access, synchronization, and notification).
We're looking to start BETA-Testing in the very near future. If you would like more information or are willing to volunteer as a NT Server BETA-Test site, please contact us at email@example.com or call us at (315) 363-8000.
All of us here at Tower Concepts hope that the New Year has been treating you well so far (and will continue to do so)! The New Year also serves as a reminder that we are entering the last year of the Twentieth Century, and that this might be a good time to take a moment to review the very pertinent issue concerning the transition to the next century...the Y2K Problem.
It has been mentioned previously in this Newsletter what Tower Concepts' position is on the Y2K issue. We encourage each of our customers to visit the Tower Concepts Web Site to review our Statement.
In part, we do state that Razor is "Millennium Compliant". But as we review our customer records, it appears that a few of you out there are running some very, Very, OLD (and unsupported) versions of Razor!
Tower Concepts cannot guarantee proper Year2000 functionality for Razor unless CUSTOMER ACTION has been taken to upgrade to the appropriate level of Razor software (that is, Razor version 4.0, or later). It is also necessary that the Host Operating System be Year2000 Compliant, since Razor relies on Host Operating System utilities (time-related functions, utilities, and the archival engines, SCCS and RCS). Again, CUSTOMER ACTION is necessary to insure this compliance.
So we urge all Razor Administrators to take a moment to review our Y2K Statement, verify your level of Razor (simply run the command, "razor version"), and to discuss the appropriate Host system compliance with your local System Administrators.
We will continue to use this Newsletter forum as a means to provide reminders to our users to review the Y2K issue and to pass along any tips/advice we come across relating to local system compliance.