[no subject]

> It's example source, treat it as such.. I shall pass on ideas, and complaints
> that it "sucks so bad" that I shouldnt have posted it. I didn't write it as
> a replacement for proterm.. :-)

> anyways, I noticed that it has :ram5: stuffed in the beginning of the
> filename and I have always had troble binscii-ing stuff with
> sscii.. If there are enough people who need it, I can either put it up
> on ccosun, or post it again (its pretty small)

Stephan,

I spent the evening trying to come up with an explanation of what the
various files I've downloaded from the internet really do. Most were no
trouble, however, there were some that were real problems. Yours fell
into the later category:

I could deal with a file :RAM5:...  I just deleted the :RAM5: prefix.

I was then left with a file of unknown format - I downloaded to to my
Apple anyway where I gave Shrinkit a try and lo and behold - it
unpacked it whereupon I got a:

SHELLTERM
SHELLTERM.L
SHELLTERM.S

Notice, nowhere in the above is there a README or a SHELLTERM.1 file
that gives the person that downloaded the file a clue as to what the
hey it does. It should NOT be the user's duty to read the .S source
file to figure out what you intended. The .S file is for the "hackers"
in your audiance. If that is your only audiance then you should have a
README file that points this out.

I don't want to seem to be picking on you alone since you had friends:

EDITW	        - A S16, a PIC, and two $B5 files - What does it do?
                  I don't have a clue. Do I dare boot it?
MOD-PIANO-PLINK - I think it is music of some sort - what do I do with it?
KWAI Music      - Same comment as above
FILLMAZE        - Jason Harper - Something on board, however, what is the
                  goal of the game?
PERMCDAs        - Two files - I run both and see no difference with my
                  CDAs. Have I runied my life by running them?
ROBOTS          - Docs on board, however, with a filetype of 0 they
                  are not recognized by most/all text readers. I will
                  have to change the filetype.
COFF            - The README is in Unix format i.e., uses ^J rather than
                  the Apple ^M for end of line. I can deal with this,
                  however, it shows a lack of understanding of the audiance
                  for the program.

My bottom line - AGAIN - to those uploading is: Do NOT underestimate
how dumb us users are :-)

Kind Regards,
-- 

		Joe Walters att!ihlpm!bird, IH 2A-227 (708) 224-7189
		To know, and not to do, is not yet to know