--------------- FIDO MESSAGE AREA==> TOPIC: 194 NOVELL Ref: DEL00025 Date: 10/05/96 From: RICHARD PEER Time: 04:21pm \/To: ALEJANDRO CALVO (Read 4 times) Subj: 2 Servers 3.12 In a message of <30 Sep 1996 21:27>, Alejandro Calvo (4:900/617.15) writes: AC> If I have 2 Servers (Both of them Novell 3.12), can I use AC>these 2 servers at the same time. Yes, login to the first and attach to the second. If the user names and passwords are the same, an attach in the login script will not prompt for these details, but if they are not, the information will be requested at the appropriate time. Attach from the command line works as login does except that the connection to the first server is maintained and no login script is run. Regards, Richard. --- Msged/Q 1.60 * Origin: Sysop "Novell User Group of SA" Pta, RSA (5:7106/22) --------------- FIDO MESSAGE AREA==> TOPIC: 194 NOVELL Ref: DEL00026 Date: 10/12/96 From: RICHARD PEER Time: 12:31pm \/To: JAMES MCCOY (Read 4 times) Subj: NOVELL 3.12 In a message of <04 Oct 1996 19:13>, James Mccoy (1:107/410@FIDONET.ORG) writes: JM>That is for the ELECTROTEXT version of the docs. later issues JM>had a dydnatext versuion or some such thing that I have no JM>experience with. Very similar to install, and similar to set up and run. Regards, Richard. --- Msged/Q 1.60 * Origin: Sysop "Novell User Group of SA" Pta, RSA (5:7106/22) --------------- FIDO MESSAGE AREA==> TOPIC: 194 NOVELL Ref: DEL00027 Date: 10/12/96 From: RICHARD PEER Time: 12:55pm \/To: JIM HEPWORTH (Read 4 times) Subj: Memory and Novell 3.12 In a message of <05 Oct 1996 21:41>, Jim Hepworth (1:2424/2406) writes: JH>Sounds like your PC is not properly recognizing memory above the 16 Meg JH>mark. Correct JH>Move the loading of your drivers from the startup.ncf to the JH>autoexec.ncf, load those drivers first, then mount volume SYS. What on earth ??????? Add the command register memory 1000000 1000000 to the autoexec.ncf file. This will inform Netware that 32 meg is installed. Auto registration of memory above 16 meg is dependant on the motherboard design. JH>You should find you have more memory after trying that. Tripe. JH>Jim Hepworth JH>CNE Ask for your money back. A CNE is required to know about the register memory command. Regards, Richard. --- Msged/Q 1.60 * Origin: Sysop "Novell User Group of SA" Pta, RSA (5:7106/22) --------------- FIDO MESSAGE AREA==> TOPIC: 194 NOVELL Ref: DEL00028 Date: 10/12/96 From: RICHARD PEER Time: 12:56pm \/To: JEROEN RUIS (Read 4 times) Subj: NOT LOGGED IN In a message of <09 Oct 1996 10:18>, Jeroen Ruis (2:281/705.30) writes: JR> KH> The "NOT LOGGED IN" stations are machines on the network, but no ser JR> KH> has logged in to it yet. Running NETX, STARTNET of whatever gets ou JR> KH> going attatches you to the network -- Correct. JR>Not just that. JR>A station that's turned on (and hasn't even booted yet) is here JR>visible a NOT-LOGGED-IN on our NW3.12 server. So it doesn't JR>need to run netx. Netx or the newer VLM is the part of the network connection that initailises the connection to the server. Only when either netx or the VLM is loaded, does the server even know about the workstation. However, a workstation that was connected, can be turned off, and the server will maintain the connection until either the workstation reconnects (when the connection is reinitialised at the server after netx or the VLM loads) or a time out (normally 15 minutes) when the server will automatically kill the connection. This time out is actually a multi step time out, the server sends a message to the workstation after a configurable time and then repeats the request several times, also configurable, and drops the connection if no response is received. Breaking the network cable will have the same effect, but reconnecting it within the time period will restore the original connection. JR>I think. I think not. Regards, Richard. --- Msged/Q 1.60 * Origin: Sysop "Novell User Group of SA" Pta, RSA (5:7106/22) --------------- FIDO MESSAGE AREA==> TOPIC: 194 NOVELL Ref: DEL00029 Date: 10/12/96 From: RICHARD PEER Time: 12:40pm \/To: PAUL KARKARIN (Read 4 times) Subj: NETWARE v3.12 In a message of <28 Sep 1996 11:36>, Paul Karkarin (2:5075/10.16@fidonet) writes: PK>Startup.ncf: PK>load .dsk PK>Autoexec.bat: PK>load ne2000 port=??? int=?? frame=????? name=xxx PK>bind ipx xxx net=?? Err, that should be autoexec.ncf, the autoexec.bat contains the server command. PK> MF> Also what is the recommended size of the DOS partitation. I think PK> MF> 40Mb is enough. But I'd like some other peoples opinions. More than enough. I think the default is 12Mb, but I was running with 5Mb for ages. PK>My DOS partition is 20 Mb Regards, Richard. --- Msged/Q 1.60 * Origin: Sysop "Novell User Group of SA" Pta, RSA (5:7106/22) --------------- FIDO MESSAGE AREA==> TOPIC: 194 NOVELL Ref: DEL00030 Date: 10/12/96 From: RICHARD PEER Time: 12:57pm \/To: DAVID BELL (Read 4 times) Subj: NCP Directory Search Limit error In a message of <06 Oct 1996 21:01>, David Bell (2:254/26@fidonet.org) ites: DB>You have exceeded your NCP Directory Search Limit - & locks the DB>user. From the Client, one can press Ctl-Enter to regain use DB>of the DV window, but thats not often an option if I'm not DB>around. This is an old DOS problem. When a directory search is started under DOS, the directory is loaded and scanned. The search should continue to the end of the directory and then it will terminate. If the search restarts without reaching the end, DOS simply overwrites the memory area containing the search information and carries on happily. Netware is a multiuser system and thus keeps a separate search area for each search started and releases these areas only when the search completes. When multiple searches are started, and none of them completed, the above error message occurs. Normally the user is unaware of the problem. DB>I've tried doubling the max directory searches but this doesn't DB>seem to have cured the problem. The problem is definately due to badly written DOS based software. DB>Comments already received suggest that the FLM2 software is not DB>Netware compatible, and/or that this is a Novell 3.12 bug. The first. It is lazy programming that does not cause problems under straight DOS. Netware cannot work around it as it has no indication as to whether the first search will later continue or not, and thus all the required buffers eventually are used and the error occurs. DB>Anyone have any more info or suggestions on possible cures please? There is only one cure, fix the DOS application (FLM2). Regards, Richard. --- Msged/Q 1.60 * Origin: Sysop "Novell User Group of SA" Pta, RSA (5:7106/22) --------------- FIDO MESSAGE AREA==> TOPIC: 194 NOVELL Ref: DEL00031 Date: 10/12/96 From: RICHARD PEER Time: 12:51pm \/To: JIM HALSEY (Read 4 times) Subj: Silly Question? In a message of <08 Oct 1996 16:26>, Jim Halsey (2:440/7.11) writes: JH>I am just in the process of a CNE course, I have just installed 3.12 JH>server on my home PC. Is it possible to run Server from inside Win95? Nope. The server module must be loaded without any memory managers loaded as it does its own memory management. JH>So that I don't have to keep switching between the two! You will need a clean DOS boot. JH>I've got a P200 with 32Mb of Ram. (I am running ISADISK). No hardware problem. Regards, Richard. --- Msged/Q 1.60 * Origin: Sysop "Novell User Group of SA" Pta, RSA (5:7106/22) --------------- FIDO MESSAGE AREA==> TOPIC: 194 NOVELL Ref: DEL00032 Date: 10/13/96 From: RICHARD PEER Time: 11:58am \/To: JOY SY (Read 4 times) Subj: Changing Topology In a message of <11 Oct 1996 11:04>, JOY SY (6:754/10) writes: JS> We changed from Thin Coaxial Cabling to UTP Cabling & Upgraded from JS>Novell 3.11 to 3.12. After changing, our Windows 95 machines were JS>able to function. However, our DOS workstations could not see the JS>server anymore. JS>Don't have to reconfigure IPX.COM? We are just using IPX.COM,NETX.COM JS>to get into the network. You have to reconfigure. But there is a simpler method. JS>MONITOR is Ethernet_802.2. Is this correct? Yes. The default is changed. The simpler method is to add the parameter frame=ethernet_802.3 to the line loading the lan driver on the server. This was the default on the older Netware versions. The new default is ethernet_802.2. The alternative is to reconfigure all the workstations. The Win95 ones drive all possible frame types which makes them seem better at the expense of more network traffic. AFAIK, the dedicated IPX.COM defaults to frame type 802.3 and can with the econfig utility be changed to Ethernet_II, but I do not think that 802.2 can be implemented this way. Which in turn means upgrading the workstation to the newer ODI stack. Regards, Richard. --- Msged/Q 1.60 * Origin: Sysop "Novell User Group of SA" Pta, RSA (5:7106/22) --------------- FIDO MESSAGE AREA==> TOPIC: 194 NOVELL Ref: DEL00033 Date: 10/13/96 From: RICHARD PEER Time: 12:08pm \/To: MUFUTAU TOWOBOLA (Read 4 times) Subj: NW 3.12 ELECTRONIC DOCS In a message of <10 Oct 1996 20:21>, Mufutau Towobola (1:278/111) writes: MT> Luckily, I got hold of those NW 3.12 DynaText Electronic documents. MT>I think the newer NW3.12 with CD-ROM formats is the only one that MT>carries them, not available with the floppy format... Not true. I have them on floppy format (actually 1.44 stiffy format) on all the copies of NW 3.12 that I have. Earlier copies of NW 3.12 came without the electronic documentation. MT>The files were about 15Meg in total.... so you can see why it's nly MT>available on CD-ROM. Plenty stiffy disks. (15 of them, I just checked). Regards, Richard. --- Msged/Q 1.60 * Origin: Sysop "Novell User Group of SA" Pta, RSA (5:7106/22) --------------- FIDO MESSAGE AREA==> TOPIC: 194 NOVELL Ref: DEL00034 Date: 10/15/96 From: MUFUTAU TOWOBOLA Time: 01:59pm \/To: RICHARD PEER (Read 4 times) Subj: NW 3.12 ELECTRONIC DOCS