In article <003901be86bb$fc8f2b00$5333883e@ray>, Raymond Jones
<rayjones@...> writes
From: "Raymond Jones" <rayjones@...>
Hello Roger,
I don't know whether the following problem is unavoidable, or whether I am
doing something which is not intended.
Firstly, with a 486DX2/66, 12 Meg, W95, UI-View 071b (yes, I do now have the
later upgrade!) BPQ, NODE2BAY and Baycom modem, I can successfully run
UI-View on its own, without Winpack. I presume that is intended.
If I start Winpack, all is fine. If I then close down Winpack, the UI-View
monitoring ceases. Monitoring can be re-started by either re-loading Winpack
or shutting down and re-loading UI-View.
That's because of the way BPQ works. You can tell it what monitored
frames you want it to decode by passing it a port mask (e.g. you can say
"provide decoded monitored frames from ports 1, 3, 4"), but the same
mask applies to all host mode applications. At the moment, when WinPack
starts up, it sets the port mask to whatever you have input using the
virtual TNC MASK command (I think the default is ports 1 to 8) but it
sets the mask to 0 when it closes, so UI-View stops getting monitored
frames.
What I really need to do is to stop using BPQ's internal mask, and mask
the ports myself in WinPack, but that will have to wait for the next
WinPack update.
Secondly, I have my normal packet machine, a P133, 48 Meg, W95 and the
dreaded Flexnet. UI-View is in DDE mode of course, and so Winpack is loaded
for UI-View to run. If I unload Winpack, and then re-load it, then UI-View
does not recommence monitoring.
If you close WinPack, you're breaking the DDE link. In the next update,
I'll force UI-View to close at that point, because once you've broken
the link, it won't re-establish itself.
--
Roger Barker, G4IDE roger@...
Boston, UK
