ÿÿÿÿÿÿ ÜÛÛÛÛÛÜ ÜßßÜ ÜÛÛÛÛÛÜ ÞÛ ÛÛ ÛÛÛÛÛÛÜ ÜÛÛÛÛÛÜ ÛÛ ÛÛ ßÜÜß ÛÛÜÜÜÛÛ ÛÛÜÜÛÛÜ ÛÛ ÛÛ ÛÛÜÜÜÛÛ ÛÛ ßÜÛÛ Üß ßÜß ÛÛßßßÛÛ ßßßßÛÛß ÛÛÛÛÛÛ ÛÛßßßÛÛ ßÛÛÛÛßÜ ßÜ ÜßÜ ÛÛ ÛÛ ÛÛ ÛÛ ßÛÛ ÛÛ ÛÛ ßß ß Revision 11 Questions and Answers for RemoteAccess 2.x °°±±²² MULTTASK.Q&A ²²±±°° Updated on 02/04/96 By: Eric Staufer The Concession Stand FidoNet 1:374/6568 Setting up RemoteAccess in different environments: * DESQview with RemoteAccess & FrontDoor (my setup) * OS/2 Setups for AutoExec.Bat/Config.Sys for RA (Karen Maynor) * OS/2 with RemoteAccess & BinkleyTerm (James FitzGibbons' setup) * Windows for Workgroups with RemoteAccess & FrontDoor (Ed Meloan's setup) °°±±²² DESQview with RA & FD ²²±±°° ÉÍChangeÍaÍProgramÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ» º Standard Options º º º º Program Name............: RemoteAccess Callup Node (1) º º º º Keys to Use on Open Menu: B1 Memory Size (in K): 550 º ºÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄĺ º Program...: C:\RA\RUNRA.BAT º º º º Parameters: 1 º º º º Directory.: C:\RA\NODE1 º ºÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄĺ º Options: º º Writes text directly to screen.......: [Y] º º Displays graphics information........: [N] º º Virtualize text/graphics (Y,N,T).....: [T] º º Uses serial ports (Y,N,1,2)..........: [N] º º Requires floppy diskette.............: [N] º º º º F1 for Help F10 for Advanced Options <ÄÙ when Done º ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ [Advanced Options] ÉÍÍChangeÍaÍProgramÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ» º Advanced Options º º º º System Memory (in K).......: 0 Maximum Program Memory Size (in K): º º º º Script Buffer Size.......: 0 Maximum EMS/XMS/VCPI/DPMI (in K): 1200 º º º º Text Pages: 1 Graphics Pages: 0 Initial Video Mode: º ºÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄĺ º Window Position: º º Maximum Height: 25 Starting Height: 11 Starting Row...: 0 º º Maximum Width.: 80 Starting Width.: 80 Starting Column: 0 º ºÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄĺ º Shared Program º º Pathname..: º º Data......: º ºÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄĺ º Close on exit (Y,N,blank)......: [N] Uses its own colors..............: [Y]º º Allow Close Window command.....: [Y] Runs in background (Y,N,blank)...: [Y]º º Uses math coprocessor..........: [Y] Keyboard conflict (0-F)..........: [0]º º Share CPU when foreground......: [Y] Share EGA when foreground/zoomed.: [Y]º º Can be swapped out (Y,N,blank).: [N] Protection level (0-3)...........: [0]º º º º F1 for Help F10 for Standard Options <ÄÙ when Done º ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ I use 3:3 for the TICKs on my System... But 1:1 and 2:2 may work just as good for your System. Just fool around with it. My batch file is nothing new.. all i have in there is just a dvansi loaded so the ansi isnt cluttered.. °±²Û OS/2 Setups for AutoExec.Bat and Config.Sys Û²±° Running RemoteAccess Under OS/2 ððððððððððððððððððððððððððððððð by Karen Maynor, 1:18/108 FidoNet A Quick Note ------------ I switched to OS/2 about 6 months ago under the urging of my good friend Mark Spivey (1:202/507). I figured OS/2 would be pretty tough to configure and learn. It took Mark over a year to convince me to try OS/2. I`ve ran my BBS under DesqView, WindowsNT, Windows For WorkGroups, Lantastic, and plain ole DOS in the past. Even though I have 16mb of memory, I constantly had memory problems under DV, and it was simply too slow.. Windows wasn`t the answer for me, and of course you can`t use your computer when the BBS is up when using just DOS. OS/2 was definately what I needed! And now with the release of OS/2 Warp 3.0, even systems with just 4mb of RAM can easily multitask. Please note that these settings work the best for my system and may not work for you. My system config: 486/33, 16MB, Hayes 28.8, Hayes ESP ComPort Card, RemoteAccess áeta, FrontDoor 2.20cmL. This information will also assume that you have knowledge of how to set up programs in OS/2. Now onto the Good Stuff. Communications Driver --------------------- You`ll first want to get a copy of Ray Gwinn's SIO. This is an absolute must! As of this date, the latest version of SIO is v1.45. SIO is updated quite often and current file name is SIO145.ZIP. SIO is a replacement for OS/2`s communications driver. Run the install program in an OS/2 Session and answer the questions. I use a Hayes ESP card which may have different settings from your particular setup. From my CONFIG.SYS: DEVICE=C:\SIO\SIO.SYS [ESP@0100] (COM1,0100:03F8,IRQ4:IRQ4) (COM2,0108:02F8, IRQ4:IRQ3) DEVICE=C:\SIO\VSIO.SYS The above shows my modem on com port 1, and com port 2 is used by my mouse. Settings>Session>DOS Settings ----------------------------- Most of the DOS Settings I have left at the default. The ones I have changed are below. I have two values under DOS_DEVICE, one loads ANSI.SYS in the BBS session and the other loads the communications driver. Simply add under values: C:\OS2\ANSI.SYS C:\SIO\VX00.SYS Other changes I made to the DOS Settings are: EMS_MEMORY_LIMIT - 0 IDLE_SECONDS - 5 IDLE_SENSITIVITY - 50 XMS_MEMORY_LIMIT - 408 You`ll also want to make sure that Sio_Allow_Access_Com1 (or applicable comport) is set to ON. Config.Sys ---------- My config.sys is left almost at default. The changes that work for me: Priority_Disk_IO=NO Maxwait=1 Priority=Dynamic Set Keys=OFF Autoexec.Bat ------------ @ECHO OFF ECHO. PROMPT $i$p$g PATH C:\OS2;C:\OS2\MDOS;C:\;D:\WINDOWS;D:\UTILS; LOADHIGH APPEND C:\OS2;C:\OS2\SYSTEM SET TMP=D:\TMP SET RA=D:\RA SET FD=D:\FD OS2SPEED TAME Pretty simple autoexec.bat... You`ll see that I set the environment for both RemoteAccess and FrontDoor. At the end of the Autoexec.Bat I run two programs, Os2speed and Tame. Tame speeds multitasking of DOS applications using OS/2, and Os2speed converts timeslice requests for DesqView to OS/2. Thats about it. This information should get your RemoteAccess BBS up and running under OS/2. Again, my settings may not be the best for you, so you may need to do some tinkering with some of the settings to get the best performance out of your BBS. °±²Û How to Setup BinkleyTerm and RemoteAccess using OS/2 Û²±° How to run an OS/2 Mailer with a DOS BBS Program ------------------------------------------------ Disclaimer ---------- Standard, but required. This textfile is meant for advice only, and the author is not responsible for any damages that occur through the use of this document. If what you have now is in one piece, and using this textfile leaves you with two broken pieces, I suggest you go out and buy an economy size tube of KrazyGlue 8-) Notes ----- In this document, when I have listed lines from my configuration files, each line is preceded by a '>' character. Do not type this in, it's just to show that this is a file line, not part of my babbling 8-) Now, on to the Good Stuff ------------------------- What will this textfile allow you to do ? Specifically, coach you in setting up BinkleyTerm v2.50EE with RemoteAccess v2.01. Hopefully, the idea will be usable with any OS/2 Mailer (or Comm program for that matter) and DOS BBS. My configuration (i.e. what I _know_ it works with) - BinkleyTerm/2 v2.50EE - RemoteAccess v2.01 - SIO (SIO, VSIO, VX00) v1.20 - 4OS2-32 v1.11 How to do it ------------ The important thing to do is remove protection from the port you will be using. OS/2 built in protection is what comes up and says "Sharing violation on COMx". SIO allows you to remove protection for a port (although it's not documented). I checked with Ray Gwinn that it was alright to document it here, so this is how : In CONFIG.SYS, put a dash (-) in the 5th position of the comm port parameters. If you are not using the 4th parameter, put an extra comma to space it out correctly. For example, my setup using COM2 locked at 38400 without protection is : > DEVICE=C:\OS2\EXTRAS\SIO.SYS (COM2:38400,,,-) Load VX00.SYS as usual after this. This is all that's required for CONFIG.SYS Now, in Binkley.Cfg, I use BBSSpawn. My SPAWNBBS.CMD contains this : > echo EXEBBS %2 2 %4 %5 > D:\RA\DOBBS.BAT > start "RemoteAccess" /FG /FS /WAIT /DOS=C:\OS2\4DOS\RA.INI D:\RA\DOBBS.BAT You'll notice that this echoes the parameters %BPS% %PORT% %EVENT TIME% %EXTENDED CONNECT% into my \RA\DOBBS.BAT file. I'm a recent FrontDoor convert, and using this produces a DOBBS.BAT that is compatible with FD's. Also, notice that I am forcing port 2 into the batch file. This is because BT passes the Port Handle that OS/2 assigns, which is not the physical port number. If you are running singleline, just force the port as I have. If not, use a %PORT environment variable to do the same task. You'll notice I'm using 4OS2 in the above example. The reason is that 4OS2-32 (not the 16 bit version) allows you to start a DOS session with a specific set of settings, similar to the way you set up an object's DOS settings on the workplace shell. The file C:\OS2\4DOS\RA.INI contains the following : > DOS_SHELL=C:\OS2\4DOS\4DOS.COM C:\OS2\4DOS @C:\OS2\4DOS\4DOSRA.INI > DOS_DEVICE=C:\OS2\EXTRAS\VX00.SYS > DOS_AUTOEXEC=C:\OS2\4DOS\BBSSTART.BAT > SIO_ALLOW_ACCESS_COM2=1 > EMS_MEMORY_LIMIT=2048 > XMS_MEMORY_LIMIT=2048 > INT_DURING_IO=1 This allows me to load VX00.SYS when the DOS session is spawned from the Binkley window. The /WAIT switch on the command line makes the session wait until the DOS session closes to restart Binkley. This eliminates the need to use semaphores as detailed in the MAGIC package that has been available for some time. If you don't want or can't use 4OS2-32, you can try using HSTART or STARTD, both of which allow you to start a DOS session with specific DOS sessions. Individual results may vary. I think we need a subtitle here... ---------------------------------- The thing that has caused me (and other people) problems in the past is with regard to SIO. I don't fully understand it, but I'll try to put it as best I can. SIO has some part of it to handle the communication with DOS sessions. This part is not initialized when SIO loads, presumably to reduce overhead on systems not using DOS communications. The part is initialized the first time that VX00.SYS is loaded. The problem is that if there is a carrier present when this part is woken up, something happens. The DOS app can send data out the port, but nothing can travel inbound. The solution to this problem has been provided by Ray Gwinn, author of SIO. I have spoken with him regarding this, and I'm not sure if my report helped him track down the cause of the problem, but the following excerpt from SIO v1.21k's READ.ME file explains : The method in which the SIO_Mode setting are implemented has been changed. These settings specify only the initial mode settings to use for a DOS session. Changes made to the mode (via a MODE or other command) within the DOS session are no longer lost. The SIO_Mode settings isolate the DOS VDM's mode from that of OS/2 sessions in all but one case. The one case is when the port is already opened when DOS first accesses it. In this one case, the SIO_Mode settings are not applied. Except for this one case, one should view OS/2 as having its mode settings and DOS sessions as having an independent group of mode settings. As you can see, the problem lied in SIO trying to apply the specified Mode settings to an opened port. You need SIO v1.21k or higher (a beta version, it is currently available as SIOBETA, but there may well be a release version implementing the same fix by the time you read this) to perform this little trick. Other Versions of Programs -------------------------- I am pretty sure that this will work using Standard BinkleyTerm/2, but I haven't yet tried. As long as your DOS BBS program runs well in a straight all DOS combination under OS/2, it should work under this method. For SIO, older versions than v1.20 should work, but newer versions (usually) provide better performance. Th-Th-Th-That's All Folks! -------------------------- Well, that's how it's done. It works here for me, and I hope this will allow people to do the same. For further information, contact me via netmail at one of the following addresses : 1:250/301 @ fidonet 18:105/301 @ zyxelnet 40:6482/301 @ ibmnet 81:416/236 @ nanet File Request Names ------------------ BinkleyTerm - BTOS2_258.ARJ for BinkleyTerm/2 v2.58 wide beta. Michael Buenter has asked that BT Extended not be distributed, so I don't have it available. BT/2 v2.58 has folded in a lot of Michael's code though, so you may be pleasantly surprised. SIO - SIO120.ARJ for the latest version as of this writing. SIO*.* should get you just the latest version, as I keep only the latest online (exception: a beta archive may be out without documentation files, so I might have two) 4OS2/32 - 4OS232.ARJ for the latest version (v1.11 as of this writing). v2.00 has been announced, but isn't yet shipping. Thanks ------ Thanks to Matthew Stein (1:250/701) for getting me involved with OS/2. Without his help I probably never would have switched. No Thanks to Matthew Stein (1:250/701) for telling me that every time I had a problem, it was "the fault of that stupid DOS BBS and you should just switch to Max/2 anyway" 8-) And a word of closing --------------------- Regarding SIO - if there is one program you're going to register for your OS/2 BBS system, make it this one. Take a minute to think where we'd be without Ray Gwinn and SIO. Can you say "CRC Error" ? Knew you could. Ray gave us X00 without charge, and now he's asking what I consider a paltry sum for SIO/VSIO/VX00 ($25 US). If you want Ray to continue to improve this fine driver, we have to show support for him. Thank you. James FitzGibbon 1:250/301@fidonet.org °°±±²² Windows for Workgroups with RA & FD ²²±±°° [READ.ME file from RAUSW4WG.ZIP] Several folks asked for the files that I use to run RA-USA under W4Ws. Here they are. One point I can't emphasize too strongly! These suggestions are for Windows for Workgroups 3.11. They are NOT for Windows 3.11. In spite of the similar version numbers, W4W has a MUCH improved COMM driver that makes third party driver unnecessary! Windows 3.11 does NOT. If you want to run a BBS under Windows, by all means, upgrade to Windows for Workgroups 3.11 or, if you must use Windows 3.1 or 3.11, use a third party COMM driver such as KingComm, TurboComm, etc. I want to thank Bill Cheeks for talking me into trying W4W . Like most of us, I had read all the messages saying that "Windoze" just couldn't cut it as a multi-tasker for a BBS. You =HAD= to use DesqView or OS/2! Bill convinced me I should try W4W and I've never been happier. And I ran RA-USA for a number of years under DesqView and have run it under OS/2 as well. For the most part I followed Bill Cheeks (1:202/731) instructions on setting the BBS up under W4WG. I am running two lines. Both use Hayes Optima V.FC 28,800 modems. I =DO= have 16550 UARTS on both lines. I believe 16550's are absolutely essential for high speed modems under =ANY= multi-tasking system! Just a word about the files... The RAx.BAT files are the files called by the two PIFS. They begin by setting up a number of environment variables AND start the FOSSIL inside the window. This is different than DesqView which wants the FOSSIL loaded BEFORE DV. Windows works BETTER with the fossil loaded in each window! It's also best to load ANSI.COM in EACH window rather than loading ANSI.SYS in the AUTOEXEC.BAT. There are two reasons for my suggesting this. 1. The ANSI.SYS driver is slower than the ANSI.COM program 2. Loading the ANSI handler in each window gives you a little more conventional memory in each window. A number of people have asked where to get ANSI.COM so I have included it in this archive for you. You will see both X00 and BNU there. I have tried both BNU and X00 and I believe BNU does a better job with W4W. File Transfers speeds are higher here with BNU. If you use X00 and file transfers are NOT as good as you expect, by all means, give BNU a try. I'll bet you'll see the transfer rates jump to what they should be. I'm currently using BNU so it doesn't have a "rem" in front of it. You will also see a NEAT little file called FDFIXW4W.COM that is loaded immediately AFTER the fossil. I'll say more that below. After handling the initialization, the remainder of RAx.BAT does the actual running of the BBS... processing mail and recycling RA after each call. The initialization section runs ONLY once when the window is first opened. From then on, we just recycle to the :Start section. RA1 processes all incoming mail. Both lines have FrontDoor answering the phone. RA1 does all the mail tossing. Line 2 just exits with echomail and creates a flag to tell RA1 there is mail to toss. RA1 also does all the maintenance. I use FrontDoor Commercial 2.20 and it has a nice feature that 2.12 doesn't have called FDFREEZE. It is described in the 2.12 docs but shown as only. It allows me to "freeze" line two while I do maintenance. If you run 2.12, you'd need another method if running two lines. I've included a couple of different methods of running RemoteAccess for you. RAx.BAT loads RA first and then SHELLS to FrontDoor. The advantage to this method is a noticably faster switch from FD to RA! Because RA is already in memory it is almost instantaneous. I will also include a set called RAFDx.BAT that load FrontDoor first and when FD gets a human caller it simply loads RA using DOBBS and EXEBBS.BAT. You will see that I check for only one errorlevel (200) to start the BBS. That works because 200 is my lowest errorlevel in FD (for 300 baud). So =ALL= higher baud rate errorlevels will work with the 200 setting and call the DOBBS file which then tells RA the exact baud rate. NOTE! The EXEBBS files are not needed for the RA1 (shell) method. I have FrontDoor create the DOBBS file with either method because if RA finds it, it can tell whether the call is from an ARQ modem or not. The PIF files are important in getting the best results with W4W. Locked memory is important for the BBS windows as is turning on "Runs in Background"! Bill Cheeks also feels the time slice on a 486 and possibly a 386 should be changed from 20 to 5. I have used 5, 10 and 20 here and can't see any difference. I'm running a 486/66-2 though. With a slower system it might make more difference. Bill says to make sure "Detect Idle time" is checked. I've read messages saying each way is best . I've tried it both ways and I can't really see any difference! I am currently running WITHOUT it checked. The PIF files included in this archive do not have it checked. I also give W4W a limit on the amount of memory. -1 tells it use whatever you need. I have read that allowing Windows to decide how much will slow things down more than telling it a specific amount. I turn off Expanded memory support and use eXtended (XMS) only. Windows likes XMS and, in fact, when you use EMS, Windows is simply converting XMS to EMS for you . This conversion is not as fast as using XMS to begin with. So, my settings ask for XMS but leave EMS at 0. For fastest speed, run your BBS either FULL SCREEN or minimized! If you run it in a window rather than full-screen, file transfers seem to go about the same speed but displays are noticeably slower because W4W must treat them as graphics rather than plain text and each letter has to be built from individual pixels rather than using an existing font of whole letters. Rather than include the complete INI files which you probably should NOT use instead of yours ... Let me give you the lines I think may help if added to the [386Enh] section of your SYSTEM.INI that you already have: [386Enh] FileSysChange=off IdleVMWakeupTime=1 Int28Critical=off UniqueDOSPSP=on InDOSPolling=off ComBoostTime=8 Com1Base=3F8H Com2Base=02F8 Com1Irq=4 Com2Irq=3 Com1FIFO=1 Com2FIFO=1 Com1TxTrigger=8 Com2TxTrigger=8 Com1RxTrigger=8 Com2RxTrigger=8 Com1Buffer=2048 Com2Buffer=2048 Com1AutoAssign=0 Com2AutoAssign=0 I am using two com ports (1 & 2) and so some of the lines are duplicated. One for each com port. You will want to use the com port/interrupt that YOU are actually using rather than mine, of course. Now a word about FrontDoor! You will want to run FrontDoor 2.12/2.20 because of the support for higher baud rates. Unfortunately, these two versions of FD have a problem with Windows time slicing. You'll find that FD doesn't answer the phone on the first ring and usually takes two. (If you don't have the IdleVMWakeupTime=1 in your SYSTEM.INI, it may never answer )! Then when it does answer, it will take a long time to send the connect message from 15 to 30 seconds depending on the system! By then, your caller may have given up. In the past, I have recommended the use of "/ForceInt28" on FD's command line. This would make FD answer on the first ring and connect immediately. The down side of this was that /ForceInt28 also cut W4W's efficiency by about half!! Now there is a very nice FIX for this problem and it works without cutting W4W's efficiency!! Included in this archive is a tiny TSR (written by Mats Wallin of the FrontDoor Beta team) which you should run immediately AFTER the fossil is loaded (FDFIXW4W.COM). This little program fools FD 2.21/2.20 into thinking it is running under DesqView and eliminates the need for /ForceInt28 while giving you the fast response to calls that you want!! It doesn't seem to have any adverse effect on RA so I never "unload" it once I have it loaded. BY all means, use this fix if you run FrontDoor. You'll find it used in the updated BAT files now included in this archive. I have it in my UTIL directory. You can place it wherever you like and change the path in the BAT file to call it. In summary... W4W seems to work well here and it was certainly easier to get running than OS/2 !! Most people I have heard from seem to agree. I've also had one fella who said it was a dog on his system! All I can say is it's worth a try. ESPECIALLY if you are one of the many folks who got W4W already installed when you bought your system ! Good luck and I would appreciate hearing how it works for you (good or bad)... Ed Meloan RA-USA - 803-279-5006 FidoNet 1:360/1 For those of you interested in setting up Windows for Workgroups with RemoteAccess, you can obtain Ed's file: RAUSW4WG.ZIP by either logging onto his board and downloading it or by logging onto mine and grabbing it. OR.. you can FREQ the file from either his address 1:360/1 or mine 1:374/6568. °°±±²² MULTTASK.Q&A ²²±±°° Total Lines: 561 Total Size: 26k