Date: Fri, 16 Aug 1996 10:17:19 -0600 From: Joe Doupnik Subject: Re: Copy as an External Command >I am trying to copy some files from one network drive to another in my >login script. I keep getting "unable to execute external command "copy". ------------- Simple. #path\command.com /c copy foo bar as in this live system login script example (NW 3.12): if OS_VERSION >= "V7.00" then map del s5: map ins s2:=f:\win95 map ins s3:=f:\win95\command map ins s4:=f:\win95\user #sys:\win95\command\attrib +r c:\command.com #sys:\win95\command\attrib +r c:\net.cfg #sys:\win95\command.com /c copy f:\win95\user\system.dat c:\ #sys:\win95\command.com /c copy f:\win95\user\user.dat c:\ #sys:\win95\command\attrib +r +s +h c:\system.dat #sys:\win95\command\attrib +r +s +h c:\user.dat else #sys:\dos\attrib +r c:\command.com #sys:\dos\attrib +r +h c:\net.cfg endif drive c: The /c means consider the following text as if typed at the DOS prompt. You must have spaces surrounding it. Joe D. ------------------------------ Date: Tue, 30 Jul 1996 18:41:10 -0400 From: Larry Hansford Subject: Re: who deleted files >I have noticed if the files are deleted using Window's >File Manager or Explorer, they usually do not appear >when you run Salvage. I assume that the Windows software >takes care of the 'purge'?? Anyone else notice this? My experience has been that it depends on how they were deleted in Windows. If one or more files are selected in file manager and then deleted, they tend to show up as salvage files. However, if the directory or subdirectory is selected in file manager and then deleted, none of the files show up as salvage files. ------------------------------ Date: Mon, 7 Aug 1995 18:07:00 EST5EDT From: "Donald E. Hanley" Subject: Re: NW 4.1 & Pmail >We just upgraded from NW 3.11 to 4.1, running bindery emulation mode >and we can not get the latest version of Pegasus Mail, which ran fine >under 3.11, to find the existing mailbox. It says it doesn't exist. There are a bunch of Mercury/Pegasus "gotchas" strewn along the path to v4.1 nirvana. It looks like you are familiar with some of them, but for completeness, here is a list all of the ones I am aware of: 1) With v4.1, Mercury/Pegasus no longer supports the print queue method of passing email back and forth. Instead, they use only the SPOOL directory method. However, many installations migrated from CHARON, which supports only print queues, to Mercury. Since most of us have a bias in favor of doing what worked in the past, a Mercury/Pegasus reconfiguration is a common NetWare v3.1x to v4.1 prerequisite. 3) SYS:MAIL\internal_ID# accounts are not created automatically for NEW users added after the upgrade to 4.x UNTIL a) they login to the server while running the NETX.EXE shell, or b) they login to the server while running the VLM redirectory with the "/b" switch (ie. bindery emulation mode) on their login command line. 5) Keeping in mind that the current versions of Mercury/Pegasus use bindery emulation, can you guess what happens if you put multiple servers into the same bindery context? Remember PCONFIG, the guy that allows you as the administrator to specify a number of things such as the host address? Well, since Pegasus has only one bindery object to play with, you will only be able to specify one host address for ALL of the servers in that bindery context. Consequently, all of your users in that context will have a From: address which has the same host (server) name, no matter which server they are actually using! To work around this problem you can employ Mercury's aliasing feature to redirect inbound mail to the correct server. Painful, but it works. ------------------------------ Date: Mon, 18 Mar 1996 12:55:31 -0500 (EST) From: "Larry C. Hansford" Subject: FAQ Update You can subscribe to receive Novell Application Notes for US$95, $135 outside the United States, by calling 800-377-4136 or 303-297-2725, or writing to Research Order Desk, Attn: Novell Program Admin, 1601 Park Ave. West, Denver, CO 80216-5199 USA Orders can also be faxed to 303-294-0930 or e-mailed to APPNOTES@HIBBERTCO.COM ------------------------------ From: Subject: A FAQ suggestion Date: Sat Feb 17 20:33:02 1996 In case this isn't already in the FAQ: >$I am setting up a small network using Novell's two-user CD and am >$trying to get by without having to buy a hub at this point. Does >$anyone know on what numbers the wires cross on an RJ45 to make this work? > > Your crossover cable will be wired: > > 1 ---- 3 > 2 ---- 6 > 3 ---- 1 > 6 ---- 2 $ I read your recent posts about netware 3.X not $allowing the use of the the 0 and 1 subnets. I've always believed $that myself, but when I spoke to a TCP/IP person at Novell the other $day, she told me that the latest 3.12 TCP/IP update would let you use $the 0 subnet if you wanted to. I haven't tried it, but I just wanted $to relay it to you. I know that the latest TCPIP.NLM for 4.10 allows this; actually, if memory serves, the TCPIP.NLM which ships with 4.10 may allow it, too. The latest TCPIP.NLM for 3.1x has some features of the 4.10 version but not all of them, and I don't know if this is one of them. >>>I've rewritten the following section, based on the earlier version. E.5.1 Why It Doesn't Always Work As Expected Internet standards are defined by papers known as RFCs (Request For Comments). Novell's TCP/IP implementation in NetWare versions prior to 4.10 is based on RFC950, which states that no portion of a node's address may consist of all zeroes or of all ones. It has become common practice in recent years to use all-zeroes and all-ones subnets; the latest TCP/IP update for NetWare 3.12, and the TCP/IP stack included in NetWare 4.10, allows the all-zeroes subnet but continues to disallow all ones. The remainder of this answer assumes that neither the all-zeroes nor the all-ones subnets may be used; this is the safest assumption to make in any case because there may be other devices on your network which also follow RFC950. You can logically break down an address into two components where subnetting is not used (the network portion, defined by the address' class; and the node portion), and three components where subnetting is used (the network address; the subnetwork address, which is the difference between the subnetwork mask and the normal mask used for that address class; and the node address). By RFC950, none of those three portions may consist of all zero bits or all one bits. Let's look at an example. Let's say we're subnetting a class B address, 166.166.0.0, into a number of class C-sized subnetworks. We would do this with a subnetwork mask of 255.255.255.0. This yields 254 networks, 166.166.1.0 through 166.166.254.0. We cannot use 166.166.0.0, as the subnetwork portion (the third octet) is all zeroes; similarly, we cannot use 166.166.255.0, as the subnetwork portion is all ones. A more common example, though, is the subnetting of a class C address. Let's use 200.200.200.0 as an example, and say that we want two subnets. Using 255.255.255.128 would result in two illegal subnets - 200.200.200.0, in which the subnetwork portion (the first bit of the last byte 0) is all zeroes, and 200.200.200.128, in which the subnetwork portion is all ones. Therefore, we can't use it. To get two subnets, we must use the mask 255.255.255.192, which gives two valid subnets - 200.200.200.64 (with 62 nodes numbered .65 through .126 inclusive) and 200.200.200.128 (with 62 nodes numbered .129 through .190 inclusive). For subnets of a class C address, your choices are: Mask Number of Subnets Size of each Subnet 255.255.255.0 1 (not subnetted) 254 nodes 255.255.255.128 0 (not allowed) N/A 255.255.255.192 2 62 nodes 255.255.255.224 6 30 nodes 255.255.255.240 14 14 nodes 255.255.255.248 30 6 nodes 255.255.255.252 62 2 nodes 255.255.255.254 0 (not allowed) N/A In Netware 4.10, 255.255.255.128 is allowed, but yields one valid subnet of 126 nodes (so it's pointless), and all lines below it yield one more valid subnet than is indicated above. And a brand new answer on subnets, particularly those of variable sizes: First, a definition. RIP is the traditional routing information protocol used by IP routers to exchange information on networks. RIP predates the concept of subnets, and is incapable of expressing subnetting information. Two newer protocols, RIP II and OSPF, are much more advanced. More on these protocols as we go along. Normally, all subnets of a given address are of the same size. RIP, in a subnetted environment, is therefore usually written to assume that whatever the subnet mask is on a particular interface, it's the same for all other subnets of that interface. This is a bit of a kludge, but it works - if, and only if, this assumption holds true. You can find people who will argue that RIP should never be used, or that it should never be used in a subnetted situation, or that if you're careful, you're OK with it in this case ... There may be cases in which you wish to break a single network address into subnets of different sizes. This is known as using a variable length subnet mask (VLSM). Prior to NetWare 4.10, Novell's TCP/IP stack did not permit this at all. In NetWare 4.10, it is permitted. However, RIP is incapable of handling VLSM. If you need to use a routing information protocol in a VLSM environment, use RIP II or OSPF; these can be configured using INETCFG.NLM. You may not actually need a routing protocol in many cases. Routing protocols are used by router to exchange information about how each other is configured. If you manually configure each router which needs to know, then routing protocols are not needed. This is known as static routing. For example, consider the following network: Internet ----- Router ----------------- Server ---------------- Network A Network B The rest of the world needs to know that networks A and B are both reached through the router. The router needs to know that network B is reached through the server. And the server needs to know that the rest of the world is reached through the router. This information does not change dynamically, and is relatively simple; it can easily be handled by static routes. In fact, if something on the network doesn't handle RIP II or OSPF, and for some reason you've had to use VLSM, then static routing is probably your only option. In this simple example, the need for VLSM is unlikely - but it's not difficult to require VLSM by adding a couple of additional networks, of varying sizes, and having to fit it all into one class C address. >>>Here's an addition to this answer: G.3 Getting garbage in printouts There's also a bug in some versions of RPRINTER which causes a single garbage character to be sent to the printer when RPRINTER is first run. Try upgrading to a current RPRINTER.EXE to cure this. >>>We should mention SYNC.NLM in the following answer. I don't >>>recall exactly where it comes from, though ... H.24 How can I keep my server on time? [add after the usual text for this one:] Another option, if you have one NetWare server which keeps good time or which uses an external time source, is to keep your other servers in sync with it using SYNC.NLM. This NLM periodically polls a given server (the polling interval is adjustable) to get the correct time, and corrects the local server's time if it's not right. It can be configured to take timezone differences into account. >>>A minor adjustment to: H.27 Advantages of purging files In theory, manually purging files on NetWare should not be necessary. Experience has shown, however, that there are advantages to purging. Purging files that are temporary in nature allows other more essential deleted files to have a longer "deleted but not purged" (ie. still salvageable) life. Also, any \TEMP directories, and all print queue directories (those funny numbered ones under SYS:system), should be marked with FLAGDIR as "purgeable" e.g. FLAGDIR Z:\SYSTEM\10000001 PURGE [add the following to the above paragraph] In NetWare 4.x, FLAGDIR was rolled into FLAG, so you'd use FLAG Z:\SYSTEM\10000001 P >>>A correction: I.4.4 Packet tuning [...] Another tip regards NCP searches. I found that the Requester performs better on searching through directories when you increase the "Maximum Outstanding NCP Searches" console set parameter from the standard value of 51 to say, 200 or 300. On NetWare 3.x servers, use SERVMAN NLM to play with it. On NetWare 4.x servers you can use SERVMAN NLM to play with these parameters. [replace the "On NetWare 3.x servers" sentence with] On NetWare 3.x servers, you'll have to adjust this manually with SET commands from the console, and incorporate the end result into your AUTOEXEC.NCF. >>>And we should update the CD-ROM material ... please replace the N.1 question, and the first paragraph of the answer, with: N.1 How do I get to see a CD drive on my Netware v3.12 or higher server? Only SCSI CD-ROMs can be mounted by NetWare straight out of the box. There is an update, CDUP2.EXE, which adds support for ATAPI drives. Treat this update with caution, as it may not be entirely stable. Also, ATAPI CD-ROMs have no place in a serious fileserver, just as IDE hard drives don't. And be forewarned that many older CD-ROM drives which appear to be IDE-like may _not_ be ATAPI drives, but may instead use some proprietary IDE-like interface which is not supported by CDUP2. >>>Replace the first paragraph of answer N.2 with: When mounting a CD-ROM on a Netware v3.12 or 4.0x server, CPU utilization may go to 100% for a long time. This is normal for the original 3.12 CDROM.NLM, but has been at least partially cured in later releases. You should upgrade to the current release (NetWare 4.10 users, as of this writing, have the current release; all others need CDROM3.EXE). ------------------------------ Date: Wed, 14 Feb 1996 11:29:04 -0800 From: steve@sdesign.com (Stephen Herzog) Subject: Request for updates to the NetWare FAQ. 3) It may be nice to combine section G.1 and section G.12 as they cover the same topic. G.1 Printing to/from Unix systems G.12 Transfering print jobs between NetWare and Unix print queues ------------------------------ Date: Mon, 4 Dec 1995 09:29:49 GMT From: Peter McGarvey Subject: Re: conlog.nlm >I use conlog.nlm to capture information from the console screen. I >love it except for one thing: conlog writes to the same file (console.log) >each time. So, if my server crashes I lose whatever information is >contained in the file because of the overwrite. Which sort of defeats >the purpose of having it. Does anyone know of parameters I can set >to prevent this from happening? CONLOG maximum=1024 save=SYS:\ETC\OLD.LOG Now all you have to do is to rename OLD.LOG each time it gets created. I personally send it to a separate directory with the name YYMMDD.LOG --------- From: "Paul Massue-Monat" Date: Tue, 16 Jan 1996 12:51:23 EST Subject: Re: ConLog -- Options or alternatives? I agree with you on the difficulty of conlog. Maybe eventmon.nlm could be of help. It records events but I'm not sure it would record "problems". I haven't tried it myself since I just learned of the nlm one week ago and I didn't have a chance to download it. I discovered it by arriving at this edinburgh web site: http://mft.ucs.ed.ac.uk/novell/techsup/freenlms.htm (they list about a dozen free useful NLMs). From here, it's allways difficult to get to Great Britain: the line is allways slow. Eventually, I'll use archie to find the file eventm.zip closer to me (netlab ? or the netlab mirror in Ottawa at nrc ?). The file eventm,.zip is supposed to contain eventmon.nlm P.S.: Joe is right to compain about the web but I sure would like a search tool at netlab. Those "whatIS" files are so difficult to use, I would love it if he would put up a search facility a la web (just like there is at novell.com). In fact, novell.com is very easy to use these days with a web browser; example: all updates for nw4.1 are in one directory called nw/os/410 or somesuch; the same for 3.11, etc. --------- Date: Fri, 19 Jan 1996 07:21:18 -0800 From: mpierce@danasoft.com (Michael Pierce) Subject: EVENTMON We no longer own this product as we sold it to Citadel System (number 800-962-0701) about a year and a half ago. If you have a specific question I can try to answer it, but we no longer own the rights to the product. DanaSoft, Inc. (703) 257-4650 http://www.danasoft.com --------- Date: Thu, 15 Feb 1996 13:44:30 +0100 From: "David W. Hanson" Subject: Re: CONLOG question [Someone] wanted to know conlog command line switches. ...from the Dyna-Text: LOAD CONLOG [FILE=log filename] [SAVE=backup filename] [MAXIMUM=max file size] [ENTIRE=YES] | HELP Parameter - Use to FILE=log filename - Specify the log file you want to use if you don't want CONLOG to write to the default log file (CONSOLE.LOG). The log filename parameter is used with SFT III servers, whose three engines must each write to a different log file. SAVE=backup file name - Specify the filename in which you want to save the preexisting console log. This parameter enables AUTOEXEC.NCF to load CONLOG without overwriting the previous console log. Use this parameter if you want to examine the old console log for troubleshooting purposes. MAXIMUM=max file size - Specify the maximum size, in kilobytes, of the log file. If the log file exceeds the max file size, it is deleted---or renamed if backup filename was specified. In either case, logging starts over with an empty log file. ENTIRE=YES - Capture the lines already on the screen at the time CONLOG is loaded. Without this parameter, CONLOG starts logging with the next output to the console after it is loaded. HELP - View a description of each CONLOG command parameter ------------------------------ Date: Thu, 08 Feb 1996 10:43:23 -0800 From: Marcus Williamson <71333.1665@Compuserve.com> Subject: NETW4X.FAQ You might like to mention two programs which may help in sections H.25.2 and H.7 of the FAQ. Memory calculation : SMEM.EXE REGISTER MEMORY calculation : REGMEM.EXE Both these, and NETW4X.FAQ, previously only in the CompuServe forums, are now available at : http://ourworld.compuserve.com/homepages/marcus_williamson I'd appreciate if you could add this to your FAQ references. The file includes many FAQs have been gathered from the CompuServe forums, Usenet and customer contact. Many of the Qs & As do not appear anywhere else in existing FAQ material. ------------------------------ Date: Fri, 19 Jan 1996 15:05:23 -0500 From: bhatia@chelsea.ios.com (Deepak Bhatia, Master CNE) Subject: Possible Addition to the FAQ How about a new section for the FAQ - Online Learning Centers: Cyber State University: ----------------------- Offer online virtual classes which combine Video, interactive chats with students, reading from the CNE guide for NetWare 4.1, testing and hands on lab exercises. To check this out call (510) 253-TREK MOLI: ----- The Microsoft Online Institute is an online interactive learning and information resource available on MSN, the Microsoft Network online service, to Windows 95 users. Using a campus paradigm, MOLI provides online access to learning materials, instructor expertise, product information, developer articles, user forums, and other resources for Microsoft product and technology information. In addition, MOLI provides information about all Microsoft training options. For more details go to Microsoft page on the World Wide Web at: http://www.microsoft.com/moli ------------------------------ Date: Wed, 27 Dec 1995 00:24:59 +1000 From: Richard Phillips Subject: H.37 Negative numbers from CHKVOL -- yup, time to worry H.37 Negative numbers from CHKVOL -- yup, time to worry -> With Netware 4.x "chkvol" is replaced with "ndir /vol", and this has been known (by me at least) to show some weird figures with 4.02 and 4.1 so you may not actually have to worry or run vrepair. If this worries you, get the latest version of ndir.exe from netwire at "ftp.novell.com/pub/updates/nwos/nw410/41ndir.exe" which appears to have fixed these problems. Although it's in the 4.1 update directory, this works with 4.02 as well as 4.1, and should work with all other older versions of 4.x although I'vce only run it with 4.02 and 4.1 Nwadmin has also been known to show weird figures, particularly with reference to compressed space and percentages - and "they're working on it". ------------------------------ Date: Tue, 26 Dec 1995 23:58:18 +1000 From: Richard Phillips Organization: McIntosh & Company Subject: H.6 Changing the number of licenced users on a Netware server H.6 Changing the number of licenced users on a Netware server Netware 2.x - requires a full "netgen" Netware 3.x - as already in FAQ, just replace server.exe Netware 4.x - the license is separate to the server.exe file. To increase or decrease the number of licenses is a matter of adding or deleting the license.mls file via install.nlm from the server console. With Netware 4.0x you may replace the current license via install.nlm, and with Netware 4.1 you may delete the previous license and/or add additional licenses. If you have two 50 user 4.1 licenses, for example, you can now create a 100 user server. If you have one 100 user license, however, you cannot split it into smaller units (at the moment) unless you can find someone to swap the license with for an equivalent number of smaller blocks of licenses. ------------------------------ From: "Rob Waterlander" Date: Thu, 14 Dec 1995 09:32:55 -01:0 Subject: NOVELL FAQ Contribution I have set password expiration on my user accounts and in request of the users I wanted to warn them a week before their password expires. In order to do so I made something within the login script like: if PASSWORD_EXPIRES<="08" then begin ... Basically this seems to work, but it also warns at 57 days, etc. Because we didn't want our users to see the warning every time they login to the system (they will not see it anymore after a few days) this wasn't a good solution. (Btw we also tried if %PASSWORD_EXPIRES<="..) I found within the NSEPro that in order to use this you have to but the word VALUE before PASSWORD_EXPIRES to get a value. So now my login script says: if VALUE PASSWORD_EXPIRES<="08" then begin Write " Your password expires within %PASSWORD_EXPIRES days" Write " " Write " You can wait %PASSWORD_EXPIRES days, after with the system" Write " will ask for a new password or, if you already know a new" Write " password then you can type SETPASS at the C:\> to change it" Write " " FIRE PHASERS 3 end [Thanks to Rob Waterlander and the NSEPro for this info] ------------------------------ From: Steven M. Dunn Subject: NetWare FAQ comments Date: Fri, 27 Oct 95 9:49:54 EDT >>G.8 Alternatives to PSERVER for more than 16 printers, etc. > > Again, NetWare 4 relieves this, by allowing PSERVER to handle > lots (255, if memory serves) of printers. OK, I was wrong. It's 256 :-) >>Alternatively, *FOR NETWARE 2.X SERVERS ONLY*, you can try the following: [...] > This isn't right; there are only two bindery files in 2.x. > Darn if I can remember 'em, though ... again, I *think* the Hacking > FAQ has 'em. NET$BIND.SYS and NET$BVAL.SYS are the two files for 2.x. >>H.24 How can I keep my server on time? [...] > 2. If you have one NetWare server which you keep set with the > correct time, you can have other 3.x servers follow its time using > SYNC.NLM (available from somewhere on Compuserve ... I'll try to > dig up the reference to it). ftp://ftp.novell.com/pub/netware/novuser/07/sync.zip; I expect that's the same directory it's in on CompuServe, too. RDATE.ZIP is also in this directory, for those who wish to sync their time to a known time source via TCP/IP. ------------------------------ I also have a few proposals, it could be worth to mention in section E.7 (BOOTP and RARP): In LAN WorkPlace or -Group (and the TCPIP in VLM Client Kit) if you use 'ip_adress 0.0.0.0' in NET.CFG it will first look for a BOOTP-server, if no bootp server respond it will look for a RARP-server. In F.3 (Mercury): You could mention that Mercury also have a function as 'Mail Server' with SEND 'filename', INDEX, LOOKUP, .... it also can act as a (simple) 'List Server' with SUBSCRIBE, UNSUBSCRIBE, then you have to dedicate a PC running Pmail 24h, and use filtering to handle in/out going mail to the list. Steen Rahbek ------------------------------ Your search on (novell) produced 16 matches: CIN-NOV Personale interno del CINECA interessato alla rete NOVELL mail the phrase info CIN-NOV to LISTSERV@ICINECA.CINECA.IT GRPWISE -GRPWISE - McGill Novell Groupwise Redistribution List mail the phrase info GRPWISE to LISTSERV@VM1.MCGILL.CA MLA-NOV Discussion of Novell-MLA-specific issues in Austria mail the phrase info MLA-NOV to LISTSERV@helios.edvz.univie.ac.at netw4-l Discussion of Novell Netware 4.x Network Operating System mail the phrase information netw4-l to listproc2@bgu.edu netware Discussion of Novell Netware administration mail the phrase info netware to majordomo@acpub.duke.edu NETWARE-L Novell netware list mail the phrase information NETWARE-L to listproc@cornell.edu novell Novell Discussion List mail the phrase information novell to listproc@mailer.fsu.edu novell Novell Information List mail the phrase info novell to Majordomo@mcc.ac.uk NOVELL Novell LAN Interest Group mail the phrase info NOVELL to LISTSERV@LISTSERV.SYR.EDU novell-support Novell Support Helpline mail the phrase info novell-support to Majordomo@mcc.ac.uk NOVUSRGP West Virginia University Novell User Group mail the phrase info NOVUSRGP to LISTSERV@WVNVM.WVNET.EDU nuglist Network/Novell Users' Group mail the phrase info nuglist to Majordomo@indiana.edu nwp Novell NetWare Programming mail the phrase information nwp to listproc@lists.pipex.com ( There is a Novell Programming mailing list at: nwp@uel.ac.uk Send subscription messages to: listproc@uel.ac.uk ) ostsnovell "OSTS Novell Admin List" mail the phrase information ostsnovell to listproc@lists.Colorado.EDU ua-novell-l University of Arizona Novell List mail the phrase information ua-novell-l to listproc@zippy.telcom.arizona.edu uci-novell Discussions regarding Novell at UCI mail the phrase information uci-novell to listserv@uci.edu --------- Your search on (netware) produced 6 matches: netw4-l Discussion of Novell Netware 4.x Network Operating System mail the phrase information netw4-l to listproc2@bgu.edu netware Discussion of Novell Netware administration mail the phrase info netware to majordomo@acpub.duke.edu NETWARE-L Novell netware list mail the phrase information NETWARE-L to listproc@cornell.edu nw-managers Leicester University NetWare Systems' Managers mail the phrase information nw-managers to listserver@leicester.ac.uk nwp Novell NetWare Programming mail the phrase information nwp to listproc@lists.pipex.com nwusers UTS Netware Users Discussion List mail the phrase info nwusers to Majordomo@uts.edu.au ------------------------------ : Does any one know where I can find a list of Netware API calls : declaration for Visual Basic if there is one? TIA! Joseph Devito has written some vb definitions to Netware. You can find them at ftp.shu.edu in /pub/nw41/nw41bas.exe. Bengt Bolinder ------------------------------ Date: Wed, 25 Oct 1995 10:33:11 -0500 From: "Rodney F. Clay" Subject: Re: Mercury, Pmail and Novell 4.1 >I am trying to configure mercury 1.21 on my Novell netware server 4.1. >I have created spool directory on the server and created my mercury.ini >file. However, when i send email from mercurys screen server that my job >has been aborted. Does anybody on the net knows what is going on. I need >to configure this server this week. I've created a page on my server documenting how I install Mercury and have it interface with Pegasus Mail: http://vasquez.csd.sc.edu From the initial page, go to WHAT'S AVAILABLE->NETWARE. The information you are needing will be at the bottom of that page. Do you have TCP/IP functioning on the server? Is the path to the Spooler directory correctly specified in MERCURY.INI? Is the MERCURY.INI file in the correct location? ------------------------------ From: "Henrik Olsen" Date: Tue, 24 Oct 1995 01:09:47 GMT+0100 H.24.1 What is my TIMEZONE? Netware's TIMEZONE variable works backwards from the rest of the world. The default timezone is US Eastern Standard Time, GMT-500 which has TIMEZONE=EST5EDT. For Eastern Australian Standard Time, GMT+1000, it's TIMEZONE=EAT-10EDT. For Central Australian Standard Time, GMT+930, it's not supported on NetWare 3.1x servers - only whole hour zones are allowed. TIMEZONE must be SET before loading CLIB. [Thanks to Gordon Keith for this info] All timezones mentioned are ok when it's daylight savings time. When not, the last three letters should be removed to remove the additional 1 hour offset they give. This should be mentioned since many countries (at least Denmark where I am) are not using daylight saving in the winter:). Perhaps it might also be an idea to mention that RDATE don't care what the three letters are before and after the timezone number as long as they are there. Henrik Olsen ------------------------------ ftp://ftp.coast.net/SimTel/msdos/editor/tsejr4.zip 199743 bytes SemWare announces a NEW version of QEdit, now called: The SemWare Editor Junior v4.0 In its 4.0 release, SemWare's classic QEdit line of editor products has undergone impressive improvements. And with this release, the name has been changed to The SemWare Editor Junior. (This name change was necessary to resolve a conflict over the "QEdit" name.) In keeping with the long-acclaimed heritage of SemWare's QEdit software, The SemWare Editor Junior (TSE Jr.) maintains QEdit's familiar features, such as small program size, ease of use, quick speed, multi-file/window editing, access to commands from pull-down menus, and a versatile macro scripting language. Version 4.0 adds a number of features, including: built-in mouse support, incremental search capability, synchronized scrolling option, file locater and directory tree utilities, support for line lengths up to 2032 characters, and the ability to copy and paste text to/from the Windows Clipboard (or the OS/2 Clipboard in the OS/2 version). The SemWare Editor Junior (TSE Jr.) is available in its standard DOS version, as well as in a memory-resident version, and a version for OS/2. tsejr4.zip replaces qedit3c.zip and previous qeditxxx.zip files. Author, Sammy Mitchell. Kyle Watkins (SemWare Support) SemWare Corporation 4343 Shallowford Rd, Suite C3A, Marietta GA 30062-5022 USA Voice: (770) 641-9002 FAX: (770) 640-6213 BBS: (770) 641-8968 kyle.watkins@semware.com http://www.semware.com CIS: 75300,2710 ------------------------------