#AmiTCP Error? Help!
40 messages in this thread
I don't know what the heck I'm doing anyway, but I'm having a problem with
AmiTCP, or perhaps PPP.
I installed PPP 1.30, per the instructions in its guide file. Then I installed
AmiTCP, following the instructions in the PPP guide file as best I could,
though there were some settings that weren't mentioned, and I just left them in
their defaults, like the user ID of the user being 100 and so on.
Then I made the changes in some AmiTCP files as per the instructions in the PPP
guide file.
Then I copied the dialscript that Steve Ahlstrom posted and put it in a file
called PPPDialScript, and I put my local access number in the appropriate spot.
Then I put the DIALSCRIPT entry in ppp0.config file in env:sana2.
Then I tried to run the startnet script, and I got the following error:
S2_ONLINE: Resource allocation failure
online failed returncode 10
Then I tried the script in Steve Pietrowicz's help file, and got the exact
same error.
When I run the script, I get the following output:
TIMEOUT 1500
SEND "ATDT 712-0479"
WAIT "CONNECT"
A
NO CARRIER
'NO CARRIER' received
except that the last line is in two different colors.
I have no idea what that means, and most of the AmiTCP documentation is greek
to me, though I'm trying to figure it out. Does anyone have any idea what I'm
doing wrong?
I have an A3000 with OS 3.1 and a 40MHz WarpEngine w/ 16MB of fast RAM, and I
used TCP4.LHA and PPP130.LHA from the libs here.
I'd really appreciate any help. TIA
Mr. Zombie
>> SEND "ATDT 712-0479"<<
I am not sure Paul, but shouldn't you remove the space and the dash?
Bart Van Bockstaele at 100574.2352@compuserve.com
… On AutoPilot and Amiga all the way from Belgium …
Bart-
I removed the dash, but that's not what did it, I think. I'm not even sure
what I did, but I seem to have to run different things in a jumbled order to
get things working.
Also, Web navigation is S..L..O…..O……..O………W………….W!
Mr. Zombie
Paul, See here what I use to dial. For me it works about *every* time. Maybe
you can do something with it?
ECHO ON
TIMEOUT 2500
REDIAL "BUSY"
SEND "ATZ"
WAIT "OK"
SEND "AT&C1"
WAIT "OK"
SEND "AT&D2"
WAIT "OK"
SEND "ATH1"
WAIT "OK"
SEND "ATDPphonenumber"
WAIT "LAPM"
SEND ""
WAIT "e:"
SEND "CIS"
WAIT "D:"
SEND "usernumber/GO:PPP89"
WAIT "ord:"
SEND "userpassword"
WAIT "please…"
DELAY 50
ECHO OFF
I do only three things:
1) I open a shell and type “startnet'' followed by <return>
2) When all goes well -it nearly always does- I start Mosaic.
3) When I am finished, I type “stopnet'' in the shell followed by <return>.
And yes, just look at my previous message. I am beginning to love snailmail
when compared to “surfing'' the net. It is just horrible!
Bart Van Bockstaele at 100574.2352@compuserve.com
… On AutoPilot and Amiga all the way from Belgium …
For some reason it's the online line in startnet that's killing things and
giving that error.
Mr. Zombie
>>For some reason it's the online line in startnet that's killing things and
giving that error.<<
My line looks like: AmiTCP:bin/online ppp0
How does yours?
Bart Van Bockstaele at 100574.2352@compuserve.com
… On AutoPilot and Amiga all the way from Belgium …
I tried that, as well as
online pp0
online devs:networks/ppp.device 0
AmiTCP:bin/online devs:networks/ppp.device 0
AmiTCP:bin/online ppp0
so I don't know what the problem is. Could it be that the unregistered version
of PPP randomly fails as a prompt to register?
Mr. Zombie
Paul,
From what I read in your messages: could it be that your modem has trouble
going off hook? In that case you *may* try to put another ATH1 after the first.
Also how does your user-startup looks like? The last lines in mine are:
;BEGIN AmiTCP/IP
assign AmiTCP: Work:AP/Amiga/AmiTCP-4.0
path AmiTCP:bin add
Assign APIPE: Exists > NIL:
IF Warn
Mount APIPE: from AmiTCP:devs/APipe-Mountlist
EndIf
;END AmiTCP/IP
;BEGIN MUI
if exists "Work:MUI"
assign MUI: "Work:MUI"
if exists MUI:Libs
assign add LIBS: MUI:Libs
endif
if exists MUI:Locale
assign add LOCALE: MUI:Locale
endif
version >nil: exec.library 39
if not warn
if exists MUI:Docs
if exists HELP:dummy ; do not remove
endif ; this entry!
assign add HELP: MUI:Docs
endif
endif
endif
;END MUI
Excuse me for all the blank lines, but I seem to have a problem with AP that
erases a line feed if there is only one between two lines.
Bart Van Bockstaele at 100574.2352@compuserve.com
… On AutoPilot and Amiga all the way from Belgium …
Bart-
The thing with the blank lines is that AP no longer force-formates messages, so
that lines that are really short get pushed back onto the previous line–UNLESS
you start the line with a period or a blanks space.
I don't think that it's the modem, because it always dials, so it's getting a
carrier I'd assume. I have the AmiTCP: assign in assign prefs, and the APIPE
bit in my user-startup, and MUI is set up right. I'm going to try
dialer.device and see if that fixes it.
Right now, though, it's not at all bad–the most I've had to wait is for one
extra execution of startnet since using your dialscript. Before, it could be
an hour of random fiddling before getting online. So THANK YOU!!!!
Mr. Zombie
>>The thing with the blank lines is that AP no longer force-formates messages,
so that lines that are really short get pushed back onto the previous
line–UNLESS you start the line with a period or a blanks space.<<
Thank you very much for the info Paul. It really made me think that AutoPilot
DID have a serious problem. I am happy this is not the case.
>>I'm going to try dialer.device and see if that fixes it.<<
I use the normal serial.device so I doubt a little bit if that will work but
then, you can always hope…
Bart Van Bockstaele at 100574.2352@compuserve.com
… On AutoPilot and Amiga all the way from Belgium …
>>Excuse me for all the blank lines, but I seem to have a problem with AP that
erases a line feed if there is only one between two lines.
Start the new line with a period or a blank space.
Input as ".blah"
blah
blah
Input as " blah"
blah
blah
John
What does your envarc:sana2/ppp0.config file look like?
Mine looks like:
serial.device 0 38400 0.0.0.0 7WIRE DIALSCRIPT=amitcp:db/myscript
That dialscript part points to the custom script I wrote, and uploaded in the
PPPHLP.LHA file.
Here it is. Two seperate lines.
serial.device 0 19200 0.0.0.0 7WIRE LOG=40 REMOTEIP=149.174.64.25
DIALSCRIPT=AmiTCP:PPPDialScript
Mr. Zombie
>>serial.device 0 19200 0.0.0.0 7WIRE LOG=40 REMOTEIP=149.174.64.25
DIALSCRIPT=AmiTCP:PPPDialScript<<
Are you sure Paul, this doesn't have to be on *one* line?
Bart Van Bockstaele at 100574.2352@compuserve.com
… On AutoPilot and Amiga all the way from Belgium …
Uh, I don't think so, but I'll try it that way.
Mr. Zombie
There's always hope…
Bart Van Bockstaele at 100574.2352@compuserve.com
… On AutoPilot and Amiga all the way from Belgium …
I would think the REMOTEIP part isn't necessary either, and may be wrong.
Shouldn't the compuserve host transmit that?
Clay
I *think* it has to be on one line, and get rid of the REMOTEIP=149.174.64.25.
The remote ip address is dynamic (so is the local ip address), and is likely
the cause of your problems.
Paul,
Just a wild guess at something to check: You said >>Then I put the DIALSCRIPT
entry in ppp0.config file in env:sana2.<< Did you also put it in
ENVARC:sana2/ppp0.config? Mine contains the line
serial.device 0 19200 0.0.0.0 7WIRE DIALSCRIPT=Work:Utilities/PPP/dialscript
This is a single line in my file.
Good luck,
Clay
Clay-
Yah, I put it in both, and it's still there after cold resets. I narrowed the
problem down a bit further. I tried executing the lines of my startnet script
one by one from wshell, and lo and behold, it was choking on the first line!
The "online" line. What happens when it fails to connect–and it still seems
random to me–is that the phone number is dialed and then it hangs up. If I
hear a ring I'm OK. So is it my dialscript file? I used both Bart's and the
one that various people and Steve posted here. With Bart's so far it fails the
first time then runs the second time, but I think I have to manually run AmiTCP
first, and then startnet runs it again, although I'm not even sure if I tested
that since trying Bart's dialscript.
Mr. Zombie
Paul,
>>With Bart's so far it fails the first time then runs the second time, but I
think I have to manually run AmiTCP first, and then startnet runs it again,
although I'm not even sure if I tested that since trying Bart's dialscript.<<
Maybe I don't understand, but I think PPP has to run first, since AmiTCP
expects it to be there as the device through which it gets to the internet. You
can run TCP first, but I don't know what happens when you try to start PPP
after that. (I've run TCP by itself to use AMosaic to look at its own html
documentation.)
Clay
Paul,
looks like we are having simila problems. I also can't get past the dialing
script. Although I have proceeded a little further than you seem to have. I get
garbage back on the screen as a result of the SEND's. I cannot seem to make a
clean connection, even though this is never a problem with AutoPilot, same
modem etc……
Have you set your ppp0.device and Serial prefs to the same Baud rates? This is
mentioned in the docs and may be related to the problems we appear to have.
Although I have not successfully been able to find the right combination!
Very frustrating.
Regards Leonard
Leonard-
I tried that just now. I set serial prefs to 19200, which is also what my
config for PPP has set, and now what AP has as its link speed, but it makes no
difference. It seems that with Bart's dialscript, I run startnet the first
time and it dials and hangs up without a ring, and then I run startnet a second
time and it dials and connects just fine, which is a lot better than before,
when I could startnet dozens of times and do a hundred other things trying to
get it to work before, seemingly at random, I'd successfully connect.
Mr. Zombie
Paul,
Try adding *AP to your userid string. This corrected my logon problem. My
DIALSCRIPT is as follows :-
ECHO ON
TIMEOUT 2000
REDIAL "BUSY"
SEND "ATZ"
WAIT "OK"
SEND "AT&D0&K3DT521 2400"
WAIT "CONNECT"
SEND ""
WAIT "H"
SEND "CIS"
WAIT "U"
SEND "123456,789*AP/GO:PPP89"
WAIT "Password"
SEND "themagicwords"
WAIT "please…"
DELAY 50
I don't believe I need the &K3 in the string, It was just something I tried
along the line. I also note that someone else had a different Modem
initialization string, they had AT&C1&d3H1 If all else fails you could try
that in your intialization string. My reading of my modem book indicates they
are harmless and may help if not the defaults set by the ATZ command.
Hope this helps.
Regards Leonard
Leonard-
I'll try it out, but the *AP part won't make a difference, because the problem
I'm having comes before the first ring of the phone, let alone connection
tones.
It's gotta be something in the dialscript. This is what I have now, and it
seems to set the modem properly somehow by running twice–that is, the first
time the modem dials and hangs up immediately without even waiting for a ring,
and gives me this message: … Huh, I just ran startnet to get the message and
everything worked fine the first time. I don't get it. Anyway, this is my
dialscript, taken from Bart's post.
Btw, I *HIGHLY* recommend you you change your password pronto, unless
"themmagicwords" isn't actually it, in which case I'm a chump but you're safe,
which is definitely more important. I hope you come online soon and get this
message, for your own well-being.
ECHO ON TIMEOUT 2500 REDIAL "BUSY" SEND "ATZ" WAIT "OK" SEND "AT&C1" WAIT "OK"
SEND "AT&D2" WAIT "OK" SEND "ATH1" WAIT "OK" SEND "ATD8729576" WAIT "CONNECT"
SEND "" WAIT "e:" SEND "CIS" WAIT "D:" SEND "76375,1776/GO:PPP89" WAIT "ord:"
SEND "<password>" WAIT "please…" DELAY 50 ECHO OFF
Mr. Zombie
Paul,
Try using the AT&D0 command instead of &D2. Check you modem manual, but the
&D0 command should tell it to not hang up even if the carrier is dropped. What
is going on (I'm guessing) is that you are essentially leaving CIS to a new
system, and the carrier drops for just a brief moment during the switching.
&D0 gets you over that hump. Why yours works the second time I have no idea!
8^)
Nate.
BTW, I've got to use just the last few letters of the prompt, too. Also, I was
having some similar problems logging on using AP until few weeks ago, when CIS
put all new 14.4K modems in the Toledo node; things have been GREAT ever since.
Gee, I'm glad it wasn't their fault…
Nate Wahl
Emerald Video
Nate-
Thanks for the tip, I'll try it, but it's not anything in CIS, because I don't
actually *reach* CIS–the modem hangs up before the phone even rings.
I'm not sure why, but Bart's dialscript works sometimes the first time, always
the second time. So far.
Mr. Zombie
Paul,
So far I haven't bothered using the dialscript. I use the AP and handson to get
access to CIS, then quit hands on type startnet and wait for the connection to
be completed, then launch Amosaic. It works every time. Be sure your init
string includes &D0 before you let AP go interactive.
I've even forgotten to set &D0 and logged in with &D2 set. I've issued the +++
AT command got the modem's OK prompt, issued an AT&D0, then ATO to go back
online and then typed GO PPPconnect, and that worked fine too!
For the time being, if your anxious to try the internet WWW, forget the
dialscript and go in manually. IMHO, the WWW on CIS so far is very, very, slow,
and not to interesting. I'm hoping that in time this will change.
Christopher
If you go on the Web, it's probably worth your time to set up the dialscript,
because it'll save chip mem. Even if you quit AP, you've already started other
stuff, so chip mem will be fragged. Several dialscripts have been posted, so
if one doesn't work, just try another.
Mr. Zombie
Paul,
From what I've seen so far (and it ain't much) I doubt I'll be doing much
surfing of the web.
Besides, I've got 2MB of chip and I don't think I'll need it all, but then
again, who knows until one tries, eh?
Chris
Chris,
If you quit Handson, where do you type "startnet"? I thought quiting Handson
wold throw you off CI$.
This is going to be some adventure when I get free dialing to a CI$ node next
month & try my hand. I've saved ALL the posts.
How are the animals?
Gracia, on AutoPilot from Cooleemee, NC
Gracia,
"If you quit Handson, where do you type "startnet"? I thought quiting Handson
wold throw you off CI$."
Well, I set my modem to stay on after quitting handson using the AT command
I change it in the init string in setup. Or I enter it interactively while on
line using the +++ and ATO commands.
AT&D0
instead of AT&D2
Then in a shell CD to AmiTCP:
then I execute my startnet script
run execute startnet
the command to start PPP.device is the first line of startnet
AmiTCP:bin/online ppp0
It takes a few seconds but finally after the guilt screen disappears I click
on the AMosaic icon and wait for the browser to load.
Simple, not really, but I got it working easier than those dialscripts, so far.
Chris
Chris,
Thanks…I'll try that next month when I get free dialing to Winston & can
better afford to spend hours experimenting. So far I have a small book of
messages saved from here in lieu of docs <VBG>.
Gracia, on AutoPilot from Cooleemee, NC
Paul,
it's not my password, but you can have it if youm like!
Regards Leonard
Resource allocation failure sounds like your serial port is in use, or you've
run out of memory or some such thing.
dale@iam.com http://www.iam.com
Intangible Assets Manufacturing
I've got plenty of memory–16 fast and 2 chip–so that shouldn't be the
problem. I'm going to try the dialer.device, because the problem seems to be
in the dialing. It dials the number, then hangs up before getting a ring–or
at least that's what I'm hearing on my modem's speaker.
Mr. Zombie