TECHNICAL BULLETIN 06.18.90 WIN300 JCR (update 9.19.90) MULTITASKING SOFTWARE: Windows 3.0, Microsoft Forwarding Comments Windows 3.0 is a complex multi-tasking application, which offers a variety of functions within network operation. Some of these functions are not currently supported with LANtastic: Running Windows 3.0 in enhanced mode on a server - Microsoft does not support this mode on a non- dedicated, MS-NET server. A problem report has been filed with their engineers and they may approach this problem with later releases. Microsoft does not believe this problem to be driver related but directly related to the 386 processor. One must rely on NET Printer Management Queue to control network print jobs, as the Printer Manager provided in Windows does not function with LANtastic. Windows 3.0 does not support the requirements necessary for LANtastic Voice. We are currently working with Microsoft to provide the most reasonable solutions for these problems and this bulletin will be updated as necessary. This bulletin should replace all other notes generated from this office on Windows 3.0 to date. While claiming Windows 3.0 and LANtastic 3.0 are compatible, Artisoft is not responsible for the compatibility of any other application(s) running within Windows unless otherwise noted. The following information is based on inhouse testing of Windows. If you received a copy of this bulletin and are not a registered LANtastic owner, your questions should be directed to our technical sales staff. ARTISOFT, Inc. 575 E. River Road, Tucson, AZ 85704, (602) 293-6363 INSTALLING WINDOWS 3.0 Windows 3.0 should be installed on the server with the network already loaded, and should be installed following the procedures for Microsoft NET. Windows creates several .INI files which contain various configuration information: CONTROL.INI - Maintains color schemes and patterns PROGMAN.INI - Maintains group information SYSTEM.INI - Maintains system configuration WIN.INI - Maintains Windows configuration (devices, fonts, etc) WINFILE.INI - Maintains settings When Windows 3.0 is installed, some modifications to the SYSTEM.INI and WIN.INI files may still be necessary. Copies of the entire files are attached at the end of this document with detailed descriptions of each command line relevant to the operation of the network, along with suggested modifications. CONFIG.SYS Windows will install any necessary devices in the config.sys file during the install process. The install program will load any mouse or other devices, SMARTDRV.SYS and HIMEM.SYS if applicable. Windows requires an extended memory manager (HIMEM.SYS) to run Windows in standard or 386 enhanced mode. AUTOEXEC.BAT Windows will modify the Autoexec.bat during installation if prompted to do so. The installation adds Windows to the PATH command and will add a SET TEMP= to the appropriate location for Windows. CONFIGURATION Once Windows has been installed, it may be configured individually for each workstation on the network. This procedure installs a group of configuration files containing information about that workstation's hardware configuration and startup options. To run the network setup, log into the network and change to the redirected drive which contains Windows. From that prompt run SETUP /N (to setup across the Network). Windows will ask for a path\directory in which to install the local files, the default is C:\WINDOWS. Windows will then display an initial configuration menu, if the selections shown are not correct for that workstation, use the arrow keys to change each item. Once the selections are correct, press enter to accept the changes and Windows will copy the necessary files to the specified directory. Once Windows has been installed, review the modifications as necessary to the WIN.INI and SYSTEM.INI files in the local workstation directory, and set PATH to include the redirected drive designation for Windows, as well as the local workstation directory. ADDITIONAL CONFIGURATION In most cases, when installed with the network activated, the default settings configured through Windows and the modifications suggested to the .INI files, Windows should be operational. If problems persist at this point, please refer to the end of this document for copies of the .INI files and additional suggestions. OPERATION Once Windows has been installed and configured, the user must log into the server and share the directory which contains Windows. From that directory prompt, the user may run Windows in either of three formats: WIN /S Standard Mode: Provides access to extended memory for 286-based systems or higher with at least 256K of extended memory WIN /E Enhanced Mode: Provides all standard mode features for 386-based systems with at least 1MB of extended memory plus Virtual Memory, multiple virtual machines, configurable time-slicing for DOS apps (to determine priority of execution) and standard DOS apps can run in their own windows or full-screen NOTE: Enhanced mode may also be activated by WIN /3. WIN /R Real Mode: Base-level operating mode for 286/386-based systems with 640K to 1 MB of memory. Uses standard 640K conventional memory, standard DOS and Windows apps can use EMS memory, and standard DOS apps run full-screen in the foreground. WIN When loaded with no switch, Windows will attempt to run the mode which best suits the current configuration. If you are running Windows on a server and have extended memory present, ALWAYS run Windows using the /S or /R switch. Otherwise Windows will attempt to load in enhanced mode, which is not supported on a server. The network should always be loaded prior to running Windows. Once Windows has been loaded, the user may execute a variety of network functions. These functions can be handled through the DOS shell, a PIF file or through Windows. The following is an outline of handling these functions through Windows. NOTE: If the user is not already logged into the server, he may do so by running NET through the DOS shell, the File Manager or a created PIF file. Connecting a Network Drive 1. The user must first be logged into the server containing the resource (If the user is not logged in, he may do so through the DOS shell or by running NET through the File Manager or through a created Net PIF file. 2. From the MAIN group, select File Manager and pull down the Disk menu. 3. Select Connect Net Drive 4. Select the desired Drive Letter and enter the Network Path (ie \\SERVER\RESOURCE). 5. Select Connect or press enter. 6. The drive should now appear on the directory tree and NET should appear in the drive box. Double click to access that drive. The bottom portion of the window indicates the full path name of the drive (\\SERVER\RESOURCE) and the available bytes on that drive. Disconnecting a Network Drive 1. From the MAIN group the user should select File Manager and pull down the Disk menu. 2. Select Disconnect Net Drive and select the drive letter to be disconnected. 3. The directory tree should now display any current connections. Connecting a Printer Windows has a Print Manager which has the capabilities of managing network print jobs. Any testing of this facility (as far as pausing or disabling the manager) proved fatal to the print job, and in some cases, to the network. By establishing connections through Windows to any network port, the manager did not operate and returned "A General Network Error has Occurred" message. By establishing connections through NOS and configuring the printer drivers to a port designated with .PRN (LPT1.PRN, LPT2.PRN etc), the job was redirected to a file therefore bypassing the Printer Manager. In this case the Manager was not accessible, returning a "There are no printers connected, run Control Panel to set up printers" message. When establishing connections to a printer, we recommend the following: 1. The user must first be logged into the server connected to the printer resource 2. A link must be established to the printing device using NET through the DOS shell, any NET PIF file created, or prior to loading Windows. 3. From the MAIN group, select Control Panel and select the Printers option. From the Printer menu, hi-lite the desired printer driver from the Installed Printers list and select the Configure option. Hi-lite the redirected port from the .PRN selections (LPT1.PRN, LPT2.PRN, etc. If you do not see these ports listed under configuration, please review the installation notes regarding WIN.INI earlier in this bulletin). Once in any application through Windows, pull down the File menu, select Printer Setup and select the printing device. Printing to Local and Network Devices 1. The user should have the network printer connected to a .PRN device as listed above. 2. A printer driver should be installed for the local printer. 3. From the MAIN group, select Control Panel and select the Printers option. From the Printer menu, hi-lite the local printer driver from the Installed Printers list and select the Configure option. Hi-lite the local port designation (do not select a .PRN device). Once in any application through Windows, pull down the File menu, select Printer Setup and select the desired printing device. Disconnecting Printers 1. Since the initial connection of a printer can be done through the application, the user may select a different printer device without disconnecting the initial printer. The same holds true for changing the driver, the user may run the Control Panel Printers program to change the configuration of the printer port. 2. If the user wishes to completely disconnect the device, he may execute a NET command through the DOS shell or through a NET PIF file. Downloading Fonts If Windows is to be configured with additional fonts, the installation procedure provided by either the font (or in some cases the printer) manufacturer must first be followed to install the fonts. Once the fonts are installed, the user may run the Control Panel, run the Fonts program and follow the Add Font Files section. After the fonts are installed, the WIN.INI [PrinterPorts] section must have the LPTX.PRN= command lines added (follow the installation instructions provided for the WIN.INI [ports] section). The font packages reported to work with Windows 3.0 and LANtastic 3.0 are Bitstream, Inc (800-522-3668) Bitstream Fontware 3.0 and ZSoft (404-428-0008) SoftType 1.01. PIF Files Whenever a non-Windows application is executed, Windows looks for that application's Program Information File (PIF). A PIF is a special file containing settings that tell Windows how to run a non-Windows application. A PIF's filename usually matches that of the corresponding application. Once such a file has been created, that application can started by double-clicking on the PIF filename. It is not necessary to create a PIF for each non-Windows application. Please refer to your Windows manual for more information. Using Expanded Memory Managers An expanded memory manager gives applications access to only a limited amount of expanded memory at a time, and is slower to use than extended memory. Therefore Windows uses expanded memory only when running in real mode. (When running in 386 enhanced mode, Windows can simulate expanded memory for applications that require it, using EMM386.SYS). Windows requires that memory to conform to version 4.0 of the Lotus-Intel-Microsoft Expanded Memory Specification (LIM EMS 4.0). If your applications requires expanded memory with Windows in real mode, the EMM386.SYS expanded memory emulator may be used. When using EMM386.SYS, it is important to note that one must exclude any conflicting memory addresses. The following is an example (the EMM386.SYS file is loaded in the CONFIG.SYS file): DEVICE-EMM386.SYS X=D800-DFFF (Where D800-DFFF is the network adapter's RAMBASE) NOTE: At this time, Quarterdeck's QEMM-386 5.0 does not work with Windows in standard or enhanced mode. The procedure QEMM-386 uses to store memory resident programs in high memory is not compatible with the methods Windows 3 uses to access extended memory in standard and enhanced modes. QEMM-386 version 5.1 will allow one to run Windows in real and standard mode, but does not correct the problem of running Windows in enhanced mode. To upgrade to QEMM-386 5.1, contact Quarterdeck (213) 392-9701. Using Extended Memory Managers Extended memory is memory beyond 640K on 80286, 80386, and 80486 computers. It is an extension of your computer's conventional memory. An extended memory manager is required in order to run Windows in standard or 386 enhanced mode. Windows includes the extended memory manager HIMEM.SYS. When running in real mode, Windows uses extended memory only for storing information. TROUBLESHOOTING TIPS AND SUGGESTIONS Installation Make sure the network is loaded during the installation - this ensures the proper network driver will be loaded and the files will be configured properly. During our tests, we tested a Windows 3.0 version from Microsoft as well as versions from CompuAdd and Northgate. The installation processes were relatively similar. Please refer to your documentation for actual install process, using the MS-NET network driver. Whenever necessary, follow the MS-NET instructions in your documentation when installing or operating Windows 3.0. Configuration Windows can accommodate almost any network configuration through modifications done to the .INI files. Please take care when making changes - you may want to print out the original files before making adjustments. Since there are so many parameters that can be set, we have included printouts of our test files along with a very brief summary of the modifications done. The values listed in these examples may not be sufficient for your particular configuration. Please review the section of your documentation entitled Networks and Windows (CH 14, page 543 in the Microsoft Windows manual). Although the documentation does not cover all aspects of each .INI file, it does cover the aspects which require changes relevant to network use. If your questions on the .INI files themselves have not been answered by this bulletin or by the documentation provided with your copy of Windows, please forward those questions to Microsoft. Printing Problems - Local If the system will not print to a local printer through Windows, run a test by printing to that device first without Windows loaded. If the test prints, check and make sure the printer driver in the Windows Control Panel is connected to a LPT1, LPT2 etc. device (rather than a .PRN device) and that driver has been selected in your application. Also check the Windows timeout. if the test does not print, check and make sure that device has not been redirected through the network and refer to your corresponding documentation. Printing Problems - Network If you are experiencing difficulties printing to a network printer, make sure the printer driver selected is connected (through the Windows Control Panel) to a .PRN device (LPT1.PRN, LPT2.PRN, etc) and make sure that port has been redirected through the network to the appropriate server resource. Since a .PRN device has been selected, a LANtastic printer timeout is not necessary (The Microsoft version of Windows does set a timeout with a default value of 45 seconds). If you do not see a .PRN device listed, please refer to the [ports] section of the WIN.INI file listed below, you will need to modify your WIN.INI file to include this information. Do not attempt to use the Windows Print Manager. Printing to the .PRN device (file) effectively bypasses the Windows Print Manager and sends the job directly to the network. Do not attempt to halt or pause the Windows Print Manager, as that may cause problems as well. If the Windows Print Manager is paused or disabled, reactivate it. All printer queue management must be handled through the network. Printing Problems - Fonts If your fonts are not downloading, first make sure the printer has been properly configured as above. Follow the install procedures provided by the font manufacturer or by the printer manufacturer to install the fonts. Once the fonts have been installed, they may be added through the Windows Control Panel. Once the fonts have been added, modify the WIN.INI [PrinterPorts] section to include the LPTX.PRN= command line (where LPTX is the actual port you wish to redirect, ie LPT1, LPT2 etc). This command may not be necessary for all font packages. Again, no LANtastic timeout is necessary. Please refer to the Fonts section above for a list of tested font packages. TROUBLESHOOTING TIPS AND SUGGESTIONS cont. Running Windows on a LANtastic Server Windows 3.00 does not support enhanced mode on a non-dedicated MS-NET server. If your server suddenly 'disappears' from the network or locks up, first check the mode it's running. It should be in standard or real mode only (on a server). When Windows is loaded with no switches (WIN) it will run the mode it thinks is appropriate. If your server is a 386 with extended memory, Windows will attempt to load in enhanced mode. Running Windows across the Network If Windows is a shared resource on the network, make sure SETUP /N has been run for each user and make sure each user has a path set to the local directory as well as the network directory for Windows. Rerun Setup and check the configuration for each workstation. The setup will create the appropriate .INI files in the designated directory for each node. Follow the suggested modifications below for each file. Running Windows with Enhanced or Expanded Memory Make sure the network adapter RAMBASE (if applicable), and any other conflicting adapter RAMBASE has been excluded with the EMMEXCLUDE parameter in the SYSTEM.INI file. For detailed memory use, please refer to the Windows documentation. Running LANvoice with Windows 3.0 At this time Windows 3.0 does not support the necessary DMA requirements to run LANvoice. A detailed problem report has been filed through Microsoft's ON-Line service by our engineering staff. Misc Comments Make sure the network is loaded prior to Windows, and make sure no TSR utilities have been loaded prior to the network. Vendor Info: Microsoft Corp. One Microsoft Way Redmond, WA 98052-6399 FILE CONFIGURATION The following is a printout of all files (and command line descriptions) as a result of in house testing. Once again, these values may not necessarily reflect the necessary values for each configuration. CONTROL.INI {Contains info on colors and patterns. No modifications were made to this file} PROGMAN.INI {Contains path information on groups. No modifications were made to this file} CONFIG.SYS {Contains the minimum required values for Windows 3.0} files=50 buffers=30 lastdrive=z {sets drive designation for network recognition} device=c:\himem.sys {added during Windows install, required for standard / enhanced modes} device=C:\windows\mouse.sys /Y {added during Windows install} stacks=0,0 {recommended by Microsoft for versions of MSDOS 3.3 or later} AUTOEXEC.BAT {Contains the minimum required values to load the network} prompt [$p] path c:\dos;c:\lantasti;c:\windows {Note that this is a sample path for a server running Windows from a local drive. If this machine were running Windows as a workstation, the path might look like: path c:\dos;c:\lantasti;c:\winfiles;w:\windows, Where the W:\WINDOWS indicates the redirected network drive on which Windows has been installed and the C:\WINFILES indicates the location of the local configuration .INI files for that workstation} AE2 {loads the low level driver for our ethernet adapter} AILANBIO {loads the NetBIOS interface for our ethernet adapter.} REDIR lab386 {loads the network redirector} share SERVER {loads the network server} SYSTEM.INI {Contains Windows system configuration} [boot] 386grabber=vga.gr3 286grabber=vgacolor.gr2 shell=progman.exe network.drv=msnet.drv language.dll= fixedfon.fon=vgafix.fon comm.drv=comm.drv sound.drv=sound.drv oemfonts.fon=vgaoem.fon fonts.fon=vgasys.fon mouse.drv=mouse.drv keyboard.drv=keyboard.drv display.drv=vga.drv system.drv=system.drv [keyboard] subtype= type=4 oemansi.bin= keyboard.dll= [boot.description] network.drv=Microsoft Network (or 100% compatible) language.dll=English (American) SYSTEM.INI Cont. keyboard.typ=Enhanced 101 or 102 key US and Non US keyboards mouse.drv=Microsoft, or IBM PS/2 display.drv=VGA system.drv=MS-DOS or PC-DOS System [386Enh] EMMExclude=D800-DFFF {This line must be added if there is a possibility of RAMBASE conflict with the network adapter. Specify the RAMBASE the network adapter is using. In this case, I have used the RAMBASE default setting of the 2mbps adapter} NetHeapSize=XX {A Windows app may not run correctly if it requires a larger buffer for transferring data over the network than Windows provides. The NetHeapSize tells Windows the max buffer size in Kb required for this data transfer. the default value (for the Microsoft version) is 12, and all values are rounded up to the nearest 4K. Microsoft's initial tests ran with a value of 76. Please refer to the Microsoft Windows manual, Using Networks With Windows, page 552, for more information.} InDOSPolling=TRUE {Value should be TRUE, ON, YES or 1} NetDMASize=XX {Add the NetDMASize setting if you need to tell Windows how much memory (in Kb) to reserve for direct memory access. The default value is 32 on Micro Channel machines and 0 on others} ebios=*ebios display=*vddvga keyboard=*vkd mouse=*vmd network=*vnetbios, *dosnet device=*vpicd device=*vtd device=*reboot device=*vdmad device=*vsd device=*v86mmgr device=*pageswap device=*dosmgr device=*vmpoll device=*wshell device=*vhd device=*vfd device=*vpd device=*parity device=*biosxlat device=*vcd device=*vmcpd device=*combuff device=*cdpscsi local=CON FileSysChange=off CGA40WOA.FON=CGA40WOA.FON CGA80WOA.FON=CGA80WOA.FON EGA40WOA.FON=EGA40WOA.FON EGA80WOA.FON=EGA80WOA.FON [standard] [NonWindowsApp] WIN.INI [windows] load= run= Beep=yes Spooler=yes NullPort=None device=HP LaserJet III,HPPCL5A,LPT1.PRN BorderWidth=3 KeyboardSpeed=31 CursorBlinkRate=530 DoubleClickSpeed=452 Programs=com exe bat pif Documents= DeviceNotSelectedTimeout=15 TransmissionRetryTimeout=45 swapdisk= NetWarn=1 [Desktop] Pattern=(None) Wallpaper=chess.bmp TileWallpaper=1 GridGranularity=0 IconSpacing=75 [Extensions] cal=calendar.exe ^.cal crd=cardfile.exe ^.crd trm=terminal.exe ^.trm txt=notepad.exe ^.txt ini=notepad.exe ^.ini pcx=pbrush.exe ^.pcx bmp=pbrush.exe ^.bmp wri=write.exe ^.wri rec=recorder.exe ^.rec [intl] sCountry=United States [ports] ; A line with [filename].PRN followed by an equal sign causes ; [filename] to appear in the Control Panel's Printer Configuration dialog ; box. A printer connected to [filename] directs its output into this file. LPT1:= LPT2:= LPT3:= COM1:=9600,n,8,1 COM2:=9600,n,8,1 COM3:=9600,n,8,1 COM4:=9600,n,8,1 EPT:= FILE:= LPT1.OS2= LPT2.OS2= LPT1.PRN= {The LPTX.PRN line must be added for each LPT device (LPT1, LPT2...) to create a file name for that specific device. These filenames will then be listed under Printer Ports in the Printer Configuration} WIN.INI Cont. [Windows Help] Xl=169 Yu=125 Xr=576 Yd=428 Maximized=0 [fonts] {Default fonts installed for HP LaserJet III} Symbol 8,10,12,14,18,24 (VGA res)=SYMBOLE.FON Helv 8,10,12,14,18,24 (VGA res)=HELVE.FON Courier 10,12,15 (VGA res)=COURE.FON Tms Rmn 8,10,12,14,18,24 (VGA res)=TMSRE.FON Roman (All res)=ROMAN.FON Script (All res)=SCRIPT.FON Modern (All res)=MODERN.FON [HPPCL5A,LPT1] paper=1 duplex=0 prtcaps=-13440 paperind=0 FontSummary=C:\WINDOWS\SYSTEM\FSLPT1.PCL prtresfac=2 [PrinterPorts] HP LaserJet III=HPPCL5A,LPT1.PRN,15,45 LPT1.PRN= {The LPTX.PRN filename must be added at this point if one is to download certain third party fonts through Windows. It is our understanding that this line must be added AFTER the fonts have been created, so the fonts may be initially created in accordance with the printer drivers installed.} [devices] HP LaserJet III=HPPCL5A,LPT1.PRN [Solitaire] Back=3 Options=89 [HPPCL5A,LPT1.PRN] paper=1 duplex=0 prtcaps=-13440 paperind=0 FontSummary=C:\WINDOWS\SYSTEM\FSLPT1.PCL [SciCalc] layout=0 WINFILE.INI [Settings] SaveSettings=1 MinOnRun=0 Replace=0 LowerCase=0 StatusBar=1 CurrentView=0 CurrentSort=201 CurrentAttribs=1841 FINAL NOTE: Please remember that the values used in these .INI files are based on in house testing only, and may require modification according to your particular configuration. This document has been designed to help with your installation and setup of Windows and to provide a guideline for trouble shooting. If a unique problem arises which we are unable to resolve either through initial phone contact or through this bulletin, a problem report can be filed through our technical support staff. While we are able to provide full support with our network products, the complexity of Windows 3.0 may require the use of additional resources not available. LANtastic has not yet been certified by Microsoft as a supported network with Windows 3.0, so they may be limited in providing direct LANtastic/Windows support. However, we suggest that any non-network specific technical questions on Windows 3.0 that are not addressed in this bulletin be forwarded to Microsoft. Any questions or suggestions on this bulletin may be mailed to our offices to the attention of the Compatibility Department / Windows 3.0 Support.