A86: Re: Guidelines for Posting
[Prev][Next][Index][Thread]
A86: Re: Guidelines for Posting
>1) Read everything posted and replied to on the list for at least 1-3
>months before you ask a question. Archives for since the list started are
>at ticalc.org. It is strongly advised to read these too if you just
>subscribed.
everyone hates the archives first because they take too damn long to wade
through and second because its not easy to find anything. there should be an
all-around search dump. this would save time and space on this list for most
of the questions.
>4) If it is not relevant to the TI-86 at all, DEFINITELY DO NOT post it.
>There have been 30-40 posts about Windows in the last month, as an example.
> There are other lists and news groups available to discuss that kind of
>information.
we (the users on this list) should be given a key and if so many of us send
the key to the list then the topic should be moderated and no threads should
be let through. this is for when the moderators cant check up on the list.
>
>5) General discussion related to hardware add-ons for the TI-86 should not
>posted. ticalc.org maintains a hardware lists that should be used for this
>purpose.
unless its for info on making drivers to run the hardware
>6) DO NOT reply to irrelevant postings. As Dan Eble (the moderator for
>this list, and co-creater of ZShell) has said, ignore it and it will go
away.
most of the time it doesnt work directly because ppl keep starting it up
again so thats why the moderation
>7) Do NOT post 100 lines of code and ask why it doesn't work. No one has
>time to disect a huge routine and debug it for you. Posting 5-10 lines
>with comments is acceptable. You should be able to narrow down the problem
>yourself.
true....use 'breakpoints' to try to debug it first, but i think that if
youve tried all day to find a bug then you can send the asm file. directly
posting in an email isnt that good because it adverts ppl from helping and
they usually trash it and hate ppl that do it that way.