DoubleVision for UNIX/Linux SCO UNIXWARE 7.x Release 3.40.00 Last Update: June 13, 2003 RELEASE NOTES ================================================================== THE FOLLOWING INFORMATION IS VERY IMPORTANT. SOME OF THIS INFORMATION SUPERSEDES THE INFORMATION CONTAINED IN THE USER'S GUIDE. IT IS HIGHLY RECOMMENDED THAT YOU READ THESE RELEASE NOTES COMPLETELY BEFORE INSTALLING OR USING DOUBLEVISION. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR: ***************** ******************** SCO Unixware 7.X PLATFORM ****************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.40.00 BUILD #1 ****** ****************************************************************** [SCO UW] Cummulative bug fixes applied to latest for Unixware 7.X. ------------------------------------------------------------------ DoubleVision 3.40.00 for Unixware 7.1/7.0 contains all the cummulative bug fixes developed on other platforms as well as fixes developed from our internal bug list. ******************* THE FOLLOWING NOTES ARE FOR: ***************** ******************** SCO Unixware 7.X PLATFORM ****************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.40.00 BUILD #2 ****** ****************************************************************** [SCO UW] Installer modification. ------------------------------------------------------------------- DoubleVision 3.40.00 build #2 has added installer support for a demonstration activation key web page. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** ******************** SCO UNIX/MPX 3.2.5.06 *********************** ***** THE FOLLOWING NOTES ARE FOR RELEASE 3.40.00 BUILD #20 ****** ****************************************************************** [SCO] Removed DoubleVision device driver debug message. ------------------------------------------------------------------- DoubleVision release 3.40.00 build #20 has the benign driver debug message 'MAXSLEEPTICKS=25' removed. This variable debug message appeared on tty1 and the system log whenever a tty is viewed. This message is not a representation of a problem. The debug message was mistakenly left in the production release. The debug message is no longer present in build #20. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** ***************** SCO UNIX/MPX 3.2.4.X/3.2.5.0-5 ***************** ***** THE FOLLOWING NOTES ARE FOR RELEASE 3.40.00 BUILD #19 ****** ****************************************************************** [SCO] Installer modification. ------------------------------------------------------------------- DoubleVision 3.40.00 build #19 has added installer support for a demonstration activation key web page. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** ********************* SCO UNIX/MPX /3.2.5.0-5 ******************** ***** THE FOLLOWING NOTES ARE FOR RELEASE 3.40.00 BUILD #18 ****** ****************************************************************** [SCO] Driver SLEEP/WAKEUP enhancements. ------------------------------------------------------------------- DoubleVision 3.40.00 build #18 contains enahcments to our SLEEP and WAKEUP subsystem. Enhancements were made to minimize server time-outs and -4 server protocol errors. [SCO] User logs in and their login and password are echoed. ------------------------------------------------------------------- DoubleVision 3.40.00 build #18 solves a condition where a preattached user logs in and their login id and password are echoed to the screen. The nature of the problem really deals with restoring the original tty settings when our process, dvscreen, is terminated with a kill -9. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** *************************** AIX 5.1/5.2 ************************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.40.10 BUILD #7 ****** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.60.00 BUILD #7 ****** ****************************************************************** [AIX] DoubleVision support for AIX 5.2. ------------------------------------------------------------------ DoubleVision release 3.60.00 build #7 supports AIX 5.2 UP/MP 32 bit and 64 bit. [AIX] DoubleVision for AIX 5.1 64 bit is out of BETA. ------------------------------------------------------------------ DoubleVision release 3.40.10 build #7 is out of BETA for AIX 5.1 64 bit. [AIX] KNOWN ISSUES: DoubleVision for AIX 5.1/5.2 64 bit. ------------------------------------------------------------------ On AIX 5.1 or 5.2 64 bit there is a known issue with the initial drawing of the 'Chat' box on the remote and host. If you press "Ctrl r" the chat boxes will be displayed fully. This issue will be addressed in a future release. On AIX 5.1 or 5.2 64 bit there is a known issue with 'scrolling' instant replay. The playback appears to be incomplete and choppy. This issue did not get resolved in the time frames allowed. We recommend using the sequential instant replay. Use the 'n'(next) and 'b'(back) keys to scroll through your replayed session. This issue will be resolved in a future release. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR: ***************** ****************** Linux Intel 2.4/XXPLATFORM ******************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.60.00 BUILD #31 ***** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.50.00 BUILD #31 ***** ****************************************************************** [LINUX INTEL] DoubleVision support for RedHat 9.0. ------------------------------------------------------------------- DoubleVision 3.60.00 build #31 supports RedHat 9.0 running kernel version 2.4.20-6 or 2.4.20-13.9. [LINUX INTEL] New kernel support for RedHat 7.X and 8.0. ------------------------------------------------------------------- DoubleVision 3.50.00 build #31 has added driver support for the latest RedHat kernel: 2.4.20-13.7 (For RedHat version 7.X) 2.4.20-13.8 (For RedHat version 8.0) ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** **************** Solaris SPARC 2.6/2.7/2.8 PLATFORM ************** ***** THE FOLLOWING NOTES ARE FOR RELEASE 3.30.00 BUILD #12 ****** ****************************************************************** [SOLARIS] Installer modification. ------------------------------------------------------------------- DoubleVision 3.30.00 build #12 has added installer support for a demonstration activation key web page. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** ************** AIX 3.2.X/4.1.X/4.2.X/4.3.X/5.1 ******************* ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.40.10 BUILD #6 ****** ****************************************************************** [AIX] Installer modification. ------------------------------------------------------------------- DoubleVision 3.40.10 build #6 has added installer support for a demonstration activation key web page. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR: ***************** ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR: ***************** ******** HP-UX 11.11 Series 800/700 32 and 64 bit - UP/MP ******** **** THE FOLLOWING NOTES ARE FOR RELEASE 3.30.00 BUILD #13 ******* ******** HP-UX 11.00 Series 800/700 32 and 64 bit - UP/MP ******** **** THE FOLLOWING NOTES ARE FOR RELEASE 3.30.00 BUILD #13 ******* ******** HP-UX 10.20 Series 800/700 32 and 64 bit - UP/MP ******** **** THE FOLLOWING NOTES ARE FOR RELEASE 3.30.00 BUILD #13 ******* ****************************************************************** [HPUX] Installer modification. ------------------------------------------------------------------- DoubleVision 3.30.00 build #12 has added installer support for a demonstration activation key web page. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR: ***************** ****************** Linux Intel 2.4/XXPLATFORM ******************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.50.00 BUILD #30 ***** ****************************************************************** [LINUX INTEL] Installer modification. ------------------------------------------------------------------- DoubleVision 3.50.00 build #30 has added installer support for a demonstration activation key web page. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR: ***************** ****************** Linux Intel 2.4/XXPLATFORM ******************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.50.00 BUILD #29 ***** ****************************************************************** [LINUX INTEL] Suse 8.2 ------------------------------------------------------------------- DoubleVision 3.50.00 build #29 supports Suse version 8.2. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** ************** AIX 3.2.X/4.1.X/4.2.X/4.3.X/5.1 ******************* ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.40.00 BUILD #5 ****** ****************************************************************** [AIX 5.1] Port completed to AIX 5.1 UP/MP 64 bit processors. ------------------------------------------------------------------ DoubleVision 3.40.00 build #5 adds support for AIX 5.1 on 64 bit processors. DoubleVision provides 64 bit binary and driver support for AIX 5.1. Version 3.40.00 build #5 is a BETA release for the 64 bit version as this is the first release of DoubleVision that supports the 64 bit platform on AIX 5. The new distribution will automatically detect the current version of AIX and install the proper binaries. Support for AIX 3.2, and 4.X are also available from within the same distribution. [AIX 5.1] Known 64 bit security breach present in 3.40.00 build #5. ------------------------------------------------------------------ DoubleVision 3.40.00 build #5 BETA has a known security bug on 64 bit platforms. If a non-root host user performs an 'su' which grants them super user access, DoubleVision will NOT detect this as a security breach and will continue to allow a non-root user to view the super session. This issue should be resolved in the post BETA release of DoubleVision. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR: ***************** ****************** Linux Intel 2.4/XXPLATFORM ******************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.50.00 BUILD #28 ***** ****************************************************************** [LINUX INTEL] DoubleVision causes a kernel Oops. ------------------------------------------------------------------- DoubleVision 3.50.00 build #28 resolves a driver and kernel incompatibility. Research has shown that the internal timing frequency, (HZ), of the kernel is different based on the kernel hardware platform. The i686 and i586 kernels contain a default value different from the older hardware platforms. For backward compatibility reasons we have always compiled our drivers against an i386 kernel. This has presented no problems until recently. The later kernel versions have deviated from the default value of '100'. The timing differences can cause a kernel Oops when running DoubleVision. We are unable to obtain the running kernel HZ value so we have made this option configurable in our /usr/lib/dv/defaults configuration file. The following default file variable contains the value DoubleVision will use as the HZ value. If you are running an i386 or i486 kernel you should change the default value of '512' to '100'. LINUX_KERNEL_HZ=512 Any changes to the LINUX_KERNEL_HZ variable require a system reboot to re-load our driver. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR: ***************** ****************** Linux Intel 2.4/XXPLATFORM ******************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.50.00 BUILD #27 ***** ****************************************************************** [LINUX INTEL] -17 Cannot open Screen Server channel ------------------------------------------------------------------- DoubleVision 3.50.00 build #27 solve the following reported viewing problem on specific linux kernels. Customers running a Linux system and one of the following kernels: 2.4.18-17.7.x 2.4.18-18.7.x 2.4.18-19.7.x 2.4.18-24.7.x 2.4.18-26.7.x may experience a "-17 Cannot open Screen Server channel" error message upon viewing. Some users may experience a kernel OOPs during their viewing session instead of the -17 viewing error. We have determined the error message originates at our kernel driver level. We uncovered differences in the downloaded kernel RPM from RedHat and the kernel build internally using the downloaded kernel source. Specifically, some kernel build options were different. The resulting effect was kernel data structures differences. This issue has been addressed by using the same configuration options as the downloaded RPM kernel. This should keep the kernel build options the same for the pre-build kernel RPM from RedHat and the kernel built by Tridia using the kernel source code. This release contains no changes to our source code. We have recompiled the kernels listed above using the kernel RPM config files. Lastly, we recompiled our driver against the new kernel builds. We have changed our development process in that we will always use the kernel configuration produced by the pre-built kernel RPM from RedHat. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR: ***************** ****************** Linux Intel 2.4/XXPLATFORM ******************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.50.00 BUILD #26 ***** ****************************************************************** [LINUX INTEL] New RedHat kernel support ------------------------------------------------------------------- DoubleVision 3.50.00 build #26 now supports RedHat kernel version 2.4.18-24.7.x and version 2.4.18-26.7.x. [LINUX INTEL] KNOWN ISSUE ------------------------------------------------------------------- Customers running a multiprocessor system and one of the following kernels: 2.4.18-17.7.x 2.4.18-18.7.x 2.4.18-19.7.x 2.4.18-24.7.x 2.4.18-26.7.x may experience a "-17 Cannot open Screen Server channel" error message upon viewing. We have determined the error message originates at our lower driver level. We are trying to solve this issue now. A new release of DoubleVision will be posted when we resolve this problem. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR: ***************** ****************** Linux Intel 2.4/XXPLATFORM ******************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.50.00 BUILD #25 ***** ****************************************************************** [LINUX INTEL] -4 Server Open Failed ------------------------------------------------------------------- DoubleVision 3.50.00 build #25 solves a bug introduced in build #24 where a "-4 Server open failed" message would appear upon viewing a virtual console screen or dumb terminal. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR: ***************** ****************** Linux Intel 2.4/XXPLATFORM ******************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.50.00 BUILD #24 ***** ****************************************************************** [LINUX INTEL] DoubleVision re-port to RedHat version 8.0 ------------------------------------------------------------------- DoubleVision 3.50.00 build #24 is a re-port to RedHat 8.0. Our previous release of DoubleVision did not work properly on some 8.0 systems. Problem symptoms range from DoubleVision viewing problems to a kernel OOPs. We did not have these problems on our own 8.0 system but they were reported by our customers. [LINUX INTEL] DoubleVision driver re-port. ------------------------------------------------------------------- DoubleVision 3.50.00 build #24 contains newly compiled DoubleVision drivers supporting kernels 2.4.18-18.7.x and 2.4.18-19.7.x. DoubleVision problems have been experienced on RedHat systems with either of the above kernels. These kernels were built using a later compiler version. We re-ported our driver using the later compiler version. Documentation found states that gcc 2.x compiled modules may not behave correctly with kernels compiled with 3.x of the gcc compilers. Our drivers are now compiled using the 3.x version of the compilers. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR: ***************** ****************** Linux Intel 2.4/XXPLATFORM ******************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.50.00 BUILD #23 ***** ****************************************************************** [LINUX INTEL] Support for RedHat version 8.0. ------------------------------------------------------------------- DoubleVision 3.50.00 build #23 supports RedHat 8.0 running kernel version 2.4.18-14. [LINUX INTEL] Support for 2.4.18-17.7.x, and 2.4.18-18.7.x kernels. ------------------------------------------------------------------- DoubleVision 3.50.00 build #23 contains driver support for linux kernel versions 2.4.18-17.7.x, and 2.4.18-18.7.x. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR: ***************** ****************** Linux Intel 2.4/XXPLATFORM ******************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.40.00 BUILD #22 ***** ****************************************************************** [LINUX INTEL] Support for 2.4.9-34, 2.4.18-5, and 2.4.18-10 kernels. ------------------------------------------------------------------- DoubleVision 3.40.00 build #22 contains driver support for linux kernel versions 2.4.9-34, 2.4.18-5, and 2.4.18-10. [LINUX INTEL] Driver enhancements ------------------------------------------------------------------- DoubleVision release 3.40.00 build #22 contains enhancements to the driver sleep and wakeup mechanisms that solve a driver disconnect problem. The driver was timing out prematurely resulting in a server protocol error. The enhancements has been applied to all supported 2.4.XX kernel versions. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR: ***************** ****************** Linux Intel 2.4/XXPLATFORM ******************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.40.00 BUILD #21 ***** ****************************************************************** [LINUX INTEL] Random server protocol errors on SuSE 8.0. ------------------------------------------------------------------- While viewing a user you may be disonnected with a "server protocol error". The DoubleVision error log, /usr/adm/DVLOG, contains a "Driver severed connection!" error message. The disconnect can occur while processing a lot of i/o. The driver is timing out prematurely. This problem appears to be specific to SuSE 8.0. DoubleVision release 3.40.00 build #21 contains enhancements to the driver sleep and wakeup mechanisms that solve the disconnect problem. The enhancements have only been applied to kernel version 2.4.18-4GB at this time. This enhancement will be applied to the remaining supported 2.4.XX kernels in build #22. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** ************************* AIX 4.3.X ****************************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.30.10 BUILD #4 ****** ****************************************************************** [AIX 4.3.X] Unable to open Chat window! ------------------------------------------------------------------ DoubleVision release 3.30.10 build #4 solves a condition that would cause a chat window open failure. The error message text: "Unable to open Chat window" would appear when invoking chat through the DoubleVision "Terminal" or with the hot keys. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** *********************** AIX 4.3.X/5.1 **************************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.40.10 BUILD #3 ****** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.30.10 BUILD #3 ****** ****************************************************************** [AIX 4.3.X/5.1] Solved streams putbq problem. ------------------------------------------------------------------ Repaired problem where under AIX 4.3.3/5.1 if one places a high priority message BACK onto a stream queue that could later lead to streams flow control problems. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR: ***************** *************** Linux Intel 2.2/XX 2.4/XXPLATFORM **************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.40.00 BUILD #20 ***** ****************************************************************** [LINUX INTEL] DoubleVision support for RedHat 7.3. ------------------------------------------------------------------- DoubleVision 3.40.00 build #20 contains added support for RedHat 7.3. [LINUX INTEL] DoubleVision support for RedHat Advanced server 7.2 ------------------------------------------------------------------- DoubleVision 3.40.00 build #20 contains added support for RedHat Advanced Server 7.2 kernel version 2.4.9-e.3. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** ***************** SCO UNIX/MPX 3.2.4.X/3.2.5.0-5 ***************** ***** THE FOLLOWING NOTES ARE FOR RELEASE 3.40.00 BUILD #17 ****** ****************************************************************** [SCO] Trojan Horse Error when logging off a pseudo device using DoubleVision. ------------------------------------------------------------------- DoubleVision 3.40.00 build #17 solves the problem where numerous errors would be reported when you log a user off the system when they are on a pseudo tty. The new DoubleVision release will not report any errors to the user interface. [SCO] Server protocol errors when viewing a host tty that is running heavy I/O. ------------------------------------------------------------------- DoubleVision 3.40.00 build #17 solves two heavy I/O conditions both resulting in a Server protocol error and a Trojan Horse. The condition is when a user views a host tty then runs an application that generates heavy I/O on the host session. DoubleVision would disconnect from the host tty after a considerable amount of time resulting in errors being generated. The other condition is viewing a host tty that already has heavy I/O running. On prior releases of DoubleVision, problems were encountered that caused remote control to freeze both the remote and host terminals for several seconds. We have solved both of these issues in the new release of DoubleVision. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR: ***************** ******************* Linux Intel 2.4/XXPLATFORM ******************* ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.35.00 BUILD #19 ***** ****************************************************************** [LINUX INTEL] Support for Linux kernel version 2.4.17 ------------------------------------------------------------------- DoubleVision 3.35.00 build #19 contains driver support for linux kernel version 2.4.17. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** ********************** SCO UNIX/MPX 3.2.5.06 ********************* ***** THE FOLLOWING NOTES ARE FOR RELEASE 3.40.00 BUILD #16 ****** ****************************************************************** [SCO] Official binary and driver support for SCO 3.2.5.06. ------------------------------------------------------------------- DoubleVision 3.40.00 build #16 contains binary and driver support for the specific version of SCO 3.2.5.06. We decided to port directly to SCO 3.2.5.06 to add further stability on that release of the operating system. [SCO] Trojan Horse Error when logging off a pseudo device using DoubleVision. ------------------------------------------------------------------- DoubleVision 3.40.00 build #16 solves the problem where numerous errors would be reported when you log a user off the system when they are on a pseudo tty. The new DoubleVision release will not report any errors to the user interface. This fix applies to SCO 3.2.5.06 only. [SCO] Server protocol errors when viewing a host tty that is running heavy I/O. ------------------------------------------------------------------- DoubleVision 3.40.00 build #16 solves two heavy I/O conditions both resulting in a Server protocol error and a Trojan Horse. The condition is when a user views a host tty then runs an application that generates heavy I/O on the host session. DoubleVision would disconnect from the host tty after a considerable amount of time resulting in errors being generated. The other condition is viewing a host tty that already has heavy I/O running. On prior releases of DoubleVision, problems were encountered that caused remote control to freeze both the remote and host terminals for several seconds. We have solved both of these issues in the new release of DoubleVision. These fixes apply to SCO 3.2.5.06 only. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR: ***************** ******************* Linux Intel 2.4/XXPLATFORM ******************* ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.35.00 BUILD #18 ***** ****************************************************************** [LINUX INTEL] Installation fails when run on a linux system with kernel version 2.4.9-31 and 2.4.18. ------------------------------------------------------------------- DoubleVision 3.35.00 build #18 solves a bug in the installation script that fatal exists when run against kernel version 2.4.9-31 and 2.4.18. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR: ***************** ******************* Linux Intel 2.4/XXPLATFORM ******************* ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.35.00 BUILD #17 ***** ****************************************************************** [LINUX INTEL] Support for kernel version 2.4.9-31 and 2.4.18. ------------------------------------------------------------------- DoubleVision 3.35.00 build #17 contains added support for linux kernel version 2.4.9-31 and 2.4.18. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** ************** AIX 3.2.X/4.1.X/4.2.X/4.3.X/5.1 ******************* ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.40.00 BUILD #2 ****** ****************************************************************** [AIX 3.X/4.X] "-906 Cannot open remote control device" ------------------------------------------------------------------ Repaired problem introduced when support was added for AIX 5.1 where the program 'cfgrcon' would not be properly installed on AIX 3.X - 4.X systems. It is possible under these operating systems not to be able to load the DoubleVision driver because of a binary version mismatch. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR: ***************** *************** Linux Intel 2.2/XX 2.4/XXPLATFORM **************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.35.00 BUILD #16 ***** ****************************************************************** [LINUX INTEL] DoubleVision support for Caldera 3.1. ------------------------------------------------------------------- DoubleVision 3.35.00 build #16 contains added support for Caldera 3.1. [LINUX INTEL] Special notice for Caldera 2.4 and 3.1 systems. ------------------------------------------------------------------- The command line virtual console screens will not be displayed on the DoubleVision interface tty list until a user logs in. At that time the virtual console will appear in the tty list. If you wish to attach to a command line virtual console that is AT LOGIN do the following. Select the "Terminal" drop down menu. Select the "Advanced" menu item. Select the "New" option. Enter in the virtual console device name you wish to view. Example /dev/tty1. The device will should be displayed on the list. Simply view it and log in. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR: ***************** *************** Linux Intel 2.2/XX 2.4/XXPLATFORM **************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.35.00 BUILD #15 ***** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.30.00 BUILD #15 ***** ****************************************************************** [LINUX INTEL] DoubleVision support for RedHat 7.2. ------------------------------------------------------------------- DoubleVision 3.35.00 build #15 contains added support for RedHat 7.2. [LINUX INTEL] DoubleVision support for RedHat kernel 2.4.9-21. ------------------------------------------------------------------- DoubleVision 3.35.00 build #15 supports the RedHat update kernel version 2.4.9-21. [LINUX INTEL] DoubleVision support for RedHat kernel 2.4.9-12. ------------------------------------------------------------------- DoubleVision 3.35.00 build #15 supports the RedHat update kernel version 2.4.9-12. [LINUX INTEL] DoubleVision support for Caldera 2.4. ------------------------------------------------------------------- DoubleVision 3.30.00 build #15 now support the Caldera 2.4 kernel. Although we supported the 2.2.14 kernel in the past for Caldera 2.3 the driver would not load due to some module version symbol differences. This issue has been resolved for build #15. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** ************** AIX 3.2.X/4.1.X/4.2.X/4.3.X/5.1 ******************* ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.40.00 BUILD #1 ****** ****************************************************************** [AIX 5.1] Port completed to AIX 5.1 UP/MP 32 bit processors. ------------------------------------------------------------------ DoubleVision now supports AIX 5.1 on 32 bit processors. The new distribution will automatically detect the current version of AIX and install the proper binaries. Support for AIX 3.2, and 4.X are also available from within the same distribution. Support for 64 bit processor systems is comming soon! ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR: ***************** ******************* Linux Intel 2.2/XX PLATFORM ****************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.35.00 BUILD #14 ***** ****************************************************************** [LINUX INTEL] Server protocol error while viewing a host terminal. ------------------------------------------------------------------- DoubleVision 3.35.00 build #14 solves the Server protocol error while viewing a host session running heavy i/o. Under certain circumstances, a remote user may receive the Server protocol error followed by the -8 Trojan Horse error. In most cases, the host terminal is running an application that is generating heavy i/o. This issue has been resolved. [LINUX INTEL] Added SuSE support. ------------------------------------------------------------------- DoubleVision 3.35.00 build #14 now supports Suse's linux operating system versions 7.3 and 6.4. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** ******************* SCO UNIX/MPX 3.2.4.X/3.2.5.X ***************** ***** THE FOLLOWING NOTES ARE FOR RELEASE 3.30.00 BUILD #15 ****** ****************************************************************** [SCO] Entering keystrokes upon attaching to a host session may cause the host user to log out. ------------------------------------------------------------------ DoubleVision 3.30.00 build #15 solves a host log out issue. Under certain circumstances a host user may be exited or logged out of the system when a user attaches to them and enters keystrokes. This issue has been resolved on SCO 3.2.5.X systems. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR: ***************** ******** HP-UX 11.00 Series 800/700 32 and 64 bit - UP/MP ******** **** THE FOLLOWING NOTES ARE FOR RELEASE 3.30.00 BUILD #12 ******* ****************************************************************** [HPUX] Connecting to the wrong host device when attaching via the command line. ------------------------------------------------------------------- DoubleVision 3.30.00 build #12 solves a problem found only when connecting to a host terminal on the command line or direct connect. The pattern matching scheme used would attach a device with the same base name even if the device name was not the intended target. This issue has been resolved for HP-UX 11.00 32/64 bit. We will port this fix to our other supported HP-UX operating system versions in the near future. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR: ***************** ******************* Linux Intel 2.2/XX PLATFORM ****************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.35.00 BUILD #13 ***** ****************************************************************** [LINUX INTEL] A system lockup or kernel panic. ------------------------------------------------------------------- DoubleVision 3.35.00 build #13 solves a problem where using DoubleVision 3.35.00 build #12 on a RedHat 7.1 MP system may cause the system to lockup or the kernel to panic. We have solved a problem in our driver SLEEP/WAKEUP locking mechanism that could cause this behavior. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR: ***************** ******************* Linux Intel 2.2/XX PLATFORM ****************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.35.00 BUILD #12 ***** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.30.00 BUILD #12 ***** ****************************************************************** [LINUX INTEL] Support for RedHat version 7.1. ------------------------------------------------------------------- DoubleVision release 3.35.00 build #12 supports RedHat's linux version 7.1. This is the first support of the 2.4.X linux kernel. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** ************** Solaris SPARC 2.7 32 BIT PLATFORM ***************** ***** THE FOLLOWING NOTES ARE FOR RELEASE 3.30.00 BUILD #11 ****** ****************************************************************** [SOLARIS] Hanging up the host session when the remote user enters keystrokes. ------------------------------------------------------------------ A remote user runs DoubleVision and views a host terminal. When the remote user enters the first keystroke an error is received "Server protocol error" and the host session is closed. This has been solved in DoubleVision 3.30.00 build #11. The fix is only available for Solaris 2.7 32 bit. This fix will be ported to other Solaris versions in the near future. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR: ***************** ******************* Linux Intel 2.2/XX PLATFORM ****************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.30.00 BUILD #11 ***** ****************************************************************** [LINUX INTEL] Added support for kernel version 2.2.14 that supports 2 GB maximum memory. ------------------------------------------------------------------- Running the kernel 2.2.14 with module versioning support and the "2GB" Maximum Physical Memory defined may generate the following error when executing DoubleVision "-906 Cannot open remote control device" Caldera eServer 2.3 has the "2GB" Maximum Physical Memory defined by default which would cause a failure when loading our driver. This problem has been resolved in DoubleVision 3.30.00 build #11. [LINUX INTEL] Added support for kernel version 2.2.19. ------------------------------------------------------------------- DoubleVision release 3.30.00 build #11 contains support for the 2.2.19 kernel. ******************* THE FOLLOWING NOTES ARE FOR: ***************** ******************* Linux Intel 2.2/XX PLATFORM ****************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.30.00 BUILD #10 ***** ****************************************************************** [LINUX INTEL] -903: (FATAL ERROR) Program aborted, ioctl #3 failed. Errno = 4 ------------------------------------------------------------------- On prior versions of DoubleVision you may receive the error above if you attempt to "Direct Connect" to a terminal via the command line. This error seems to occur only when you bypass the DoubleVision user interface by connecting directly. Ex. "dv /dev/tty15 -t linux" This issue does not exist if you connect to a host terminal through the DoubleVision user interface. DoubleVision version 3.30.00 build#10 solves this issue. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** ******************* SCO UNIX/MPX 3.2.4.X/3.2.5.X ***************** ***** THE FOLLOWING NOTES ARE FOR RELEASE 3.30.00 BUILD #14 ****** ****************************************************************** [SCO] Unable to view devices with minor number over 255. ------------------------------------------------------------------ DoubleVision 3.30.00 build #14 solves a problem viewing a terminal that has a minor number greater than 255. The problem may manifest itself with the remote user attaching to the host device successfully but not seeing the host screen image. We have solved this issue by improving our device number mapping sub-system. This enhancement will not impact most users. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** ******************* SCO UNIX/MPX 3.2.4.X/3.2.5.X ***************** ***** THE FOLLOWING NOTES ARE FOR RELEASE 3.30.00 BUILD #13 ****** ****************************************************************** [SCO] Enhancements to the Digiboard entry trigger. ------------------------------------------------------------------ DoubleVision 3.30.00 build #13 contains an enhanced Digiboard entry trigger. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** **************** Solaris Intel 2.6/2.7/2.8 PLATFORM ************** ***** THE FOLLOWING NOTES ARE FOR RELEASE 3.30.00 BUILD #9 ****** ****************************************************************** [SOLARIS x86] Bug fixes and enhancements to DoubleVision removal scripts. ------------------------------------------------------------------ DoubleVision 3.30.00 build #9 contains bug fixes and enhancements to the product removal scripts. We corrected an incorrect environment variable path used to remove our loadable module from the system. Some enhancements were made that allow the removal script to unload our "rcsrv" module from the kernel exclusively. The changes in this build are dedicated to DoubleVision's removal only. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** ************** Solaris SPARC 2.6/2.7 32 BIT PLATFORM ************* ***** THE FOLLOWING NOTES ARE FOR RELEASE 3.30.00 BUILD #10 ****** ****************************************************************** [SOLARIS] Display buffering problem upon viewing a host terminal. ------------------------------------------------------------------ The problem manifests itself by the remote terminal not displaying the entire screen of the host terminal. If the remote user presses a key the display begins to catch up and be correct. From a low level perspective, the problem is due to a bug in the operating system "poll" system call. We have worked around the operating system bug. This issue does not exist on Solaris Sparc versions 2.7 64 bit and 2.8 32/64 bit. DoubleVision 3.30.00 build #10 solves display buffering problem. ******************* THE FOLLOWING NOTES ARE FOR: ***************** ******************* Linux Intel 2.2/XX PLATFORM ****************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.30.00 BUILD #9 ****** ****************************************************************** [LINUX INTEL] Support added for 'restartable' read system calls. ------------------------------------------------------------------- DoubleVision 3.30.00 build #9 has added support for restarting read system calls that have been interrupted by a signal. This modification is Linux specific. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR: ***************** ******** HP-UX 11.11 Series 800/700 32 and 64 bit - UP/MP ******** **** THE FOLLOWING NOTES ARE FOR RELEASE 3.30.00 BUILD #11 ******* ******** HP-UX 11.00 Series 800/700 32 and 64 bit - UP/MP ******** **** THE FOLLOWING NOTES ARE FOR RELEASE 3.30.00 BUILD #11 ******* ******** HP-UX 10.20 Series 800/700 32 and 64 bit - UP/MP ******** **** THE FOLLOWING NOTES ARE FOR RELEASE 3.30.00 BUILD #11 ******* ****************************************************************** [HPUX] Unable to view dumb terminals. ------------------------------------------------------------------- This DoubleVision release contains timing enhancements that allow the viewing of dumb terminals. Under certain conditions you may experience errors upon viewing a dumb terminal. The most common error message is: -4 Server protocol error occured! DoubleVision 3.30.00 build #11 for HP-UX 10.20, 11.00 and 11.11 solves this issue. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR: ***************** ******************* Linux Intel 2.2/XX PLATFORM ****************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.30.00 BUILD #8 ****** ****************************************************************** [LINUX INTEL] New kernel support added. ------------------------------------------------------------------- DoubleVision 3.30.00 build #8 has added support for kernel versions 2.2.17-14 and 2.2.18. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** ******** Solaris SPARC 2.6/2.7/2.8 32/64 BIT PLATFORM ************ ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.30.00 BUILD #9 ****** ****************************************************************** [SOLARIS] Cummulative bug fixes applied to latest for Solaris SPARC. ------------------------------------------------------------------ DoubleVision 3.30.00 for Solaris SPARC contains all the cummulative bug fixes developed on other platforms as well as fixes developed from our internal bug list. [SOLARIS] Recorded session playback problem solved. ------------------------------------------------------------------ DoubleVision 3.30.00 Build #9 solves a recorded session problem. Under certain conditions the recording of a host session may stop. The recording file will quit growing in size. If you attempt to playback the recorded session the following error is displayed: "No screen activity recorded" The cause of this error is an improperly formatted recording file. Format corruption has been resolved in this new build. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR: ***************** ******************* Linux Intel 2.2/XX PLATFORM ****************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.30.00 BUILD #7 ****** ****************************************************************** [LINUX INTEL] Cummulative bug fixes applied to latest for Intel Linux. ------------------------------------------------------------------ DoubleVision 3.30.00 for Linux Intel 2.2/XX contains all the cummulative bug fixes developed on other platforms as well as fixes developed from our internal bug list. [LINUX INTEL] Added support for RedHat 7.0 enterprise edition. ------------------------------------------------------------------ DoubleVision 3.30.00 build #7 supports the RedHat 7.0 enterprise edition kernel 2.2.16-22enterprise. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR: ***************** ******************** SCO Unixware 7.X PLATFORM ****************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.30.00 BUILD #3 ****** ****************************************************************** [SCO UW] Cummulative bug fixes applied to latest for Unixware 7.X. ------------------------------------------------------------------ DoubleVision 3.30.00 for Unixware 7.1/7.0 contains all the cummulative bug fixes developed on other platforms as well as fixes developed from our internal bug list. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** ************** Solaris Intel 2.5/2.6/2.7/2.8 PLATFORM ************ ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.30.00 BUILD #9 ****** ****************************************************************** [SOLARIS] Cummulative bug fixes applied to latest for Solaris Intel. ------------------------------------------------------------------ DoubleVision 3.30.00 for Solaris SPARC contains all the cummulative bug fixes developed on other platforms as well as fixes developed from our internal bug list. ****************************************************************** ***** THE FOLLOWING NOTES ARE FOR RELEASE 3.08.00 BUILD #10 ****** *********** HP-UX 11.00 Series 800/700 64 bit - UP/MP ************ ****************************************************************** [HPUX] Solved improper 32 bit central driver in 64 bit distribution tree. ------------------------------------------------------------------ DoubleVision 3.08.00 Build #9 for HP-UX 11.00 64 bit contained a 32 bit central driver. This driver should be 64 bit. The 64 bit central has been corrected for build #10. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** **************** Solaris Intel 2.6/2.7/2.8 PLATFORM ************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.30.00 BUILD #8 ****** ****************************************************************** [SOLARIS x86] Cummulative bug fixes applied to latest for Solaris Intel. ------------------------------------------------------------------ DoubleVision 3.30.00 for Solaris Intel contains all the cummulative bug fixes developed on other platforms as well as fixes developed from our internal bug list. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** **************** AIX 3.2.X/4.1.X/4.2.X/4.3.X ********************* ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.30.00 BUILD #8 ****** ****************************************************************** [AIX 4.1.X/4.2.X/4.3.X] Cummulative bug fixes applied to latest build for AIX. ------------------------------------------------------------------ DoubleVision 3.30.00 for AIX contains all the cummulative bug fixes developed on other platforms as well as fixes developed from our internal bug list. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** ******************* SCO UNIX/MPX 3.2.4.X/3.2.5.X ***************** ***** THE FOLLOWING NOTES ARE FOR RELEASE 3.30.00 BUILD #12 ****** ****************************************************************** [SCO] Cummulative bug fixes applied to latest build for SCO. ------------------------------------------------------------------ This new version of DoubleVision for SCO UNIX/MPX contains all the cummulative bug fixes developed on other platforms as well as fixes developed from our internal bug list. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR: ***************** ******** HP-UX 11.11 Series 800/700 32 and 64 bit - UP/MP ******** **** THE FOLLOWING NOTES ARE FOR RELEASE 3.30.00 BUILD #9 ******** ******** HP-UX 11.00 Series 800/700 32 and 64 bit - UP/MP ******** **** THE FOLLOWING NOTES ARE FOR RELEASE 3.08.00 BUILD #9 ******** ****************************************************************** [HPUX] Port completed to HPUX 11.11 UP/MP 32 and 64 bit processors. ------------------------------------------------------------------- DoubleVision now supports HP-UX 11.11 on 32 and 64 bit processors otherwise known as PA RISC 1.X and PA RISC 2.X processors. The new distribution will automatically detect the current version of HP-UX and install the proper binaries. Support for HP-UX 10.10, 10.20 and 11.00 is also available from within the same distribution. For HP-UX 11.XX platforms the install program will automatically place the proper 32 bit or 64 bit binaries based on what the current target cpu type. [HPUX] Signal enhancements ------------------------------------------------------------------ Interim changes were made to the DoubleVision driver which improved how signals were being handled. These changes are supported on HP-UX 11.0 and HP-UX 11.11. ****************************************************************** ***** THE FOLLOWING NOTES ARE FOR RELEASE 3.08.00 BUILD #8 ******* *********** HP-UX 11.00 Series 800/700 32 bit - UP/MP ************ ****************************************************************** [HPUX] Solved improper 64 bit central driver in 32 bit distribution tree. ------------------------------------------------------------------ DoubleVision 3.08.00 Build #7 for HP-UX 11.00 32 bit contained a 64 bit central driver. This driver should be 32 bit. The 32 bit central has been corrected for build #8. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR: ***************** ******************* Linux Intel 2.2/XX PLATFORM ****************** ** THE FOLLOWING NOTES ARE FOR RELEASE 3.12.00/3.06.01 BUILD #6 ** ****************************************************************** [LINUX INTEL] Added support for RedHat version 7. ------------------------------------------------------------------ DoubleVision 3.12.00 Build #6 supports RedHat version 7. Support the native kernel on RedHat 7, 2.2.16-22, has been added. [LINUX INTEL] -906 error solved when running the kernel 2.2.5-15 multiprocessor kernel. ------------------------------------------------------------------ Running the RedHat kernel 2.2.5-15 with multiprocessor support may generate the following error when executing DoubleVision "-906 Cannot open remote control device" This problem has been resolved in DoubleVision 3.12.00/3.06.01 Build #6. [LINUX INTEL] -906 error solved when running the kernel 2.2.16-3 multiprocessor kernel. ------------------------------------------------------------------ Running the RedHat kernel 2.2.16-3 with multiprocessor support may generate the following error when executing DoubleVision "-906 Cannot open remote control device" This problem has been resolved in DoubleVision 3.12.00/3.06.01 Build #6. [LINUX INTEL] Signal enhancements ------------------------------------------------------------------ Interim changes were made to the DoubleVision driver which improved how signals were being handled while in the middle of a read system call. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** ******************** Solaris Intel 2.6 PLATFORM ****************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.00.01 BUILD #7 ****** ****************************************************************** [SOLARIS x86] Not possible to view Solaris Intel 2.6 character based console. ------------------------------------------------------------------ DoubleVision release 3.00.01 Build #7 solves a problem where a user could not view the Solaris 2.6 Intel character based console. The error message received upon the console connection attempt was: "17: Cannot OPEN Screen Server channel" Please keep in mind that the console can only be viewed successfully when in "Command Login" or character based mode. You are not able to view the console while the X server is running. [SOLARIS x86] Display buffering problem upon second view has been solved. ------------------------------------------------------------------ The problem manifests itself by the remote terminal not displaying the entire screen of the host terminal. If the remote user presses a key the display begins to catch up and be correct. This problem appears only upon viewing the same device for a second time. From a low level perspective, the problem is due to a bug in the operating system "poll" system call. We have worked around the operating system bug. DoubleVision 3.00.01 Build #7 solves this problem. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** ******************* SCO UNIX/MPX 3.2.4.X/3.2.5.X ***************** ***** THE FOLLOWING NOTES ARE FOR RELEASE 3.00.01 BUILD #11 ****** ****************************************************************** [SCO] Recorded session playback problem solved. ------------------------------------------------------------------ DoubleVision 3.00.01 Build #11 solves a recorded session problem. Under certain conditions the recording of a host session may stop. The recording file will quit growing in size. If you attempt to playback the recorded session the following error is displayed: "No screen activity recorded" The cause of this error is an improperly formatted recording file. Format corruption has been resolved in this new build. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR: ***************** ********************** DG/UX Intel 4.1/4.2 *********************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.00.00 BUILD #2 ****** ****************************************************************** [DGUX Intel] Recorded session playback problem solved. ------------------------------------------------------------------ DoubleVision 3.00.00 Build #2 solves a recorded session problem. Under certain conditions the recording of a host session may stop. The recording file will quit growing in size. If you attempt to playback the recorded session the following error is displayed: "No screen activity recorded" The cause of this error is an improperly formatted recording file. Format corruption has been resolved in this new build. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR: ***************** ******************** SCO Unixware 7.X PLATFORM ****************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.07.01 BUILD #2 ****** ****************************************************************** [SCO UW] Recorded session playback problem solved. ------------------------------------------------------------------ DoubleVision 3.07.01 Build #2 solves a recorded session problem. Under certain conditions the recording of a host session may stop. The recording file will quit growing in size. If you attempt to playback the recorded session the following error is displayed: "No screen activity recorded" The cause of this error is an improperly formatted recording file. Format corruption has been resolved in this new build. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR: ***************** *************** HP-UX 10.20 Series 800/700 - UP/MP *************** ***** THE FOLLOWING NOTES ARE FOR RELEASE 3.00.05 BUILD #7 ******* *********** HP-UX 11.00 Series 800/700 32 bit - UP/MP ************ ***** THE FOLLOWING NOTES ARE FOR RELEASE 3.08.00 BUILD #7 ******* ******** HP-UX 11.00 Series 800/700 32 and 64 bit - UP/MP ******** *** THE FOLLOWING NOTES ARE FOR RELEASE 3.08.00 BUILD BUILD #7 *** ****************************************************************** [HPUX] Recorded session playback problem solved. ------------------------------------------------------------------ DoubleVision 3.00.05/3.08.00 Build #7 solves a recorded session problem. Under certain conditions the recording of a host session may stop. The recording file will quit growing in size. If you attempt to playback the recorded session the following error is displayed: "No screen activity recorded" The cause of this error is an improperly formatted recording file. Format corruption has been resolved in this new build. [HPUX] Random signal SIGALRM receipts handled correctly. ------------------------------------------------------------------ Only under HP-UX 11.00 32 and 64 bit systems would a ramdomly delivered signal SIGALRM would cause dvscreen ( back end remote control process ) to die prematurely when a user would first try to view a terminal device. This issue has been resolved. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR: ***************** *********** HP-UX 11.00 Series 800/700 32 bit - UP/MP ************ ***** THE FOLLOWING NOTES ARE FOR RELEASE 3.08.00 BUILD #6 ******* ****************************************************************** [HPUX] Additional debug messages added to dvexec and dvscreen. ------------------------------------------------------------------- Additional debug messages were added to dvexec and dvscreen in order to better document the receipt of signals which can terminate either process. The modification is currently present only in the HP-UX 11.00 32bit binaries. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** **************** AIX 3.2.X/4.1.X/4.2.X/4.3.X ********************* ** THE FOLLOWING NOTES ARE FOR RELEASE 3.00.04/3.01.04 BUILD #6 ** ****************************************************************** [AIX 4.1.X/4.2.X/4.3.X] Recorded session playback problem solved. ------------------------------------------------------------------ DoubleVision 3.00.04/3.01.04 Build #6 solves a recorded session problem. Under certain conditions the recording of a host session may stop. The recording file will quit growing in size. If you attempt to playback the recorded session the following error is displayed: "No screen activity recorded" The cause of this error is an improperly formatted recording file. Format corruption has been resolved in this new build. [AIX 4.3.X] Lingering dvrecord process solved. ------------------------------------------------------------------ DoubleVision 3.00.04/3.01.04 Build #6 solves a boundary condition where the "dvrecord" and "dvscreen" process linger. If a user logs in on a pseudo device and runs the prerecord script the two processes, dvrecord and dvscreen, may remain running after the user logs out. Also, our streams module remains on the streams stack for the pseudo device. This results in the pseudo device not being available for a user logging in at a later time. This issue has been resolved. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR: ***************** ******************** SCO Unixware 7.X PLATFORM ****************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.07.01 BUILD #1 ****** ****************************************************************** [SCO UW] Buffer overflow problem solved. ------------------------------------------------------------------ The program '/usr/lib/dv/dvtermtype' could be caused to spawn a shell with root priviledges under very specific conditions of a buffer overflow. For security reasons we're not disclosing how to re-create these conditions. To solve this problem users should install DoubleVision 3.07.01 Build#1 or higher for Unixware 7.X. Another solution is to issue the following commands while as root to disable the setuid bit of the program /usr/lib/dv/dvtermtype : chmod 555 /usr/lib/dv/dvtermtype chmod 666 /usr/lib/dv/ttytype [SCO UW] Prerecord script enhanced. ------------------------------------------------------------------ The script /usr/lib/dv/prerecord has been enhanced such that a more unique filename is automatically generated for the pre- recorded session. The new filenames that the form of : /tmp/dvrec..on So for example if a user logs in via tty /dev/pts000 then the filename generated would be in the form of : /tmp/dvrec.pts000.on07-28-00at09:51:25 Assuming the pre-recorded session started on 07/27/2000 at 9:51:25am. With this new scheme sysadmins will be able to see multiple pre- recorded sessions per user. In addition in the rare event that a duplicate pre-record filename were to be generated a rotating filename scheme is used by appending a digit to the end of the file such as : /tmp/dvrec.pts000.on07-28-00at09:51:25.0 /tmp/dvrec.pts000.on07-28-00at09:51:25.1 /tmp/dvrec.pts000.on07-28-00at09:51:25.2 /tmp/dvrec.pts000.on07-28-00at09:51:25.3 /tmp/dvrec.pts000.on07-28-00at09:51:25.4 The above would be a very unlikely case. Still the goal is to preserve the recorded sessions as much as possible. [SCO UW] Translation and emulation engines were enhanced. ------------------------------------------------------------------ Both the generic terminal translation and emulation engines were enhanced to handle the special conditions of when the host terminal has auto-right-margins BUT has disabled screen scrolling when a character is output on the bottom right corner. [SCO UW] Security enhancements made to dvtermtype. ------------------------------------------------------------------ Several security enhancements were made to the terminal type collector program /usr/lib/dv/termtype with the goal of improved security. Some of the change are : 1- Control characters are not allowed in any command line arguments. 2- Only valid terminal devices can be specified from the command line. Before no validation of the device names provided was performed. 3- The terminal type data base must be owned to root and have specific permissions for it to be considered 'safe'. Additional checks are made to ensure the data base is a regular file and not a device, nor symbolic link, etc. 4- Only the absolute path of the terminal type data base can be used. This means that the environment variable $DVLIB is not obeyed for this particular data base. This is the only way to ensure the file is safe and secure. 5- Only the owner the terminal can update his/her terminal type data base entry. Root is granted this privildge at all times. 6- Command line arguments lengths cannot exceed certain predetermined 'safe sane' lengths. 7- Checks are applied to make sure that the directory /usr/lib/dv has the proper 'secure' permissions. That is owned by root and it NOT a symbolic link. [ALL] New terminal type data base 'vt100-ssh' was added. ------------------------------------------------------------------ To better support users of the popular terminal emulator 'SSH' a custom EXTENDED terminal type data base sepcific to ssh was developed and named 'vt100-ssh'. The major difference between a 'standard' vt100 terminal and 'SSH's are the definition of the function keys. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR: ***************** **************** Linux Intel 2.0.XX/2.2/XX PLATFORM ************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.06.00 BUILD #3 ****** ****************************************************************** [LINUX INTEL] Added support for two new Red Hat kernels. ------------------------------------------------------------------ Release 3.06.00 Build#3 of DoubleVision has added support for Red Hat kernel version 2.2.14-5 UP/MP. Support for kernel version 2.2.15 was added to support the latest stable kernel found on www.kernel.org. [LINUX INTEL] Panic condition solved. ------------------------------------------------------------------ Under specific conditions, DoubleVision may cause a kernel panic. If a user views his own session a kernel panic may occur. DoubleVision has a built in mechanim to prevent a tty from viewing itself. You should notice the tty you run DoubleVision on never shows up in your list of viewable terminals. There are ways of creating a pseudo terminal that runs on your tty. For example, you log in to the system on the console /dev/tty1. You then telnet/rlogin back in to the same system. If you run the 'tty' command you are now on a pseudo device /dev/ttypX. If you were to run DoubleVision and view your originating tty, /dev/tty1, you would be viewing yourself in a loop. This action may cause a system panic. DoubleVision does not detect that /dev/tty1 and /dev/ttypX are one in the same. We have resolved the panic condition in DoubleVision release 3.06.00 Build #3. You could still see the pseudo device present but an error will be displayed if you try to view the device. [LINUX INTEL] Linux kernel 2.2.12-20 MP module versioning problem solved. ------------------------------------------------------------------ DoubleVision release 3.06.00 Build #3 solves a module versioning problem on Linux kernel 2.2.12-20 multi-processing systems. This problem only manifests itself if 'Module versioning support' is enabled on multi-processing systems. The error would be seen as "-906 Cannot open remote control device." On previous DoubleVision builds we did not have support for this kernel with versioning enabled. Support has now been added. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** *********** Solaris SPARC 2.5/2.6/2.7/2.8 PLATFORM ************* ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.10.00 BUILD #8 ****** ****************************************************************** [SOLARIS] Corrupt help file in 32 bit distrutions. ------------------------------------------------------------------- Only with DoubleVision versions 3.00.00, 3.03.00, 3.05.00, 3.09.00 or 3.10.00 Build #7 for 32bit systems one gets an error -25 when trying to invoke the help system. The problem is caused by having installed the 64 bit version of the help file data base onto a 32 bit system. DoubleVision versions 3.00.00, 3.03.00, 3.05.00, 3.09.00 and 3.10.00 Build#8 solves this problem. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR: ***************** *************** HP-UX 10.20 Series 800/700 - UP/MP *************** ***** THE FOLLOWING NOTES ARE FOR RELEASE 3.00.05 BUILD #5 ******* *********** HP-UX 11.00 Series 800/700 32 bit - UP/MP ************ ***** THE FOLLOWING NOTES ARE FOR RELEASE 3.08.00 BUILD #5 ******* ****************************************************************** [HPUX] Corrupt help file in 32 bit distrutions. ------------------------------------------------------------------- Only with DoubleVision versions 3.08.00 or 3.00.05 Build #1 - #4 for 32bit systems one gets an error -24 when trying to invoke the help system. The problem is caused by having installed the 64 bit version of the help file data base onto a 32 bit system. DoubleVision 3.08.00/3.00.05 Build#5 solves this problem. Update #39 solves this problem. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** *********** Solaris SPARC 2.5/2.6/2.7/2.8 PLATFORM ************* ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.10.00 BUILD #7 ****** ****************************************************************** [SOLARIS] Solaris SPARC 2.X 32 bit installation problem solved. ------------------------------------------------------------------ DoubleVision 3.10.00 Build #6 is not able to install or be removed properly on Solaris 2.5/2.6/2.7/2.8 32 bit systems. During the installation the following error will appear: Checking current operating system version ... cp: cannot create /usr/kernel/drv/sparcv9/rcentral: No such file or directory ERROR: Unable to install proper Solaris SPARC 2.5 CENTRAL 32 bit driver. This problem has been resolved in DoubleVision release 3.10.00 Build #7. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR: ***************** *************** HP-UX 10.20 Series 800/700 - UP/MP *************** ***** THE FOLLOWING NOTES ARE FOR RELEASE 3.00.05 BUILD #4 ****** ****************************************************************** [HPUX] 10.20 Licensing problem solved. ------------------------------------------------------------------- DoubleVision 3.00.05 Build #3 for HP-UX 10.20 only is not able to accept a valid TLA number. The following error message is displayed : TLA specified is invalid or corrupt. The problem resides only within the program : /usr/lib/dv/tlalicense when option number 3 is selected. Problem solved. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** ******************* SCO UNIX/MPX 3.2.4.X/3.2.5.X ***************** ***** THE FOLLOWING NOTES ARE FOR RELEASE 3.00.01 BUILD #10 ****** ****************************************************************** [SCO] Solved the problem where DoubleVision's driver could not be configured into the kernel under some systems. ------------------------------------------------------------------ During the installation or upgrading to of DoubleVision 3.00.01 BUILD #5 through BUILD #9 it was possible for the installation or upgrade to failed with the following error message : ERROR: Unable to configure DoubleVision driver into UNIX. DoubleVision 3.00.01 Build# 10 solves this problem. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** ******************** Solaris Intel 2.8 PLATFORM ****************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.11.00 BUILD #6 ****** ****************************************************************** [SOLARIS x86] Port completed to Solaris Intel 2.8 UP/MP 32 bit processor systems. ------------------------------------------------------------------ DoubleVision release 3.11.00 Build #6 now supports Solaris 2.8 Intel 32 bit processor systems. This release also provides support for the following Solaris Intel operating systems: -- Solaris 2.4 32 bit UP/MP systems. -- Solaris 2.5 32 bit UP/MP systems. -- Solaris 2.6 32 bit UP/MP systems. -- Solaris 2.7 32 bit UP/MP systems. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** *********** Solaris SPARC 2.5/2.6/2.7/2.8 PLATFORM ************* ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.10.00 BUILD #6 ****** ****************************************************************** [SOLARIS] Port completed to Solaris SPARC 2.8 UP/MP 32 bit and 64 bit processor(s). ------------------------------------------------------------------ DoubleVision release 3.10.00 Build #6 now supports Solaris 2.8 32 bit and 64 bit processor(s) systems. For Solaris 2.8 platforms the install program will automatically place the proper 32 bit or 64 bit binaries based on the current target cpu type. DoubleVision release 3.10.00 Build #6 also supports the following Solaris Sparc operating system releases: -- Solaris SPARC 2.5 32 bit UP/MP systems. -- Solaris SPARC 2.6 32 bit UP/MP systems. -- Solaris SPARC 2.7 32 bit and 64 bit UP/MP systems. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR: ***************** *************** HP-UX 10.20 Series 800/700 - UP/MP *************** ***** THE FOLLOWING NOTES ARE FOR RELEASE 3.00.05 BUILD #3 ****** ****************************************************************** [HPUX] 10.20 Double echo or corrupted psuedo-tty problem solved. ------------------------------------------------------------------- DoubleVision 3.00.05 Build #3 contains the fix for the prevention of psuedo-tty's becoming corrupt or unuseable after one is logged out via DoubleVision. This particular problem would manifest itself only on certian HP-UX systems and would occur at random. A new DoubleVision driver was engineered which prevents this condition from ever occuring again. Problem solved. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR: ***************** ******** HP-UX 11.00 Series 800/700 32 and 64 bit - UP/MP ******** *** THE FOLLOWING NOTES ARE FOR RELEASE 3.08.00 BUILD #2 BETA **** ****************************************************************** [HPUX] Recommended patches to apply on 11.XX systems. ------------------------------------------------------------------- The following list of patches are recommended to be installed on any HP-UX 11.XX 32 or 64 bit system. DoubleVision does not require them to function properly. But as DoubleVision does use some of the resources repaired by these patches, not having them can increase the chances of a system panic. It is important to understand that if that were the case, it is NOT DoubleVision who is at fault. By installing these patches the end user is only ensuring the proper operating of the HP-UX system. Recommended patches as of 3/29/2000 : s700_800 11.0 telnet kernel patch(PHNE_16546) s700_800 11.00 telnetd(1M) cumulative patch(PHNE_19298) s700_800 11.00 Cumulative Mux and Pty Patch(PHNE_20431) s700_800 11.00 Streams Pty cumulative patch(PHNE_20094) s700_800 11.00 Cumulative STREAMS Patch(PHNE_20008) [HPUX] Kernel panics when viewing psuedo-ttys problem solved. ------------------------------------------------------------------- Under HP-UX 11.0 on a 32 or 64 bit based system, when there is a high number of users connected via psuedo-ttys ( generated by either rlogin or telnet ), DoubleVision could panic the kernel. This problem has been solved. The solution was to use 'spinlocks' as opposed to 'beta locks' within the STREAMS sub-system. This problem would not occur when viewing a terminal connected to a serial device. [HPUX] Running tlalicense would result in a core dump at random. ------------------------------------------------------------------- Typically when a user first installs DoubleVision on a system which was not previously licensed, sometimes the license program would core dump after the user accepted the license agreement. This problem would occur only on 64 bit systems. Problem solved. [HPUX] Nothing would display when running the 'view log' option. ------------------------------------------------------------------- Only under 64 bit versions of DoubleVision would the 'view log' ( Main->seCurity->View log->on Screen ) option fail to display any output. The same would be true if the actual view log program /usr/lib/dv/dvlog was invoked from the command line. Problem solved. [HPUX] Unable to 'break out' of viewing an instant replay session. ------------------------------------------------------------------- Only under 64 bit versions of DoubleVision was it possible for user to seem 'locked' in an infinite loop while viewing a 'instant replay' session. Problem solved. [HPUX] Random terminals would appear as 'pre-attached'. ------------------------------------------------------------------- Only on psuedo-ttys would this problem ocurr. The cause of the problem would be when a remote user logged a host user out who in turn was logged in on a psuedo-tty. The effect would be ( at random ) for that particular psuedo-tty to appear as 'preattached'. That is with the marker 'PRE' on the DoubleVision user interface. Problem solved. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** ***************** Solaris SPARC 2.5/2.6/2.7 PLATFORM ************* ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.09.00 BUILD #5 ****** ****************************************************************** [SOLARIS] Port completed to Solaris SPARC 2.7 UP/MP 64 bit processor(s). ------------------------------------------------------------------ DoubleVision release 3.09.00 Build #5 now supports Solaris 2.7 32 bit and 64 bit processor(s) systems. For Solaris 2.7 platforms the install program will automatically place the proper 32 bit or 64 bit binaries based on the current target cpu type. Support for Solaris 2.5 and 2.6 32 bit processors is also available in this distribution. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** ******************** NCR Unix 3.X PLATFORM ********************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.04.00 BUILD #2 ****** ****************************************************************** [NCR] Added support for non-interactive installation ------------------------------------------------------------------ DoubleVision release 3.04.00 Build #2 has added support for a non-interactive installation. Non-interactive installation means that you will not be prompted by DoubleVision's installation script. The installation script will use default responses in performing the product installation. To invoke the non-interactive installation provide the '-s' command line argument to 'install-dv'. Ex. "./install-dv -s". [ALL] Added terminal type support. ------------------------------------------------------------------ Added Extended database support for the following terminal types: -- 2900 -- 2920 -- 4940 -- a2920 -- ancr2920 -- ncr2920 -- z2920 -- zcolor -- zncr2920 ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR: ***************** ******** HP-UX 11.00 Series 800/700 32 and 64 bit - UP/MP ******** * THE FOLLOWING NOTES ARE FOR RELEASE 3.08.00 BUILD #1 POST-BETA * ****************************************************************** [HPUX] Default file variable ENABLE_UTMP_CACHE=YES is not supported. ------------------------------------------------------------------- DoubleVision now supports caching the contents of the /etc/utmp data base for performance purposes on 64 bit systems. [HPUX] 64 bit perfomance enhancements added to DoubleVision. ------------------------------------------------------------------- Development efforts and technology developed for DoubleVision's Solaris Sparc 64 bit port have been folded into the HP-UX 64 bit port. [HPUX] View log fatal errors solved. ------------------------------------------------------------------- View log initialization and termination errors would appear only on a 64 bit platform and random. This issue has been resolved. [HPUX] The view log facility is currently disabled for this port. ------------------------------------------------------------------- Under HP-UX 11.XX for 64 bit systems the view log facility is currently disabled. A future release will solve this problem. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR: ***************** ******** HP-UX 11.00 Series 800/700 32 and 64 bit - UP/MP ******** **** THE FOLLOWING NOTES ARE FOR RELEASE 3.08.00 BUILD #1 BETA *** ****************************************************************** [HPUX] Port completed to HPUX 11.XX UP/MP 32 and 64 bit processors. ------------------------------------------------------------------- DoubleVision now supports HP-UX 11.XX on 32 and 64 bit processors otherwise known as PA RISC 1.X and PA RISC 2.X processors. The new distribution will automatically detect the current version of HP-UX and install the proper binaries. Support for HP-UX 10.10 and 10.20 is also available from within the same distribution. For HP-UX 11.XX platforms the install program will automatically place the proper 32 bit or 64 bit binaries based on what the current target cpu type. DoubleVision now supports STREAMS based terminal devices in addition to the 'classical' terminal devices. Starting with HP-UX 10.20 psuedo-tty devices are STREAMS based. Now with version 3.08.00 Build#1 of DoubleVision, automatic support to remote control either type of terminal is available. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR: ***************** **************** Linux Intel 2.0.XX/2.2/XX PLATFORM ************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.06.00 BUILD #2 ****** ****************************************************************** [LINUX INTEL] A system wide lock up may occur when attaching to a host terminal running heavy i/o. ------------------------------------------------------------------ Release 3.06.00 Build#2 of DoubleVision resolves a possible system lock up condition. If a user attaches to a host terminal that is running heavy i/o a system lock up may occur. We resolved this issue by enhancing our driver sleep and wakeup mechanism. [LINUX INTEL] Added driver support for module symbol versioning. ------------------------------------------------------------------ Release 3.06.00 Build#2 of DoubleVision has added support for Red Hat kernel module versioning. In the previous build of DoubleVision for Red Hat linux we provided module support for kernels with module versioning disabled. Attempting to run the prior build of DoubleVision, on a module version enabled kernel, would result in a module load failure due to numerous unresolved symbols. This issue has been resolved for our supported kernel versions in this new build. [LINUX INTEL] Added support for two new Red Hat kernels. ------------------------------------------------------------------ Release 3.06.00 Build#2 of DoubleVision added support for Red Hat kernel 2.2.12-32 and 2.2.14 UP/MP versions. Kernel version 2.2.12-32 was added to support the standard Red Hat Linux kernel shipped by Dell Computers on their Unix servers. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** ***************** Solaris Intel 2.6/2.7 PLATFORM ***************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.00.01 BUILD #5 ****** ****************************************************************** [SOLARIS x86] DoubleVision's digiboard trigger will not execute properly when called from a non-root user's .profile. ------------------------------------------------------------------ Customers that are using DoubleVision's Digiboard entry trigger support from a non-root user's .profile will not execute the trigger properly. This problem manifests itself when a user views the non-root user on a terminal connected to a Digiboard serial I/O board. The remote user can not send keystrokes over to the host being viewed. DoubleVision release 3.00.01 Build #5 resolves this problem. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** ******************* SCO UNIX/MPX 3.2.4.X/3.2.5.X ***************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.00.01 BUILD #9 ****** ****************************************************************** [SCO] Interim version of DoubleVision. ------------------------------------------------------------------ This version of DoubleVision was a work in progress version which started to solve the problem of not being able to link the SCO 3.2.4.X kernel in some instances. The problem arises from the need to be within the /etc/conf/cf.d directory when one issues the /etc/conf/cf.d/link_unix command. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** ******************* SCO UNIX/MPX 3.2.4.X/3.2.5.X ***************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.00.01 BUILD #8 ****** ****************************************************************** [SCO] Corrupt distribution solved. ------------------------------------------------------------------ DoubleVision 3.00.01 BUILD #7 was a corrupt distribution. The image that was copied onto the ftp/web site became corrupt. Thus this version has been successfully tested from the ftp and web site without any problems. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** ******************* SCO UNIX/MPX 3.2.4.X/3.2.5.X ***************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.00.01 BUILD #7 ****** ****************************************************************** [SCO] DoubleVision's digiboard trigger will not execute properly when called from a non-root user's .profile. ------------------------------------------------------------------ This build is basically a re-release of BUILD #6. It turns out that during the mastering process the new digiboard trigger changes were to copied into BUILD #6. Hence that build would not solve properly the problem which is described below : Customers that are using DoubleVision's Digiboard entry trigger support from a non-root user's .profile will not execute the trigger properly. This problem manifests itself when a user views the non-root user on a terminal connected to a Digiboard serial I/O board. The remote user can not send keystrokes over to the host being viewed. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** ******************* SCO UNIX/MPX 3.2.4.X/3.2.5.X ***************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.00.01 BUILD #6 ****** ****************************************************************** [SCO] DoubleVision's digiboard trigger will not execute properly when called from a non-root user's .profile. ------------------------------------------------------------------ Customers that are using DoubleVision's Digiboard entry trigger support from a non-root user's .profile will not execute the trigger properly. This problem manifests itself when a user views the non-root user on a terminal connected to a Digiboard serial I/O board. The remote user can not send keystrokes over to the host being viewed. DoubleVision release 3.00.01 Build #6 resolves this problem. [SCO] Installations of DoubleVision 3.00.01 releases prior to Build #6 may fail on SCO release 3.2.4.2 systems. ------------------------------------------------------------------ DoubleVision release 3.00.01 Build #6 resolves a problem where the SCO kernel configuration command 'configure' detects a previous instance of DoubleVision's device driver but does not return the MAJOR number associated with our device driver. This behavior causes DoubleVision's installation to fail. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** **************** SCO Unixware 7.1 AND 7.0 PLATFORM *************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.07.00 BUILD #1 ****** ****************************************************************** [SCO UW] Port completed to Unixware 7.1 and 7.0. ------------------------------------------------------------------ Release 3.07.00 Build #1 of DoubleVision was developed for the Unixware 7.1 and 7.0 Intel platforms. Uni-processor and Multi-processor kernels are supported. Known Issues: ------------------------------------------------------------------ Issue #1: If the remote user invokes DoubleVision's 'CHAT'. The remote screen may not be repainted with the host users screen upon the closing of the 'CHAT' window. This will be resolved in a future release. Issue #2: A remote user attaches to a 'rlogin' session to log them out. The host-tty will not be deconstructed until the remote user peforms a 'CTRL-Z' and is no longer viewing. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR: ***************** **************** Linux Intel 2.0.XX/2.2/XX PLATFORM ************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.06.00 BUILD #1 ****** ****************************************************************** [LINUX INTEL] DoubleVision was ported to the Linux Intel Platform. ------------------------------------------------------------------ Release 3.06.00 Build#1 of DoubleVision was developed for the Linux Intel 2.0.XX and 2.2.XX platforms. Uni-processor and Multi-processor kernels are supported. DoubleVision has been tested against Red Hat's Linux distribution. Other distributions of Linux on the Intel platform will be tested at a later date. This means that DoubleVision has only been certified by Tridia Corporation under Red Hat's 5.X/6.X distribution. The following is the list of supported versions of Linux : 2.0.36 UP 2.2.0 UP/MP 2.2.1 UP/MP 2.2.2 UP/MP 2.2.3 UP/MP 2.2.4 UP/MP 2.2.5 UP/MP 2.2.5-15 UP/MP 2.2.6 UP/MP 2.2.7 UP/MP 2.2.8 UP/MP 2.2.9 UP/MP 2.2.10 UP/MP 2.2.11 UP/MP 2.2.12 UP/MP 2.2.12-20 UP/MP 2.2.13 UP/MP [LINUX INTEL] Linux specific defaults file variables were added. ------------------------------------------------------------------ The following list of defaults file variables were added in order to better support the Linux Intel platform. TERMINAL_TRIGGERS_VERBOSE=NO LINUX_CLISTS_BUFFERS = 800 LINUX_NCALL = 800 LINUX_NPROC = 512 LINUX_NOPEN = 256 Please see the file: /usr/lib/dv/default for more details as to each variable's behavior. [LINUX INTEL] New terminal data bases added. ------------------------------------------------------------------ During the Linux port of DoubleVision the following EXTENDED terminal data bases where added : linux-2.0.XX # Specific to Linux 2.0.XX linux-2.2.XX # Specific to Linux 2.2.XX xterm-color Note that the Linux console under 2.0.XX vs 2.2.XX changed slightly in how the alternate character set is selected. For that reason during install time DoubleVision will use the Linux specific EXTENDED terminal data base and link it to the file '/usr/lib/dv/termdb/linux'. The end result is the proper display/translation of the Linux console under any version of Linux. [LINUX INTEL] Special device considerations. ------------------------------------------------------------------ DoubleVision intentionally does not allow the user to connect to the system device files : /dev/console /dev/tty0 Instead the user should connect directly to the current console device. Such as /dev/tty1, /dev/tty2, etc. [LINUX INTEL] Module load warning messages. ------------------------------------------------------------------ When loading the DoubleVision remote control module 'rcon.o' the program 'insmod' will issue an error message similar to the one below : Warning: kernel-module version mismatch /lib/modules/2.2.12/misc/rcon.o was compiled for kernel version 2.2.5-15 while this kernel is version 2.2.12 The above message will appear only within DoubleVision's general error file /usr/adm/DVLOG. This message is benign. The insmod program will complain if the version of a module is not identical to the version of the current kernel. In DoubleVision's case the module is meant run on versions of a kernel major release. Such as 2.2.XX or 2.0.XX. The minor differences between kernel version 2.2.5 vs 2.2.10 do not affect DoubleVision's functionality nor that of the kernel on which it is loaded. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** ***************** Solaris SPARC 2.5/2.6/2.7 PLATFORM ************* ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.05.00 BUILD #4 ****** ****************************************************************** [SOLARIS] Added granular security support for Solaris system's running system auditing (Basic Security Module). ------------------------------------------------------------------ DoubleVision release 3.05.00 Build #4 has enhanced security checks to support the Solaris Operating systems Basic Security Module. In prior releases of DoubleVision a security breach may occur for a non-root user even if they have DoubleVision's security permission to view the host user. Running the Solaris Basic Security Module creates a scenario where a root owned process is running on the host users tty. The process is called 'login'. DoubleVision sees this is a security violation to our rule that a non-root user may not view a root user. DoubleVision sees this as the host user being root at some point during their session. Build #4 resolves this issue such that a non-root user may view a host user with a 'root' owned 'login' process. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** **************** AIX 3.2.X/4.1.X/4.2.X/4.3.X ********************* ** THE FOLLOWING NOTES ARE FOR RELEASE 3.00.04 BUILD #4/BUILD #5 * ****************************************************************** [AIX 4.1.X/4.2.X/4.3.X] Streams buffering problem solved. ------------------------------------------------------------------ A buffering problem would occur on DoubleVision when viewing a HOST terminal. Specifically the REMOTE terminal would not get a complete screen from the HOST. An example could be where if one issued a long listing when viewing the HOST and the REMOTE would see all but the last few lines on the screen ( the last few lines of the output of the ls command ). This buffering problem could manifest itself in different forms. This buffering problem would be differnt based on the application being used, terminal type and operating system version. Modifications were made to DoubleVision's driver technology to prevent any buffering problems from occuring. Users who are installing this new version of DoubleVision will have to reboot their machines for the changes to take effect. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** **************** AIX 3.2.X/4.1.X/4.2.X/4.3.X ********************* ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.00.04 BUILD #3 ****** ****************************************************************** [ALL] Added terminal type support. ------------------------------------------------------------------ Added Extended database support for the following terminal types: -- vt240 -- vt241 [AIX 4.3.X] Ioctl Synchronization issue on AIX 4.3.X ------------------------------------------------------------------ DoubleVision release 3.00.04 Build #3 corrects an ioctl synchronization problem on AIX 4.3.X systems. The ioctl problem manifests itself by the cursor position stair stepping on the host (user being viewed) terminal. Stair stepping can be best described at the Unix shell where the shell prompt moves over a number of spaces each time the users presses the return key. ex. $[ENTER] $[ENTER] $[ENTER] ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** ***************** Solaris Intel 2.6/2.7 PLATFORM ***************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.00.01 BUILD #4 ****** ****************************************************************** [SOLARIS x86] Added support for non-interactive installation ------------------------------------------------------------------ DoubleVision release 3.00.01 Build #4 has added support for a non-interactive installation. Non-interactive installation means that you will not be prompted by DoubleVision's installation script. The installation script will use default responses in performing the product installation. To invoke the non-interactive installation provide the '-s' command line argument to 'install-dv'. Ex. "./install-dv -s". ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** ******************* SCO UNIX/MPX 3.2.4.X/3.2.5.X ***************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.00.01 BUILD #5 ****** ****************************************************************** [SCO] Random session lock ups occur at the password prompt when attaching to a terminal/console that is AT LOGIN and attempting to login in. ------------------------------------------------------------------ On some SCO Open Server 3.2.5.X systems a user may experience a random session lockup while attempting to login in on a host terminal that is AT LOGIN. The problem is most prevalent while viewing a SCO console session [tty01 - tty12] that is AT LOGIN and attempting to login. The session may hang or lockup at the password prompt due to the fact we can not complete the password read. DoubleVision version 3.00.01 Build #5 solves this problem. [SCO] Restore the /etc/inittab file during DoubleVision's installation and removal. ------------------------------------------------------------------ During the installation and removal of DoubleVision we backup important system files, one of those being "/etc/inittab". We backup these files for safety sake. We now restore the backed up copy of "/etc/inittab" after the kernal is relinked in the installation and removal scripts. The purpose for doing this is to preserve the original "/etc/inittab" in case the file is reconstructed during the kernel re-link phase. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** ***************** Solaris SPARC 2.5/2.6/2.7 PLATFORM ************* ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.05.00 BUILD #3 ****** ****************************************************************** [SOLARIS] Port completed to Solaris SPARC 2.7. ------------------------------------------------------------------ Version 3.05.00 Build #3 was ported to the Solaris SPARC 2.7 platform. [SOLARIS] Unable to establish proper viewing access rights for system user's with a UID value greater then 64K. ------------------------------------------------------------------ In previous versions of DoubleVision 3.0 for Solaris SPARC proper security authorization could not be verified on system users with a UID value greater then 64K. The problem manifests itself while using Privileged User or Group, User or Group ACL, or local .dvsc files for remote control access rights. DoubleVision would not allow this type of user to take remote control even if set up properly in the respective remote control access rights file. This problem is resolved in DoubleVision version 3.03.00 Build #3 and version 3.00.00 Build #3. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** ***************** Solaris Intel 2.6/2.7 PLATFORM ***************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.00.01 BUILD #2 ****** ****************************************************************** [SOLARIS x86] Port completed to Solaris Intel 2.6 and 2.7 ------------------------------------------------------------------ Version 3.00.01 Build #2 was ported to the Solaris Intel 2.6 and 2.7 platform. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** ******************* SCO UNIX/MPX 3.2.4.X/3.2.5.X ***************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.00.01 BUILD #4 ****** ****************************************************************** [SCO] Additional support for Digiboard's terminal boards has been provided for. The DoubleVision digiboard trigger makes use of the "ditty" command. The newer ditty version requires a command line syntax change. DoubleVision version 3.00.01 Build #4 now supports the old ditty command line syntax that requires input re-direction as well as the new command line syntax which requires the device as a command line argument. DoubleVision version 3.00.01 Build #4 also supports MPI driver versions 2.9.2 - 3.2.2 which are known as the "buggy" versions of the MPI driver. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** ******************* Solaris Intel 2.6 PLATFORM ******************* ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.00.01 BUILD #2 ****** ****************************************************************** [SOLARIS x86] Port completed to Solaris Intel 2.6 ------------------------------------------------------------------ Version 3.00.01 Build #2 was ported to the Solaris Intel 2.6 platform. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** ********************* HP-UX 10.10 PLATFORM *********************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.00.03 BUILD #3 ****** ****************************************************************** [HPUX] Port completed to HPUX 10.10 ------------------------------------------------------------------ Version 3.00.03 Build #3 was ported to the HPUX 10.10 platform. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** ********************* HP-UX 10.20 PLATFORM *********************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.00.03 BUILD #2 ****** ****************************************************************** [HPUX] SAM cannot relink kernel after installing DoubleVision. ------------------------------------------------------------------ Only when installing DoubleVision 3.00.03 Build#1 on an HP-UX system 10.20 which has DoubleVision 2.0.23 Builds 1 through 4 or when installing again over DoubleVision 3.00.03 Build #1 would an error be instroduced which would cause HP's SAM utility to fail to link the kernel. The cause of the error was the accidental removal of the file : /usr/conf/master.d/rcon which is one of DoubleVision's device driver specification files. The file is not be needed if one links the kernel manually. But when using the SAM utility, SAM analyzes the HP-UX kernel based on the information found in the HP 'system file', and failure to have the proper file in the /usr/conf/master.d directory would cause SAM to report an error rightly so. This version ( DoubleVision 3.00.03 Build# 2 ) ensures that when installing a newer version of DoubleVision on a system which currently has a copy of DoubleVision installed, will not loose this or other critical files. [HPUX] Highest minor number limit detected during installation. ------------------------------------------------------------------ DoubleVision 3.00.03 Build #2 now has the added feature of analyzing the system's terminal minor number distribution and of configuring itself automatically. All previous versions of DoubleVision would use a safe low terminal minor number default. This would be an incovenience for those systems whose terminal devices use very high minor numbers. If fact higher than the safe default. The user would have to figure out ( or call tech support ) to determine what the new highest minor number is, and to then update the default file variable : SEARCHED_MINOR_NUM_HARD_LIMIT to reflect this new value. Not to mention that then one would have to reboot the machine for this value to take effect. Now at installation time the system is scanned and the default file is automatically configured for the user. If at any time additional terminal devices are added to the system then the utlity program : /usr/lib/dv/update_minor can be run to re-configure DoubleVision's default file. But the system will then have to be rebooted for the new limit to take effect. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** ******************** NCR Unix 3.X PLATFORM ********************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.04.00 BUILD #1 ****** ************************* AS OF 3/22/99 ************************** ****************************************************************** [NCR] Cannot determine number of CPUs on system. ------------------------------------------------------------------ NCR 3.02.00 introduced a bug where the operating system call used to deterine the number CPUs the current platform has was broken. To be precise backwards compatibility with the manner in which the number of CPUs used to be determined was broken. For that reason any version of DoubleVision prior to DV 3.04.00 Build#1 ( as of 3/22/99 ) would report -1 number of CPUs. DoubleVision 3.04.00 Build# 1 downloaded or distributed on physical media as of 3/22/99 do not have this problem. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** **************** AIX 3.2.X/4.1.X/4.2.X/4.3.X ********************* ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.00.04 BUILD #2 ****** ****************************************************************** [AIX 3.2.X] Port completed to AIX 3.2.X ------------------------------------------------------------------ Version 3.00.04 Build #2 was ported to the AIX 3.2.X platform. [AIX] Added more robust error messaging to tlalicense. [ALL] All subsequent releases of DoubleVision will contain this tlalicense enhancement. ------------------------------------------------------------------ Enhanced error messaging was added to /usr/lib/dv/tlalicense on release 3.00.04 Build #2 to assist with troubleshooting of licensing problems. [AIX] Added License Agreement viewing instructions to tlalicense. [ALL] All subsequent releases of DoubleVision will contain this tlalicense enhancement. ------------------------------------------------------------------ Instructions on how to scroll through the screen pages of the License Agreement have been added to DoubleVision release 3.00.04 Build #2. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** ********************** AIX 4.1.X/4.2.X/4.3.X ********************* ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.00.04 BUILD #1 ****** ****************************************************************** [AIX] Support added for pre-configured STREAMS stack. ------------------------------------------------------------------ This version of DoubleVision ( and all subsequent STREAMS based versions as well ) now support having the remote control STREAMS module pre-configured onto a HOST terminal's STREAMS stack. When a terminal has the remote control STREAMS module pre-configured on its stack, DoubleVision will not be required not to reconstruct the HOST terminal's STREAM stack in order to perform terminal remote control. Not having to reconstruct a HOST terminal's STREAM stack can avoid potential complications with the operating system ( see next note below ). If the operating system has a buggy implementation of the STREAMS environment OR if the device driver which controls the HOST terminal device is not able to support the stack being reconstructed are such examples of such complications. This new feature is automatic within DoubleVision. No external configuration is needed. To test for the presence of the remote control STREAMS module on any given host terminal issue the following command : strconf < /dev/tty??? where /dev/tty??? is the HOST terminal device name, and the output is similar to what follows : tioc ldterm rcsrv <<<<< Remote control server module. pts [AIX] Randmon 'stair stepping' effect problem on HOST terminal solved. ------------------------------------------------------------------ On some versions of AIX and mostly on terminals connected to a 128 port board concentrator, stair stepping will occur on the HOST terminal only. The REMOTE terminal does NOT see this problem. The stair stepping effect starts as soon as the terminal is viewed ( remote controlled ) or preattached. Even after issuing the command : stty sane or stty onlcr the problem still persists. Only by disconnecting from the HOST terminal and logging out does the stair stepping effect disappear. When stair stepping occurs the output of an 'ls' command would look somewhat as follows : .mlaact 3.2.4 3.2.4.0 3.2.5 The problem is caused by a bug in the STREAMS subsystem and sometimes within the native terminal driver where it looses the state of the 'on-newline to newline-carriage-return' mapping. The state of this mapping is lost when the STREAMS stack is reconstructed by DoubleVision in order to perform terminal level remote control. To solve the stair stepping problem one must pre-configure the STREAMS stack to contain the DoubleVision remote control server module on the STREAMS stack. One way to accomplish the 'pre-configuring' of the STREAMS stack under AIX would be to issue the following command while as the super user ( root ) : chdev -l tty0 -a modules='rcserver,ldterm,tioc' where 'tty0' is the terminal that needs to be pre-configured. An alternative method to the above example would be to perform the following steps using AIX's system administration tool 'SMIT' : 1- become root. 2- smit 3- Select 'Devices' option. 4- Select 'TTY' option. 5- Select 'Change / Show Characteristics of a TTY' option. 6- Select the terminal which exhibits stair stepping problem from the pull down list. 7- Select 'STREAMS modules to be pushed at OPEN time'. 8- Press F7 to select the 'EDIT' option. 9- Insert 'rcsrv,' at the begining of the list of STREAMS modules to push on the stack. Since there is no 'real' insert mode with this option one needs to retype the entire line. For example the list would like as follows BEFORE it is edited : ldterm,tioc and after it is edited the list would look as follows : rcsrv,ldterm,tioc 10-Press [ENTER] to accept the value entered. 11-Press [ENTER] again to process the requested change. 12-Press F10 to exit from SMIT. The above steps may not be identical from one version of AIX to another since SMIT is changed ever so slightly from one version of AIX to another. But in general one can figure out where does the 'edit list of STREAMS modules to push' option appears within SMIT. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** ******************* SCO UNIX/MPX 3.2.4.X/3.2.5.X ***************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.00.01 BUILD #3 ****** ****************************************************************** [SCO] Support added for SCO UNIX 3.2.4.0 and 3.2.4.1 ------------------------------------------------------------------ Previously only DoubleVision 2.0.13 or lower supported SCO UNIX releases 3.2.4.0 or 3.2.4.1. There exist subtle differences between the kernels for the above versions of SCO UNIX and the kernels starting with SCO UNIX 3.2.4.2. DoubleVision 3.0 was ported to the earlier releases of SCO UNIX. The integrated distribution package will now auto-detect the presence of the earlier releases of SCO UNIX and install the appropiate 3.0 binaries and drivers. [SCO] Support was added for Digiboard's new MPI 3.2.X drivers. ---------------------------------------------------------------------- With MPI driver's 3.2.0 and higher one of the programs ( commands ) that is distributed with every Digiboard was modified drastically. The 'ditty' command was changed such that stardard input/output can no longer be re-directed to it. Also terminal device names cannot have the '/dev/' path name present when passed as a command line option. This release of DoubleVision contains the newly updated triggers program which interacts with the new and old ditty commands. The effect of this added support is that users can take control of a host terminal's keyboard which is in turn connected onto a Digiboard. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** ********************* HP-UX 10.20 PLATFORM *********************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.00.03 BUILD #1 ****** ****************************************************************** [HPUX] Double echo of characters on terminals problem. ================================================================== Only under HP-UX 10.20 and DoubleVision version 2.0.23 and higher and some systems with terminal concentrators would it be possible for a terminal to enter permanently into 'double echo' mode after it was remotely controlled or pre-attached by DoubleVision. This release of DoubleVision now has a new default variable flag named : DISABLE_SESSION_ON_VIEW_EXIT=NO By default this variable is disabled. When it is enabled, DoubleVision will terminate any remote control session as soon as the user exits from actively viewing a terminal and proceed to reset the host terminal's driver. This is done in order to eliminate the possibility of the terminal entering into the permanent 'double echo' mode again. Users who have or do experienced this problem should proceed to enable the above default file flag in order to prevent any further occurances of double echoed terminals. The disadvantage to enabling this control variable will be that no terminal can be pre-attached on the system. If a terminal should enter into 'double echo' mode even after having enabled the above default file variable, a user can reset the terminal at any time as follows : dv -d ttyname where 'ttyname' is the device name of the terminal which is experiencing the 'double echo' problem. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** ********************* HP-UX 10.20 PLATFORM *********************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.00.02 BUILD #1 ****** ****************************************************************** [HPUX] Function keys causing tty driver to lock up. ================================================================== Only under HP-UX 10.20 and any version of DoubleVision 2.0.12 and higher it was possible for a user to sent from the remote terminal a series of function keys over to the host terminal. After the sequence was sent sometimes at random the host tty driver become confused and/or locked up. Application would seem not to be able to read from its keyboard and at times not to be able to sustain a subsequent login process. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** ******************** NCR Unix 3.X PLATFORM ********************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.04.00 BUILD #1 ****** ****************************************************************** [NCR] Psuedo-tty issues. ========================================================================== When connecting to a psuedo-tty via DoubleVision and then proceeding to logout the psuedo-tty, DoubleVision cannot sense the psuedo-tty being deconstructed. This has to do with how the psuedo-tty mechanism is implemented under NCR. This always happens with psuedos of the name format : nty/NNN The effect to DoubleVision users will be that when a pseudo-terminal is logged out through DoubleVision, the remote control connection will NOT be by severed until the user EXITS from DoubleVision's own user interface. The second effect will be if a user is recording a session of a psuedo-terminal and the psuedo-terminal is logged out, lingering processes will be left over. The processes are : dvscreen dvrecord As they remain active thinking that the psuedo-tty is still present. It is safe to kill -1 such processes. [NCR] Problem dates for the recorder module. ========================================================================== We expereinced date conversion problems at random when the recorder module would schedule a session into the future with any of the following dates : 12/31/1999 ... Erratic behaviour. 01/01/2000 ... Erratic behaviour. 01/20/2000 ... Erratic behaviour. 04/05/2010 ... Erratic behaviour. 02/29/2000 ... Erratic behaviour. 01/01/2100 ... Not tested, NCR supports dates up to 2037 via the internal 'getdate' function. An error is logged in the DoubleVision error log file : /usr/adm/DVLOG and the text of the message will be as follows : Possible recording date conversion problem What this means to the users is that the recorder module may or may not be able to schedule a future recording when the system's date is anywhere past the year 2000. It is possible that with future patches from NCR this will not be an issue at all. [NCR] NO RESPONSE FROM HOST TERMINAL ===================================== If you attempt to view a terminal and you are not getting any response, first make certain that the terminal is properly configured, etc. If all else fails, the drivers could have gotten out of sync. To correct this, issue the following command: dv -d ttyname where ttyname is the terminal device your are trying to view. [NCR] NCR CONSOLE DRIVER/EMULATOR PROBLEM ========================================= The emulator does not support the following commands, contrary to what the manual states, and contrary to other versions of UNIX who support the at386 console. \E[=14;12C \E[=15;16C \E[=16;16C \E[=16;0C \E[=11;12C \E[=0;12C \E[=9;12C \E[=10;12C \E[=11;12C \E[=12;12C The implication here is that when a DoubleVision session runs on the console, these escape sequences will appear on the screen. The at386 emulator, just 'throws' them back on the screen. These escape sequence are supposed to control the number of scan lines to display for the cursor, thus controlling the cursor size. If this is creates a problem, these sequences can be ignored by changing the associated command description in the at386 terminal database to 'Ignore'. This database is located in the /usr/lib/dv/termdb directory. [NCR] ONLY USERS LOGGED IN ARE DISPLAYED ========================================= Only users that are logged in will be displayed on the terminal list. If you wish to view a terminal that is not logged in, you may add it to the terminal list using the New command. Showing all terminals, including those at login, will be added in the a subsequent release. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** ******************* SCO UNIX/MPX 3.2.4.X/3.2.5.X ***************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.00.01 BUILD #2 ****** ****************************************************************** [SCO] [ALL] Handling of 'NULL' controlling terminal names. ------------------------------------------------------------------ Version 3.00.01 Build#2 of DoubleVision was released solely to handle those operating systems whose 'ttyname( S )' function fails to return at times the name of the controlling terminal. In other words any application under UNIX if not running in the background will have a controlling terminal. In some cases this information is not available via the 'ttyname( S )' function. When such condition occurs, DoubleVision will automatically use the psuedo device '/dev/tty' as its controlling terminal. This problem was first ever encountered under SCO 3.2.5.5 with Equinox terminal I/O boards. [SCO] Minor number mapping. ------------------------------------------------------------------ Starting with Version 3.00.01 Build#2 of DoubleVision, minor number mapping to and from modem devices are no longer performed by default. To re-enable this feature modify the default file variable as follows : GLOBAL_CAN_UNMODEM_MINOR_NUMS = YES Minor number mapping is no longer a major requirement since it is rare that a user would view at the same time the modem vs the non-modem device. For example : a remote control session on /dev/tty1a and /dev/tty1A being held at the same time. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.01.00 BUILD #1 ****** ****************************************************************** [SCO Unixware] Port completed to SCO Unixware 2.X ------------------------------------------------------------------ Version 3.02.00 Build #1 was ported to the SCO Unixware 2.X platform. ****************************************************************** ******************* THE FOLLOWING NOTES ARE FOR : **************** ****** THE FOLLOWING NOTES ARE FOR RELEASE 3.00.00 BUILD #1 ****** ****************************************************************** ****************************************************************** ******************** Solaris SPARC PLATFORM ********************** ***** THE FOLLOWING NOTES ARE FOR RELEASE 3.00.00 BUILD #2 ******* ****************************************************************** [Solaris SPARC] Removed 'BETA' file maker from distribution. ------------------------------------------------------------------ Removed the empty file marker from the distribution and renamed the BUILD version to BUILD #2. ================================================================== GENERAL NOTES ================================================================== Some items will apply to all DoubleVision releases, while others will be platform specific. Below is a legend of the notations used. LEGEND: ------- [ALL] All DoubleVision releases [SCO] SCO UNIX, MPX, and SCO XENIX releases [HPUX] HP-UX releases [AIX] IBM AIX releases [ISC] INTERACTIVE UNIX releases [NCR] NCR UNIX SVR4.0 Versions 2.0, (2.00.01) and Version 3.0 (2.00.02) [UW] UNIVEL UNIXWARE SVR4.2 [SCO UW] SCO UNIXWARE 2.0/7.X [SVR4] ALL SVR4.0 and SVR4.2 releases [DGUX] DATA GENERAL UNIX releases [SOLARIS] Sun SOLARIS SPARC 2.x releases [SOLARIS x86] Sun SOLARIS INTEL 2.x releases [UNISYS] UNISYS Uni- and Multi-Processor [LINUX INTEL] Linux on Intel releases ================================================================== SUPPORTED I/O BOARDS ================================================================== DoubleVision has been tested successfully on the following I/O boards: Arnet Arnet Cluster Board Comtrol RocketPort Digiboard family of boards Equinox Equinox Super Serial Specialix family of boards Stallion family of boards IBM7318 Terminal Server NOTE: DoubleVision will work on all other non-intelligent serial I/O boards. NOTE: All intelligent serial I/O boards not included in this list must have on-board processing turned off when attaching to a terminal on the serial I/O port. ================================================================== TRUESCREEN(TM) SUPPORTED TERMINALS ================================================================== DoubleVision'S TrueScreen feature supports the following terminals: AT&T ---- ATT4410 ATT605 ATT610 ATT615 ATT620 ADDS ---- ADDS Viewpoint ADDS 2020 ADDS 4000 DATA GENERAL ------------ DATA GENERAL DASHER 6053 DATA GENERAL DASHER 200 DATA GENERAL DASHER 210 DATA GENERAL DASHER 211 DATA GENERAL DASHER 214 DATA GENERAL DASHER 215 DATA GENERAL DASHER 216 DATA GENERAL DASHER 217 DATA GENERAL DASHER 230C DATA GENERAL DASHER 400 DATA GENERAL DASHER 410 DATA GENERAL DASHER 411 DATA GENERAL DASHER 412 DATA GENERAL DASHER 413 DATA GENERAL DASHER 450 DATA GENERAL DASHER 460 DATA GENERAL DASHER 461 DATA GENERAL DASHER 462 DATA GENERAL DASHER 463 DATA GENERAL DASHER 470 DATA GENERAL DASHER 555 DATA GENERAL DASHER 577 DATA GENERAL DASHER 578 DEC --- DEC VT52 DEC VT100 DEC VT220 DEC VT240 DEC VT241 DEC VT320 DEC VT340 DEC VT420 HEWLETT-PACKARD --------------- HP2382 HP2392 HP2393 HP2394 HP2397 HP2621 HP2622 HP2623 HP2624 HP2625 HP2626 HP2627 HP2628 HP2703 HP2709 HP70092 HP70094 HP70096 HP70060 HP928 hpterm A208LC1280 IBM --- IBM HFT IBM 3151 IBM 5151 IBM 6153 MAI --- MAI 4309 MAI 4310 MAI 4312 MAI 4313 MAI 4314 MAI 4315 NCR --- NCR 2900 NCR 4940 NCR 2920 QUME ---- QUME 51 QUME 101, 101+ QUME 102 QUME 108 QUME 109 QUME 119, 119+ TEXAS INSTRUMENTS --------