--------------------------------------------------------------------------- NVCL32D2.DOC -- 19980109 -- Email thread on NetWare's Client 32 for DOS&Win --------------------------------------------------------------------------- Feel free to add or edit this document and then email it back to faq@jelyon.com Date: Tue, 27 Aug 1996 08:17:00 -0400 From: PowrTekSys@aol.com (Kevin C. McIntosh) To: NETW4-L@bgu.edu Subject: DOSWIN32 ACU Process After 3 days of discussin' and cussin', I've got everything in the Novell Client32 for DOS/WINDOWS Automatic Client Update configured and working, except for one item. The MLID (3C5X9.LAN) requires ISA to be added to the load line in the STARTNET.BAT. So far, I have to do this manually. Any ideas on how to add this parameter automatically? By the way, originally, the INSTALL file kept aborting. Novell has a patch named DW32I1.exe that contains the following updates: CLIENT32.NLM, NWIP.NLM, and INSTALL.CFG. The file is dated 8/22/96 and, as of this writing, was only available on the BBS @ 801-373-6999. Any help with how to automatically add the ISA, EISA, MCA, or PCI parameter to the LOAD line for the MLID would be appreciated. ------------------------------ Date: Wed, 11 Sep 1996 10:09:56 +0200 From: "Niels Chr Nielsen, 5551" Subject: Re: Setup defaults in Netware Client32 for Windows95 >Is it possible to change the defaults for Client32 before installation >so all clients being installed have the same settings? > >What I want is to disable Opportunistic Locking, specify a preferred >tree, set default capture settings etc. Take a look at Netware Connection (http://www.nwconnection.com/) articles on integrating Netware and W95. (Issues Nov/Dec95, Jan/Feb96 and Mar/Apr96). ------------------------------ Date: Thu, 12 Sep 1996 13:19:38 -0400 From: Clay Gibney Subject: Task Switcher -Reply >Could someone please tell me what the error message > >"The 32bit netware client does not support task switchers" mean > >I have the 32bit client installed on a win3.1 machine. I get >the error message in 2 instances. >1. Before running wp6.0 for dos, but runs windows ok >2. Before starting windows (on a different machine) You can run WP for DOS this way: wp /da /d-c:\temp This disables the task switcher that is built into WordPerfect. Other programs that are not compatible with the new DOS/Win 32 bit client are: WP Shell, WP 5.1+, DOSSHELL and SoftSolutions for DOS (if you use the driver.exe). With the WordPerfect programs above, you can use the "/da" option, though, to get around the problem. ------------------------------ Date: Thu, 12 Sep 1996 12:52:25 -0700 From: Mike Wallendahl Subject: Re: NAM Application snapin error -Reply >Where does one find out the installation and useage documentation for NAM? Try the Netware Connection homepage. IT just had an EXCELLENT article on setting up NAL/NAM: http://www.nwconnection.com/ Use the version of NAL included with the 32-bit DOS/Win3.x client--it's version 1.1, whereas version 1.0 is included with Win95 client. ------------------------------ Date: Thu, 12 Sep 1996 21:06:45 -0400 From: DonPoko@aol.com To: netw4-l@bgu.edu Subject: Re: Problem w/DOS Printing under Win95 To print a dos program using a 4.1 NDS NOVELL server, NOVELL Client 32, and Windows 95, You will need a C3295D.exe patch for the Client 32 from Novell, a windows 95 service pack 1 from Microsoft. Install both of these on your workstation. Now the fun starts. Install a network printer (add a printer) to Windows 95. If you can take out all other printers. In the printer properties menu choose DEFAULT CAPTURE and uncheck the prtsc box. Left click on the network neighborhood the right click on it to bring up the menu. Choose the Novell Client 32 then choose properties. In the properties menu choose MISC, check the AUTO ENDCAP and change the timout to 15. If you want notify the check the NOTIFY box. ------------------------------ Date: Fri, 13 Sep 1996 14:22:57 +0100 From: Richard Letts Subject: Re: Winsock in Client32 DOS/WIN >We have just purchased a new Ethernet Switch and every machine on the >network with TCP/IP installed on it can ping this switch apart from >the one machine that is trialing Client 32 DOS/WIN. I want to move to >Client 32 but we need to be abel to run the SNMP software to see this >switch and the other network devices which it sees OK. The documentation >says Winsock compatible machine. Any ideas?? Application [TCP/UDP] programs have no problem, only things trying to access RAW [ie RAW IP] packets have problems. PING sends ICMP packets and needs RAW packets... SNMP (UDP/IP) should work okay, of course if it's a dumb application that pings before sending an SNMP packet. This is no good for you. [it should not, as PINGS are likely to be blocked for administrative reasons in any case.] ------------------------------ Date: Mon, 16 Sep 1996 20:28:35 +0100 From: Steven Weaver Subject: One problem - two failed solutions... I'm preparing to set up a large number of Win95 workstations, connecting to a Netware 4.1 LAN via Client32. To save time, I would like to automate the install so that it requires no user intervention. I've tried two methods but can't get either to work. Method 1 - batch install. I am installing Win95 from a volume on the Netware server. After running the Win95 Netsetup utility, and following Novell's instructions on combining the installation of Client32 with win95 using the .inf files everything seemed fine. The install ran with no user intervention, and the PC re-booted. After the re-boot, Client32 was shown to be installed in the control panel, but Windows wanted to copy more Netware related files from the server in order for it to work. Unfortunately, Client32 needed the missing files to talk to the server - a vicious circle! The only thing that I didn't specify in the .inf file was the network adapter - 3Com 905XL. Method 2 - file copy I then tried to do what I used to do with Windows 3.11 - first copy an installed machine's contents to the server, then boot from a floppy, format the HDD, log in to the server and copy the entire contents of the hard disk onto the new PC. After a bit of trial and error with Win95's various hidden files, I did the following. 1. Copied the machine's contents to the server using xcopy (with switches to copy hidden files, and preserve file attributes. The server volume has OS/2 name space loaded) 2. Booted from Win95 boot disk, formatted HDD as system disk, logged into server using VLM's. 3. Using Laplink(!), copied across from server all files - including hidden and system files. (I used Laplink because xcopy and ncopy wouldn't copy hidden and system files) 4. Re-booted. After this Win95 started OK, but Client32 wouldn't talk to the server and all my long filenames had gone. I even tried the above together with a backup and restore of the registry using regedit. So here are the questions. Has anyone managed to get Client32 to install with Win95 using a batch install? If so, where am I going wrong? CAn I add a driver for the 3com card to the Client32 install script? And if not, how can I duplicate a Win95 workstation like I used to do with Windows 3.11? --------- Date: Mon, 16 Sep 1996 13:54:45 -0600 From: Joe Doupnik Subject: Re: One problem - two failed solutions... >Sorry if this question is more suited to a Microsoft list, but here goes >anyway... > >I'm preparing to set up a large number of Win95 workstations, connecting >to a Netware 4.1 LAN via Client32. To save time, I would like to >automate the install so that it requires no user intervention. I've >tried two methods but can't get either to work. >Steven Weaver Let's see here. First, you are installing Win95 to client's hard drives, not to the server proper, right? That's because you want to use Novell's Client32 which does not run until after the GUI is up. Once done you want to image copy that hard disk to N other clients. Refer to MS Resource Kit and Win95 CD-ROM on converting long filenames to rational stuff prior and post backups. Here's my "don't raise the bridge..." solution. Install Win95 on the server. Don't use client32, don't use long filenames. Whether or not you end up with client hard disks is up to you. This solution is discussed in files w95inst7.zip (PowerPoint v7 show) and its Postscript printer rendtion w95instps.zip, in directory misc on netlab2.usu.edu. All the client needs locally is the pair of registry files and command.com; everything else can be elsewhere. Joe D. ------------------------------ Date: Wed, 25 Sep 1996 09:37:28 -0800 From: Mark Schoonover Subject: Re: Client32 login name - can't clear >I am using the client32 with a Netware 4.1 server. My problem is that the >client32 remembers the username of the last person to login. I am looking >for a way to make the username field default to a blank rather than to the >last valid username. A faq on Novel''s web site describes how to reset the >value manually using the win95 registry but I need this to be automatic. This information is stored in two place in the registry. One under HKEY_CURRENT_USER\Network\Persistant\0 and under HKEY_CURRENT_USER\Network\Recent keys. The default names for each server are stored under the latter. I haven't tried this yet -- but I would think it would be possible to just rename the UserName value under each server to something else. There wouldn't be a place to store the user name within the registry. It may be possible that client32 will create new valuenames. Try this on a practice machine and let me know. I'll include this information in the next release of my client32 info file. ------------------------------ Date: Sun, 29 Sep 1996 15:57:06 -0600 From: Joe Doupnik Subject: Re: 32Bit Packet driver/App. Speed >Why is there no 32bit packet driver (ODI), Does this have I have to stop here and pick nits with the choice of technical words. Packet Drivers and ODI are quite different things, please, so let's not add confusion by mixing the terms. >something to do with the nic which is only 16bit. I use the 32bit >client and the only way to make some apps work is by using a 16 >bit nic driver along with a 16bit odi driver ie. Kermit which does >not work with winsock. Therefore my question. At this point we forget 16 vs 32 advertizing jargon and come to grips with the proper aspect, which is real mode versus protected mode (as in say Windows). It has nothing to do with the bus width of your lan adapter. The lan drivers written for protected mode opertion are typically written in C, so typically have that as the first letter of their name from Novell, and also happen to be platform independent code (at the source level). That means they are using a 32-bit flat address space, protected mode in Intel-speak. A few such drivers are written in assembler and lack the C prefix to their name. But they all have .LAN as a file extension. Real mode drivers are .COM things and work only below 1MB with real mode addressing constraints. Client32 has a real-to-protected mode bridge such that real mode drivers can be used, as well as real mode ODI client material. It's named pdoseth.com or pdostok.com or pdosfddi.com, from which the sharp eyes in the crowd will deduce "P" for Protected mode, "DOS" for Real Mode, and then eth/tok/fddi for the media kind. Technically speaking, these look like fake real mode MLIDs (board drivers). LSL.COM is a real mode ODI application, and you can tell right off by the extension. >Is there a performance degradation is use the 32bit client with >a 16bit nic driver. If no. How come ??? There should be ?? >don't you think. Please help enlighten. Run what works best on your particular machines, and it is best to not ask "why?" quite so often (the answers may be lengthy indeed). ------------------------------ Date: Wed, 23 Oct 1996 21:19:09 +1000 From: Greg J Priestley Subject: Novell's 32 bit client An Australia software vendor (who at this point in time will remain anonymous) has made the following comment about why their software won't support the 32 bit Novell clients:- "Unfortunately we can't fix Novell's problems for them. The problem is that DOS int 21, 5Fh function does not work correctly in the 32 bit Novell client for Win 95. Novell have been advised and have indicated that it will be fixed in a "future" client update & we have an SPR number. But we note that it has not been fixed in "Green River". Curiously early VLM's had the same problem..." ------------------------------ Date: Fri, 25 Oct 1996 14:32:29 -0400 From: Jason Lester Subject: Re: Client32 Win31 Login >Has anybody had similar problems: > >(Some) programs that run fine with a dos login fail in a variety of ways >when used with a windows based login. > >We need to run programs from the login script. Sometimes the script log box >shows following error - sometimes it doesn't. User does not matter. Admin >or guest get the error if they are going to get it. > >the login script line is >#c:\command /c g:\login\update g:\login\starnav.scr > >the box shows: >Error returned from '#c:\command /c g:\login\update g:\login\starnav.scr' >command: 17 I had the same problem, it seems that you have to specify the extension also. On my system, #UPDATE wouldn't work, but #UPDATE.EXE would. I'm not sure if it's program related or a bug/feature of Client32. ------------------------------ Date: Sat, 26 Oct 1996 09:04:00 -0500 From: Peter Turner Subject: Client32 on Win 3.1 I'm trying to do it and so far there have been a few anomilies. If you do anything (like run dos program)in your login script, make sure to test with client32. Particularily if you are using the in-windows login. The startup login changes back to F:\login from the vlm F:\ not serious but adds pathing problems in mixed environment. I have used subdirectories off SYS:LOGIN to store update files that get sent to PCs. Now sometimes (more often than not) the contents of LOGIN subdirectories are not available before login. same machine just cold boot it again and they are available? (bug - feature?). My point is try to break it before you turn it loose. (I have it on 10 PCs in a 120 user network.) I think you will find it does break. I have some users on a foxpro program that apparently, with vlm's was OK and would send "printing done" message to capture. Now with client32, we need to time out the capture. Granted it is a dos based program run in a windows box but it used to work, now it's different. As you use it, you will find other quirks. ------------------------------ Date: Wed, 30 Oct 1996 09:27:45 +0000 From: Richard Klemme Subject: Client 32 for DW 2.1 vs 2.11 Ive just been to ftp.novell.com and saw that there are 2 versions of the 32-bit Client for Dos/Win namely cl32dw21 and cl32dw211. I went to the new one and went to the webpage and got the TID (2915626) and it mentions that it is the same as the one in INW / NW 4.11. We are planning to deploy this throughout our organisation, and were wondering if there are any issues using this with our existing NW4.10 / 3.12 / 3.11 (all 3.x to be upgraded to 4.10 first then all later to 4.11). What are the significant differences (bug fixes??) between 2.1 and 2.11?? ------------------------------ Date: Wed, 30 Oct 1996 10:17:54 EST From: David Hodge Subject: Client32 problem Since moving to Client32 for Dos/Win I have been seeing the following problem: When students are using netscape and are at a site that requires them to send information (usually subscription info., or a site like hot mail) the machines running client32 do not seem to be able to send the info. The results is students get the waiting for reply message from the host site, and never get loged in. From our one machine running the vlm's (1.20) they get signed in immediatly. ------------------------------ Date: Thu, 31 Oct 1996 16:02:16 -0000 From: Robin Bowes To: "'netw4-l@bgu.edu'" Subject: RE: [Client32 DOS/WIN] TCP/IP setup >Has anyone any experience of setting up the TCP/IP stack that is built >into Client32 for DOS/Win? > >I seem to be having problems using DHCP to dynamically allocate >addresses. > >When the machine first boots, before going into windows, TCP/IP seems >to work OK. I can drop to a DOS prompt and use "ping www" and our DNS >resolves the alias and pings our web server. > >However after running windows, this doesn't work. It seems that >something gets "broken" by running windows (this is WfWG 3.11 with no >Windows networking components installed at all). > >I don't have this problem if I use static IP addressing, ie specify >everything explicitly in NET.CFG. This is a known problem and there is a fix. See TID 2915346. ------------------------------ Date: Thu, 7 Nov 1996 19:44:28 -0600 From: Joe Doupnik Subject: Re: Client32 and terminal emulation >I'm cooking along, getting client32 installed and loving it. Come to the issue >of running terminal emulation software, and ?!?!?!?? > >My question is, does anyone have a good suggestion for running terminal >emulation to an hp3000 in a dos/win3.11 envoronment? > >We are currently running WRQ NS-Connect V2.11 for Dos, and WRQ Reflection V4.21 >for Windows (under VLM). This apparently won't work with client32 (needs LSL >and ODI). I have a copy of LanWorkPlace 5.0 to evaluate, but so far this too >has turned into a major pain. > >Any suggestions? I'm just looking for a simple, reliable solution for a >handful of users to connect up to an HP3000, while running client32 for >DOS/Windows. ------------ I'm going to help, on one condition. That condition is you obtain and try MS-DOS Kermit, v3.14 is the latest release, v3.15 is in open beta, from kermit.columbia.edu. It also works over LWP/DOS via the Telapi shim in that package, in case you are curious and have that requirement. Ok? Good. Below is part of this morning's Kermit tech support traffic. Subj: Kermit & Novell Dos client32 >Dear Sir, > >I'm trying to set up a telnet session using MS-Kermit V3.13 in >combination with Novell's Dos Client32 with a TCPIP stack loaded. >I have a script that works correctly with the ODI-driver & ODIPKT, >but I'd prefer to use the Dos Client32 with its own TCPIP-stack. > >In the manual I found a reference to 'set port telapi', but this only >results in 'no connection status=-8108'. > >Could you help me or tell me where I can find more information on >this subject? -------------- Novell's Client32 did not exist when MS-DOS Kermit 3.13 was released. The current release is version 3.14, with version 3.15 in beta test. Using MSK with Client32 is easy. Below is an example startnet.bat file, and a section of net.cfg to support the real mode ODI components LSL and PDOSETH. Please note this is Novell's Client32 for DOS and Windows 3.1. Joe D. -------------- (sample startnet.bat, with QEMM/386 memory manager) SET NWLANGUAGE=ENGLISH C:\NOVELL\CLIENT32\NIOS.EXE LOAD C:\NOVELL\CLIENT32\LSLC32.NLM LOAD C:\NOVELL\CLIENT32\CMSM.NLM LOAD C:\NOVELL\CLIENT32\ETHERTSM.NLM LOAD C:\NOVELL\CLIENT32\CNE2000.LAN INT=5 PORT=300 FRAME=ETHERNET_802.2 LOAD C:\NOVELL\CLIENT32\CNE2000.LAN INT=5 PORT=300 FRAME=ETHERNET_802.3 LOAD C:\NOVELL\CLIENT32\CNE2000.LAN INT=5 PORT=300 FRAME=ETHERNET_II LOAD C:\NOVELL\CLIENT32\CNE2000.LAN INT=5 PORT=300 FRAME=ETHERNET_SNAP LOAD C:\NOVELL\CLIENT32\IPX.NLM LOAD C:\NOVELL\CLIENT32\CLIENT32.NLM C:\QEMM\LOADHI C:\NOVELL\CLIENT32\LSL C:\QEMM\LOADHI C:\NOVELL\CLIENT32\PDOSETH -------------- (goes into net.cfg) Link Driver PDOSETH Frame Ethernet_II Frame Ethernet_SNAP Frame Ethernet_802.3 frame ethernet_802.2 protocol ipx 8137 ethernet_ii protocol ip 0800 ethernet_II protocol arp 0806 ethernet_II protocol rarp 8035 ethernet_II ------------------------------ Date: Sat, 9 Nov 1996 12:23:49 +0200 From: Patrick Medhurst Subject: Re: Client32 and MSNDS >>I'm currently testing the MSDNS file from MS, and found that in order to >>get into the NWADMIN, there are certain files needed. The problem is >>the files are on the C32 disks, and using the normal EXPAND application >>does not extract the files. Does anyone know of a application that is >>designed to extract only the files needed? Use NWEXPAND. ------------------------------ Date: Thu, 14 Nov 1996 08:59:44 MET-1MST From: Joop van Buuren Subject: Re: Client32 DOS/WIN and TELNET >My telnet program no longer works with Client 32 for DOS/WIN. Can >someone point me to a free telnet client that does. It took us a while to figure out how to install the client to work with our NCSA-telnet (DOS) but it works now. Following our NET.CFG and STARTNET.BAT -----start of NET.CFG ----------- # # NET.CFG File for 3C503 # Default net.cfg for use in Medical Faculty EUR # Link Support Buffers 4 1550 Mempool 2048 Link Driver 3C503 PORT 280 INT 3 MEM D8000 FRAME Ethernet_802.3 FRAME Ethernet_II Protocol IPX 8137 Ethernet_802.3 Protocol IP 0800 Ethernet_II Protocol ARP 0806 Ethernet_II NetWare DOS Requester FIRST NETWORK DRIVE =3D F SHORT MACHINE TYPE =3D IBM NETWARE PROTOCOL=3DBIND,NDS USE DEFAULTS=3DON NAME CONTEXT=3D".OU=3DFGG.O=3DEUR" PREFERRED SERVER=3DMT1-FGG-EUR-NL FIRST NETWORK DRIVE=3DF FORCE FIRST NETWORK DRIVE=3DON READ ONLY COMPATIBILITY=3DON AUTO RECONNECT=3DON AVERAGE NAME LENGTH=3D20 BIND RECONNECT=3DON CHECKSUM=3D0 SHOW DOTS=3DON PROTOCOL TCPIP PATH TCP_CFG C:\NWCL32\TCP IF_CONFIGURATION BOOTP NIOS LINE DRAW CHARS =3D "++++a-" ---- end of NET.CFG file ------------ Note that order is important in net.cfg (Thanks to Joe D.) ------ start of STARTNET.BAT -------- set nwlanguage=3Denglish c:\nwcl32\nios.exe c:\nwcl32\lsl.com c:\nwcl32\n16odi.com c:\nwcl32\nesl.com c:\nwcl32\3c503.com load c:\nwcl32\lslc32.nlm load c:\nwcl32\pc32mlid.lan load c:\nwcl32\tcpip.nlm load c:\nwcl32\ipx.nlm load c:\nwcl32\client32.nlm lh c:\nwcl32\odipkt 1 97 lh c:\nwcl32\winpkt 0x61 ------ end of STARTNET.BAT -------- This works with our DOS NCSA Telnet version 2.3.07.04 If you have any questions you can eMail me directly. ------------------------------ Date: Fri, 15 Nov 1996 10:07:43 -0500 From: Brian Dunworth Subject: Re: Problems with Client 32 for DOS/Win >I just read that there is a bug in Novell's Client 32. It was written >as effecting MS Internet Explorer (IE) when using DNS. It times out >searching for sites. It may help the NetScape, etc. I don't know where you read this, but I'll bet it was a document originating at Microsoft. The 'bug' is NOT in Client32; rather it is in MS Internet Explorer (notice that the suggested "fix" for this 'bug' is editing the Registry entry for Internet Explorer, not Client32!). Client32 was written to the standards. MSIE (and, presumably, MS Client for Netware Networks) hacked a few of the network calls, modifying them so that MSIE would -appear- to work faster than other web browsers when resolving addresses through DNS... with absolutely _no_ regard for the established STANDARDS. The "fix" suggested works only for MS Internet Explorer, as only MS Internet Explorer is affected (as it is the only browser that was written with disregard for the standards already established). Netscape, Mosaic, Lynx, etc function perfectly well under Client32, with no Registry editing necessary. ------------------------------ Date: Fri, 15 Nov 1996 10:54:33 -0800 From: Mark Schoonover Subject: Re[2]: Client32 "Please wait" problem >>Anybody seen this error message from a N 4.1 workstation running >>Client32 for DOS/WIN >> >>"Client32: Please wait while System retries request to tcvb_lrc-1 >>to stop waiting, Press enter >> >>Netware will then return an error code and try to reconnect in the >>background" >> >>thats the message. The pc is now frozen. Upon reboot the message is >>"Please wait while netware client shuts down" >> >>The client never shuts down, and the pc must be rebooted again. >> >>Suggestions?? > >I get that too!... Don't know why it's happening. It generally happens >when I'm in a dos application. What's even weirder is that it doesn't >happen under windows 95. I get the same error message under 95. It seems to only affect me when I'm attached to a 3.12 server, as I haven't seen it related to my 4.1 server. FWIW. ------------------------------ Date: Mon, 18 Nov 1996 15:42:05 -0500 From: Clay Gibney Subject: DBASE_IV , CLIENT32 & printing -Reply >I changed from Netx to Client32 & now dBase_IV crashes when it is asked to >print (no error message either, it just hangs). The other modules work >properly.I can create reports & queries. All the other DOS & Win 3.11 >programs have no problem printing. The server is NW2.2. > >NETWARE DOS REQUESTER > FIRST NETWORK DRIVE = F > PREFERRED SERVER = cs > show dots =on > pb buffers=4 > file handles = 100 > large internet packets = on > signature level =1 > read only compatability = on > network printers=6 I don't use dBase, but one thing you may want to check is that Client32 now uses file handles from your config.sys rather than from the net.cfg file. So the line you have in your net.cfg is no longer used, and you would instead want to have 'files=100' in your config.sys file. ------------------------------ Date: Mon, 18 Nov 1996 22:36:20 +0100 From: Sven Ostlind Subject: Win95 Client32 (New) problem >I've applied the new Client32 to one of my Win95 machines for >test purposes. Since I've applied the patch, I'm having problems >running my login script's CAPTURE statement. We have the typical >CAPTURE statement as follows: < > CAPTURE L=1 Q=TOR_HP4PLUS_8208 NB NFF TI=15 < >However, when this command is issued, the followin error message >appears: < > Unable to locate queue TOR_HP4PLUS_8208NB. < >So, it appears that it is dropping the space between the queue >name and the NB for No Banner. Is anyone having this problem or >are aware of a fix? I came to think about a similiar problem that we had accessing a NetWare directory from ArcServe 6.0 and Intel Landesk Virus Protect 3.01. The problem came with Win95 Client32. The solution then was to shorten the name of the NW 4.1 server that initially exceeded 16 characters, and rebuild the NDS tree. Try to create a new queue with less characters and map to this. I don't know if it's applicable on Your specific problem but it's always worth a try. How long is your server name? The only information that we have to validate this issue is a fax from Cheyenne (below). One of the Engineers at Cheyenne told us that Novell are currently working on a solution but I haven't found anything about it in Novell's databases. ================ FAX FROM CHEYENNE ============================== PROBLEM Client has installed ARCserve on a volume that has 8 character volume name. Netware 3.11, running Windows 95 with Netware 32-bit client. When he run the manager he gets message: "You do not have rights to ARCserve home directory". The actual syntax of the error is: "You do not have access to the SERVERNAME/VOLUMENAME:PUBLIC dir. Could not detect arcserve home directory. Ask your ADMIN to use users profile to set..." RESOLUTION Install on a volume that has less than 7 characters in name or rename volume. This error will also occur if the server name is over 16 character. **NOTE** Same resolution applies to Novell's DOS/WINDOWS 32-bit client. ------------------------------ Date: Tue, 19 Nov 1996 08:11:07 -0500 From: Mike Soules Subject: Re: Client32 "Please wait" problem >>>Anybody seen this error message from a N 4.1 workstation running >>>Client32 for DOS/WIN >>> >>>"Client32: Please wait while System retries request to tcvb_lrc-1 >>>to stop waiting, Press enter. Netware will then return an error code >>>and try to reconnect in the background" Would have to disagree with your comment about the NIC or the network being the problem. I consistently get this problem whenever there is heavy PC interaction with our 4.1 servers. For example, if a user tries to copy a 13MB file from one drive to another, the error appears. Also, when there are a high number of file requests from a client, the error again appears. My Win95 clients all have the latest drivers (IBM (ISA/PCI) and 3Com (ISA)) drivers and the problem persists. Typical file requests or copies are fine, just when you tax the system the problems appear. ------------------------------ Date: Mon, 25 Nov 1996 12:42:14 BST From: Owen Stewart Subject: Re: Client32 and login scripts >Lucky you! You actually can run external programs from the login >script? I am not able to do so: login gives me the message: >LOGIN-4.20.10-740: This utility could not run external command: NMAIL >blabla > >It did work with an older client (Actually the 1.0 beta version I >think). After upgrading to 2.11 this message appeared. > >Maybe it's a FAQ, but I cannot find any solutions to this. Please >anyone help me! Something to try with dos commands not working like this is to put the command in a batch file and run than from the login script instead. That said, nmail.exe was one of the programs which did not need that treatment. It has also been suggested on this list (I have not tried it) that to avoid multiple dos windows one might put all such dos commands in a single batch file so as to get only a single dos window. ------------------------------ Date: Wed, 27 Nov 1996 22:56:38 -0500 From: Glenn Fund Subject: Novell App Launcher Bugs? Has anybody else out there dabbled with the the latest NAL 1.1. Yes, you do have to update to the the latest 32 bit clients, and NWADMIN to the latest releases. I am finding the following: On Windows 3.1 workstations: When you start up NAL, all icons appear correctly. However, addtions and deletions do not automatically show up (even when a 10 second poll rate is selected). Even an F5 to force a refresh does not work. In addition, any property changes to served applications do not show up on client workstations until NAL is closed and then refreshed. On Windows 95 and windows NT workstations: Startup is just fine. Icons do get added and go away as they are supposed to based on NWADMIN modifications. However, property changes to icons do not get transmitted down to the workstation here either. We are working on a project that utilizes Seagate's WinInstall to do the background application setup for the app launcher icons. Setup of the application and running an application is transparent to the user. No need to visit any clients anymore. Establish the WinInstll script. Go into NWADMIN and create an application object that serves the script up and then runs the application. Really cool. Lost of potential. Has anyone else made more progress with NAL? Does anyone have fixes for the above problem areas? ------------------------------ Date: Sat, 7 Dec 1996 22:13:57 -0500 From: Philip Reznek Subject: Re: Client 32 vs. MS Client for Netware >>No, it does not mean "more stable and has less bugs":- >>1. no one runs it - people want proper functionlity >>2. this is not a MS list for resolving problems with "core" M$ >operating systems > >Actually, I've found that the MS Client for Netware _IS_ more stable and >_DOES_ have fewer bugs than Client 32. My users (and superiors) will >pick stability and reliability over 'enhanced features' any day. Following the beta, I think there have been two releases of the Novell Netware Client for Windows 95 and an update to the first release. Which released Novell Netware Client do you have in mind? Is support for the complete set of NW calls we've come to like and love part of the 'enhanced features' you mention? Or error free execution of login scripts? The current release, 2.1, distributed with Netware 4.11, in informal testing seems to perform on par with the MS Client. I think we've found on a NIC with so-so performance anyway that not replacing NDIS drivers with ODI (an install-time option) gave better performance even with the addition software layer on both IPX/SPX and TCP/IP. It could be that the NIC vendor's NDIS 3 driver was more efficient than the ODI equivalent in the client kit. The general genuflection toward Redmond can make life difficult. I'm told I have to replace all of the Novell Netware Clients shortly because (and this is hearsay) Btrieve, Inc. told Vendor X that there are too many IPX/SPX bugs in Novell's Netware Client and that Vendor X should support only MS' Client in Vendor X's next release. And we, of course, use Vendor X's software and need the next release. Here's the other shoe dropping: We have other software that supports only the Novell Netware Client because the vendors say that the MS Client is not an exact emulation of the Novell Netware client. I don't think I'm really anti-MS. We have NT servers as application servers and they're fine in their place :-). I have a problem with the real problems MS' marketing causes in the trenches. ------------------------------ From: "Phillip S. Buckland, Jr." Date: Mon, 9 Dec 1996 11:06:02 CST6CDT Subject: Client 32 for DOS and Windows V2.11 problems and solutions I've come across a problem in the Client 32 for DOS and Windows NET.CFG documentation and behavior. To wit: the Long and Short Machine Type values are supposed to be enclosed in double-quotes according to the windows Client 32 help file (these appear in the NetWare DOS Requester section of the NET.CFG file): Long Machine Type = "IBM_PC" However, when I enclosed the machine type values in quotes, I had the following problems: 1) During login script processing, references to %MACHINE and %SMACHINE would fail. However, only ONE error message would appear even if both variables were referenced, and the offending variable would change depending upon the caching parameters on the client. 2) DOS utilities would fail (PCONSOLE, NETADMIN, and probably others) with "Error reading file IBM_DOS.OVL" messages. The applications would not run, of course. Also, of course, the windows utilities (NWADMIN, NWUSER) would work fine. The solution: don't enclose the machine type value in double-quotes. Long Machine Type = IBM_PC Short Machine Type = IBM No more problems! ------------------------------ Date: Wed, 11 Dec 1996 08:42:15 -0800 From: Floyd Maxwell To: netw4-l@BGU.EDU Subject: Re: Client32 memory >>It is my understanding that, at load time, Client32 finds out how much >>memory there's available, and then it takes about 25% of the available XMS >>for caching and other stuff. Not True, see below >>You can control the cache size in the NET.CFG under "NETWARE DOS REQUESTER" >>by adding the line >> >> MAX CACHE SIZE = XXXX >> >>where XXXX is the cache size *in kilobytes* > >What I've done is remove the caching all at once by adding the line > > FILE CACHE LEVEL = 0 > >which will not create any caching at all and only eat up to 2MB of >your extended. File Cache Level = 0 will turn off caching, however the "2MB" comment is Not True. Here are the facts, as per the help files that ship with C32: The 2 relevant Net.CFG parameters are: File Cache Level x default=3, (0-disabled, 1-read ahead & write behind, 2-short-lived caching, 3-long-lived caching), higher # is faster/riskier Max Cache Size = x x ranges from 0 to 9999999, def=0 (calculated dynamically) For machines with: FREE Machine RAM Cache size 0 - 6 MB free 384 KB 6 - 8 MB free 512 KB 8 - 12 MB free 1.5 MB 12 - 16 MB free 2 MB 16 - 20 MB free 3 MB 20 - 24 MB free 8 MB >24 MB free 50% of avail. memory So it is (1) the amount of *FREE* RAM that matters. A significant (cause its both common and a big RAM consumer) example is that of loading SmartDrv BEFORE NIOS [NIOS will use less RAM] versus loading SmartDrv AFTER NIOS [NIOS will see more RAM, and so will use more] (2) the cache consumption is not linear, except when one has more than 24 MB of RAM. As to NIOS RAM consumption when File Cache Level=0 (or Max Cache Size=0) the last time I looked it was about 800KB...this could vary...for example, running TCP/IP will probably increase consumption. I suggest experimenting... Floyd Maxwell mailto:floyd@direct.ca NOVELL (listserv@listserv.syr.edu) FAQ Maintainer FTP the FAQ at: ftp://netlab1.usu.edu/novell.faq/ WWW: http://netlab1.usu.edu/novell.faq/nov-faq.htm ------------------------------ Date: Mon, 16 Dec 1996 10:58:37 +0100 From: Peter Scherrer Subject: Solution:Problem with 32Bit DOS Client:NIOSWIN.NLM After a few weeks, I found the answer myself. If anybody gets into similar problems, try to increase the environment space of DOS. The question was >I installed Novells 32 Bit Dos/Windows client on a Compaq Deskpro >6000 PC. As long as I use only Dos and Dos applications, everything >seems to work all right: users can login without any problem, drive >mapping, file copying etc. works. But as soon as a user wants to start >Windows 3.1 (installed on the server) the following happens: >1. Windows starts and shows on the screen the 32 bit Novell logo. >2. The error message "Module NIOSWIN.NLM did not properly free one >resource" appears. >3. The machine hangs, the only thing that works is rebooting. >Anybody any idea? If I use the 16 bit VLMs instead of the 32 bit >drivers there are no problems. I tried different network cards >(NE2000, ATI 2450), no difference. The only thing that had to be done, was increasing DOS environment space to 2k, 1k was not enough. Now the CONFIG.SYS looks like SHELL=C:\COMMAND.COM /p/e:2048 and everything works perfectly. ------------------------------ Date: Thu, 19 Dec 1996 07:57:05 EST From: "Wayne St.Jacques" Subject: Netware and cc:Mail - Corruption of Mail Databases Lotus has documented problems with the Client32 corrupting specific databases. Upon installation of the Client32 a few months ago, our cc:Mail database began crashing daily, and NFT errors kept re-occuring throughout MLANDATA. According to Lotus, you need to immediately write the record(s) you are updating, and with the 'Opportunistic locking' value set to on, the client is auto-detecting whether to cache the information or not. (A severe problem when it comes to updating MLANDATA.) Novell has issued a patch as well, which updates CLIENT32.NLM, so that the users can't change the Opportunistic Locking field back to on. (Do a search of CLIENT32.NLM, and you should find it.) We haven't had any problems since changing the recommended parameters as follows: (This DID require about 4-5 calls to Tech Support though!) Auto Reconnect -> Set to 0 Cache Writes -> Set to OFF Delay Writes -> Set to OFF Opportunistic Locking -> Set to OFF Packet Burst -> Set to OFF (Just for stations running the ADMIN utility.) True Commit -> Set to ON File Cache Level -> Set to 0 ------------------------------ Date: Fri, 10 Jan 1997 12:28:18 MST From: Patrick Scannell Subject: Re: Win95 Client32 probs w/ Landesk [on this issue] I opened a case with Intel and the problem is easy to fix: Landesk puts indented IF commands in your login script. Version 2.01 accepts these, but v2.11 _sometimes_ rejects them and crashes the login. So if client32 v2.11 is giving you trouble, make sure the commands in your login script and all include files are flush left. ------------------------------ Date: Tue, 4 Mar 1997 18:50:42 -0800 From: Frank Wakelin Subject: Re: Client 32 for W95 - system policies >I'm looking for an easy way to protect the Netware 4.1 login setup >parameters from un/intentional meddling by students. Specifically, >I would like to configure each PC to automatically login with a >predetermined ID, and preferably without showing the Netware logon >screen. Also, prevent modification of the network properties. > >I've tried setting "Computer System Policies", as described in Novell >document 2911296. So far, I can't see that anything has changed. Is >there a better description of the proper procedure? One that even I >might understand? Please look for (and install) a program called Tweak UI on the net (@microsoft I think). This program will allow you to add (to the windows 95 registry) a username and password to logon to the net with by default EACH time, without prompting). In addition to this you can use the windows 95 system policy editor (on windows 95 cd (admin tools)) to edit that users' properties and remove their access to the contorl panel, logon as different user, etc. This should accomplish everything you need. In addition TweakUI is a control panel applet so restricting control panel access in that users policy should prevent that user from editing the default login password. Be carefull of how much access you restrict though. Here's a thought... If the default username and password are automaticly entered, and once that users' policy is logged into the system, you can not "close all programs and logon as a diferent user" (if you have restricted this (not entirely sure you can though)). If this happens you yourself will effectively be locked out of the system too. Not easy to get back in (requires editing of the registry in dos safe mode, due to the fact that you can also disable registry editing tools in the policies). Something to think about...... ------------------------------ Date: Wed, 5 Mar 1997 12:35:07 -0600 From: Joe Doupnik Subject: Re: Trouble with SCSI >Several days ago, in the following mail, you talked about PDOSETH. I cannot >get this to load. I believe this lets me run applications which talk to a >16bit ODI stack under client32. Is this correct? > >I have added a PDOSETH section to NET.CFG with frame types etc. > >I load LSL ok, then load PDOSETH. Client32 then complains that there is >insufficent frames to enable PDOSETH to operate properly. I have tried >upping the BOARDS figure to 2, this doesnt help. Anyone got any ideas? > >Joe Doupnik said >> ODIPKT is needed only if running MSK in Windows. MSK is a native >>ODI client, the same as is IPXODI from Novell. It is also a native Packet >>Driver client. To use MSK with Client32 for DOS/Windows be sure to run >>protected to real mode shim PDOSETH (or PDOSTOK etc) and LSL.COM. ---------- Yet again, here is an example: File c:\client32\startnet.bat - SET NWLANGUAGE=ENGLISH C:\CLIENT32\NIOS.EXE /L >start.log LOAD C:\CLIENT32\LSLC32.NLM >>start.log LOAD C:\CLIENT32\CMSM.NLM >>start.log LOAD C:\CLIENT32\ETHERTSM.NLM >>start.log LOAD C:\CLIENT32\CNE2000.LAN INT=5 PORT=300 FRAME=ETHERNET_II >>start.log LOAD C:\CLIENT32\CNE2000.LAN INT=5 PORT=300 FRAME=ETHERNET_802.3 >>start.log LOAD C:\CLIENT32\CNE2000.LAN INT=5 PORT=300 FRAME=ETHERNET_SNAP >>start.log LOAD C:\CLIENT32\CNE2000.LAN INT=5 PORT=300 FRAME=ETHERNET_802.2 >>start.log LOAD C:\CLIENT32\IPX.NLM >>start.log LOAD C:\CLIENT32\CLIENT32.NLM >>start.log c:\qemm\loadhi c:\client32\lsl >>start.log c:\qemm\loadhi c:\client32\pdoseth >>start.log File net.cfg, with omissions - ; File NET.CFG for NW 4.0, from Joe Doupnik ; Don't forget to say lastdrive=z in config.sys! Link Support Max Stacks 10 Buffers 4 1550 MemPool 2048 max boards 8 Link Driver NE2000 int 5 port 300 Frame Ethernet_II Protocol IPX 8137 Ethernet_II Protocol IP 0800 Ethernet_II Protocol ARP 0806 Ethernet_II Protocol RARP 8035 Ethernet_II protocol LAT 6004 ETHERNET_II frame ETHERNET_802.3 frame ETHERNET_802.2 frame ETHERNET_SNAP Link Driver PDOSETH Frame Ethernet_II Protocol IP 0800 Ethernet_II Protocol ARP 0806 Ethernet_II Protocol RARP 8035 Ethernet_II protocol LAT 6004 ETHERNET_II Joe D. ------------------------------ Date: Fri, 14 Mar 1997 09:36:13 -0600 From: Joe Doupnik Subject: Re: Client32 for DOS remote boot - solution Patrick Medhurst wrote: >Although it says in Novell TID 2911817 that you cannot remote boot >with Client32, you can if you swap the order of loading ipx and your >lan driver (i.e. load ipx before your lan driver) as in the following >example: > > nios.exe > load lslc32.nlm > load cmsm.nlm > load ethertsm.nlm > load ipx.nlm > load ne2000.lan port=360 int=5 frame=ethernet_802.3 > load ne2000.lan port=360 int=5 frame=ethernet_ii > load tcpip.nlm > load client32.nlm > >Unfortunately, if the workstation contains an A: drive it does >not become visible again after the remote boot completes. >Anyone have a solution to this? ---------- "This" being A: invisible until boot completion? That depends on the precise details of the remote boot program (of three common flavors). During remote booting there is mini-ODI material in action for the New Novell and RPL flavors and one needs to wait for the system re-boot process to complete and release resources. I have source code for some of this, and it's not trivial stuff to read. Alas I can't show it (zipped lips etc), and changing it is a formal project kind of thing. Joe D. ------------------------------ Date: Fri, 14 Mar 1997 23:52:24 EST From: seanstanton@juno.com (Sean M Stanton) To: netw4-l@ecnet.net Subject: Re: Win95 Client32 -Reply True, Microsofts MSNDS.EXE emulates VLM.EXE and the Win3x versions of the NW*.DLL drivers. You cannot, therefore, run the 32 bit Win95 version of NWADMIN. You can run the 16 bit Win3x version of NWADMIN.EXE just fine, and NETADMIN in a DOS box works fine as well. I have a large corporate client that has nothing but Win95 desktop PC's, with MS's Client for Novell Networks with MSNDS on top of it, and they run a wide mixture of DOS and 16 & 32 bit WIndows applications off of the NW4.1servers and their PC's are as stable, or more stable, than any Win95 network environment I've seen. ------------------------------ Date: Tue, 18 Mar 1997 16:05:09 +0000 From: Richard Letts Subject: Re: Client32 for Windows95 >Anybody know if there is a way to find what is the verion of >Novell client install on a windows95 workstation. C:\WINDOWS> NVER ------------------------------ Date: Tue, 18 Mar 1997 20:28:01 -0500 From: Jason Lester Subject: Re: HELP - Dual Frame Types on 3Com PCI NICs without prompt >Using Client32 to connect to NW 3.12 server using 3C590X driver on a >Dell Pentium w/ preinstalled 3Com 10/100 PCI PnP ethernet NIC's > >Need 802.2 for IPX and Ethernet_II for IP >Loading through startnet.bat called from autoexec.bat > >Client32 installation created the two needed LOAD lines >Loads 802.2 fine --BUT-- >When the LOAD Ethernet_II line runs I get a dialogue titled "Command >Line Parameter Prompt" asking me if I want to load another frame type on >an already loaded board. Oddly enough I have to answer No and Ok then >everything goes ahead and loads fine. > >What do I need to add to which bat file to avoid this? I think we jumped through these hoops a couple of months ago on the list, but they aren't in the FAQ yet. What you need to do is add a parameter in the STARTNET.BAT to the load lines for your network card. The parameter is the BOARD= that you sometimes use when loading LAN drivers on a server. Some cards require this and some don't. If the PORT and IRQ aren't specified, the driver has no other way of knowing if you mean the same card or another one. For example: LOAD 3COM.LAN (other parameters) FRAME=Ethernet_II BOARD=1 LOAD 3COM.LAN (other parameters) FRAME=Ethernet_802.2 BOARD=1 That tells the driver that you're loading another frame type for the same physical board. If this doesn't work, there were a couple of other things to try, but this fixed it on all of our systems for several different brands of cards (3Com, Addtron, Kingston, and Microdyne). ------------------------------ Date: Wed, 19 Mar 1997 15:07:52 -0500 From: Debbie Becker Subject: Re: Printing Probs? Client32/W95it2 >Has anyone else had printing problems once they installed the new client >with/without the w95it2 patch? We're running multiple brands of computers >on Win95 all priting to HP LaserJet 4Si and 5Si printers. Running >IntraNetWare with the printers set up as Remote Printers. > >When my labs went to the latest Client32 client to fix some other >problems, the win95 machines mysteriously started dropping prints. >Actually I believe the machines are somehow losing their connections to >the printer, since they set themsevles to print off-line. I haven't had >this happen to me personally, but I've had reports of it from other people >I work with. This seems to happen with or without the w95it2 patch. >(Anyone else notice that you can't get to the w95it2.exe patch from the >support.novell.com site anymore?). I haven't worked much in the Win95 environment (so take this with a grain of salt ), but had similar problems on my laptop when I had used a network printer by simply defining a network printer by queue. I was having the same sort of problem that you are (even when printer was setup, I'd log in through Win95 and try to print and it would say the printer was "offline") -- if I'd reboot Win95, that would sometimes fix the problem for the time being, but this didn't seem to be a very practical thing to have to do on an on-going basis. I was also experiencing error messages telling me that the file hadn't printed correctly even when it had (and then the printer would go offline again!) Based on several things I'd read on the list, I made the following changes: 1) I went into the printer properties and told it to capture a printer port (LPT1 to the queue). Told it to reconnect upon login. 2) I also changed the spool data format (under spool settings) from RAW to EMF. I'm not sure if this had a positive effect or not, but everything seems to print consistently now and even if the printer truly is offline initially, I'm able to reach it when it goes back online. These are probably work-arounds at best (reflecting a less-than-perfect understanding of how Win95 deals with printers ), and kind of inconvenient to have to implement in a large-scale environment (love that going around workstation to workstation, don't you), but might help you out if you don't get a more practical response... ------------------------------ Date: Thu, 27 Mar 1997 09:13:32 -0600 From: Joe Doupnik Subject: Re: Stil having problem with MS Kermit 3.14-15 >I'm still unable to make MS Kermit work with my Client32 for DOS. I tried >several things. Is there someone here who can explain me what to do >exactly or point me on good docs on installing it with Client32. --------- Once again, only one protocol stack of a given kind (say TCP/IP) over a single network adapter. Thus one may not have a winsock and Kermit's internal TCP/IP stack run at the same time. Joe D. ------------------------------ Date: Thu, 27 Mar 1997 14:13:42 -0600 From: "Paille, Dominik" To: "'netw4-l@ecnet.net'" Subject: RE: Client32 creates two connections >Using the VLM client, each computer used only one connection on the >server. After using Client32 for a while I noticed many, many "Not >logged in" connections showing up at the Console Monitor. When I >checked closely I found that for each connection of a logged-in user >using Client32 there was one not-logged-in connection for the same >NIC id. > >If I delete the "extra connection", the user seems to be able to >continue to work on the network normally until logging out. At log >out, the user is immediately logged out of the server but it takes a >minute and a half to get logged out of the directory services tree! > >When the user logs back in, at the instant the password is entered, >the "extra connection" reappears! > >Is this normal? I find it hard to believe it is! This Ghosting of connections is by design in the 32 bit client. I was at a clients sight, and they brought this up as a concern. We found out in the literature that in 4.1 this ghosting connection does not harm anything and it acts like a static "just in Case" for instant reconnection if accidently disconnected. ------------------------------ From: "Peter Scherrer" To: floyd@direct.ca Date: Thu, 3 Apr 1997 07:04:15 +1 Subject: Addition to novell FAQ I have received the error message "Module NIOSWIN.NLM did not properly free 1 resource" with Novell's DOS 32-bit client. Usually the machine crashes after the message, but sometimes just the connection to the network is lost. In the meantime others reported that Client32 is also causing some of the machines to crash - randomly. The solution is quite simple: increase the dos environment space in CONFIG.SYS. Change or add the line: COMSPEC=C:\command.com C:\ /p/e:2048 ------------------------------ Date: Wed, 9 Apr 1997 14:07:57 -0600 From: Joe Doupnik Subject: Re: Protected Mode Definition >Anyone have a succinct definition of "protected mode" (as in "Client32 >is a protected mode driver")? -------- I'll refer you to any of the Intel 286 and later cpu docs. The machine architecture changes from emulating 8088/8086 1MB total to dealing with more memory, which means registers change too, and with allowance/ disallowance of certain instructions, and so on at great length. If those details are of little interest we can summarize the matter as "different." The word "protected" is a catchall for meaning many things, all different from the simple 8088 style cpu architecture. Joe D. --------- Date: Wed, 9 Apr 1997 16:11:58 EST From: Bill Hodges Subject: Re: Protected Mode Definition >Anyone have a succinct definition of "protected mode" (as in "Client32 >is a protected mode driver")? The operating system doesn't have to switch the processor to real mode to interact with the hardware controlled by the driver. --------- Date: Wed, 9 Apr 1997 14:17:41 -0700 From: Shawn Subject: Re: Protected Mode Definition >Anyone have a succinct definition of "protected mode" (as in "Client32 >is a protected mode driver")? Here's a definition from "The Free On-line Dictionary of Computing". There's a link to it on my Glossaries page, http://www.futureone.com/~opeth Protected Mode -------------- An operating mode of Intel 80x86 processors. The opposite of real mode. The Intel 8088, Intel 8086, Intel 80188 and Intel 80186 had only real mode, processors beginning with the Intel 80286 feature a second mode called protected mode. In real mode, addresses are generated by adding an address offset to the value of a segment register shifted left four bits. As the segment register and address offset are 16 bits long this results in a 20 bit address. This is the origin of the one megabyte (2^20) limit in real mode. There are 4 segment registers on processors before the Intel 80386. The 80386 introduced two more segment registers. Which segment register is used depends on the instruction, on the addressing mode and of an optional instruction prefix which selects the segment register explicitly. In protected mode, the segment registers contain an index into a table of segment descriptors. Each segment descriptor contains the start address of the segment, to which the offset is added to generate the address. In addition, the segment descriptor contains memory protection information. This includes an offset limit and bits for write and read permission. This allows the processor to prevent memory accesses to certain data. The operating system can use this to protect different processes' memory from each other, hence the name "protected mode". While the standard register set belongs to the CPU, the segment registers lie "at the boundary" between the CPU and MMU. Each time a new value is loaded into a segment register while in protected mode, the corresponding descriptor is loaded into a descriptor cache in the (Segment-)MMU. On processors before the Pentium this takes longer than just loading the segment register in real mode. Addresses generated by the CPU (which are segment offsets) are passed to the MMU to be checked against the limit in the segment descriptor and are there added to the segment base address in the descriptor to form a linear address. On a 80386 or later, the linear address is further processed by the paged MMU before the result (the physical address) appears on the chip's address pins. The 80286 doesn't have a paged MMU so the linear address is output directly as the physical address. The paged MMU allows for arbitrary remapping of four klilobyte memory blocks (pages) through a translation table stored in memory. A few entries of this table are cached in the MMU's Translation Lookaside Buffer to avoid excessive memory accesses. After processor reset, all processors start in real mode. Protected mode has to be enabled by software. On the 80286 there exists no documented way back to real mode apart from resetting the processor. Later processors allow switching back to real mode by software. Software which has been written or compiled to run in protected mode must only use segment register values given to it by the operating system. Unfortunately, most application code for MS-DOS, written before the 286, will fail in protected mode because it assumes real mode addressing and writes arbitrary values to segment registers, e.g. in order to perform address calculations. Such use of segment registers is only really necessary with data structures that are larger than 64 kilobytes and thus don't fit into a single segment. This is usually dealt with by the huge memory model in compilers. In this model, compilers generate address arithmetic involving segment registers. A solution which is portable to protected mode with almost the same efficiency would involve using a table of segments instead of calculating new segment register values ad hoc. To ease the transition to protected mode, Intel 80386 and later processors provide "virtual 86 mode". ------------------------------ Date: Tue, 15 Apr 1997 11:49:50 -0500 From: Jason Lohrenz Subject: Client 2.12 differences Here's the big change from 2.11 client 32 to 2.12 Major updates included in version 2.12 include: - Updates to Client32.nlm. - Updates to ODINSUP.SYS to provide support for the OSR2 release of Windows 95. (OEM Service Release version 2) - Updated ODI Lan drivers. ------------------------------ Date: Sun, 27 Apr 1997 10:26:51 -0600 From: Joe Doupnik Subject: Re: Win95b and Client32 >I don't know if this has been covered, but has anyone else had problems >with Client32 for Win95. > >I have a Vectra VL series 5 with an Intel10/100BTX card, that when I load >Client32, it freaks----loss of network community is the most minor of it. > I had to reload windows entirely. (Make me happy that my main machine is >a Macintosh). > >Are there patches for Client32? ------------ Look for memory conflicts above the top of physical memory. The Intel Etherexpress 100B uses such a memory buffer, and alas so do some video adapters, and they can conflict to lose video and/or communications. There is an undocumented command to the Intel driver, IOMAPMODE=1, which changes the board from shared memory to port i/o. But so far I see no way of stating that change with the Win95 version of Client32, and I spent part of Saturday trying. The alternative is to tinker with the video board settings/driver while within Win95. What is needed is a way of stating command line options for the Intel driver when it loads. That is not present in the current Win95 Client32 material. Alternatively, the option ought to be expressable to the Intel board's CMOS setup, and that's on my list to probe. The memory conflict problem does not appear at DOS level; it happens when the Windows drivers get cute about dense graphics modes. The fallback is to use the 16-bit real mode driver E100BODI.COM. Additional info: the identical problem occurs with Client32 for Win31. But the cure is very easy because we add that phrase to the LOAD line of the driver, like this: SET NWLANGUAGE=ENGLISH C:\NOVELL\CLIENT32\NIOS.EXE LOAD C:\NOVELL\CLIENT32\LSLC32.NLM LOAD C:\NOVELL\CLIENT32\CMSM.NLM LOAD C:\NOVELL\CLIENT32\ETHERTSM.NLM LOAD C:\NOVELL\CLIENT32\E100B.LAN slot=10001 SPEED=10 IOMAPMODE=1 TXTHRESHOLD=200 FRAME=Ethernet_II (line above is broken into two for mailing) LOAD C:\NOVELL\CLIENT32\E100B.LAN slot=10001 FRAME=Ethernet_802.2 LOAD C:\NOVELL\CLIENT32\E100B.LAN slot=10001 FRAME=Ethernet_802.3 LOAD C:\NOVELL\CLIENT32\E100B.LAN slot=10001 FRAME=Ethernet_SNAP LOAD C:\NOVELL\CLIENT32\IPX.NLM LOAD C:\NOVELL\CLIENT32\CLIENT32.NLM /c=c:\novell\client32\net.cfg c:\qemm\loadhi c:\novell\client32\lsl c:\qemm\loadhi c:\novell\client32\pdoseth Joe D. ------------------------------ Date: Mon, 5 May 1997 11:59:03 +0100 From: "David W. Hanson" Subject: Re: Client32, DOS/WIN client32 and VLM:s ? >Floyd Maxwell wrote: >>Client32 Cons: >> - Relatively new technology - some issues/bugs still remaining (but >> are being fixed) > ^^^^^ > worked on >> - Can't be used to run Win95 shared from network server >> - No private drive mappings in a DOS box under any Windows ver. >> - Requires 386+ and a few MB of extended memory. > ^^^^^^^^^^^^^^^^^^^^^^^^^^^ >This was Jon's worst error/omission -- as written it could be viewed >as a "show stopper" also. The fact is C32 needs about 800 KBytes of RAM, >but will use more, or much more, (for caching) _by default_ depending on >the amount of RAM in the client...best to decide how much RAM cache, if >any, you want each client to have and then set it explicitly. > >I'd add another "Con also: >- Caching seems to bring problems and many have turned it off. Another "Con" is that Client32 eats up licensed server connections in multi-server 4.x environments. If you are using Client32 and you use a resource on a server, you will use up a licensed connection on that server, even after you have stopped using the resource, until you -explicitly- log out of that server. Going from VLM to Client32 in a multi-server environment will most likely require you to increase your license counts on some/all servers. ------------------------------ Date: Wed, 30 Jul 1997 13:04:00 -0700 From: Kevin Miller Subject: Re: Novell Clients, NT 4.0 Server w/FPNW ???? There is a bug (rather, an implementation error) in Microsoft's FPSW that makes it incompatible with Client 32 clients. There is a patch for this on Microsoft's WWW site. ------------------------------ Date: Thu, 14 Aug 1997 09:43:57 +1000 From: Michael Strasser Subject: Re: Client32 for NT/Win95 and login scripts >We run a number of external programs in our login scripts, which has >worked well for DOS logins, but not so well for NT and Win95 logins. >I'm checking ways of combining all of the output from login script >commands and external programs into a single window. Some questions: > >1. Has anyone found a slick way of doing this? No. I found that only the script processor can write to the "Login results" window. I have a simple Win32 program that counts new mail messages (*.CNM in SYS:MAIL/xxxxxxxx) and puts up an alert. It is very crude and relies on being passed the user ID as an argument. (This is on NW 4.11 but we still use Mercury and Pegasus in bindery mode.) >2. Is there any way to control the size of the window created by the > login program? The size and position is saved in the registry in: [HKEY_LOCAL_MACHINE\Network\Novell\System Config\Network Provider\Graphical Login\Results Pos] so any changes you make are 'remembered' (regardless of the "Save settings on exiting Login" settings on the Client 32 Properties login tab). I guess you could change them in advance if you had a registry-poking tool. >3. Is there any way to control the font used - I want to use > a non-proportional font. Not as far as I know. ------------------------------ Date: Tue, 28 Oct 1997 14:00:30 -0700 From: Tim Madden Subject: Re: Dos Windows client question >How would one enable, if possible, the use of two IP routers >at the client level. In Win95 this is possible and used for >roaming users. But with the Dos/Windows client I am not >sure how it would work. Has anyone ever done this before. I, too, am just learning the DOS/Win3.1 client. Have been reading the nwcfgdw.hlp and setup.hlp files. Both files found in the nls\english sub-dir of the parent directory. Definite required reading. Found this in the first one. IP_ROUTER Defines the IP address of the default router for packets being sent to remote networks when no specific routing information to the destination network exists. Syntax: ip_router ip_address [network_name ] Default: none Example: PROTOCOL TCPIP IP_ROUTER 222.33.44.50 Notes: A maximum of three IP_ROUTER entries per network interface can be used. The order of IP_ROUTER entries determines the order in which the routers are used. ------------------------------ Date: Tue, 28 Oct 1997 18:42:27 -0700 From: Brandon Fouts Subject: client32 dos/windows >I need to ensure that TCP/IP, and only TCP/IP, loads on my >3C905 NIC, and that IPX, and only IPX, loads on my 3C590 >NIC. I've been playing with load order and NET.CFG >settings for several hours and am mostly there. STARTNET.BAT NOT NET.CFG (can you run two NICs in a workstation at the same time??) I use the 2.12 version - working great. Just go into the STARTNET.BAT file and delete what you don't want to load - actually, I'd REM it out, I never delete from any setup files, it helps me back track and reminds me what I did months earlier - I also add comments to help me remember. You can get a past Application Note on Client32, a little out dated, but has all the basics - cost about $20 to order from Novell. IF you belong to NUI, check the CD - or NesPro also has it. The windows read hlp files are very good, so I'd find a windows computer to read them with. Application Notes May 1996 Also check out the Novell knowledge base and see what TIDs you find. --------- Date: Wed, 29 Oct 1997 09:34:42 -0700 From: Tim Madden Subject: Re: client32 dos/windows >>I need to ensure that TCP/IP, and only TCP/IP, loads on my >>3C905 NIC, and that IPX, and only IPX, loads on my 3C590 >>NIC. I've been playing with load order and NET.CFG >>settings for several hours and am mostly there. > >STARTNET.BAT NOT NET.CFG >(can you run two NICs in a workstation at the same time??) > >I use the 2.12 version - working great. > >Just go into the STARTNET.BAT file and delete what you >don't want to load - actually, I'd REM it out, I never delete >from any setup files, it helps me back track and reminds me >what I did months earlier - I also add comments to help me >remember. > >You can get a past Application Note on Client32, a little out >dated, but has all the basics - cost about $20 to order from >Novell. IF you belong to NUI, check the CD - or NesPro also >has it. The windows read hlp files are very good, so I'd find a >windows computer to read them with. > >Application Notes May 1996 > >Also check out the Novell knowledge base and see what >TIDs you find. Actually, your suggestion about reading the Windows help files was right on target. I did just that yesterday and found out how to do what I wanted. And it was the NET.CFG that needed the proper settings. Protocol TCP/IP and Protocol IPX are the pertinent areas, if you're interested. So, yes, you can run two NICs in a workstation. ------------------------------ Date: Tue, 4 Nov 1997 07:56:24 -0800 From: Darren House Subject: Re: VLM - DOS vs. WIN LOGIN The only real difference between the GUI Win311 Login and the Non-GUI DOS Login for Client32 is that the DOS login.exe is executed from the server, off the SYS: Volume and the GUI LoginW31.exe is executed from the Novell\Client32 directory on the workstation. The load order remains the same for both GUI & non-GUI. ------------------------------ Date: Wed, 3 Dec 1997 21:47:00 +0000 From: Randy Richardson Subject: Novell Client 32 vs MS Client 32 >>I run Novell's client 32 and Microsofts client on different machines, are >>there any advantages of one client over the other? We presently have a >>Novell 4.1 server with the latest patches. > >The main difference is the MS client is not NDS aware. You cannot use any >of the many NDS features. That's correct. Additional features you may also be interested in: - Auto-reconnect drives, open files, record locks, etc. - C2 redbook (security) compliant - Nice login screen with configurable options - NetWare Application Launcher support - Roaming profiles support - ODI driver support - NDPS support The list goes on. --------- Date: Thu, 4 Dec 1997 07:52:04 +0200 From: Mike Glassman - Admin Subject: Novell Client 32 vs MS Client 32 Two points regarding this issue. The Netware client is built for working in a Netware (and other) environment and is best suited for the Netware connectivity. It is periodically updated and is constantly being improved. The MS client was written way back when Netware was still 4.0X and has not once been updated since then, and as far as MS is concerned, works so they will not change it. From looking at these two points, will you choose a software connectivity client which was written specifically for an OS by the company which wrote the OS, or choose one which was written by a company which is well known for putting out buggy software (no matter that it is a big comapny), and which wrote the client for an OS that was fazed out a while back and is not going to put out a new client. Don't get me wrong, I have every respect for MS and it's software. What other company could get away every single time with software that has the amount of bugs and problems that theirs does :) Today is not my love-MS day. ------------------------------ Date: Tue, 9 Dec 1997 19:44:00 +0000 From: Randy Richardson Subject: Re: Client32 and MS Databases >i have not had this locking problem yet, but am currently implementing a >developer product called ACEWARE that is foxpro based and was warned by tech >support it may be problematic if client32 is used due to these issues > >from bad memory , i remember the tech stating something like maximum locks >with client 32 as 170 - dont quote me!! > >in my case,not a problem yet as this particular server is 3.x, using NETX >but will be upgraded so i expressed concerns as we "require" client32 to >access all INW4 servers > >developer tech support indicated they would send a list of about 12 TIDs, >but i have not seen it yet > >if i get it , i will post - i will be talking to the developer later this >week and raise these issues The maximum number of record locks is set at the server. The best way to find out if there are any problems is to write a small program that locks more than 170 records, and see if all those records are actually locked by trying to access them from a second workstation. The following SET parameters, from an IntranetWare server, should be helpful: Maximum Record Locks Per Connection: 500 Limits: 10 to 100000 Description: Maximum number of record locks per connection (physical, logical & semaphores) Maximum File Locks Per Connection: 250 Limits: 10 to 1000 Description: Maximum number of file locks per connection (including open files) Maximum Record Locks: 20000 Limits: 100 to 400000 Description: System wide maximum number of record locks (physical, logical & semaphores) Maximum File Locks: 10000 Limits: 100 to 100000 Description: System wide maximum number of file locks (including open files) If these default settings on your IntranetWare server need to be increased, then include that information in your documentation. Make sure you use the latest version of Client32 (v2.20 at this time), and get familiar with all the Client32 parameters. ------------------------------ Date: Thu, 11 Dec 1997 14:03:40 -0600 From: Joe Doupnik Subject: Re: Client 32 W95 questions, problems >I support an accounting app which in the past, with VLMs, I had good >success using "True Commit = ON" to maintain data integrity. While >this had some impact on performance, it wasn't severe. > >With C32 v2.20 and Win95, when I turn on True Commit I get a *huge* >performance loss on writes, far more than when I used it with the >VLMs. Is this to be expected? Shouldn't be that way. True Commit means what it says, do the I/O synchronously with the request subject to delays in Win95 itself. Suggests that whenever True Commit is turned on, all write caching is turned off. If so, what is the purpose of the separate "Cache Writes" parameter, and what is the difference in their effect? Is Caching and true commit are clearly in opposition. So one can have either one or the other. >turning off Cache Writes identical to using True Commit, in >particular for apps that actually do a "write commit"? (even in dumb >copies like Xcopy, turning off True Commit improves performance >drastically in C32 v2.20) > >Novell suggests performance problems with C32 are often resolved by >using ODI instead of NDIS drivers. I use the latter due to reports >of problems with this application using ODI drivers under C32. If I >decide to switch to ODI, should I completely uninstall the client >first? Some people suggest they have to do that when they change >NICs. This is difficult to answer. The clean approach is to perform a complete uninstall and then do a reinstall and then peek at the registry to see if loose ends exist. However, I swap lan drivers on the fly with no reinstallation of the client material. Deep beneath the covers ODI should be faster than NDIS material, but then we are speaking of drivers written by the board makers rather than by Novell so particulars vary with board. Novell is aware of some loose ends persisting and are trying to automate cleaning them up. Joe D. ------------------------------ Date: Fri, 9 Jan 1998 11:00:00 +0000 From: Randy Richardson Subject: Re: Client32-other languages? >The new Client32 2.2. (DOS, WIN31, WIN95) and 4.11a (WinNT) are >available for months in english. > >Does anybody know when other languages (german) will be available? Go to the following URL, then click on the "Feedback" link at the bottom of the page: http://www.novell.com/download/locale.html I've asked questions through these "Feedback" links before, and I've received responses. ------------------------------