Dear Customer,

On behalf of Miramar Systems, thank you for downloading Personal MACLAN Connect 
(for Windows 3.x), the leading Windows-based solution for PC-to-Mac networking.

	YOUR SERIAL NUMBER IS 55-35F1E54D.

If you require additional serial numbers to network more machines, 
call 1-800-862-2526 or, email us at sales@miramarsys.com.

Also, if you are a U.S. or Canadian customer, call now for our

****** SPECIAL LIMITED TIME OFFER and SAVE $100 *****

Upgrade directly from Miramar within the next 30 days, and get 
PC MACLAN for Windows 95/98 (V7.2 ) for only $99!


Lastly, if you should experience any problems during the installation, please 
feel free to visit our technical support web site at 
http://support.miramarsys.com/techsupp/ or email support@miramarsys.com.  We 
also offer limited technical support for our FREE products at 1-805-965-5161 
(8am-5pm PST).


Looking forward to serving you.
Sincerely,

Katherine Vargas
Customer Service/Sales Executive
kvargas@miramarsys.com
(800) 862-2526 Ext. 108

=============================================================================



Miramar Systems, Inc.
Personal MACLAN Connect v 5.53

-----------------------------------------------------------------------------
This document contains information not found in the Manual. Please read. 
-----------------------------------------------------------------------------

C O N T E N T S

 I.     Additional version information
 II.    Upgrading from Personal MACLAN v3.02 to 5.5
 III.   Unlisted Adapters Information  (ODI & NDIS3)
 IV     Errors on Startup - WIN 3.1,3.11,WfW 3.11
 V.     Errors during Installation - WIN 3.1,3.11,WfW 3.11
 VI.    Incompatible Network Adapters
 VII.   Performance Issues

============================================================================= 
I.  Additional version information

  This version of Personal MACLAN Connect will only install into Windows 3.1,
  Windows v3.11 and Windows for workgroups v3.11.  Please ignore any of the
  referenes to Windows 95 that are in the Help files.

=============================================================================
 II. Upgrading from Personal MACLAN v3.02 to 5.5

 Personal MACLAN version 5.5 is not compatible with version 3.02. To retain 
 Macintosh file structure it will be necessary to perform the following:
  
  1.Start Personal MACLAN ver.3.02

  2.Backup all Macintosh files located on your Personal MACLAN v3.02 Shares
	(the local PC hard drive) onto either a Macintosh hard drive or Macintosh
	compatible Tape backup system.

  3.Write down all Users and Groups as they will need to be re-entered in 
	the new version.

  4.Startup Personal MACLAN v5.0; define Shares, Users, Groups, etc...

  5.Restore Macintosh files from backup onto the newly created /Volumes/Shares.

=============================================================================
 III. Unlisted Adapters information

  If you have a Network adapter that was not listed during Install then 
  you will need to determine whether it came with NDIS or ODI drivers.

  ---------------------------------------------------------------------------
  A.For ODI unlisted Ethernet adapters

  If you cannot locate your specific network adapter from the Install 
  "Adapter selection list" perform the following STEPS:

	1.Locate the ODI driver on the disk that came with your adapter.
	  (XXXXXXXX.COM)

	2.Copy the ODI driver file into the Personal MACLAN Installation
	  directory.
		Ex: Copy A:\ODI\XXXXXXXX.COM C:\PMACLAN5
	
	3.Run INSTALL, select INSTALL AppleTalk Network Drivers and select 
	  UNLISTED adapter from the NET CARD list.

	4.After INSTALL  use a text editor like NOTEPAD and edit the NET.CFG
	  file located in the Personal MACLAN Installation directory and
	  change all XXXXX text to the name of your ODI driver.

	5.Using a text editor, edit the PMDRIVER.BAT file located in the
	  Personal MACLAN Installation directory & change XXXXX text to the
	  name of your ODI driver.

  If your adapter has settings such as different interrupts, DMA, Memory 
  Address, Port Address than those presented during installation it maybe
  necessary to edit the NET.CFG file located in the PMACLAN5 directory.

	Example:

