ÛßßÛ É͵ Help Document #1 ÆÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ» Ûßßßßßßß ßßßßßßßÛ º TOPIC: RoboBOARD/FX General Questions º ÛÜÜÜÜÜÜÜ ÜÜÜÜÜÜÜÛ º FOR: RoboBOARD/FX 1.00b º ÜÜÜÜÜÜÛ ÛÜÜÜÜÜÜ º REVISED: October 13th, 1993. (Rel #1) º Û Û º º ßßßßßßÛ Ûßßßßßß ºÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄĺ ÛßßÛ ÛßßÛ Û Û ÛßßßßßßßßÛ º º Û Û Û Û Û Û Û ÜÜÜÜÜÜÛ º Ordering/Info: 1(819)682-9737 9am-5pm EST º Û ßßßß Û Û Û Û Û ÜÜÜÜÜ º Tech Support: 1(819)682-6670 9am-5pm EST º Û ÜÜÜÜ Û Û Û Û Û Û Û º FAX: 1(819)685-0994 º Û Û Û Û Û Û Û ßßßß Ûß º BBS: 1(819)682-7771 (4 lines) º ÛÜÜÛ ÛÜÜÛ Û Û ÛÜÜÜÜÜÜÜÜÛ º º ÛÜÜÛ ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ Copyright (c) 1993, Hamilton TeleGraphics Inc. RoboBOARD and TEL-FX are trademarks of Hamilton TeleGraphics Inc. PREFACE ÄÄÄÄÄÄÄ Welcome to the RoboBOARD technical notes. These notes are provided for your benifit to help you trouble shoot your problems and provide you with a broader understanding of RoboBOARD/FX. This document as well as others written by HTG is revised regularly. If you do not find a solution to your problem in this document, call the RoboBOARD WORLD HQ BBS and check for a newer version, or call us on our Tech line at 819-682-6670. All RoboBOARD/FX Technical notes are dated and given a release number to aid you in your quest for current information. INDEX OF QUESTIONS ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ # TOPIC REVISION 0. It won't work 10-13-93 1. Transfers are very slow or don't work 10-13-93 2. Terminal freezes when Dialing 10-13-93 3. Typing is Slow or the HD never stops 10-13-93 4. I get random lockups 10-13-93 5. I only get 16 colours 10-13-93 6. My graphics are messy 10-13-93 7. I get a runtime error in the Drawing program 10-13-93 8. My Doors & Transfers don't work on my 9600+ modem 10-13-93 9. My uploads are vanishing. 10-13-93 10. My users get random lines or missing characters. 10-13-93 A. Common Causes for RunTime Errors 10-13-93 0. It won't work ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ If you are having problems with the package there are a few steps you should be taken on your end before calling HTG (or driving yourself crazy): 1) Are you running the most current version of the package? HTG releases FREE updates as more features are added, or as bugs or problems are resolved. These can be found on the HTG BBS (The RoboBOARD/HQ) or at: BBS++ 1(619)793-8360 v32bis (San Diego, CA) Mikes Communications System +49-6131-474483 v32bis (Germany) 2) Have you read the section of the manual (RTFM - "Read the Friendly Manual") that pertains to your problem? 3) Have you read the ADDENDUM supplied with the most current package or update you recieved (ADDENDUM.TXT is always found in the ROBOFX directory) 4) Have you read the "Trouble Shooting" appendice in the manual? 5) Are you meeting the minimum system requirements as described in the MANUAL or ADDENDUM? Additional information may have been displayed after the installation or update process was completed. 1. Transfers are very slow or don't work ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ If your system is transfering files very slowly or isn't doing anything at all after the file transfer window pops up then there are likely only a few causes. 1) The first thing that could cause this problem is an improperly configured FOSSIL driver. RoboBOARD/FX requires that you use 4K transmit and receive buffers. With the X00 fossil by Ray Gwinn this is set with the R= and T= commands. Fifos set to 8 ³ Lock Com 2. ³ No Commercial 19200 baud. ³ ³ ³ ³ DEVICE=C:\FOSSIL\X00.SYS E 2 T=4096 R=4096 B,1,19200 F=8 ³ ³ ÀÄÄÂÄÄÄÙ ³ Its in the Fossil Dir ³ ³ ³ If Com 1 ³ ³ ÀÄÄÄ set to 0 2 ports Transmit and receive buffers at 4K. (RoboBOARD requires 4K) *NOTE: FOSSIL ports are numbered from 0-7 not 1-8 2) If you are using 4K buffers with your FOSSIL or you are using the RoboBOARD/FX direct UART support and are not receiving top speed with your 14.4 modem there could be a few problems: - You do not have a 16550A UART. If you do have one and are using a FOSSIL driver you have to turn it on (in X00 use F=8 or F=12). - You have your BUS clock speed set very slow. This is often found in your power on settings under an option called ATCLK (AT CLOCK). The ATCLK value is actually a diviser. You take the speed of your processor and divide it by the ATCLK value to come up with the BUS clock speed you are selecting. A standard ISA bus can handle 12-16Mhz, however some older cards and 8 bit cards require the bus to be set at 8Mhz (this is acceptable). A bus clock of 12- 16Mhz will also increase the general performance of your system. It should be noted that a 486DX2/50 has a true clock rate of 25Mhz and a 486DX2/66 has a true clock rate of 33Mhz (don't divide by 50 or 66). 2. Terminal freezes when Dialing ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ If this is happening to you or one of your users, check the size of a file called ROBODIAL.DAT. If the file is 0 bytes, then delete the file. FXTerm will recreate it the next time you go to dial. 3. Typing is Slow or the HD never stops ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ RoboBOARD/FX requires 512K of EMS. This memory is used for Overlay management. XMS does not work, but may also exist in your system. Without the 512K buffer, your disk will be used as the paging area. The following are ways to get 512K (or more) EMS for RoboBOARD/FX. UNDER DOS 5 (Without 386MAX or QEMM) Install HIMEM.SYS and EMM386.SYS in your CONFIG.SYS. Consult your DOS manuals for examples. EMM386.SYS will provide EMS services but will also use 64K of upper memory for paging. Make sure you also have the lines DOS=UMB and DOS=HMA in you CONFIG.SYS. UNDER DOS 6 (Without 386MAX or QEMM) Install HIMEM.SYS and EMM386.SYS in your CONFIG.SYS, or run MEMMAKER which will do this for you. It is important to answer "Y"es when asked if you run programs which use EMS. MEMMAKER will also load additional device drivers and TSR programs into high memory freeing up conventional memory for RoboBOARD/FX. UNDER DOS # WITH QEMM386 Qemm 7.01 by Quarterdeck will allow you to operate with the required EMS. QEMM allows your memory to be both EMS or XMS for applications which like either. QEMM386 will also move your TSR and device drivers into high memory. If you run DOS 6 DOUBLESPACE then you may want to check out QEMM386 as it will eliminate the 44K used by the disk drivers. UNDER DV WITH QEMM386 Under program setup on the "Advanced Options" menu be sure to specify 512K EMS/XMS/VCPI/DPMI. It is also suggested that you set "Maximum Program Size (in K)" to 640, and "Memory Size" (on the "Standard Options" menu) to 128K. 4. I get random lockups ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ There are several things which can cause lock ups: 1) Under DOS do you have 550K (or more) conventional memory? This can be check by typing MEM at the dos prompt and reading the "Largest Executable" results. If you have less that 550K do the following: DOS 5 : Load more Drivers high (see DOS manual) DOS 6 : Run MEMMAKER QEMM386 : Run OPTIMIZE 2) Under DV do you hae 490K (or more) conventional memory. You may check this by typing MEM at the dos prompt and reading the "Largest Executable" results. If you have less that 490K do the following: - Run Optimize and select Stealth Testing. - Unload any unneeded TSR or Device Driver programs. 3) Do you have two devices sharing the same interupt? For example, do you have an Internal Modem on the same interupt as a Multi-IO card? 4) If you think it is graphics, try running ROBOFX with an added -16COL command line option. You may (probably do) have to change your RUN-ROBO.BAT and LOCAL.BAT files to add this command. Check the "MY GRAPHICS ARE MESSY" for video related problems. 5. I only get 16 colours ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ To see 256 colours RoboBOARD/FX requires an SVGA adaptor. That means we require you to have more that 256K of video memory. We support the following video cards directly: ATI, Paradise, Trident, Tseng 3000/4000 and VIDEO SEVEN. If you have more than 256K of video memory (512K or 1024K) and would like to see 256 colour graphics then check to see if your manufacturer has supplied a Device Driver or TSR called a VESA DRIVER. RoboBOARD/FX has full support for VESA DRIVER mode graphics as well. If you cannot find one for your card, call your video card manufacturer. 6. My graphics are messy ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ If you have a 1 meg (or 2 meg) Video card and are having garbled graphics or random lockups, it may be caused by the DOS 6 MEMMAKER or QEMM386 memory managers. If you run either and this "SEEMS" to be a problem add the following to your command lines: QEMM386.SYS : DEVICE=C:\QEMM\QEMM386.SYS X=C000-C1FF DOS 5 or 6 EMM386.SYS : DEVICE=C:\DOS\EMM386.SYS X=C000-C1FF NOTE: 2 meg video card may require an exclude of X=C000-C7FF. 7. I get a runtime error in the Drawing program ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ If you are getting a runtime error 203 or 204 this is caused by running out of memory. If you are getting any other errors call HTG for further assistance. Please Refer to ITEM #3 for memory setup. 8. My DOORS & TRANSFERS don't work on my 9600+ modem ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ If you find your doors work locally but don't work remotely and you own a 9600, 14400, 16800, 19200 or 21600 bps modem, be sure your PORT is LOCKED one baud rate higher than your modems Maximum: Modem Rate Locked Rate 9600 19200 14400 19200 (or 38400) 16800 38400 19200 38400 (or 57600) 21600 38400 (or 57600) 9. My uploads are vanishing. ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ If your uploads are vanishing there may be a few causes. All of them are fairly easy to resolve: 1) You do not have a valid upload area defined. Use the menu editor under the display pull down to edit the "UPLOAD" menu command. Make sure the "FILE AREA #" field corresponds with a valid file area as found on the files pulldown, "FILE AREAS" option. 2) On the FILES pulldown under upload handling you have specified YES to "SCAN NEW UPLOADS" and/or "CONVERT UPLOADS". If you have either of these toggled to YES it is critical that SCAN (by McAFEE) and/or the Archivers you support are all found in the "C:\ARCH\" directory (or any other you specify). Simply having the scanner and/or archivers in the Path will not do (although they may be for your convenience). Make sure you have the newest versions of your archivers and/or scanner. RoboBOARD/FX will delete any file that it cannot process do to an error during the scan/convert process. 10. My users get random lines or missing characters. ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ Losing characters is a common problem with high speed modems. This is only magnified when VGA or SVGA graphics are being displayed at the same time. There are a few solutions, 1) getting a 16550A uart, 2) specifying a correct locked rate, 3) getting a DigiBOARD. We will talk about two of these. 1) A 16550A UART should eliminate character loss completely. RoboBOARD/FX has full support for the 16550A FIFO BUFFERS. Most fossil drivers have support as well, however often you have to turn this option on (in X00 you add an F=8 or F=12 to the command line). The main advantage of the 16550A UART is that it has tiny buffers for holding characters in so the computer has time to them before they are overwritten by another incoming character. Please read "MULTINODE OPERATION & OPTIMIZATION" under the "I/O performance" heading in your manual. 2) Another common problem is that people tend to lock their com ports at an overly high baud rate. 14400 bps modem manufaturers brag about 57600 baud throughput, but that is only under optimum data flow, and only happens for 100ths (or 1000ths) of seconds. In all these tiny bursts average out to about 1635 cps (characters per second), that is the same as about 16350 bps. Because all data going in and coming out of your modem is buffered it is safe to lock a 14400 bps modem at 19200 bps without any serious loss of speed. After all 19200 bps is still faster than 16350 bps which allows your modem buffers to be filled well in advance of the compression process. Here is a chart of modem rates and suggested locked rates: Modem Rate Locked Rate 9600 19200 14400 19200 (or 38400) 16800 38400 19200 38400 (or 57600) 21600 38400 (or 57600) Please be sure you have HARDWARE FLOW CONTROL and DATA COMPRESSION turned on if you are running a 9600+ modem. A. Common Causes for RunTime Errors ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ The most common errors are: RunTime Error 101: This is caused when your Hard Drive is full. On the BBS end a minimum of 5 megs operating space is suggested. RunTime Error 203 or 204: These errors are caused when RoboBOARD/FX (or FXDRAW) runs out of Conventional memory. 550K free dos memory is a required. This can be checked by typing MEM at the DOS PROMPT and check the "LARGEST EXECUTABLE" results. chart of modem rates and suggested locked rates: Modem Rate Locked Rate 9600 19200 14400 19200 (or 38400) 16800 38400 19200 38400 (or 57600) 21600 38400 (or 57600) Please be sure you have HARDWARE FLOW CONTROL and DATA COMPRESSION turned on if you are running a 9600+ modem. A. Common Causes for RunTime Errors ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ The most common errors are: RunTime Error 101: This is caused when your Hard Drive is full. On the BBS end a minimum of 5 megs operating space is suggested. RunTime Error 203 or 204: These errors are caused when RoboBOARD/FX (or FXDRAW) runs out of Conventional memory. 550K free dos memory is a required. This can be checked by typing MEM at the DOS PROMPT and check the "LARGEST EXECUTABLE" results. 11. Adding Extended Descriptions to Files. ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ This paragraph explains how to add extended decriptions to files. When we added Extended Descriptions to files it was not our intention that 30,000 files all have an extended description. Rather it was intended to describe important files, especially for support systems and and the like, where the number of files with extended desriptions is limited and managed. - Extended Descriptions are located in their own directory and NOT in the same directory as the files they describe. - Extended Descriptions are located in their own directory called C:\ROBOFX\EXTENDED\ the drive letter depends on where ROBOFX is located on your system. - Extended Descriptions are written in a text editor like Dos Edit. They should be no more then 70 columns wide and contain no control characters. - An example: You have a Dir specifically for Archivers and it is located at D:\ARCHIVER\ It contains PKZIP.EXE, LHARC.EXE and ARJ.EXE. You want to tell your users more about these files so you write 3 text files with Dos Edit in the C:\ROBOFX\EXTENDED\ directory called PKZIP.EXD, LHARC.EXD and ARJ.EXD. 12. UPLOAD HANDLING (VIRUS SCANNING) ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ RoboBOARD/FX allows you the SysOp to automate the process of Virus Scanning files that are uploaded to your BBS by users. RoboBOARD has direct support for the McAfee Associates Virus Scanner. If your version becomes out of date you can receive a current version at one of the numbers below. The McAfee Scanner will pause execution if the version you are running becomes outdated and will not pass control back to RoboBOARD until you intervene manually. If this happens in the middle of the night you won't receive callers on that node until you notice the problem. There is an command line parameter called /NOEXPIRE that will turn off this option (not recommended). McAfee Associates, Inc. (408) 988-3832 office 3350 Scott Blvd, Bldg. 14 (408) 970-9727 fax Santa Clara, CA 95054-3107 (408) 988-4004 BBS (25 lines) U.S.A. USR HST/v.32/v.42bis/MNP1-5 CompuServe GO MCAFEE InterNet support@mcafee.COM When a User logs onto one of the nodes on your BBS a directory called C:\ROBOFX\TEMP_#\ is created. (assuming drive C: and # represents the current node) All temporary information that is relevent for that session is stored in this directory including any uploaded files. When the user logs off your BBS, before RoboBOARD deletes the temporary directory SCAN is run only if files have been uploaded by that user. If SCAN is required to run a temporary directory called C:\ROBOFX\ARC_#\ is created. (assuming drive C: and # represents the current node) If RoboBOARD encounters an archived file: - With an extension as defined in the second screen shown below [ ie: #1 Archive Extension ZIP ] it will unarchive the contents of the file. - Next each file in the archive will be virus SCANed. - If you have a BBS AD defined in the [ BBS AD file name ] field of the following screen it will be copied into this directory. - If the SCAN is successful the contents will be rearchived into the archive format defined in the [ Destination extension ZIP ] field defined in the first sample screen below. - If the file(s) in question does not have an archiver extension it will be imported no matter what, in the scan is successful. If the scan fails McAfee's SCAN will return ERRORLEVEL 1 to RoboBOARD. Upon encountering an ERRORLEVEL 1 RoboBOARD will clean out everything in the temporary directory. This guaranties the integrity of the system. The following screen is captured from the Files menu in RoboCFG. It shows the Upload Handling Template. From top to bottom the fields are: 1) The Scan Command Line that activates the McAfee SCAN.EXE file including parameters. The /NOMEM parameters tells the scanner to Skip Memory Checking, and the /NLZ command means Skip internal scan of LZEXE compressed files (in other words this means turn off the virus scanners internal check). Do not use the /D option that instructs McAfee SCAN to delete the file since RoboBOARD automatically deletes the archive file if it fails. 2) This is the Path to your Archivers (don't forget the last \ ). Not having the Archivers at that location on the hard drive or having the incorrect path will cause the file upload to fail. This is the single most common problem that we have uncovered while doing Technical Support at HTG. 3) This is the path and the name of your BBS AD. You can create an AD for your BBS in an Ascii Editor or in a package like Thedraw. RoboBOARD will replace any adds having the same name that are included in the archive being scanned. 4) Turn Scanning Off or On. 5) Convert Upload Archives as defined in screen 2. Yes or No. 6) This is the Extension of the archiver that will be converted to if Convert Upload Archives is set to Yes. Exit System User Messages Files Display Languages Nodes ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ» ÉÍ͵ Upload Handling ÆÍÍÍÍÍÍÍÐÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÐÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ» º º º Scan Command Line SCAN /NOMEM /NLZ____________________ º º Path to Archivers C:\ARCH\____________________________ º º BBS AD file name C:\ROBOFX\BBSAD.TXT_________________ º º º º Scan New Uploads Yes º º Convert Upload Archives Yes º º Destination Extension ZIP º º º º [DONE] º ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ HELP: Command line for McAFEE SCANV virus scanner. (or Blank) The next screen displays the command lines that handle unarchiving and rearchiving of files after a successful virus SCAN. All archiver formats are converted to the extension type noted in the above screen under Destination Extension. The format of the converter is: 1) Define Archive Extension type. 2) The Unarchive command line and parameters. 3) The Archive command line and parameters. To explain the options used in our example below. PKUNZIP -en ... Extract files sorted by Name PKZIP -ex ... Create ZIP files using exceptional compression. Since the user is off the BBS anyway, you might as well get the best compression. ARJ e -y ... Extract files from archive. Assume Yes on all queries. ARJ a -m0 ... Add files to archive. Use Method 0 which is the highest level of compression. LHA e /cm ... Extract files. Skip time stamp Check. No Message for query. LHA a /tm ... Add files. Time stamp files. No Message for query. PAK e /wa /sn ... Extract files from archive. Write over always. Sort by name. PAK a /sn ... Add files to archive. Sort by name. Exit System User Messages Files Display Languages Nodes ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ» É͵ Archive Control ÆÍÍÍÍÍÍÍÍÐÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÐÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ» º º º #1 Archive Extension ZIP º º Unarchive Command PKUNZIP -en__________________________ º º Archive Command PKZIP -ex____________________________ º º #2 Archive Extension ARJ º º Unarchive Command ARJ e -y_____________________________ º º Archive Command ARJ a -m0____________________________ º º #3 Archive Extension LZH º º Unarchive Command LHA e /cm____________________________ º º Archive Command LHA a /tm____________________________ º º #4 Archive Extension PAK º º Unarchive Command PAK E /WA /SN________________________ º º Archive Command PAK A /SN____________________________ º º #5 Archive Extension ___ º º Unarchive Command _____________________________________ º º Archive Command _____________________________________ º º º º [DONE] º ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ HELP: Extension of archived file format #1. 13. NEW FILES & LIST FILES ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ This section is intended for people who are having "New Files" and "List Files" problems. It is really a check list of things that can be looked into if you are experiencing difficulties. - Do the FORUM numbers on your file areas match the FORUM numbers in the "New files" and "List files" commands on your FILES.MNU (this file menu may possibly one you created). Please use the menu editor under the DISPLAY template to check this out. By default the menu commands are set to FORUM 1. If these do not match, no files will be displayed. - Do the file areas have any files in them? If they don't RoboBOARD/FX will not display them. This avoids confusion for your users. - Do your access tags and access match the file area tags, and the "New Files" and "List Files" menu command tags? Your access must match or be greater than or equal to both of these. - In the "DataBase" field all your FILE AREAs must have seperate DataBase names. Perhaps try Re-Managing your various file areas to check for corruption.