Banyan VINES resurrection - Revision history

JQW: minor edits

2024-06-15T15:18:48Z

minor edits

← Older revision		Revision as of 15:18, 15 June 2024
Line 303:		Line 303:

	==== VINES 3.xx ====		==== VINES 3.xx ====
	*VINES/386, for 386 based PC servers,		*VINES/386, for 386 based PC servers.
	*VINES/TEAM, a cheaper version which supported a restricted number of users.		*VINES/TEAM, a cheaper version which supported a restricted number of users.
	*Banyan also introduced their serial controller, the ICA.		*Banyan also introduced their serial controller, the ICA.
	* VINES/386 3.00 appears to have been limited to the Compaq Deskpro 386.		* VINES/386 3.00 appears to have been limited to the Compaq Deskpro 386. More plaforms were supported with VINES 3.10.

	==== VINES 4.00 ====		==== VINES 4.00 ====
Line 318:		Line 318:
	=====VINES 4.10 =====		=====VINES 4.10 =====
	*added support for Windows 3.0 and OS/2 1.x clients.		*added support for Windows 3.0 and OS/2 1.x clients.
	*There were changes made at the session level to allow workstations to multiple sessions ~~to be made~~ with some services simultaneously.		*There were changes made at the session level to allow multi-tasking workstations to have multiple sessions with some services simultaneously.
	*The initial release of 4.10 had a serious bug which would lead to file system corruption on certain file truncation operations.		*The initial release of 4.10 had a serious bug which would lead to file system corruption on certain file truncation operations.

BlackCoffeeDrinker: Organized the new per version better

2024-05-03T21:01:59Z

Organized the new per version better

← Older revision		Revision as of 21:01, 3 May 2024
Line 295:		Line 295:
	The early history of VINES is lost, with very little surviving. Here's a brief, but incomplete, history of changes.		The early history of VINES is lost, with very little surviving. Here's a brief, but incomplete, history of changes.

	VINES 1.xx ~~was only~~ available on Banyan's own BNS servers, which were 680x0 based.		====VINES 1.xx====
			*Only available on Banyan's own BNS servers, which were 680x0 based.

	VINES 2.xx introduced support for Banyan's DTS (Desktop) servers~~, and~~ VINES/286 which ran on IBM AT and clones.		====VINES 2.xx====
			*introduced support for Banyan's DTS (Desktop) servers
			*VINES/286 which ran on IBM AT and clones.

	VINES 3.xx ~~introduced~~ VINES/386, for 386 based PC servers, ~~and~~ VINES/TEAM, a cheaper version which supported a restricted number of users. Banyan also introduced their serial controller, the ICA. VINES/386 3.00 appears to have been limited to the Compaq Deskpro 386.		==== VINES 3.xx ====
			*VINES/386, for 386 based PC servers,
			*VINES/TEAM, a cheaper version which supported a restricted number of users.
			*Banyan also introduced their serial controller, the ICA.
			* VINES/386 3.00 appears to have been limited to the Compaq Deskpro 386.

	VINES 4.00 introduced major changes to StreetTalk - changes to the way it updated meant that the the special group Servers@Servers was no longer required. VINES 4.00 was also the first version of VINES to support the MS-DOS 3.1 network API. ~~It was also the first~~ version of VINES to support 486 servers. 4.00 was also the last version to be released for 680x0 and 286 based servers. VINES 4.00 also introduced the STDA directory assistant service, in the form of patch 4.00(1).		==== VINES 4.00 ====
			*introduced major changes to StreetTalk
			**changes to the way it updated meant that the the special group Servers@Servers was no longer required.
			*VINES 4.00 was also the first version of VINES to support the MS-DOS 3.1 network API.
			*First version of VINES to support 486 servers.
			*4.00 was also the last version to be released for 680x0 and 286 based servers.
			*VINES 4.00 also introduced the STDA directory assistant service, in the form of patch 4.00(1).

	VINES 4.10 added support for Windows 3.0 and OS/2 1.x clients. There were changes made at the session level to allow workstations to multiple sessions to be made with some services simultaneously. The initial release of 4.10 had a serious bug which would lead to file system corruption on certain file truncation operations.		=====VINES 4.10 =====
			*added support for Windows 3.0 and OS/2 1.x clients.
			*There were changes made at the session level to allow workstations to multiple sessions to be made with some services simultaneously.
			*The initial release of 4.10 had a serious bug which would lead to file system corruption on certain file truncation operations.

	VINES 4.11 ~~was~~ a new cut of 4.10 to add support for additional server storage hardware.		=====VINES 4.11 =====
			* Was a new cut of 4.10 to add support for additional server storage hardware.

	VINES 5.00 added support for Apple Macs and file access rights on a per file basis. This was a fork of 4.10 so didn't support the new hardware platforms introduced in 4.11. The default S5 filesystem was replaced with the S10 one - under the S5 filesystem servers could run out of inodes despite having plenty of spare disk space.		==== VINES 5.00====
			*added support for Apple Macs and file access rights on a per file basis.
			** This was a fork of 4.10 so didn't support the new hardware platforms introduced in 4.11.
			*The default S5 filesystem was replaced with the S10 one
			**under the S5 filesystem servers could run out of inodes despite having plenty of spare disk space.

	VINES 5.50 added 4.11's hardware support to the other features of 5.00. The routing protocol used between servers was changed to one that generates far less traffic on large networks.		=====VINES 5.50=====
			*added 4.11's hardware support to the other features of 5.00.
			*The routing protocol used between servers was changed to one that generates far less traffic on large networks.

	VINES 5.52, 5.53 and 5.54 added additional server hardware support.		===== VINES 5.52, 5.53 and 5.54 =====
			*added additional server hardware support.

	VINES 6.00 added loadable device drivers and root access. Loadable device drivers were now available for storage adaptors and network interfaces. StreetTalk was also enhanced, allowing read-only copies of groups to be shadowed to other servers, and allowing some additional characters in item names.		====VINES 6.00 ====
			*added loadable device drivers and root access.
			*Loadable device drivers were now available for storage adaptors and network interfaces.
			*StreetTalk was also enhanced, allowing read-only copies of groups to be shadowed to other servers, and allowing some additional characters in item names.

	VINES 6.20, 6.30 and 6.40 were maintenance releases of 6.00, issued as sets of patches.		=====VINES 6.20, 6.30 and 6.40=====
			* were maintenance releases of 6.00, issued as sets of patches.

	VINES 7.00 added support for larger filesystems (previously they were limited to 2GB), together with long filename support from certain clients. The root filesystem was also enlarged to circumvent installation problems seen with VINES 6.xx. VINES 7.00 also introduced paper-based server keys and option codes, although dongles could still be used. Patches were also issued to allow paper-based option keys to be used with previous VINES revisions. The LAN server-to-server and SMP options were now bundled with the base release.		====VINES 7.00====
			*added support for larger filesystems (previously they were limited to 2GB)
			*together with long filename support from certain clients.
			*The root filesystem was also enlarged to circumvent installation problems seen with VINES 6.xx.
			*VINES 7.00 also introduced paper-based server keys and option codes, although dongles could still be used.
			* Patches were also issued to allow paper-based option keys to be used with previous VINES revisions.
			*The LAN server-to-server and SMP options were now bundled with the base release.

	VINES 7.10 was a maintenance release for 7.00, applied as a set of patches. There were no significant new features.		=====VINES 7.10=====
			*was a maintenance release for 7.00, applied as a set of patches.
			*There were no significant new features.

	VINES 8.00 added very little other than support for MPS 1.4, ~~and~~ support for add-on ISDN card drivers (although none seem to have been released). SMP had been supported since at least VINES 4.00 on certified hardware, but needed to be installed from SMP specific media. VINES 8.00 was unique in that it didn't have its own option bit, and could be installed on any existing VINES 7.00 server.		====VINES 8.00 ====
			*added very little other than support for MPS 1.4,
			*support for add-on ISDN card drivers (although none seem to have been released).
			*SMP had been supported since at least VINES 4.00 on certified hardware, but needed to be installed from SMP specific media.
			*VINES 8.00 was unique in that it didn't have its own option bit, and could be installed on any existing VINES 7.00 server.

	VINES 8.50 was the Y2K compliant version of 8.00. Some services and features were not supported beyond 1999 for various reasons, although these services continued to run.		=====VINES 8.50=====
			* was the Y2K compliant version of 8.00.
			*Some services and features were not supported beyond 1999 for various reasons, although these services continued to run.

	VINES 8.60 was the final release of VINES, containing all of the maintenance patches issued for VINES 8.50 since its release.		=====VINES 8.60=====
			*was the final release of VINES, containing all of the maintenance patches issued for VINES 8.50 since its release.

			====VINES ENS====
	There was also a product named ENS for Netware that allowed Netware servers to use StreetTalk. Initially these used their own special ENS servers, which were cut down VINES servers. ENS 1.00 was effectively VINES 5.20, and ENS 1.1 was VINES 5.30. A server running VINES 5.50 onwards could also act as an ENS server with the relevant software option. The Netware NLM and ENS client files are currently lost, as are media for the two ENS server releases.		There was also a product named ENS for Netware that allowed Netware servers to use StreetTalk. Initially these used their own special ENS servers, which were cut down VINES servers. ENS 1.00 was effectively VINES 5.20, and ENS 1.1 was VINES 5.30. A server running VINES 5.50 onwards could also act as an ENS server with the relevant software option. The Netware NLM and ENS client files are currently lost, as are media for the two ENS server releases.

			==== VINES UNIX====
	There were also versions of VINES released for some versions of commercial UNIX - SCO Unix, Solaris, HP-UX and AIX, the latter running on the RS/6000. Some of these were issued under ENS branding. None of these appear to have survived.		There were also versions of VINES released for some versions of commercial UNIX - SCO Unix, Solaris, HP-UX and AIX, the latter running on the RS/6000. Some of these were issued under ENS branding. None of these appear to have survived.

			====StreetTalk for NT====
	Banyan also issued a VINES implementation that ran on Windows NT entitled StreetTalk for NT. There were also several other NT based software, including a webmail gateway for Intelligent Messaging under IIS, and software to allow an NT drive to act as a VINES file service.		Banyan also issued a VINES implementation that ran on Windows NT entitled StreetTalk for NT. There were also several other NT based software, including a webmail gateway for Intelligent Messaging under IIS, and software to allow an NT drive to act as a VINES file service.
	== What's Missing ==
			==What's Missing==
	An incomplete list of currently missing software:		An incomplete list of currently missing software:

