#WHAP & ALTERNATE NODES
23 messages in this thread
Does WHAP! expect to get a CIS node's attention by issuing a CTRL-C? How does
it allow TYMENET (and other network users) to access CIS. My local CIS node
(Dayton, OH) wants a Host name of Compuserve before asking for the user ID. A
ctrl-C is useless here. If WHAP! cannot be configures then this is a major bug
in the software and will limit potential users.
When I get WHAP to dail it seems to hang at the user ID and CIS times out and
disconnects the line.
OK. CTRL-C works at my node (Dumb Greg!). Whap trys to log on and read the
message base (new mssages). They scroll ok on the screen and if a QSN, are
stored as garbage when accessed. RTNs are probably the same, but I keep getting
it to lock up during the first message.
I have Easyplex notify set,and command mode for prompts in all three forums and
CIS. I have the messages sent to ram: for now. I have a lot of stuff running in
the backgroundPCLI III, GOMF2.2, CONMAN. I am running a 68010 CPU. When Whap
locks up, it fails to respond to the ABORT and HANGUP gadgets. The modem stays
on-line with no data being send or recieved. I know CIS is awfully slow tonite,
but the gadgets should have responded.
This happens whether 3 wire or 7 wire handshake is used. I have seen the
Access! baud rate problem as well (will set preferences, but I use both 2400 &
1200 baud as the Dayton CIS node has a bad 2400 modem which will connect but
not let you log in (part of problem leading me to believe WHAP couldn't log in
at my Dayton node -see first message)).
Whap seems to be navigating ok, just problems with saving the messages.
-Greg
Greg,
You said "command mode for prompts", does that mean that your permanent
CompuServe profile has BRIEF set to YES?
In background I run with PopCLI III, GOMF 2.2, Conman, WShell, SnipIt and
Co-Pilot. I don't use the 68010.
Check that BRIEF is set to YES, delete your Txxxx file and have it
initialize again.
Best,
-jcs-
Jim,
Whap autodial assumes that a modem needs a CR to dial. Unfortunately, my
modem (a DEC Scholar) requires a plain jane ! to dial. No CR. Have a way to fix
that for me and other DEC modem users? Regards, Paul /end
Jim,
When Whap issues the GO AMIGATECH command, it waits EXACTLY 30 sec. after the
"One memHHoment please…" message before giving up and heading off to the next
Forum. This was a bit frustrating. Any way to change that? It is repeatable.
Paul
Paul,
The system has been extremely slow the last 3 nites and I understand there
is a good news/bad news answer to that problem. The good news is that all of
the system problems will improve dramatically. The bad news is that it won't
take place until mid-week.
Yes, Whap! has a 30 second time-out. We thought that sufficient. Some
of the beta testers thought that too long. With the system slowness of the
last few nights, it is not nearly long enough.
There will be a new distributable version available this evening or
tomorrow. This will include the fix for the confusion caused by files in the
Libraries that start with LIBn. It also includes much longer timeout periods.
In some cases, depending where you are and what you are doing, up to 4 times
longer. That should do the trick.
Other changes include MUCH better handling of the Whap! initialization.
It takes much less time (even though in theory it runs only once). The first
time user will no long have to manually go to Default and set Top Page, Brief,
and EasyPlex. Also, a look at the QSN code showed a problem.
I had full intention of uploading it tonight (1 full system ARC file for
people just getting it and 1 Whap! only arc for people who already have 1.0d).
However, with the system response the way it is, I was getting something like
70 bps at 2400. I gave up. I was on the system a few minutes ago and things
appeared to be much better so I may try again in a few minutes.
Best,
-jcs-
Okay Jim. Things zipped along just fine when I logged in at 8:00 am. I am
looking forward to the new version. By the way, any solution to my autodial
problem? Not all modems use a CR to dial the number. My modem (DEC Scholar)
uses a !.
Paul
Paul,
That's a tough one.
There's no way to autodial CIS without sending a CR but you might be able
to do it by placing the telephone dialing string in the INIT modem string since
this will be sent out every time whap attempts to dial. You will have to leave
the telephone number blank and the baud set and number selected. I think that
just might work. You will be in manual dial mode and when you see that you're
connected, you can press ok on the requester.
Best,
-jcs-
Jim,
I got autodial to work! Here's how with a DEC Scholar modem:
883-5551! = =
The "= =" adds a 30 second delay for acquiring a second carrier. The delay puts
off receipt of your CR at my modem, just long enough for the "Attached" message
to appear when the CIS carrier is acquired. Once the "Attached" message is
read, Whap! sends a ^C and the rest of the login information.
So I essentially trick the modem into thinking its waiting for a second carrier
from a linked service.
No problems with 1.1D.
Paul
Paul,
Great!
Best,
-jcs-
A look at the QSN code showed a problem? Is that the one I've been nagging
about? 🙂
Don't forget the 3 things that were left out of the docs.
1) Manually assign your TOP PAGE to CIS-1 or MAIN.
2) Set Eayplex to NOTIFY ONLY.
3) Set CIS to command mode.
Henry, I've done that. One area of ambiguity is where do you set the forum
mode? you can set it to COMMAND (expert) either globally at GO DEFAULTS or
within each forum. My first attempt was only in the forums. Maybe that's why
EasyPLex still gave me the MORE ! prompt. I've found out the hard way that it
is better to do it in DEFAULTS.
Yes, even when you have your defaults set to EXPERT globally, that can be
overridden in each forum. Check that out – it will be documented better and I
do think Whap! should check for it too…
Gregory,
To use Whap! via TymNet, preface the phone number in with an @ (like
@555-1212) and it will go throught the TymNet logon sequence. And no, that's
also not in the current doc.
All CompuServe nodes respond to a ^C. If yours doesn't there is a
problem with the node and you should report it to CompuServe. However, should
you get the CONNECT message from Whap! and the node does not respond to the ^C,
click in the window and manually hit a carriage return. Whap! will take over
from there. Again, if the node is not responding to the ^C, it's sick and
should be reported as such.
Whap currently does not have TeleNet support. If someone would like to
give me the logon sequence for TeleNet I will include it in the registered
version. Same goes for INet, DataPac, and any others you can think of.
Best,
-jcs-
Jim, at 2400 baud, most of the CompuServe modems want a few seconds to
determine if your using an MNP or non-MNP modem and then enable the transfer of
packets. My auto-login file for OnLine! uses a five second delay before
sending CTL-C. Have never had a problem with this setting.
Just something to keep in mind.
Ted
Ted,
That used to be the case. Several months ago CompuServe changed the
modems at the local node end. The delay is no longer needed.
Best,
-jcs-
Sorry about that Jim, CompuServe will not get the CTL-C unless you wait at
least two to three seconds after connect. I use five seconds just to be sure.
It was about the same amount of time before they switched to the new modems.
Ted
Don't know about you, Ted, but my node responds to a ^C within 1 second of
connect. Maybe CIS is still in the process of replacing all the modems and
haven't gotten to your area yet.
Nope. They did my modem about 4 months ago. That's when I had the problems
with the CTS modem I was using.e'.hrPswitched to a Supra modem, I get very
reliable and clean data. There is a specific and very consistant delay after
connect before you can talk to CIS. There always was, and is today. Perhaps
it's a function of the network itself, as all comm lines in this area have to
compete with NYC.
Ted
Ted,
Ok, that was a guess. Like Steve, I don't have the 'problem' if it is
indeed a problem.
Best,
-jcs-
I've been using 2400 baud on an MNP compatible node for a LONG time now and I
usually type the Ctrl-C as soon as I see the CONNECT 2400 message from the
modem. I never have to type it twice…
–>Steve Bennett
Interesting. I guess it's just the way my node works. No problems with data,
so not much point in worring about it.
Ted