| |
VK2TV > WINPAC 31.05.09 01:00l 68 Lines 2496 Bytes #999 (0) @ WW
BID : 880327VK2TV
Read: GUEST
Subj: re longstanding problem
Path: IZ3LSV<IK2XDE<DB0RES<DK0WUE<7M3TJZ<F6CDD<F6BVP<VK2TV
Sent: 090530/2253Z @:VK2TV.#MNC.NSW.AUS.OC #:58674 [Kempsey, QF68JX] $:880327VK
From: VK2TV@VK2TV.#MNC.NSW.AUS.OC
To : WINPAC@WW
M1CUK wrote:-
> From : M1CUK
> To : WINPAC@WW
> Type/status : B$
> Date/time : 31-May 01:01
> BID (MID) : 8E0934M1CUK
> Message # : 320801
> Title : re longstanding problem
>
> Path: !GB7LDI!ZS0MEE!UA6ADV!I4UKI!IK6ZDE!IK2XDE!ON4HU!ON0BEL!GB7FCR!
>
> From: M1CUK@GB7FCR.#16.GBR.EU
> To : WINPAC@WW
>
>
> VK2TV wrote:-
>>
>> Hi Trev,
>>
>> The default in Winpack works for FBB bbs's. I've never had to touch the
>> headers in Winpack.
>
> HI,
>
> well to be honest I think Roger g4ide knew best on this one, its his
> advice in the helpfile that you NEED to set the columns up manually in
> winpack if your not using the fbb unproto beacons.
>
> and I am not on about headers in winpack, its the actual message columns
> that need to be set, not what I say what Roger g4ide who wrote the
> software in the 1st place says in his winpack help files.
>
> and Just because its worked for you everytime, dosent mean to say it
> will work for everyone else everytime. I have come across lots of users
> with the same problems as Bob has been seeing and setting the columns up
> always sorted the problems out and thats a fact.
Hi Trev,
Roger's help documents are unquestionably up there with the best of them;
if only other's could write help documents half as well!
When I said I used the default header column layout and it worked, I was
quite correct. What I neglected to add was that of course I checked to see
if they were right before adopting them. I didn't need to SET them, they
were already correct.
In this current situation of Bob's, which I am now also experiencing, I
truly believe Bob has changed nothing, as I have changed nothing on my
system. Having been in industrial servicing for 45 years, when I find two
geographically isolated systems that have worked perfectly for a
considerable length of time (years) and then they both start to misbehave
in an identical manner at about the same time, I logically look beyond
configuration errors.
Bob had a serious intrusion on his system last year. As I understand it,
the system was repaired (I'd have done format c) and, about this time
Winpack started playing up. My system is also now playing up. Given that
Bob uses telnet to get here, and telnet is basically an open door to a
smart bug, has my Winpack somehow been affected. I don't know, I'm just
trying to look at the bigger picture, and apply some logic.
Cheers ... Ray vk2tv
Read previous mail | Read next mail
| |