JQW: Updated to reflect recently recovered software, plus a few other edits.

2024-05-03T14:05:39Z

Updated to reflect recently recovered software, plus a few other edits.

← Older revision		Revision as of 14:05, 3 May 2024
Line 37:		Line 37:
	The installation process would create a root partition (6MB initially, 32MB from VINES 7.00 onwards), and a swap partition, under which the core Unix system was installed. The remainder of the disk would become a second partition named ''/disk1'', under which the rest of the OS would reside, together with server data. Prior to VINES 7.00, additional partitions would be created, if necessary, named ''/disk2'' onwards, due to a 2GB limitation on disk partitions. Additional drives could be installed and partitioned once the main operating system was installed.		The installation process would create a root partition (6MB initially, 32MB from VINES 7.00 onwards), and a swap partition, under which the core Unix system was installed. The remainder of the disk would become a second partition named ''/disk1'', under which the rest of the OS would reside, together with server data. Prior to VINES 7.00, additional partitions would be created, if necessary, named ''/disk2'' onwards, due to a 2GB limitation on disk partitions. Additional drives could be installed and partitioned once the main operating system was installed.

	VINES service binaries were stored in their particular directory under ''/disk1/banyan'', with third-party binaries under ''/disk1/local''. Each directory contained the ~~server~~ binary, scripts for starting, creating and deleting services, log files, and so forth.		VINES service binaries were stored in their particular directory under ''/disk1/banyan'', with third-party binaries under ''/disk1/local''. Each directory contained the service binary, scripts for starting, creating and deleting services, log files, and so forth.
	== Installing The Server ==		== Installing The Server ==
	Installation media has been recovered for VINES 5.00, 5.54, 7.00 and 8.50. VINES 5.00 and ~~5.54~~ came as a stack of floppies, whilst 7.00 and 8.50 consisted of five floppies and a CD-ROM ISO. Images of the VINES 6.00 floppies have also been recovered, but the CD-ROM image is still missing.		Installation media has been recovered for VINES 3.00, 4.00, 5.00, 5.52, 5.54, 6.00, 7.00 and 8.50. VINES 5.54 and earlier came as a stack of floppies, whilst 6.00 and 8.50 consisted of five floppies and a CD-ROM ISO. Images of the VINES 6.00 floppies have also been recovered, but the CD-ROM image is still missing.

	Some releases of VINES were supplied with a pack-in patch on one or two floppies that either fixed serious issues or added a feature that wasn't ready when the gold master was produced. This would need to be applied once the server was up and running and would change the patch level of the server. For example, VINES 4.00 came with the 4.00(1) patch which added the STDA service, whilst VINES 6.00 came with the 6.00(1) patch to resolve a potential issue with the mail service.		Some releases of VINES were supplied with a pack-in patch on one or two floppies that either fixed serious issues or added a feature that wasn't ready when the gold master was produced. This would need to be applied once the server was up and running and would change the patch level of the server. For example, VINES 4.00 came with the 4.00(1) patch which added the STDA service, whilst VINES 6.00 came with the 6.00(1) patch to resolve a potential issue with the mail service.

	Most versions can be installed without the need for a server key, by gaining root access and editing some files. CD based versions tend to require a SCSI CD-ROM drive - although there were drivers released for Compaq and HP based ATAPI drives, these were tied to specific server hardware. IDE hard drives are supported but are limited to a maximum capacity of 504MB on most systems.		Most versions can be installed without the need for a server key, by gaining root access and editing some files. CD based versions tend to require a SCSI CD-ROM drive - although there were drivers released for Compaq and HP based ATAPI drives, these were tied to specific server hardware. IDE hard drives are supported but are limited to a maximum capacity of 504MB on most systems.

			VINES 3.00 appears to only install on machines fitted with certain Compaq video adaptors, as the installation kernel seems to use some Compaq specfic video code that fails on other hardware.

			There's a logic hole in the VINES 4.00 installer that causes an essential startup file to be removed from the installation if a valid server key can't be found, prompting a reload of the whole OS from release media on reboot. To get around this press CTRL-ALT-DEL as soon as the final installation floppy has been installed.
	==== Installing under VirtualBox ====		==== Installing under VirtualBox ====
	The system can be installed under VirtualBox, but requires version 7.0.0, as this fixes an issue with the floppy drive support, and also adds support for legacy ISA network cards. As VINES's support for IDE drives was somewhat limited, with a limit of 504MB per drive and no UDMA support, it's best to configure the VM to use a BusLogic SCSI adaptor. VINES's Adaptec SCSI driver should work with such a controller in ISA emulation mode, but it only probes the ISA I/O address of 0x330h for such a controller, whilst VirtualBox's driver defaults to 0x338h instead. Thankfully VirtualBox's BusLogic SCSI adaptor's ISA I/O address can be changed by using the following command: <syntaxhighlight lang="dosbatch">		The system can be installed under VirtualBox, but requires version 7.0.0, as this fixes an issue with the floppy drive support, and also adds support for legacy ISA network cards. As VINES's support for IDE drives was somewhat limited, with a limit of 504MB per drive and no UDMA support, it's best to configure the VM to use a BusLogic SCSI adaptor. VINES's Adaptec SCSI driver should work with such a controller in ISA emulation mode, but it only probes the ISA I/O address of 0x330h for such a controller, whilst VirtualBox's driver defaults to 0x338h instead. Thankfully VirtualBox's BusLogic SCSI adaptor's ISA I/O address can be changed by using the following command: <syntaxhighlight lang="dosbatch">
