I0OJJ  > OBCM     19.11.25 20:00l 43 Lines 1447 Bytes #200 (1) @ WW
BID : JBZI0OJJ_003
Subj: Re^6: Notes for DC6AP
Path: ED1ZAC<ED1ZAC<LU4ECL<VK2RZ<IR0AAB<I0OJJ
Sent: 251119/2044z @:I0OJJ.ITA.EU [Rome] obcm1.08-11-2-gbfe9 LT:001
From: I0OJJ @ I0OJJ.ITA.EU (Gustavo)
To:   OBCM @ WW
X-Info: Sent with login password

From: DC6AP @ DB0APK.#SLH.DEU.EU (Andreas)
To:   OBCM @ WW
X-Info: Sent with login password
>Right now, only some output of "check", "l", and "a" should be colored
>if messages.<language>.ans is there. Did you restart OpenBCM to see if it's a
>caching issue?

I'm using V1.08-11-2-gbfe9 Linux and it is running steady rock here;
last source download was on 22 Sept 2025.

Definitively, taking the above running version and changing the 1.9.0
executable and new supplied message files, it does not function at all. 
 
>Another question! What is these "bct" or bcm connect program and where can I
>can that?

It is a simple BayCom terminal based with ncurses you may find in
German sites.

>And yes, it would be interesting to see whether you have the same issue with
>a "virgin" installation. It's possible that the 1.08 version I forked is
>slightly different from the 1.08 you were using.

Starting from scratch I obtained a *not usable system* in particular:
the mail.imp and 7p process from crontab produce a SIGSEGV and abort
the bcm; in some occasion reappear the famous munmap_chunk(): invalid
pointer and abort the bcm. 

If you started this actual mods before the 22 Sept 2025 it is probable
your suspect above.

But if I started from scratch the references are pertinent only at
the new archives 1.9.0 ...

>73'
>Andreas (DC6AP)

73. gustavo i0ojj
 



Read previous mail | Read next mail