LINK SUPPORT
   BUFFERS 9 628
   MEMPOOL 16K
   MAX BOARDS 4

LINK DRIVER XXXXX       ----->XXXXX          change to your drivers name
#   UNLISTED ADAPTER NAME    
	INT #1 9            ----->INTERRUPT      change 9 to your value
	PORT #1 200 8       ----->PORT ADDRESS   change 200 to your value
	DMA #1 3            ----->DMA Channel    change 3 to your value
	MEM #1 C000 10      ----->Memory Address change C000 10 to your value   
	FRAME ETHERNET_SNAP         
	FRAME ETHERNET_II
	FRAME ETHERNET_802.2
	FRAME ETHERNET_802.3
	PROTOCOL IPX 0 ETHERNET_802.3
	PROTOCOL APPLETALK 80007809B ETHERNET_SNAP
	PROTOCOL AARP 80F3 ETHERNET_SNAP

  --------------------------------------------------------------------------
  B.For NDIS3 unlisted adapters. 
        If you do not have Windows for WorkGroups v3.11 skip this section.
  
	1.Run Windows Setup or Network Setup from Windows. 

	2.Select Drivers 

	3.Select Add adapter to see if your Network adapter is listed. If it's
	  unlisted follow the manufacturers' directions on installing NDIS3 
	  drivers for Windows.

	4.If you find your adapter, select it.
	  Double click on the adapter and the Drivers window will appear. 

	5.Select "Enhanced Mode NDIS Driver" then proceed as normal.  

	Be sure to check your Windows for WorkGroups manual for details.

  --------------------------------------------------------------------------
  C.For WINDOWS 3.1 ODI or Windows for WorkGroups ODI Unlisted Token 
	Ring adapter follow these steps:

	1.Make a backup copy of DISK1

	2.On your backup copy of DISK1 rename UNLISTED.DEF to UNLISTED.BAK

	3.On your backup copy of DISK1 rename UNLISTTR.DEF UNLISTED.DEF

	4.Proceed with Install and select UNLISTED adapter during the ODI
	  Network adapter selection dialog.
 
=============================================================================
IV. ERRORS during system STARTUP - WIN 3.1,3.11,WfW 3.11
  --------------------------------------------------------------------------
  "Need to run LSL.COM" This error will occur if you are running Novell
  Netware and Install detected LSL.COM in system memory.

  FIX:  Edit your AUTOEXEC.BAT and move the "CALL PMDRIVER.BAT" 
	statement AFTER the line(s) that execute the LSL and MLID 
	statements.

  Example:
	Before  CALL PMDRIVER.BAT
		PATH C:\DOS;C:\WINDOWS
		C:\NETWARE\LSL
		C:\NETWARE\3C5X9
		etc....
 
	After   PATH C:\DOS;C:\WINDOWS
		C:\NETWARE\LSL
		C:\NETWARE\3C5X9
		CALL PMDRIVER.BAT
		etc....
	
  NOTE:All network device drivers are provided for the exclusive use of
  Personal MACLAN Connect using the manufacturer's proprietary network 
  adapters. Using a manufacturer's network drivers with another manufac-
  turers' network adapter is strictly prohibited.

=============================================================================
V. ERRORS during INSTALLATION - WIN 3.1,3.11,WfW 3.11

  1.Personal MACLAN may have detected incompatible AppleTalk drivers on
	your system.  Please remove all items as listed below from your 
	system  files.

	Install reports "Found Farallon"

	 IN AUTOEXEC.BAT 
				"aboth.bat"  may appear as "call ABOTH.BAT"
				"aprint.bat" may appear as "call APRINT.BAT"
				"afiles.bat" may appear as "call AFILES.BAT"
				"aarp.com"
				"atalk.com"
				"pntvdd.exe"
  
  IN FILE DIRECTORIES
	Locate your "c:\phonenet" directory and rename "net.cfg" to "net.xxx".

  IN SYSTEM.INI
	 Edit & remove: "PhoneNETMemoryPool" statement from the  "386Enh" section