Line 194:		Line 198:
	\|-		\|-
	\|4.00		\|4.00
	\|~~vivelaVINES~~		\|vivelaVines
	\|		\|
	\|-		\|-
Line 255:		Line 259:
	StreeTalk - ''ST@server-name@Servers'' - was the directory service. StreetTalk services maintain a list of all other services, and the groups that they contained, but would only contain full item information for its local groups. Later versions of VINES added StreetTalk shadowing, which allowed read-only copies of groups to be placed on other servers. Mandatory.		StreeTalk - ''ST@server-name@Servers'' - was the directory service. StreetTalk services maintain a list of all other services, and the groups that they contained, but would only contain full item information for its local groups. Later versions of VINES added StreetTalk shadowing, which allowed read-only copies of groups to be placed on other servers. Mandatory.
	=== StreetTalk Directory Assistant (STDA) ===		=== StreetTalk Directory Assistant (STDA) ===
	An optional service that presented details of the entire distributed StreetTalk database. Its purpose was to reduced traffic to remote StreetTalk services over slow links. STDA would rebuild its databases once a day (typically overnight). Services could be configured as Satellite STDA servcices, meaning that they picked up their data from another STDA service.		An optional service that presented details of the entire distributed StreetTalk database. Its purpose was to reduced traffic to remote StreetTalk services over slow links. STDA would rebuild its databases once a day (typically overnight). Services could be configured as Satellite STDA servcices, meaning that they picked up their data from another STDA service. Introcuded with VINES 4.00(1).

	=== VINES Security ===		=== VINES Security ===
	VINES Security - ''VS@sever-name@Servers'' (or ''VanGuard@server-name@Servers'' in early releases) looked after security sessions, validating a user or service's security tokens. It would poll workstations occasionally to keep sessions alive. Mandatory.		VINES Security - ''VS@sever-name@Servers'' (or ''VanGuard@server-name@Servers'' in early releases) looked after security sessions, validating a user or service's security tokens. It would poll workstations occasionally to keep sessions alive. Mandatory.
Line 267:		Line 272:
	A print queue. By default these could only be connected to parallel or serial ports on the server itself. With the PC Print option installed these services could also be mapped to PC based printers (the PC had to be running the PCPRINT.EXE TSR) or Banyan compatible print servers. Apple connected PAP printers were also supported.		A print queue. By default these could only be connected to parallel or serial ports on the server itself. With the PC Print option installed these services could also be mapped to PC based printers (the PC had to be running the PCPRINT.EXE TSR) or Banyan compatible print servers. Apple connected PAP printers were also supported.
	=== NetBIOS Naming ===		=== NetBIOS Naming ===
	Banyan's implementation of NetBIOS allowed clients to talk to each other over NetBIOS even if they were attached to different LAN segments. They did this via a NetBIOS naming service. The workstation had to load the additional NetBIOS TSR, and issue a SETNETB command to connect to the relevant NetBIOS naming service.		Banyan's implementation of NetBIOS allowed clients to talk to each other over NetBIOS even if they were attached to different LAN segments. They did this via a NetBIOS naming service which co-ordinated machine names. The workstation had to load the additional NetBIOS TSR, and issue a SETNETB command to connect to the relevant NetBIOS naming service.
	=== Semaphore ===		=== Semaphore ===
	Like NetBIOS, Banyan also supported the old DOS Semaphore API over the entire network, using a TSR and service. This was obsolete by the early 1990s.		Like NetBIOS, Banyan also supported the old DOS Semaphore API over the entire network, using a TSR and service. This was obsolete by the early 1990s.
