From: IN%"reitsmac@DENISON.BITNET" 8-JAN-1993 09:44:10.04 To: IN%"NOVELL@SUVM.BITNET" "Multiple recipients of list NOVELL" CC: Subj: RE: Burst Mode Return-path: Received: from VM.BYU.EDU (YMAIL@BYUVM) by CC.USU.EDU (PMDF #2458 ) id <01GT9SEHSGOW92A6SI@CC.USU.EDU>; Fri, 8 Jan 1993 09:43:03 MDT Received: from BYUVM.BITNET by VM.BYU.EDU (Mailer R2.08 R208004) with BSMTP id 4675; Fri, 08 Jan 93 09:40:25 MST Date: 08 Jan 1993 11:24:54 -0600 (CST) From: Charlie Reitsma Subject: RE: Burst Mode Sender: NOVELERR@SUVM.SYR.EDU To: Multiple recipients of list NOVELL Reply-to: reitsmac@DENISON.BITNET Message-id: <01GT9SFAS33U92A6SI@CC.USU.EDU> Content-transfer-encoding: 7BIT X-To: novell@suvm.bitnet >Does this newsgroup have an archive containing >old mail? Can anyone direct me to it? There was a request a while back for information about how to query the NOVELL LISTSERV for previously answered questions. It was hoped that people would take the time to look up past questions/answers so that the same question wasn't being answered over and over again. The full documentation on this subject comprises some 30 pages. It covers both an interactive query and mail query method. I've never taken the time to download and setup the files needed for the interactive query method so all I can cover is the mail query method. And I won't cover the whole topic...just the parts I use. I think I've gleaned the most useful parts for presentation here. Those interested in the full text can get it by sending a message to the LISTSERV (LISTSERV@SUVM.BITNET). No subject is needed and the message must be: GET LISTDB MEMO It can also be gotten via anonymous ftp from info.umd.edu in the directory info/Computers/NetInfo/Listserv. The file is named listdb-memo. The practical example I will use for this is my recent attempt to answer the question `How can I get remote boot to work on a workstation using DOS 5 and the ODI drivers?' QUERYING THE LISTSERV DATABASE VIA MAIL MESSAGES The process is simple to describe. You send a mail message to the LISTSERV of your choice (for NOVELL it is LISTSERV@SUVM.BITNET) and the LISTSERV responds with information. The mail message you send must constitute a valid Listserv Command Job Language Interpreter (CJLI) command file. Luckily for us you only need two basic skeletons of the command file to answer the question `Has this topic been covered before?' The first skeleton is the SEARCH: // Database Search DD=Rules //Rules DD * Search 'remote boot' in NOVELL Index /* The message begins with two forward slashes (//) and ends with slash-star (/*). The line: Search 'remote boot' in NOVELL is the only line that ever needs changing. You put what you are looking for in quotes followed by the name of the List to search. The Listserv searches the subject line and message text of every message in its database and returns to you an index number, date and subject line of every message containing the search string. [If you are searching for a single word you do not need quotes. Single quotes (') are different from double quotes ("). Single quotes uses case- insensitive searching; double quotes searches for an exact match of what you type.] You can refine your search by adding extra search lines and leaving off the `in NOVELL' part. Below is the exact message I sent to LISTSERV@SUVM.BITNET to answer my question: `How can I get remote boot to work on a workstation using DOS 5 and the ODI drivers?' // Database Search DD=Rules //Rules DD * Search 'remote boot' in NOVELL Search ODI Index /* This command file asks the Listserv to search the NOVELL database for all occurrences of `remote boot.' The second search line asks it to search only those messages matching the first search for the word ODI. Here's the response I received from the Listserv: > Search 'remote boot' in NOVELL --> Database NOVELL, 260 hits. > Search ODI --> Database NOVELL, 66 hits. > Index Item # Date Time Recs Subject ------ ---- ---- ---- ------- 000898 91/11/20 15:42 33 Western Digital (SMC) with Boot Rom 000984 91/11/22 09:36 69 Re: Western Digital (SMC) with Boot Rom 001704 91/12/09 08:23 26 Re: Problem with boot rom 001758 91/12/09 21:52 13 Boot rom with Lan Workplace 003079 92/01/16 12:56 53 Re: dos5 and novell 003442 92/01/23 10:57 23 REMOTE BOOT ( with LSL and ipxodi) 003578 92/01/27 09:55 29 Re: REMOTE BOOT ( with LSL and ipxodi) 004169 92/02/07 13:05 18 RE: remote boot with emm386.exe 004195 92/02/07 11:44 23 Re: remote boot with emm386.exe 004460 92/02/12 17:45 57 RE: simultaneous Netware and VAX conn. 004571 92/02/14 16:50 54 RE: simultaneous Netware and VAX conn. 004598 92/02/14 08:18 56 RE: simultaneous Netware and VAX conn. 006773 92/04/01 15:21 15 Remote booting and ODI 006775 92/04/01 08:53 20 Re: Remote booting and ODI 006826 92/04/01 12:02 19 Re: Remote booting and ODI 006907 92/04/02 14:58 28 Re: Remote booting and ODI 006910 92/04/02 18:06 22 Re: Re: Remote booting and ODI 006917 92/04/02 16:10 16 Re: Remote booting and ODI 006932 92/04/03 09:03 22 Re: Re: Remote booting and ODI 006988 92/04/04 08:40 28 Re: Remote booting and ODI 006989 92/04/04 12:13 31 Re: Remote booting and ODI 007455 92/04/15 19:44 31 Re: MS-DOS 5.0 DOSGEN problems 007818 92/04/23 14:16 22 FRED 007840 92/04/23 13:43 23 remote boot and odi 007873 92/04/24 09:49 50 RE: remote boot and odi 008168 92/04/30 21:12 39 Re: remote boot and odi 008178 92/05/01 10:15 52 Re: remote boot and odi 008519 92/05/08 00:52 34 Re: remote boot and odi 008756 92/05/12 13:04 21 pcn2l odi remote boot 009348 92/05/24 17:00 20 remote boot with odi 011082 92/07/03 08:58 65 Re: WIN vs OS/2 011289 92/07/09 17:41 61 Re: Help needed: RPL+DOS5+ODI+IBM E-net/ 011586 92/07/16 17:30 38 Re: remote reset w/ODI 011691 92/07/19 16:14 647 Windows vs. NetWare Troubleshooting Tips 011936 92/07/23 19:30 28 Re: Remote boot in an academic setting 011942 92/07/23 18:13 29 Re: Re: Remote boot in an academic sett 011971 92/07/24 09:31 45 Re: Remote boot in an academic setting 012248 92/07/30 12:03 30 Re: Need Driver for PCN-006 012620 92/08/07 10:15 22 Remote Boot with ODI drivers 012680 92/08/10 09:50 46 Re: Remote Boot with ODI drivers 012713 92/08/11 19:47 232 Re: Setting up Windows on Lab Machines 013109 92/08/19 12:20 22 Remote Boot DOS5.0 problems 013143 92/08/19 12:37 39 RE: Remote Boot DOS5.0 problems 013222 92/08/21 10:39 29 Re: Remote Boot DOS5.0 problems 013344 92/08/25 13:31 67 Re: Setting up Windows on Lab Machines 013504 92/08/28 15:53 53 Re: Help needed: RPL+DOS5+ODI+IBM E-net 013692 92/09/01 17:01 56 Setting up Printer server (pserver) 013756 92/09/02 17:03 42 Re: Remote Boot DOS5.0 problems 013801 92/09/03 11:21 20 Re: Remote Boot DOS5.0 problems 013816 92/09/03 09:21 36 Re: Remote Boot DOS5.0 problems 013830 92/09/03 08:04 31 Re: Remote Boot DOS5.0 problems 014550 92/09/16 22:23 69 RE: remote boot / dos5 and xt's 014614 92/09/17 13:18 20 RE: remote boot / dos5 and xt's 015107 92/09/26 21:54 521 [SUMMARY]:NW31,WIN31,MAC,PRINTING 2/2 015770 92/10/08 18:11 25 NI5210, ODI, and Remote Boot ?? 015922 92/10/09 15:41 77 Re: help on implementing internet & tcp 016070 92/10/13 09:29 55 Re: help on implementing internet & tcp 016511 92/10/22 07:22 37 Compex 16 combo and remote boot 016856 92/10/28 21:55 36 Re: Remote boot and TCP, together ? 016911 92/10/29 18:49 93 Re: Remote boot and TCP, together ? 017360 92/11/06 23:03 43 Re: ODI remote booting with SMC cards 017367 92/11/06 19:52 23 ODI remote booting with SMC cards 017633 92/11/12 08:12 19 018328 92/11/23 22:27 56 Re: Windows on NW3.11 addicted to a: drive 018721 92/12/01 13:07 51 re: IBM Token Ring Boot ROMs 020340 92/12/30 23:04 36 Re: Cannot run RPL on baseband The subject lines of the messages let me see whether or not the subject has been discussed but I needed to get the messages themselves to determine if my question had been anwered. [Listservs default to spending no more than 60 CPU seconds on any job and sending only 2000 lines of output. These limits can be modified from within the job but I'll let you get the full description if you find the defaults too limiting.] The second CLJI skeleton is a variation on the search CLJI command file. // Database Search DD=Rules //Rules DD * Search 'remote boot' in NOVELL Search ODI print all /* The change is substituting the `print all' part for the `Index' part. `All' refers to database portions not the messages found to contain the search strings. You have to repeat the search lines to extract the pertinent messages from the database. Knowing that the output is limited to just 2000 lines you might choose to list only some of the messages. Here's what I used: // Database Search DD=Rules //Rules DD * Search 'remote boot' in NOVELL Search ODI print all 3079 3442 3578 4169 4195 6773 6775 6826 6907 6910 6917 6932 6988 print all 6989 7840 7873 8168 8178 8519 9348 11289 11586 12620 12680 13109 print all 13143 13222 13504 13756 13801 13816 13830 /* As you look at that the thought might have occurred to you that it would be nicer to tell it to just print all the messages that had 'remote boot' in the Subject line. Then you would not have to list all those numbers for the individual messages you want to see. Well, it's possible. You can ask search to limit it's search to any of these database portions: Date, Time, Recs, Sender, Subject, and Text. [The documentation says each list may define other keywords but offers no method for querying the Listserv to get a list of the keywords. It offers these keywords as available in any Listserv.] // Database Search DD=Rules //Rules DD * Search * in NOVELL where Subject contains 'remote boot' Search ODI print all /* The first search line extracts only those messages containing `remote boot' in the Subject line. The second search line trims the messages to just those with `ODI' anywhere in the message. The print line then tells the Listserv to send me all the contents of the resulting messages. I won't list all the output here (1354 lines) but I will go on and answer the question: `How can I get remote boot to work on a workstation using DOS 5 and the ODI drivers?' It seems that everyone asking the question had successfully set up ODI on at least one workstation. So they knew about LSL, some_specific_device_driver, IPXODI, NETX, NETCFG and even ODIPKT. The only problem they had was that remote boot failed. A few answers were really unhelpful: `Sure, I do it all the time.', for example. At least now the whole list knows who this person is and can attempt to get more information from him/her. Several answers mentioned RPLFIX.COM required to get the remote boot to work with DOS5 and RPLODI required to get the remote boot to work with ODI. This was useful information. But I knew all that and it still didn't work for me. The really helpful information came from those who took the time to list their CONFIG.SYS, AUTOEXEC.BAT and NET.CFG files. What I discovered was that I needed to rearrange the order of my FRAME and PROTOCOL statements in my NET.CFG file. Doing that required that I change the `logical board parameter' on my ODIPKT command line from 0 to 1. With those fixes the RPLFIX'd DOSGEN'd image remote boots fine and provides more conventional memory than my previous Packet Driver/IPX image. Here's my final setup: CONFIG.SYS ---------- FILES=40 BUFFERS=40 DEVICE=HIMEM.SYS DEVICE=EMM386.EXE 2048 m9 ram DOS=HIGH,UMB SHELL=COMMAND.COM /P /E:512 AUTOEXEC.BAT ------------ clus2odi CLUS2ODI.BAT ------------ @echo off SET CLU=2 PROMPT $p$g loadhigh LSL loadhigh RPLODI loadhigh NE2000 loadhigh IPXODI loadhigh ODIPKT 1 96 ;had to change parameters from `0 96' to `1 96' loadhigh NETX go NET.CFG ------- Link Driver NE2000 INT 5 PORT 320 ; I used to have Frame Ethernet_802.3 ;Frame Ethernet_II Frame Ethernet_II ;Frame Ethernet_802.3 Protocol IPX 0 Ethernet_802.3 ;Protocol ADD 1234 Ethernet_II Protocol ADD 1234 Ethernet_II ;Protocol IPX 0 Ethernet_802.3 show dots = on all servers = on file handles = 40 local printers = 0 netbios broadcast ; I don't know why I have these 4 lines here count = 5 ; other than they were in an example netbios broadcast ; net.cfg I saw. delay = 10 ; preferred server = SUPERCLUSTER There was also plenty of other information that didn't seem related to my problem: a fight broke out about boot-roms getting out of date and needing to be upgraded with every new version of DOS and Netware; some said that all the files had to be in the LOGIN directory (to-date the only files required in my LOGIN directory are the batch file containing NETX and any program that loads after NETX.); and some information relating to Windows that I will file away until I'm ready to load it on the network. Charlie Reitsma reitsmac@cc.denison.edu