MSGID: 2:221/1.58@fidonet ef718475
REPLY: 2:280/464 60780064
PID: OpenXP/5.0.49 (Win32)
CHRS: ASCII 1
TZUTC: -0400
Hello Wilfred!

** On Thursday 15.04.21 - 10:57, you wrote to me:

 AA>> It seems to be a problem for WinPoint when building a
 AA>> reply message.  The REPLYID seems to result in 00000000.

 WvV> So that is the first discovered problem. There are
 WvV> probably more. And probably harder to discover...

I may have to spin up my Winpoint to see for myself. But  
apparently Winpoint is getting new life in development and the  
uber msgid could be accomodated.  :D

 WvV>>> Because it doesn't conform to the standard (not strictly
 WvV>>> hex chars),

 AA>> You are adding words to the spec.  "strictly" does not appear.

 AA>> ;)  However, "may" is very clear.  :D

 WvV> I beg to differ...

According to fta-1006, the definitions are clear. But  
interestingly, the doc expired 20 years ago.  Why a definition  
doc needs to expire (and not be replaced by something else)  
alludes me.

 AA>> They're all just a bunch of 1's and 0's in the end.  It's
 AA>> all the same stuff.  :D

 WvV> But how we get there isn't...

Oh.. that's true enough.  But I've made my point. Assuming that  
the serialno must be implemenet in hex is just that, an  
assumption.
--
  ../|ug

--- OpenXP 5.0.49
 * Origin: Mobile? ASIAN_LINK https://preview.tinyurl.com/y6rwskq (2:221/1.58)
SEEN-BY: 1/123 18/200 90/1 105/81 114/705 120/340 123/120 131 124/5016
SEEN-BY: 129/305 153/250 154/10 203/0 220/70 221/1 6 360 226/17 30
SEEN-BY: 227/114 229/101 424 426 452 664 700 1016 1017 230/0 240/5832
SEEN-BY: 249/206 317 400 250/5 8 267/800 280/464 5003 282/1038 288/100
SEEN-BY: 292/8125 298/25 301/1 305/3 310/31 317/3 322/757 340/1000
SEEN-BY: 342/200 396/45 423/81 120 460/58 633/280 712/848 770/1 100
SEEN-BY: 770/330 340 772/210 220 230
PATH: 221/1 280/464 770/1 317/3 229/426