Line 283:		Line 288:
	Optional management tools comprising of a suite of utilities, plus a server-based service that monitored its server and sent out alerts if certain thresholds had been met.		Optional management tools comprising of a suite of utilities, plus a server-based service that monitored its server and sent out alerts if certain thresholds had been met.

	Third Party Services		=== Third Party Services ===

	Other developers could also produce services with Banyan's SDK. Example services include several mail gateways, at least two different RDBMS packages, calendaring tools, and ports of various TCP/IP services such as DNS and LPR. Prior to VINES 5.54 TCP/IP based services need the TCP/IP Routing option to be installed to enable the TCP/IP stack.		Other developers could also produce services with Banyan's SDK. Example services include several mail gateways, at least two different RDBMS packages, calendaring tools, and ports of various TCP/IP services such as DNS and LPR. Prior to VINES 5.54 TCP/IP based services need the TCP/IP Routing option to be installed to enable the TCP/IP stack.
	== SDK ==		== SDK ==
Line 295:		Line 299:
	VINES 2.xx introduced support for Banyan's DTS (Desktop) servers, and VINES/286 which ran on IBM AT and clones.		VINES 2.xx introduced support for Banyan's DTS (Desktop) servers, and VINES/286 which ran on IBM AT and clones.

	VINES 3.xx introduced VINES/386, for 386 based PC servers, and VINES/TEAM, a cheaper version which supported a restricted number of users. Banyan also introduced their serial controller, the ICA.		VINES 3.xx introduced VINES/386, for 386 based PC servers, and VINES/TEAM, a cheaper version which supported a restricted number of users. Banyan also introduced their serial controller, the ICA. VINES/386 3.00 appears to have been limited to the Compaq Deskpro 386.

	VINES 4.00 introduced major changes to StreetTalk - changes to the way it updated meant that the the special group Servers@Servers was no longer required. It was also the first version of VINES to support 486 servers. 4.00 was also the last version to be released for 680x0 and 286 based servers. VINES 4.00 also introduced the STDA directory assistant service, in the form of patch 4.00(1).		VINES 4.00 introduced major changes to StreetTalk - changes to the way it updated meant that the the special group Servers@Servers was no longer required. VINES 4.00 was also the first version of VINES to support the MS-DOS 3.1 network API. It was also the first version of VINES to support 486 servers. 4.00 was also the last version to be released for 680x0 and 286 based servers. VINES 4.00 also introduced the STDA directory assistant service, in the form of patch 4.00(1).

	VINES 4.10 added support for Windows 3.0 and OS/2 1.x clients. There were changes made at the session level to allow workstations to multiple sessions to be made with some services simultaneously. The initial release of 4.10 had a serious bug which would lead to file system corruption on certain file truncation operations.		VINES 4.10 added support for Windows 3.0 and OS/2 1.x clients. There were changes made at the session level to allow workstations to multiple sessions to be made with some services simultaneously. The initial release of 4.10 had a serious bug which would lead to file system corruption on certain file truncation operations.
Line 331:		Line 335:
	An incomplete list of currently missing software:		An incomplete list of currently missing software:

	VINES 2~~.xx or 3~~.xx release media and patches for PC based servers.		VINES 2.xx release media and patches for 286 based servers.

			VINES 3.10 release media.

	VINES ~~4.00,~~ 4.10 or 4.11 release media ~~and~~ maintenance patches.		VINES 4.10 or 4.11 release media, plus maintenance patches for VINES 4.00, 4.10 and 4.11.

	VINES 5.00 maintenance patches. 5.00(0) has been recovered, but has some serious bugs fixed in later maintenance releases.		VINES 5.00 maintenance patches. 5.00(0) has been recovered, but has some serious bugs fixed in later maintenance releases.

JQW: Updated list of missing software.

2023-05-26T13:05:02Z

Updated list of missing software.

← Older revision		Revision as of 13:05, 26 May 2023
Line 336:		Line 336:

	VINES 5.00 maintenance patches. 5.00(0) has been recovered, but has some serious bugs fixed in later maintenance releases.		VINES 5.00 maintenance patches. 5.00(0) has been recovered, but has some serious bugs fixed in later maintenance releases.

	~~VINES 6.00 release media. The five installation floppies have been recovered, but the corresponding CD-ROM is lost.~~

	VINES 8.00 release media.		VINES 8.00 release media.
Line 347:		Line 345:
	Documentation for the 8.60 maintenance patch.		Documentation for the 8.60 maintenance patch.

	~~SMP and MicroChannel variants of any VINES revision. The SMP version appears to have been integrated into the standard release of VINES 7.00 and above.~~		Installation media for Banyan's own hardware - BNS, DTS or CNS, together with a working server.

	Installation media for Banyan's own hardware - BNS, DTS or CNS, together with a working server~~. It may be possible to re-create the installation tape of VINES 6.00 for a CNS server from the 6.00 CD-ROM~~.

	VINES 286 - any revision.		VINES 286 - any revision.

	VINES Application Toolkit - any revision. Documentation was originally released in printed form, moving to CD-ROM with VINES 6.00.		VINES Application Toolkit - any revision. Documentation was originally released in printed form, moving to CD-ROM with VINES 6.00.

	Client for OS/2 - 1.x or 2.x. Although the relevant driver files survive as part of the core OS installation, the undocumented configuration files are missing, and efforts to recreate them have failed.

	Client for Windows 98		Client for Windows 98
Line 370:		Line 364:

	ENS for HP-UX, Solaris and AIX		ENS for HP-UX, Solaris and AIX

	~~ENS Management Tools - an early GUI for managing servers. Replaced by StreetTalk Explorer.~~

	Demarc - SNMP based management tools.		Demarc - SNMP based management tools.
