ftp.wwiv.com

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

/ ftp.wwiv.com / ftp.wwiv.com.zip / ftp.wwiv.com / pub / HATCH / WWIVNEWS.ZIP / 9403_7.NWS < prev next >

Wrap

Text File | 1994-03-02 | 26KB | 501 lines

Log on as NEW user. WWIV Sysops will be validated automatically. G = Guest Sysop Account systems [GSA] Log on info - Name : Guestsys PW : WWIV Phone: 0000 ───────────────────────────────────────────────────────────────────────────── DIRECTORY ───────────────────────────────────────────────────────────────────────────── Files & Account type-| Services Protocol-| | ACDEGILMNOPQSVWX*#@!%^ Node Net Phone BBS Name St Sp | | ───────────────────────────────────────────────────────────────────────────── c M w *# 7 1 415-349-4141 Crest CA 16 <!$ A W *# 856 1 011-81-611-733-4832 Shinobi's SwordJA 14 <!$ A c ilm w *#@ 2050 3 512-631-5841 The Dragons Den TX 14 !$ A C ilM w *#@ 2051 3 512-631-9417 The Dragon's Den II TX 14 !$ A A DEG Mnop s wX # 2077 1 210-659-7267 Sam's BBS TX 14 <!$ A c lm w % 2456 1 214-570-5950 The Insane Asylum TX 14 <!$ A ACDeGilMN P svwX 2623 1 206-252-1568 The FIREHOUSE! WA 9 >! AG cdeg n p s wx 2660 1 216-743-4215 R.A.D.S Y-TOWN BBS OH 9 ! AG cdeg w 2661 1 216-337-0758 K's Korner BBS OH 14 !$ AG CD n s W *# 2914 3 209-549-0423 Anything Goes BBS CA 12 !$ A AcDEG lmNOP SvwX 2932 1 209-274-0621 Ship's BBS CA 14 !$ A c mn p s wx ^ 3081 3 310-973-4949 Entity CA 14 !$ AG cd gilm p ^ 3085 1 310-790-8560 The SlowSleep BBS CA 14 !$ G acdeg mn p x 3101 1 301-229-2957 The Star-Lit BBS MD 14 !$ A c m w 3106 1 301-208-0832 Dupont Plaza [ASV-GSA]MD 2 AG cdegilmnps wx*# !%^ 3314 3 303-755-1884 Erana's Peace CO 14 !$ A ACDEG NoP wX %^ 3359 3 313-668-0221 Freewheelin' BBS MI 14 !$ A c n p s w * % 3459 1 314-861-1820 The M&M Factory MO 14 <!$ G egilM !% 3476 3 314-939-4113 Callahan's Crosstime MO 9 ! AG c il W 3484 1 314-963-7960 Rap City BBS MO 2 G a D g MN P S X 3495 1 314-821-7985 Land of Little People MO 14 !$ AG ac eg lmn w 3518 1 305-587-0185 The Samurai Palace FL 14 !$ A g lmnOp s wx # 3900 3 309-452-2838 Adventurer's Corner IL 21 <!$ A c mn w 3905 1 309-452-2616 The Dark Side IL 2 A Cd ilmn p w @ 3950 3 319-296-1529 HIT BBS IA 16 <!$ AG d il n p s w ^ 3956 3 319-277-0166 Diamond's BBS IA 16 <!$ A acdEgILMn p s wx 4052 2 410-252-8355 The Futile Maelstrom MD 14 !$ A cd g M p x 4065 1 410-374-4696 Doug's Den <CIN> MD 14 !$ A 4075 1 410-315-9854 Central Station MD 2 AG acd g p S x 4079 1 410-290-3752 Sorcerer's Quarters MD 14 !$ AG ACDEGi mNOP SvWX ~4654 1 416-208-7029 Sledgehammer Base BBS ON 14 !$ AG acdi mn p s wx 4656 1 416-267-6559 Cloud 9 BBS ON 9 ! AG acDEG mnop wX ~4703 1 407-352-4699 The Professor's Lab FL 14 !$ A acdEg mn p s wx 4704 1 407-384-7166 No Name Yet!! BBS Fl 9 >! AG ACDEgI MNoP s WX @ 4707 3 407-994-4427 Patriot Games MS 14 !$ AG ABdEG mnoPs wX 5079 3 510-522-3583 StarPort Valhalla CA 14 !$ A cdegIlmn p s x 5212 1 502-352-2169 The Barbarian's Hut KY 14 !$ AG ac m 5480 1 514-652-5752 Twiggy's Board PQ 2 A Cd IL N P Svw 5489 1 514-948-4802 CYBERGATE! PQ 14 !$ AG acde ilmn p wx # 5497 3 514-664-4503 Alternative Worlds CN 2 A AcDEGi MNop S wX # 5800 1 508-795-7672 Bears Cave BBS MA 14 !$ A d g w 5809 1 508-251-9812 Omega BBS MA 2 G cdG ilMn p s wX @ 5900 3 509-487 6572 DATA*NORTH*WEST WA 14 !$ AG CD MN W 6101 1 601-388-3745 Hacker's Heaven MS 21 <!$ G cd gi Mn p s w *#@ % 6211 3 602-942-9228 Moon Valley Triangle AZ 14 <!$ AG cd gi Mn p s ! ^ 6259 3 612-935-3505 AeroTech BBS MN 14 !$ AG g mn p w 6401 3 604-578-7634 The BS BBS BC 9 ! AG ACDEGIL V 6460 1 614-282-3409 The GWE BBS OH 14 <!$ A AcDegi mNoP S wX !% 6754 3 617-247-3383 DataExpress MA 14 !$ G AcDEG mNoPqs wx % 6755 1 617-282-7796 BitByteBob's BBS MA 14 !$ AG AcDEG MNOP SvwX ~6970 1 619-446-1316 The Clinic BBS CA 14 !$ AG cd g m ~7105 1 701-746-7778 The Hard Disk Cafe ND 14 ! A a dEg mn w 7111 1 701-293-9197 The Final Frontier ND 16 <!% AG acdegilmn p s wx % 7313 1 703-978-4611 The Church VA 9 ! AG aCDeg Mn p svWx*# 7400 1 704-554-1496 Funny Farm (East) NC 14 <!$ AG C ILM vW # ~7652 1 716-684-7939 BoardWalk [DSS] NY 14 < A acd gilMn p s x 7653 3 716-677-0232 The Cavern [ASV/RIP] NY 16 >!$ A d Gil * 7663 1 716-837-1636 Paragon NY 16 <!$ AG acdegI mnop s wx ! 7663 2 716-691-7257 Lunar Lounge NY 14 !$ A il 7668 3 716-649-3530 The Pinnacle NY 14 !$ A AcdEgI NoP S x 7678 2 716-484-0065 Shadow Canyon NY 14 !$ AG ac mn p s 7686 2 716-283-7236 Tower of High Sorcery NY 9 ! AG d gI Mn p svw ! 7704 2 707-539-8361 Atlantica CA 14 !$ AG d g n p s x 7707 1 707-485-7143 Divers Delight BBS CA 9 ! G CD MN P Svw 7750 1 717-823-0027 The Doctor's Office PA 14 !$ AG cdEgi M w *# 8135 1 801-774-5574 The Sandbox ][ [ASV] UT 14 <!$ A cd g lMnop s w * 8251 1 812-877-4342 The Resource Center IN 14 <!$ AG m w 8270 1 812-331-1796 The Gate BBS IN 2 AG a d Mn p w 8307 3 803-749-3171 Dream World BBS SC 14 !$ A CD gIL NopqsVWx #@ ^ 8315 3 803-731-0690 Trading Post [SOUTH] SC 16 <!$ A acdeg mn p s wx 8375 1 813-434-0911 The Cat Box BBS FL 16 <!$ A i m w ^ 8433 1 804-766-3192 Collage VA 14 !$ A acdeg n vw 8513 1 805-937-5354 Info Center II CA 14 !$ AG acdegilMn p s W # 8861 3 818-848-4101 Blue Thunder BBS CA 16 <!$ A aCDeGilMN P s wx 9353 3 913-651-5129 Back At The Ranch BBS KS 14 !$ AG c m w 9402 1 904-771-7770 Data*West BBS FL 2 AG Ac E n p s wx 9408 1 904-223-5374 The Timewarp FL 14 AG c e lm w 9654 1 916-891-3546 Mirage Works CA 2 G acd I mn w # ! 9680 3 916-222-8911 Maestro BBS CA 14 <!$ A cd m w 9692 1 916-674-0947 The DFLmemCyberStop CA 9 ! A Cd i Mnop s ! 9707 3 907-356-7632 Trading Post [NORTH] AK 14 <!$ AG c g % 9933 1 909-370-3773 Damar's Haven CA 9 ! A de m s ~9939 1 909-931-7395 Dyson's Sphere CA 2 AG m ~9949 1 909-621-2007 The Wireless Cafe CA 2 AG acdegIlmn p svwx ! 9969 3 919-497-2963 The Pet Shop NC 14 !$ A AcDEG MNOP S wX 9982 2 919-851-2657 Theater of Vampires NC 14 !$ A M 13452 1 314-821-5146 Ronda's Riverboat BBS MO 14 !$ AG C MN 15267 1 512-595-0838 Forbidden Borders TX 14 !$ AG cDegil Nop S wX 15269 1 512-592-8054 Secret City BBS TX 14 !$ AG cdeg Mn p s Wx ^ 19955 1 919-676-0738 The Rubicon NC 14 !$ A a e x ^ 29951 1 919-571-1467 Alchemist's LaboratoryNC 2 < A g m s 29958 1 919-523-3730 The Wizard's Conclave NC 14 !$ AG ───────────────────────────────────────────────────────────────────────────── GUEST Sysop ACCOUNT INFORMATION: ──────────────────────────────── Name :Guestsys PW :WWIV Phone:0000 To apply for a listing, to update your's, or for additional info on setting up a GSA, PLEASE contact 1@6211 LISTING ERRORS: ─────────────── I don't have time to "Police" all the listings in this directory. I take the Sysop's word for the correctness of the listings. If, in your calling, you find any descrepancies, PLEASE E-mail 1@6211 with that info, and I will look into it. As usual, all comments, complaints, and suggestions are welcome. That is where I get the ideas to improve this directory. ───────────────┬─────────────────────────────────────────────┬─────────────── │ Type 0 Forum │ │ Edited by Omega Man (WWIVnet 1@5282) │ └─────────────────────────────────────────────┘ Dear Editor: Recently, the 512 AC suffered a rather interesting connection problem I'd like to share with the readers of WWIVnews. While this was a localized problem, the nature of the problem was such that it could easily happen again if one isn't too careful. First, a little background: Want to establish a direct connection with someone instead of going through a server? Be aware there are some things to consider before going ahead with a direct connect. How will this connection affect the other connections in the network, and will you end up being the carrier for the LD traffic for more than just yourself. A good analysis of your connections could prevent you from finding out after the bills come in that connecting directly to your good buddy's BBS in Saskatchewan has also made you the conduit for half that area's packet traffic! Remembering the way WWIVnet logic is applied to node numbers may prevent headaches and loss of money, and sketching mail routes between nodes on a piece of paper also helps a great deal. The way it works is like this: If your direct connection request causes fewer hops to occur between someone else and your friend, you route will be the route chosen. If the number of hops between systems is the same or more as having a network servers handle it, the network server takes priority. Got all that? Ok, with this in mind, here's what happened to AC512 that caused all the headaches: OK, remember that mail going from point A to point D will take the shortest route. Default is to go to a netsever, or a node with the lowest number if there are several alternatives. In our situation here, we had Filo's net server, point A, (@1040) routing mail (normally) through point B, @1021, which then goes to point C (@1043) our LD netserver, then to point D (@1041) our local server, and then to all of us here in Austin. Filo had set one of his connects on 1040 to a BBS located in Spain (yes, that's in Europe, of all places!), WWIVnet @871. This node was having some trouble connecting with @1040, so Filo added a connect to @1041 to hopefully cure @871's connect problems. As a result, @1040-@871-@1041 is now that the routing being taken for all the mail coming to Austin. Can anyone see what happened? Since @871 hasn't connected to Filo since the change to the connections, a 9+ Meg file started accumulating on Filo's server. Meanwhile, our traffic was waiting to go overseas before coming back here! All this dawned on me as I was trying to determine why the mailpacket arriving on @1021 was not containing ANYTHING for our local systems, as well as some LD systems that connect to @1043. When I started looking for connects that @1040 and @1043 have in common, I saw the "short-circuit". A quick voice call to Filo corrected the matter, and as expected the dam did burst open and Austin was flooded with about 10 days worth of backlogged network traffic. While some might see this as just a local problem, it could just as easily happen anywhere if people aren't careful about setting up their network connections. ───────────────────────────────────────────────────────────────────────────── Dear Editor: DOS 6.2 has arrived, and once again we're given dull white text on black as the command line default. While it's true that we can always use ANSI.SYS and the PROMPT command to modify things, this takes up memory that some of us can find a better use for it. This is especially true when all some of us want to do is simply change the default screen colors to something more readable on an aging, fading monitor. Here is the procedure for changing the default colors. Some of the addresses may be different on some releases, but the principle is the same. Remember, the new color only take effect when you do a CLS. DEBUG \COMMAND.COM -RCX CX BAE5 -S 100 L BAE5 CD 10 22CC:432B 22CC:4337 22CC:435F 22CC:436C 22CC:4370 22CC:4376 -U 4300 - - Enter U a few times - -U 22CC:4366 B406 MOV AH,06 22CC:4368 B707 MOV BH,07 22CC:436A 32DB XOR Bl,BL -Q What you're looking for here is the MOV BH,07 instruction. Remember to hit ENTER twice after the RCX instruction. The address you get after RCX and the listing when you enter the S command determines where you start looking for the MOV instruction. Note that in the example above, the address for the MOV you're after is 4368. Add 1 to that address (whatever you come up with) and then do the following: DEBUG \COMMAND.COM -D 4369 L1 22CC:4369 07 -Q You should see 07 off to the right, otherwise go back and search again. When you've found the correct address, do the following: DEBUG \COMMAND.COM -E 4369 22CC:4369 07. -W Writing 0BAFB bytes -Q After you do the E instruction, debug will return the address with the "07."; now select the colors you want, and enter them after the period. The first number denotes the background color, while the second is the foreground color. Be sure that you don't enter a number larger than 7 for the first number, or the screen will flash! Here's the list of colors as DOS sees'em: Black - 0 Grey - 8 Blue - 1 Bright Blue - 9 Green - 2 Bright Green - A Cyan - 3 Bright Cyan - B Red - 4 Bright Red - C Magenta - 5 Bright Magenta - D Brown - 6 Yellow - E White - 7 Bright White - F You may want to change where you start searching from. The important thing is to look for the MOV BH,07 instruction. Dipole Vaulter WWIVnet 111@5282 Editor's Reply: While it' *is* true that ANSI.SYS can do the same things this patch does, there are those out there who consider ANSI.SYS a waste of memory even in this day and age of UMB's. Still, the general aesthetic non-configurability of the basic DOS environment reminds me of how Peter Norton once paraphrased Henry Ford: "You can have it in any color you want, so long as it's black!" ───────────────────────────────────────────────────────────────────────────── Dear Editor: With the release of WWIV 4.23, many a Sysop has voiced concerns that WWIVnet in it's current state may be assimilated inside FIDOnet. I think it's an unwarranted fear mostly found in people who are wary of change. Ive been involved with WWIVnet since August of 1990. I've seen the network grow, change and adapt. In it's present format it has become quite viable. Perhaps it's not as well spread outside North America as FIDOnet, or INTERNET/USENET, however WWIVnet continues to grow and expand. With the multi-language addition it will most certainly attract new systems from other areas world wide. What has made WWIV software popular among those who use it is it's user friendly interface. With a minimum of computer literacy, most have been able to run a netted WWIV BBS. Such is not the case with FIDOnet compatible BBS softwares. In the past year we have seen features such as multi-network capability. This has brought to life numerous WWIV based networks, some which are bound to expand, but most are nothing more then local networks who's well-being is entirely dependent on one individual, the N.C. Most of these smaller nets come and go without affecting WWIVnet. As AC in WWIVnet and IceNET for the 514 area, I've noticed recently that most of the BBSes that have had longevity with WWIVnet also carry either WWIVlink, IceNET as well as local networks. We've had FIDOnet in the 514 area code for as long as I can remember. Twice a local system had decided to gate subs between FIDO and WWIV. Twice it was dropped due to the lack of interest from the majority of the sysops in both networks. Making WWIV software compatible with FIDOnet will permit those who already gate subs or run a dual system to continue to do so. Those who are like myself who like things quick and dirty and had been thinking FIDO will take the leap, but for most it will be nothing more then an extra feature they have the option to use. The philosophy behind both networks is totally different from both the standpoint of the Sysop and also that of the users. We can all enjoy the anonimity that WWIV provides us. This is extremely important to those who are part of visible and not so visible minorities. As a female pagan, I have the opportunity to discuss with others all over without the fear of being persecuted for my beliefs in my daily life. Fidonet does not have the same standards. For instance it is common practice to send files via the network, through automatic request. WWIVnet is a more cost conscious network, where Sysops are concerned about the extra cost of having routing information imbedded in the messages. Even the structure of both networks is different. My understanding is that it is easier to weed out bad apples in WWIVnet, and keep some control over the systems that are in the network. Have you tried moderating a heavy traffic Fidonet conference? Assimilated inside Fidonet? In some people's dreams only. Those who have made the network what it is today will not go Fidonet tommorow. If they had wished to do so, they would have left long ago. Jessica Lovecraft WWIVnet 1@5462 Editor's Reply: As most of you know, I personally have a rather negative stance on Fidonet, its sysops, and its policies. As Fidonet compatibility with WWIV comes closer to becoming part of the basic WWIV package, this issue will become a bit more heated. A future issue of WWIVnews will spotlight the multi-net WWIV, and I'll have a more in-depth commentary on the matter then. ───────────────────────────────────────────────────────────────────────────── Dear Editor: Since the arrival of RIP graphics, many WWIV sysops have encouraged both Wayne Bell and myself to jump on the RIP bandwagon and add RIP graphics to WWIV. This issue is one which has both pros and cons and deserves careful consideration. First, it is not now apparent which, if any, of the competing graphics packages will emerge as the "winner." Of these, there are three that stand out as potential standards - NAPLPS, RIP, and RoboFX. NAPLPS is a graphics package which was available before RIP. It has some decent support and many adherents. Apparently it is more compact in its graphics design. The last blurb that I saw on it mentioned that a terminal program - NAPLPS/JPEG - would have 3D-Windows, CUA/GUI interfacing, mouse support, and built-in protocols including Xmodem, Ymodem, and Zmodem. RIP is the second of the competing graphics programs to be developed and has the advantage of having Qmodem and Telix announce that they intend to support it. It is, however, built to an EGA standard while NAPLPS and RoboFX are built to a VGA standard. RoboFX is the latest entrant to the field. It is promoted by RoboBoard BBS and, according to some, has the best graphics of any of these graphic designs. So, one problem facing WWIV is that of selecting which of these competing products would seem to be the best. At one time, Roland De Graff, the VBBS author thought that his VGIX would become the standard, but apparently he has given up the project after spending several months on coding the VGIX project. A second problem is one of disk space and time on line. As I understand it, these graphical interfaces may be like the ANSI graphics on our own boards and sent over the modem; however, such an approach is time consuming and somewhat slow. The graphics, on the other hand, may be downloaded from the board and triggered by the BBS. In that instance, the actual graphic would be on the user's hard disk and the imaging would be much faster. The problem here (as I see it) is that most users will not want to devote multi-megabytes of their hard disks just to see "pretty pictures". If hard disk space becomes cheaper and/or CD-ROM usage becomes greater, this disadvantage might change rather quickly. However, until users are willing to use their hard disks for such storage, the use of such graphics will almost demand that sysops stay with "standard" menus. A third problem is that it appears that the primary way to obtain such graphic capability is by the purchase of "libraries" from the distributor which are then compiled into the BBS. This would (I think) virtually mean that we would have to distribute some OBJ files as part of the BBS code or that WWIV sysops would have to individually purchase that library code. Currently, the RIP people sell that for $199. The RIP_PAINT program is also $199 and is needed to create individualized graphics unless one registers the shareware version which is $69. The shareware version will produce graphics that can be seen locally but will not produce graphics for over the modem use until it is registered. So, the questions are: 1) Should WWIV Software Services invest in Rip Graphics? 2) Are sysops willing to pay the $199 or $69 for drawing programs to produce such graphics? 3) Are users willing to devote megabytes of their hard disks for storage of RIP graphics. 4) Is RIP the graphic that will "win" the graphics race? Clearly answers to such questions must be determined in the months ahead. In order for us to make the best choice, it will be advantageous for WWIV Sysops to educate themselves regarding these types of graphical interfaces, to call board which use them, and to become familiar enough with them that they can guide us in this choice. Filo 1@2050 WWIVnet Editor's Reply: For those not aware, RoboTerm is out now. Reports from its users say that the RoboFX support is a bit buggy, and not very tolerant of minor menuing errors. Still, it has one definate advantage over RIP, and that's the fact that it supports VGA level graphics. RIP is *still* mired in EGA, which renders it unadaptable for most GUI environments according to several Windows and OS/2 programmers who've looked at the routines. Another problem with RIP is the extortion fees that the designers of the RIP Menuing programs are demanding for their wares. Without getting into a debate over the idiocy of believing that demand can automatically dictate a higher expense for software, the bottom line is that very few, if any, WWIV sysops are willing to pay for any additional software save for the cost of registering WWIV itself. There's a comment a local TBBS sysop once made when comparing WWIV to TBBS. He claimed that he couldn't understand why everyone in WWIV and WWIVnet hadn't registered each and every WWIV-based chain, game and/or util for as low as they cost. In the TBBS world, he claimed, the average cost per onliner is $100, and the average cost per TBBS-specific utility is $150! Compared to these costs, the average WWIV setup is a drop in the bucket! Of course, the average WWIV system has more to offer than the average still-rooted-in-monochrome-RBBS TBBS setup, but that's beside the point. The question still remains whether WWIV Sysops are willing to fork over the bucks to purchase something that's obviously overpriced just to make their systems just a bit more flashier. I'm open to comments on this one, folks. Filo's opened up a serious can of worms, and we need to see if they're worth fishing with! ───────────────────────────────────────────────────────────────────────────── Dear Editor: I've noticed that many people are interested in changing the flashing red on their boards to non-flashing for ALL new users. But usually they don't know what the number codes are for the standard IBM color set, or have a hard time figuturing it out. Here is a simple system to use to figure out the color numbers: 0 Black 1 Blue 2 Green 3 Cyan 4 Red 5 Magenta 6 Brown 7 Grey Add 8 to make it Intense (bright) (brown becomes yellow) Add the color number * 16 for background (ignore to leave black). Add 128 to make it flashy.. So you want Red(4) + Intense(8) + Black-Background(0*16=0) And no flashy. 4 + 8 + 0 = 12. Or look at this way, 140 - 128(flashy) = 12. So non-flashy intense red is 12.