Hi Paul,

I probably wouldn't use any of those test .exe files right now. It seems
that by trying to fix IREX its causing all sorts of other problems.

--- Mystic BBS v1.12 A36 2017/11/13 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 11/13/17, g00r00 pondered and said...

Hi Paul,

I probably wouldn't use any of those test .exe files right now. It seems that by trying to fix IREX its causing all sorts of other problems.

Thanks James... all good. I ended up having a night off BBS last night
instead watching some Netflix so had not upgraded. I will sit tight and leave the current .exes in place. They are the first ones you rolled out for Skuz
and I and seem to be working ok.

7.50am Tuesday and off to work I go.. have a good one.

Best, Paul

--- Mystic BBS v1.12 A36 2017/11/09 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

Thanks James... all good. I ended up having a night off BBS last night instead watching some Netflix so had not upgraded. I will sit tight and leave the current .exes in place. They are the first ones you rolled out for Skuz and I and seem to be working ok.

I've since made another update this morning which fixes at least one issue
the previous .exe files had.

--- Mystic BBS v1.12 A36 2017/11/13 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

Quoting g00r00 to Avon <=-

I probably wouldn't use any of those test .exe files right now. It
seems that by trying to fix IREX its causing all sorts of other
problems.

As someone who still runs IREX on my DOS system... IMO you should not
cripple your product so it will work with old un supported software.
I think you're wasting time and energy on "breaking" BinkP to get along
with rex.

If Paul netmailed me and said "I can't hub you in 3 days if you don't get
rid of irex" it wouldn't be the end of the world and I'd get off my lazy
ass and configure binkd on the windows VM.

Just IMO of course.

Shawn

... Failure is a measurement that depends on the standard applied.
--- Blue Wave/386
* Origin: A Tiny slice o pi (21:1/130.4)

On 11/13/17, g00r00 pondered and said...

I've since made another update this morning which fixes at least one
issue the previous .exe files had.

The great alpha/beta question of our times.... to update or not to update :) That is the question..

--- Mystic BBS v1.12 A36 2017/11/09 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

The great alpha/beta question of our times.... to update or not to
update :) That is the question..

I would probably update from what you're using now if you are using those A36 test versions.

--- Mystic BBS v1.12 A36 2017/11/13 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 11/13/17, g00r00 pondered and said...

I would probably update from what you're using now if you are using
those A36 test versions.

OK will do this tonight, which is now about six hours away... 12.52pm local time, just at work and eating lunch/reading echomail... as you do :)

--- Mystic BBS v1.12 A36 2017/11/09 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

On 11/13/17, g00r00 pondered and said...

^^^^^^^^^^^^

Just a quick request...the date that used in the quote header... I have a
hunch I can't alter the MM/DD/YY to DD/MM/YY using the hard coded MCI codes
for that prompt... is there something you add to allow that?

The version 2.0 update of the above request would be to allow the sysop to insert a day, month MCI code that could display as

On Tuesday, November 14th 2017, g00r00 pondered and said.... (or something like that)...

I'd also love a code I could insert in the body copy or in my sig that would show the date *and* local time I posted my reply. Just because it's nice to
see the time of day when something is posted.. well I enjoy seeing it :)

Anywhoo just some thoughts and suggestions for the ideas pot.

Thanks :)

Best, Paul

--- Mystic BBS v1.12 A36 2017/11/09 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

On 11/13/17, g00r00 said the following...

I would probably update from what you're using now if you are using
those A36 test versions.

I've updated mine a few minutes ago and did a 3rd installment of the logs
from polling my system for waiting mail.. logs where just emailed (fluph_debug3_A36.zip) I do agree with what "Tiny" said about ancient internet rex being abandon-ware and hate to see you wast valuable time on it. I can
also get off my lazy butt and config binkd for win32 or some other mailer.

--- Mystic BBS v1.12 A36 2017/11/09 (Windows/32)
* Origin: flupH | fluph.darktech.org (21:1/105)

On 11/13/17, g00r00 pondered and said...

I would probably update from what you're using now if you are using
those A36 test versions.

All done, both .exe's now in place at 1/100

[snip]

Nov 14 18:50:05 FIDOPOLL Version 1.12 A36 2017/11/13
Nov 14 18:50:05 Scanning 21:1/112

[snip]

---------- Mystic v1.12 A36 2017/11/13 Tue, Nov 14 2017 (loglevel 3)
+ 18:48:50 MANAGER Starting event system
+ 18:48:50 MANAGER Starting 1 server(s)
+ 18:48:50 BINKP Listening on IPV4 port 24556 using interface "0.0.0.0"
+ 18:48:50 BINKP Listening on IPV6 port 24556 using interface "::"
+ 18:48:50 EVENT Starting 4 event(s)
+ 18:49:25 BINKP > Connect on slot 1/16
+ 18:49:25 BINKP 1-Address 199.166.5.19
+ 18:49:25 BINKP 1-HostName zork.platinum.net
+ 18:49:25 BINKP 1-Frame wait
+ 18:49:25 BINKP 1-Auth State:SendChallenge Have:False Need:True
+ 18:49:25 BINKP 1-Sent Frame: NUL OPT CRAM-MD5-bb9d607efeeeb56c2f2c47b10eec0200
+ 18:49:25 BINKP 1-New frame detected
+ 18:49:25 BINKP 1-Begin receive command frame: NUL (Size=20)

[snip]

will send you logging for 12 hours when I get up tomorrow morning... just
set this in place coming up 19:00 local time Tue night.

Best, Paul

--- Mystic BBS v1.12 A36 2017/11/09 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

Just a quick request...the date that used in the quote header... I have a hunch I can't alter the MM/DD/YY to DD/MM/YY using the hard coded MCI codes for that prompt... is there something you add to allow that?

It should be using your configured date input format. I intend to change it to DD MMM YYYY though, which is the direction I am moving for date display, outside of date input which will be still configurable per-user as it is now.

I'd also love a code I could insert in the body copy or in my sig that would show the date *and* local time I posted my reply. Just because

I am a bit confused by this one. There is a date and time in the message header already!

--- Mystic BBS v1.12 A36 2017/11/14 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)