Line 384:		Line 376:

	MacMail Gateway - little is known about this service. May not have been released.		MacMail Gateway - little is known about this service. May not have been released.

	~~EBR client software.~~

	FTP Software's PC-TCP suite with Banyan specific drivers, version 2.x and 3.x. IBANYAN encapsulated TCP/IP in VINES-IP, EBANYAN hooked the currently installed Ethernet driver.		FTP Software's PC-TCP suite with Banyan specific drivers, version 2.x and 3.x. IBANYAN encapsulated TCP/IP in VINES-IP, EBANYAN hooked the currently installed Ethernet driver.

	~~IPSwitch's TCP/IP suite for DOS - needed to get Banyan's DOS TCP/IP client working.~~

JQW: /* What's new per version */

2023-02-16T21:01:54Z

What's new per version

JQW: /* What's Missing */

2023-02-04T15:03:04Z

What's Missing

← Older revision		Revision as of 15:03, 4 February 2023
Line 154:		Line 154:
	A client was issued in late 1999, after Banyan had declared that they were pulling out of the market. As of yet it hasn't been recovered.		A client was issued in late 1999, after Banyan had declared that they were pulling out of the market. As of yet it hasn't been recovered.
	==== Mac System 7.0 ====		==== Mac System 7.0 ====
	There was also an extension for Mac System 7.0 to 7.5.5 added some extra functionality, although a Mac could login to VINES without it. There was also client for Banyan's E-mail system. Both have been recently recovered. ~~The extension may~~ also ~~support~~ Mac OS 8.		There was also an extension for Mac System 7.0 to 7.5.5 which added some extra functionality, although a Mac could login to VINES without it. There was also client for Banyan's E-mail system. Both have been recently recovered. This software also works with Mac OS 8.0.
	==== Others ====		==== Others ====
	There were various third-party Windows clients for Banyan's E-mail system. In addition Banyan acquired BeyondMail and offered versions 2 and 3 of that to customers.		There were various third-party Windows clients for Banyan's E-mail system. In addition Banyan acquired BeyondMail and offered versions 2 and 3 of that to customers.
Line 370:		Line 370:

	ENS Management Tools - an early GUI for managing servers. Replaced by StreetTalk Explorer.		ENS Management Tools - an early GUI for managing servers. Replaced by StreetTalk Explorer.

	~~StreetTalk for Windows NT. One release survives, but it needs an activation key to be installed.~~

	Banyan Intranet Connect - webmail portal that ran under IIS on NT.		Banyan Intranet Connect - webmail portal that ran under IIS on NT.

JQW: Update to add recovery of Mac clients.

2023-01-29T20:34:10Z

Update to add recovery of Mac clients.

← Older revision		Revision as of 20:34, 29 January 2023
Line 154:		Line 154:
	A client was issued in late 1999, after Banyan had declared that they were pulling out of the market. As of yet it hasn't been recovered.		A client was issued in late 1999, after Banyan had declared that they were pulling out of the market. As of yet it hasn't been recovered.
	==== Mac System 7.0 ====		==== Mac System 7.0 ====
	There was also an extension for Mac System 7.0 ~~and above that~~ added some extra functionality, although a Mac could login to VINES without it. There was also client for Banyan's E-mail system. Both ~~are currently lost~~.		There was also an extension for Mac System 7.0 to 7.5.5 added some extra functionality, although a Mac could login to VINES without it. There was also client for Banyan's E-mail system. Both have been recently recovered. The extension may also support Mac OS 8.
	==== Others ====		==== Others ====
	There were various third-party Windows clients for Banyan's E-mail system. In addition Banyan acquired BeyondMail and offered versions 2 and 3 of that to customers.		There were various third-party Windows clients for Banyan's E-mail system. In addition Banyan acquired BeyondMail and offered versions 2 and 3 of that to customers.
Line 245:		Line 245:
	VINES also supported TCP/IP. Initially this was to allow TCP/IP to be routed through VINES networks, or VINES IP to be routed through TCP/IP networks. There was also a variant of FTP Software's PCTCP suite that encapsulated TCP/IP in VINES IP, and some third party services could also talk via TCP/IP. As of later maintenance releases of 5.54 it was also possible to have workstations talk to the server via TCP/IP. This was fairly straightforward to configure on Windows 95 and NT clients - with DOS clients it required some lost third-party software. Early releases of VINES required a TCP/IP routing software option to be installed to allow a server based service to talk via TCP/IP - this limit was relaxed by VINES 6.00.		VINES also supported TCP/IP. Initially this was to allow TCP/IP to be routed through VINES networks, or VINES IP to be routed through TCP/IP networks. There was also a variant of FTP Software's PCTCP suite that encapsulated TCP/IP in VINES IP, and some third party services could also talk via TCP/IP. As of later maintenance releases of 5.54 it was also possible to have workstations talk to the server via TCP/IP. This was fairly straightforward to configure on Windows 95 and NT clients - with DOS clients it required some lost third-party software. Early releases of VINES required a TCP/IP routing software option to be installed to allow a server based service to talk via TCP/IP - this limit was relaxed by VINES 6.00.

	VINES also supported AppleTalk from VINES 5.00 onwards, including LocalTalk using a server installed card.		VINES also supported AppleTalk from VINES 5.00 onwards, including LocalTalk using a server installed card. There was an optional extension for System 7.x which has been recovered.

	IPX was also supported, but only for use with ENS for Netware.		IPX was also supported, but only for use with ENS for Netware.
Line 358:		Line 358:

	Client for Windows 2000		Client for Windows 2000

	~~Macintosh System 7 extension and VINES Mail for Mac.~~

	Advanced 3270 Service installation floppy		Advanced 3270 Service installation floppy

JQW: /* What's new per version */

2023-01-28T16:36:12Z

What's new per version

← Older revision		Revision as of 16:36, 28 January 2023
Line 291:		Line 291:
	The early history of VINES is lost, with very little surviving. Here's a brief, but incomplete, history of changes.		The early history of VINES is lost, with very little surviving. Here's a brief, but incomplete, history of changes.

	VINES 2.xx ~~existed in some form~~ on PC based ~~servers but may have been limited to 286 processors only~~.		VINES 1.xx was only available on Banyan's own BNS servers, which were 680x0 based.

	VINES 4.00 introduced major changes to StreetTalk - changes to the way it updated meant that the the special group Servers@Servers was no longer required. 4.00 was also the last version to be released for 680x0 and 286 based servers. VINES 4.00 also introduced the STDA directory assistant service, in the form of patch 4.00(1).		VINES 2.xx introduced support for Banyan's DTS (Desktop) servers, and VINES/286 which ran on IBM AT and clones.

			VINES 3.xx introduced VINES/386, for 386 based PC servers, and VINES/TEAM, a cheaper version which supported a restricted number of users. Banyan also introduced their serial controller, the ICA.

			VINES 4.00 introduced major changes to StreetTalk - changes to the way it updated meant that the the special group Servers@Servers was no longer required. It was also the first version of VINES to support 486 servers. 4.00 was also the last version to be released for 680x0 and 286 based servers. VINES 4.00 also introduced the STDA directory assistant service, in the form of patch 4.00(1).

	VINES 4.10 added support for Windows 3.0 and OS/2 1.x clients. There were changes made at the session level to allow workstations to multiple sessions to be made with some services simultaneously. The initial release of 4.10 had a serious bug which would lead to file system corruption on certain file truncation operations.		VINES 4.10 added support for Windows 3.0 and OS/2 1.x clients. There were changes made at the session level to allow workstations to multiple sessions to be made with some services simultaneously. The initial release of 4.10 had a serious bug which would lead to file system corruption on certain file truncation operations.
