From Newsgroup: alt.bbs.wildcat

Hi, I'm new to Wildcat (4 for DOS) and I am having problems getting
ascii menus for some clients. When I connect via a DOS machine with a
term program that has ANSI I get the nice colour menus. If I use
something like say my TRS-80 Model 100 and it's built-in terminal
program with no ANSI I get text interspersed with garbled characters.

I edited the .bbs files, leaving the colour codes in but removing the
extended ascii characters. This didn't help. Then I deleted all the
files in the menu folder (yes they're backed up) so that Wildcat will
only serve dynamically generated ascii menus, and I still get garbled characters (with "lesser" terminal client programs).

Am I missing something? Should ascii menus not work with any old 8-
bit machine that has the basic ascii character set?

Regards,
Doug

--- Synchronet 3.20c-Linux NewsLink 1.2

From Newsgroup: alt.bbs.wildcat

On 24 Apr 2007 12:38:48 -0700, Doug_M <doug.mccomber@gmail.com> wrote:

Hi, I'm new to Wildcat (4 for DOS) and I am having problems getting
ascii menus for some clients. When I connect via a DOS machine with a
term program that has ANSI I get the nice colour menus. If I use
something like say my TRS-80 Model 100 and it's built-in terminal
program with no ANSI I get text interspersed with garbled characters.

Whoa... WC4, TRS-80... did this just pop up from somebody's
backed-up outbound message queue, or is this really a new message in
2007?? Feeling like I'm in a time warp...

Unfortunately, it's been too many years since I ran WC4 (or, really,
any BBS at all) to be of any help. I vaguely remember there being
color even in the WC-generated menus (with all .bbs files gone), but
I'm not sure of that. If there is, there might be a way to disable
it, to ensure no terminal codes for color are sent over the wire.
--
S. Whitmore [Omit -bounce to respond]

Show off your best videos at:
http://www.MyVidsRock.com/
--- Synchronet 3.20c-Linux NewsLink 1.2

From Newsgroup: alt.bbs.wildcat

S. Whitmore wrote:

On 24 Apr 2007 12:38:48 -0700, Doug_M <doug.mccomber@gmail.com> wrote:

Hi, I'm new to Wildcat (4 for DOS) and I am having problems getting
ascii menus for some clients. When I connect via a DOS machine with a
term program that has ANSI I get the nice colour menus. If I use
something like say my TRS-80 Model 100 and it's built-in terminal
program with no ANSI I get text interspersed with garbled characters.

Whoa... WC4, TRS-80... did this just pop up from somebody's
backed-up outbound message queue, or is this really a new message in
2007?? Feeling like I'm in a time warp...

Unfortunately, it's been too many years since I ran WC4 (or, really,
any BBS at all) to be of any help. I vaguely remember there being
color even in the WC-generated menus (with all .bbs files gone), but
I'm not sure of that. If there is, there might be a way to disable
it, to ensure no terminal codes for color are sent over the wire.

Hi...

Wow, another flashback... :)

Been waaaay too long for me, too... but I vaguely remember
that wc auto-detected ansi (get cursor position = 0,0 is
impossible, hence non-ansi), and then displayed the appropriate
version of each file (menu's, conf listings, etc)

Take care.

Ken
--- Synchronet 3.20c-Linux NewsLink 1.2

From Newsgroup: alt.bbs.wildcat

On Apr 24, 4:38 pm, Doug_M <doug.mccom...@gmail.com> wrote:

Hi, I'm new to Wildcat (4 for DOS) and I am having problems getting
ascii menus for some clients. When I connect via a DOS machine with a
term program that has ANSI I get the nice colour menus. If I use
something like say my TRS-80 Model 100 and it's built-in terminal
program with no ANSI I get text interspersed with garbled characters.

I edited the .bbs files, leaving the colour codes in but removing the extended ascii characters. This didn't help. Then I deleted all the
files in the menu folder (yes they're backed up) so that Wildcat will
only serve dynamically generated ascii menus, and I still get garbled characters (with "lesser" terminal client programs).

Am I missing something? Should ascii menus not work with any old 8-
bit machine that has the basic ascii character set?

Regards,
Doug

Yup, I really asked this question in 2007! Old computers/software is
a hobby of mine. Anyway, the answers turns out to be something called
extended ASCII (or high ASCII). http://en.wikipedia.org/wiki/Extended_ASCII

Some of the dynamically generated menus WC4 makes uses them but one
can create menus without any. Turned out that I used a couple of
characters I thought were pure ASCII but were actually extended.

Regards,
Doug

--- Synchronet 3.20c-Linux NewsLink 1.2

From Newsgroup: alt.bbs.wildcat

On 26 Apr 2007 12:21:34 -0700, Doug_M <doug.mccomber@gmail.com> wrote:

Some of the dynamically generated menus WC4 makes uses them...

That's interesting, because I was pretty sure that wasn't the case.
But given how long it's been since I ran WC4, I'm not surprised that
my memory didn't serve me correctly!
--
S. Whitmore [Omit -bounce to respond]

Show off your best videos at:
http://www.MyVidsRock.com/
--- Synchronet 3.20c-Linux NewsLink 1.2

From Newsgroup: alt.bbs.wildcat

Ken Weitzel <kweitzel@shaw.ca> wrote in news:FQvXh.122889$DE1.109012 @pd7urf2no:

S. Whitmore wrote:

On 24 Apr 2007 12:38:48 -0700, Doug_M <doug.mccomber@gmail.com> wrote:

Hi, I'm new to Wildcat (4 for DOS) and I am having problems getting
ascii menus for some clients. When I connect via a DOS machine with

a

term program that has ANSI I get the nice colour menus. If I use
something like say my TRS-80 Model 100 and it's built-in terminal
program with no ANSI I get text interspersed with garbled characters.

Whoa... WC4, TRS-80... did this just pop up from somebody's
backed-up outbound message queue, or is this really a new message in
2007?? Feeling like I'm in a time warp...

Unfortunately, it's been too many years since I ran WC4 (or, really,
any BBS at all) to be of any help. I vaguely remember there being
color even in the WC-generated menus (with all .bbs files gone), but
I'm not sure of that. If there is, there might be a way to disable
it, to ensure no terminal codes for color are sent over the wire.

Hi...

Wow, another flashback... :)

Been waaaay too long for me, too... but I vaguely remember
that wc auto-detected ansi (get cursor position = 0,0 is
impossible, hence non-ansi), and then displayed the appropriate
version of each file (menu's, conf listings, etc)

Take care.

Ken

Been a long time for me too (96), but if I recall correctly, you needed ansi.sys on any system connecting to get the ansi text to display
properly. The TRS-80 is before my time, so I don't know if ansi.sys was
even around then.
--- Synchronet 3.20c-Linux NewsLink 1.2

From Newsgroup: alt.bbs.wildcat

I believe that if you use .asc for the filename it will display them as
plain text.

Allen
--- Synchronet 3.20c-Linux NewsLink 1.2