аЯрЁБс>ўџ ўџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџ§џџџўџџџўџџџ  ўџџџўџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџRoot Entryџџџџџџџџ РF аvDЧЏК€WordDocumentџџџџџџџџ )CompObjџџџџџџџџџџџџnџџџџџџџџџџџџўџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџill support the command line syntax of the TRCDLC utility. No support related to connecting to another computer with this protocol will be provided by Microsoft. For more information about server related settings or other information regarding setting requirements to connect to the server via Microsoft 32 bit DLC protocol (MSDLC32), please contact your System Administrator or the Manufacturer of the network software utilizing the protocol. END OF README.DOC ќLMNOZ\]^КЛМЦЧвгкл  ()FGQRqr|}ЫЬийії)*34VWX~€ЃќљїѕёюьшцфтромкиждваЮЬЪШЦФТРОМКИЖДВАЎЌЊЈІЄЂ žœš–’‹ˆU]]]U]U]^]c]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]c]U]U]^]]U]U]5ЃЄЅОбвUVWhuv>?@A_`a†‡ЁЂЛМН      b c d     P Q S T _ ` b c s t v w ˆ ќљієђ№юьщчхусплйзегбЯЭЫЩЧХУСПНЛЗДВАЎЌЊЈІЄЂ žœš˜–”’ŽŒŠ]]]]]]]]]]]]]]]]]]]]]]^U]^]]]]]]]]]]]]]]]]U]^]]]]]U]]]]]]U]U]U]6ˆ ‰ ‹ Œ Ш Щ й к м н ч ш ъ ы     Y Z [ ~  ‚ ƒ Е Ж З Т џ  = > ? S T U ‚ ƒ „ ! " + , 5 6 7 M N O P €§ћљїѕѓёяэыщчхуспнлйзегбЯЭЫШХУСПНЛЙЗЕГЏЋЇЅЃЁŸ›™•’‹‰]]]U]U]U]^]]]]]]]U]^U]^U]^]]]]]]]]]U]U]]]]]]]]]]]]]]]]]]]]]]]]]]]5€‰Š‹ŒЫЬ`almš›йкUVŽЇЈклєѕі]^ЂЃуф+,;<=…†ЧШcdИЙ§љієђ№юьъшцфтромкиждваЮЬЪШЦФТРОКИЖДВАЎЌЊЈІЄЂ žœš˜–”’ŽŒ]]]]]]]]]]]]]]]]]]]]]]]U]^]]]]]]]]]]]]]]]]]]]]]]]]]]]]U]U]^]7ЙТУФеж§ћљіє]U]]]]ќMNO]^ЛМгGrЬї*WX€ЄЅвVљєяъхрлжбЬЧТМЗВ­ЈЃž™”Š№№№№№№№№№№жќ№№№№№№№№№№№№јј№VWv@A`a‡ЂМН   њѕ№ыцсмзГkfa\W№№№№# 4hЗh˜ў№# 4hЗh˜ў№# 4hЗh˜ў№№№№№№№№№мЅe#Р ќж)к,(l,(l(( ( ЊR((ь(˜(Tю( RMS Sans Serif Symbol SystemTimes New Roman ArialMicrosoft 32-bit DLC protocol stack - Release version: 4.10.989. Nov. 10, 1995 1. CONTENTS: The MSDLC32.exe file is a self-extracting compressed file that contains the following files: README.DOC - This file DLC.VXD - the retail version of the DLC driver DLCAPI.DLL - the ACSLAN DLL DLCNDI.DLL - the custom installation DLL TRCDLC.EXE - the trace utility application DLCHLP.EXE - the 16-bit helper executable for CCB1 support for DOS and Win16 applications NETDLC32.INF - the installation/setup file DLC32.HLP - Help file for configuration parameters DLC32.CNT - configuration file for DLC32.HLP 2. THINGS TO CONSIDER WHEN INSTALLING : MS 32-bit DLC Protocol stack over: - IBM LAN Support Program (DXM mode drivers) You first need to remove the "existing IBM DLC" from the Control Panel Network setup and then add the MS 32-bit DLC protocol stack. - MADGE SMART.EXE (Token-Ring) You first need to remove the "existing ODI driver" from the Control Panel Network setup. Then add the NDIS3.1 TR MADGE driver and the MS 32-bit DLC protocol stack. 3. APPLICATION COMPATIBILITY ISSUES: The following applications require a TSR (Terminate and Stay Resident) program to connect to a host computer prior to starting Windows 95. These applications work with the MS 16bit DLC protocol that shipped with Windows 95 but WILL NOT work with the Microsoft 32-bit DLC protocol stack. IBM PC SUPPORT (versions V2R1 - V2R3) RELAY GOLD v. 5.0 and 6.0a EICON ACCESS 5250 v. 3.21 Please contact your vendor for updated information on these products. 4. INSTALLATION Please follow the following steps to install the Microsoft 32-bit DLC product 1) Create an installation disk or create a temp directory on your hard disk. Copy the MSDLC32.EXE into the directory. Run MSDLC32.EXE to extract the files. 2) Invoke the Network Control panel (My Computer -> Control Panel -> Network). 3) Select Add. 4) Select Protocol. 5) Select Have Disk. 6) Specify the drive and path for the installation disk ( e.g., A:\ or C:\DLC32) 7) Select OK 8) Select "Microsoft 32-bit DLC" and select OK. 9) The system will ask you to insert Windows 95 disks and it will reinstall other Network components. 10) The system will prompt you to shutdown and reboot. Attention: Unless you want to change the CCB adapter number association, shutdown and reboot the system. See below for how to modify CCB adapter numbers. 5. Installation of the 32 bit DLC Help file. A DLC32.HLP file. The setup program does not copy the help files to your Windows help directory. Copy the following files to your WINDOWS\HELP sub-directory: DLC32.HLP DLC32.CNT 6. CCB Adapter Numbers: The installation process automatically associates a unique CCB adapter number with each adapter bound to the 32-bit DLC protocol. This unique number may be modified by the user in the Advanced property sheet identified by the CCB Adapter Num parameter. The valid value for this field is 0 through F. 7. NOTES: 1) After rebooting you can verify that the driver is installed by running TRCDLC. To do this, open a DOS window and type: \windows\system\trcdlc -s. This causes the driver to return its version number and build time stamp. 2) To run TRCDLC type: \WINDOWS\SYSTEM\TRCDLC This will trace the most interesting events including sent and received data. Trace output by default goes to the screen and to two "tumbling" trace files - TRCDLC0.DAT and TRCDLC1.DAT. 3) To get help on the TRCDLC command line options type: \WINDOWS\SYSTEM\TRCDLC -H 4) To close TRCDLC - from another DOS window type: \WINDOWS\SYSTEM\TRCDLC -C Microsoft Product Support (PSS) Microsoft Product Support Services will support installation of this protocol via the user interface, functionality of the configuration dialogs, and booting without error with the protocol installed. Personal Operating Systems w  c d  Q ` t ‰ к ш  Z  Ж > T U ƒ „ " њѕ№шуойдЯЪХРЛЖБЌЇЂš•№№h˜ў№№№№№№№№№№№№№№№а0§№№№№" , 6 7 O P €‹Ьam›кVŽлЗВ­ЈЃž™”Š…€{vqlg№№№№№№№№№№№№№№№№# 4hЗh˜ў№# 4hЗh˜ў№ŽЈлѕі^Ѓф,<=†ШdЙУФжњѕ№ыцсмзвЭШУОЙДЏЊЅ ›№№№№№№№№№№№№№№№№№№№№ќж ќжкџџџџџџџџ,%K@ёџNormala "A@ђџЁ"Default Paragraph Fontаџ@џџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџўџ џџџџ РFMicrosoft Word 6.0 Document MSWordDocWord.Document.6є9ВqаЯрЁБсаЯрЁБс>ўџ ўџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџ