| |
F5PYF > BPQ 11.03.96 07:40l 39 Lines 1353 Bytes #-11196 (0) @ EU
BID : 680065F5PYF
Read: DH9MEC DG0EL GUEST
Subj: BPQ KISS AND WIN95 PROBLEMS
Path: DB0AAB<DB0PV<DB0WGS<OE3XBS<S50BOX<S50BBS<IV3LAV<IV3AVQ<IW3FPP<IW3GAE<
I3XTY<IW3FHV<IW3GRX<IW1BBL<I1ICZ<I1XZZ<IK1MDL<IK1MVX<TK5KP<F6KDJ<
F5KBJ
Sent: 960308/1208Z @:F5KBJ.FPCA.FRA.EU #:18221 [La Seyne] FBB5.15c $:680065F5PY
From: F5PYF@F5KBJ.FPCA.FRA.EU
To : BPQ@EU
Hello All BPQ Users,
I have some problems to run BPQ under Win95 with my TNC (KAM) which is in
KISS mode, could you please help me ?
As said in the WINBPQ doc, the files BPQCODE.386 and BPQDLL.DLL have been
moved in the \WINDOWS\SYSTEM directory and BPQCODE is loaded BEFORE to run
Win95 (AUTOEXEC.BAT).
I have made a new HARDWARE PROFILE to disable the KISS COM1 serial port
which is used by the TNC, so, this serial COM1 port isn't recognised by
Win95 otherwise Win95 crashes consecutively.
When i run Win95, i can see the BPQ message before the first Win95 main
screen.
Then, i can run (in a win95 virtual Dos window) the PAC4 program. All
seems to work normally, the node access for instance, but, when i connect
somebody, there are too many retries ...
If i run BPQCODE and PAC4 with the same TNC in KISS mode, the same PC
(Toshiba T2150 laptop) and the same configutation under DOS (not Win95), i
do not have any retry !
In fact, under Win95, the virtual BPQ node seems to become "deafer" than
under DOS. But, all the frames sent by BPQ are still decoded by other TNC
as well in DOS mode than under the Win95 profile.
All suggestions about this retry problem will be welcome here.
Thanks in advance and best regards,
73 - Olivier, F5PYF @ F5KBJ (TOULON)
[WinPack + BPQ] le 08 Mar 96 a 12:58
Read previous mail | Read next mail
| |
