OpenBCM V1.08-5-g2f4a (Linux)

Packet Radio Mailbox

IZ3LSV

[San Dona' di P. JN]

 Login: GUEST





  
VK6BE  > WINPAC   28.05.09 05:30l 102 Lines 4605 Bytes #999 (0) @ WW
BID : 960029VK6BE
Read: GUEST
Subj: Re: Longstanding problem
Path: IZ3LSV<IK2XDE<DB0RES<ON0AR<GB7YKS<VK2DOT<VK5ZAR<VK2TV
Sent: 090528/0308Z @:VK2TV.#MNC.NSW.AUS.OC #:58480 [Kempsey, QF68JX] $:960029VK
From: VK6BE@VK2TV.#MNC.NSW.AUS.OC
To  : WINPAC@WW


OK Charlie, so your bulletin this time had no text after I made some of
the alterations suggested. How do you explain that? The entire message
came down as soon as I connected so I was able to read what you said but
on the normal download only headers and signature and NO text.. I now have
to reverse the changes I made.

The changes I have made in response to some of the suggestions have only
made matters worse it seems. Before I only had a problem when Ray VK2TV
sent a bull. Now you have all caught the disease!! How do you explain
that?

I have always used a chevron as a BBS prompt and others of my acquaintance
here have always done the same. That is not the problem, so let us
dispense with that idea. It has worked for me and for others in VK since
time immemorial so why not now? Maybe you do some things differently in
the UK and elsewhere.The chevron has worked OK here.I didn't download
Andy's bull so can't answer your question as to whether his text came
down. I was not interested in light pens.

I can assure you there are no "daft errors" in the .ini file. If I am
making "daft errors" then so are Dave VK2AWZ and Ray VK2TV whose ini files
I have tried. I still have Ray's in place with Dave's on the laptop.Those
people  are not having problems so forget the "daft errors".There is no
point in publishing the .ini file I am using since it works OK for at
least two others whose files I have changed to as a test. No result. The
.ini file is OK.

The only constants in all these tests and trials are the BBS, which is
beyond reproach as far as I can see, and my computer. On the  balance of
things it seems that my computer has a problem and that is what I have to
work on. After all noone  has the problem except me which seems to me to
eliminate as a source of trouble the BBS, the other users, Winpack itself
- after all it worked fine for me for at least  12  years and the
difficulties have only surfaced recently.

You can forget lack of skill or of knowledge of the system on my part also
Charlie. I have used Winpack from the time I gave away DOS as an O/S and
that is a long long time ago, almost from the first version of Winpack.I
am not exactly a beginner. The only help I have asked for in setting up is
from Ray to get BBS details of address and other necessary information
which I did not have because of the change to TELNET from a local BBS.That
is the only change made here except for a different computer of course.
Computers have advanced considerably from 12 years or so ago.

Cheers, and thanks for your suggestions Charlie.
Bob VK6BE.

QUOTE
>Interesting - I'll take your word for it that there are no daft errors as 
>you won't tell us it's contents other than "it used to work".  That INI 
>file contains your Personal+BBS settings and as it stands seems to be 
>likely cause of your problem ;)

The other option is that something has changed at the BBS end, but if the 
other users are managing (with a similar INI) then we're back to your 
config.

> (1) The BBS prompt is a chevron and has been for at least 12 years.
> (2) The BBS prompt is a chevron and has been for at least 12 years.

So the BBS prompt consists entirely of one character ?  That's a bit 
unusual as a BBS usually has it's callsign or some letters before it:

ie: M0PZT de VK0ZZZ BBS (A,B,Help,L,S,X) >

or something along those lines.  Looking at my old WinPack config, I NEVER

include the chevron in the Prompt setting, just some text that ONLY
appears 
in the actual prompt.  A prompt like my example above is actually a good 
example of a prompt because there is more to specify and that sort of text

doesn't appear in casual text (like Ray's callsign!).

A single chevron for a BBS prompb
t would be a bit careless on the sysop's 
part as all sorts of fun could be had by inserting the odd lone > into 
messages just to wind you up, Bob!  (EBT take note).

> (3) Ray has sent test messages and they have no text except for an
> isolated one. 

Right - just out of interest, look for GM7HUD's recent bulletin to TECH@WW

about Lightpens - it has a single chevron in it.  Does that message 
download correctly... ?

If it does - then I suspect that you need to be more specific about your 
BBS Prompt setting.  I would quote my own BBS prompt but it's possible
that 
I'd cause all sorts of grief for GM7HUD as there's no telling what string 
WinPack is set to look for ;)

I can see KEMPC:VK2TV-14 but it won't connect and I can't see a route to 
the actual BBS from the UK XRouter network so cannot test your BBS.

END OF QUOTE


Read previous mail | Read next mail


 25.09.2024 15:25:16lGo back Go up