🚀 go-pugleaf

In article <20111212.2244.269snz@cj4386.demon.co.uk>
           colin@cj4386.demon.co.uk "colin may" writes:

> In article <20111212.1451.258snz@cj4386.demon.co.uk>
>            colin@cj4386.demon.co.uk "colin may" writes:
> 
> > I am trying to change the base address of the com ports in KA9Q and
> > its variants. The problem is I need four characters for the hex address, 
> there
> > is only space for three. Is there anything I can do? Any help would be
> > appreciated.

[I replied]
> Not sure I understand the problem -- are you referring to the DIS
> front end to set this?  It seems that you might have a somewhat
> strange setup to require a 4-digit base address; the entry in my
> autoexec.net is:
> 
>   attach asy 0x3f8 4 ppp sl0 4096 576 115200
> 
> Can you edit this file and manually enter the address you need?  It's
> a while since I had to configure anything in this area but have a
> vague recollection that the base addresses are
> 
>   0x3f8 - com1
>   0x2f8 - com2
>   0x3e8 - com3
>   0x2e8 - com4
> 
> What COM port are you trying to configure?
> Pete
> ------------------
> High Pete
> 
> I am trying to send the output to a com port card with address 0xac00. I have
> put it in the autoexec.net file. When I run up the program it takes out one of
> the zeros at the end.
> 
> Colin

Hi Colin,

0xac00 is certainly a non-standard address.  Having taken a very brief 
glance at the KA9Q (GremNOS) source I didn't spot any obvious reason 
for this truncation -- if that is what it is.  Whereabouts are you 
seeing 0xac0 reported?

The only thing I spotted that *might* be causing the problem is that 
the code tries (rightly or wrongly) to parse this value into an 'int', 
i.e. a signed 16 bit quantity, and 0xac00 would be negative.  Whether 
this would have a dtrimental effect I don't know.

Maybe someone else can help, but I'll try to take a deeper look this 
evening.

Pete
-- 
   "We have not inherited the earth from our ancestors,
    we have borrowed it from our descendants."