TZUTC: -0500   
   MSGID: 26698.memoryln@1:2320/105 2d18e80e   
   REPLY: 23401.memories@1:218/700 2d18b43a   
   PID: Synchronet 3.21a-Linux master/123f2d28a Jul 12 2025 GCC 12.2.0   
   TID: SBBSecho 3.28-Linux master/123f2d28a Jul 12 2025 GCC 12.2.0   
   BBSID: CAPCITY2   
   CHRS: ASCII 1   
   FORMAT: flowed   
   >  Most of what I use the calculator on my desk for it converting decimal   
   >  to hex and vice versa. Fidonet technology, when passing files back and   
   >  forth, uses the hex representation of the decimal network and node   
   >  number for file names, and figuring out which file goes to who can be   
   >  tricky.   
      
   That has always frustrated me because we dealt with hex at work all the   
   time, and the hex values I see on an FTN do *not* equal what we used at   
   work.  Granted, ours were *usually* EBCDIC but even the ASCII values are   
   not "right."   
      
   How did you do it on a calculator?  That might be handy to know.   
      
   >  Although, Synchronet's echocfg utility, where you define nodes, now   
   >  displays the net/node number in hex. Handy!   
      
   Yes it does.   
      
   Mike   
      
    * SLMR 2.1a * I wish Noah had swatted those two mosquitoes.....   
   --- SBBSecho 3.28-Linux   
    * Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (1:2320/105)   
   SEEN-BY: 4/0 19/10 90/0 93/1 104/119 105/81 106/201 114/10 120/302   
   SEEN-BY: 120/616 128/187 129/14 305 153/757 7715 154/10 30 50 110   
   SEEN-BY: 154/700 218/700 840 220/30 90 221/1 6 360 226/18 30 44 50   
   SEEN-BY: 227/114 229/110 206 300 317 400 426 428 470 664 700 705 266/512   
   SEEN-BY: 280/464 291/111 292/854 301/1 320/219 322/757 335/364 341/66   
   SEEN-BY: 341/200 234 342/200 396/45 460/58 633/280 712/848 900/0 102   
   SEEN-BY: 900/106 902/0 19 26 905/0 2320/0 105 304 3634/12 5019/40   
   SEEN-BY: 5075/35   
   PATH: 2320/105 154/10 221/6 341/66 902/26 229/426