Citrix Winview Application Note Meridian Data, Inc. CD-NET CD-ROM Server Software (Client only) DOS-Based CD-ROM Server Solution Version 5.0 This application note is for informational use only and Citrix makes no representations or warranties with respect to the contents or use of this document or of any of third-party products discussed within. (October 25, 1994) Citrix Systems 210 University Drive Suite 700 Coral Springs, FL 33071 Phone (305) 755-0559 FAX (305) 341-6880 Overview: ------------- This application note facilitates the configuration of the Meridian Data CD-NET CD-ROM DOS client with Citrix "WinView for Networks" Application Server Software. The Meridian Data CD-NET CD-ROM Server is a software package that utilizes a DOS machine with NetWare drivers to share CD-ROM's attached to it. The system comprises two major elements: 1. The CD-NET for DOS Server, which runs on a DOS machine, with a network interface card, appropriate network drivers, supported CD-ROM drives and controller. No Citrix software is needed on this machine. 2. The CD-NET for DOS Client software, which is run in a Specific DOS* session to give access to the CD-ROM's in the CD-NET Server. The CD-Net Client can be run under WinView 2.3 from a specific DOS session. The Citrix clients, LanLink and Remote Link, connect to the WinView Application Server and from a specific DOS session that allow access to the CD-ROM's available on the CD-NET CD-ROM server. The CD-ROM's can be accessed by applications, or by drive letter, as if they were local. Disclaimer: ---------------- The scenarios described in this document have been tested by Citrix Systems. Other variations to the scenarios described in this document may work, however they have not specifically been tested by Citrix. In order to recreate the configurations, you should use the specified revision levels of all software products described in this document and stay within the bounds of the features and functions described in this document. Please note that this application note is a living document and will be modified as new information and versions of the software described herein become availiable. Make sure you have the latest version of this document before you begin. The latest version is always available in the Citrix Forum on Compuserve. Requirements: --------------------- Software 1. Citrix WinView for Networks Version 2.3 2. Meridian Data CD-NET Version 5.0 software Hardware 1. WinView Application Server 2. Citrix clients running Remote Link, IPLink, or Lanlink 3. CD-NET CD-ROM Server (Dos machine with CD-ROM drives as per CD-Net requirments) 4. Novell Fileserver running NetWare 2.15 or above This document assumes a Novell fileserver and DOS 5.00 (for Specific DOS box) are being used, and that the WinView boot drive is C:. Substitute your WinView boot drive letter in place of C:. The CD-NET Server is installed as per the Meridian CD Server installation guide. This document covers preparation of Specific DOS sessions on the WinView Application Server to run the CD-NET Client software. Setup -------- CD-NET CD Server Installation -------------------------------------------- 1. Install and configure a standard DOS machine with CD-NET Server software as per the Meridian Data server installation guide. No special changes are required for operation with WinView Application Servers as clients. CD-NET Client software ---------------------------------- 1. At the console of the WinView Application Server, open a DOS session and install the CD-NET client software as per the Meridian CD-NET Client software installation manual. No special changes are necessary for WinView Application Servers. Specific DOS Session Configuration ---------------------------------------------------- To use the CD-NET V5.0 client under WinView 2.3, we must first create a Specific DOS session, because the CD-NET Client will NOT run under a WinView DOS prompt. A standard DOS machine is required to create the boot diskette. DOS 5.00 is recommended, because it uses the least amount of RAM. Since we are using a non-WinView virtual DOS session, upper memory is not available. This means we have 640K to work with, but the WinView drivers for Novell are gracious in their memory requirements. Creating a DOS 5.00 Boot Diskette --------------------------------------------------- 1. A. Use FORMAT A: /S /U Format the blank disk as a bootable disk B. Make a directory on the WinView drive to hold the DOS 5.00 files. C. Copy all the DOS 5.00 files from the DOS workstation's DOS directory, to the directory. For example, during this test, C:\OS2\DOS50 was used to hold the DOS 5.00 files. D. Put the bootable DOS 5.00 floppy disk in the WinView server A: drive. E. Copy FSFILTER.SYS, FSACCESS.EXE, and ANSI.SYS from C:\OS2\MDOS to the A: floppy. F. Copy DOSVIPX.SYS and DOSVSHLL.SYS from C:\NETWARE to the A: floppy. 2. Edit a CONFIG.SYS file on the A: floppy to include at least the following: DEVICE=FSFILTER.SYS <-- gives access to WinView hard disk DEVICE=DOSVIPX.SYS <-- gives IPX access (for LAN's) DEVICE=DOSVSHLL.SYS <-- gives Novell NetWare Shell DEVICE=C:\OS2\MDOS\ANSI.SYS <-- gives the proper ANSI emulation FILES=40 BUFFERS=20 3. Edit an AUTOEXEC.BAT file on the A: floppy to include at least the following: PROMPT [WV23/DOS5] $P-$G <-- prompt tells that DOS 5 is running SET COMSPEC=C:\OS2\DOS50\COMMAND.COM <-- make sure the COMSPEC is set! PATH C:\OS2\DOS50;C:\OS2;C:\OS2\MDOS; <-- set the DOS path as needed. C:\OS2\MDOS\MOUSE.COM <-- activated mouse (on console only) DOSKey Test Booting from DOS 5.00 Disk ------------------------------------------------ 1. A. Login to the WinView server using an administrative account. B. Run CFGAPP to create a profile named DOS5A.PSF C. Leave the settings to the default except for below: * DOS Full Screen session * UMB's OFF * DOS HIGH OFF * SHELL left blank * DOS Startup Drive set to A: * VIPX enabled ON * NetWare resources set to Force Global D. Insert this .PSF file into the PSEL menu, and execute it. C:\OS2\MDOS\EXITDOS.COM will exit out of the session. when verified that everything works ok, proceed to creating an image file. Creating a Boot Image File -------------------------------------- 1. A. Run VMDISK A: C:\OS2\DOS50\DOS50.IMG 2. A. Run CFGAPP to create a profile named DOS50IMG.PSF B. Leave the settings to the default except for below: * DOS Full Screen Session * UMB's OFF * DOS HIGH OFF * SHELL left blank * DOS Startup Drive set to C:\OS2\DOS50\DOS50.IMG (or the image filename you used in image creation) * VIPX Enabled set to ON * NetWare resources set to Force Global C. Insert this .PSF file into the PSEL menu, and execute it. Note that until 'FSACCESS.EXE A:' is run from the C: drive, A: will reference the image file. EXITDOS.COM will exit this session D. The .PSF file created can be installed on other user profiles via the standard WinView Application Server administration utilities. Operation -------------- 1. Run RLINK, LANLINK, or IPLINK to attach to the WinView Application Server NOTE: The WinView client used does not matter, but the connection between the WinView Application Server and the CD-NET CD-Server MUST use IPX/SPX transport protocol. 2. Once logged in, and at the PSEL, the Specific DOS session can be opened, and the CD-NET client software can be run from it's batch file. Notes --------- 1. Only the Client software will function in a Specific DOS session. The Server software is not supported. Note that with no LASTDRIVE= in the CONFIG.SYS of the image files, the last letter usable for CD-NET is E:, which is the DOS default. 2. Most, if not all, of the WinView will not function in a Specific DOS session. Utilities such as QUERY, CONFIG, and the CFG??? will function ONLY in a standard WinView OS/2 or DOS session. 3. Only (1) session can use any given image file at once, even if a previous started session has executed FSACCESS.EXE to access the A: drive. If multiple sessions are required, copy the image file to another filename, and create another .PSF profile for it. 4. When a client starts a Specific DOS session, a message will appear saying that VSHELL.SYS must be loaded for mouse support. Ignore this, as mouse support is NOT available in a Specific DOS session. If this driver is loaded in a statement in the CONFIG.SYS, the Specific DOS session will give a DOS TRAP error, and the session will end. 5. The use of Specific DOS sessions have the following side-effects: A. Use twice as much CPU time when task is active. B. Does not take advantage of full NetWare integration. (need to run login.exe from Novell \LOGIN directory) C. Multiple sessions can access the CD Server (see 3 above) up to the user limit of the server. Each session attaching will count as another user. D. Mouse support is unavailable in Specific DOS sessions, except when run on the console