2. Personal MACLAN has detected a previous installation. Drivers are
   incompatible with version 5.xx

	Found earlier version MACLAN Connect/Personal MACLAN
	  IN AUTOEXEC.BAT
					 ATDRIVER.BAT        
					 MLDRIVER.BAT
					 LMSTART.BAT

3. Personal MACLAN has detected AppleShare for Windows installation. This 
   is compatible with Personal MACLAN versions 5.xx

	Found AppleShare
	IN AUTOEXEC.BAT
					"ATDRIVER.BAT"

=============================================================================
VI. Incompatible Adapters (ODI & NDIS3)

  Some older adapters have not had their ODI driver updated by the manufacturer
  and have become out of spec to the current requirements of ODI and NDIS3.
  The following list contains the adapter, the problem you may experience and
  a possible workaround.

  NE1000                  
  Problem:   Incompatible, obsolete drivers.
  solution:  None

  INTEL ETHER EXPRESS PRO  
  Problem:   Windows freezes at splash/intro screen
			 Windows freezes on re-entry after closing

  Solution:  1.If running Windows for WorkGroups select the ODI protocol
			 2.Obtain the latest NDIS3 driver. 
			 EPRO.386 dated 2/21/95 or later NDIS3 (in the Windows SYSTEM dir)
			 EPRO.DOS dated 5/09/95 or later NDIS2/NDIS3 (in the Windows dir) 

  APPLE LOCALTALK
  Problem:   Incompatible, obsolete drivers.
  Solution:  Use a Dayna or Farallon LocalTalk (PC3) adapter instead.

  TOPS/SITKA CARDS
  Problem:   Incompatible, obsolete drivers.
  Solution:  Use a Dayna or Farallon LocalTalk (PC3) adapter instead.

  SMC 8216  
  Problem:   Can cause a Page Fault (Blank screen with flashing cursor) if the
			 cable is disconnected from adapter during a file copy.
  Solution:  Obtain the latest NDIS3 drivers from SMC. ODI does not have this
			 problem.

=============================================================================
VII. Performance Issues

  Some network adapters drivers may not perform to your expectations.  Miramar 
  recommends that you always use the latest drivers available from the 
  manufacturer.  You can also try switching from ODI to NDIS3 or NDIS3 to ODI 
  and compare performance. Note that NDIS3 protocol is only available in 
  Windows for WorkGroups v3.11 and later.

  Make sure that there are no conflicts with Memory, Interrupts, DMA etc... 
  as this can also cause poor performance.  The higher the CPU power the better 
  Personal MACLAN will perform.
 
=============================================================================                    

			 D I S C L A I M E R

Miramar Systems makes no guarantees as to the compatibility with any third 
party device drivers operability with Miramar products. IN NO EVENT SHALL  
MIRAMAR SYSTEMS, INC. HAVE ANY LIABILITY FOR ANY SPECIAL, INDIRECT, OR 
CONSEQUENTIAL DAMAGES INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOST 
PROFITS, BUSINESS INTERRUPTION, LOSS OF USE OF EQUIPMENT, LOSS OF DATA 
OR COSTS OR PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES, ARISING IN ANY 
WAY, OR UNDER ANY CAUSE OF ACTION, WHETHER OR NOT MIRAMAR SYSTEMS, INC. 
OR AN AUTHORIZED REPRESENTATIVE OF MIRAMAR SYSTEMS,INC. HAS BEEN ADVISED
OF THE POSSIBILITY OF SUCH DAMAGES. THESE LIMITATIONS SHALL APPLY NOTWITH-
STANDING THE FAILURE OF THE ESSENTIAL PURPOSE OF ANY LIMITED REMEDY.