Line 315:		Line 319:
	VINES 8.00 added very little other than support for MPS 1.4, and support for add-on ISDN card drivers (although none seem to have been released). SMP had been supported since at least VINES 4.00 on certified hardware, but needed to be installed from SMP specific media. VINES 8.00 was unique in that it didn't have its own option bit, and could be installed on any VINES 7.00 server.		VINES 8.00 added very little other than support for MPS 1.4, and support for add-on ISDN card drivers (although none seem to have been released). SMP had been supported since at least VINES 4.00 on certified hardware, but needed to be installed from SMP specific media. VINES 8.00 was unique in that it didn't have its own option bit, and could be installed on any VINES 7.00 server.

	VINES 8.50 was the Y2K compliant version of 8.00. Some services and features were not ~~Y2K compliant~~ for various reasons, although these services continued to run.		VINES 8.50 was the Y2K compliant version of 8.00. Some services and features were not supported beyond 1999 for various reasons, although these services continued to run.

	VINES 8.60 was the final release of VINES, containing all of the maintenance patches issued for VINES 8.50 since its release.		VINES 8.60 was the final release of VINES, containing all of the maintenance patches issued for VINES 8.50 since its release.

JQW: /* PC Based Service */

2023-01-25T17:02:45Z

PC Based Service

← Older revision		Revision as of 17:02, 25 January 2023
Line 277:		Line 277:
	A special service only made available if certain third-party services were installed. It allowed a PC to access the entire filesystem on the server, but only as the user 'local', the user account under which all third-party services ran. Typically, this was used to pass files to and from the queue directories of mail gateways. Most VINES services ran as 'root', hence their files were not accessible. The service was also made available if the Application Toolkit option was installed.		A special service only made available if certain third-party services were installed. It allowed a PC to access the entire filesystem on the server, but only as the user 'local', the user account under which all third-party services ran. Typically, this was used to pass files to and from the queue directories of mail gateways. Most VINES services ran as 'root', hence their files were not accessible. The service was also made available if the Application Toolkit option was installed.
	=== PC Based Service ===		=== PC Based Service ===
	It was also possible to run services on a PC and have that available via StreetTalk. Lotus Notes, for example, ran as such service under VINES. Banyan also had a product that allowed NT servers to act as a standard file service, which too ran as PC based service. In every case the PC needed to be logged in as a user on the AdminList of the group in which the service resided, as the service's StreetTalk recorded needed to be updated with the current socket address at startup.		It was also possible to run services on a PC running DOS, Windows NT or OS/2 and have that available via StreetTalk. Lotus Notes, for example, ran as such service under VINES. Banyan also had a product that allowed NT servers to act as a standard file service, which too ran as PC based service. In every case the PC needed to be logged in as a user on the AdminList of the group in which the service resided, as the service's StreetTalk recorded needed to be updated with the current socket address at startup.
	=== RIPL ===		=== RIPL ===
	Used for managing boot disk images sent to diskless workstations which communicated via the RIPL protocol. Seldom used.		Used for managing boot disk images sent to diskless workstations which communicated via the RIPL protocol. Seldom used.

JQW: /* DOS/Unix Bridge */

2023-01-25T16:58:13Z

DOS/Unix Bridge

← Older revision		Revision as of 16:58, 25 January 2023
Line 60:		Line 60:
	The server will start booting and perform at disk check. Once "Done with disk checking" is displayed, press CTRL-C and type in the root password (passwords for 5.00 and 5.54 are listed below, passwords for later revisions are chosen at installation time), and gain a root prompt.		The server will start booting and perform at disk check. Once "Done with disk checking" is displayed, press CTRL-C and type in the root password (passwords for 5.00 and 5.54 are listed below, passwords for later revisions are chosen at installation time), and gain a root prompt.

	You need to set a serial number. Banyan's serial numbers for servers were seven decimal digits long, with the middle digit either a 0 or 1. Ensure that the serial number is unique across servers.<syntaxhighlight lang="shell-session">		You need to set a serial number. Banyan's own serial numbers for servers were seven decimal digits long, with the middle digit either a 0 or 1, but any value should work. Ensure that the serial number is unique across servers on the same network.<syntaxhighlight lang="shell-session">
	echo 2130145 > /disk1/banyan/comm/serial		echo 2130145 > /disk1/banyan/comm/serial
	</syntaxhighlight>Next the server key reader binary, /disk1/banyan/install/mwidget, needs to be replaced with a shell script. Make a backup copy of the original, as it contains pertinent information which can be extracted later. The shell script should contain the following - the file .skini is written by the original mwidget, and its timestamp is checked by the server service during bootup. Echo is used here as VINES lacks touch. Don't forget to make the script executable.<syntaxhighlight lang="shell-session">		</syntaxhighlight>Next the server key reader binary, /disk1/banyan/install/mwidget, needs to be replaced with a shell script. Make a backup copy of the original, as it contains pertinent information which can be extracted later. The shell script should contain the following - the file .skini is written by the original mwidget, and its timestamp is checked by the server service during bootup. Echo is used here as VINES lacks touch. Don't forget to make the script executable.<syntaxhighlight lang="shell-session">
