--------------------------------------------------------------------------- NVCL32D1.DOC -- 19960826 -- 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: Wed, 10 Apr 1996 13:47:05 -0600 From: Joe Doupnik Subject: Client32 for DOS/Win 3.1, open beta announcement Those with Internet access will find the beta Client32 files in updates/nwos/CL32DWOB as two 5MB files, one for installing from floppy (d)isk images and the alternative for installing from a (N)etWare server directory. To alleviate network congestion we recommend you contact one of the official Novell mirror sites listed below (or use ftp.novell.com) Boston NetWare User's Group, bnug.harvard.edu [128.103.85.201] Lincoln University, tui.lincoln.ac.nz [138.75.90.4] National Research Council (Canada), novell.nrc.ca [132.246.160.4] University of Groningen, ftp.rug.nl [129.125.4.15] University of Salford, ftp.salford.ac.uk [146.87.255.21] Utah State University, netlab2.usu.edu [129.123.1.44], and netlab1.usu.edu [129.123.1.43] Joe D. -------------- April 10, 1996 Novell Announces Open Beta Availability of NetWare Client 32 for DOS/Windows New Client Offers 32-bit Access to NetWare Services from DOS or Windows Desktops OREM, Utah April 10, 1996 Novell, Inc. today announced the open beta availability of its NetWare Client 32 for DOS/Windows. The NetWare Client 32 for DOS/Windows is the only client software to offer DOS and Windows 3.1 desktop users full 32-bit access to NetWare services, including its industry-leading Novell Directory Services (NDS). In addition to providing increased speed through 32-bit access, the NetWare Client 32 software lets users benefit from full automatic reconnection to all network files and resources, as well as simultaneous access to multiple directory trees and fault tolerance to ensure reliable and comprehensive access to network services. The Client 32 software includes the NetWare Application Manager, which gives users transparent access to network applications and centralizes network application installation and administration through NDS. Built on Novell's proven Client 32 architecture, the NetWare Client 32 for DOS/Windows is a key component in Novell's strategy to enable a Smart Global Network by giving users reliable access to the information they need anytime, anyplace. "One of the biggest benefits of NetWare Client 32 for DOS/Windows is that it loads into extended memory," said Ron Dike, network engineer for the Alyeska Pipeline Service Company. "This allows us to run PC card services on our laptops. We also have more flexible configurations on desktops because there is significantly more conventional RAM without having to implement costly upgrades. Novell's Client 32 provides us with the best Windows integration available." Novell is committed to providing complete network access to all desktop operating systems, including the legacy operating systems which exist in today's heterogeneous networks. The NetWare Client 32 for DOS/Windows provides 16-bit desktop environments with full 32-bit access, offering users enhanced performance and superior network integration. The NetWare Client 32 for DOS/Windows and the recently released NetWare Client 32 for Windows 95 share the same code-base, easing upgrades from DOS and Windows 3.1 to Windows 95 by allowing network administrators to leverage network drivers as they upgrade client software. The NetWare Client 32 for DOS/Windows extends the full availability of NetWare services to users of MS-DOS 5.0 or above, Windows 3.1 or above and Windows for Workgroups 3.11 or above. The NetWare Client 32 for DOS/Windows allows users to: - Authenticate to and simultaneously browse resources on multiple NDS trees (graphically within Windows), simplifying connections to all network information and resources; - Operate with a smaller conventional memory or Upper Memory Block (UMB) footprint, freeing up additional memory to run applications (4kb in most environments using 32-bit LAN drivers); - From within Windows, use a GUI login utility to access NetWare servers, including updating environment variables and searching drive mappings; - Fully access NetWare 2.x, 3.x and 4.x resources throughout the network, providing connectivity and backwards compatibility with all services and information; - Take advantage of extensive automatic reconnect capabilities, including open files, mappings and file locks, providing intelligent recovery and fault tolerance for the user; - Benefit from dynamic client-side caching, enabling faster performance of repetitive desktop functions; and - Enjoy improved LAN and WAN performance via support for Large Internet Packets (LIP) and Third Generation Packet Burst. The NetWare Client 32 for DOS/Windows also provides the following network management capabilities to network administrators: - Dynamically setup and refresh client software across the network with Automatic Client Update capabilities, lowering the cost and complexity of client upgrades; and - Centrally administer applications accessed by users through NDS with NetWare Application Manager. Pricing and Availability The NetWare Client 32 for DOS/Windows with NetWare Application Manager is available now to NetWare users electronically, free of charge, from NetWire on CompuServe (GO NWCLIENT) and the World Wide Web (http://netwire.novell.com). For additional information, customers can contact Novell at 1-800-NETWARE, or download information from NetWire on CompuServe or the World Wide Web (http://www.novell.com). ------------------------------ Date: Thu, 11 Apr 1996 16:43:37 -0600 From: Joe Doupnik Subject: Re: Client 32 (Dos/Win) NIOS problems >I've recently downloaded the Client 32 Beta for Dos/Windows and have not had >any success in getting it running. My problem is that NIOS.EXE hangs the >workstation and I'm unsure of how to proceed. > >I suspect that, because I'm using a 16 bit NIC, special handling is required >but it would seem that any failures with the Lan card itself should show up >later, not during the load of NIOS. I manually added the 802.3 frame type >(defaults to 802.2), and tried loading with different NET.CFG's (original >has more information specific to the VLM's I'm running now) but no luck. >Any suggestions? -------- Most likely your system needs lotsa help with memory management. Please check that carefully. Recall that Client32 material puts its components above 1MB so space is needed up there and a decent memory manager is the way to accomplish it. I use QEMM/386 with no problems of this kind. You can change the way Client32 treats your memory manager; please have a look at the notes for assistance. PDOSETH is an attachment for a 16-bit ODI interface to appear, and the 16-bit LSL is needed as a prerequisite. Here's an example startnet.bat file using it: SET NWLANGUAGE=ENGLISH C:\CLIENT32\NIOS.EXE LOAD C:\CLIENT32\LSLC32.NLM LOAD C:\CLIENT32\CMSM.NLM LOAD C:\CLIENT32\ETHERTSM.NLM LOAD C:\CLIENT32\CNE3200.LAN SLOT=6 FRAME=ETHERNET_II LOAD C:\CLIENT32\CNE3200.LAN SLOT=6 FRAME=ETHERNET_802.3 LOAD C:\CLIENT32\CNE3200.LAN SLOT=6 FRAME=ETHERNET_SNAP LOAD C:\CLIENT32\CNE3200.LAN SLOT=6 FRAME=ETHERNET_802.2 LOAD C:\CLIENT32\IPX.NLM LOAD C:\CLIENT32\CLIENT32.NLM c:\client32\lsl c:\client32\pdoseth Notice above I'm using the CODI 32-bit board handler in this case. Here is a second example, with a 16-bit board handler: SET NWLANGUAGE=ENGLISH C:\CLIENT16\NIOS.EXE > c16.log C:\CLIENT16\LSL.COM >> c16.log C:\CLIENT16\N16ODI.COM >> c16.log C:\CLIENT16\NESL.COM >> c16.log C:\CLIENT16\NE2000.COM >> c16.log LOAD C:\CLIENT16\LSLC32.NLM >> c16.log LOAD C:\CLIENT16\PC32MLID.LAN >> c16.log LOAD C:\CLIENT16\IPX.NLM >> c16.log LOAD C:\CLIENT16\CLIENT32.NLM >> c16.log Joe D. ------------------------------ Date: Fri, 12 Apr 1996 21:05:26 -0700 From: Floyd Maxwell Subject: Is it just me? -- C32 4 DOS/Win Beta Is it just me or is this a great product? - 30-100 KB less "lower 1MB" RAM usage...your mileage may... - fast (at times) thanks to cool *network* caching - painless to install Sure its buggy, but I have renewed faith in Novell's ability to innovate and _improve_ their main product. ...Thank You, Mr. Frankenburg! Tip: Depending on the other TSRs you normally load, the Client 32 (beta) for DOS/Windows saves so much memory that you may be able to do away with EMM/QEMM/whateverMM and gain 10 or 15% performance from that as well! ------------------------------ Date: Fri, 12 Apr 1996 07:53:33 +0200 From: Henno Keers Subject: Re: Client 32 (Dos/Win) NIOS problems >I've recently downloaded the Client 32 Beta for Dos/Windows and have not had >any success in getting it running. My problem is that NIOS.EXE hangs the >workstation and I'm unsure of how to proceed. > >I suspect that, because I'm using a 16 bit NIC, special handling is required >but it would seem that any failures with the Lan card itself should show up >later, not during the load of NIOS. I manually added the 802.3 frame type >(defaults to 802.2), and tried loading with different NET.CFG's (original >has more information specific to the VLM's I'm running now) but no luck. >Any suggestions? > >Details: >During startup, NIOS starts and a line stating that logging is ENABLED shows >up on the screen but then the system hangs. No log file is recorded and >CTRL-ALT-DEL is ineffective. The system must be booted with the reset >switch (or power cycle). I tried it first without logging to a file, then >added the /L command. > >Novell 3.12 on Ethernet 802.3 >NIC: Intel EtherExpress PRO >PC: Dell Dimension XPS P90 (Pentium, 16 MB) >EMM386.EXE is dated 11/01/93 > > ---------- STARTNET.BAT ---------- >SET NWLANGUAGE=ENGLISH >C:\NOVELL\CLIENT32\NIOS.EXE /L >C:\NOVELL\CLIENT32\LSL.COM >C:\NOVELL\CLIENT32\N16ODI.COM >C:\NOVELL\CLIENT32\NESL.COM > >(NOTE: I tried with and without the following file >which is required for 16 bit protocol stacks >according to the help file) >C:\NOVELL\CLIENT32\PDOSETH.COM > >C:\NOVELL\CLIENT32\EPROODI.COM >LOAD C:\NOVELL\CLIENT32\LSLC32.NLM >LOAD C:\NOVELL\CLIENT32\PC32MLID.LAN >LOAD C:\NOVELL\CLIENT32\IPX.NLM >LOAD C:\NOVELL\CLIENT32\CLIENT32.NLM > > ---------- NET.CFG ---------- >Link Driver EPROODI > PORT 300 > FRAME Ethernet_802.3 > int 5 > >NETWARE DOS REQUESTER > PREFERRED SERVER = RACE > FIRST NETWORK DRIVE = F > NETWORK PRINTERS = 3 > NETWARE PROTOCOL = BIND May I suggest to check out the diskette that came with the Intel NIC and look for a .LAN driver for a NetWare 3.12/4.x server ? It is a .LAN driver NLM that needs MSM and ETHERTSM, of which special versions come with Client32. Use that NLM instead of the 16 bit (real mode) ODI material. The startnet.bat will then look like: > ---------- STARTNET.BAT ---------- >SET NWLANGUAGE=ENGLISH >C:\NOVELL\CLIENT32\NIOS.EXE /L >LOAD C:\NOVELL\CLIENT32\LSLC32.NLM >LOAD C:\NOVELL\CLIENT32\??????.LAN >LOAD C:\NOVELL\CLIENT32\IPX.NLM >LOAD C:\NOVELL\CLIENT32\CLIENT32.NLM Fill in the ?????.LAN for the correct file-name. ------------------------------ Date: Mon, 15 Apr 1996 12:52:57 +0100 From: Phil Randal Subject: Re: Is it just me? -- C32 4 DOS/Win Beta On 12 Apr 96 at 21:05, Floyd Maxwell wrote: > Is it just me or is this a great product? > > - 30-100 KB less "lower 1MB" RAM usage...your mileage may... > > - fast (at times) thanks to cool *network* caching The network caching is so cool it conficts with several DOS programs I run here. Using the defaults for File Cache Level resulted in a corrupted Pegasus Mail Folder (for this list, darn it) after running PMail for DOS (v3.31) and various problems with other DOS-based software. To ensure compatibility with existing software I've had to set File Cache Level to 1. Another strange quirk I've found is client32.nlm not finding the network when loaded. Unload and reload and it attaches. Or delay 2 seconds before loading client32.nlm and it attaches properly. This is on a segment running NLSP routing only. LAN driver is the Intel EtherExpress Pro 10 EPRO.LAN driver. Workstation is a DX4/100 PC. The third quirk is with Vernon Buerg's LIST and FV programs. Run LIST on a network drive, select a .zip file to view, Alt-V to get the zip calalogue, and Alt-I to view one of the files therein... Redirecting of stdout doesn't seem to happening correctly... Perhaps Floyd would like to start a 'Client32 Bugs ' mailing list :-) ------------------------------ Date: Sun, 14 Apr 1996 15:59:46 -0400 From: "David P. Moon" Subject: Client 32 lockups - Part 2 On 12 Apr 96 at 16:34, David P. Moon wrote: >Installed Client 32 for DOS and Windows (network install) >on a Gateway 2000 486DX 66MHz PC with an Intel EtherExpress Pro >10 network card. 40MB RAM, DOS 6.22, HIMEM.SYS > >Novell Netware 3.11 Servers, with Netware Name Services. >LOGIN.EXE v 3.71 >CAPTURE.EXE v 3.50 > >First installed using the 32 bit driver EPRO.LAN >(20457,11-30-95). Computer locks up while executing the >#CAPTURE command from the users login script. MONITOR shows >that I have the file SYS:PUBLIC/NET$PRN.DAT open at this point, >but no activity. Keyboard is also locked. After removing the >#CAPTURE from the login script and rebooting, the PC completes >the login, but locks up at the end of the autoexec.bat file >when the IBM antivirus program runs. > >@CALL C:\IBMAV\IBMAVDR C:\IBMAV\ AFTERLAN L:\APPS\IBMAV\ > >I commented out the IBM antivirus, and inserted a number of >PAUSE statements into the domain, profile, and user login >scripts so I could catch any error messages that might be >there. The first command in the domain login script is MAP INS >S1:=SYS:PUBLIC. Sometimes this worked, other times I get the >error message "Attempt to map drive to invalid path..etc". > >Seems to have trouble executing other external commands in the >login scripts as well, such as #caston, even if S1 gets mapped >to sys:public successfully first. > >If I remove >#CAPTURE L=1 NA NT NFF NB TI=20 Q=ROOM6HP4 NOTI >from the login script, and then try to run it manually after the >autoexec.bat, I lock up again with the file >SYS:PUBLIC/NET$PRN.DAT open. > >In the login script, I have >MAP M:=560server-1/sys: >Drive M: gets mapped to SYS:, but with strange results. >DIR M:\ shows me the directories, one of which is M:\CAL. >DIR M:\CAL responds with just M:\CAL, no files. >CD\CAL responds with "Invalid directory" >If I remap the drive by entering >MAP M:=SYS: >the directory rights are then recognized correctly and I can >access the files in M:\CAL. I changed the MAP statements in the login scripts to external MAP commands (#MAP), and this solved the above mentioned problems with directory rights. >I commented out the DOS LOGIN.EXE command, rebooted and ran >MS Windows. Using NWTools, I manually attached to my servers, >and mapped the various drives, and search drives I needed, and >attached to the print queue. Most everything worked great from >here. Pegasus fired right up, and my winsock programs (Mosaic, >WS_FTP, EWAN, SPRY) all seemed to work very well with the new >TCPIP.NLM. I marked all the drives/searchdrives as permanent, and restarted (no DOS LOGIN). When WINDOWS starts up, it asks me for my login name and password, attaches to the server, and correctly maps the drives/printers I need. But when I opened a DOS window, and browsed through the drives, I found one drive which wouldn't allow me to list any of its subdirectories. The RIGHTS command showed me as having RF rights to the drive, and RWCEMF rights to the subdirectory. CD\dir reported "Invalid directory". The drive I: was mapped to server/mac ( I:=server/mac: ). This is a problem I found elsewhere also before changing the login script to run the external MAP command. If I mapped a drive to the root of a volume (using LOGIN's internal MAP command), then I seemed to lose filescan rights to the subdirs. If I mapped a drive to a subdir of a volume, I then had all the proper filesan rights to the root and its subdirs. >One windows program, CaLANdar by Microsystems, doesn't get along >well with the Client 32. It runs from M:\CAL. When I try to >run it, it flashes on the screen for an instant, and then >my screen gets knocked back into text mode, and there is an error >message on the screen which says "NIOSWIN.NLM did not properly >free 1 resource." The PC is locked up at this point and I have >to hit the power switch to reboot. This program uses MHS to >deliver its files, and uses the MV variable which is set to >MV=560SERVER-1/SYS:\ . Does Client 32 recognize this, or does >it need UNC? The DOS version of CaLANdar worked OK, so I don't think UNC has anything to do with this problem. I've sent a message to Microsystems to find out if the windows version is making somekind of netwarecall when it starts up. >Reinstalled the client 32 software using the 16bit driver >EPROODI.COM (36992,11-10-95), but had the same problems. > >Could this be a problem just with the Intel cards or drivers? I >have an SMC card around here somewhere that I will swap into my >system to run some more tests with. Installed an SMC Elite 16T (8013WC) card, reinstalled the client 32, but had the same problems. >Anyone having similar problems? Also, I retried the IBM anitvirus after changing to external MAP commands in the LOGIN script. It still locks up on the AFTERLAN portion. (This is the part of IBM AV which checks its version against what is installed on the server directory). ------------------------------ Date: Mon, 15 Apr 1996 08:50:28 +1100 From: Richard Phillips Subject: Re: Is it just me? -- C32 4 DOS/Win Beta >Is it just me or is this a great product? > >- 30-100 KB less "lower 1MB" RAM usage...your mileage may... > >- fast (at times) thanks to cool *network* caching > >- painless to install > >Sure its buggy, but I have renewed faith in Novell's >ability to innovate and _improve_ their main product. Yup. I agree! I'm currently using an Intel pro100b card running at 100meg, am using the standard 4.1 server e100b.lan driver, and it goes like a scalded thing. Couple of minor hassles with installation, but nothing major. I've also had a couple of lock ups, but not sure if I can blame the client yet - heck it's still dos/windows..... The loader (nios.exe) puts itself (automatically) into upper memory of which it uses about 3k, and everything else appears to be loaded into extended memory - including tcpip. 8-O ------------------------------ Date: Mon, 15 Apr 1996 08:30:42 -0800 From: Mark Schoonover Subject: Re: Client32 lockups David: Similar, yes and no. I had a problem that caused capture, the version from Netware 4.1, to lock the PC up while running any login script, and even running it at the dos prompt. Version that shipped with 3.12 ran just fine. This particular PC had a 1GB HD that required one of those little sector translator programs so DOS could see all 1GB. I installed another sector translator type program from MicroHouse and all has been fine. The version I removed was from Conner itself. Not sure why this was causing the problem, but all I can figure is that either login.exe or capture.exe was stomping that area of memory. ------------------------------ Date: Mon, 15 Apr 1996 17:00:35 +0100 From: Richard Letts Subject: Re: Is it just me? -- C32 4 DOS/Win Beta Phil Randal wrote.... >Another strange quirk I've found is client32.nlm not finding the >network when loaded. Unload and reload and it attaches. Or delay 2 >seconds before loading client32.nlm and it attaches properly. This >is on a segment running NLSP routing only. LAN driver is the Intel >EtherExpress Pro 10 EPRO.LAN driver. Workstation is a DX4/100 PC. [I'm an official beta-tester for this stuff, and have been for months] the IPX stack resolves the IPX network numbers before the client32 driver loads; It appears to bind to multiple frame-types, allowing a workstation to be multi-homed. it may be that the workstation is having difficulty determining the network numbers before the client32.nlm loads. It may be that the RIP part of the NLSP router needs waking up, or is sluggish in responding when IPX loads. [this is not a generic RIP broadcast, but a route-request rip broadcast to discover routers; I don't recall a similar mechanism being discussed for NLSP, indeed the NLSP designers envisaged this mode of RIP/SAp would be around forever from thier slides at this year's brainshare] ------------------------------ Date: Mon, 15 Apr 1996 15:39:04 EDT From: Mark Yount Subject: Client 32 for DOS/WIN Problems noted: 1. Under the old NETWARE.DRV, you could add to the [Netware] section of the SYSTEM.INI a line NWShareHandles=False to control the sharing of drive handles between virtual DOS sessions in enhanced mode. In my case, I do not want drive handles shared. The client 32 has that option in the setup box of NWUSER, but I am unable to check or uncheck the box, and the default appears to be shared. Will this be corrected? 2. After installing the Client 32 files and running windows, I am getting strange behavior with Adobe type manager. As ATMSYS.DRV loads, it is attempting to copy ATM16.NDL to the windows system directory. I get an error message from ATMSYS.DRV to that effect. Apparently, it erases the old file first before the copy, because the ATM16.DLL is gone the next time I start windows. The end result is that ATMSYS.DRV fails to load, and programs that require ATM such as ACROREAD fail to run. The attempt to copy ATM16.NDL did not happen before I installed Client 32. The source is not available, and the copy should fail if it was attempted, but there were never any such error messages. Any ideas? ------------------------------ Date: Tue, 16 Apr 1996 08:40:49 EDT From: Mark Yount Subject: Client 32 for DOS/Win and cc:Mail NFT error I just had a case of file corruption with my USR file on cc:Mail. Reading what the FILE CACHE LEVEL parameter defaulting to 3 means, I suspect that the algorithm that determines if a file has been changed on the server was fooled by cc:Mail, maybe because the router was updating the file just as Client 32 was writing out recent changes from deleting a message from a folder. This caused an NFT error and a folder message error. Both were luckily correctable without going to a backup. I suspect that this will be a tough, if not impossible logic fix, since a CRC type of check would be the only truely reliable check, and to compute a CRC would probably kill any cache performance gains. I have changed the FILE CACHE LEVEL to 1 in the meantime and will suffer whatever performance loss that change means. ------------------------------ Date: Tue, 16 Apr 1996 12:50:25 EDT From: Mark Yount Subject: Re: New *.DLL's with Client 32 for DOS/WIN Someone suggested that I try this To do these tests, I copied all the Client 32 windows files to a new directory that I inserted first on the search path. The list included these files that already existed in my windows SYSTEM directory on the LAN: VNETWARE.386 NWCALLS.DLL NWGDI.DLL NWIPXSPX.DLL NWLOCALE.DLL NWNET.DLL NWPSRV.DLL TLI_SPX.DLL TLI_WIN.DLL WINSOCK.DLL WLIBSOCK.DLL NETWARE.DRV NWPOPUP.EXE NWUSER.EXE plus all the new windows files unique to Client 32. I run Windows 3.1 with LWP 4.2 for TCPIP, so I installed the Client 32 TCPIP stack. In my AUTOEXEC.BAT, I called either the new STARTNET.BAT installed by Client 32 or my original STARTNET.BAT for my VLM configuration, both in separate directories. Neither the VLM or Client directories were on the path. NOTE: AN INSTALL HEADS UP The Client 32 install program did not handle frame types correctly. I am a Token Ring shop and the old NET.CFG used TOKEN-RING for IPX and TOKEN-RING_SNAP for TCP/IP. The STARTNET.BAT file created by install only loaded the LAN ODI driver once with no frame type specified, it defaulted to TOKEN-RING_SNAP so TCP/IP worked but no servers were found. THE RESULTS: In my limited testing, EVERYTHING worked under both setups (even the new NETWARE.DRV) EXCEPT for WINSOCK.DLL. WINSOCK.DLL was the ONLY common file that I had to load from the LWP directory under VLM's and from my new test files directory under Client 32. Since WINSOCK.DLL is loaded indirectly, the only way I have of loading the correct file is the path statement, which means another search drive and another drive letter down the drain. Any other ideas would be appreciated. Some of the new features of NWUSER.EXE, such as the search drive mappings, shouldn't work under VLM's, so I didn't try them. Probably to be safe, the VLM NETWARE.DRV probably ought to still be used to avoid troubles. Giving the path to the different files on the netware.drv line in the SYSTEM.INI is all that is needed to make this work. ------------------------------ Date: Wed, 17 Apr 1996 12:43:21 +0100 From: Phil Randal Subject: Re: NW Client 32 for DOS/Win...bugs... On 16 Apr 96 at 13:28, Floyd Maxwell wrote: > ...NVC32DW.DOC is in progress... Great. Another funny: NPRINT now comes up with a queue error 0002 - works fine under VLMs. ------------------------------ Date: Wed, 17 Apr 1996 08:06:22 -0400 From: "David P. Moon" Subject: Re: Client32 lockups On 15 Apr 96 at 8:30, Mark Schoonover wrote: > Similar, yes and no. I had a problem that caused capture, the >version from Netware 4.1, to lock the PC up while running any login >script, and even running it at the dos prompt. Version that shipped >with 3.12 ran just fine. This particular PC had a 1GB HD that required >one of those little sector translator programs so DOS could see all >1GB. I installed another sector translator type program from >MicroHouse and all has been fine. The version I removed was from >Conner itself. Not sure why this was causing the problem, but all I >can figure is that either login.exe or capture.exe was stomping that >area of memory. I have a 720MB HD on an enhanced IDE controller (Phoenix BIOS), so I don't have a sector translator program running. I am loading a IDE drive accelerator program (CMD PCI-640X IDE driver V2.07 M1). I remarked this program out of the CONFIG.SYS and SYSTEM.INI files, and reloaded CLIENT 32. Things ran noticably slower, and I still had the same problems with CAPTURE, drive mappings, and CaLANdar. If sector translation is the cause, then it is a problem in my Phoenix BIOS. Ouch. This is with the "as installed" Client 32 settings. I haven't tried manually optimizing anything yet. ------------------------------ Date: Wed, 17 Apr 1996 09:06:38 EDT From: "Andrew J. Scott" Subject: Re: Client 32 for DOS/Win and Adobe ATM On 16 Apr 96 at 17:07, Mark Yount wrote: >Client 32 is apparently blocking whatever check ATMSYS.DRV is doing to see if >this is the first execution after a new install, and is forcing ATMSYS.DRV to >think every time windows starts it is a first time install of ATM. > >Has anyone been successful in installing/running ATM under Client 32? Haven't tried that, but you might try setting "file cache level 0" and "pb buffers = 0" in the net.cfg file. I've found, so far at least, that turning these features off fix several problems. ------------------------------ Date: Thu, 18 Apr 1996 07:50:00 -0400 From: Rick Troha Subject: Re: Novell CLient 32 for Win/Dos driver >Does anybody know where you can find the Novell Client 32 for DOS/Win >3.1x open beta driver for the 3Com 3c5x9 16bit ISA network card ? >It doesn't seem to be supplied with the Client 32. Look on the diskette that came with your NIC. Client 32 uses the same *.lan driver as your server, in your case 3C5X9.LAN. ------------------------------ Date: Thu, 18 Apr 1996 08:11:09 -0500 From: George Cohen Subject: Re: Novell CLient 32 for Win/Dos driver >>Does anybody know where you can find the Novell Client 32 for DOS/Win >>3.1x open beta driver for the 3Com 3c5x9 16bit ISA network card ? >>It doesn't seem to be supplied with the Client 32. > >Look on the diskette that came with your NIC. Client 32 uses the same >*.lan driver as your server, in your case 3C5X9.LAN. This is correct. I have tried the Client 32 / DOS / Windows and it does work with the 3c5x9. using the server driver. It was realy impresive but I did have a problem with Microsoft office products. If I loaded any of these from the server, I got a complete lockup, and even a black screen of death.... (netware 3.12 server) I have since stop using the Beta Client until it goes through more testing. Has anyone else seen this problem?? ------------------------------ Date: Thu, 18 Apr 1996 16:29:21 EDT From: Scott Smith Subject: Re: Client 32 lockups - Part 2 >>>On 12 Apr 96 at 16:34, David P. Moon wrote:[snip] >>>> Novell Netware 3.11 Servers, with Netware Name Services.[snip] >>>But when I opened a DOS window, and browsed >>>through the drives, I found one drive which wouldn't allow me to >>>list any of its subdirectories. The RIGHTS command showed me as >>>having RF rights to the drive, and RWCEMF rights to the subdirectory. >>>CD\dir reported "Invalid directory". >> >>There is a patch required for NW3.11 servers to fix this specific >>problem. I believe it is included with the Client32 distribution (we had >>to load it on a couple of servers when we started our pilot of Client32). > >I found some patches located in \ADMIN\PATCHES\NW311 (of DW32NA.EXE): > > OS2OPNFX NLM 1,385 12-19-95 4:52p > PATCHMAN NLM 15,591 01-22-96 11:22a > SHORTAFX NLM 1,010 04-05-95 11:41a > >but I can't find any references in the text files, or the >windows Client 32 help, which explains what these are for. >Anyone know their purpose? or can you point me to the documentation. I know that a similar problem was happening with the Client32 for Win95, and that loading the three NLM's above onto your 3.11 server would solve the problem. Remember that PATCHMAN should be loaded before the other two, as it manages the patches to the OS. ------------------------------ Date: Fri, 19 Apr 1996 21:40:16 +1000 From: "Michael Mollard" To: netw4-l@bgu.edu, CL32dw@novell.com Subject: Client32 DosWin: Map del error? With Client32 Dos/Win installed ... When I log in (DOS), the login script MAP ROOT D:=(a network 'home directory). I'm one of the few people who have a phisical (Local) Drive C: and D:. All is fine, until I try and MAP DEL D:. If I'm currently logged to D: and try to MAP DEL D:, the system loses the plot and seems to generate a couple of PrintScreen Keystrokes, sending my printer into hysterics. Reboot is the only option. If I'm logged to another drive and try to MAP DEL D:, it throws a couple of Runtime errors and locks up (again, reboot is the only out). ------------------------------ Date: Fri, 19 Apr 1996 09:14:40 +0100 From: Phil Randal Subject: Re: Client32 / Groupwise DOS showstopper On 18 Apr 96 at 20:39, Jerry White wrote: >When I start Groupwise for DOS (OF.EXE) under C32, I get the following >message: "NIOS-201-85. The 32-bit Netware client does not support task >switching." When I start Windows after the error message, my system >freezes. > >If I try running this program from a DOS prompt within Windows, it gets a >little farther. OF says "Windows detected, task switching API disabled." >Then the system freezes. > >Any ideas about how to disable task switching in GW-DOS, or enable >task switching in C32? From the readme.txt file in the client32 directory: 4.1 GroupWise for DOS To run GroupWise for DOS, disable the DOS task-switching support by using the /da command line switch. NetWare Client 32 for DOS and Windows 3.1x does not support task-switchers. ------------------------------ Date: Sat, 20 Apr 1996 08:26:16 -0700 From: Randy Grein To: "NetWare 4 list" Subject: Re: TCP/IP and Windows95 >We have a situation where we need to run a TCP/IP stack on several >PC's which run Windows 95 locally and connect to our Novell 4.1 >network using Novell Client 32. The Win95 built-in TCP/IP apparently >won't work with the Client 32, so are there any suggestions as to >which TCP/IP stack I should configure? Does Novell offer a free >TCP/IP stack? And if so, can it work with the VLM client also? Others have stated correctly that Novell's client/32 runs with the MS TCP stack; if you need VLM support you can either use the free update for WFW 3.11 from MS or get the latest update to the VLMs off the website - the 6th disk contains Novell's TCP stack and an OK winsock, but no utilities. ------------------------------ Date: Mon, 22 Apr 1996 09:44:04 -0600 From: Joe Doupnik Subject: Re: Client 32 >Has anyone figured out how to fine tune memory for the new client 32 > >Although it's quicker it seems to be at the expense of about 4mb of >extended memory ! ------- Quicker than ?? Net.cfg, Netware DOS Requester section, add line file cache level = 0 to turn off using 1/4 of your machine's memory for caching. 4 milli-bits of memory isn't much to give up, but 4MB is. With the above 0 about 2MB of memory will be consumed, or that's what I see on my machine. Joe D. ------------------------------ Date: Mon, 22 Apr 1996 15:33:10 -0400 From: "David P. Moon" Subject: FYI. Client 32 Update File FYI, Haven't seen it mentioned here yet, but there is a new patch file for Client 32 DOS/WIN at ftp://ftp.novell.com/pub/updates/nwos/cl32dwob/dw32p1.exe dw32p1.exe: 239430 bytes OPEN BETA Client 32 for DOS/Win File Updates -- 4-12-96/20:14p The file, DW32Px.EXE contains the latest file updates for the OPEN BETA release of Client 32 for DOS/Windows 3.1x. ------------------------------ Date: Tue, 23 Apr 1996 18:07:33 +0100 From: Richard Letts Subject: Re: DOS client32 & trumpet winsock >Is there any way I can get rid of trumpet winsock without buying >another product? There is a winsock.dll in the client32 distribution. >Can I use that instead? Yes, there is a TCPIP.NLM and a WINSOCK.DLL in the client32 kit. In fact, I'm using it as I type this to you. It supports RARP, BOOTP and DHCP for configuration; the install process doesn't tell you this, and I've sent a note to the dev. team saying install options for this stuff would be neat. The *BEST* thing about it is TCPIP under DOS requires no more memory below 640k than NIOS itself requires. It's compatible with LAN Workplace for DOS apps too. ------------------------------ Date: Tue, 23 Apr 1996 12:08:08 -0600 From: Joe Doupnik Subject: Re: Windows95 and Longer File Names >When you started using Windows95, what kind of effect did using longer >file names have on your fileserver drive space? ----- First off, long filenames are not required. Yes, we hear all the hyperbole on the subject but they are not required. How can I say that? Because I have had Win95 running in production mode on a NW 3.12 file server since last July. Even MS Office 95 does not require them. See my notes on both in directory misc on netlab2.usu.edu. Adding name spaces dilutes your directory cache buffering effect. Same buffers divided by name spaces equals effective directory caching. It also makes backup/restores a real problem unless you have high quality backup software. It makes admin worse, but you will see that first hand if you try. It isolates those files to programs which are prepared to deal with long filenames, which means very very few. Joe D. ------------------------------ Date: Tue, 23 Apr 1996 21:48:12 -0600 From: "Mike Avery" To: netw4-l@bgu.edu Subject: Re: problem with novell win95 NetWare client >I have one user who is testing out the Novell Win95 NetWare client >for me. His biggest complaint is that when the login script runs, he >has to keep closing windows, not only for the login script itself, >but for all the DOS commands imbedded in the script. There is a function in the advanced features for the NetWare shells, controlling the login behavior that says "close window on exit" or some such thing. Check the box. When that doesn't work, right click the upper left corner of the program windows that won't go away, click on properties, and then put an "X" in the box that says "Close on Exit" next to it. It's a hassle, but it's a one time hassle. ------------------------------ Date: Wed, 24 Apr 1996 08:27:45 -0700 From: Emerson Tripoli To: netw4-l@bgu.edu Subject: Re: problem with novell win95 NetWare client To make login results automatically close Here's the step-by-step to automatically close the Login Results window: 1. Go to the control panel 2. Open "Network" 3. Click on "Novell NetWare Client32", then click "Properties" 4. Click on the "Login" tab. 5. Click on the radio box for "Display Script Page" to turn it on. 6. Click on the radio box for "Clear Script Results" to turn it on. 7. Click the radio box for "Display Script Page" again to turn it off. 8. Close both the windows, and restart. The reason for turning the "Display Script Page" back off, is that it puts another tab, unnecessary for most user, on the NetWare32 login window. As for why his getting the item in the taskbar, it might just be that Win95 'forgot' about removing it. If it's any consolation, none of our Win95 machines here have ever done that, and we have some pretty wierd things happen. ------------------------------ Date: Mon, 6 May 1996 11:53:59 -0400 From: Rob Albertson Subject: Client32 and Nios: problem resolved! Well, I figured out my problem with the Client32 and the inability to initialize the NIOS: device upon startup of Windows. Everyone who posted suggestions dealing with a possible memory problem were pretty much correct. However, it was not a particular exclusion or inclusion that was the problem. The problem was that on my EMM386.EXE command in config.sys I had the parameter HIGHSCAN. I removed that parameter, and everything worked fine! It's amazing what one little word can do! I wish to thank everybody who posted suggestions, and especially Joe D. for his efforts to help me through private E-mail. ------------------------------ Date: Sun, 12 May 1996 16:07:42 +0100 From: Richard Letts Subject: Re: remote booting & client32 Client32 does not currently support remote booting; the ipx.nlm initialises the card becore client32.nlm can load, with the result that drvieA: is still the boot image. ------------------------------ Date: Mon, 20 May 1996 14:40:33 +-200 From: "J.C. Vader" Subject: Re: Netware Application Launcher & the New Client32 >Has anyone had a fiddle with the Client32 kit. I have installed it and found no problems with the installation >We got it to work, and found the NAL (Netware Application Launcher). >This little tool promisies to run applications which are part of the NDS. In the NDS you can make an entry in which you store command-line- parameters and other stuff related to the application. >The NAL is supposed to 'snap-in' to NWAdmin, which you then use to >create >an application object. yes >The NAL can then be used as a replacement for Program Manager from >which >to run you're networked applications. In windows95 you run the program NALw95.exe this program checks the NDS to see which programs you have rights to. It opens a folder in which the programs are showed. I assume it works the same with windows 3.x. >It also talks of the NAM (Netware Application Manager). This is the snapin in NWADMIN >My question is has anyone got any info on this, and how you get it to >work? Place the software in the directory in which NWADMIN stays. Edit the nwadmin.ini (the one you use!!) en place an entry under [Snapin Object DLL] which states NAM=drive:directory\appsnap.dll The first time you start NWADMIN it alters the schema. Now you can add an application object. Make sure the user has enough rights and you can start the NAL. You can find more detailed info in the appsnap.hlp which is included with the program. ------------------------------ Date: Wed, 29 May 1996 09:03:58 -0700 From: Floyd Maxwell To: netw4-l@bgu.edu Subject: Re: Client32 for DOS >I'm reading a lot about Client32 for Win95. I'm curious if anyone >is trialling Client32 for Dos/Win, and if anyone knows how the updates >and patches are coming along? Is anyone having major problems or >wonderful successes with it? We (the computer dept.) are trialing it. Saves a ton of memory. Is faster or the same speed, never slower. Easy to install, no configuration needed yet. Gained so much base memory on my machine that I removed DOS EMM386 -- thus gaining 10 or 15% performance boost by not having to switch from real to protected mode and back dozens of times per second. There have been 3 updates, first 2 addressing the same issue -- poor freeing up of 1 resource when quitting Windows. Pretty benign problem, really, but it will be nice when it is finally resolved. See my .SIG for the ftp & http addresses of 1 of 18 FAQ sites. Then see Section S.59 (NVCL32DW.DOC) that has logged all significant posts on the subject. --------- Date: Thu, 30 May 1996 10:11:47 GMT+1000 From: "Andrew Gray" Subject: Re: Client32 for DOS I've set it up and it works, but .... It's not stable enough for me to put out to my users. What I really like is the GUI login script processing from inside windows, the built in TCP support using either BootP or DHCP for lookup, the price, the fact that you can add search drives from the windows nwuser program. When they get it right, I put it out for general use. We run mixed 3.11/3.12/4.1 server environment with IPX and TCP mainly. Can anyone tell me how to bind the IPX protocol to a specific frame type? The only way I got it to work was to delete every frame type except Ethernet_II, so it defaulted to this. When you add another frame (Ethernet_802.3) IPX and TCP both bind to this and only IPX works (as far as I can tell anyway). The net.cfg file below works as long as only one (Ethernet_II) frame type is loaded in the startnet.bat file. * Link Driver CNE2000 *;NOTE: 32 Bit driver settings are found in STARTNET.BAT *;This section does not reflect 32 bit settings. *;The values in this section are the 16 bit values from the old *net.cfg. * ISA * INT=C * PORT=2C0 * FRAME=Ethernet_II * RETRIES= 5 * *PROTOCOL TCPIP * PATH TCP_CFG C:\NOVELL\CLIENT32\TCP * IP_ROUTER 141.132.64.2 * IP_NETMASK 255.255.224.0 * IP_ADDRESS 0.0.0.0 * IP_BROADCAST 141.132.95.255 * INSTALL TCPIP=TRUE * * IF_CONFIGURATION BOOTP * BIND CNE2000 #1 Ethernet_II *# NET BIND Ethernet_II CNE2000 #1 * *Link Support * Mempool 4096 * Buffers 16 1600 *# *Netware DOS Requester * IPX Sockets=60 * cache buffers=16 * print header=255 * print tail=255 * spx abort timeout=2000 * * preferred tree = UNIVERSITY OF BALLARAT * spx=60 * long machine type=v622 * get local target stacks=5 * show dots=on * file handles = 150 * Search Mode = 5 * * First network drive = F * Force First Network drive = ON * name context = "O=UoB" * Netware Protocol = nds,bind * Auto Reconnect = ON * Bind Reconnect = ON * Auto Retry = 0 * message timeout = 200 * * Use Defaults = ON * vlm=wssnmp.vlm * vlm=wstrap.vlm * vlm=wsreg.vlm * vlm=wsasn1.vlm * vlm= mib2if.vlm * vlm=wsdrvprn.vlm --------- Date: Thu, 30 May 1996 16:30:34 -0400 From: PowrTekSys@aol.com (Kevin C. McIntosh) Subject: Re: Client32 for DOS >I'm reading a lot about Client32 for Win95. I'm curious if anyone is >trialling Client32 for Dos/Win, and if anyone knows how the updates >and patches are coming along? Is anyone having major problems or >wonderful successes with it? The May issue of Application Notes is dedicated to it. I'm running it on two test machines with no problems, yet. Remember, it is an OPEN BETA and there is already a patch out. [Floyd: 3 patches at this writing] The Automated Client update (ACU) is pretty neat. I'd copy in a previously configured NETWARE.INI, after the ACU install runs. I haven't figured out how to setup "Launch login at Startup" through the ACU. If anyone knows how, please share. ------------------------------ Date: Sun, 2 Jun 1996 12:35:22 -0400 From: "David P. Moon" Subject: Client32 DOS/WINDOWS status? Anyone know what the current status is of the Client32 for DOS/Windows? Hasn't been any new info on the web page for quite a while. After applying the undocumented patches in \ADMIN\PATCHES\NW311 and DW32P2.EXE, most of my problems have been solved. It even works with my Netware Name Services! (provided I login from DOS). My only remaining problems are: 1. My Pegasus Email Folders become corrupted on the server. I've tried various settings for FILE CACHE LEVEL, but the only setting that reliably corrects my problem is turning on TRUE COMMIT (which slows things down). 2. Client32 gets confused when running APPMETER protected programs on the server. APPMETER uses a stub file by the same name as the executable file, but in a separate directory. When you run the stub file, APPMETER checks for available licenses, grants you rights to the actual executable in its program directory, and then executes it. This will fail 50% of the time with a "segment load failure" or an "application error". But if I hit OK on the error message and rerun the program, it will usually come up OK the second time. ------------------------------ Date: Wed, 5 Jun 1996 09:27:42 -0600 From: Joe Doupnik Subject: Re: Remote-booting Client32? >Has anyone successfully remote-booted with Client32? > >I am currently remote-booting Windows 95 with the VLMs. >But to get long filename support, it seems the only way >with Novell clients is with Client32. > >I have Client32 on a standalone Windows 95 system but I can't >see how to remote-boot it. I would be grateful for any >help from anyone who has tried this. ----------- At this time Client32 does not support remote-booting (RPL). It is a very messy problem. But don't give up hope for a solution. In the meanwhile I recommend using VLMs, and I constantly recommend not using long filenames (creates islands of incompatibility). Joe D. ------------------------------ Date: Fri, 7 Jun 1996 11:51:00 EDT From: "Webster, Ronald G." Subject: [Solved]Win95 Client32 Error while initializing device NIOS >>When installing Novell Client32 on a users computer with Win95. I received >>the following error >>"While initializing device NIOS. Windows protection error. You need to >>restart your computer." I received several replys both on list and off. Most pointed to memory errors dealing with emm386.exe. On person (Lisa Reeves) suggested checking out the BIOS version. I did and the machine giving the problem had an old BIOS. I downloaded the new BIOS from IBM and installed it and that fixed the problem. It seems that there are more than one way to cause this error. Thanks to all who replied. ------------------------------ Date: Thu, 20 Jun 1996 16:18:58 -0400 From: "Mitchell, Luke" Subject: Client32 beta In the past few weeks, there have been many questions about TCPIP.NLM and Novell's 32 bit client that is currently in beta. Here are excerpts from Novell's Frequently Asked Questions document regarding TCP/IP and Client 32 for Dos/WIN (Open Beta). The full FAQ is at: http://netwire.novell.com/servsup/tidhtml/nwos/cl32dwob/2906517.htm Q: Where do I get a copy of the Novell Client-32 software? A: The Client-32 package is now available in Open Beta format. Point your web browser at: http://netwire.novell.com/home/client/ Q: Will the TCP/IP protocol stack be free of charge in the final version of Client 32? A: Yes. Q: Will TCP/IP for Client 32 be available for free after the date of July 4, 1996? A: Yes. Q: Does the PING.EXE program shipped with LAN WorkPlace 5 work with Client-32 TCPIP.NLM? A: No. You will need to get the TCP16.EXE patch from http://netwire.novell.com/home/lwp/flup.htm and use the PING.EXE and PING.MSG found there. ------------------------------ Date: Thu, 20 Jun 1996 19:14:32 -0600 From: Joe Doupnik Subject: Re: VLM vs Client 32 > What are the pros and cons of using VLM or Client 32 at the >workstation in a 4.1 network? ----------- Picking one of your five leading questions. Client32 is where the company is going: one set of drivers for all platforms and thus less driver writing. It is also protected mode and thus fits in snuggly with that icon business. VLMs are still highly effective, and let real mode applications run with least overhead. They work with DOS, Win3.1 and Win95. Client32 for DOS/Win3.1 has a real-mode attachment point permitting regular LSL to be visible and available for real-mode applications. But that costs some memory and a noticable amount of performance. If you wish to remote boot client machines then at this time VLMs are the only answer, though it is possible to finesse Client32/DOS to work too. Win95 folks have VLMs at this time for remote booting (and I show how to accomplish the feat); diskful clients can use either VLMS or Client32/Win95. Performance overall can be important, and live on-site testing is recommended to see what happens on your particular hardware. On mine VLMs are markedly faster than any Client32 material. Memory consumption is another issue, and that depends on the base o/s employed as well as whether or not decent memory management software is applied. Client32 wants to cache locally and intelligently, at a default cost of 1/4 of your machine's memory. Cache size and availability are controllable to suit local tastes, and you should pay attention to server side interactions with essentially locked-files on the server while being cached on clients. Client32 can operate over protected mode or real mode ODI drivers because the NCP component is separable from the ODI part. Mixing and matching typically costs memory and performance, and a login headache if not in Windows from the beginning. Client32 is young technology. The DOS/Win3.1 version is still in open beta but near release. Normally such major advances take a year or more to become mature. Thus you have a risk factor to include. I've run them all extensively. Joe D. ------------------------------ Date: Thu, 20 Jun 1996 21:28:38 -0600 From: Joe Doupnik Subject: Re: Win95 & Client 32 >I have a question for y'all. We are running a Novell 3.12 >network. I have Windows 95 running, and have the Netware >Client 32 installed. We have several lines in the system login >script that look something like this: > >#COMMAND /C IF NOT EXIST K:\EXCEL MD K:\EXCEL > NUL > >That checks to see if there is an EXCEL directory on the user's K: >drive (which is their personal, or users drive). If the directory >doesn't exist, the system login script creates it. > >What I'm running in to (and it's not really a "problem", per se, >it's just annoying) is that when I login, and the system login >script gets to this section (there are probably 10-15 lines like >the above...for different applications), the screen flashes to a >black screen, like it is jumping to DOS for a second. It does this on >every line like that. Does anyone know WHY it does this? Or, better >yet, what I can do to make it stop? We are going to be upgrading >several computers to Win95 eventually, and this kind of thing would >freak some of our users out. Hehehehe, what can I say, some of them >just aren't that bright! > >Is there a fix for this? I installed what I believe to be the latest >Client 32 patch, but I'm not entirely sure. Any help would be GREATLY >appreciated! TIA!!! --------- Well, the answer is right there in front of us, by construction as they say. What does "command /c blah" mean? It means run COMMAND.COM with blah as the command apparently typed (/c) at the keyboard. Command.com means DOS. Win95 really runs over/with DOS 7, so you get DOS 7 Command.com invoked and the screen follows along; it invokes the DOS box. As you said, it is jumping to DOS. A suggestion is "if it hurts don't do that"(tm). Try another tact, such as running a DOS program yourself which creates the needed directories one fine day, or maybe let the users manage their areas, or similar. Another is point the application shortcut icon to a DOS .BAT file, in which you do the test/mkdir and also run the Windows program. Oh, you say? So how in the heck does one run a Windows program from a DOS .BAT file (which itself is running in a DOS box)? Simple, I reply smoothly; invoke the Windows program this way in that .BAT file: START /W windows-program-name command-line-arguments Please see my Win95 NW installation draft document, binary file w95inst7.zip in directory misc on netlab2.usu.edu. Also, it's better to avoid drive letters and use volume names when possible in scripts to provide more freedom for variation on clients. Joe D. ------------------------------ Date: Thu, 27 Jun 1996 07:23:59 -0400 From: Rick Troha Subject: Final Release of Client 32 for Dos/Win available The final release of Client 32 for Dos/Win is now available. See directory /pub/updates/nwos/cl32dw21 at ftp.novell.com (and, I presume, its mirrors). ------------------------------ Date: Tue, 2 Jul 1996 10:24:40 +0100 From: Eric Hall Subject: Re: client32 and rconsole (windows95) >I am running Novell's client32 on Windows95 workstations and rconsole >no longer works. It worked when I initially installed it and now I get >error messages stating that an SPX connection problem occured. Turn off auto-detect frame-type, and explicitly provide the one that you use. If that doesn't work, re-install the client32 stuff. ------------------------------ Date: Wed, 3 Jul 1996 10:25:01 -0600 From: Joe Doupnik Subject: Re: NETWARE CLIENT 32 FOR DOS & WINDOWS 3.x & LAT >Has anyone been able to run the Meridian SuperLAT driver with the netware >client 32 for DOS and Windows 3.x? When I try to load slatsp3.exe it >complains that it can't find the network manager. I have been loading the 32 >bit NIC driver but I don't think this makes any difference. It would be very >nice for us if I could make it all work - unfortunately there are >applications here that we have to access using LAT. ---------- Works here, using it with MS-DOS Kermit to write this message. Likely problems at your end: Net.cfg does not have section Protocol LATDRVR bind #1 where 1 is to be replaced with the logical board number using frame Ethernet_II. or Net.cfg does not have indented line Protocol LAT 6004 Ethernet_II within the Link Driver section or Real mode ODI shim pdoseth and the lsl aren't loaded (32 bit lan driver flavor of Client32). Joe D. ------------------------------ Date: Tue, 9 Jul 1996 03:43:16 -0400 From: Rob Waterlander Subject: Re: Client32 DOS won't run windows! >Now I've hit a problem. I have about 30 IBM PS-VP's 486-SX 25 >machines with 4Mb ram, and IBM NE2000 clone T/P ethernet cards. > >They are in more need of client32 than most, but when I install it >and go to run windows I get a nice red message saying "The 32 bit >netware client doesn't support task switchers" and it returns to >DOS. > >I've tried with both the DOS & windows install with the same result. This happens when your workstations starts Windows in standard mode instead of enhanced mode. Have a look at your workstation memory. Maybe they use something like smartdrive or maybe you have configured the Client32 with a lot of cache memory, which consumes XMS memory and therefore Windows forcing to launch in standard mode. --------- Date: Wed, 10 Jul 1996 09:18:44 -0700 From: Floyd Maxwell Subject: Re: Client32 DOS won't run windows! >You're spot on with this. I was using the TCPIP.NLM as well which >made things about 200k worse. Looks like I can't have client32 & >TCP/IP on 4Mb machines. You can disable caching...with a "0" to 6MB machine this will save 384KB...might make the difference. ------------------------------ Date: Thu, 11 Jul 1996 12:37:27 -0500 From: Paul Rhoads Subject: Re: Client32 for DOS/Win & nprint >I have a Dell Dimension XPS P133c running DOS 6.2, Windows 3.1 and the >latest version of Client 32 for DOS/Win. This machine has a CD rom drive. >When she tries to do an nprint from a DOS window (or from DOS - completely >out of windows), she gets an error message as it tries to read from her >D: drive ( CD ). The error is b/c there is no CD in the drive. I took this from the documentation on the internet about 32DOS/Win. The document ID is 2909379 . This may be the solution.... 4.5 CD-ROM Drivers MSCDEX.EXE must be loaded before NetWare Client 32 for DOS and Windows 3.1x. If you have a CD-ROM drive and are experiencing problems with the NetWare Client, ensure that the statement to load MSCDEX.EXE comes before the call to STARTNET.BAT in your AUTOEXEC.BAT file. ------------------------------ Date: Tue, 16 Jul 1996 09:58:58 +0100 From: "David W. Hanson" Subject: Re: Client32 DOS/Windows - Can't See Server >If someone else has a 3COM 3c5x9 board, and has Client32 DOS/WIN working, >please let me look at your net.cfg, and startnet.bat files. Thanks!! This appears to work for me... NET.CFG ------- Link Driver 3C5x9 ;NOTE: 32 Bit driver settings are found in STARTNET.BAT ;This section does not reflect 32 bit settings. ;The values in this section are the 16 bit values from the old net.cfg. INT 10 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 Link Support MAX STACKS 8 BUFFERS 16 1514 MEMPOOL 6144 NetWare DOS Requester FIRST NETWORK DRIVE = F SHORT MACHINE TYPE = IBM LONG MACHINE TYPE = AST Print Header = 85 Print Tail = 85 Netware Protocol = NDS BIND Preferred Server = DANCER Load Low Conn = On Load Conn Table Low = On Bind Reconnect = On Connections = 8 Average Name Length = 16 Max Tasks = 64 Checksum = 0 Signature Level = 0 Message Timeout = 540 Message Level = 2 Cache Buffers = 10 Cache Writes = Off ; Pb Buffers = 0 Pb Buffers = 1 Pburst Write Window Size= 32 Pburst Read Window Size = 32 True Commit = Off Local Printers = 1 Network Printers = 4 Print Buffer Size = 64 Read Only Compatibility = Off Show Dots = On Protocol IPXODI Bind 3C5x9 Ipx Sockets = 40 PROTOCOL TCPIP PATH TCP_CFG J:\tcp IP_ADDRESS xx.xx.xx.xx IP_ROUTER xx.xx.xx.xx IP_NETMASK 255.255.255.240 path lwp_cfg J:\hstacc path script J:\script path profile J:\profile tcp_window 16384 NIOS LINE DRAW CHARS = "U?AU3AE" STARTNET.BAT ------------ @ECHO OFF C: CD \NWCLIENT 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\3C5X9.LAN FRAME=Ethernet_II ISA PORT=300 IDPORT=110 : Next line was moved to autoexec.bat so that LWG would work. : (ie., not logged in yet!) : LOAD C:\NOVELL\CLIENT32\TCPIP.NLM LOAD C:\NOVELL\CLIENT32\IPX.NLM LOAD C:\NOVELL\CLIENT32\CLIENT32.NLM CD \ ------------------------------ Date: Wed, 24 Jul 1996 10:27:02 -0500 From: Lloyd Petrey Subject: Re: Follow up: Win95 won't process login scripts >One more question. I downloaded Client 32 and it has a newer date >than the patch. Do I still need the patch? Yes, you do. And BTW there is another patch out there now for a total of 2. Sooooo what you need is: C3295N_1.EXE, C3295C.EXE, and C3295D.EXE ------------------------------ Date: Mon, 29 Jul 1996 10:27:57 CST From: Michael Levy Subject: Client32 can corrupt cc:Mail post office This is taken from the FAQ: "Q: I am having problems with database and mail programs when using Client 32. What can I do to troubleshoot the problem? A: There have been reported cases of problems with some applications that do record locking. To verify whether the issue is with the Client, Go to Control Panel | Network. Select Client 32 and choose Properties. Now select Advanced settings and select Opportunistic Locking. Turn this parameter OFF (the default is ON) and restart the machine to verify if this is the issue." I can report from unfortunate first-hand experience that you will corrupt your cc:Mail post office if you do not heed this warning. The cc:Mail list has posted a set of 5 Client32 for Windows95 parameters and their recommended values: cache writes off file cache level 0 (ZERO) opportunistic locking off true commit on packet burst off (especially with admin functions of cc:Mail) I read somewhere that Novell may have changed some of the defaults in their latest client versions, but I used the Feb 96 version and the latest patches and still ran into a problem. From first glance these settings seem to negate some of the advantages of moving to Client32, especially the packet burst. I hope these vendors address this issue in the future. (cc:Mail help from Andy Bach -- thx a.) ------------------------------ Date: Wed, 31 Jul 1996 10:05:25 -0400 From: Clay Gibney Subject: DOS Client32 & Groupwise notify I have installed the released version of DOS/Win client32 on three different PCs. On all three PCs, the PC will "hang" after a few minutes if I leave it in a DOS program. It doesn't matter what DOS program I leave it in. After experimenting and removing things from config.sys and autoexec.bat, it appears that DOS/Win client32 does not like the DOS version of Groupwise notify. Every other TSR I load doesn't cause a problem, just the DOS notify. With the DOS version of notify (v4.1 of GW), the PC will lock up within about 3-5 minutes after I login. ------------------------------ Date: Wed, 31 Jul 1996 10:41:00 CDT From: Glennon McBride Subject: Client 32 Losing Writes? I have a repeatable test case that indicates the Novell Client 32 loses writes to the server. This occurs with both the Windows 95 and the Dos/Windows 32 bit clients. Changing to the 16 bit VLMs or using Microsoft's Windows 95 client makes everything work fine. Testing using both a 3.11 and 4.1 host show the same results. The scenario is: Small program called SUBMIT opens a network based file, reads a number out of the file, and closes it. After using the number, the original file is opened in write mode, and the original number is incremented and written back to the file. The file is then closed and the program terminates. This program is called repeatedly from a BAT file which should result in the number used going up sequentially as 1, 2, 3, etc. Actual execution shows the number having frequent repeats. Some executions have even had it go backward 1, 2, 2, 3, 2, 3, etc. with the frequent repeats. The program tests all opens and reports any errors opening the file. None are reported. This all indicates that either the Client 32 is losing the writes to the file or that it thinks it doesnt need to reread the file. I have removed SMARTDRV and set CACHE WRITES=OFF in the NET.CFG. Also tried setting TRUE COMMIT=ON with no change in the results except it ran slower. --------- Date: Wed, 31 Jul 1996 12:44:55 -0400 From: "David P. Moon" Subject: Re: Client 32 Losing Writes? >I have a repeatable test case that indicates the Novell Client 32 loses >writes to the server. What kind of NIC are you using. I've found that some of these problems are specific to certain NIC vendors and/or the version of driver being run. On my own PC (Intel EtherExpress Pro ), turning off CACHE WRITES fixed my entire problem, but on another, older NIC, I had to turn off all the file cacheing also to get the problems to go away. ------------------------------ Date: Wed, 31 Jul 1996 08:56:22 -0500 From: "Scott Etienne, C.N.E." To: netw4-l@bgu.edu Subject: Re: NAL objects in NWADMIN? >I've got NAL running successfully in NW4.1. When i use my PC, >NWADMIN shows all the application objects ok. But when I go to >another PC, or use a network setup of Windows, NWADMIN shows the app >objects as unknown objects. In order to see NAL objects, there is a .DLL file you must reference in the NWADMIN.INI. Under [Snapin Object DLLs] header, you must have a line that reads like this: ASSNAP1=Z:\PUBLIC\APPSNAP.DLL. Also, make sure that the .DLL file is in Z:\PUBLIC. I had to put it there myself. ------------------------------ Date: Thu, 1 Aug 1996 13:56:37 -0400 From: Tim Edwards Subject: Re: Client32 can corrupt cc:Mail post office Look at Novell's Technical Information Document number 2907761 (support.novell.com). According to Novell "opportunistic locking caused corruption of CC:Mail database files. Further testing showed this problem also existed with the DOS/Windows Client32." Novell went on to say that "Because of the nature of this problem, it was determined that the opportunistic locking feature would need to be hardcode disabled in the release of the DOS/Windows Client32 and the next release of the Windows 95 Client32." I have not found any reason to disable packet burst, caching, or turn true commit off. In my personal opinion Lotus was using a sledgehammer to pound thumb tacks and the disabling of these functions should not be required and will handicap the workstations network client without reason. Anyone using the beta versions of the DOS/Windows Client32 or any version of the Windows 95 Client32 should verify that the Client32.NLM file is dated after 4-23-96. All versions after 4-23-96 have opportunistic locking disabled regardless of how the option is set. The new Client32.NLM is available from Novell's web site. ------------------------------ Date: Fri, 2 Aug 1996 08:36:50 -0400 From: "Mitchell, Luke" Subject: Client32DW /temporary files with MS Word When running the Client32 for Dos/Win3.1, the small temporary files that MS Word creates in the same directory as the opened document don't go away after the file is closed. Can anybody else verify this problem? Or is there a fix? The file is 54 bytes, and if you open a document called filename.doc on a local drive, the file (~$lename.doc) is created in the same directory as filename.doc. When you close the file, the other goes away. On a network drive, the temporary file remains. ------------------------------ Date: Mon, 5 Aug 1996 13:59:15 MDT From: "John L. Stevens" Subject: Re: how to logout using Client 32 >I don't know how to log out from my server using Client 32 under Windows >95. I tried to logout by clicking the item "logout" of the server icon in >the network section of Window 95, but I failed. Logout.exe runs, but I >am still logged in. After LOGOUT, RightClick on My Computer, Click Disconnect Network Drives and delete all references to the Network. I had that problem this morning on one of my users machines and that seemed to take care of it. Interested to find out if this is the "real" solution. ------------------------------ Date: Tue, 6 Aug 1996 16:31:36 -0400 From: Clay Gibney Subject: Dos Telnet & client32 -Reply >Please email me if you are using DOS Telnet with client32. thanks I don't think that will work. I've been using a DOS telnet program (MS Kermit 3.14) for several years, but when I started experimenting with client 32, it was time to find a winsock compatible telnet program. There are lots to choose from. Go: www.tucows.com for a large list of shareware and freeware telnet clients. --------- Date: Tue, 6 Aug 1996 22:00:35 +0100 From: Richard Letts Subject: Re: Dos Telnet & client32 >Please email me if you are using DOS Telnet with client32. thanks Yes. You load lsl.com and the client32 with a 16-bit shim which gives DOS programs access to the client32. ------------------------------ Date: Tue, 6 Aug 1996 19:53:21 -0500 From: Mobeen Azhar Subject: Re: Problems with DOS/WIN Client32 -Reply I have installed client32 for DOS and Windows 3.X successfully on many different Austin and Compaq workstations. Everything works fine. The installation was not without it's headaches (what is, these days?). On a lot of the workstations, I had to remove EMM386.EXE from CONFIG.SYS (even excluding all of upper memory did not help, EMM386.EXE had to be removed). On some workstations I actually had to change out RAM SIMMS. Apparently there were bad spots in RAM that surfaced only when client32 gobbled up chunks of it for caching. However, client32 does now run fine. One thing you might want to try is to remove EMM386.EXE from the CONFIG.SYS, and also remove VIPX.386 from the SYSTEM.INI. ------------------------------ Date: Wed, 7 Aug 1996 15:26:32 +1000 From: David Lane Subject: Client 32 windows 3.1x To all those who cannot get the GUI Login to close the script screen after logging in and you have checked that the Auto close scripts box is checked. Look at your login script and fix any mapping errors that occur. These will prevent the script box from closing. One assumes Novell wishes to ensure you get the error message. ------------------------------ Date: Wed, 7 Aug 1996 12:41:00 -0500 From: Randy Richardson Subject: How to make Cient32 For DOS/Windows 3.1x work really well I've been reading a lot of messages about Client32 for DOS/Windows 3.1x, many of which appear to contain a lot of frustration. As an attempt to help everyone, I've included a set of all the appropriate configuration files that I use to support over 100 workstations with no problems. The hardware ranges from 386 clones to Compaq DeskPro Pentium desktops (wow, these sure are nice machines!). I've standardized the entire network on Intel EtherExpress Pro 10+ cards (and a few Compaq NetFlex3 cards in Compaq Proliant file servers running NetWare 3.12). These network cards don't require any memory exlusion in Emm386.Exe, and unlike the 3Com cards, they actually pass diagnostic information up the ODI stack properly. Good luck with Client32, hopefully with my experience, you'll have success and reliability! By the way: My "Total Available Conventional Memory" is 621k after the user is logged in. === ---------------------------------------- === General tips === - Use MS-DOS v7.x (comes with Windows95). - Use HiMem.Sys and Emm386.Exe from MS-DOS 7.x. - Remove SetVer.Exe. - Use the "NoEMS" parameter with Emm386.Exe. - Load your mouse drivers and SmartDrv.Exe AFTER Client32. - Make sure you have the LATEST version of Client32 (I've got version 2.01, Version.Exe checksum is 674DEFCF37ECE2A43B032). - Make sure Windows is COMPLETELY updated with Client32. - I also recommend that you re-install Windows 3.11 AFTER installing MS-DOS v7.x. === ---------------------------------------- === MSDOS.Sys === [Paths] [Options] BootMulti=1 BootGUI=0 Network=1 BootKeys=1 BootDelay=2 BootMenu=0 BootMenuDelay=4 Logo=0 ;Don't forget to add the >1024 bytes of filler! === ---------------------------------------- === Config.Sys === Switches = /F Device = \HiMem.Sys /TestMem:On /Verbose DeviceHigh = \Emm386.Exe NoEMS Auto X=C000-C7FF Verbose Dos = High,UMB Buffers = 32 Files = 99 Shell = \Command.Com /e:2048 /p LastDrive = Z Device = \IFSHlp.Sys Stacks = 9,256 === ---------------------------------------- === AutoExec.Bat === @Echo off Prompt $P$G Path \DOS \Novell\Client32\StartNet.Bat === ---------------------------------------- === StartNet.Bat === Set NWLanguage=ENGLISH \Novell\Client32\NIOS.Exe /W /D Load \Novell\Client32\LSLC32.NLM Load \Novell\Client32\CMSM.NLM Load \Novell\Client32\EtherTSM.NLM Load \Novell\Client32\EPro.LAN Port=210 Frame=EtherNet_802.3 Load \Novell\Client32\EPro.LAN Port=210 Frame=EtherNet_II Load \Novell\Client32\IPX.NLM Load \Novell\Client32\Client32.NLM F: F:\Login\Begin.Bat === ---------------------------------------- === Net.Cfg === Link Support Buffers 8 1526 MemPool 4096 Max Stacks 8 NetWare DOS Requester Auto reconnect level = 4 Cache writes = On Checksum = 2 Close behind ticks = 36 Delay writes = On File cache level = 3 First network drive = F Force first network drive = On Max cache size = 1024 Max cur dir length = 255 Message level = 4 NetWare protocol = NDS Bind Network printers = 9 PB buffers = 8 Preferred server = Search dirs first = On Show dots = On Signature level = 2 Protocol IPX IPX Sockets 40 Protocol TCPIP Bind EPro IP_Address IP_Router IP_NetMask Path TCP_Cfg \Novell\Client32\TCP === ---------------------------------------- === Explanations === Replace the keyword "" with the actual drive and option subdirectory of the correct location of the file. Replace the keyword "" with the name of the file server this workstation should connect to by default. I always turn on all the verbose options for two reasons; 1. It will be helpful to me if I ever need to troubleshoot, and 2. The user knows something is happening when the computer is booting in the morning. In MS-DOS 7.x: MSDOS.Sys is an ASCII text file that can be edited. I disabled the logo so users won't see the "Windows 95" graphical logo at startup and come to me and say "So where's Windows 95?" In MS-DOS 7.x: You can use a lot of the MS-DOS 6.22 utilities with MS-DOS 7.x, and they will work quite well. In MSDOS.Sys: Must be greater than 1024k to resolve a compatibility issue with the way Microsoft designed MS-DOS. In Config.Sys: The "Switches /F" paramater disables the 2 second delay that comes into play when booting. In Config.Sys: Microsoft recommends excluding the video ROM at C000-C7FF, so I've done just that. This has fixed a lot of problems that show up mostly in clones (non-name brand stuff). In AutoExec.Bat: You MUST set the path if you want your C:\DOS\ directory to be searched. By default, MS-DOS 7.00 does NOT set this up for you (MS-DOS 6.x does). In StartNet.Bat: The last line passes control to a batch file in Sys:Login on your default file server which loads the mouse driver, SmartDrv.Exe, and TCPIP.NLM from drive F: (this means less files at the client, enforcement of standardization of driver versions, plus easy file updating). In Net.Cfg: I've set the buffer size to 1526 bytes after reading some technical books that show the actual packet size to be 1526 (not 1514). I figure an extra 12 bytes to stay on the safe side and ensure stability is no big deal. In Net.Cfg: These settings are optimized for really good performance. If you see any way I can improve this, please let me know. In Net.Cfg: Both NetWare 3.12 and 4.10 (both fully patched) work very reliably (we're just upgrading from NetX.Exe). In Sys:Login/Begin.Bat: I run McAfee anti-virus once each day from this batch file, and a second anti-virus product as well (which I won't reveal in public). I recommend you load the mouse driver and SmartDrv before the virus check to speed things up a bit. The mouse driver allows the user to check if the mouse is working in the second anti-virus utility, and does no harm. I've found that some users will panic if they are familiar with the anti-virus software and the mouse cursor doesn't show up. If you have any suggestions for me, or any further questions, please feel free to send me EMail at "Randy.Richardson@MindLink.BC.Ca" because I don't read all the ListServer messages and will probably miss it. - Randy Richardson. ------------------------------ Date: Fri, 9 Aug 1996 17:20:04 -0600 From: Joe Doupnik Subject: Re: Dos Telnet & client32 >I'm going in circles...my dos telnet says "Network Jammed" and now it >has a hard time connecting to the server when I log in. It can't hold >its connection. Here is my startnet.bat and net.cfg...can anyone >help. thanks >Also, should I be loading the 16bit TCPIP driver instead of tcpip.nlm > >SET NWLANGUAGE=ENGLISH >C:\CLIENT32\NIOS.EXE >C:\CLIENT32\LSL.COM >C:\CLIENT32\n16odi.COM >C:\CLIENT32\nesl.COM >C:\CLIENT32\smc8000 >LOAD C:\CLIENT32\LSLC32.NLM > rem ***C:\CLIENT32\pdoseth.com ***"I thought pdoseth loads pc32mlid" >LOAD C:\CLIENT32\PC32MLID.lan > rem ***LOAD C:\CLIENT32\CMSM.NLM > rem ***LOAD C:\CLIENT32\ETHERTSM.NLM > rem ***LOAD C:\CLIENT32\SMC8000.LAN FRAME=Ethernet_802.3 PORT=280 >MEM=D4000 INT=3 > rem ***LOAD C:\CLIENT32\SMC8000.LAN FRAME=Ethernet_II PORT=280 >MEM=D4000 INT=3 >LOAD C:\CLIENT32\TCPIP.NLM >LOAD C:\CLIENT32\IPX.NLM >LOAD C:\CLIENT32\CLIENT32.NLM >rem C:\CLIENT32\TSASMS.COM >c:\lan\odipkt > >Link Driver SMC8000 > ;NOTE: 32 Bit driver settings are found in STARTNET.BAT > ;This section does not reflect 32 bit settings. > ;The values in this section are the 16 bit values from the old >net.cfg. > PORT 280 > INT 5 > MEM d0000 > Frame Ethernet_II > Frame Ethernet_802.3 >; Protocol IP 0800 Ethernet_II >; Protocol IPX 0 Ethernet_802.3 >; Protocol ARP 0806 Ethernet_II >; Protocol RARP 8035 Ethernet_II > > >NetWare DOS Requester > FIRST NETWORK DRIVE = I > SHORT MACHINE TYPE = IBM > NETWARE PROTOCOL = NDS BIND > >PROTOCOL TCPIP > PATH TCP_CFG C:\CLIENT32\TCP > IP_ADDRESS 198.138.81.138 > IP_ROUTER 198.138.81.1 > IP_NETMASK 255.255.255.0 > >NetWare DOS TSA > TSA Server Name = Franklin > Workstation Name = testpc486/50 > Password = > Disk Buffers = 10 > Drives = C >NIOS > LINE DRAW CHARS = "######" ----------- Here's my 16-bit Client-32 material, if it helps. Order is important Joe D. File startnet.bat - SET NWLANGUAGE=ENGLISH C:\CLIENT16\NIOS.EXE > c16.log C:\CLIENT16\LSL.COM >> c16.log C:\CLIENT16\N16ODI.COM >> c16.log C:\CLIENT16\NESL.COM >> c16.log C:\CLIENT16\NE3200.COM >> c16.log LOAD C:\CLIENT16\LSLC32.NLM >> c16.log LOAD C:\CLIENT16\PC32MLID.LAN >> c16.log rem ;;LOAD C:\CLIENT16\TCPIP.NLM rem ;;LOAD C:\CLIENT16\NWIP.NLM LOAD C:\CLIENT16\IPX.NLM >> c16.log LOAD C:\CLIENT16\CLIENT32.NLM >> c16.log Bottom of net.cfg - Link Support Max Stacks 10 Buffers 4 1550 MemPool 2048 max boards 6 Link Driver NE3200 int 5 slot 1 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 ; Below is for Novell's Lan WorkPlace for DOS Protocol TCPIP PATH TCP_CFG N:\LWPDOS5\NET\TCP;N:\LWPDOS5\TCP; IP_ADDRESS 129.123.1.45 LAN_NET IP_NETMASK 255.255.255.0 LAN_NET IP_ROUTER 129.123.1.254 LAN_NET Bind NE3200 #1 Ethernet_II LAN_NET NWIP AUTORETRIES 1 AUTORETRY SECS 10 NSQ_BROADCAST ON NWIP1_1 COMPATIBILITY OFF NWIP_Domain_Name Protocol IPX IPX SOCKETS 40 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: Mon, 12 Aug 1996 08:42:51 -0400 From: "David P. Moon" Subject: Client 32 update file The file CLTDR1.EXE has been posted on Novell's FTP site. I've included the first few lines of its description file below. Besides the updated LAN drivers, the files CMSM.NLM, ETHERTSM.NLM, LSLC32.NLM, are newer than the ones I had from the original CL32 DOS/WIN installation. No info is provided as to what bugs may have been fixed since the previous versions of these files. NOVELL TECHNICAL INFORMATION DOCUMENT TITLE: Readme for CLTDR1.EXE README FOR: CLTDR1.EXE NOVELL PRODUCTS and VERSIONS: NetWare Client for DOS/MS Windows 1.2 NetWare Client32 for DOS/Windows 2.1 NetWare Client32 for WIN95 2.1 ABSTRACT: These are the latest ODI LAN Drivers and associated files for Client32 for Windows95, Client32 for DOS/WIN, and the VLM client. ------------------------------ Date: Thu, 15 Aug 1996 13:01:14 +0100 From: Phil Randal Subject: Re: Client32 DOS/Win + Access + Btrieve = #:( Here's another Client32 bug: It allows a program to delete the currently logged directory. I.e. I'm in f:\me\test and run the program rmd f:\me\test where rmd.exe does an rmdir of its command line. VLMs, NetX all didn't allow it, but Client32 does and then gets itself into a right mess. --------- Date: Thu, 15 Aug 1996 13:40:28 +0000 From: Jon Hall Subject: Re: Client32 DOS/Win + Access + Btrieve = #:( >Here's another Client32 bug: > >It allows a program to delete the currently logged directory. I don't think that one's specific to Client32. The last version of NETX (which I'm still using for various reasons) allows it. To use your example, if while in f:\me\test you run the command rd ..\test (assuming test is empty), the F: drive mapping is lost causing COMMAND.COM to report "Current drive no longer valid". ------------------------------ Date: Thu, 15 Aug 1996 13:16:27 -0400 From: Clay Gibney Subject: Re: Client32 DOS/Win + Access + Btrieve = #:( -Reply > >>However, if I install Client32 on a workstation, then switch back >>to VLMs, it continues not to work. > >>Does anyone have recommendations for an easy way to truely undo the >>Client32 install? > >C32 does update files in \Windows\System. > >I would suggest someone make a ZIP of their system directory, >install the C32, do a DIRMATCH (or equiv) to find out the >files that have changed and save only those files in an >UNDO-C32.ZIP. > >If that special someone does such a fine thing, I will note >the files in NVCL32DW.DOC. I can't address the Btrieve/Access issue, but I do know that you can take a PC that had VLM's installed and then install DOS/Win client32. If you then want to go back to using VLM's, just correct your autoexec.bat to load the VLM software again, and make one change in your system.ini file in the [386enh] section: On the line that has vnetware.386, add back in the vipx.386 driver (the client32 install takes it out). I have done this successfully on several PCs, and in fact Novell says that this can be done as the NETWARE.DRV and other files for client32 are compatible with VLM's. ------------------------------ From: "David W. Hanson" Date: Fri, 16 Aug 1996 13:01:40 +0100 Subject: Re: Client32 DOS/Win + Access + Btrieve = #:( >I would suggest someone make a ZIP of their system directory, >install the C32, do a DIRMATCH (or equiv) to find out the >files that have changed and save only those files in an >UNDO-C32.ZIP. > >If that special someone does such a fine thing, I will note >the files in NVCL32DW.DOC. Here ya go... /WINDOWS/SYSTEM/NETWARE.DRV 170736 96-05-21 16:57:12 /WINDOWS/SYSTEM/NETWARE.DRV 165632 94-10-24 14:29:54 /WINDOWS/SYSTEM/NWPOPUP.EXE 18416 96-05-01 14:57:50 /WINDOWS/SYSTEM/NWPOPUP.EXE 4592 94-09-30 10:58:28 /WINDOWS/SYSTEM/VNETWARE.386 15838 96-05-07 15:24:42 /WINDOWS/SYSTEM/VNETWARE.386 15645 94-08-17 15:38:34 /WINDOWS/SYSTEM/NWCALLS.DLL 147856 96-02-14 12:56:54 /WINDOWS/SYSTEM/NWCALLS.DLL 147616 94-10-20 11:56:36 /WINDOWS/SYSTEM/NWIPXSPX.DLL 41088 96-01-09 14:17:58 /WINDOWS/SYSTEM/NWIPXSPX.DLL 41456 94-10-18 14:55:50 /WINDOWS/SYSTEM/NWLOCALE.DLL 43440 96-04-29 08:19:04 /WINDOWS/SYSTEM/NWLOCALE.DLL 43088 94-09-20 12:16:42 /WINDOWS/SYSTEM/NWNET.DLL 225280 96-06-11 10:06:28 /WINDOWS/SYSTEM/NWNET.DLL 225264 94-10-18 16:35:50 /WINDOWS/SYSTEM/NWPSRV.DLL 279770 96-01-26 10:55:30 /WINDOWS/SYSTEM/NWPSRV.DLL 277532 94-10-06 13:35:30 /WINDOWS/SYSTEM/NWGDI.DLL 108176 96-04-30 11:19:18 /WINDOWS/SYSTEM/NWGDI.DLL 82064 94-05-17 10:25:48 /WINDOWS/SYSTEM/NWUSER.EXE 5296 96-04-15 15:38:42 /WINDOWS/SYSTEM/NWUSER.EXE 5072 93-10-28 08:12:42 /WINDOWS/SYSTEM/TLI_SPX.DLL 52837 95-12-13 11:24:38 /WINDOWS/SYSTEM/TLI_SPX.DLL 52437 94-09-15 14:26:06 /WINDOWS/SYSTEM/TLI_WIN.DLL 15713 95-08-07 16:56:42 /WINDOWS/SYSTEM/TLI_WIN.DLL 15713 94-06-08 17:28:24 /WINDOWS/SYSTEM.INI 1726 96-08-16 12:22:58 /WINDOWS/SYSTEM.INI 1718 96-02-27 08:28:26 /WINDOWS/PROGMAN.INI 346 96-08-16 12:23:00 /WINDOWS/PROGMAN.INI 317 96-03-06 17:02:08 /WINDOWS/NLS/1252_UNI.001 727 96-01-11 16:51:52 /WINDOWS/NLS/1252_UNI.001 727 94-05-31 12:39:46 /WINDOWS/NLS/UNI_1252.001 1017 96-01-11 16:48:30 /WINDOWS/NLS/UNI_1252.001 2264 94-05-31 12:39:48 /WINDOWS/NLS/UNI_COL.001 665 96-01-11 16:51:52 /WINDOWS/NLS/UNI_COL.001 1752 94-04-04 12:22:18 /WINDOWS/NLS/UNI_MON.001 2361 96-01-11 16:47:46 /WINDOWS/NLS/UNI_MON.001 4312 94-04-04 12:22:18 /WINDOWS/NLS/ENGLISH/NETWARER.DRV 27968 96-05-21 17:24:24 /WINDOWS/NLS/ENGLISH/NETWARER.DRV 165632 94-10-24 14:29:54 /WINDOWS/NLS/ENGLISH/NETWARE.HLP 164471 96-05-20 12:31:28 /WINDOWS/NLS/ENGLISH/NETWARE.HLP 419701 94-08-29 13:15:00 /WINDOWS/NETWARE.INI 11 96-08-16 12:18:54 /WINDOWS/NETWARE.INI 11 96-07-03 19:22:10 ------------------------------ Date: Wed, 21 Aug 1996 12:21:00 +1 From: "Haas, Marcel" Subject: Re: MS Word, Temporary Files, and Client32 DOS/Windows >When opening a file, a hidden, temporary file is automatically created >in the directory alongside the file that is now open in Word. In the past >(pre Client32 DOS/Windows), after I closed the file or exited Word, the >temporary file would be automatically deleted. This is not happening now, >and I must manually delete these TEMP files if I want to get rid of >them. There is a way to suppress the use of these temp-files (see Word Help): file: WINWORD6.INI section [Microsoft Word] add: NoOwnerFiles= ------------------------------ Date: Mon, 26 Aug 1996 14:13:26 -0600 From: Joe Doupnik Subject: Re: Packet Drivers not in NETX >Is there a way of using packet drivers under VLM or Client32? >How can I enable a TCP stack with them? --------- I think you mean "with Client32" rather than implying a particular load/functional order. Packet Drivers are virtual boards to the users of PDs, an they are real-mode objects at that side. I don't have time today to give a long discourse on Packet Drivers, NDIS, and ODI so the snippet below will have to do; it's been on this list a couple of times recently. Client32 with 32 bit drivers plus a real mode interface on the side. Once pdoseth is running you can load odipkt and winpkt. I have more frames loaded than you need because I do many other things with this material. Whose TCP/IP stack is the vital question. Only one per physical board. Joe D. ------------ File 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\CNE3200.LAN SLOT=1 FRAME=ETHERNET_II >>start.log LOAD C:\CLIENT32\CNE3200.LAN SLOT=1 FRAME=ETHERNET_802.3 >>start.log LOAD C:\CLIENT32\CNE3200.LAN SLOT=1 FRAME=ETHERNET_SNAP >>start.log LOAD C:\CLIENT32\CNE3200.LAN SLOT=1 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 - ; Don't forget to say lastdrive=z in config.sys! Netware dos requester PB buffers=1 PBurst read window 6 PBurst write window 6 checksum=on ; speedup high quality links true commit=off ; off=let server buffer writes lip start size= 1500 ; long packets across routers ;; auto reconnect=off ; off=do not load auto.vlm bind reconnect=on cache buffers=0 ; 0=removes cache network printers=1 ; shrinks print.vlm, won't load it average name length=24 ; shrinks connection table load low conn=ON load low ipxncp=ON load low fifo=on ; part of fifo.vlm, speeds accesses load low netx=on ; part of netx.vlm, speeds accesses load low redir=on ; part of redir.vlm, speeds accesses ;;;; print buffer size=0 file cache level=0 signature level=0 ; 0=don't load security.vlm read only compatibility=on first network drive=n netware protocol= nds,bind preferred server=edu-usu-netlab2 preferred tree=EDU name context="O=USU" ; VLM selection, order sensitive - ; For Bindery include bind and netx, omit nds. ; Also preferred server is read for Bindery only. ; For Directory Services include nds, omit bind and netx. ; Also preferred tree and name context are read for DS only. use defaults=off ; off=use explict list of vlms which follow vlm=conn.vlm ; Connection tables vlm=ipxncp.vlm ; NCP over IPX vlm=tran.vlm ; Transport services worker vlm=security.vlm ; Security, optional vlm=nds.vlm ; DS, NCP Directory Services vlm=bind.vlm ; Bindery, NCP vlm=nwp.vlm ; Transport services worker vlm=fio.vlm ; File i/o vlm=general.vlm ; General support routines vlm=redir.vlm ; Redirector vlm=print.vlm ; Print services, optional vlm=netx.vlm ; Bindery, shell compatibility ; vlm=rsa.vlm ; DS, RSA encryption, optional ; vlm=auto.vlm ; DS, autoreconnect/retry, optional ; vlm=nmr.vlm ; Managment responder, optional Netx show dots=on ;# Below this line material is the same as for NetWare 3.11 protocol KERMIT ; bind SLIP_PPP ; bind exos ; bind ne2000 ; bind #1 ; bind smcplus bind pdoseth ; bind telebit ; MYIP 129.123.247.1 Link Support Max Stacks 10 Buffers 4 1550 MemPool 2048 max boards 8 Link Driver NE3200 int 5 slot 1 Frame Ethernet_II Frame ETHERNET_802.3 Frame ETHERNET_802.2 Frame ETHERNET_SNAP Protocol IPX 8137 Ethernet_II Protocol IP 0800 Ethernet_II Protocol ARP 0806 Ethernet_II Protocol RARP 8035 Ethernet_II Protocol IPX IPX SOCKETS 40 Link Driver PDOSETH Frame Ethernet_II Protocol IP 0800 Ethernet_II Protocol ARP 0806 Ethernet_II Protocol RARP 8035 Ethernet_II ------------------------------