| |
VK2TV > WINPAC 01.06.09 03:40l 71 Lines 2981 Bytes #999 (0) @ WW
BID : 660329VK2TV
Read: GUEST
Subj: Re: Long problem (M0PZT)
Path: IZ3LSV<IK2XDE<DB0RES<DK0WUE<7M3TJZ<F6CDD<F6BVP<VK2TV
Sent: 090601/0231Z @:VK2TV.#MNC.NSW.AUS.OC #:58736 [Kempsey, QF68JX] $:660329VK
From: VK2TV@VK2TV.#MNC.NSW.AUS.OC
To : WINPAC@WW
G6KUI wrote:-
> From : G6KUI
> To : WINPAC@WW
> Type/status : B$
> Date/time : 01-Jun 00:00
> BID (MID) : 27899_G6KUI
> Message # : 320852
> Title : Re: Long problem (M0PZT)
>
> Path: !GB7LDI!ZL2BAU!GB7MAX!GB7DBY!GB7DBY!
>
>
> Hi,
> Glad to see that Charlie finally made the connection to the BBS at VK2TV.
> Did you go via a list of VE stations or did you find a different way ?
> My link was supprisingly fast, fast enough to make useful use of the
> connection. I listed and read many bulletins and also had a YAPP download
> session.
>
> Again it is so supprising that so many WINPACK users havn't read and
> followed the instructions from G4IDE.
>
> Other means of solving the problem if those outlined by Trev do not work
> include Compressed Downloading where the contents are of no significance.
>
> Another would be for Ray to put VK6BE in FBB as a BBS.
> After many years, I got a download problem between my BBS and my PMS.
> Changing the designation of my PMS in FBB to "BBS" solved that problem.
> The problem just appeared out of the blue, NOTHING, absolutely NOTHING
> had been changed on either the PMS or BBS. There had been no alterations
> of any sort on either PC. I even swapped the PMS PC, to another spare PC
> with pms installed that had worked perfectly years previously.
> Therefore it was FBB that had somehow took a dislike to my PMS setup.
> It does happen - probably a bug in FBB.
>
> On the subject of Telnet, where Ray took exception to my comments on the
> suitability of Telnet, I only suggested to use an alternative. Both Ray
> and I know that AXIP is much more suitable as we both use it on a daily
> basis and it usually performs flawlessly unlike telnet ! ( YAPP works ).
>
> 73, Pete G6KUI
Hi Pete,
My apology for being a bit crabby with you.
I did read the help documentation for Winpack, and followed the
instructions contain therein. Suddenly my system is doing what Bob's
system is doing, after working fine for a number of years, and I am shown
in FBB as a BBS, naturally :-) I don't use compressed upload/download.
I'm not sure about it being an FBB problem, but I'm can't testify that it
isn't. I am using a test version from F6BVP. However, I rolled back to the
previous version, the one I'd been using for about 18 months, and got the
same problem. You may be heading in the right direction with the
Winpack/FBB interaction theory but I keep coming back to the same question
of why would it suddenly happen on two systems? Still, stranger things
have happened. Then I reflect back a few years to a Windoze update that
affected Winpack so that a single character (such as B) wouldn't work from
Winpack. Double characters - RM - were fine or <spaceB> was fine.
Today is the first day in five that I'll have half a chance of
investigating the situation a bit more fully. Maybe I'll find something,
maybe I won't.
Cheers ... Ray vk2tv
Read previous mail | Read next mail
| |