Line 132:		Line 132:
	ebrjbl:Enterprise Backup and Restore Jukebox Large (ebr104)		ebrjbl:Enterprise Backup and Restore Jukebox Large (ebr104)
	rev7.0:Revision 7.00 of VINES		rev7.0:Revision 7.00 of VINES
	</syntaxhighlight>Exit the shell and the server should start to come up again. Say no to the two questions on restoring from a backup on installing additional options. You will now be presented with a lists of supported network cards, serial communications cards and tape controller adaptors. Select the relevant network adaptor here - under VINES 7.00 and later it's possible to ~~instal~~ additional network drivers from a floppy if nothing suitable is listed, but not until after the server is up and running.		</syntaxhighlight>Exit the shell and the server should start to come up again. Say no to the two questions on restoring from a backup and on installing additional options. You will now be presented with a lists of supported network cards, serial communications cards and tape controller adaptors. Select the relevant network adaptor here - under VINES 7.00 and later it's possible to install additional network drivers from a floppy if nothing suitable is listed, but not until after the server is up and running.
	==== Final steps ====		==== Final steps ====
	The server will prompt for a server name. It will then try to look on the network for other servers to validate that the server name is unique. If another server is discovered on the network, the account details of an administrator of that server can be used to add this server to StreetTalk. If no other server is found the server can be set up as either the first server on the network, or as a server to be added to a network later. The second option leaves AdminList@server-name@Servers empty, which must be updated by an existing user on another server once the server joins the network.		The server will prompt for a server name. It will then try to look on the network for other servers to validate that the server name is unique. If another server is discovered on the network, the account details of an administrator of that server can be used to add this server to StreetTalk. If no other server is found the server can be set up as either the first server on the network, or as a server to be added to a network later. The second option leaves AdminList@server-name@Servers empty, which must be updated by an existing user on another server once the server joins the network.
Line 221:		Line 221:
	\|		\|
	\|}		\|}
	There was also a password for accessing the low-level formatter from the release media on Banyan's own server hardware - Banyan required severs to be fitted with drives bearing Banyan's signature, but this could be circumvented by invoking the formatter by typing the relevant password at ~~the~~ installation menu. On CNS servers with later copies of the release media this was '''nosedive''', whilst other known formatter passwords were '''goforit''' and '''format.'''		There was also a password for accessing the low-level formatter from the release media on Banyan's own server hardware - Banyan required severs to be fitted with drives bearing Banyan's signature, but this could be circumvented by invoking the formatter by typing the relevant password at a certain installation menu. On CNS servers with later copies of the release media this was '''nosedive''', whilst other known formatter passwords were '''goforit''' and '''format.'''
	== Managing the system ==		== Managing the system ==
	The server console has several menus for managing the server. Tasks available include changing communications options, hardware configuration, kernel configuration from VINES 6.00 onwards, network management, print queue management, and server shutdown. UNIX access is also available if configured.		The server console has several menus for managing the server. Tasks available include changing communications options, hardware configuration, kernel configuration from VINES 6.00 onwards, network management, print queue management, and server shutdown. UNIX access is also available if configured.
Line 259:		Line 259:
	VINES Security - ''VS@sever-name@Servers'' (or ''VanGuard@server-name@Servers'' in early releases) looked after security sessions, validating a user or service's security tokens. It would poll workstations occasionally to keep sessions alive. Mandatory.		VINES Security - ''VS@sever-name@Servers'' (or ''VanGuard@server-name@Servers'' in early releases) looked after security sessions, validating a user or service's security tokens. It would poll workstations occasionally to keep sessions alive. Mandatory.
	=== VINES Files ===		=== VINES Files ===
	VINES Files - VINES Files@server-name@Servers - was a file service containing VINES client programs and management tools. It would be mapped to drive Z: at login~~, and could be any local instance of~~ the service running the same ~~client~~ version as the ~~user's workstation~~. Its contents were read only to all users.		VINES Files - ''VINES Files@server-name@Servers'' - was a file service containing VINES client programs and management tools. It would be mapped to drive Z: at login. A client would poll for the nearest VINES Files service running the same version as the client at login, and map itself to the first to respond. Its contents were read only to all users.
	=== Mail ===		=== Mail ===
	Email services - later known as Intelligent Messaging. The service was typically named MS@server-name@Servers, and would be created under that name if the software option was present at server installation, but could have any name. A user's Mail service was controlled by the SETMAIL command in their profile.		Email services - later known as Intelligent Messaging. The service was typically named MS@server-name@Servers, and would be created under that name if the software option was present at server installation, but could have any name. A user's Mail service was controlled by the SETMAIL command in their profile.
Line 275:		Line 275:
	This service allowed a client to connect to a shared serial line on the server to access a shared modem or terminal session on a legacy system. The service required either a Banyan ICA card (Intelligent Communications Adaptor) or a Persyst DCP-88/VM serial adaptor to function. The service could also act as a remote server console.		This service allowed a client to connect to a shared serial line on the server to access a shared modem or terminal session on a legacy system. The service required either a Banyan ICA card (Intelligent Communications Adaptor) or a Persyst DCP-88/VM serial adaptor to function. The service could also act as a remote server console.
	=== DOS/Unix Bridge ===		=== DOS/Unix Bridge ===
	A special service only made available if certain third-party services were ~~installed, or if the SDK was~~ installed. It allowed a PC to access the entire filesystem on the server, but only as the user 'local', the user account under which all third-party services ran. Typically, this was used to pass files to and from the queue directories of mail gateways. Most VINES services ran as 'root', hence their files were not accessible.		A special service only made available if certain third-party services were installed. It allowed a PC to access the entire filesystem on the server, but only as the user 'local', the user account under which all third-party services ran. Typically, this was used to pass files to and from the queue directories of mail gateways. Most VINES services ran as 'root', hence their files were not accessible. The service was also made available if the Application Toolkit option was installed.
	=== PC Based Service ===		=== PC Based Service ===
	It was also possible to run services on a PC and have that available via StreetTalk. Lotus Notes, for example, ran as such service under VINES. Banyan also had a product that allowed NT servers to act as a standard file service, which too ran as PC based service. In every case the PC needed to be logged in as a user on the AdminList of the group in which the service resided.		It was also possible to run services on a PC and have that available via StreetTalk. Lotus Notes, for example, ran as such service under VINES. Banyan also had a product that allowed NT servers to act as a standard file service, which too ran as PC based service. In every case the PC needed to be logged in as a user on the AdminList of the group in which the service resided, as the service's StreetTalk recorded needed to be updated with the current socket address at startup.
	=== RIPL ===		=== RIPL ===
	Used for managing boot disk images sent to diskless workstations which communicated via the RIPL protocol. Seldom used.		Used for managing boot disk images sent to diskless workstations which communicated via the RIPL protocol. Seldom used.

