PicLan Version 126.96.36.199 Release Announcement
(C) Copyright 1990-1998 Modular Software Corporation. All rights reserved.
For more information about PicLan contact: firstname.lastname@example.org
or visit http://modsoft.com
PicLan Version 188.8.131.52 is currently being released for all platforms and
February 28, 1998
PicLan version 184.108.40.206 is currently being released for all platforms
and clients. This release includes a number of signifigant bug fixes
and new features. Because this is a signifigant release, most users
should consider upgrading to this release. Also because this is a
signifigant release, it currently has BETA status, so users should
excercise caution for the next several weeks.
This release consolidates a number of interim releases and features
PicLan version 220.127.116.11 has the following bug fixes and additions (this
list is relative to version 18.104.22.168):
Native SOFTRAP aborts on Mentor PRO during PL-LOAD
PCI adapter TP full/half duplex interface programming
PCI adapter support for Fast Ethernet
Windows DSG printing functions with Win95 and WinNT
Major additions to Windows 95 and Windows NT client support:
Windows NT Winsock usage when IPX routing is loaded
Windows 95/NT Winsock usage when 3rd-party windows sockets DLLs are
This fixes past problems with NetWare's IPX/IP Gateway on Win95
PCI Network Adapters
A bug in the programming of 21041 adapters with TP interfaces has been
A problem with the PCI driver interface that programs 21041 network
adapters with a half-duplex twisted-pair interface has been corrected.
This bug would force users to run 21041 adapters in full-duplex mode, which
in turn would create an excessive number of network collisions reducing
network performance and in some cased impacting on connection reliability.
Some problems using the WIN printer path through the Windows DSG
have been reported.
The method of implementing the WIN printing path inside of the
Windows DSG has been re-implemented. This new code should make printing
through the Windows DSG more reliable and versatile. In addition,
the WIN printer paths can now specify printer names, network paths,
or local device names.
Some systems experience a NAT SOFTRAP abort when running PL-LOAD
This bug has been fixed in 22.214.171.124. It appears this is a conflict
between a PicLan function and the system's BIOS. The PicLan function
has been modified to avoid the problem.
GP Fault in PLTW.EXE
A General Protection fault in PLTWD.DLL was fixed.
Additional PCI Support
Additional support has been included for PCI adapters in the Pick host
For Pick hosts that support PCI adapters, a number of new adapters have
been officially supported and tested. The list of PCI adapters now
100 Megabit adapters are also working in both 10 Megabit mode and 100 Megabit
mode (using 100 Base T cabling). Code in the PicLan driver for 100TX
and 100FX interfaces is included, but this has not been tested. Network
performance at 100 Megabits is still being tested but appears to be quite
good. Look for an application note on this in the near future.
Generic 21040 adapters
Compex has been tested at MSC
Generic 21041 adapters
Compex and Linksys have been tested at MSC
SMC and Kingston have been tested in the field with previous PicLan releases.
Generic 21140 adapters
Compex and Linksys have been tested at MSC
Compex 21143 adapters
Compex FreedomLine 100 has been tested at MSC
PL-DSG32.EXE is a new PicLan program.
PicLan now includes a 32-bit executable as a Windows DOS Services Gateway.
This new program has the following enhanced features:
The 32-bit DSG does not currently support direct NetWare print paths, although
you can still print to NetWare by using a Windows path or named printer.
Support for long file names
Support for re-direction to Windows print queues either by printer name,
device name, or network path.
Print Job PRE and POST Control Records
New control items allow print jobs to include pre and post
These functions allow the system administrator to setup a print queue
to automatically setup a printer configuration without changing the jobs
that generate the print files themselves. This is intended so that
you can create print queues that automatically place a printer in landscape
mode, or automatically setup a font size.
SERVER-PROCESS Spooler Poll-Time Setting
The amount of time that the SERVER-PROCESS waits between checking the spooler
is now programmable.
You can now set the delay time between SERVER-PROCESS spooler polls
to any value from 10 to 60 seconds. While this is not really necessary
for most sites, enough people asked for it to justify it's inclusion. The
PL-KICK-SERVER command remains the preferred method of reducing the delay
in network printing.
Windows Socket Usage Changes for Win32
A number of changes have been made to PLAN32S.EXE to make Windows 95 and
Windows NT installations more versatile.
All of these options are setup with PL_SETUP.EXE
You can now choose the IPX interface API that you wish to use
WSOCK32.DLL - Winsock version 1.1 interface from Microsoft
WS2_32.DLL - Winsock version 2 interface from Microsoft
NWSIPX32.DLL - 32-bit IPX interface from Novell
The SAP (Service Advertising Socket) will now only be opened if the client
is configured as a DSG
If the SAP socket fails to open, the client will still function, although
the DSG may not advertise.
You can select to advertise IPX services via Winsock 2 or NWSIPX API calls
instead of having PicLan manually broadcast SAP packets.
The main limitations that these changes address are:
Because of the number of possible configurations with Windows 95 and Windows
NT, Microsoft and Novell clients, advertising DOS Services Gateway processes,
multi-homed adapters, and IPX routing not all possible combinations have
been tested. As such, you should start with these guidelines:
You can now use the NetWare IPX/IP and IP/IP gateway on Windows 95 by using
the NWSIPX32.DLL instead of Winsock.
You can now run the PicLan client and DSG on a Windows NT system that is
routing IPX packets or has RRAS (routing and RAS) loaded.
If you have Client32 from Novell loaded, choose the NWSIPX option. This
option uses Novell interfaces to talk to IPX instead of Microsoft's.
If you are running the NetWare IPX/IP or IP/IP Gateway, then you must run
NWSIPX. Winsock 1.1 will not function.
Winsock 1.1 also works with Client32 loaded provided that you are not using
the IPX/IP Gateway.
If you do not have Client32 from Novell loaded, choose the Winsock 1.1
Winsock 2 is not available with Windows 95. It may be available in
Try to use Winsock 2 if possible
If you are running a DSG, try to use the API calls instead of SAP. This
appears to be more compatible with multi-homing and SAP router services.
The API calls have a 5-15 second delay built into them, so the DSG will
not show up on the rest of the network for a short period of time.
If the DSG is not visible to the network, try Winsock 2 SAP or NWSIPX (if
the InternetWare C for Windows NT is loaded)
You should not need to use Winsock 1.1 as Winsock 2 is always available
on Windows NT 4.0.
If you are loading onto Windows NT 3.51, you might get PicLan
to work with Winsock 1.1. This platform is theoretically possible,
but no longer supported by Modular Software.