| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Binkleyterm 2.60 XR6 DOS |
David Nyquist wrote in a message to Craig Ford: DN> There's the reason. I used to run OS/2 and you don't need a DN> fossil. Plus the OS/2 version of Binkley Xr6 is more stable. But DN> I don't think there are enough beta testers to test out the DOS DN> version of XR6. That's why I'm probably getting this Lost Carrier DN> message. It's strange though it never happened in the XR5 DOS DN> version. DN> Cheers, DN> David Nyquist PMFJI, but I have been following this thread and let me add my experiences. I'll set the conditions: I use Bink OS2 XR6 and my "BOSS" uses OS2 XR5. ....When I started using XR6, no problem on the incoming mail or files. ....But when I sent mail...LOST CARRIER showed up in the log and once or twice ....had EMSI password problems. My solution, and I'm still in a testing mode.... ....was to go back to the default transmit protocol string (HYD,JAN,ZAP,ZMO). ....I also commented out the "NoHydra" and the "NoJanus" verbs. I found if I ran with ZAP,HYD,ZMO it gave me "Lost Carrier". I put ZAP,HYD,JAN,ZMO and it still gave "Lost Carrier". I currently run with HYD,JAN,ZAP,ZMO (default) and that has solved the lost carrier problem. YMMV, but that string is sent during the EMSI handshake and thats why I started troubleshooting there. Like I said above I'm still testing and I'd like to send some 5k to 10k packets for a more complete check. Hope this helps. TTYL, Richard --- timEd/2 1.10.y2k+* Origin: DPSystem:4285 Tucson AZ 520.290.8418 Courier V.34+ (1:300/105) SEEN-BY: 396/1 632/0 371 633/260 267 270 284 371 634/397 635/444 506 728 SEEN-BY: 639/252 670/218 @PATH: 300/105 603 396/1 633/260 635/506 728 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.