← Older revision		Revision as of 21:01, 16 February 2023
Line 309:		Line 309:
	VINES 5.52, 5.53 and 5.54 added additional server hardware support.		VINES 5.52, 5.53 and 5.54 added additional server hardware support.

	VINES 6.00 added loadable device drivers and root access. Loadable device drivers were now available for storage adaptors and network interfaces.		VINES 6.00 added loadable device drivers and root access. Loadable device drivers were now available for storage adaptors and network interfaces. StreetTalk was also enhanced, allowing read-only copies of groups to be shadowed to other servers, and allowing some additional characters in item names.

	VINES 6.20, 6.30 and 6.40 were maintenance releases of 6.00, issued as sets of patches.		VINES 6.20, 6.30 and 6.40 were maintenance releases of 6.00, issued as sets of patches.

	VINES 7.00 added support for larger filesystems (previously they were limited to 2GB), together with long filename support from certain clients. The root filesystem was also enlarged to circumvent installation problems seen with VINES 6.xx. VINES 7.00 also introduced paper-based server keys and option codes, although dongles could still be used. Patches were also issued to allow paper-based option keys to be used with previous VINES revisions.		VINES 7.00 added support for larger filesystems (previously they were limited to 2GB), together with long filename support from certain clients. The root filesystem was also enlarged to circumvent installation problems seen with VINES 6.xx. VINES 7.00 also introduced paper-based server keys and option codes, although dongles could still be used. Patches were also issued to allow paper-based option keys to be used with previous VINES revisions. The LAN server-to-server and SMP options were now bundled with the base release.

	VINES 7.10 was a maintenance release for 7.00, applied as a set of patches. There were no significant new features.		VINES 7.10 was a maintenance release for 7.00, applied as a set of patches. There were no significant new features.

	VINES 8.00 added very little other than support for MPS 1.4, and support for add-on ISDN card drivers (although none seem to have been released). SMP had been supported since at least VINES 4.00 on certified hardware, but needed to be installed from SMP specific media. VINES 8.00 was unique in that it didn't have its own option bit, and could be installed on any VINES 7.00 server.		VINES 8.00 added very little other than support for MPS 1.4, and support for add-on ISDN card drivers (although none seem to have been released). SMP had been supported since at least VINES 4.00 on certified hardware, but needed to be installed from SMP specific media. VINES 8.00 was unique in that it didn't have its own option bit, and could be installed on any existing VINES 7.00 server.

	VINES 8.50 was the Y2K compliant version of 8.00. Some services and features were not supported beyond 1999 for various reasons, although these services continued to run.		VINES 8.50 was the Y2K compliant version of 8.00. Some services and features were not supported beyond 1999 for various reasons, although these services continued to run.
Line 325:		Line 325:
	There was also a product named ENS for Netware that allowed Netware servers to use StreetTalk. Initially these used their own special ENS servers, which were cut down VINES servers. ENS 1.00 was effectively VINES 5.20, and ENS 1.1 was VINES 5.30. A server running VINES 5.50 onwards could also act as an ENS server with the relevant software option. The Netware NLM and ENS client files are currently lost, as are media for the two ENS server releases.		There was also a product named ENS for Netware that allowed Netware servers to use StreetTalk. Initially these used their own special ENS servers, which were cut down VINES servers. ENS 1.00 was effectively VINES 5.20, and ENS 1.1 was VINES 5.30. A server running VINES 5.50 onwards could also act as an ENS server with the relevant software option. The Netware NLM and ENS client files are currently lost, as are media for the two ENS server releases.

	There were also versions of VINES released for some versions of commercial UNIX - SCO Unix, Solaris, HP-UX and AIX. Some of these were issued under ENS branding. None of these appear to have survived.		There were also versions of VINES released for some versions of commercial UNIX - SCO Unix, Solaris, HP-UX and AIX, the latter running on the RS/6000. Some of these were issued under ENS branding. None of these appear to have survived.

	Banyan also issued a VINES implementation that ran on Windows NT entitled StreetTalk for NT. There were also several other NT based software, including a webmail gateway for Intelligent Messaging under IIS, and a software to allow an NT drive to act as a VINES file service.		Banyan also issued a VINES implementation that ran on Windows NT entitled StreetTalk for NT. There were also several other NT based software, including a webmail gateway for Intelligent Messaging under IIS, and software to allow an NT drive to act as a VINES file service.
	== What's Missing ==		== What's Missing ==
	An incomplete list of currently missing software:		An incomplete list of currently missing software:
Line 340:		Line 340:

	VINES 8.00 release media.		VINES 8.00 release media.

			VINES 8.00 and 8.50 maintenance patches.

	Release notes for any revision of VINES.		Release notes for any revision of VINES.
Line 345:		Line 347:
	Documentation for the 8.60 maintenance patch.		Documentation for the 8.60 maintenance patch.

	SMP and MicroChannel variants of any VINES revision.		SMP and MicroChannel variants of any VINES revision. The SMP version appears to have been integrated into the standard release of VINES 7.00 and above.

	Installation media for Banyan's own hardware - BNS, DTS or CNS, together with a working server. It may be possible to re-create the installation tape of VINES 6.00 for a CNS server from the 6.00 CD-ROM~~. Needed in case a working example of any of these servers survive~~.		Installation media for Banyan's own hardware - BNS, DTS or CNS, together with a working server. It may be possible to re-create the installation tape of VINES 6.00 for a CNS server from the 6.00 CD-ROM.

	VINES 286 - any revision.		VINES 286 - any revision.

	VINES Application Toolkit - any revision.		VINES Application Toolkit - any revision. Documentation was originally released in printed form, moving to CD-ROM with VINES 6.00.

	Client for OS/2 - 1.x or 2.x. Although the relevant driver files survive as part of the core OS installation, the undocumented configuration files are missing, and efforts to recreate them have failed.		Client for OS/2 - 1.x or 2.x. Although the relevant driver files survive as part of the core OS installation, the undocumented configuration files are missing, and efforts to recreate them have failed.
Line 370:		Line 372:

	ENS Management Tools - an early GUI for managing servers. Replaced by StreetTalk Explorer.		ENS Management Tools - an early GUI for managing servers. Replaced by StreetTalk Explorer.

			Demarc - SNMP based management tools.

	Banyan Intranet Connect - webmail portal that ran under IIS on NT.		Banyan Intranet Connect - webmail portal that ran under IIS on NT.