WPC> 2 B V J Z Courier T ? x x x x 6X @ K X@Apple LaserWriter IINTX APLASIIN.PRS x @ hhhhSSX@#| x 2 < FYI:NetWare v2.2 and Leading Edge Keyboard Response Problems FYI (Note: 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.) TITLE: NetWare v2.2 and Leading Edge Keyboard Response Problems DOCUMENT ID#: FYI.P.9915 DATE: 20DEC91 PRODUCT: NetWare PRODUCT VERSION: v2.2, v2.1x SUPERSEDES: NA SYMPTOM: Erratic keyboard response ISSUE/PROBLEM When running Nondedicated NetWare versions 2.2 and 2.1x on Leading Edge's D3/33, MT33, and D3/SX20c machines, in DOS mode, the server experiences erratic keyboard response. SOLUTION KBDPATCH.EXE, which has been tested on NetWare versions 2.2, 2.15c, ELS II v2.15, and ELS I v2.12, fixes the problem. It can be found on NetWire in NOVLIB 17 as LEKBD.ZIP. It can also be found on Leading Edge's bulletin board (508-836-3967, 2400 baud 8 data bits and 1 stop bit) in the D-UTILS directory as KBDPATCH.EXE. FYI: Restoring Users From Backup 286 NetWare FYI (Note: 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.) TITLE: Restoring Users From Backup 286 NetWare DOCUMENT ID#: FYI.P.4815 DATE: 02DEC91 PRODUCT: NetWare PRODUCT VERSION: v2.15c, v2.2 SUPERSEDES: NA SYMPTOM: User does not have any disk space available on the file server. ISSUE/PROBLEM h) 0*0*0* Ԍ SPD #8327. A NetWare v2.15c server is set up to limit disk access for the users. If the server is backed up and a user is deleted, and then the user is restored with the associated trustee rights to the directories, the user will no longer have any space on the disk. The backup software was written by an unnamed developer who reported the problem through Austin developer support. A similar situation occurred with another customer using v2.2. In this case the customer was upgrading the hard disk and when he restored users, the DIR command would show no disk space available for users (0 bytes free). The Supervisor did not have the problem. This customer was using the Mountain Tape backup v5.2.3 to backup data and binderies. SOLUTION This has been reported to Engineering as a problem with the OS and a need to re-initialize the disk space limitation structure after the bindery is restored. The solution is to reboot the server. In the case of the V2.2 server above, the server had not been rebooted since the restore and the problem was corrected upon rebooting. FYI: NSD003.ZIP Upload To Compuserve FYI (Note: 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.) TITLE: NSD003.ZIP Upload To Compuserve DOCUMENT ID#: FYI.P.4806 DATE: 02DEC91 PRODUCT: NetWare Requester for OS/2 PRODUCT VERSION: v1.3 SUPERSEDES: NA SYMPTOM: NA ISSUE/PROBLEM This concerns the file NSD003.ZIP which is available on NetWire. This is a Novell Service Diskette #3 (NSD #3). It solves h) 0*0*0* minor problems found in the NetWare Requester for OS/2 version 1.3 software. This third NSD incorporates all changes from the first and second NSDs. PROBLEMS SOLVED BY THIS NSD (#3) * ` ` You will now see "OS/2 Requester: V1.30 Rev. F" when you type NVER. * ` ` Previously, if your application or utility specified a UNC path with just a server and volume name (and no directory), you would receive a File Not Found error. This problem has been fixed. * ` ` The Requester now correctly reads directory attributes for fake root drives. * ` ` If your application issues a Named Pipes request when you are running dual requesters with NetWare loaded first and with NetWare Named Pipes support not loaded, the request is now properly passed on to the non-NetWare Requester. * ` ` The DOS box now supports closing and reopening file handles 0 through 4. * ` ` The Requester now automatically reattaches to a server if you lose your last connection. The Requester attaches to your preferred server or to the nearest server if you have not specified a preferred server. This enables you to log in again after a connection is lost without having the LOGIN utility on your local disk. * ` ` The Requester has been enabled so that it can support Double Byte Character Sets (DBCS). * ` ` When you run the WHOAMI utility on a NetWare v2.15 or v2.2 server, you will now see the correct connection number for your workstation. * ` ` If your workstation is a Named Pipes server, do not set your SPX connection limit higher than 255. * ` ` Previously, if you were running a multi-threaded program with all threads issuing SPX commands, one or more of the threads may have hung. This no longer occurs. * ` ` Previously, you received an error if you ` ` 1. ran a program off the network in one OS/2 session, and ` ` 2. opened a second session and ran the same program, and ` ` 3. closed the first program and exited the first session, and ` ` 4. opened a third session and tried to run the same program. This problem no longer occurs. h) 0*0*0* Ԍ * ` ` When using SPX applications, your workstation will no longer run out of SPX sessions or freeze up, as may have happened previously. * ` ` In some cases, your workstation may not have attached to a NetWare server upon booting. Your workstation will now attach properly. * ` ` Your workstation now provides diagnostic information for network management. * ` ` When using Named Pipes applications, your workstation will no longer freeze up, as may have happened previously. * ` ` Previously, when you typed CASTOFF ALL to turn off broadcast messages from a particular server, it appeared that you no longer had a connection to that server. This now works properly. * ` ` On a DOS workstation, you can specify the number of files that can be open simultaneously by using the FILES= option in the CONFIG.SYS file and the FILE HANDLES option in the SHELL.CFG file. The total number of files specified with these two options cannot exceed 253. When you load the Named Pipes Extender for DOS, the SHELL.CFG FILE HANDLES option is set to 40 by default. Therefore, the maximum number of files you can specify in CONFIG.SYS without adjusting the SHELL.CFG default is 213 (for a total of 253). If you specify more than 253 total files, when the Named Pipes Extender loads, you receive a message telling you to reduce the total number of files. * ` ` When you boot a workstation that is running both the Novell NetWare Requester and the IBM LAN Requester on an Ethernet network, you receive a message saying the workstation can't find a file server. The workstation actually does attach to a server. Please disregard the error message. * A check has been included to ensure that the NWIFS.IFS and NWREQ.SYS files are at the same revision level. If revision levels do not match, you will see the following error message: NWREQ.SYS version does not match NWIFS.IFS version. If you see this error message, reinstall NSD #3. PROBLEMS SOLVED BY NSD #2 * ` ` IPX options in NET.CFG no longer need to be followed by a space. * ` ` When using NETAPI.DLL for WINDOWS, you will no longer lose the functionality of your serial port, as may have happened previously. h) 0*0*0* Ԍ * ` ` Caching now works properly with any allowable size of Link Support Layer (LSL) buffer (see the NetWare Requester for OS/2 manual for allowable sizes). * ` ` Attempting to view a non-existent file or directory by typing the DIR command with wildcard characters now displays the proper error message. * ` ` You can now type a server and volume name using a Universal Naming Convention (UNC) path, and if that server or volume doesn't exist, the software will display the correct error message. PROBLEMS SOLVED BY NSD #1 * ` ` Applications that use NetWare routines from the NWCALLS.DLL file when the Requester is not loaded will no longer be terminated. Instead, they will receive the following error message: 88ff (REQUESTER NOT LOADED). * ` ` A sending and receiving error code is now properly displayed as 8805 instead of 8905. * ` ` Previously, if the ring broke on a Token-Ring network when the Requester was trying to send, the Requester would hang the workstation. Now the send process will simply time out and the Requester will display an error message. * ` ` Occasionally, OS/2's File Manager does not properly copy a network directory and its accompanying subdirectories. Previously, this error caused the system to hang. Now, because of changes to the Requester, you simply receive an error message. * ` ` Previously, if you used the OS/2 E.EXE editor to create a new file, the file would not save properly to your file server. An error of 899C was returned. This problem no longer occurs. * ` ` Child processes now close correctly when using Named Pipes. * ` ` The installation program, INSTALL.EXE, will now install on Extended Edition OS/2 when IBM NetBIOS is running. This was only a problem on the Extended Edition of OS/2. * ` ` Previously, if a Named Pipes server was a slower system than a Named Pipes client connected to it, performance was very poor. Performance has been improved in this situation. * ` ` A new configuration option, called "DisplayHardErrors," has been added to the NET.CFG file. This option allows programs to keep running without interaction when a hard error is displayed. This is specifically for sites with unattended workstations. The option has the following syntax: h) 0*0*0* Ԍ displayharderrors no To display error messages, simply leave this line out of your NET.CFG file. * ` ` In certain circumstances, a NetWare server specified with lower-case letters in a UNC path would not be recognized. This problem has been solved. * ` ` The CMGRLAN.SYS driver replaces the TOKENEE.SYS driver. Select Communication Manager on the Modify CONFIG.SYS screen during Requester installation. CMGRLAN.SYS works with IBM Ethernet, IBM PC, and Token-Ring networks using Extended Edition Communications Manager. If you are running OS/2 Extended Edition, you should use this new driver. FYI: Maximum Print Servers Under 386 NetWare FYI (Note: 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.) TITLE: Maximum Print Servers Under 386 NetWare DOCUMENT ID#: FYI.P.4805 DATE: 02DEC91 PRODUCT: NetWare PRODUCT VERSION: v3.x SUPERSEDES: NA SYMPTOM: NA ISSUE/PROBLEM How many printservers can be configured per file server using PSERVER.NLM? SOLUTION You can run one PSERVER.NLM and as many PSERVER.EXE's as you have user connection slots. PSERVER.NLM does not use connection slots from the user pool, it uses one from the pool of 100 reserved specifically for NLMs. If you have a 10 user version of 3.11 you could have 5 PSERVER.EXE's, one PSERVER.NLM and 5 connection slots left over for users. h) 0*0*0* ԌFYI: "Net 1060 Error, IPX Is Not Loaded" NetWare v3.11 FYI (Note: 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.) TITLE: "Net 1060 Error, IPX Is Not Loaded" NetWare v3.11 DOCUMENT ID#: FYI.P.4804 DATE: 02DEC91 PRODUCT: NetWare PRODUCT VERSION: v3.11 SUPERSEDES: NA SYMPTOM: Getting error "Net 1060 error, IPX is not loaded". ISSUE/PROBLEM Received the above error when trying to use PCONSOLE or Cheyenne's ArcServe tape backup software under OS/2. SOLUTION They needed to go into CONFIG.SYS and make sure that SPX.SYS and SPDAEMON.EXE were not remarked out. After taking the remarks off, everything worked fine. FYI: Stack Fault Processor Exception. NetWare v3.11 FYI (Note: 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.) TITLE: Stack Fault Processor Exception. NetWare v3.11 DOCUMENT ID#: FYI.P.4801 DATE: 02DEC91 PRODUCT: NetWare PRODUCT VERSION: v3.11 SUPERSEDES: NA SYMPTOM: Error displayed on the server "Abend: stack fault processor exception". ISSUE/PROBLEM h) 0*0*0* Ԍ Configuration: DTK 386/25, 8MB RAM ` ` WD ESDI ctlr, 90MB disk, ISADISK WD Ethernet NIC LANPort (print server) The customer only received the above error when they were printing large print jobs. Otherwise the network was fine and printing jobs a couple of pages in size was fine also. SOLUTION Loaded the ISADISK with the /b switch ie. LOAD ISADISK /b. This completely solved the problem. FYI: Server Crawls Copying 350Meg Of Files, v3.11 FYI (Note: 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.) TITLE: Server Crawls Copying 350Meg Of Files, v3.11 DOCUMENT ID#: FYI.P.4840 DATE: 04DEC91 PRODUCT: NetWare PRODUCT VERSION: v3.11 SUPERSEDES: NA SYMPTOM: The server slows down copying 350mg worth of files across the network. ISSUE/PROBLEM Experiencing a major slow down in copying files after upgrading from NetWare v3.10 to v3.11. Solution Try going back to the 3.10 isadisk driver. FYI: Menu utilities Not Executing Properly. NetWare v2.2 FYI (Note: 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.) h) 0*0*0* Ԍ TITLE: Menu utilities Not Executing Properly. NetWare v2.2 DOCUMENT ID#: FYI.P.4894 DATE: 06DEC91 PRODUCT: NetWare PRODUCT VERSION: v2.2 SUPERSEDES: NA SYMPTOM: NA ISSUE/PROBLEM A customer had some 8086's on the lan, so had to get the new menu files so they could run the menu. Put all the new menu files out onto the PUBLIC directory and everyone used those files (not just the 8086's). Then, when they started accessing any utilities that were menu driven, they would look like they were coming up, then the screen would go black and the machine was hung. Sometimes the menu utilities would come up to the background screen and then hang. SOLUTION The menu driven utilities use the Novell MENU files (IBM$run.ovl, Sys$err.dat, Sys$msg.dat, etc.) to execute and bring up the utility. Apparently, the older menu files will not run the newer menu driven utilities. They had to create a new directory that they called utilities, copied the v2.2 menu files into this directory, along with all the menu driven utility files, and deleted SYSCON, FCONSOLE, etc from the PUBLIC directory. Now every time they have to access these utilities they are using the new menu files in that directory. FYI: DIR*.* Fails To Return Files Without Extensions FYI: Utilities Compatibility With NetWare For VMS FYI (Note: 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.) TITLE: Utilities Compatibility With NetWare For VMS DOCUMENT ID#: FYI.P.4891 DATE: 06DEC91 PRODUCT: NetWare for VMS PRODUCT VERSION: v2.1 rel. 3.01 SUPERSEDES: NA SYMPTOM: NA h) 0*0*0* ԌISSUE/PROBLEM The only two utilities from more recent versions of NetWare that are supported with this version of NetWare for VMS are SLIST.EXE and LOGIN.EXE. FYI: Out Of Memory Errors Trying To Print On OS/2 FYI (Note: 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.) TITLE: Out Of Memory Errors Trying To Print On OS/2 DOCUMENT ID#: FYI.P.4890 DATE: 06DEC91 PRODUCT: NetWare Requester for OS/2 PRODUCT VERSION: v1.3 SUPERSEDES: NA SYMPTOM: Getting "Out of memory" errors. ISSUE/PROBLEM Customer had an installation of 6 OS/2 machines all of them running 2 3270 sessions, Lotus and Word. The machines are all PS/2s with 8Mb of memory. They wanted to add a NetWare server for print sharing and some file sharing. After loading the NetWare Requester when they went into Lotus or word and tried to print they would get an "Out of Memory" error. They could print out a directory listing ie. Dir > lpt1. SOLUTION We suggested that they had disabled the Swap file. As it turned out they did have a swap area defined in the CONFIG.SYS but it was set to drive c: which only had about 600k free. After they set the swap area to their drive d: which had plenty of space, they were able to print fine. FYI: NetWare For VMS Binderies FYI (Note: 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 h) 0*0*0* document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: NetWare For VMS Binderies DOCUMENT ID#: FYI.P.4881 DATE: 06DEC91 PRODUCT: NetWare for VMS PRODUCT VERSION: v2.1 rel. 3.01 SUPERSEDES: NA SYMPTOM: NA ISSUE/PROBLEM If for some reason the NetWare for VMS binderies get corrupted, someone used a non-NetWare for VMS SYSCON etc. (NetWare for VMS binderies have a different layout then Native NetWare binderies so using other utilities to make changes will corrupt them). Currently there is not a bindfix utility provided and no other bindfix will work. SOLUTION There are two ways to deal with bindery problems. 1) Reinstall NetWare for VMS, during the INSTALL it will detect the old binderies and ask if you want to save them or create new ones. After the install they will have to add the users again and their trustee rights. The data files will remain intact during the reinstall. 2) If they have a known time when the binderies were ok and if they have a VMS backup from that time they can restore the bindery files. In NetWare for VMS there are four bindery files: OBJECTS.BND PROPERTIES.BND PROP_VALUES.BND and TRUSTEE.DB. The Trustee.db is a database file for trustee rights. Since all files are stored in RMS structure we can't put the trustee rights in the dir. tree so it is done as a separate file. FYI: NetWare For VMS And Map Root Support FYI (Note: 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.) TITLE: NetWare For VMS And Map Root Support DOCUMENT ID#: FYI.P.4878 DATE: 06DEC91 PRODUCT: NetWare for VMS h) 0*0*0* ԌPRODUCT VERSION: v2.1 rel. 3.01 SUPERSEDES: NA SYMPTOM: Map root command not working correctly in NetWare for VMS. ISSUE/PROBLEM When you try to map root a drive with NetWare for VMS you are going to run into the following problems: 1. ` ` The version of shell that supports map root (rev 3.01) is not the version that ships with NetWare for VMS. The shell that ships with NetWare for VMS is 2.15 and the only shell that is fully supported. 2. ` ` If you use a version of the shell that supports map root, the map root is not very reliable. Example: If you set a map root for PRV-NSD-VAX\SYS:PUBLIC, and there is a subdirectory off of public called DOS, then when you cd into DOS, your "map rooted drive" will appear as PUBLIC\DOS, instead of \DOS. Thus, your map root is displaying the full path. 3. ` ` Like native NetWare - if you do a dir sys:, your map root will be gone, this is the same for NetWare for VMS. SOLUTION NetWare for VMS does not support map root at this time. FYI: "Only 0 Redirection Blocks Available On Drive" FYI (Note: 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.) TITLE: "Only 0 Redirection Blocks Available On Drive" DOCUMENT ID#: FYI.P.4876 DATE: 06DEC91 PRODUCT: NetWare PRODUCT VERSION: v2.2 SUPERSEDES: NA SYMPTOM: Getting error "Only 0 redirection blocks available on drive". ISSUE/PROBLEM h) 0*0*0* Ԍ The customer was using a model 60 and installing a new mfm 40Mb drive because the old one had died. He received the error above. This error occurred after the install program copied NetWare v2.2 os to drive and before the volume mount. SOLUTION Had him go into INSTALL -f and replace track zero information. This fixed the problem. FYI: Group And User Trustee Assignments FYI (Note: 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.) TITLE: Group And User Trustee Assignments DOCUMENT ID#: FYI.P.4867 DATE: 05DEC91 PRODUCT: NetWare PRODUCT VERSION: v3.x SUPERSEDES: NA SYMPTOM: NA ISSUE/PROBLEM In the v3.11 concepts manual section describing rights, a misconception is presented. The section describes how to calculate the effective rights in a directory. The explanation is a good one unless you start to mix group trustee assignments and user trustee assignments. The manual explains that the effective rights flow down until they are masked off or modified with another trustee assignment. It states that any trustee assignment will overwrite the rights flowing down. This is not the case. SOLUTION If you are dealing only with user trustee assignments, then the effective rights do flow down and can be changed (increased or decreased) with a new user trustee assignment. However, if you grant a group trustee assignment, it will be "or"ed with the user rights flowing down from the parent directory. In other words, a group trustee assignment will not take away from rights flowing down from a parent directory if they were granted to a user. A good rule to follow is if a trustee assignment is made in the same box in syscon, then it will follow the rules in the book. h) 0*0*0* Ԍ FYI: Unable To Copy DLL Files To NetWare Directory FYI (Note: 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.) TITLE: Unable To Copy DLL Files To NetWare Directory DOCUMENT ID#: FYI.P.4866 DATE: 05DEC91 PRODUCT: NetWare Requester for OS/2 PRODUCT VERSION: v1.3 SUPERSEDES: NA SYMPTOM: NA ISSUE/PROBLEM Customer was installing NSD003 into his OS/2 Client. During the installation he was notified that two DLL files could not be copied. The current version of the Requester(V1.3) and NSD002 were running on the Client at the time. SOLUTION Had the customer remove the C:\NetWare references in the LIBPATH and SET DPATH statements in the CONFIG.SYS file, reboot the Client and then reinstall NSD003. The customers Client was already running the REQUESTER, the names of the files stored in the C:\NetWare directory and the files in the NSD003 for the OS/2 REQUESTER have the same names. NDS003 installation just copies over the existing files with the new information leaving the filename unchanged. The installation could not copy the two DLL files because the OLD DLL files in the C:\NetWare" directory were currently in use and could not be overwritten. By removing the C:\NetWare references and then rebooting, no requester files would be in use, and the Installation of NSD003 will install all files and put the references back where they should be. FYI: OS/2 File Manager Crashes With "Trap 000D" FYI (Note: The origin of this information may be internal or external h) 0*0*0* 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.) TITLE: OS/2 File Manager Crashes With "Trap 000D" DOCUMENT ID#: FYI.P.4865 DATE: 05DEC91 PRODUCT: NetWare Requester for OS/2 PRODUCT VERSION: v1.3 SUPERSEDES: NA SYMPTOM: Getting a "Trap 000D" error. ISSUE/PROBLEM SPD#: 10285 If a file or folder is dragged from the local drive to a network drive, or from one network drive to another, and the file doesn't already exist on the target drive the file manager will get a TRAP 000D. The application dies but the OS continues to run ok. SOLUTION There is no solution at this time. This is a problem in the OS/2 kernel. IBM is putting out a new CSD (corrective service diskette) real soon now that should fix the problem. FYI: Logical Connections Supported In NetWare v2.2, v3.11 FYI (Note: 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.) TITLE: Logical Connections Supported In NetWare v2.2, v3.11 DOCUMENT ID#: FYI.P.4835 DATE: 02DEC91 PRODUCT: NetWare PRODUCT VERSION: v2.2, v3.11 SUPERSEDES: NA SYMPTOM: NA ISSUE/PROBLEM How many logical connections are supported in NetWare v2.2 and h) 0*0*0* v3.11? SOLUTION It depends on which "user version" you have: v2.2 Connections 5 user 32 10 user 32 50 user 64 100 user 116 v3.11 Connections 10 user 110 20 user 120 100 user 200 250 user 350 Connections are taken by logged-in users, NLMs, VAPs, etc. A work station that is connected without being logged in will also take a connection. After someone logs out they still have a connection to one server, and have access to the login directory. Remember that in 2.x NetWare when you run out of your user connections you will get a message similar to the following depending on the version of LOGIN.EXE that is used: Given server has no free connection slots at the current time. OR The file server has reached its maximum number of connections. Whereas the 3.x server just stops SAPping (advertising itself) and you will get a message such as "Unknown file server." Unlike 3.x where this "inactive" connection shows up in the list of connections as user NOT-LOGGED-IN, NetWare 2.x does not have such a designation; the connection just doesn't appear on the list. FYI: "Bad Block Table Not Accessed" FYI (Note: 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.) h) 0*0*0* Ԍ TITLE: "Bad Block Table Not Accessed" DOCUMENT ID#: FYI.P.9602 DATE: 03JUN91 PRODUCT: NetWare PRODUCT VERSION: v2.2 SUPERSEDES: NA SYMPTOM: NA ISSUE/PROBLEM 1. ` ` What does it mean when you get the error "BAD BLOCK TABLE NOT ACCESSED" in the process of booting the file server? 2. ` ` You have an ESDI drive and do a low-level format on it, keying in the defects (bad blocks) manually. Everything goes just fine. You then run a Compsurf saying 0 passes, 0 random I/O's and NO to format. When you go to look at the bad block information, the table is empty. Why? You just keyed in all of the defects for the low-level format. SOLUTION 1. ` ` The explanation I received way back in the 2.15 rev C days is the following. This message comes from the LOADER.DAT. All it means is that while the NET$OS.EXE is booting up the bad block table will not be accessed. If you get to the colon prompt you are fine. If you don't it means that while booting you encountered a bad block that couldn't be redirected and you will have to boot from floppy until you can reload the OS again. ` ` Another reason this comes up is because the NET$OS.EXE is located on a disk with more than 1024 cylinders. Since we have trouble seeing past 1024 cylinders, it's not possible to access a redirected block that is past that point during bootup. 2. ` ` The analyze disk option of COMPSURF and ZTEST will write over the Bad Block sectors (18-21) of Track Zero. That is why you saw the table empty. Instead of running COMPSURF or ZTEST, ESDIDISK on NetWire (ESDIDR.ZIP) should be used after the ESDI low-level format. ESDIDISK will place the COMPSURF stamp on the drive, as well as ensure the bad blocks are preserved on Track Zero. ` ` On most hard disks (I assume ESDI also) when a low level format is performed, the bad block (sector) itself is locked or marked bad. Since a low-level format is independent of the operating system, each OS then has to deal with the blocks that are marked bad in it's own way. When you do a high-level format with DOS it tries 5 times to read each sector then marks it as bad in it's internal tables. NetWare uses HotFix to redirect blocks that have been marked bad by the low-level format routine. ` ` COMPSURF's low level format does the same thing and in h) 0*0*0* addition builds a table on track 0 of those bad blocks. This is a COMPSURF specific bad block table and, except for a few 3rd party utilities such as Ontrack Diskmanager-N, is not uses by anybody else. When a disk is initialized under NetWare 2.x, the bad block table is read and all the bad blocks are redirected with HotFix. Otherwise they are redirected later when you try to write to them. This is the only time the bad block table is used (when a drive is initialized). ` ` NetWare 3.x is similar in that if you select "Surface Test (optional)" under "Disk Options" from the INSTALL.NLM the blocks that were marked bad with the low-level format are found and redirected to the HotFix redirection area. FYI: Problems With User Login Script. NetWare v2.2 FYI (Note: 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.) TITLE: Problems With User Login Script. NetWare v2.2 DOCUMENT ID#: FYI.P.9601 DATE: 03JUN91 PRODUCT: NetWare PRODUCT VERSION: v2.2 SUPERSEDES: NA SYMPTOM: Users login scripts would not execute. ISSUE/PROBLEM After upgrading from NetWare v2.15a to v2.2 the users login script would not execute unless the user was a supervisor equivalent. The system login script executed without problems. SOLUTION For whatever reason, the upgrade gave the user only create rights and thus they could not read from the login file because he did not have enough rights. Went in and gave the user proper rights [ RWCEMF ] and now all is working properly. FYI: MAP ROOT And DOS DIR Command FYI h) 0*0*0* Ԍ(Note: 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.) TITLE: MAP ROOT And DOS DIR Command DOCUMENT ID#: FYI.P.9600 DATE: 03JUN91 PRODUCT: NetWare PRODUCT VERSION: v2.2, v3.11 SUPERSEDES: NA SYMPTOM: The map root gets deleted. ISSUE/PROBLEM If a map root has been created and a user issues a DOS "Dir" command to a directory lower than the map root directory, the map root is deleted. For example: command Map Root f:=Server\sys:users\ralph returns Drive F: = SERVER\SYS:USERS\RALPH \ command Dir f:sys:users returns Volume in drive F is SYS Directory of F:\USERS RALPH