NOVELL TECHNICAL INFORMATION DOCUMENT DOCUMENT PROCESSING INFO: TITLE: NETWARE TROUBLESHOOTING WITH DR DOS 6 DOCUMENT ID: TID800064 DOCUMENT REVISION: A DATE: 18AUG94 AUTHOR: SNICOSIA;CEREKSON ALERT STATUS: Yellow DISTRIBUTION: Public INFORMATION TYPE: Symptom Solution README FOR: NA NOVELL PRODUCT CLASS: Desktop Products NOVELL PRODUCT and VERSION: DR DOS 6.0 CATEGORY: Client ABSTRACT: N/A ----------------------------------------------------------------- DISCLAIMER THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO NOVELL. NOVELL MAKES EVERY EFFORT WITHIN ITS MEANS TO VERIFY THIS INFORMATION. HOWEVER, THE INFORMATION PROVIDED IN THIS DOCUMENT IS FOR YOUR INFORMATION ONLY. NOVELL MAKES NO EXPLICIT OR IMPLIED CLAIMS TO THE VALIDITY OF THIS INFORMATION. ----------------------------------------------------------------- SYMPTOM SYMPTOM: PROBLEMS LOADING NETWARE DRIVERS WITH DR DOS 6 CAUSE ISSUE/PROBLEM: Common Questions. SOLUTION SOLUTION: Here are some common questions and answers on using NetWare and DR DOS 6. Q - NetWare shell programs won't load into upper memory. A - Make sure that upper memory is available and that the size of one or more upper memory areas marked as FREE exceeds the size of the NetWare shell program that is loaded into conventional memory instead of upper memory. (See the DR DOS 6.0 User Guide, Chapter 10, for more information on the MEMMAX and MEM commands and how they can be used to determine if the above conditions aremet.) Also, consider the following: For EMM386.SYS users: * You can append the /LOWEMM switch to the EMM386.SYS device driver line in the CONFIG.SYS file. The EMM386.SYS device driver leaves its program code in conventional memory, which should provide an additional 28K of upper memory. * If LIM (Expanded memory) is not really necessary, consider disabling it. Change the /FRAME switch on the EMM386.SYS device driver line so that it reads /F=NONE. * If LIM is necessary, you might consider using another NetWare shell instead of NETX.COM. Refer to the Novell reference manuals for information on how EMSNETX.COM and XMSNETX.COM work. Do not use the HILOAD command with either EMSNETX.COM or XMSNETX.COM. * With XMSNETX.COM the /BDOS switch on the EMM386.SYS device driver line should be changed so that it reads /B=AUTO or /B=NONE. Try changing the line that reads HIDOS=ON in the CONFIG.SYS file so that it reads HIDOS=OFF. This prevents the DR DOS 6.0 operating system from automatically relocating certain portions of the operating system into upper memory. * If only text-based applications will be run at this workstation, use the /VIDEO switch on the EMM386.SYS device driver line along with the MEMMAX +V command to enable the use of video RAM for extending conventional memory. This relieves the need to relocate the NetWare shell programs into upper memory. For HIDOS.SYS users: * Verify that the computer will supports upper memory. The DR DOS 6.0 User Guide, Chapter 12, has information on what regions are available on certain computers. * Consider using XMSNETX.COM instead of NETX.COM. With XMSNETX.COM, change the /BDOS switch on the HIDOS.SYS device driver line so that it reads /B=AUTO or /B=NONE. * If you are using HIDOS.SYS with the /CHIPSET option set to EMSUMB, consider disabling the LIM (Expanded memory) support provided by your LIM 4.0 driver by using the /CHIPSET=EMSALL option instead. EMSALL will disable the LIM 4.0 page frame and make available a larger region of upper memory for mappable RAM. * If your machine is equipped with at least 64K of extended memory above one megabyte, make sure that the /BDOS switch on the HIDOS.SYS device driver line reads /B=FFFF. * Try changing the line that reads HIDOS=ON in your CONFIG.SYS file so that it reads HIDOS=OFF. This prevents the DR DOS 6.0 operating system from automatically relocating certain portions of the operating system into upper memory. This will free those regions for loading NetWare drivers. * Use the /VIDEO switch on the HIDOS.SYS device driver line along with the MEMMAX +V command to enable the use of video RAM for extending conventional memory. This relieves the need to relocate the NetWare shell programs into upper memory. Q - Machine locks up when trying to load NetWare shell programs. A - Some network cards maintain ROM addresses in the upper memory region. The MemoryMAX drivers (EMM386.SYS or HIDOS.SYS) are not able to recognize such areas because at the time they load these areas are not in use by the network card. If DR DOS 6.0 has written some portion of the operating system to a region of upper memory, which later gets used by the network card's ROM, the system might hang unpredictably. To correct this problem, append an /EXCLUDE switch to the MemoryMAX device driver line in the CONFIG.SYS file to prevent the MemoryMAX driver from attempting to use an area known to be used by the network card. Refer to your documentation on the network card for information on areas used in upper memory and follow the instructions for using the /EXCLUDE switch on those areas as shown in the HIDOS.SYS and EMM386.SYS sections of Chapter 11 in the DR DOS 6.0 User Guide. If you installed Novell NetWare, or you installed additional hardware in your computer after you installed the DR DOS 6.0 operating system, it is possible that the IRQ or DMA settings on the new hardware might be conflicting with existing hardware. In this case, it is best to resolve hardware conflicts by changing the configuration of one or more installed boards before changing the configuration of DR DOS. Q - The computer locks or generates "Packed file corrupt" error message when executing Novell NetWare utility programs. A - This situation might occur in older versions of the NetWare utilities. The error message does not reflect the true cause of the problem. Use the MEMMAX -L command before executing the problematic NetWare utility, and then use the MEMMAX +L command after executing the NetWare utility in question. The following is an example of how this might look in the AUTOEXEC.BAT or login file: MEMMAX -L LOGIN MEMMAX +L Q - COMPAQ DOS 3.31 and DR DOS clients are mapping the same directories. When setting up a Novell NetWare Network Server machine, it is normal for a Network Administrator to actually create a directory structure on the server's hard disk which contains all of the various DOS operating system files for all the DOS operating systems being used by the network's DOS clients. A line like MAP INS S2:=SYS:PUBLIC/%OS/%OS_VERSION in the System Login Script will not handle the mapping for DR DOS properly if Compaq DOS 3.31 is also on the server. When DR DOS is the DOS client's operating system, the %OS and %OS_VERSION variables actually return MS DOS and v3.31 respectively. Both COMPAQ DOS 3.31 and DR DOS versions 5.0 and 6.0 will end up being mapped to the same sub-directory on the NetWare server's hard drive. Because the DR DOS client operating system actually maintains two environment variables called OS and VER which equal DRDOS and 6.0 respectively, it is actually possible to test the DOS client operating system in the System Login Script to determine if the DOS client is running COMPAQ DOS 3.31 or DR DOS 6.0. Once the DR DOS client is detected, the Login Script should map the client to a directory with the following path: SYS:PUBLIC/PC_DOS/DRDOS/6.0 This sample System Login Script explains and implements such a technique: REM These lines establish environment variables OS and VER REM if the DOS client is NOT running DR DOS (any version). REM That is, any DOS client operating system other than REM DR DOS does not already maintain the environment REM variables OS and VER, and as a result, REM they need to be set. IF != "DRDOS" AND != "DRMDOS" THEN BEGIN DOS SET OS="%OS" DOS SET VER="%OS_VERSION" END REM All that's left to be done is to map the DOS client using REM the DOS environment variables and . MAP INS S2:=%FILE_SERVER/SYS:PUBLIC/%MACHINE/%/% COMSPEC=S2:COMMAND.COM The above script would result in the following: Compaq DOS 3.31's map: SYS:PUBLIC\PC_DOS\MSDOS\3.31\ DR DOS 6.0's map: SYS:PUBLIC\PC_DOS\DRDOS\6.0\ DR Multiuser DOS's map: SYS:PUBLIC\PC_DOS\DRMDOS\5.0\ KEY WORDS: DR6 NETWARE ----------------------------------------------------------------- Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information. -----------------------------------------------------------------