Running the latest version of Mystic, does anyone have a way to get the emulated baud rate working in the ANSI Art Gallery?

I have tried this on the "DATA" portion: M:\ANSI-1;50 and also M:\ANSI-1;DI50.

It seems to ignore those parameters and displays at top speed.

- Mark
ÿÿÿÿÿ
--- WWIVToss v.1.51
* Origin: http://www.weather-station.org * Bel Air, MD -USA (21:1/132.0)

On 09/18/16, Weatherman said the following...

Running the latest version of Mystic, does anyone have a way to get the emulated baud rate working in the ANSI Art Gallery?

I think it was taken out of the latest version (A31). Not sure why, but I
know it doesn't work under A31 on any system (Windows/Linux/Mac). My guess is speed problems - meaning it depended on the system speed and the faster the system the less the effect of it (as timing loops work).

--- Mystic BBS v1.12 A31 (Raspberry Pi)
* Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)

I think it was taken out of the latest version (A31). Not sure why, but I know it doesn't work under A31 on any system (Windows/Linux/Mac). My
guess is speed problems - meaning it depended on the system speed and
the faster the system the less the effect of it (as timing loops work).

Maybe the option could turn into more of a "delay" option, so the faster your particular system, the more delay you would have to add. Basically would be unique depending on hardware.

I'm happy to report that I'm live over here on my Weather Station BBS
(Mystic) side of things in fsxNet!

I did reproduce the "Use CRAM-MD5" thing with both WWIVnet and fsxNet.

When Mystic does a Fidopoll to my D'Bridge hub, all works fine with the CRAM-MD5 setting to "YES". When D'Bridge polls Mystic, it fails in that direction. D'Bridge reports "No matching AKA" on remote system, but I see
the match. Setting CRAM-MD5 to "NO" fixes this.

I don't know if this is a D'Bridge issue or Mystic, but that sums up the particular situation.

- Mark

--- Mystic BBS v1.12 A31 (Windows)
* Origin: Weather Station BBS * Bel Air, MD -USA (21:1/170)