1. Forum
  2. FidoNet
  3. RA UTIL

  • RA_UTIL Echo Suggestions

    From Moderator@1:3634/12 to All on Fri Aug 1 05:47:12 2014

    RemoteAccess Utils Echo Guidelines: rev. 06 Oct 11
    Posting Frequency: 1st and 15th of the month.
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    These are "not" rules per se', but "ideals" which we hope you will
    all agree with and shoot for, within this echo.

    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    1. When anouncing a file is available, give the pertinent data
    concerning the file:

    RA_262SW.ZIP ------------> FileName
    RA ----------------------> MagicName (if available)
    848,297 -----------------> Filesize
    56K V.90 ----------------> Max baudrate
    1:3634/12 ---------------> Address 1...
    2547:1000/12 ------------> Address 2... (and so on...)
    1-919-774-5930 ----------> System Telephone Number
    Via SDS -----------------> Yes/No (was it released into the SDS?)
    Sanford, NC, USA --------> City, State, Country (where you are)
    Anyone May FREQ 24/7 ----> Or do you allow unlisted nodes to freq?

    2. Before reporting what you believe to be a bug, check and double
    check everything, then make your report (often you will find it is
    operator error and not program error). Include enough information
    (pertinent to your problem) in your message, to enable people to
    understand your problem and offer solutions. This may include
    configurations (software & hardware), initialization strings,
    possible TSR programs, etc.

    3. When quoting a message, only quote what is pertinent to your
    response, not the whole message (if possible).

    4. Tearlines should be left as the mail proccessor makes/inserts them
    (35 characters max. none if PID is in message).

    5. When discussing your "views" on any program, be descriptive, explain
    what features you like or dislike (and why?), what works or doesn't
    and limit them to programs which work with (in one way or another)
    RemoteAccess, etc. Getting involved with "Mine is better than yours"
    type of conversations, is not productive and has no place here, or
    in any other conference. Try to maintain an objective view so that
    your post does not come across as software or author bashing.

    6. When posting an ad for a new product, make it "descriptive", but try
    to be reasonable.

    Thank You

    |Andrew Leary, 1:320/119, andrew.leary@tvcconnect.net
    Mark Lewis, 1:3634/12

    Conference Moderators



    * Origin: (1:3634/12)
  • From Moderator@1:3634/12 to All on Mon Sep 1 00:00:20 2014

    |RemoteAccess Utils Echo Guidelines: rev. 29 May 14 |Posting Frequency: 1st of the month.
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    These are "not" rules per se', but "ideals" which we hope you will
    all agree with and shoot for, within this echo.

    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    1. When anouncing a file is available, give the pertinent data
    concerning the file:

    RA_262SW.ZIP ------------> FileName
    RA ----------------------> MagicName (if available)
    848,297 -----------------> Filesize
    56K V.90 ----------------> Max baudrate
    1:3634/12 ---------------> Address 1...
    2547:1000/12 ------------> Address 2... (and so on...)
    1-919-774-5930 ----------> System Telephone Number
    Via SDS -----------------> Yes/No (was it released into the SDS?)
    Sanford, NC, USA --------> City, State, Country (where you are)
    Anyone May FREQ 24/7 ----> Or do you allow unlisted nodes to freq?

    2. Before reporting what you believe to be a bug, check and double
    check everything, then make your report (often you will find it is
    operator error and not program error). Include enough information
    (pertinent to your problem) in your message, to enable people to
    understand your problem and offer solutions. This may include
    configurations (software & hardware), initialization strings,
    possible TSR programs, etc.

    3. When quoting a message, only quote what is pertinent to your
    response, not the whole message (if possible).

    4. Tearlines should be left as the mail proccessor makes/inserts them
    (35 characters max. none if PID is in message).

    5. When discussing your "views" on any program, be descriptive, explain
    what features you like or dislike (and why?), what works or doesn't
    and limit them to programs which work with (in one way or another)
    RemoteAccess, etc. Getting involved with "Mine is better than yours"
    type of conversations, is not productive and has no place here, or
    in any other conference. Try to maintain an objective view so that
    your post does not come across as software or author bashing.

    6. When posting an ad for a new product, make it "descriptive", but try
    to be reasonable.

    Thank You

    |Andrew Leary, 1:320/119, andrew.leary@tvcconnect.net
    Mark Lewis, 1:3634/12

    Conference Moderators



    * Origin: (1:3634/12)
  • From Moderator@1:3634/12 to All on Wed Oct 1 00:00:16 2014

    |RemoteAccess Utils Echo Guidelines: rev. 29 May 14 |Posting Frequency: 1st of the month.
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    These are "not" rules per se', but "ideals" which we hope you will
    all agree with and shoot for, within this echo.

    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    1. When anouncing a file is available, give the pertinent data
    concerning the file:

    RA_262SW.ZIP ------------> FileName
    RA ----------------------> MagicName (if available)
    848,297 -----------------> Filesize
    56K V.90 ----------------> Max baudrate
    1:3634/12 ---------------> Address 1...
    2547:1000/12 ------------> Address 2... (and so on...)
    1-919-774-5930 ----------> System Telephone Number
    Via SDS -----------------> Yes/No (was it released into the SDS?)
    Sanford, NC, USA --------> City, State, Country (where you are)
    Anyone May FREQ 24/7 ----> Or do you allow unlisted nodes to freq?

    2. Before reporting what you believe to be a bug, check and double
    check everything, then make your report (often you will find it is
    operator error and not program error). Include enough information
    (pertinent to your problem) in your message, to enable people to
    understand your problem and offer solutions. This may include
    configurations (software & hardware), initialization strings,
    possible TSR programs, etc.

    3. When quoting a message, only quote what is pertinent to your
    response, not the whole message (if possible).

    4. Tearlines should be left as the mail proccessor makes/inserts them
    (35 characters max. none if PID is in message).

    5. When discussing your "views" on any program, be descriptive, explain
    what features you like or dislike (and why?), what works or doesn't
    and limit them to programs which work with (in one way or another)
    RemoteAccess, etc. Getting involved with "Mine is better than yours"
    type of conversations, is not productive and has no place here, or
    in any other conference. Try to maintain an objective view so that
    your post does not come across as software or author bashing.

    6. When posting an ad for a new product, make it "descriptive", but try
    to be reasonable.

    Thank You

    |Andrew Leary, 1:320/119, andrew.leary@tvcconnect.net
    Mark Lewis, 1:3634/12

    Conference Moderators



    * Origin: (1:3634/12)
  • From Moderator@1:3634/12 to All on Sat Nov 1 00:00:18 2014

    |RemoteAccess Utils Echo Guidelines: rev. 29 May 14 |Posting Frequency: 1st of the month.
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    These are "not" rules per se', but "ideals" which we hope you will
    all agree with and shoot for, within this echo.

    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    1. When anouncing a file is available, give the pertinent data
    concerning the file:

    RA_262SW.ZIP ------------> FileName
    RA ----------------------> MagicName (if available)
    848,297 -----------------> Filesize
    56K V.90 ----------------> Max baudrate
    1:3634/12 ---------------> Address 1...
    2547:1000/12 ------------> Address 2... (and so on...)
    1-919-774-5930 ----------> System Telephone Number
    Via SDS -----------------> Yes/No (was it released into the SDS?)
    Sanford, NC, USA --------> City, State, Country (where you are)
    Anyone May FREQ 24/7 ----> Or do you allow unlisted nodes to freq?

    2. Before reporting what you believe to be a bug, check and double
    check everything, then make your report (often you will find it is
    operator error and not program error). Include enough information
    (pertinent to your problem) in your message, to enable people to
    understand your problem and offer solutions. This may include
    configurations (software & hardware), initialization strings,
    possible TSR programs, etc.

    3. When quoting a message, only quote what is pertinent to your
    response, not the whole message (if possible).

    4. Tearlines should be left as the mail proccessor makes/inserts them
    (35 characters max. none if PID is in message).

    5. When discussing your "views" on any program, be descriptive, explain
    what features you like or dislike (and why?), what works or doesn't
    and limit them to programs which work with (in one way or another)
    RemoteAccess, etc. Getting involved with "Mine is better than yours"
    type of conversations, is not productive and has no place here, or
    in any other conference. Try to maintain an objective view so that
    your post does not come across as software or author bashing.

    6. When posting an ad for a new product, make it "descriptive", but try
    to be reasonable.

    Thank You

    |Andrew Leary, 1:320/119, andrew.leary@tvcconnect.net
    Mark Lewis, 1:3634/12

    Conference Moderators



    * Origin: (1:3634/12)
  • From Moderator@1:3634/12 to All on Mon Dec 1 00:00:14 2014

    |RemoteAccess Utils Echo Guidelines: rev. 29 May 14 |Posting Frequency: 1st of the month.
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    These are "not" rules per se', but "ideals" which we hope you will
    all agree with and shoot for, within this echo.

    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    1. When anouncing a file is available, give the pertinent data
    concerning the file:

    RA_262SW.ZIP ------------> FileName
    RA ----------------------> MagicName (if available)
    848,297 -----------------> Filesize
    56K V.90 ----------------> Max baudrate
    1:3634/12 ---------------> Address 1...
    2547:1000/12 ------------> Address 2... (and so on...)
    1-919-774-5930 ----------> System Telephone Number
    Via SDS -----------------> Yes/No (was it released into the SDS?)
    Sanford, NC, USA --------> City, State, Country (where you are)
    Anyone May FREQ 24/7 ----> Or do you allow unlisted nodes to freq?

    2. Before reporting what you believe to be a bug, check and double
    check everything, then make your report (often you will find it is
    operator error and not program error). Include enough information
    (pertinent to your problem) in your message, to enable people to
    understand your problem and offer solutions. This may include
    configurations (software & hardware), initialization strings,
    possible TSR programs, etc.

    3. When quoting a message, only quote what is pertinent to your
    response, not the whole message (if possible).

    4. Tearlines should be left as the mail proccessor makes/inserts them
    (35 characters max. none if PID is in message).

    5. When discussing your "views" on any program, be descriptive, explain
    what features you like or dislike (and why?), what works or doesn't
    and limit them to programs which work with (in one way or another)
    RemoteAccess, etc. Getting involved with "Mine is better than yours"
    type of conversations, is not productive and has no place here, or
    in any other conference. Try to maintain an objective view so that
    your post does not come across as software or author bashing.

    6. When posting an ad for a new product, make it "descriptive", but try
    to be reasonable.

    Thank You

    |Andrew Leary, 1:320/119, andrew.leary@tvcconnect.net
    Mark Lewis, 1:3634/12

    Conference Moderators



    * Origin: (1:3634/12)
  • From Moderator@1:3634/12 to All on Thu Jan 1 00:00:18 2015

    |RemoteAccess Utils Echo Guidelines: rev. 29 May 14 |Posting Frequency: 1st of the month.
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    These are "not" rules per se', but "ideals" which we hope you will
    all agree with and shoot for, within this echo.

    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    1. When anouncing a file is available, give the pertinent data
    concerning the file:

    RA_262SW.ZIP ------------> FileName
    RA ----------------------> MagicName (if available)
    848,297 -----------------> Filesize
    56K V.90 ----------------> Max baudrate
    1:3634/12 ---------------> Address 1...
    2547:1000/12 ------------> Address 2... (and so on...)
    1-919-774-5930 ----------> System Telephone Number
    Via SDS -----------------> Yes/No (was it released into the SDS?)
    Sanford, NC, USA --------> City, State, Country (where you are)
    Anyone May FREQ 24/7 ----> Or do you allow unlisted nodes to freq?

    2. Before reporting what you believe to be a bug, check and double
    check everything, then make your report (often you will find it is
    operator error and not program error). Include enough information
    (pertinent to your problem) in your message, to enable people to
    understand your problem and offer solutions. This may include
    configurations (software & hardware), initialization strings,
    possible TSR programs, etc.

    3. When quoting a message, only quote what is pertinent to your
    response, not the whole message (if possible).

    4. Tearlines should be left as the mail proccessor makes/inserts them
    (35 characters max. none if PID is in message).

    5. When discussing your "views" on any program, be descriptive, explain
    what features you like or dislike (and why?), what works or doesn't
    and limit them to programs which work with (in one way or another)
    RemoteAccess, etc. Getting involved with "Mine is better than yours"
    type of conversations, is not productive and has no place here, or
    in any other conference. Try to maintain an objective view so that
    your post does not come across as software or author bashing.

    6. When posting an ad for a new product, make it "descriptive", but try
    to be reasonable.

    Thank You

    |Andrew Leary, 1:320/119, andrew.leary@tvcconnect.net
    Mark Lewis, 1:3634/12

    Conference Moderators



    * Origin: (1:3634/12)
  • From Moderator@1:3634/12 to All on Sun Feb 1 00:00:10 2015

    |RemoteAccess Utils Echo Guidelines: rev. 29 May 14 |Posting Frequency: 1st of the month.
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    These are "not" rules per se', but "ideals" which we hope you will
    all agree with and shoot for, within this echo.

    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    1. When anouncing a file is available, give the pertinent data
    concerning the file:

    RA_262SW.ZIP ------------> FileName
    RA ----------------------> MagicName (if available)
    848,297 -----------------> Filesize
    56K V.90 ----------------> Max baudrate
    1:3634/12 ---------------> Address 1...
    2547:1000/12 ------------> Address 2... (and so on...)
    1-919-774-5930 ----------> System Telephone Number
    Via SDS -----------------> Yes/No (was it released into the SDS?)
    Sanford, NC, USA --------> City, State, Country (where you are)
    Anyone May FREQ 24/7 ----> Or do you allow unlisted nodes to freq?

    2. Before reporting what you believe to be a bug, check and double
    check everything, then make your report (often you will find it is
    operator error and not program error). Include enough information
    (pertinent to your problem) in your message, to enable people to
    understand your problem and offer solutions. This may include
    configurations (software & hardware), initialization strings,
    possible TSR programs, etc.

    3. When quoting a message, only quote what is pertinent to your
    response, not the whole message (if possible).

    4. Tearlines should be left as the mail proccessor makes/inserts them
    (35 characters max. none if PID is in message).

    5. When discussing your "views" on any program, be descriptive, explain
    what features you like or dislike (and why?), what works or doesn't
    and limit them to programs which work with (in one way or another)
    RemoteAccess, etc. Getting involved with "Mine is better than yours"
    type of conversations, is not productive and has no place here, or
    in any other conference. Try to maintain an objective view so that
    your post does not come across as software or author bashing.

    6. When posting an ad for a new product, make it "descriptive", but try
    to be reasonable.

    Thank You

    |Andrew Leary, 1:320/119, andrew.leary@tvcconnect.net
    Mark Lewis, 1:3634/12

    Conference Moderators



    * Origin: (1:3634/12)
  • From Moderator@1:3634/12 to All on Sun Mar 1 00:00:10 2015

    |RemoteAccess Utils Echo Guidelines: rev. 29 May 14 |Posting Frequency: 1st of the month.
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    These are "not" rules per se', but "ideals" which we hope you will
    all agree with and shoot for, within this echo.

    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    1. When anouncing a file is available, give the pertinent data
    concerning the file:

    RA_262SW.ZIP ------------> FileName
    RA ----------------------> MagicName (if available)
    848,297 -----------------> Filesize
    56K V.90 ----------------> Max baudrate
    1:3634/12 ---------------> Address 1...
    2547:1000/12 ------------> Address 2... (and so on...)
    1-919-774-5930 ----------> System Telephone Number
    Via SDS -----------------> Yes/No (was it released into the SDS?)
    Sanford, NC, USA --------> City, State, Country (where you are)
    Anyone May FREQ 24/7 ----> Or do you allow unlisted nodes to freq?

    2. Before reporting what you believe to be a bug, check and double
    check everything, then make your report (often you will find it is
    operator error and not program error). Include enough information
    (pertinent to your problem) in your message, to enable people to
    understand your problem and offer solutions. This may include
    configurations (software & hardware), initialization strings,
    possible TSR programs, etc.

    3. When quoting a message, only quote what is pertinent to your
    response, not the whole message (if possible).

    4. Tearlines should be left as the mail proccessor makes/inserts them
    (35 characters max. none if PID is in message).

    5. When discussing your "views" on any program, be descriptive, explain
    what features you like or dislike (and why?), what works or doesn't
    and limit them to programs which work with (in one way or another)
    RemoteAccess, etc. Getting involved with "Mine is better than yours"
    type of conversations, is not productive and has no place here, or
    in any other conference. Try to maintain an objective view so that
    your post does not come across as software or author bashing.

    6. When posting an ad for a new product, make it "descriptive", but try
    to be reasonable.

    Thank You

    |Andrew Leary, 1:320/119, andrew.leary@tvcconnect.net
    Mark Lewis, 1:3634/12

    Conference Moderators



    * Origin: (1:3634/12)
  • From Moderator@1:3634/12 to All on Wed Apr 1 00:00:18 2015

    |RemoteAccess Utils Echo Guidelines: rev. 29 May 14 |Posting Frequency: 1st of the month.
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    These are "not" rules per se', but "ideals" which we hope you will
    all agree with and shoot for, within this echo.

    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    1. When anouncing a file is available, give the pertinent data
    concerning the file:

    RA_262SW.ZIP ------------> FileName
    RA ----------------------> MagicName (if available)
    848,297 -----------------> Filesize
    56K V.90 ----------------> Max baudrate
    1:3634/12 ---------------> Address 1...
    2547:1000/12 ------------> Address 2... (and so on...)
    1-919-774-5930 ----------> System Telephone Number
    Via SDS -----------------> Yes/No (was it released into the SDS?)
    Sanford, NC, USA --------> City, State, Country (where you are)
    Anyone May FREQ 24/7 ----> Or do you allow unlisted nodes to freq?

    2. Before reporting what you believe to be a bug, check and double
    check everything, then make your report (often you will find it is
    operator error and not program error). Include enough information
    (pertinent to your problem) in your message, to enable people to
    understand your problem and offer solutions. This may include
    configurations (software & hardware), initialization strings,
    possible TSR programs, etc.

    3. When quoting a message, only quote what is pertinent to your
    response, not the whole message (if possible).

    4. Tearlines should be left as the mail proccessor makes/inserts them
    (35 characters max. none if PID is in message).

    5. When discussing your "views" on any program, be descriptive, explain
    what features you like or dislike (and why?), what works or doesn't
    and limit them to programs which work with (in one way or another)
    RemoteAccess, etc. Getting involved with "Mine is better than yours"
    type of conversations, is not productive and has no place here, or
    in any other conference. Try to maintain an objective view so that
    your post does not come across as software or author bashing.

    6. When posting an ad for a new product, make it "descriptive", but try
    to be reasonable.

    Thank You

    |Andrew Leary, 1:320/119, andrew.leary@tvcconnect.net
    Mark Lewis, 1:3634/12

    Conference Moderators



    * Origin: (1:3634/12)
  • From Moderator@1:3634/12 to All on Wed Jul 1 00:00:20 2015

    |RemoteAccess Utils Echo Guidelines: rev. 29 May 14 |Posting Frequency: 1st of the month.
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    These are "not" rules per se', but "ideals" which we hope you will
    all agree with and shoot for, within this echo.

    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    1. When anouncing a file is available, give the pertinent data
    concerning the file:

    RA_262SW.ZIP ------------> FileName
    RA ----------------------> MagicName (if available)
    848,297 -----------------> Filesize
    56K V.90 ----------------> Max baudrate
    1:3634/12 ---------------> Address 1...
    2547:1000/12 ------------> Address 2... (and so on...)
    1-919-774-5930 ----------> System Telephone Number
    Via SDS -----------------> Yes/No (was it released into the SDS?)
    Sanford, NC, USA --------> City, State, Country (where you are)
    Anyone May FREQ 24/7 ----> Or do you allow unlisted nodes to freq?

    2. Before reporting what you believe to be a bug, check and double
    check everything, then make your report (often you will find it is
    operator error and not program error). Include enough information
    (pertinent to your problem) in your message, to enable people to
    understand your problem and offer solutions. This may include
    configurations (software & hardware), initialization strings,
    possible TSR programs, etc.

    3. When quoting a message, only quote what is pertinent to your
    response, not the whole message (if possible).

    4. Tearlines should be left as the mail proccessor makes/inserts them
    (35 characters max. none if PID is in message).

    5. When discussing your "views" on any program, be descriptive, explain
    what features you like or dislike (and why?), what works or doesn't
    and limit them to programs which work with (in one way or another)
    RemoteAccess, etc. Getting involved with "Mine is better than yours"
    type of conversations, is not productive and has no place here, or
    in any other conference. Try to maintain an objective view so that
    your post does not come across as software or author bashing.

    6. When posting an ad for a new product, make it "descriptive", but try
    to be reasonable.

    Thank You

    |Andrew Leary, 1:320/119, andrew.leary@tvcconnect.net
    Mark Lewis, 1:3634/12

    Conference Moderators



    * Origin: (1:3634/12)
  • From Moderator@1:3634/12 to All on Sat Aug 1 00:00:10 2015

    |RemoteAccess Utils Echo Guidelines: rev. 29 May 14 |Posting Frequency: 1st of the month.
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    These are "not" rules per se', but "ideals" which we hope you will
    all agree with and shoot for, within this echo.

    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    1. When anouncing a file is available, give the pertinent data
    concerning the file:

    RA_262SW.ZIP ------------> FileName
    RA ----------------------> MagicName (if available)
    848,297 -----------------> Filesize
    56K V.90 ----------------> Max baudrate
    1:3634/12 ---------------> Address 1...
    2547:1000/12 ------------> Address 2... (and so on...)
    1-919-774-5930 ----------> System Telephone Number
    Via SDS -----------------> Yes/No (was it released into the SDS?)
    Sanford, NC, USA --------> City, State, Country (where you are)
    Anyone May FREQ 24/7 ----> Or do you allow unlisted nodes to freq?

    2. Before reporting what you believe to be a bug, check and double
    check everything, then make your report (often you will find it is
    operator error and not program error). Include enough information
    (pertinent to your problem) in your message, to enable people to
    understand your problem and offer solutions. This may include
    configurations (software & hardware), initialization strings,
    possible TSR programs, etc.

    3. When quoting a message, only quote what is pertinent to your
    response, not the whole message (if possible).

    4. Tearlines should be left as the mail proccessor makes/inserts them
    (35 characters max. none if PID is in message).

    5. When discussing your "views" on any program, be descriptive, explain
    what features you like or dislike (and why?), what works or doesn't
    and limit them to programs which work with (in one way or another)
    RemoteAccess, etc. Getting involved with "Mine is better than yours"
    type of conversations, is not productive and has no place here, or
    in any other conference. Try to maintain an objective view so that
    your post does not come across as software or author bashing.

    6. When posting an ad for a new product, make it "descriptive", but try
    to be reasonable.

    Thank You

    |Andrew Leary, 1:320/119, andrew.leary@tvcconnect.net
    Mark Lewis, 1:3634/12

    Conference Moderators



    * Origin: (1:3634/12)
  • From Moderator@1:3634/12 to All on Tue Sep 1 00:00:18 2015

    |RemoteAccess Utils Echo Guidelines: rev. 29 May 14 |Posting Frequency: 1st of the month.
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    These are "not" rules per se', but "ideals" which we hope you will
    all agree with and shoot for, within this echo.

    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    1. When anouncing a file is available, give the pertinent data
    concerning the file:

    RA_262SW.ZIP ------------> FileName
    RA ----------------------> MagicName (if available)
    848,297 -----------------> Filesize
    56K V.90 ----------------> Max baudrate
    1:3634/12 ---------------> Address 1...
    2547:1000/12 ------------> Address 2... (and so on...)
    1-919-774-5930 ----------> System Telephone Number
    Via SDS -----------------> Yes/No (was it released into the SDS?)
    Sanford, NC, USA --------> City, State, Country (where you are)
    Anyone May FREQ 24/7 ----> Or do you allow unlisted nodes to freq?

    2. Before reporting what you believe to be a bug, check and double
    check everything, then make your report (often you will find it is
    operator error and not program error). Include enough information
    (pertinent to your problem) in your message, to enable people to
    understand your problem and offer solutions. This may include
    configurations (software & hardware), initialization strings,
    possible TSR programs, etc.

    3. When quoting a message, only quote what is pertinent to your
    response, not the whole message (if possible).

    4. Tearlines should be left as the mail proccessor makes/inserts them
    (35 characters max. none if PID is in message).

    5. When discussing your "views" on any program, be descriptive, explain
    what features you like or dislike (and why?), what works or doesn't
    and limit them to programs which work with (in one way or another)
    RemoteAccess, etc. Getting involved with "Mine is better than yours"
    type of conversations, is not productive and has no place here, or
    in any other conference. Try to maintain an objective view so that
    your post does not come across as software or author bashing.

    6. When posting an ad for a new product, make it "descriptive", but try
    to be reasonable.

    Thank You

    |Andrew Leary, 1:320/119, andrew.leary@tvcconnect.net
    Mark Lewis, 1:3634/12

    Conference Moderators



    * Origin: (1:3634/12)
  • From Moderator@1:3634/12 to All on Thu Oct 1 00:00:18 2015

    |RemoteAccess Utils Echo Guidelines: rev. 29 May 14 |Posting Frequency: 1st of the month.
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    These are "not" rules per se', but "ideals" which we hope you will
    all agree with and shoot for, within this echo.

    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    1. When anouncing a file is available, give the pertinent data
    concerning the file:

    RA_262SW.ZIP ------------> FileName
    RA ----------------------> MagicName (if available)
    848,297 -----------------> Filesize
    56K V.90 ----------------> Max baudrate
    1:3634/12 ---------------> Address 1...
    2547:1000/12 ------------> Address 2... (and so on...)
    1-919-774-5930 ----------> System Telephone Number
    Via SDS -----------------> Yes/No (was it released into the SDS?)
    Sanford, NC, USA --------> City, State, Country (where you are)
    Anyone May FREQ 24/7 ----> Or do you allow unlisted nodes to freq?

    2. Before reporting what you believe to be a bug, check and double
    check everything, then make your report (often you will find it is
    operator error and not program error). Include enough information
    (pertinent to your problem) in your message, to enable people to
    understand your problem and offer solutions. This may include
    configurations (software & hardware), initialization strings,
    possible TSR programs, etc.

    3. When quoting a message, only quote what is pertinent to your
    response, not the whole message (if possible).

    4. Tearlines should be left as the mail proccessor makes/inserts them
    (35 characters max. none if PID is in message).

    5. When discussing your "views" on any program, be descriptive, explain
    what features you like or dislike (and why?), what works or doesn't
    and limit them to programs which work with (in one way or another)
    RemoteAccess, etc. Getting involved with "Mine is better than yours"
    type of conversations, is not productive and has no place here, or
    in any other conference. Try to maintain an objective view so that
    your post does not come across as software or author bashing.

    6. When posting an ad for a new product, make it "descriptive", but try
    to be reasonable.

    Thank You

    |Andrew Leary, 1:320/119, andrew.leary@tvcconnect.net
    Mark Lewis, 1:3634/12

    Conference Moderators



    * Origin: (1:3634/12)
  • From Moderator@1:3634/12 to All on Sun Nov 1 00:00:18 2015

    |RemoteAccess Utils Echo Guidelines: rev. 29 May 14 |Posting Frequency: 1st of the month.
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    These are "not" rules per se', but "ideals" which we hope you will
    all agree with and shoot for, within this echo.

    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    1. When anouncing a file is available, give the pertinent data
    concerning the file:

    RA_262SW.ZIP ------------> FileName
    RA ----------------------> MagicName (if available)
    848,297 -----------------> Filesize
    56K V.90 ----------------> Max baudrate
    1:3634/12 ---------------> Address 1...
    2547:1000/12 ------------> Address 2... (and so on...)
    1-919-774-5930 ----------> System Telephone Number
    Via SDS -----------------> Yes/No (was it released into the SDS?)
    Sanford, NC, USA --------> City, State, Country (where you are)
    Anyone May FREQ 24/7 ----> Or do you allow unlisted nodes to freq?

    2. Before reporting what you believe to be a bug, check and double
    check everything, then make your report (often you will find it is
    operator error and not program error). Include enough information
    (pertinent to your problem) in your message, to enable people to
    understand your problem and offer solutions. This may include
    configurations (software & hardware), initialization strings,
    possible TSR programs, etc.

    3. When quoting a message, only quote what is pertinent to your
    response, not the whole message (if possible).

    4. Tearlines should be left as the mail proccessor makes/inserts them
    (35 characters max. none if PID is in message).

    5. When discussing your "views" on any program, be descriptive, explain
    what features you like or dislike (and why?), what works or doesn't
    and limit them to programs which work with (in one way or another)
    RemoteAccess, etc. Getting involved with "Mine is better than yours"
    type of conversations, is not productive and has no place here, or
    in any other conference. Try to maintain an objective view so that
    your post does not come across as software or author bashing.

    6. When posting an ad for a new product, make it "descriptive", but try
    to be reasonable.

    Thank You

    |Andrew Leary, 1:320/119, andrew.leary@tvcconnect.net
    Mark Lewis, 1:3634/12

    Conference Moderators



    * Origin: (1:3634/12)
  • From Moderator@1:3634/12 to All on Tue Dec 1 00:02:52 2015

    |RemoteAccess Utils Echo Guidelines: rev. 29 May 14 |Posting Frequency: 1st of the month.
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    These are "not" rules per se', but "ideals" which we hope you will
    all agree with and shoot for, within this echo.

    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    1. When anouncing a file is available, give the pertinent data
    concerning the file:

    RA_262SW.ZIP ------------> FileName
    RA ----------------------> MagicName (if available)
    848,297 -----------------> Filesize
    56K V.90 ----------------> Max baudrate
    1:3634/12 ---------------> Address 1...
    2547:1000/12 ------------> Address 2... (and so on...)
    1-919-774-5930 ----------> System Telephone Number
    Via SDS -----------------> Yes/No (was it released into the SDS?)
    Sanford, NC, USA --------> City, State, Country (where you are)
    Anyone May FREQ 24/7 ----> Or do you allow unlisted nodes to freq?

    2. Before reporting what you believe to be a bug, check and double
    check everything, then make your report (often you will find it is
    operator error and not program error). Include enough information
    (pertinent to your problem) in your message, to enable people to
    understand your problem and offer solutions. This may include
    configurations (software & hardware), initialization strings,
    possible TSR programs, etc.

    3. When quoting a message, only quote what is pertinent to your
    response, not the whole message (if possible).

    4. Tearlines should be left as the mail proccessor makes/inserts them
    (35 characters max. none if PID is in message).

    5. When discussing your "views" on any program, be descriptive, explain
    what features you like or dislike (and why?), what works or doesn't
    and limit them to programs which work with (in one way or another)
    RemoteAccess, etc. Getting involved with "Mine is better than yours"
    type of conversations, is not productive and has no place here, or
    in any other conference. Try to maintain an objective view so that
    your post does not come across as software or author bashing.

    6. When posting an ad for a new product, make it "descriptive", but try
    to be reasonable.

    Thank You

    |Andrew Leary, 1:320/119, andrew.leary@tvcconnect.net
    Mark Lewis, 1:3634/12

    Conference Moderators



    * Origin: (1:3634/12)
  • From Moderator@1:3634/12 to All on Fri Jan 1 00:00:18 2016

    |RemoteAccess Utils Echo Guidelines: rev. 29 May 14 |Posting Frequency: 1st of the month.
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    These are "not" rules per se', but "ideals" which we hope you will
    all agree with and shoot for, within this echo.

    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    1. When anouncing a file is available, give the pertinent data
    concerning the file:

    RA_262SW.ZIP ------------> FileName
    RA ----------------------> MagicName (if available)
    848,297 -----------------> Filesize
    56K V.90 ----------------> Max baudrate
    1:3634/12 ---------------> Address 1...
    2547:1000/12 ------------> Address 2... (and so on...)
    1-919-774-5930 ----------> System Telephone Number
    Via SDS -----------------> Yes/No (was it released into the SDS?)
    Sanford, NC, USA --------> City, State, Country (where you are)
    Anyone May FREQ 24/7 ----> Or do you allow unlisted nodes to freq?

    2. Before reporting what you believe to be a bug, check and double
    check everything, then make your report (often you will find it is
    operator error and not program error). Include enough information
    (pertinent to your problem) in your message, to enable people to
    understand your problem and offer solutions. This may include
    configurations (software & hardware), initialization strings,
    possible TSR programs, etc.

    3. When quoting a message, only quote what is pertinent to your
    response, not the whole message (if possible).

    4. Tearlines should be left as the mail proccessor makes/inserts them
    (35 characters max. none if PID is in message).

    5. When discussing your "views" on any program, be descriptive, explain
    what features you like or dislike (and why?), what works or doesn't
    and limit them to programs which work with (in one way or another)
    RemoteAccess, etc. Getting involved with "Mine is better than yours"
    type of conversations, is not productive and has no place here, or
    in any other conference. Try to maintain an objective view so that
    your post does not come across as software or author bashing.

    6. When posting an ad for a new product, make it "descriptive", but try
    to be reasonable.

    Thank You

    |Andrew Leary, 1:320/119, andrew.leary@tvcconnect.net
    Mark Lewis, 1:3634/12

    Conference Moderators



    * Origin: (1:3634/12)
  • From Moderator@1:3634/12 to All on Mon Feb 1 00:00:22 2016

    |RemoteAccess Utils Echo Guidelines: rev. 29 May 14 |Posting Frequency: 1st of the month.
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    These are "not" rules per se', but "ideals" which we hope you will
    all agree with and shoot for, within this echo.

    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    1. When anouncing a file is available, give the pertinent data
    concerning the file:

    RA_262SW.ZIP ------------> FileName
    RA ----------------------> MagicName (if available)
    848,297 -----------------> Filesize
    56K V.90 ----------------> Max baudrate
    1:3634/12 ---------------> Address 1...
    2547:1000/12 ------------> Address 2... (and so on...)
    1-919-774-5930 ----------> System Telephone Number
    Via SDS -----------------> Yes/No (was it released into the SDS?)
    Sanford, NC, USA --------> City, State, Country (where you are)
    Anyone May FREQ 24/7 ----> Or do you allow unlisted nodes to freq?

    2. Before reporting what you believe to be a bug, check and double
    check everything, then make your report (often you will find it is
    operator error and not program error). Include enough information
    (pertinent to your problem) in your message, to enable people to
    understand your problem and offer solutions. This may include
    configurations (software & hardware), initialization strings,
    possible TSR programs, etc.

    3. When quoting a message, only quote what is pertinent to your
    response, not the whole message (if possible).

    4. Tearlines should be left as the mail proccessor makes/inserts them
    (35 characters max. none if PID is in message).

    5. When discussing your "views" on any program, be descriptive, explain
    what features you like or dislike (and why?), what works or doesn't
    and limit them to programs which work with (in one way or another)
    RemoteAccess, etc. Getting involved with "Mine is better than yours"
    type of conversations, is not productive and has no place here, or
    in any other conference. Try to maintain an objective view so that
    your post does not come across as software or author bashing.

    6. When posting an ad for a new product, make it "descriptive", but try
    to be reasonable.

    Thank You

    |Andrew Leary, 1:320/119, andrew.leary@tvcconnect.net
    Mark Lewis, 1:3634/12

    Conference Moderators



    * Origin: (1:3634/12)
  • From Moderator@1:3634/12 to All on Tue Mar 1 00:01:10 2016

    |RemoteAccess Utils Echo Guidelines: rev. 29 May 14 |Posting Frequency: 1st of the month.
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    These are "not" rules per se', but "ideals" which we hope you will
    all agree with and shoot for, within this echo.

    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    1. When anouncing a file is available, give the pertinent data
    concerning the file:

    RA_262SW.ZIP ------------> FileName
    RA ----------------------> MagicName (if available)
    848,297 -----------------> Filesize
    56K V.90 ----------------> Max baudrate
    1:3634/12 ---------------> Address 1...
    2547:1000/12 ------------> Address 2... (and so on...)
    1-919-774-5930 ----------> System Telephone Number
    Via SDS -----------------> Yes/No (was it released into the SDS?)
    Sanford, NC, USA --------> City, State, Country (where you are)
    Anyone May FREQ 24/7 ----> Or do you allow unlisted nodes to freq?

    2. Before reporting what you believe to be a bug, check and double
    check everything, then make your report (often you will find it is
    operator error and not program error). Include enough information
    (pertinent to your problem) in your message, to enable people to
    understand your problem and offer solutions. This may include
    configurations (software & hardware), initialization strings,
    possible TSR programs, etc.

    3. When quoting a message, only quote what is pertinent to your
    response, not the whole message (if possible).

    4. Tearlines should be left as the mail proccessor makes/inserts them
    (35 characters max. none if PID is in message).

    5. When discussing your "views" on any program, be descriptive, explain
    what features you like or dislike (and why?), what works or doesn't
    and limit them to programs which work with (in one way or another)
    RemoteAccess, etc. Getting involved with "Mine is better than yours"
    type of conversations, is not productive and has no place here, or
    in any other conference. Try to maintain an objective view so that
    your post does not come across as software or author bashing.

    6. When posting an ad for a new product, make it "descriptive", but try
    to be reasonable.

    Thank You

    |Andrew Leary, 1:320/119, andrew.leary@tvcconnect.net
    Mark Lewis, 1:3634/12

    Conference Moderators



    * Origin: (1:3634/12)
  • From Moderator@1:3634/12 to All on Fri Apr 1 00:00:18 2016

    |RemoteAccess Utils Echo Guidelines: rev. 29 May 14 |Posting Frequency: 1st of the month.
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    These are "not" rules per se', but "ideals" which we hope you will
    all agree with and shoot for, within this echo.

    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    1. When anouncing a file is available, give the pertinent data
    concerning the file:

    RA_262SW.ZIP ------------> FileName
    RA ----------------------> MagicName (if available)
    848,297 -----------------> Filesize
    56K V.90 ----------------> Max baudrate
    1:3634/12 ---------------> Address 1...
    2547:1000/12 ------------> Address 2... (and so on...)
    1-919-774-5930 ----------> System Telephone Number
    Via SDS -----------------> Yes/No (was it released into the SDS?)
    Sanford, NC, USA --------> City, State, Country (where you are)
    Anyone May FREQ 24/7 ----> Or do you allow unlisted nodes to freq?

    2. Before reporting what you believe to be a bug, check and double
    check everything, then make your report (often you will find it is
    operator error and not program error). Include enough information
    (pertinent to your problem) in your message, to enable people to
    understand your problem and offer solutions. This may include
    configurations (software & hardware), initialization strings,
    possible TSR programs, etc.

    3. When quoting a message, only quote what is pertinent to your
    response, not the whole message (if possible).

    4. Tearlines should be left as the mail proccessor makes/inserts them
    (35 characters max. none if PID is in message).

    5. When discussing your "views" on any program, be descriptive, explain
    what features you like or dislike (and why?), what works or doesn't
    and limit them to programs which work with (in one way or another)
    RemoteAccess, etc. Getting involved with "Mine is better than yours"
    type of conversations, is not productive and has no place here, or
    in any other conference. Try to maintain an objective view so that
    your post does not come across as software or author bashing.

    6. When posting an ad for a new product, make it "descriptive", but try
    to be reasonable.

    Thank You

    |Andrew Leary, 1:320/119, andrew.leary@tvcconnect.net
    Mark Lewis, 1:3634/12

    Conference Moderators



    * Origin: (1:3634/12)
  • From Moderator@1:3634/12 to All on Sun May 1 00:00:18 2016

    |RemoteAccess Utils Echo Guidelines: rev. 29 May 14 |Posting Frequency: 1st of the month.
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    These are "not" rules per se', but "ideals" which we hope you will
    all agree with and shoot for, within this echo.

    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    1. When anouncing a file is available, give the pertinent data
    concerning the file:

    RA_262SW.ZIP ------------> FileName
    RA ----------------------> MagicName (if available)
    848,297 -----------------> Filesize
    56K V.90 ----------------> Max baudrate
    1:3634/12 ---------------> Address 1...
    2547:1000/12 ------------> Address 2... (and so on...)
    1-919-774-5930 ----------> System Telephone Number
    Via SDS -----------------> Yes/No (was it released into the SDS?)
    Sanford, NC, USA --------> City, State, Country (where you are)
    Anyone May FREQ 24/7 ----> Or do you allow unlisted nodes to freq?

    2. Before reporting what you believe to be a bug, check and double
    check everything, then make your report (often you will find it is
    operator error and not program error). Include enough information
    (pertinent to your problem) in your message, to enable people to
    understand your problem and offer solutions. This may include
    configurations (software & hardware), initialization strings,
    possible TSR programs, etc.

    3. When quoting a message, only quote what is pertinent to your
    response, not the whole message (if possible).

    4. Tearlines should be left as the mail proccessor makes/inserts them
    (35 characters max. none if PID is in message).

    5. When discussing your "views" on any program, be descriptive, explain
    what features you like or dislike (and why?), what works or doesn't
    and limit them to programs which work with (in one way or another)
    RemoteAccess, etc. Getting involved with "Mine is better than yours"
    type of conversations, is not productive and has no place here, or
    in any other conference. Try to maintain an objective view so that
    your post does not come across as software or author bashing.

    6. When posting an ad for a new product, make it "descriptive", but try
    to be reasonable.

    Thank You

    |Andrew Leary, 1:320/119, andrew.leary@tvcconnect.net
    Mark Lewis, 1:3634/12

    Conference Moderators



    * Origin: (1:3634/12)
  • From Moderator@1:3634/12 to All on Wed Jun 1 00:00:12 2016

    |RemoteAccess Utils Echo Guidelines: rev. 29 May 14 |Posting Frequency: 1st of the month.
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    These are "not" rules per se', but "ideals" which we hope you will
    all agree with and shoot for, within this echo.

    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    1. When anouncing a file is available, give the pertinent data
    concerning the file:

    RA_262SW.ZIP ------------> FileName
    RA ----------------------> MagicName (if available)
    848,297 -----------------> Filesize
    56K V.90 ----------------> Max baudrate
    1:3634/12 ---------------> Address 1...
    2547:1000/12 ------------> Address 2... (and so on...)
    1-919-774-5930 ----------> System Telephone Number
    Via SDS -----------------> Yes/No (was it released into the SDS?)
    Sanford, NC, USA --------> City, State, Country (where you are)
    Anyone May FREQ 24/7 ----> Or do you allow unlisted nodes to freq?

    2. Before reporting what you believe to be a bug, check and double
    check everything, then make your report (often you will find it is
    operator error and not program error). Include enough information
    (pertinent to your problem) in your message, to enable people to
    understand your problem and offer solutions. This may include
    configurations (software & hardware), initialization strings,
    possible TSR programs, etc.

    3. When quoting a message, only quote what is pertinent to your
    response, not the whole message (if possible).

    4. Tearlines should be left as the mail proccessor makes/inserts them
    (35 characters max. none if PID is in message).

    5. When discussing your "views" on any program, be descriptive, explain
    what features you like or dislike (and why?), what works or doesn't
    and limit them to programs which work with (in one way or another)
    RemoteAccess, etc. Getting involved with "Mine is better than yours"
    type of conversations, is not productive and has no place here, or
    in any other conference. Try to maintain an objective view so that
    your post does not come across as software or author bashing.

    6. When posting an ad for a new product, make it "descriptive", but try
    to be reasonable.

    Thank You

    |Andrew Leary, 1:320/119, andrew.leary@tvcconnect.net
    Mark Lewis, 1:3634/12

    Conference Moderators



    * Origin: (1:3634/12)
  • From Moderator@1:3634/12 to All on Fri Jul 1 00:00:26 2016

    |RemoteAccess Utils Echo Guidelines: rev. 29 May 14 |Posting Frequency: 1st of the month.
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    These are "not" rules per se', but "ideals" which we hope you will
    all agree with and shoot for, within this echo.

    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    1. When anouncing a file is available, give the pertinent data
    concerning the file:

    RA_262SW.ZIP ------------> FileName
    RA ----------------------> MagicName (if available)
    848,297 -----------------> Filesize
    56K V.90 ----------------> Max baudrate
    1:3634/12 ---------------> Address 1...
    2547:1000/12 ------------> Address 2... (and so on...)
    1-919-774-5930 ----------> System Telephone Number
    Via SDS -----------------> Yes/No (was it released into the SDS?)
    Sanford, NC, USA --------> City, State, Country (where you are)
    Anyone May FREQ 24/7 ----> Or do you allow unlisted nodes to freq?

    2. Before reporting what you believe to be a bug, check and double
    check everything, then make your report (often you will find it is
    operator error and not program error). Include enough information
    (pertinent to your problem) in your message, to enable people to
    understand your problem and offer solutions. This may include
    configurations (software & hardware), initialization strings,
    possible TSR programs, etc.

    3. When quoting a message, only quote what is pertinent to your
    response, not the whole message (if possible).

    4. Tearlines should be left as the mail proccessor makes/inserts them
    (35 characters max. none if PID is in message).

    5. When discussing your "views" on any program, be descriptive, explain
    what features you like or dislike (and why?), what works or doesn't
    and limit them to programs which work with (in one way or another)
    RemoteAccess, etc. Getting involved with "Mine is better than yours"
    type of conversations, is not productive and has no place here, or
    in any other conference. Try to maintain an objective view so that
    your post does not come across as software or author bashing.

    6. When posting an ad for a new product, make it "descriptive", but try
    to be reasonable.

    Thank You

    |Andrew Leary, 1:320/119, andrew.leary@tvcconnect.net
    Mark Lewis, 1:3634/12

    Conference Moderators



    * Origin: (1:3634/12)
  • From Moderator@1:3634/12 to All on Mon Aug 1 00:01:00 2016

    |RemoteAccess Utils Echo Guidelines: rev. 29 May 14 |Posting Frequency: 1st of the month.
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    These are "not" rules per se', but "ideals" which we hope you will
    all agree with and shoot for, within this echo.

    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    1. When anouncing a file is available, give the pertinent data
    concerning the file:

    RA_262SW.ZIP ------------> FileName
    RA ----------------------> MagicName (if available)
    848,297 -----------------> Filesize
    56K V.90 ----------------> Max baudrate
    1:3634/12 ---------------> Address 1...
    2547:1000/12 ------------> Address 2... (and so on...)
    1-919-774-5930 ----------> System Telephone Number
    Via SDS -----------------> Yes/No (was it released into the SDS?)
    Sanford, NC, USA --------> City, State, Country (where you are)
    Anyone May FREQ 24/7 ----> Or do you allow unlisted nodes to freq?

    2. Before reporting what you believe to be a bug, check and double
    check everything, then make your report (often you will find it is
    operator error and not program error). Include enough information
    (pertinent to your problem) in your message, to enable people to
    understand your problem and offer solutions. This may include
    configurations (software & hardware), initialization strings,
    possible TSR programs, etc.

    3. When quoting a message, only quote what is pertinent to your
    response, not the whole message (if possible).

    4. Tearlines should be left as the mail proccessor makes/inserts them
    (35 characters max. none if PID is in message).

    5. When discussing your "views" on any program, be descriptive, explain
    what features you like or dislike (and why?), what works or doesn't
    and limit them to programs which work with (in one way or another)
    RemoteAccess, etc. Getting involved with "Mine is better than yours"
    type of conversations, is not productive and has no place here, or
    in any other conference. Try to maintain an objective view so that
    your post does not come across as software or author bashing.

    6. When posting an ad for a new product, make it "descriptive", but try
    to be reasonable.

    Thank You

    |Andrew Leary, 1:320/119, andrew.leary@tvcconnect.net
    Mark Lewis, 1:3634/12

    Conference Moderators



    * Origin: (1:3634/12)
  • From Moderator@1:3634/12 to All on Thu Sep 1 00:00:10 2016
    |RemoteAccess Utils Echo Guidelines: rev. 29 May 14 |Posting Frequency: 1st of the month.
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    These are "not" rules per se', but "ideals" which we hope you will
    all agree with and shoot for, within this echo.

    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    1. When anouncing a file is available, give the pertinent data
    concerning the file:

    RA_262SW.ZIP ------------> FileName
    RA ----------------------> MagicName (if available)
    848,297 -----------------> Filesize
    56K V.90 ----------------> Max baudrate
    1:3634/12 ---------------> Address 1...
    2547:1000/12 ------------> Address 2... (and so on...)
    1-919-774-5930 ----------> System Telephone Number
    Via SDS -----------------> Yes/No (was it released into the SDS?)
    Sanford, NC, USA --------> City, State, Country (where you are)
    Anyone May FREQ 24/7 ----> Or do you allow unlisted nodes to freq?

    2. Before reporting what you believe to be a bug, check and double
    check everything, then make your report (often you will find it is
    operator error and not program error). Include enough information
    (pertinent to your problem) in your message, to enable people to
    understand your problem and offer solutions. This may include
    configurations (software & hardware), initialization strings,
    possible TSR programs, etc.

    3. When quoting a message, only quote what is pertinent to your
    response, not the whole message (if possible).

    4. Tearlines should be left as the mail proccessor makes/inserts them
    (35 characters max. none if PID is in message).

    5. When discussing your "views" on any program, be descriptive, explain
    what features you like or dislike (and why?), what works or doesn't
    and limit them to programs which work with (in one way or another)
    RemoteAccess, etc. Getting involved with "Mine is better than yours"
    type of conversations, is not productive and has no place here, or
    in any other conference. Try to maintain an objective view so that
    your post does not come across as software or author bashing.

    6. When posting an ad for a new product, make it "descriptive", but try
    to be reasonable.

    Thank You

    |Andrew Leary, 1:320/119, andrew.leary@tvcconnect.net
    Mark Lewis, 1:3634/12

    Conference Moderators



    * Origin: (1:3634/12)
  • From Moderator@1:3634/12 to All on Sat Oct 1 00:00:06 2016

    |RemoteAccess Utils Echo Guidelines: rev. 29 May 14 |Posting Frequency: 1st of the month.
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    These are "not" rules per se', but "ideals" which we hope you will
    all agree with and shoot for, within this echo.

    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    1. When anouncing a file is available, give the pertinent data
    concerning the file:

    RA_262SW.ZIP ------------> FileName
    RA ----------------------> MagicName (if available)
    848,297 -----------------> Filesize
    56K V.90 ----------------> Max baudrate
    1:3634/12 ---------------> Address 1...
    2547:1000/12 ------------> Address 2... (and so on...)
    1-919-774-5930 ----------> System Telephone Number
    Via SDS -----------------> Yes/No (was it released into the SDS?)
    Sanford, NC, USA --------> City, State, Country (where you are)
    Anyone May FREQ 24/7 ----> Or do you allow unlisted nodes to freq?

    2. Before reporting what you believe to be a bug, check and double
    check everything, then make your report (often you will find it is
    operator error and not program error). Include enough information
    (pertinent to your problem) in your message, to enable people to
    understand your problem and offer solutions. This may include
    configurations (software & hardware), initialization strings,
    possible TSR programs, etc.

    3. When quoting a message, only quote what is pertinent to your
    response, not the whole message (if possible).

    4. Tearlines should be left as the mail proccessor makes/inserts them
    (35 characters max. none if PID is in message).

    5. When discussing your "views" on any program, be descriptive, explain
    what features you like or dislike (and why?), what works or doesn't
    and limit them to programs which work with (in one way or another)
    RemoteAccess, etc. Getting involved with "Mine is better than yours"
    type of conversations, is not productive and has no place here, or
    in any other conference. Try to maintain an objective view so that
    your post does not come across as software or author bashing.

    6. When posting an ad for a new product, make it "descriptive", but try
    to be reasonable.

    Thank You

    |Andrew Leary, 1:320/119, andrew.leary@tvcconnect.net
    Mark Lewis, 1:3634/12

    Conference Moderators



    * Origin: (1:3634/12)
  • From Moderator@1:3634/12 to All on Tue Nov 1 00:00:08 2016

    |RemoteAccess Utils Echo Guidelines: rev. 29 May 14 |Posting Frequency: 1st of the month.
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    These are "not" rules per se', but "ideals" which we hope you will
    all agree with and shoot for, within this echo.

    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    1. When anouncing a file is available, give the pertinent data
    concerning the file:

    RA_262SW.ZIP ------------> FileName
    RA ----------------------> MagicName (if available)
    848,297 -----------------> Filesize
    56K V.90 ----------------> Max baudrate
    1:3634/12 ---------------> Address 1...
    2547:1000/12 ------------> Address 2... (and so on...)
    1-919-774-5930 ----------> System Telephone Number
    Via SDS -----------------> Yes/No (was it released into the SDS?)
    Sanford, NC, USA --------> City, State, Country (where you are)
    Anyone May FREQ 24/7 ----> Or do you allow unlisted nodes to freq?

    2. Before reporting what you believe to be a bug, check and double
    check everything, then make your report (often you will find it is
    operator error and not program error). Include enough information
    (pertinent to your problem) in your message, to enable people to
    understand your problem and offer solutions. This may include
    configurations (software & hardware), initialization strings,
    possible TSR programs, etc.

    3. When quoting a message, only quote what is pertinent to your
    response, not the whole message (if possible).

    4. Tearlines should be left as the mail proccessor makes/inserts them
    (35 characters max. none if PID is in message).

    5. When discussing your "views" on any program, be descriptive, explain
    what features you like or dislike (and why?), what works or doesn't
    and limit them to programs which work with (in one way or another)
    RemoteAccess, etc. Getting involved with "Mine is better than yours"
    type of conversations, is not productive and has no place here, or
    in any other conference. Try to maintain an objective view so that
    your post does not come across as software or author bashing.

    6. When posting an ad for a new product, make it "descriptive", but try
    to be reasonable.

    Thank You

    |Andrew Leary, 1:320/119, andrew.leary@tvcconnect.net
    Mark Lewis, 1:3634/12

    Conference Moderators



    * Origin: (1:3634/12)
  • From Moderator@1:3634/12 to All on Thu Dec 1 00:00:28 2016

    |RemoteAccess Utils Echo Guidelines: rev. 29 May 14 |Posting Frequency: 1st of the month.
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    These are "not" rules per se', but "ideals" which we hope you will
    all agree with and shoot for, within this echo.

    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    1. When anouncing a file is available, give the pertinent data
    concerning the file:

    RA_262SW.ZIP ------------> FileName
    RA ----------------------> MagicName (if available)
    848,297 -----------------> Filesize
    56K V.90 ----------------> Max baudrate
    1:3634/12 ---------------> Address 1...
    2547:1000/12 ------------> Address 2... (and so on...)
    1-919-774-5930 ----------> System Telephone Number
    Via SDS -----------------> Yes/No (was it released into the SDS?)
    Sanford, NC, USA --------> City, State, Country (where you are)
    Anyone May FREQ 24/7 ----> Or do you allow unlisted nodes to freq?

    2. Before reporting what you believe to be a bug, check and double
    check everything, then make your report (often you will find it is
    operator error and not program error). Include enough information
    (pertinent to your problem) in your message, to enable people to
    understand your problem and offer solutions. This may include
    configurations (software & hardware), initialization strings,
    possible TSR programs, etc.

    3. When quoting a message, only quote what is pertinent to your
    response, not the whole message (if possible).

    4. Tearlines should be left as the mail proccessor makes/inserts them
    (35 characters max. none if PID is in message).

    5. When discussing your "views" on any program, be descriptive, explain
    what features you like or dislike (and why?), what works or doesn't
    and limit them to programs which work with (in one way or another)
    RemoteAccess, etc. Getting involved with "Mine is better than yours"
    type of conversations, is not productive and has no place here, or
    in any other conference. Try to maintain an objective view so that
    your post does not come across as software or author bashing.

    6. When posting an ad for a new product, make it "descriptive", but try
    to be reasonable.

    Thank You

    |Andrew Leary, 1:320/119, andrew.leary@tvcconnect.net
    Mark Lewis, 1:3634/12

    Conference Moderators



    * Origin: (1:3634/12)
  • From Moderator@1:3634/12 to All on Sun Jan 1 02:26:46 2017

    |RemoteAccess Utils Echo Guidelines: rev. 29 May 14 |Posting Frequency: 1st of the month.
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    These are "not" rules per se', but "ideals" which we hope you will
    all agree with and shoot for, within this echo.

    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    1. When anouncing a file is available, give the pertinent data
    concerning the file:

    RA_262SW.ZIP ------------> FileName
    RA ----------------------> MagicName (if available)
    848,297 -----------------> Filesize
    56K V.90 ----------------> Max baudrate
    1:3634/12 ---------------> Address 1...
    2547:1000/12 ------------> Address 2... (and so on...)
    1-919-774-5930 ----------> System Telephone Number
    Via SDS -----------------> Yes/No (was it released into the SDS?)
    Sanford, NC, USA --------> City, State, Country (where you are)
    Anyone May FREQ 24/7 ----> Or do you allow unlisted nodes to freq?

    2. Before reporting what you believe to be a bug, check and double
    check everything, then make your report (often you will find it is
    operator error and not program error). Include enough information
    (pertinent to your problem) in your message, to enable people to
    understand your problem and offer solutions. This may include
    configurations (software & hardware), initialization strings,
    possible TSR programs, etc.

    3. When quoting a message, only quote what is pertinent to your
    response, not the whole message (if possible).

    4. Tearlines should be left as the mail proccessor makes/inserts them
    (35 characters max. none if PID is in message).

    5. When discussing your "views" on any program, be descriptive, explain
    what features you like or dislike (and why?), what works or doesn't
    and limit them to programs which work with (in one way or another)
    RemoteAccess, etc. Getting involved with "Mine is better than yours"
    type of conversations, is not productive and has no place here, or
    in any other conference. Try to maintain an objective view so that
    your post does not come across as software or author bashing.

    6. When posting an ad for a new product, make it "descriptive", but try
    to be reasonable.

    Thank You

    |Andrew Leary, 1:320/119, andrew.leary@tvcconnect.net
    Mark Lewis, 1:3634/12

    Conference Moderators



    * Origin: (1:3634/12)
  • From Moderator@1:3634/12 to All on Wed Feb 1 00:00:08 2017

    |RemoteAccess Utils Echo Guidelines: rev. 29 May 14 |Posting Frequency: 1st of the month.
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    These are "not" rules per se', but "ideals" which we hope you will
    all agree with and shoot for, within this echo.

    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    1. When anouncing a file is available, give the pertinent data
    concerning the file:

    RA_262SW.ZIP ------------> FileName
    RA ----------------------> MagicName (if available)
    848,297 -----------------> Filesize
    56K V.90 ----------------> Max baudrate
    1:3634/12 ---------------> Address 1...
    2547:1000/12 ------------> Address 2... (and so on...)
    1-919-774-5930 ----------> System Telephone Number
    Via SDS -----------------> Yes/No (was it released into the SDS?)
    Sanford, NC, USA --------> City, State, Country (where you are)
    Anyone May FREQ 24/7 ----> Or do you allow unlisted nodes to freq?

    2. Before reporting what you believe to be a bug, check and double
    check everything, then make your report (often you will find it is
    operator error and not program error). Include enough information
    (pertinent to your problem) in your message, to enable people to
    understand your problem and offer solutions. This may include
    configurations (software & hardware), initialization strings,
    possible TSR programs, etc.

    3. When quoting a message, only quote what is pertinent to your
    response, not the whole message (if possible).

    4. Tearlines should be left as the mail proccessor makes/inserts them
    (35 characters max. none if PID is in message).

    5. When discussing your "views" on any program, be descriptive, explain
    what features you like or dislike (and why?), what works or doesn't
    and limit them to programs which work with (in one way or another)
    RemoteAccess, etc. Getting involved with "Mine is better than yours"
    type of conversations, is not productive and has no place here, or
    in any other conference. Try to maintain an objective view so that
    your post does not come across as software or author bashing.

    6. When posting an ad for a new product, make it "descriptive", but try
    to be reasonable.

    Thank You

    |Andrew Leary, 1:320/119, andrew.leary@tvcconnect.net
    Mark Lewis, 1:3634/12

    Conference Moderators



    * Origin: (1:3634/12)
  • From Moderator@1:3634/12 to All on Sat Apr 1 00:00:08 2017

    |RemoteAccess Utils Echo Guidelines: rev. 29 May 14 |Posting Frequency: 1st of the month.
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    These are "not" rules per se', but "ideals" which we hope you will
    all agree with and shoot for, within this echo.

    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    1. When anouncing a file is available, give the pertinent data
    concerning the file:

    RA_262SW.ZIP ------------> FileName
    RA ----------------------> MagicName (if available)
    848,297 -----------------> Filesize
    56K V.90 ----------------> Max baudrate
    1:3634/12 ---------------> Address 1...
    2547:1000/12 ------------> Address 2... (and so on...)
    1-919-774-5930 ----------> System Telephone Number
    Via SDS -----------------> Yes/No (was it released into the SDS?)
    Sanford, NC, USA --------> City, State, Country (where you are)
    Anyone May FREQ 24/7 ----> Or do you allow unlisted nodes to freq?

    2. Before reporting what you believe to be a bug, check and double
    check everything, then make your report (often you will find it is
    operator error and not program error). Include enough information
    (pertinent to your problem) in your message, to enable people to
    understand your problem and offer solutions. This may include
    configurations (software & hardware), initialization strings,
    possible TSR programs, etc.

    3. When quoting a message, only quote what is pertinent to your
    response, not the whole message (if possible).

    4. Tearlines should be left as the mail proccessor makes/inserts them
    (35 characters max. none if PID is in message).

    5. When discussing your "views" on any program, be descriptive, explain
    what features you like or dislike (and why?), what works or doesn't
    and limit them to programs which work with (in one way or another)
    RemoteAccess, etc. Getting involved with "Mine is better than yours"
    type of conversations, is not productive and has no place here, or
    in any other conference. Try to maintain an objective view so that
    your post does not come across as software or author bashing.

    6. When posting an ad for a new product, make it "descriptive", but try
    to be reasonable.

    Thank You

    |Andrew Leary, 1:320/119, andrew.leary@tvcconnect.net
    Mark Lewis, 1:3634/12

    Conference Moderators



    * Origin: (1:3634/12)
  • From Moderator@1:3634/12 to All on Mon May 1 00:00:08 2017

    |RemoteAccess Utils Echo Guidelines: rev. 12 Apr 17
    Posting Frequency: 1st of the month.
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    These are "not" rules per se', but "ideals" which we hope you will
    all agree with and shoot for, within this echo.

    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    1. When anouncing a file is available, give the pertinent data
    concerning the file:

    RA_262SW.ZIP ------------> FileName
    RA ----------------------> MagicName (if available)
    848,297 -----------------> Filesize
    56K V.90 ----------------> Max baudrate
    1:3634/12 ---------------> Address 1...
    2547:1000/12 ------------> Address 2... (and so on...)
    1-919-774-5930 ----------> System Telephone Number
    Via SDS -----------------> Yes/No (was it released into the SDS?)
    Sanford, NC, USA --------> City, State, Country (where you are)
    Anyone May FREQ 24/7 ----> Or do you allow unlisted nodes to freq?

    2. Before reporting what you believe to be a bug, check and double
    check everything, then make your report (often you will find it is
    operator error and not program error). Include enough information
    (pertinent to your problem) in your message, to enable people to
    understand your problem and offer solutions. This may include
    configurations (software & hardware), initialization strings,
    possible TSR programs, etc.

    3. When quoting a message, only quote what is pertinent to your
    response, not the whole message (if possible).

    4. Tearlines should be left as the mail proccessor makes/inserts them
    (35 characters max. none if PID is in message).

    5. When discussing your "views" on any program, be descriptive, explain
    what features you like or dislike (and why?), what works or doesn't
    and limit them to programs which work with (in one way or another)
    RemoteAccess, etc. Getting involved with "Mine is better than yours"
    type of conversations, is not productive and has no place here, or
    in any other conference. Try to maintain an objective view so that
    your post does not come across as software or author bashing.

    6. When posting an ad for a new product, make it "descriptive", but try
    to be reasonable.

    Thank You

    |Andrew Leary, 1:320/219, ajleary19@gmail.com
    Mark Lewis, 1:3634/12

    Conference Moderators



    * Origin: (1:3634/12)
  • From Moderator@1:3634/12 to All on Thu Jun 1 00:00:18 2017

    |RemoteAccess Utils Echo Guidelines: rev. 12 Apr 17
    Posting Frequency: 1st of the month.
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    These are "not" rules per se', but "ideals" which we hope you will
    all agree with and shoot for, within this echo.

    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    1. When anouncing a file is available, give the pertinent data
    concerning the file:

    RA_262SW.ZIP ------------> FileName
    RA ----------------------> MagicName (if available)
    848,297 -----------------> Filesize
    56K V.90 ----------------> Max baudrate
    1:3634/12 ---------------> Address 1...
    2547:1000/12 ------------> Address 2... (and so on...)
    1-919-774-5930 ----------> System Telephone Number
    Via SDS -----------------> Yes/No (was it released into the SDS?)
    Sanford, NC, USA --------> City, State, Country (where you are)
    Anyone May FREQ 24/7 ----> Or do you allow unlisted nodes to freq?

    2. Before reporting what you believe to be a bug, check and double
    check everything, then make your report (often you will find it is
    operator error and not program error). Include enough information
    (pertinent to your problem) in your message, to enable people to
    understand your problem and offer solutions. This may include
    configurations (software & hardware), initialization strings,
    possible TSR programs, etc.

    3. When quoting a message, only quote what is pertinent to your
    response, not the whole message (if possible).

    4. Tearlines should be left as the mail proccessor makes/inserts them
    (35 characters max. none if PID is in message).

    5. When discussing your "views" on any program, be descriptive, explain
    what features you like or dislike (and why?), what works or doesn't
    and limit them to programs which work with (in one way or another)
    RemoteAccess, etc. Getting involved with "Mine is better than yours"
    type of conversations, is not productive and has no place here, or
    in any other conference. Try to maintain an objective view so that
    your post does not come across as software or author bashing.

    6. When posting an ad for a new product, make it "descriptive", but try
    to be reasonable.

    Thank You

    |Andrew Leary, 1:320/219, ajleary19@gmail.com
    Mark Lewis, 1:3634/12

    Conference Moderators



    * Origin: (1:3634/12)
  • From Moderator@1:3634/12 to All on Sat Jul 1 00:00:14 2017

    |RemoteAccess Utils Echo Guidelines: rev. 12 Apr 17
    Posting Frequency: 1st of the month.
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    These are "not" rules per se', but "ideals" which we hope you will
    all agree with and shoot for, within this echo.

    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    1. When anouncing a file is available, give the pertinent data
    concerning the file:

    RA_262SW.ZIP ------------> FileName
    RA ----------------------> MagicName (if available)
    848,297 -----------------> Filesize
    56K V.90 ----------------> Max baudrate
    1:3634/12 ---------------> Address 1...
    2547:1000/12 ------------> Address 2... (and so on...)
    1-919-774-5930 ----------> System Telephone Number
    Via SDS -----------------> Yes/No (was it released into the SDS?)
    Sanford, NC, USA --------> City, State, Country (where you are)
    Anyone May FREQ 24/7 ----> Or do you allow unlisted nodes to freq?

    2. Before reporting what you believe to be a bug, check and double
    check everything, then make your report (often you will find it is
    operator error and not program error). Include enough information
    (pertinent to your problem) in your message, to enable people to
    understand your problem and offer solutions. This may include
    configurations (software & hardware), initialization strings,
    possible TSR programs, etc.

    3. When quoting a message, only quote what is pertinent to your
    response, not the whole message (if possible).

    4. Tearlines should be left as the mail proccessor makes/inserts them
    (35 characters max. none if PID is in message).

    5. When discussing your "views" on any program, be descriptive, explain
    what features you like or dislike (and why?), what works or doesn't
    and limit them to programs which work with (in one way or another)
    RemoteAccess, etc. Getting involved with "Mine is better than yours"
    type of conversations, is not productive and has no place here, or
    in any other conference. Try to maintain an objective view so that
    your post does not come across as software or author bashing.

    6. When posting an ad for a new product, make it "descriptive", but try
    to be reasonable.

    Thank You

    |Andrew Leary, 1:320/219, ajleary19@gmail.com
    Mark Lewis, 1:3634/12

    Conference Moderators



    * Origin: (1:3634/12)
  • From Moderator@1:3634/12 to All on Fri Sep 1 00:00:10 2017

    |RemoteAccess Utils Echo Guidelines: rev. 12 Apr 17
    Posting Frequency: 1st of the month.
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    These are "not" rules per se', but "ideals" which we hope you will
    all agree with and shoot for, within this echo.

    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    1. When anouncing a file is available, give the pertinent data
    concerning the file:

    RA_262SW.ZIP ------------> FileName
    RA ----------------------> MagicName (if available)
    848,297 -----------------> Filesize
    56K V.90 ----------------> Max baudrate
    1:3634/12 ---------------> Address 1...
    2547:1000/12 ------------> Address 2... (and so on...)
    1-919-774-5930 ----------> System Telephone Number
    Via SDS -----------------> Yes/No (was it released into the SDS?)
    Sanford, NC, USA --------> City, State, Country (where you are)
    Anyone May FREQ 24/7 ----> Or do you allow unlisted nodes to freq?

    2. Before reporting what you believe to be a bug, check and double
    check everything, then make your report (often you will find it is
    operator error and not program error). Include enough information
    (pertinent to your problem) in your message, to enable people to
    understand your problem and offer solutions. This may include
    configurations (software & hardware), initialization strings,
    possible TSR programs, etc.

    3. When quoting a message, only quote what is pertinent to your
    response, not the whole message (if possible).

    4. Tearlines should be left as the mail proccessor makes/inserts them
    (35 characters max. none if PID is in message).

    5. When discussing your "views" on any program, be descriptive, explain
    what features you like or dislike (and why?), what works or doesn't
    and limit them to programs which work with (in one way or another)
    RemoteAccess, etc. Getting involved with "Mine is better than yours"
    type of conversations, is not productive and has no place here, or
    in any other conference. Try to maintain an objective view so that
    your post does not come across as software or author bashing.

    6. When posting an ad for a new product, make it "descriptive", but try
    to be reasonable.

    Thank You

    |Andrew Leary, 1:320/219, ajleary19@gmail.com
    Mark Lewis, 1:3634/12

    Conference Moderators



    * Origin: (1:3634/12)
  • From Moderator@1:3634/12 to All on Sun Oct 1 00:00:08 2017

    |RemoteAccess Utils Echo Guidelines: rev. 12 Apr 17
    Posting Frequency: 1st of the month.
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    These are "not" rules per se', but "ideals" which we hope you will
    all agree with and shoot for, within this echo.

    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    1. When anouncing a file is available, give the pertinent data
    concerning the file:

    RA_262SW.ZIP ------------> FileName
    RA ----------------------> MagicName (if available)
    848,297 -----------------> Filesize
    56K V.90 ----------------> Max baudrate
    1:3634/12 ---------------> Address 1...
    2547:1000/12 ------------> Address 2... (and so on...)
    1-919-774-5930 ----------> System Telephone Number
    Via SDS -----------------> Yes/No (was it released into the SDS?)
    Sanford, NC, USA --------> City, State, Country (where you are)
    Anyone May FREQ 24/7 ----> Or do you allow unlisted nodes to freq?

    2. Before reporting what you believe to be a bug, check and double
    check everything, then make your report (often you will find it is
    operator error and not program error). Include enough information
    (pertinent to your problem) in your message, to enable people to
    understand your problem and offer solutions. This may include
    configurations (software & hardware), initialization strings,
    possible TSR programs, etc.

    3. When quoting a message, only quote what is pertinent to your
    response, not the whole message (if possible).

    4. Tearlines should be left as the mail proccessor makes/inserts them
    (35 characters max. none if PID is in message).

    5. When discussing your "views" on any program, be descriptive, explain
    what features you like or dislike (and why?), what works or doesn't
    and limit them to programs which work with (in one way or another)
    RemoteAccess, etc. Getting involved with "Mine is better than yours"
    type of conversations, is not productive and has no place here, or
    in any other conference. Try to maintain an objective view so that
    your post does not come across as software or author bashing.

    6. When posting an ad for a new product, make it "descriptive", but try
    to be reasonable.

    Thank You

    |Andrew Leary, 1:320/219, ajleary19@gmail.com
    Mark Lewis, 1:3634/12

    Conference Moderators



    * Origin: (1:3634/12)
  • From Moderator@1:3634/12 to All on Wed Nov 1 00:00:10 2017

    |RemoteAccess Utils Echo Guidelines: rev. 12 Apr 17
    Posting Frequency: 1st of the month.
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    These are "not" rules per se', but "ideals" which we hope you will
    all agree with and shoot for, within this echo.

    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    1. When anouncing a file is available, give the pertinent data
    concerning the file:

    RA_262SW.ZIP ------------> FileName
    RA ----------------------> MagicName (if available)
    848,297 -----------------> Filesize
    56K V.90 ----------------> Max baudrate
    1:3634/12 ---------------> Address 1...
    2547:1000/12 ------------> Address 2... (and so on...)
    1-919-774-5930 ----------> System Telephone Number
    Via SDS -----------------> Yes/No (was it released into the SDS?)
    Sanford, NC, USA --------> City, State, Country (where you are)
    Anyone May FREQ 24/7 ----> Or do you allow unlisted nodes to freq?

    2. Before reporting what you believe to be a bug, check and double
    check everything, then make your report (often you will find it is
    operator error and not program error). Include enough information
    (pertinent to your problem) in your message, to enable people to
    understand your problem and offer solutions. This may include
    configurations (software & hardware), initialization strings,
    possible TSR programs, etc.

    3. When quoting a message, only quote what is pertinent to your
    response, not the whole message (if possible).

    4. Tearlines should be left as the mail proccessor makes/inserts them
    (35 characters max. none if PID is in message).

    5. When discussing your "views" on any program, be descriptive, explain
    what features you like or dislike (and why?), what works or doesn't
    and limit them to programs which work with (in one way or another)
    RemoteAccess, etc. Getting involved with "Mine is better than yours"
    type of conversations, is not productive and has no place here, or
    in any other conference. Try to maintain an objective view so that
    your post does not come across as software or author bashing.

    6. When posting an ad for a new product, make it "descriptive", but try
    to be reasonable.

    Thank You

    |Andrew Leary, 1:320/219, ajleary19@gmail.com
    Mark Lewis, 1:3634/12

    Conference Moderators



    * Origin: (1:3634/12)
  • From Moderator@1:3634/12 to All on Fri Dec 1 00:00:10 2017

    |RemoteAccess Utils Echo Guidelines: rev. 12 Apr 17
    Posting Frequency: 1st of the month.
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    These are "not" rules per se', but "ideals" which we hope you will
    all agree with and shoot for, within this echo.

    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    1. When anouncing a file is available, give the pertinent data
    concerning the file:

    RA_262SW.ZIP ------------> FileName
    RA ----------------------> MagicName (if available)
    848,297 -----------------> Filesize
    56K V.90 ----------------> Max baudrate
    1:3634/12 ---------------> Address 1...
    2547:1000/12 ------------> Address 2... (and so on...)
    1-919-774-5930 ----------> System Telephone Number
    Via SDS -----------------> Yes/No (was it released into the SDS?)
    Sanford, NC, USA --------> City, State, Country (where you are)
    Anyone May FREQ 24/7 ----> Or do you allow unlisted nodes to freq?

    2. Before reporting what you believe to be a bug, check and double
    check everything, then make your report (often you will find it is
    operator error and not program error). Include enough information
    (pertinent to your problem) in your message, to enable people to
    understand your problem and offer solutions. This may include
    configurations (software & hardware), initialization strings,
    possible TSR programs, etc.

    3. When quoting a message, only quote what is pertinent to your
    response, not the whole message (if possible).

    4. Tearlines should be left as the mail proccessor makes/inserts them
    (35 characters max. none if PID is in message).

    5. When discussing your "views" on any program, be descriptive, explain
    what features you like or dislike (and why?), what works or doesn't
    and limit them to programs which work with (in one way or another)
    RemoteAccess, etc. Getting involved with "Mine is better than yours"
    type of conversations, is not productive and has no place here, or
    in any other conference. Try to maintain an objective view so that
    your post does not come across as software or author bashing.

    6. When posting an ad for a new product, make it "descriptive", but try
    to be reasonable.

    Thank You

    |Andrew Leary, 1:320/219, ajleary19@gmail.com
    Mark Lewis, 1:3634/12

    Conference Moderators



    * Origin: (1:3634/12)
  • From Moderator@1:3634/12 to All on Thu Feb 1 00:00:10 2018

    |RemoteAccess Utils Echo Guidelines: rev. 12 Apr 17
    Posting Frequency: 1st of the month.
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    These are "not" rules per se', but "ideals" which we hope you will
    all agree with and shoot for, within this echo.

    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    1. When anouncing a file is available, give the pertinent data
    concerning the file:

    RA_262SW.ZIP ------------> FileName
    RA ----------------------> MagicName (if available)
    848,297 -----------------> Filesize
    56K V.90 ----------------> Max baudrate
    1:3634/12 ---------------> Address 1...
    2547:1000/12 ------------> Address 2... (and so on...)
    1-919-774-5930 ----------> System Telephone Number
    Via SDS -----------------> Yes/No (was it released into the SDS?)
    Sanford, NC, USA --------> City, State, Country (where you are)
    Anyone May FREQ 24/7 ----> Or do you allow unlisted nodes to freq?

    2. Before reporting what you believe to be a bug, check and double
    check everything, then make your report (often you will find it is
    operator error and not program error). Include enough information
    (pertinent to your problem) in your message, to enable people to
    understand your problem and offer solutions. This may include
    configurations (software & hardware), initialization strings,
    possible TSR programs, etc.

    3. When quoting a message, only quote what is pertinent to your
    response, not the whole message (if possible).

    4. Tearlines should be left as the mail proccessor makes/inserts them
    (35 characters max. none if PID is in message).

    5. When discussing your "views" on any program, be descriptive, explain
    what features you like or dislike (and why?), what works or doesn't
    and limit them to programs which work with (in one way or another)
    RemoteAccess, etc. Getting involved with "Mine is better than yours"
    type of conversations, is not productive and has no place here, or
    in any other conference. Try to maintain an objective view so that
    your post does not come across as software or author bashing.

    6. When posting an ad for a new product, make it "descriptive", but try
    to be reasonable.

    Thank You

    |Andrew Leary, 1:320/219, ajleary19@gmail.com
    Mark Lewis, 1:3634/12

    Conference Moderators



    * Origin: (1:3634/12)
  • From Moderator@1:3634/12 to All on Thu Mar 1 00:00:10 2018

    |RemoteAccess Utils Echo Guidelines: rev. 12 Apr 17
    Posting Frequency: 1st of the month.
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    These are "not" rules per se', but "ideals" which we hope you will
    all agree with and shoot for, within this echo.

    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    1. When anouncing a file is available, give the pertinent data
    concerning the file:

    RA_262SW.ZIP ------------> FileName
    RA ----------------------> MagicName (if available)
    848,297 -----------------> Filesize
    56K V.90 ----------------> Max baudrate
    1:3634/12 ---------------> Address 1...
    2547:1000/12 ------------> Address 2... (and so on...)
    1-919-774-5930 ----------> System Telephone Number
    Via SDS -----------------> Yes/No (was it released into the SDS?)
    Sanford, NC, USA --------> City, State, Country (where you are)
    Anyone May FREQ 24/7 ----> Or do you allow unlisted nodes to freq?

    2. Before reporting what you believe to be a bug, check and double
    check everything, then make your report (often you will find it is
    operator error and not program error). Include enough information
    (pertinent to your problem) in your message, to enable people to
    understand your problem and offer solutions. This may include
    configurations (software & hardware), initialization strings,
    possible TSR programs, etc.

    3. When quoting a message, only quote what is pertinent to your
    response, not the whole message (if possible).

    4. Tearlines should be left as the mail proccessor makes/inserts them
    (35 characters max. none if PID is in message).

    5. When discussing your "views" on any program, be descriptive, explain
    what features you like or dislike (and why?), what works or doesn't
    and limit them to programs which work with (in one way or another)
    RemoteAccess, etc. Getting involved with "Mine is better than yours"
    type of conversations, is not productive and has no place here, or
    in any other conference. Try to maintain an objective view so that
    your post does not come across as software or author bashing.

    6. When posting an ad for a new product, make it "descriptive", but try
    to be reasonable.

    Thank You

    |Andrew Leary, 1:320/219, ajleary19@gmail.com
    Mark Lewis, 1:3634/12

    Conference Moderators



    * Origin: (1:3634/12)
  • From Moderator@1:3634/12 to All on Sun Apr 1 00:00:10 2018

    |RemoteAccess Utils Echo Guidelines: rev. 12 Apr 17
    Posting Frequency: 1st of the month.
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    These are "not" rules per se', but "ideals" which we hope you will
    all agree with and shoot for, within this echo.

    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    1. When anouncing a file is available, give the pertinent data
    concerning the file:

    RA_262SW.ZIP ------------> FileName
    RA ----------------------> MagicName (if available)
    848,297 -----------------> Filesize
    56K V.90 ----------------> Max baudrate
    1:3634/12 ---------------> Address 1...
    2547:1000/12 ------------> Address 2... (and so on...)
    1-919-774-5930 ----------> System Telephone Number
    Via SDS -----------------> Yes/No (was it released into the SDS?)
    Sanford, NC, USA --------> City, State, Country (where you are)
    Anyone May FREQ 24/7 ----> Or do you allow unlisted nodes to freq?

    2. Before reporting what you believe to be a bug, check and double
    check everything, then make your report (often you will find it is
    operator error and not program error). Include enough information
    (pertinent to your problem) in your message, to enable people to
    understand your problem and offer solutions. This may include
    configurations (software & hardware), initialization strings,
    possible TSR programs, etc.

    3. When quoting a message, only quote what is pertinent to your
    response, not the whole message (if possible).

    4. Tearlines should be left as the mail proccessor makes/inserts them
    (35 characters max. none if PID is in message).

    5. When discussing your "views" on any program, be descriptive, explain
    what features you like or dislike (and why?), what works or doesn't
    and limit them to programs which work with (in one way or another)
    RemoteAccess, etc. Getting involved with "Mine is better than yours"
    type of conversations, is not productive and has no place here, or
    in any other conference. Try to maintain an objective view so that
    your post does not come across as software or author bashing.

    6. When posting an ad for a new product, make it "descriptive", but try
    to be reasonable.

    Thank You

    |Andrew Leary, 1:320/219, ajleary19@gmail.com
    Mark Lewis, 1:3634/12

    Conference Moderators



    * Origin: (1:3634/12)
  • From Moderator@1:3634/12 to All on Fri Jun 1 00:00:16 2018

    |RemoteAccess Utils Echo Guidelines: rev. 12 Apr 17
    Posting Frequency: 1st of the month.
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    These are "not" rules per se', but "ideals" which we hope you will
    all agree with and shoot for, within this echo.

    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    1. When anouncing a file is available, give the pertinent data
    concerning the file:

    RA_262SW.ZIP ------------> FileName
    RA ----------------------> MagicName (if available)
    848,297 -----------------> Filesize
    56K V.90 ----------------> Max baudrate
    1:3634/12 ---------------> Address 1...
    2547:1000/12 ------------> Address 2... (and so on...)
    1-919-774-5930 ----------> System Telephone Number
    Via SDS -----------------> Yes/No (was it released into the SDS?)
    Sanford, NC, USA --------> City, State, Country (where you are)
    Anyone May FREQ 24/7 ----> Or do you allow unlisted nodes to freq?

    2. Before reporting what you believe to be a bug, check and double
    check everything, then make your report (often you will find it is
    operator error and not program error). Include enough information
    (pertinent to your problem) in your message, to enable people to
    understand your problem and offer solutions. This may include
    configurations (software & hardware), initialization strings,
    possible TSR programs, etc.

    3. When quoting a message, only quote what is pertinent to your
    response, not the whole message (if possible).

    4. Tearlines should be left as the mail proccessor makes/inserts them
    (35 characters max. none if PID is in message).

    5. When discussing your "views" on any program, be descriptive, explain
    what features you like or dislike (and why?), what works or doesn't
    and limit them to programs which work with (in one way or another)
    RemoteAccess, etc. Getting involved with "Mine is better than yours"
    type of conversations, is not productive and has no place here, or
    in any other conference. Try to maintain an objective view so that
    your post does not come across as software or author bashing.

    6. When posting an ad for a new product, make it "descriptive", but try
    to be reasonable.

    Thank You

    |Andrew Leary, 1:320/219, ajleary19@gmail.com
    Mark Lewis, 1:3634/12

    Conference Moderators



    * Origin: (1:3634/12)
  • From Moderator@1:3634/12 to All on Sun Jul 1 00:00:10 2018

    |RemoteAccess Utils Echo Guidelines: rev. 12 Apr 17
    Posting Frequency: 1st of the month.
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    These are "not" rules per se', but "ideals" which we hope you will
    all agree with and shoot for, within this echo.

    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    1. When anouncing a file is available, give the pertinent data
    concerning the file:

    RA_262SW.ZIP ------------> FileName
    RA ----------------------> MagicName (if available)
    848,297 -----------------> Filesize
    56K V.90 ----------------> Max baudrate
    1:3634/12 ---------------> Address 1...
    2547:1000/12 ------------> Address 2... (and so on...)
    1-919-774-5930 ----------> System Telephone Number
    Via SDS -----------------> Yes/No (was it released into the SDS?)
    Sanford, NC, USA --------> City, State, Country (where you are)
    Anyone May FREQ 24/7 ----> Or do you allow unlisted nodes to freq?

    2. Before reporting what you believe to be a bug, check and double
    check everything, then make your report (often you will find it is
    operator error and not program error). Include enough information
    (pertinent to your problem) in your message, to enable people to
    understand your problem and offer solutions. This may include
    configurations (software & hardware), initialization strings,
    possible TSR programs, etc.

    3. When quoting a message, only quote what is pertinent to your
    response, not the whole message (if possible).

    4. Tearlines should be left as the mail proccessor makes/inserts them
    (35 characters max. none if PID is in message).

    5. When discussing your "views" on any program, be descriptive, explain
    what features you like or dislike (and why?), what works or doesn't
    and limit them to programs which work with (in one way or another)
    RemoteAccess, etc. Getting involved with "Mine is better than yours"
    type of conversations, is not productive and has no place here, or
    in any other conference. Try to maintain an objective view so that
    your post does not come across as software or author bashing.

    6. When posting an ad for a new product, make it "descriptive", but try
    to be reasonable.

    Thank You

    |Andrew Leary, 1:320/219, ajleary19@gmail.com
    Mark Lewis, 1:3634/12

    Conference Moderators



    * Origin: (1:3634/12)
  • From Moderator@1:3634/12 to All on Wed Aug 1 00:00:12 2018

    |RemoteAccess Utils Echo Guidelines: rev. 12 Apr 17
    Posting Frequency: 1st of the month.
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    These are "not" rules per se', but "ideals" which we hope you will
    all agree with and shoot for, within this echo.

    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    1. When anouncing a file is available, give the pertinent data
    concerning the file:

    RA_262SW.ZIP ------------> FileName
    RA ----------------------> MagicName (if available)
    848,297 -----------------> Filesize
    56K V.90 ----------------> Max baudrate
    1:3634/12 ---------------> Address 1...
    2547:1000/12 ------------> Address 2... (and so on...)
    1-919-774-5930 ----------> System Telephone Number
    Via SDS -----------------> Yes/No (was it released into the SDS?)
    Sanford, NC, USA --------> City, State, Country (where you are)
    Anyone May FREQ 24/7 ----> Or do you allow unlisted nodes to freq?

    2. Before reporting what you believe to be a bug, check and double
    check everything, then make your report (often you will find it is
    operator error and not program error). Include enough information
    (pertinent to your problem) in your message, to enable people to
    understand your problem and offer solutions. This may include
    configurations (software & hardware), initialization strings,
    possible TSR programs, etc.

    3. When quoting a message, only quote what is pertinent to your
    response, not the whole message (if possible).

    4. Tearlines should be left as the mail proccessor makes/inserts them
    (35 characters max. none if PID is in message).

    5. When discussing your "views" on any program, be descriptive, explain
    what features you like or dislike (and why?), what works or doesn't
    and limit them to programs which work with (in one way or another)
    RemoteAccess, etc. Getting involved with "Mine is better than yours"
    type of conversations, is not productive and has no place here, or
    in any other conference. Try to maintain an objective view so that
    your post does not come across as software or author bashing.

    6. When posting an ad for a new product, make it "descriptive", but try
    to be reasonable.

    Thank You

    |Andrew Leary, 1:320/219, ajleary19@gmail.com
    Mark Lewis, 1:3634/12

    Conference Moderators



    * Origin: (1:3634/12)
  • From Moderator@1:3634/12 to All on Sat Sep 1 00:00:20 2018

    |RemoteAccess Utils Echo Guidelines: rev. 12 Apr 17
    Posting Frequency: 1st of the month.
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    These are "not" rules per se', but "ideals" which we hope you will
    all agree with and shoot for, within this echo.

    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    1. When anouncing a file is available, give the pertinent data
    concerning the file:

    RA_262SW.ZIP ------------> FileName
    RA ----------------------> MagicName (if available)
    848,297 -----------------> Filesize
    56K V.90 ----------------> Max baudrate
    1:3634/12 ---------------> Address 1...
    2547:1000/12 ------------> Address 2... (and so on...)
    1-919-774-5930 ----------> System Telephone Number
    Via SDS -----------------> Yes/No (was it released into the SDS?)
    Sanford, NC, USA --------> City, State, Country (where you are)
    Anyone May FREQ 24/7 ----> Or do you allow unlisted nodes to freq?

    2. Before reporting what you believe to be a bug, check and double
    check everything, then make your report (often you will find it is
    operator error and not program error). Include enough information
    (pertinent to your problem) in your message, to enable people to
    understand your problem and offer solutions. This may include
    configurations (software & hardware), initialization strings,
    possible TSR programs, etc.

    3. When quoting a message, only quote what is pertinent to your
    response, not the whole message (if possible).

    4. Tearlines should be left as the mail proccessor makes/inserts them
    (35 characters max. none if PID is in message).

    5. When discussing your "views" on any program, be descriptive, explain
    what features you like or dislike (and why?), what works or doesn't
    and limit them to programs which work with (in one way or another)
    RemoteAccess, etc. Getting involved with "Mine is better than yours"
    type of conversations, is not productive and has no place here, or
    in any other conference. Try to maintain an objective view so that
    your post does not come across as software or author bashing.

    6. When posting an ad for a new product, make it "descriptive", but try
    to be reasonable.

    Thank You

    |Andrew Leary, 1:320/219, ajleary19@gmail.com
    Mark Lewis, 1:3634/12

    Conference Moderators



    * Origin: (1:3634/12)