Full instructions for installing "stealth digi" on a PC. The Stealth.zip file contains a dual port setup, addressed to look for and use two tnc's (in KISS mode) on com 1 and com2. This configuration is in no way the largest it can be, but its a start for those of you that dont want to "mess" with a bunch of settings right now. When I made this zip file, I had installed this on a single 3.5 720K diskette, so this could even run on a older laptop! with no harddrive. Below are the files contained in the ZIP and I'll describe their function and placement, in case you want to install this on a hard drive instead. AUTOEXEC.BAT BPQCFG.BIN BPQCFG.EXE BPQCFG.TXT BPQCODE.EXE BPQNODES CONFIG.SYS F.BAT README.TXT S.BAT W0RLI/CFG/DIGI.INI W0RLI/CFG/DIGI.LNK W0RLI/CFG/DIGIAPRS.INI W0RLI/CFG/DIGIHF.INI W0RLI/EXE/DIGI.EXE LOGS/STARTUP.LOG --------------------------- Autoexec.bat @ECHO OFF PROMPT $p$g SET TEMP=A:\ SET RLIEXE=A:\w0rli\exe SET RLICFG=A:\w0rli\cfg SET RLILOG=A:\w0rli\logs bpqcode cd\w0rli\exe digi cd\ this file contains the settings I use to boot into "stealth DIGI". Notice the SET statements. If your going to use this on a hard disk, change the reference to A: to be C: (or what ever drive you want it to be). BPQCODE is the G8BPQ tsr that gets loaded into memory. Your returned to DOS after it loads. DIGI.exe, in W0RLI\exe directory is the actual stealth program. In any case, the sequence as shown here will need to be followed. Make sure the SET statements are in the AUTOEXEC.BAT of the boot up drive (C: or A:). Also it doesnt hurt to leave these SET statements in your autoexec even when your not running stealth. -------------------------- BPQCFG.BIN This is a run time binary "settings" file that gets created after you change settings for G8BPQ in BPQCFG.TXT and you "convert" the BPQCFG.TXT file into a binary file with BPQCFG.EXE. You dont have to, but on my stealth, I have all the BPQ stuff in a BPQ directory. Make sure any references to the BPQ stuff specifies the directory you have it in. -------------------------- BPQCFG.EXE Once you have edited any changes, and yes, you will want to edit the BPQCFG.TXT file to place your own callsigns in, run BPQCFG.EXE to "convert" the settings into the above BPQCFG.BIN file. You dont have to, but on my stealth, I have all the BPQ stuff in a BPQ directory. Make sure any references to the BPQ stuff specifies the directory you have it in. ------------------------- BPQCFG.TXT This file contains the settings that describe the TNC and its settings. Baud rates, callsigns for BPQ's node software are in this file. After changing the settings, make sure you run BPQCFG.EXE to convert this to a binary file. ------------------------- BPQCODE.EXE This is the G8BPQ node TSR. It reads the BPQCFG.BIN file and loads itself, sets up com ports, and then returns to DOS. Usually the BPQCFG.BIN file resides in the same directory as this file. ------------------------ CONFIG.SYS DEVICE=C:\DOS\HIMEM.SYS DEVICE=C:\DOS\EMM386.EXE NOEMS BUFFERS=15,0 FILES=30 DOS=UMB LASTDRIVE=E FCBS=4,0 DEVICEHIGH /L:1,12048 =C:\DOS\SETVER.EXE DOS=HIGH Nothing special about the config. I had to include it, since this zip file makes a boot disk (less the actual MS-dos sys files) with all the settings. Obviously, the reference to the DEVICE statements need to be corrected to reflect how your going to install this. Dont sweat if you dont use the HIMEM and EMM386 stuff - Stealth and BPQ only use the bottom 128K of memory anyway. ------------------------- F.BAT a: cd\w0rli\cfg edit digi.ini CD\ This is just a simple batch file I set up to "edit" DIGI.INI file. It calls "EDIT A:\W0RLI\CFG\DIGI.INI" and when done returns back to the root directory. I call this F for "Fix" the settings. Easy to remember, right? You dont have to have this - I just made it to allow for "quick" settings changes. ------------------------- Readme.txt A quick and simple explaination about stealth. This file was a quick setup reply to a user I configured stealth for. Here is the readme.txt file as in Stealth.zip --- Install notes for Stealth Digi. By Byron Smith WA6YLB Email me at wa6ylb at theworks.com This is a fully functional setup for the stealth digi, which runs on any kind of IBM PC compatible PC. (XT Too!) This version has been installed on a single floppy and boots from A drive right into Stealth digi. You can run this on a hard disk if you like, but make sure the SET commands and the W0RLI directory exists. If you attempt to place all the files in a single directory, you'll get a "null pointer error" and Stealth digi wont work. 1. Make a boot able floppy. From drive C: , type SYS A: 2. copy the stealth.zip file to A:\ 3. PKUNZIP the file, and make *sure* you use the -d option: PKUNZIP -d stealth The G8BPQ files all can be in a single directory, but the W0RLI software must have a directory structure. Make sure this exists. The program expects to be able to find programs with in a directory and subdirectory of \W0RLI\xxx directorys. The S.bat file allows you to restart DIGI after getting out of it with F4 key. The F.bat command allows you to "edit" the DIGI.INI file to adjust settings. The SET commands in the AUTOEXEC.BAT file must be moved to the AUTOEXEC.BAT file found on C:\ if you plan on running Stealth digi from the hard drive. These SET statements must be involked to allow DIGI to find the files to run with. This program will operate with a single TNC , in KISS mode, if you desire. I have also used this with a HF TNC in KISS mode, adding a gateway port to the local APRS net. The BPQCFG.TXT file must be modified for the callsigns etc you plan on using. After doing this, run BPGCFG.EXE which converts the BPQCFG.TXT file into a binary run time file. If you plan on having more serial ports than two, you must use different IRQ's numbers for the third and fourth COMM ports other than IRQ 4 and IRQ 3, which are typically associated with COMM 1 and 2 respectively. The Stealth digi does alias callsign swapping. This is true even for HF use on one of the ports. When the Stealth digi is running, from another packet station, try connecting to the MYCALL callsign, and then do a C DIGI. You'll be suprised in what you see. The G8BPQ software will still run as a NODE, if the equates are set properly. Email me about IRQ's for more than two ports... ------------------------ S.BAT a: bpqcode cd\w0rli\exe digi cd\ This file invokes DIGI after I just edited the DIGI.INI file. It trys to reload the G8BPQ TSR, (which usually says its already loaded), and then invokes DIGI. ------------------------ W0RLI\CFG\DIGI.INI This file contains all the settings for the Stealth. All aliases, and paths for digipeated packets are contained in this file. DIGI.EXE uses this INI file without converting to a binary file like BPQCFG.TXT did. Examples of digipeat statements are in this file. You *must* edit this file to suit the APRS activity in your area. Lines beginning with ; are comment lines. I'm going to add comments to this file starting with ;-->, so you will know this is my comments here. The ;--> doesnt exist in the DIGI.INI file, but is something I'm doing in this file now. ; custom made for wa6rke-1 in morrow bay. ;--> see why this needs to be changed for your area? ; * Place this file with your other .ini files. ; * I'm running DIGI.EXE in a 45K window. ; * The numbers in the Digipeat lines represent node ports. ; Change to match your rf port numbers. ; * Wild cards: ; Wildcards may be used to match the incoming callsigns. ; * Matches any 0 or more character(s). ; ? Matches any 1 character. ; @ Matches any alpha character. ; ! Matches any digit. ;--> Digi can be setup to match characters in callsigns and aliases. neet? ;--> some common ones are WIDE* and APR*. Becareful of doing this as some callsing fields ;--> use things like GPSLJ and MIC-e's use random characters in their "to:" field. ; * Include the contents of a file: ; The '@' reference in the Send: line means to send the ; current contents of that file. ;--> This is something interesting. Beacon position and BEACON status text are ;--> stored as a disk file! DIGI just sends the text thats stored in the file names ;--> below ; * Port List: ; A comma separated list of port numbers "1,3,5,7" or "All" or "AllBut". ; "All" means all switch ports. ; "AllBut" means all switch ports EXCEPT the port where the frame was heard. ; Port numbers refer to the G8BPQ hardware ports (TNCs), ; as shown by the switch P command. ; Used to specify receive or transmit ports. ;--> the ports are referred to in BPQCFG.TXT file. In other words, port 1 in BPQ = port ;--> in this DIGI.INI. In this configuration, COMM port 1 is port 1, COMM port 2 is ;--> port 2. ; * Call List: ; Comma separated list of callsigns. ;--> use commas to separate CALLSIGNS. ; * Alter the digipeater list: ; Be very careful if you use more than one option to specify ; how frames will be repeated between a given pair of switch ports. ; Repeat a frame if we are next in the digipeater list. ; Use "Digipeat:". Assume we select on a digipeater field of WIDE. ; For incoming frame: A>B,C,D*,WIDE,E,F ; gives: A>B,C,D,W0RLI-1*,E,F ; Add X,Y gives: A>B,C,D,W0RLI-1*,E,F,X,Y ; Replace X,Y gives: A>B,C,D,W0RLI-1*,X,Y ; New X,Y gives: A>B,W0RLI-1*,X,Y ;--> I haven't used REPLACE, but you see how its used. ; Repeat a frame if we heard it from it's last digipeater. ; Use "DigiEnd:". Assume we select on a digipeater field of W6APA. ; For incoming frame: A>B,C,D,WIDE,E,W6APA* ; New X,Y gives: A>B,W0RLI-1*,X,Y ;--> DIGIEND is used to "pick up" a packet that died due to lack of ;--> any more path. This is useful when seeing a packet come a couple hops, such ;--> as the beacon of a distant digi, picking it up and ADDING more path to ;--> it and resending it out. ; Repeat a frame if it has a desired TO field, and 0 or more digipeaters. ; Use "DigiTo:". Assume we select on a to field of APRS. ; For incoming frame: A>APRS,A,B*,C,D,E ; New X,Y gives: A>APRS,W0RLI-1*,X,Y ;--> Digito: came about because we had a NODE that beaconed the digi path ;--> to its OWN callsign. (this node had a APRS formatted POSITION beacon in it) This ;--> allows you to specify the TO: callsign, and allow you to "capture it" and ;--> apply paths to it as described above. ; Repeat a frame if it has a desired TO field, and no digipeaters. ; Use "Echo:". Assume we select on a to field of ID. ; For incoming frame: A>ID ; Via X,Y gives: A>ID,W0RLI-1*,X,Y ;--> useful for picking up a packet with no digis on it at all. ;--> some settings are CQ, ID and BEACON . ; * Note that the node callsign replaces any alias or callsign ; used to digipeat, or is added into the digipeater list as ; required to allow DIGI to detect potential digipeat loops. ; e.g. (WIDE,WIDE,WIDE) ;--> yes, this Stealth does callsign swapping, and wont repeat its own packet. Send: From 0 to 23 Each 19 At 1 1 WA6RKE-1 APRS WA6RKE-3,WIDE @\w0rli\cfg\digiaprs.ini EOF Send: From 0 to 23 Each 20 At 5 2 WA6RKE-1 APRS WA6BRW-10,K6TZ-10,KB6TLJ-5,WIDE,WA6YLB-3 @\w0rli\cfg\digiaprs.ini EOF :--> these are where Stealth gets the position beacon text. You can have multi path beacons ;--> if you want. the format for the setting reads as follows [using the data in the ;--> first SEND above]: ;--> SEND beacons from 0000 hrs thru 2300 hours(as per the PC clock), starting 19 minutes ;--> after the beginning of each hour, and delayed by 1 minute ;--> (makes a 20 minute beacon - see?) out port 1 ;--> with the MYCALL of OF wa6rke-1 (THATS THE MYCALL OF THIS STEALTH) to "APRS" (notice no ;--> "via" here, (its implied) using the path of WA6RKE-3,WIDE. SO what actually is sent is: ;--> :--> WA6RKE-3>APRS,WA6RKE-3,WIDE:contents of file digiaprs.ini ;--> you could cause beacons to only be sent at certain times of the day if you wanted. ; Digipeat frames with these digipeater calls. digipeat: 1 local 1 ;--> digipeat the alias of "local" from port one back out onto port 1. dont add anything. digipeat: 1 worm 2 ;--> digipeat this alias of "WORM" heard on port 1 out onto port 2. digipeat: 2 wide*,trace* 1 add wide ;--> digipeat WIDE*, TRACE* from the second port back to port 1. digipeat: 2 worm 1 add wide ;--> digipeat from the second port the alias of "WORM" and add WIDE to the path end. digipeat: 1 south 2 new WA6BRW-10,K6TZ-10,WB6TLJ-5,WIDE ;--> digipeat "south" alias from port 1 to port 2, and completely repath the packet with this one. digiend: 2 WA6BRW-10,K6TZ-10 1 add WA6RKE-3,WIDE ;--> if stealth hears a packet that "ended" at BRW-10 or TZ-10, pick it up, and add RKE-3 and ;--> wide to it, and send it back out. digiend: 1 K6IXA-3,WA6JJA-3,K6ARP,W6UR-3 1 add WA6RKE-3 ;--> like above but listing on a different port. ;--> do you see why DIGI.INI *must* be edited? ; Digpeat frames with these TO calls and no existing digipeaters. Echo: 1 APR???,BEACON,ID,WX,CQ 1 via wide ;--> pick up these packets if they didnt have any "path" node: 100 ;--> how many callsigns kept in the NODE software. user: 8 broadcast: 10 linktimeout: 60 ;--> leave these as shown. bbscall: wa6rke-1 bbsalias: nobbs ;--> you *must* edit bbscall to the MYCALL of the digi. ------------------------------ W0RLI\CFG\DIGI.LNK This is a file that DIGI creates after you run Stealth digi. Its data for the NODE software showing callsigns heard and on which ports etc. Dont sweat this. ----------------------------- W0RLI\CFG\DIGIAPRS.INI W0RLI\CFG\DIGIHF.INI This is where a beacon text is stored. In my 4 port version, I made a VHF position text with a DIGI icon symbol, and for HF I made a beacon text with a GATE symbol. All thats in this file is a single line of text. My actual VHF beacon is: !3616.91N\11918.35W#PHG3580/A=000321/wa6ylb-at theworks.com 3 port Stealth digi 2.5 My HF beacon is: !3616.91N/11918.35W& wa6ylbat- theworks.com 4 port Gate/WORM Stealth digi 2.5 This needs to be modified to have the correct information for your Stealth. Be aware of the length of the line, as you cant view all of it in APRSdos version. Be brief if you can. ---------------------------- W0RLI\EXE\DIGI.EXE I tried and tried setting the SET statements to allow the digi program to be placed in a different directory location. I never got it to work except in this directory. Maybe I overlooked some thing. I dont care, since its running it doesnt bother me. This is the actual Stealth application that runs on G8BPQ node software. Use F4 to exit from Stealth. ---------------------------- LOGS\STARTUP.LOG When DIGI starts up, it logs any "settings" problems or things it doesnt know what to do in this file. Usually this LOGS is a directory under W0rli like CFG and EXE is. I dont know why I show it here as a directory under the root. If you cant find the Startup.log after running stealth a couple of times, build a \W0RLI\LOGS directory and see if Startup.log appears there. Also, look into this log from time to time, as it will tell you things here that It doesnt understand what to do with. This includes syntax and typos. (now we never do these things, do we?) --------------------------- Manual install of files. Make sure the SET statements are in the autoexec.bat file of the PC your running this on. Make a BPQ directory, and place all the BPQ stuff in it. Else, add the BPQ files to one of the other directorys if you like. Make sure the BPGCFG.BIN is in the same directory as BPQCODE.EXE is. Make a W0RLI directory. Make subdirectorys of CFG and EXE and LOG under W0RLI. Copy the files as shown at the top of this tutorial into the proper locations as shown. Create a "startup" batch file, one where it invokes BPQCODE and its binary file where ever you have them stored. Then invoke DIGI.EXE in \W0RLI\EXE directory. Edit DIGIAPRS.INI, DIGIHF.INI(if needed - if not, comment out the second SEND: command and following lines) , DIGI.INI and BPGCFG.TXT. Run BPGCFG.TXT after making any changes in BPQCFG.TXT. Note, the BPQCFG.TXT has a MYCALL there too. Any questions? Email me at wa6ylb remove words at yahoo.com