Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
- Bpq32
- Messages
Search
Re: OT: Digipoint Authors (RETRO fun)
The documentation is good, and the setup is logical.? If you ever need help I am happy to do help.? No, I gave up on 32 bit after getting DOSFBB with Dos BPQ.? It works very well.? Super stable and fast.? Now have DesqView in DOS for a big desktop and multitasking.? That is also nice and stable. Digipoint is really neat. ?60,000 lines of code for just the BBS. Thanks, Chris Maness -Sent from my iPhone On Wed, Apr 16, 2025 at 5:42?PM Chris Lance WW2BSA via <Ww2bsa=[email protected]> wrote:
|
Re: OT: Digipoint Authors (RETRO fun)
¿ªÔÆÌåÓýHi Chris, did you ever come across a 32 bit windows version of FBB? I found LinFBB but I'm not a Linux guy. In any case? I'm jealous of you: I find configuring FBB highly complex and admire anybody proficient it.?73 de Chris ww2bsa -------- Original message -------- From: "Chris Maness KQ6UP via groups.io" <christopher.maness@...> Date: 4/16/25 7:09 PM (GMT-05:00) To: BPQ Packet Switch <[email protected]> Subject: [bpq32] OT: Digipoint Authors (RETRO fun) on to Atari TOS :D I have been playing with DPBOX for a couple of years now, and I thought I would give digipoint (t's predecessor on Atari) a spin.? It is really an awesome piece of code.? It kind of makes me sad to see this very cool and powerful BBS software go the way of the do-do bird. At least DOSFBB is Y2K compliant (at least 7.00i is).? I have it running, but I am not even going to mess with satellite tracking as it thinks it is in November 1995.? I am not certain this has to do with the emulator -- I am still learning it. Anyhow, to my point.? I would like to patch this thing for Y2K compliance, and I need the source. Does anyone know how to get in touch with: Joachim Schurig, DL8HBS or Mark Wahl, DL4YBG I figure I would have the best luck finding info here. -73 de Chris Maness -- Thanks, Chris Maness |
OT: Digipoint Authors (RETRO fun)
Now that I have DOSFBB running nicely with Dos BPQ4.09, I have moved
on to Atari TOS :D I have been playing with DPBOX for a couple of years now, and I thought I would give digipoint (t's predecessor on Atari) a spin. It is really an awesome piece of code. It kind of makes me sad to see this very cool and powerful BBS software go the way of the do-do bird. At least DOSFBB is Y2K compliant (at least 7.00i is). I have it running, but I am not even going to mess with satellite tracking as it thinks it is in November 1995. I am not certain this has to do with the emulator -- I am still learning it. Anyhow, to my point. I would like to patch this thing for Y2K compliance, and I need the source. Does anyone know how to get in touch with: Joachim Schurig, DL8HBS or Mark Wahl, DL4YBG I figure I would have the best luck finding info here. -73 de Chris Maness -- Thanks, Chris Maness |
Re: LinBPQ says: Error - Port in use (Session Attached
Some drivers need a longer wait, So i would try to place a PAUSE 30 or PAUSE 60 after the ELSE. I notice that its not consistent on drivers, so drivers like VARA dont need those, but if you use WinRPR, they dont seem to fully release the port for around 30 seconds. I would also recommend you put IDLETIME 60 in there before each ATTACH. This is a failsafe if the modem gets LOCKED and does nothing, it will break out of that cycle in 1 minute. Maybe John has better suggestions, but these are general ones I employ across a wide range of different modem types so I think they'd be a good practice to try. 73 |
LinBPQ says: Error - Port in use (Session Attached
Hi all,
I have been experimenting with a newly-added KAM port (#6). It looks to me that after an outgoing call was tried in G-tor mode (either from QtTermTCP or from within a forwarding script) the modem remains in some state where no other command is accepted, such as bellow: Connected to TelnetServer att 6 LPTP:YU7BPQ} Ok c <call> *** Failure with <call> gtor <call> KAM} $ Input ignored gtor KAM} gtor <call> KAM} $ Input ignored pactor KAM} c <call> tor KAM} Disconnected ... or when a fwd script session fails, it does not return to scan frequencies but remains on the last one used. Seems that it keeps the port busy: Connected to TelnetServer att 6 LPTP:YU7BPQ} Error - Port in use (Session Attached Disconnected Connected to TelnetServer att 6 LPTP:YU7BPQ} Error - Port in use (Session Attached Disconnected Connected to TelnetServer att 6 LPTP:YU7BPQ} Error - Port in use (Session Attached A sample fwd script includes this: ATTACH 6 RADIO 14.10230 USB #\TRX F 14102.30 #\TRX F 7044 PAUSE 2 #MYLEVEL 1 MSGTYPES PTRB5000 C <call> ELSE ATTACH 6 RADIO 14.10230 USB #\TRX F 14102.30 #\TRX F 7044 PAUSE 2 #MYLEVEL 1 MSGTYPES PTRB5000 GTOR <call> Any idea what can be wrong? Misko YT7MPB |
IDMSG BTMSG
Hi Everyone
?
? Can someone please advise, running linbpq on Ubuntu 24.2
??
? What is the max chars used for IDMSG and BTMSG, and is the any chars I must not use
?
? and last, when I update any of these message whey don't they change for the user, even after a restart on BPQ service
?
? Thanks in advance Alan |
Re: Current ("new") Rig Control and associated ports
Hi Rich, At one time I had 3 interlocked ports with no rig control in place at all. It was because I was on one band on one dial frequency 7x24. When I added rig control, I understood at the time that the interlock and radio statements were equivalent - most likely due to John clarifying it in other discussions going on in that time frame - so I just left the interlock statements in place in the ports. Sadly a year went by, and I forgot about those statements being equivalent. 73, Lee K5DAT On Tue, Apr 15, 2025 at 3:24?PM Rich Sahlender via <wa3wlh=[email protected]> wrote: Hi Lee, |
Re: Current ("new") Rig Control and associated ports
Hi Lee,
It was curious to learn that your use of the new / current method worked for you WITHOUT a "RADIO n" reference in a port config section. I assume it was required. With John's clarification that RADIO and INTERLOCK do the same thing it now makes sense. 73 de Rich WA3WLH |
Re: Current ("new") Rig Control and associated ports
Thank-you very much. That sounds familiar, and sure enough, it has been stated previously in this group. I should have done a search for it. 73, Lee On Tue, Apr 15, 2025 at 2:39?PM John G8BPQ via <john.wiseman=[email protected]> wrote:
|
Re: Current ("new") Rig Control and associated ports
¿ªÔÆÌåÓýRADIO and INTERLOCK do the same thing. With the new method of defining rigcontrol it seemed sensible to use RADIO to link the radio definition with the ports but INTERLOCK still works for compatibility with old configs.73, John On 15/04/2025 17:53, Lee Bengston via
groups.io wrote:
|
Re: Current ("new") Rig Control and associated ports
I thought the whole point of INTERLOCK was that you want them to lock each other out, i.e. as soon as one port is in use with its specific modem or TNC, other ports that share the same radio are locked out so that there will be no conflict. 73, Lee K5DAT On Tue, Apr 15, 2025 at 1:57?PM Mark Taylor via <mtaylor=[email protected]> wrote:
|
Current ("new") Rig Control and associated ports
Hi All,
?
I've been using the new/current rig control method ever since adding rig control
to linbpq a little over a year ago. I only have one HF radio for now, and I've never
needed?a "RADIO 1" statement in any of the ports that are associated with the
radio. Given there are multiple ports using the same radio, I do have INTERLOCK=1
in each port.
?
If I were to add a second radio and therefore a RADIO 2 section in the rig control
area of the main config, would INTERLOCK=2 in each associated port be sufficient
to "point" new ports to radio #2, or would I need to add RADIO 1 and RADIO 2
statements to each applicable port?
?
Currently I can't tell if the interlock statement is taking care of associating the
ports to the radio, or if I am getting away with no RADIO 1 statement because
it's implied due to only having one radio.
?
Thanks,
Lee K5DAT |
Re: SESSIONTIMELIMIT
¿ªÔÆÌåÓýSorry, ADDR must come first in the CONFIG section.73, John On 15/04/2025 16:06, N3MEL - Glenn via
groups.io wrote:
|
Re: SESSIONTIMELIMIT
Hi Glenn,
Your config looks like a mix of the old RIGCONTROL style with the newer RADIO style. Per choose one OR the other method but not both. If you prefer the older RIGCONTROL method it may be as simple as removing the "RADIO 1" from within your port definition. Personally I would also move the BW500 just before or after the SESSIONTIMELIMIT rather than after the **** terminator for the RIGCONTROL section. To use the newer method remove the RIGCONTROL statement and create a new RADIO 1 block outside of the port definition. Move all of the rig timing and scan parameters into the new RADIO 1 block and terminate this new block with "****". The end result should be a global RADIO 1 block that is referenced within the config section of your VARA port with the RADIO 1 that you already have there. I hope that helps... 73 de Rich WA3WLH |
Re: SESSIONTIMELIMIT
Here it is currently John.
?
PORT
?PORTNUM=5 ?ID=VARA HF(20/40) & 80 ?DRIVER=VARAHF ?INTERLOCK=1 ? ?CONFIG
?SESSIONTIMELIMIT 5 ?ADDR 192.168.86.34 ?8351 PTT CAT PATH ?
?RIGCONTROL ?Remote 192.168.86.34:8500 ICOM IC7300 94
? ?RADIO 1 ? ?0:00 ?8,7.1032,USB,F2,D ?;4,14.1065,USB,F2,D ?02:00 ?5,3.596,USB,F2,D ?13:00 ?10,7.1032,USB,F2,D ?;4,14.1065,USB,F2,D ?
****
?BW500 ?ENDPORT
?
It can't be working, below is the the very first session after make the latest change to the Config. I finally stopped it myself with the Stopport command.
?
2025-04-15 12:38:19 ? ?Connecting to KN4LQN-2... 1/15
2025-04-15 12:38:23 ? ?Connecting to KN4LQN-2... 2/15 2025-04-15 12:38:42 ? ?Connected to KN4LQN-2 ?VARA HF v4.8.7 2025-04-15 12:52:16 ? ?8351 TCP Port Closed unexpectedly 2025-04-15 12:52:22 ? ?KN4LQN-2 Average S/N: -15.9 dB 2025-04-15 12:52:22 ? ?Disconnected ? ? ?TX: 1434 Bytes (Max: 88 bps) ? RX: 41 Bytes (Max: 18 bps) ? Session Time: 13:40 ?
?
|
to navigate to use esc to dismiss