Shareware 1 2 the Maxx

home *** CD-ROM | disk | FTP | other *** search

/ Shareware 1 2 the Maxx / sw_1.zip / sw_1 / BBS / PCBDEMO1.ZIP / Q&A.TXT < prev next >

Wrap

Text File | 1991-11-22 | 17KB | 332 lines

Below are the questions (and answers) most often asked by PCBoard sysops: ┌────────────────────────────────────────────────────────────────────────────┐ │1) Can I run multiple nodes on a single machine? │ └────────────────────────────────────────────────────────────────────────────┘ Yes and no. To do so requires a multitasker such as DESQview and at least good 386SX based machine (or better). We do not recommend attempting to run under a multitasker on a 286 based machine. You may try it and you may be successful but you'll find a 386 based machine gives not only better performance but does it much more reliably. In trying to run multiple nodes the one thing to be aware of is that each modem must be set up on a separate comm port and each comm port must have a unique IRQ and ADDRESS setting. For instance, some internal modems are switchable between COM1/COM2/COM3/COM4 - the only trouble is, they are usually configured like this: COM1 - IRQ 4, Address 3F8 COM2 - IRQ 3, Address 2F8 COM3 - IRQ 4, Address 3E8 COM4 - IRQ 3, Address 2E8 If you look closely at the above you'll see that each of the four addresses are unique HOWEVER the IRQ values for COM3 and COM4 are identical to those used by COM1 and COM2. Since two devices cannot share the same interrupt level on a standard AT bus that means you could not possibly get COM1 and COM3 to work together on the same machine nor could you get COM2 and COM4 to work together. The following, however, will work: COM1 - IRQ 4, Address 3F8 COM2 - IRQ 3, Address 2F8 COM3 - IRQ 2, Address 3E8 COM4 - IRQ 5, Address 2E8 In this case COM3 and COM4 have separate and unique IRQ's. Another very important aspect is the UART chip contained on the comm port. The most common is the 8250 and 16450 chips and yet these are NOT the ones you want to use if you are going to be multitasking. The chip to use is the National Semiconducter 16550AFN. This chip is not only rated for higher speeds but is more reliable in a multitasking environement. Boards such as the Everex Magic I/O card come with the above mentioned requirements. The Magic I/O card has 3 comm ports on a single card. Each can be set up as a unique IRQ and Address. And all three UARTs are socketed for easy replacement with the 16550A chips. For help in configuring your multitasking software we recommend that you call the Salt Air BBS and check out the files in directory #17 of the support conference. DESQview is by far the most widely known and used among PCBoard sysops and that means that there are more people that can help you if you run into troubles. Windows 3.0 works but we don't necessarily recommend it due to execution speed as well as the fact that Windows 3.0 masks out the 16550A chip which was just mentioned as being a requirement for running multiple nodes. ┌────────────────────────────────────────────────────────────────────────────┐ │2) What do all of the numbers mean down on the status line while a caller is│ │ logged onto the system? │ └────────────────────────────────────────────────────────────────────────────┘ There is a lot of information packed into that tiny space. The following diagram should help explain what all of the numbers mean: Minutes Used Total Free Memory ───────┐ │ ┌─────── Logon Time │ │ │ Max Number of 252K 15 23:56 File Handles ─────── 13 33K 13 00:12 │ │ │ Free Memory ───────┘ │ └─────── Current Time in 64K Seg Minutes Left The "Total Free Memory" is the amount of DOS memory that was left after PCBoard loaded itself into memory. If you are not using the /SWAP switch then that is also approximately how much memory will be free if you shell out to DOS for such things as "external protocols", "message capture compression", "online file viewing" and the F5 Shell to DOS function key. The "Free Memory in 64K Data Segment" is really for PCBoard's own use but gives some indication as to how well PCBoard is managing its own memory. The "Max Number of File Handles" gives some indication as to the number of files that have been opened. In reality the number is simply the highest numbered file handle returned by DOS. DOS uses 5 handles for itself and has a maximum of 20 file handles available to PCBoard. In addition there are a couple of 'flashing characters' that may appear at the bottom of the screen near the Logon and Current Times, they are: 'N' = Sysop on next after caller logs off 'X' = Exit to DOS after caller logs off 'p' = Caller paged the sysop '' = PCBoard is scanning the USERNET.DAT file ┌────────────────────────────────────────────────────────────────────────────┐ │3) My callers log is missing the Minutes Used number whenever a caller logs │ │ off the system. My log looks like this: │ │ │ │ ************************************************************** │ │ 04-12-91 (20:48) (12) JOHN DOE (19200E) (G) SLC, UT │ │ Minutes Used: <--- the number is missing │ │ 04-12-91 (20:48) (12) JOHN DOE Off Normally │ │ ************************************************************** │ └────────────────────────────────────────────────────────────────────────────┘ PCBoard writes to the log according to what is in your PCBTEXT file. The contents of which changed during the BETA TESTING period in 1990 in which PCBoard version 14.5 was being tested. This missing number indicates that your PCBTEXT file has not been upgraded since you last ran the v14.5 BETA software but you have since upgraded to the release version of PCBoard v14.5 or the release version of v14.5a. The PCBTEXT file can be fixed by one of two methods: 1) Call into Salt Air and join the SUPPORT conference. In directory #2 you will find a couple of files called FIXmmdd.ZIP where "mmdd" is the month and date of the BETA code that required those fixes be made to the PCBTEXT file. Download the FIXmmdd.ZIP files that are more recent than the last beta version of the software you were running and run the FIX programs on your PCBTEXT file. 2) A much simpler approach is available if you have not customized your PCBTEXT file and that is to simply delete it. Then run MKTXT145.EXE to create a brand new copy. NOTE: the above procedure must be done for every copy of PCBTEXT file if you are running a multi-lingual system. ┌────────────────────────────────────────────────────────────────────────────┐ │4) How do I set up the Zmodem protocol on my system? │ └────────────────────────────────────────────────────────────────────────────┘ First of all, you need to understand that the Zmodem protocol is an external protocol. That means that the protocol itself is not built directly into the PCBoard software. PCBoard is capable of executing any number of these "external" protocols. Zmodem is the most popular and you'll find sample batch files right on our distribution disks. For reference, the following information is what is important to setting up the Zmodem protocol on a PCBoard v14.5 system. First, edit your PCBPROT.DAT file by running PCBSetup and going to the File Locations 2 screen. Once your cursor is on the PCBPROT.DAT file press the F2 function key to edit it. Set Zmodem up like this: Port Lock Use Type Size MNP Open Lines Protocol Description ═══ ════ ════ ═══ ════ ═════ ════════════════════════════════ Z D 1024 N N Y Zmodem (Batch U/L and D/L) Next, create a pair of batch files called PCBSZ.BAT and PCBRZ.BAT (for sending and receiving respectively) like this: PCBSZ.BAT --------- echo off if exist pcberr.fil del pcberr.fil if exist pcbdsz.log del pcbdsz.log dsz handshake both pB4096 estimate 0 %5 z sz %3 PCBRZ.BAT --------- echo off if exist pcberr.fil del pcberr.fil if exist pcbdsz.log del pcbdsz.log dsz handshake both estimate 0 %5 pB4096 pd0 z pr1 rz -p %3 And then edit your BOARD.BAT file and make sure that you have a line in there that says "SET DSZLOG=PCBDSZ.LOG" like this: >───────────┐ │ echo off │ c: │ cd\pcb │ set pcb= │ set dszlog=pcbdsz.log <<<──────────────────────────────────┘ if exist remote.bat rename remote.bat remote.sys if exist event.bat rename event.bat event.sys if exist door.bat del door.bat if exist endpcb del endpcb pcb145 if exist remote.bat remote if exist door.bat door if exist event.bat event if exist endpcb goto end board :end The actual filename or location of the DSZLOG file doesn't matter as long as it is valid and is UNIQUE for each node. NOTE: you need a copy of DSZ.COM in order to implement the Zmodem. It can be downloaded from many BBS's around the world. It can also be found on Salt Air by joining the support conference and searching for DSZ*.ZIP. The file usually is posted as DSZmmdd.ZIP where "mmdd" is the month and date of the version posted (example: DSZ0416.ZIP). ALSO NOTE: don't forget to register your copy of DSZ. You'll find that until you do batch uploads will not work properly given the above batch files. The following is a work-around until you register your copy: In place of the last line in the PCBRZ.BAT file use: cd %3 dsz.com handshake both estimate 0 %5 pB4096 pd0 z pr1 rz -p cd %PCBDIR% The above lines (first and third) take care of changing to the private upload directory where the files will be uploaded and then changing back to the PCBoard directory. NOTE: PCBoard version 14.5a sets up the PCBDIR environment variable at the time you bring the board up. It is the "home" directory for PCBoard. Also note that the above expects the home directory to be on the same DRIVE as the private upload directory. ┌────────────────────────────────────────────────────────────────────────────┐ │5) When I try to make a file FREE for download (so that the caller does not │ │ get charged for the time downloading it) PCBoard continues to charge him │ │ time. Why? │ │ │ │ Or, when I set up the security for a file to level 100 my lower security │ │ callers are still able to download it. Why? │ └────────────────────────────────────────────────────────────────────────────┘ Most likely you have set up your FSEC file incorrectly. There are several very common mistakes in this area. One is in thinking that simply adding a line to the end of the FSEC file will work. However, the order of the entries in the FSEC files is extremely important. The following is a list of example FSEC file entries followed by explanations for each entry and a few more rules to consider when creating your file. Path FileSpec Security Password (in the file looks like) ──────────────────────────────────────── ──────────────────────── C:\PCB\DL1\ MYFILE 100 MINE C:\PCB\DL1\,MYFILE,100,MINE C:\PCB\DL2\ *.DAT 50 SECRET C:\PCB\DL2\,*.DAT,50,SECRET C:\PCB\DL2\ *.* 40 C:\PCB\DL3\,*.*,40, C:\PCB\UP\ FILES.ZIP 5 NOTIME C:\PCB\UP\,FILES.ZIP,5,NOTIME BLT* 5 FREE ,BLT*,5,FREE *.TXT 35 TEXT ,*.TXT,35,TEXT *.* 20 ,*.*,20, REASONS: 1) a file called MYFILE found in C:\PCB\DL1\ requires a security level of 100 and a password of MINE to access 2) all files in C:\PCB\DL2\ with a .DAT extension require that the user have a security level of 50 or grate and know the password SECRET 3) all files in C:\PCB\DL2\ (other than .DAT files) require a security level of 40 or greater to access the files 4) the file called FILES.ZIP found in C:\PCB\UP\ requires a security level of 5 to download and is considered a FREE download and also stops the clock for the duration of the download 5) all files starting with BLT without an extension (i.e. BLT*) are considered FREE downloads but the clock is not stopped 6) all files with a .TXT extension regardless of directory require at least a security level of 35 to access plus a password of TEXT 7) all OTHER files no matter where they are require a security level of at least 20 to access them NOTES: 8) Note the very specific ORDER in which the above lines are entered. You should place your entries in the file such that the more specific the description of the file or placement the closer it is to the top (the top one for example is very explicit in both location and file name) next come files with some wild cards with locations and next come files without a specific location, etc. PCBoard *stops* scanning the FSEC file just as soon as it finds a match in the FSEC file so if the ",*.*,20," line were at the top of the file PCBoard would NEVER see the rest of the lines because *.* without a path matches EVERY file on the system. 9) Note that NOTIME implies that the file is also FREE and that the specification of such files is done via the password field. 10) Be aware that if you place anything in the PATH field of the FSEC file that it must be an EXACT MATCH on the path that is specified in your DLPATH.LST file. In other words, the following two lines do *not* match \PCB\UP\ and C:\PCB\UP\ because the first one can be applied to any drive while the second applies to only drive C:. Make sure the paths in the two files match precisely. The same rules as you see above are equally applicable to the UPSEC file except that FREE and NOTIME are not considered on uploads since all uploads stop the clock anyway. ┌────────────────────────────────────────────────────────────────────────────┐ │6) How do I set up a 2 node system where everyone can access Node 1 but only│ │ certain callers can access Node 2? │ └────────────────────────────────────────────────────────────────────────────┘ All you really need is two seperate PWRD files. Let's say PWRD1 is for node 1 which is PUBLIC and PWRD2 is for node 2. PWRD1 PWRD2 ------------------- ------------------- pwrd sec time bytes pwrd sec time bytes 10 30 100 10 0 0 20 60 9999 20 0 0 25 60 9999 25 60 9999 30 60 9999 30 0 0 35 60 9999 35 60 9999 40 90 9999 40 0 0 45 90 9999 45 90 9999 Using the above example, ALL levels 10 thru 45 can log onto Node 1 without any problem. Node 2, however, will only allow levels 25, 35 and 45 to log onto the system. You'll also want to modify the "CLOSED" file to indicate to the callers of Node 2 why they were not allowed onto the system and set that node to "closed" status via PCBSetup.