MultiValue Implementation Information
General Automation

Mentor PRO

Mentor PRO is a native Pick implementation that executes in 32-bit flat-model memory space on Intel x86 PC systems.  Maximum system configuration is 256 interactive terminal users.  Systems have 486 thru Pentium II (and maybe Pention III) processors with potential disk storage exceeding 100 gigabytes (although most systems are 2-10 gigabytes).

PicLan-IP is implemented on Mentor PRO as an extension driver to the PicLan ethernet IPX product which GA distributes with Mentor PRO.  When PicLan-IP is loaded, TCP/IP supported is added to the existing PicLan ethernet driver.  PicLan IPX functions continue to operate and can be used concurrently with PicLan-IP TCP/IP functions.

The low-level PicLan-IP TCP/IP stack is implemented as an event-driven "state machine" (this is also how the PicLan IPX support layer is implemented).  This provides for a very high performance TCP/IP stack with minimal memory usage.  Maximum TCP/IP configured support is for about 4000 concurrent connection streams with up to 50 configured IP addresses on the local host system.

High-level PicLan-IP functions like HTTP and SMTP/POP3 services are implemented as standard Pick/BASIC programs that run on phantom processes.  Other than inbound TELNET sessions, PicLan-IP server processes do not consume any Mentor PRO user licenses regardless of the number of users accessing the system.

Sequoia PRO

Mentor PRO is a native Pick implementation that executes in 32-bit flat-model memory space on Intel x86 PC systems.  Maximum system configuration is 256 interactive terminal users.  Systems have 486 thru Pentium II (and maybe Pention III) processors with potential disk storage exceeding 100 gigabytes (although most systems are 2-10 gigabytes).
PicLan-IP is implemented on Sequoia PRO as an extension driver to the PicLan ethernet IPX product.  In order to run PicLan-IP on Sequoia PRO, you must have at least a 1-user PicLan license on the system.  When PicLan-IP is loaded, TCP/IP supported is added to the existing PicLan ethernet driver.  PicLan IPX functions continue to operate and can be used concurrently with PicLan-IP TCP/IP functions.

The low-level PicLan-IP TCP/IP stack is implemented as an event-driven "state machine" (this is also how the PicLan IPX support layer is implemented).  This provides for a very high performance TCP/IP stack with minimal memory usage.  Maximum TCP/IP configured support is for about 4000 concurrent connection streams with up to 50 configured IP addresses on the local host system.

High-level PicLan-IP functions like HTTP and SMTP/POP3 services are implemented as standard Pick/BASIC programs that run on phantom processes.  Other than inbound TELNET sessions, PicLan-IP server processes do not consume any Sequoia PRO user licenses regardless of the number of users accessing the system.

Pick/64+

Pick/64+ is an older native Pick implementation developed by Alpha Microsystems.  Alpha Micro is no longer marketting Pick products and General Automation has taken over support and upgrades for this product line.  To help existing users migrate, Modular Software has implemented a version of PicLan-IP for Pick/64+ version 2.3.  Pervious releases of Pick/64+ are not supported.  While the PicLan-IP implementation is complete and includes all PicLan-IP elements, users running Pick/64+ are encouraged to upgrade to more modern, and supports Pick platforms.  The most obvious upgrade path is to Sequoia PRO, but other MultiValue platforms are also possible.  The intent at Modular Software is to freeze the PicLan-IP release for Pick/64+ in the near future and not continue to develop for this platform.

Pick/64+ is a native Pick implementation that executes in 32-bit flat-model memory space on Intel x86 PC systems.  Maximum system configuration is 192 interactive terminal users.  Systems have 386 thru Pentium II (and maybe Pention III) processors with potential disk storage exceeding 100 gigabytes (although most systems are 2-10 gigabytes).

PicLan-IP is implemented on Pick/64+ as an extension driver to the PicLan ethernet IPX product.  In order to run PicLan-IP on Pick/64+, you must have at least a 1-user PicLan license on the system.  When PicLan-IP is loaded, TCP/IP supported is added to the existing PicLan ethernet driver.  PicLan IPX functions continue to operate and can be used concurrently with PicLan-IP TCP/IP functions.

The low-level PicLan-IP TCP/IP stack is implemented as an event-driven "state machine" (this is also how the PicLan IPX support layer is implemented).  This provides for a very high performance TCP/IP stack with minimal memory usage.  Maximum TCP/IP configured support is for about 4000 concurrent connection streams with up to 50 configured IP addresses on the local host system.

High-level PicLan-IP functions like HTTP and SMTP/POP3 services are implemented as standard Pick/BASIC programs that run on phantom processes.  Other than inbound TELNET sessions, PicLan-IP server processes do not consume any Pick/64+ user licenses regardless of the number of users accessing the system.

mv/Base

mv/Base is a hosted Pick implementation that executes as a Win32 application on Windows 95/98/NT.  Only single user systems should consider using mv/Basic on Windows 95/98.  Larger, server, systems should definately use Windows NT because of increased reliability and performance.

The PicLan-IP implementation for D3/NT uses a low-level Windows DLL (Dynamic Link Library) implemented in 'C'.  This library off-loaded many network communications and buffering functions from PicLan-IP into a lower-level language.  Becuase of the nature of the mv/Base server application, the library actually runs within the same process memory space as mv/Base itself.  To maximize performance, the support DLL makes full use of Win32 synchronization and thead functions to create a fully event-driven environment that requires no polling.

High-level PicLan-IP functions like HTTP and SMTP/POP3 services are implemented as standard Pick/BASIC programs that run on phantom processes.  Because PicLan-IP processes execute exclusively on mv/Base phantom processes, no mv/Base user licenses are consumed regardless of how many users are accessing PicLan-IP server functions.