PGOETZ@LOYVAX.BITNET (03/01/88)
Miscellaneous stuff:
Crack:
Odyssey: The Compleat Apventure
Synergistic Software
recently on Softdisk
When I bought my Apple (early 1980), Odyssey and Zork I were the best games
available. But you couldn't play Odyssey without Integer BASIC or 64K, so I
never did until Softdisk put it on a disk in Applesoft ($10 - $5 coupon if you
are a Softdisk contributor).
The game is still fun, but just too hard. I needed help. Like my drill
sergeant said, "If you ain't cheating, you ain't trying." To cheat I had to
defeat Softdisk's wimpy protection.
Anyway, if you have Demuffin Plus:
1. Initialize a disk.
2. Write a sector starting with 01 AD E8 C0 4C 59 FF or something to stop
the drive & halt bootup to T0 S0.
3. Boot Odyssey.
4. Put in the noboot disk & press reset. It will load T0S0 to $800-8FF, but
won't overwrite the protected DOS.
5. *2000<9000.BFFFM Move DOS out of way
6. Boot normal disk.
7. ]BLOAD DEMUFFIN PLUS,A$803
8. ]CALL-151
9. *9000<2000.4FFFM Move protected DOS back
10. *803G
11. Copy all files to blank disk with wildcard =.
To cheat, interrupt the program at any point with a ctrl-C, change variables
(ie FM = men, BG & BI & Bsomething else control inventory)
][e price: $500 sounds like a reasonable price for a IIe system, since a new
IIe system costs about $750 and a Laser 128 about $350 (I think.)
But why get a IIe?
Wildcard transfer: Alan & Valerie Floeter published a patch to DOS 3.3
which allows the use of wildcards in all file operations, on p. 120-123 of
Nibble Vol. 4 No. 4 (1983).
Fractals: Yes, you can use fractals in arcade games, or so the people at
Lucasfilm? Software who wrote Eidolon & Rescue from Fractalus or something
like that claim.
Preemptive multitasking: The Apple II, let us remember, is as fast as the
original IBM PC. The IIgs is 3.5? times as fast. It is certainly fast
enough. I don't think speed is the problem. The big problem is that
you can't write a program which will generate interrupts on the II
(can you on the IIgs?) There is a 1-wire hardware mod that will cause
the apple to generate 60 interrupts or so per second, I think it was in
Micro about 4 years ago.
Write protection: It is hardware. You CANNOT write to a write-pro:{ected disk.
The fellow who said you could was probably think of protected disks, which are
different.
I modified my Apple 5 1/4 drive so I can override the write
protection or pretend a disk is write protected. I can post schematics
if anyone is interested, but not for a few weeks.
Phil Goetzlaba-4an@web2e.berkeley.edu (Andy McFadden) (03/07/88)
>Article 4846 of comp.sys.apple: >From: PGOETZ@LOYVAX.BITNET Miscellaneous stuff: >Crack: >Odyssey: The Compleat Apventure >Synergistic Software >recently on Softdisk How about a subscription to COMPUTIST? Probably a more appropriate place for this sort of thing than comp.sys.apple... COMPUTIST Subscription Department PO Box 110846-T Tacoma, WA 98411 Features copy protection removal for Apple II's, some Mac stuff, and (recently) an occasional IBM program. Also has program modifications, cheats, and the usual character editing/map listing programs. Subscriptions are $32/year. >Preemptive multitasking: The Apple II, let us remember, is as fast as the > original IBM PC. The IIgs is 3.5? times as fast. It is certainly fast > enough. I don't think speed is the problem. The big problem is that > you can't write a program which will generate interrupts on the II > (can you on the IIgs?) There is a 1-wire hardware mod that will cause > the apple to generate 60 interrupts or so per second, I think it was in > Micro about 4 years ago. >Phil Goetz On the //gs, you can generate interupts at 1 seconds intervals, 1/4 second, 1/60 second, or on each scan line. All from software. That should be enough. -- (One of these days, I'll settle on a REAL .signature)
mkao@crash.cts.com (Mike Kao) (03/14/88)
I think comp.sys.apple is a FINE place for talk about copy protection. I mean,
why do people speak of deprotection as a taboo? It's perfectly legal!
--
To insure my reception of any replies, please respond via e-mail. Thanks!
-- Mike Kao
UUCP: {cbosgd, hplabs!hp-sdd, sdcsvax, nosc}!crash!pnet01!mkao
ARPA: crash!pnet01!mkao@nosc.mil
INET: mkao@pnet01.CTS.COMlaba-4an@web7b.berkeley.edu (Andy McFadden) (03/15/88)
>I think comp.sys.apple is a FINE place for talk about copy protection. I mean, >why do people speak of deprotection as a taboo? It's perfectly legal! > >-- > >To insure my reception of any replies, please respond via e-mail. Thanks! > > -- Mike Kao It's not taboo. I just feel that it belongs elsewhere. Most deprotection stuff can be found on BBSs, magazines (I gave one a while back; there may be another one called the "Software Protection Digest" laying around here somewhere), or sold as text files on disk. Anyone who is really interested should look there. I would like to see this newsgroup be used to discuss current Apple // products, problems, and questions; if I want to read about someone's latest "warez" (or similarly misspelled items) I will look in an appropriate place. Incidentally, "talk about copy protection" is different from "give methods for defeating copy protection". The former belongs in a philosophical newsgroup, while the latter belongs elsewhere. - Andy -- "Wise man say: be wary of fony phreaks."
PGOETZ@LOYVAX.BITNET (03/16/88)
Tramp: The Apple III and the Lisa are two entirely different computers. Which
do you mean? The III came with a II emulator program (it could only
emulate a 48K II, I think).
Craig Williamson: I bought a keyboard & case combo for my II+ from Jameco (I
think) which I really like. It has full lowercase, extra characters like
_\[]{}, a numeric keypad which I never use, and ROMed-in macros (ie
ctrl-; or something is CALL-151, ctrl-2 is CATALOG). It has both autorepeat
(like the IIe) and a repeat key (like the II+). The repeat key repeats
twice as fast as a standard Apple, a great help if you do any Applesoft
programming (I don't know how Apple got away with such a lousy editor;
the Commodore PET 2001 did full-screen editing in 1976 or 77).
Keyboard & case cost around $90? about 3? years ago.
Andy McFadden: I, too, think info-apple is a fine place to talk about
specific methods for deprotecting Apple software. It is an Apple forum,
for everything relating to Apples. And copy-protection teaches you many
things about the Apple. I find copy protection interesting. I have several
games which I bought, deprotected, and never used (or traded) - the protection
was more interesting than the game. If you don't like it, don't read those
messages. I also support the distribution of Apple BBS numbers,
regardless of what obnoxious names they have given themselves. Caveat hackor.
I happen to believe that information should be shared, so it's true I have a
knee-jerk reaction to anybody saying "Don't give this information here," but
in this case I think it is justified.
I'd like DDD too.
comp.apple.binaries: When this vote was being taken, I tried to vote but
don't think my vote got thru. Anyway, I never saw a SINGLE message
explaining just WHAT comp.apple.binaries would be (I still don't know
if it would be a file server or a newsgroup). So don't complain of
apathy to me - how do you expect us to get excited about something which
you never tell us what it is?
BTW, does anyone know how to find other groups on the net like this one?
Phil Goetz
PGOETZ@LOYVAX.BITNETmkao@crash.cts.com (Mike Kao) (03/17/88)
> It's not taboo.
Yet you treat it as such in your talk. Why is this subject not "appropriate"
to a general Apple users' forum? I believe that any topic that is legal is
germane. I think too many people equate talk of deprotection to piracy. The
two are distinct. Isn't there a clause somewhere grants people the right to
make archival copies of their software? If so, then why can't people discuss
HOW to do this out in the open, instead of being referred to some "underground"
magazine?
--
To insure my reception of any replies, please respond via e-mail. Thanks!
-- Mike Kao
UUCP: {cbosgd, hplabs!hp-sdd, sdcsvax, nosc}!crash!pnet01!mkao
ARPA: crash!pnet01!mkao@nosc.mil
INET: mkao@pnet01.CTS.COMlaba-4an@web2e.berkeley.edu (Andy McFadden) (03/19/88)
In article <2692@crash.cts.com> mkao@crash.CTS.COM (Mike Kao) writes: >> It's not taboo. > >Yet you treat it as such in your talk. Why is this subject not "appropriate" >to a general Apple users' forum? I believe that any topic that is legal is >germane. I think too many people equate talk of deprotection to piracy. The >two are distinct. Isn't there a clause somewhere grants people the right to >make archival copies of their software? If so, then why can't people discuss >HOW to do this out in the open, instead of being referred to some "underground >magazine? An underground magazine?!? They've been publishing for about five years now, advertising in nibble, softalk, and a number of other places. Hardly underground. I just don't want to see this turn into a place for posting deprotection methods, for the same reasons I don't want it to be a place where people discuss the civil rights of armadillos: it's out of place. I have nothing against deprotecting software; in fact, I strongly encourage developers to distribute software without copy protection. But if you want to discuss it, start a new newsgroup. I'll be the first to subscribe. -- "They want to make backups?!? We gave them two copies, one on each side of the disk!" - Utilico Microware [inferred]
laba-4an@web2e.berkeley.edu (Andy McFadden) (03/19/88)
>Andy McFadden: I, too, think info-apple is a fine place to talk about > specific methods for deprotecting Apple software. It is an Apple forum, > for everything relating to Apples. And copy-protection teaches you many > things about the Apple. I find copy protection interesting. I have several >games which I bought, deprotected, and never used (or traded) - the protection > was more interesting than the game. If you don't like it, don't read those > messages. I also support the distribution of Apple BBS numbers, > regardless of what obnoxious names they have given themselves. Caveat hackor. > happen to believe that information should be shared, so it's true I have a > knee-jerk reaction to anybody saying "Don't give this information here," but > in this case I think it is justified. >Phil Goetz >PGOETZ@LOYVAX.BITNET Well, you're certainly entitled to your opinion. The problem that often occurs is that once deprotection methods start getting posted, everybody and his cousin Fred start posting messages everywhere. Saying that I shouldn't read those messages is fine, but tell that to the usenet sysops who have to store these things, pass them down the line over (often expensive) telephone lines, and so on. I simply feel that there are much better ways of distributing this kind of information. I've said it before and I'll say it again: I have nothing against software deprotection [unlike certain highly flammable people]. But there's no point in blasting twenty gigabytes of info across the news. -- "signature" "no, really. that's my signature." "A moose bit my sister once..."
PGOETZ@LOYVAX.BITNET (03/24/88)
Misc. copying trivia Piracy (something new, I think) Keyboard update EOA boot code F-15 Strike Eagle Test players Wes Williams: > 1. How does the " copy all you want until the disk has been booted one time" work? A disk could insist on writing to itself when booted (refuse to continue until you remove the write protect tab). However, this would have no value for protection. More likely, you mean programs which allow you to make a certain number (like 1) of backups. Simple. They write a note to the original saying "this guy's already made a backup" when they make the backup with a special copy program included with the program. > 2. How does the "copy from the original but not from a copy" work? In most cases like this, the program does a nibble count, so a working copy has to have the same number of nibbles per track on at least one track. It's harder to get this right off a copy. > 4. I have seen protected software self destruct an original when a copy program is run to make a backup. As these originals are write protected, how is the protected software screwing things up? It isn't. Sorry, you're wrong. Something else makes them go bad, you can't write over a write protect. If there is no write protect, the only way I can think of this could happen is if company A puts out a copy program which checks each disk to see if the user is using it to copy itself, in which case it would erase the original if possible. Then company B releases programs with the same signature (which they get from examining the copy program) so the copy program erases them too. But this has never happened. So if you don't understand it, don't worry. Piracy (bear with me): I've heard many, many flames on the subject, but I've never heard anyone who shares my views. They are: a. Those involved with computers are programmers and users. b. Programmers want to make money. c. Users (including programmers) want to utilize their system in as many ways as possible. The user should have and understand a core of application programs (Appleworks, Applewriter, etc.) But to effectively use his system he also needs a slew of utilities: copy programs, sector editors if he knows how to use them, file translators, terminal emulators, archiving programs (despite the fact that there STILL don't seem to be any for the Apple), system verification programs like Apple-Cillin, etc., etc. d. Few people can afford to fully utilize their computer under current market conditions. This is because program prices are targeted at people who would use the program often, yet effective utilization of the computer implies having professional packages for anything you might want to do. So, the problem is the tension between the need for users to utilize their systems, and for programmers to make money. It is important both that users can get their hands on whatever they need, and that programmers are paid enough to keep the programs coming. The ideal solution, which I try to follow myself, is to buy enough to maintain a market and pirate enough to use your system. I would say that allowing yourself to pirate about 10 programs for every 1 you buy would be reasonable. I buy programs which I plan to use regularly, or which I need for my work. If I don't need a program but think it might come in handy sometime, I copy it. This comes out somewhere near a 1:10 ratio. Admittedly, this can fail when you copy a program you don't think you need and then find out you can't live without it. But, 1) this is a kind of statistical ethics, and small problems aren't statistically significant, and 2) you probably wouldn't have bought the program anyway. With games, I just worry about the 10:1 ratio and not whether I'm buying the best ones. This is because it is much harder to know before buying if you will like a game. Ex: Among games I bought recently, I found Fahrenheit 451, Amnesia, and F-15 Strike Eagle boring. But this was no problem, as I pirated others which I found I loved. The only radical thing about this argument is that instead of asking whether piracy is right or wrong, I ask what is the best end result for the user and the programmer. So it's a kind of utilitarian relativism, I'm ashamed to admit. The ultimate goal is to advance the quality of software and of the user environment. The implication for software companies is that ideally they should gear their protection routines so they are not too difficult to crack, but sufficiently difficult that only a moderate amount of pirated copies will circulate. Of course I don't expect them to do this. I might if I sell a program. Craig Williamson: The keyboard I mentioned is from JDR Microdevices, now for $69 or so. It also includes a shift-lock, BTW. Whoever asked about Electronic Arts boot-code tracing: I did trace their code, and on all their games I've cracked (which is about five) the code looks so tricky because they use an interpreter to interpret what is essentially a subset of 6502 assembly language. The only reason is to confuse boot code tracers. I wrote a disassembler for EOA interpreted code; I was going to publish it in COMPUTIST about a year ago but never wrote it up because they stopped paying for contributions. (Shame on me, I know I'm supposed to write out of concern for the computer community, but it's hard to find the time to do it right without money. I don't mind blowing off essays for info-apple, but when you put it in print I want it to be right.) If there's interest, I'll provide details. F-15 Strike Eagle, from Microprose: Has anybody cracked F-15 Strike Eagle? I've disabled three protection routines already & it still doesn't run. None of the cracks in COMPUTIST go beyond the first two routines. (Info on Silent Service would be applicable.) To everybody who sent me a SASE to test my adventure: I'll try to get the envelopes mailed out by March 28 or so. Be patient. There are some significant bugs still. Phil Goetz PGOETZ@LOYVAX.BITNET
DSEAH@WPI.BITNET (04/23/88)
My favorite all-time disk zap utility for DOS 3.3 has always been Zap from the Bag of Tricks disk. I find myself in need of a ProDOS block/sector editor of the same caliber. I heard that Bag of Tricks II has such a zap on it, but can not verify this myself. Help! Hallooo! Anybody in Taiwan on Info-Apple? I am going back to 'Wan this summer, so I was just curious if there were any die-hard Apple loyalists left. My good friend Mark Kern, who left a year and a half after I, mentioned that there is a local chapter of APDA in Taipei. And goody for me, I am bringing my GS, sans RGB monitor (*sob*). I suppose I had better bring receipts for the equipment upon return to the US, lest the curs in Customs jump all over me. Dave Seah --- Rockin' at WPI +-----------------------------------------------+---------------------------+ | Bitnet: DSeah@WPI.Bitnet | We can't receive files! | | Internet: DSeah%WPI.Bitnet@CUNYVM.CUNY.EDU | EMAIL only! Apples Rock! | +-----------------------------------------------+---------------------------+
laba-4an@web3d.berkeley.edu (Andy McFadden) (04/23/88)
In article <8804222308.AA02239@wpi.local> DSEAH@WPI.BITNET writes: >My favorite all-time disk zap utility for DOS 3.3 has always been >Zap from the Bag of Tricks disk. I find myself in need of a ProDOS >block/sector editor of the same caliber. I heard that Bag of Tricks II >has such a zap on it, but can not verify this myself. Help! Copy II+ v8 has a block/sector editor, but it doesn't have as many features as Zap does. It's better than Apple's DiskEdit program; that didn't even have a search function. -- laba-4an@widow.berkeley.edu (Andy McFadden)
tmetro@lynx.northeastern.EDU (07/25/88)
Does anyone know:
1. Of an "input-anything" routine for AppleSoft that is public domain and
compatable with BASIC.SYSTEM? I need this for disk access to avoid
INPUT A$'s problems with punctuation. GET A$ is too slow.
2. Where to get the source code to FredWriter or FreeWriter?
3. A program that will allow you to reconstruct a file (text) from
sectors (DOS 3.3, ProDOS, and Pascal)?
4. A squeeze/unsqueeze utility that will work as a command from
BASIC.SYSTEM (not a .SYS file)?
5. A spell checking program that will process plain text files
or a "dictionary" data file that could be used for a spell
checking program.
___________
/ Tom Metro \_____________________________________________________________
| _ _ |
| INET: tmetro@pro-angmar.uucp --/\/\_| |_| '- DigiTell, Inc. |
| ARPA: crash!pnet01!pro-angmar!tmetro@nosc.mil Newton, MA |
| UUCP: [ihnp4 sdcsvax nosc]!crash!pnet01!pro%angmar!tmetro |
|_Alternate: tmetro@lynx.northeastern.edu__________________________________|
"The Ghost crowd supports me. They're "BOO"-ing you!" -Hobbes
wes@csd4.milw.wisc.edu (Wesley James Vokes) (07/31/88)
In article <memo.39233@lynx.northeastern.edu> tmetro@lynx.northeastern.EDU writes: > >Does anyone know: > > 1. Of an "input-anything" routine for AppleSoft that is public domain and > compatable with BASIC.SYSTEM? I need this for disk access to avoid > INPUT A$'s problems with punctuation. GET A$ is too slow. > Tom, This is sloppy, and I'm writing this on the spot, but it'll give you an idea as to how to write your own subroutine to use. Here's a short listing, I'll explain it after I've typed it in. 1000 REM Keyboard Input Subroutine 1005 A$ = "" 1010 FOR X=1 TO 16: 1020 Poke -16368,0 1030 A= PEEK (-16384) 1040 IF (A>127) THEN 1060 1050 GOTO 1020 1060 B$ = CHR$(PEEK(-16384)-128) 1070 IF B$ = "" THEN 1100 1080 A$ = A$+B$ 1085 POKE -16368,0 1090 NEXT X 1100 POKE -16368,0 1110 RETURN Ok, the key to this is, that at location 16368, in applesoft, the highbit ASCII value of the last letter typed is stored. I wrote the program to allow 16 letters max, and it takes each key typed and adds it on to the string A$. Noene of the keys typed are displayed on the screen, so you might want to put that in. Also, if they try to backspace, it won't work. But, you can customize it toaccomodate backspacing with alittle work. I hope this works. Any questions, just send my account email. _ ____ ' ) / arpanet: wes@csd4.milw.wisc.edu / / / _ _ bitnet: wes%csd4.milw.wisc.edu@wiscvm.bitnet (_(_/ </_/_)_ UUCP: !ihnp4!uwmcsd1!csd4!wes p/g - "grace under pressure"
SEWALL@UCONNVM.BITNET (Murph Sewall) (08/02/88)
> 5. A spell checking program that will process plain text files
The Sensible Speller will do that (as well as work with practically
every Apple word processor known to man).
Murph Sewall Sewall@UCONNVM.BITNET
Business School sewall%uconnvm.bitnet@mitvma.mit.edu [INTERNET]
U of Connecticut {rutgers psuvax1 ucbvax & in Europe - mcvax}
!UCONNVM.BITNET!SEWALL [UUCP]
-+- My employer isn't responsible for my mistakes AND vice-versa!
(subject to change without notice; void where prohibited)
"It might help if we ran the MBA's out of Washington." - Adm Grace HopperSEWALL@UCONNVM.BITNET (Murph Sewall) (08/02/88)
>In article <memo.39233@lynx.northeastern.edu> tmetro@lynx.northeastern.EDU > writes: >> >>Does anyone know: >> >> 1. Of an "input-anything" routine for AppleSoft that is public domain and >> compatable with BASIC.SYSTEM? I need this for disk access to avoid >> INPUT A$'s problems with punctuation. GET A$ is too slow. >> > >1000 REM Keyboard Input Subroutine >1005 A$ = "" >1010 FOR X=1 TO 16: >1020 Poke -16368,0 >1030 A= PEEK (-16384) >1040 IF (A>127) THEN 1060 >1050 GOTO 1020 >1060 B$ = CHR$(PEEK(-16384)-128) >1070 IF B$ = "" THEN 1100 >1080 A$ = A$+B$ >1085 POKE -16368,0 >1090 NEXT X >1100 POKE -16368,0 >1110 RETURN Sorry, but that's not going to do it. The "killer" is 1080 A$= A$+B$ (takes too much time and creates "garbage" - which then takes even more time to "collect"). What Tom needs is an "input anything" routine for ProDOS (there are numerous DOS 3.3 versions -- or perhaps just variants on a version) that will INPUT a line into a single string variable regardless of colons, semicolons, and commas that may be in the line. Such a criter would have to be in machine code (either a routine to BLOAD or something that can be POKEd from DATA statements). Isn't PEEKing the keyboard character buffer the equivalent of GET A$ (or at least not noticeably quicker)? Murph Sewall Sewall@UCONNVM.BITNET Business School sewall%uconnvm.bitnet@mitvma.mit.edu [INTERNET] U of Connecticut {rutgers psuvax1 ucbvax & in Europe - mcvax} !UCONNVM.BITNET!SEWALL [UUCP] -+- My employer isn't responsible for my mistakes AND vice-versa! (subject to change without notice; void where prohibited) "It might help if we ran the MBA's out of Washington." - Adm Grace Hopper
jason@lakesys.UUCP (Jason) (08/03/88)
In article <8808011402.aa04788@SMOKE.BRL.ARPA>, SEWALL@UCONNVM.BITNET (Murph Sewall) writes: > [Original post & program deleted - part of Mr. Sewall's post deleted as well] > > What Tom needs is an "input anything" routine for ProDOS (there are > numerous DOS 3.3 versions -- or perhaps just variants on a version) that > will INPUT a line into a single string variable regardless of colons, > semicolons, and commas that may be in the line. Such a criter would have > to be in machine code (either a routine to BLOAD or something that can be > POKEd from DATA statements). The input anything routine I have works under both DOS 3.3 and ProDOS. Unfortunately, it's from Call A.P.P.L.E.'s "All about Applesoft", and, it would seem, copywritten & un-put-here-able. > Isn't PEEKing the keyboard character buffer the equivalent of GET A$ (or > at least not noticeably quicker)? The GET A$ does a few more things: It goes through the ROM code until it hits the re-routing vector, which calls ProDOS' BI or DOS 3.3. In either case the OS checks to see if there's a file being used for input, in which case it goes to internal code. If there's no file open for input, the OS puts the original vectors back in, and calls them. If unchanged (by things like keyboard macro expanders and the like), the ROM gets called, which actually checks the keyboard. Then, back up through the levels until we return to Applesoft... All the peek has to do is translate the address of the number to be PEEKed, and encode the number returned (actually, there's some other overhead from FORMEVL, but it would seem that less time would be taken overall - quite possible I'm wrong on this one, tho'). As for the need for speed in getting characters in Applesoft, it really doesn't make all that much difference - I can't out-type GET's, and the PEEK method can't be used with disk files, which is generally where the speed is needed. Then again, Applesoft in general isn't the worlds quickest way to do things :) (At least as far as execution times go) > Murph Sewall Sewall@UCONNVM.BITNET -- Jason - Not your average iconoclast | UUCP: uwvax!uwmcsd1!lakesys!jason
mdavis@pro-sol.cts.com (Morgan Davis) (01/11/89)
One note. If you do make a reliable network connection to the GBBS domain, *YOU* will be held responsible for any and all problems that are caused in that chain of the connectivity, just as *I* am responsible for any problems arising from the ProLine network. GBBS Pro users, as a whole, do not have the reputation that netters respect. For that matter, I think most UUCP net users look down (frown) upon ProLine as well. It gets exponentially WORSE in the GBBS domain. So, keep your knightstick at the ready. Please make all documents known to GBBS sites that you get into the network. This includes network rules, syntax, semantics, signatures, mail standards, do's and dont's and all that kind of stuff. It is imperative that every GBBS sysop become a net expert, as irresponsible sysops will be a major detriment to all of us. Realize that allowing your network to connect with ProLine is a gift, given on the pretense that there will be no trouble. But should trouble arise, I, Bill Blue, and other sysops that have some stake in all of this will not hesitate to refuse connectivity with your network of sites. I just had to say this. I hope you realize the seriousness of all of this. --Morgan Davis UUCP: crash!pnet01!pro-sol!mdavis ProLine: mdavis@pro-sol ARPA: crash!pnet01!pro-sol!mdavis@nosc.mil MCI Mail: 137-6036 INET: mdavis@pro-sol.cts.com APE, BIX: mdavis
dvac@drutx.ATT.COM (Daniel Vachon) (01/13/89)
In article <8901110116.AA01397@crash.cts.com>, mdavis@pro-sol.cts.com (Morgan Davis) writes: > One note. If you do make a reliable network connection to the GBBS domain, > *YOU* will be held responsible for any and all problems that are caused in > that chain of the connectivity, just as *I* am responsible for any problems > arising from the ProLine network. > ..... > I just had to say this. I hope you realize the seriousness of all of this. > > --Morgan Davis > Morgan, not to rag on you or anything, but I don't think he was thinking about networking with uucp or your proline for that matter... I too have written a networking segment for GBBS Pro, and it is up and running right now on about 10 boards from california to colorado to ohio to Mass. I have no desire to network with uucp or proline. I just wanted to establish a way for sysops of other GBBS boards to be able to keep in contact with each other. Most of the time I have trouble finding time to call the boards I want to call (and the LDX bills don't help either), so I wrote the networking seg to network amongst our boards....simple in theory, and if anyone has a problem with the network, I am willing to iron out the bugs...I mean I wrote it! Just an opinion....it seemed you got kind of edgy when someone else said they wanted to design a network for apples.... I felt this had to be said.... Later -Dan