#internet access
17 messages in this thread
Help!!!
I've been beating my head against my Amiga all evening trying to set up all the
goodies I need to get into the Internet. I've run the iinst151 program and
everything seems happy…until I try doing something! More specifically, when I
get into the shell and type 'INTERNET', my A4000 grunts a little bit, the IO
LED flickers a moment on my Prometheus ProModem 144e and … nothing happens.
No dialing, no noise, no nothing! After a short while, I get the message PPP
FAILED…
I spend all day at work futzing about with messDOS machines and NOVELL. I look
forward to using my Amiga at home (in the 20 or so minutes my 2-year old
daughter allows me each night!). Can someone out there in netland help me get
my computer to talk to my modem so I can waste even more money and time on the
net?
Robert Fisher
What are you using as a initialazation string? ATZ is always the safest route.
There was something in the docs for iiNSTl1.51 that mentions something about
that problem.
MDEVOE
I've tried a variety of init strings, including ATZ. This is the same modem I'm
using right now. The wimpy terminal program I'm using has a simple init
string…I would think most anything would at least be enough to DIAL out! (I
fully expected strangeness AFTER getting connected.)
If I SHELL and type INTERNET right now, it'll tell me the serial port is
busy…so at least it sees that.
Do I need some kind of special cable? Cross pins 2 and 3 or something obscure?
Time to eat dinner…then I'll try again.
Robert
I had the same problem with PPP failed and was told to set the baud rate in
both the Amiga Prefs. and when iNTERiNSTALL asks, to 38400. Maybe this will
help.
MDEVOE
As long as both the Amiga Prefs and the answer you give iNTERiNSTALL are the
same you should be fine. My problem was solved when I put in a
Assign AmiTCP: WB_3:AmiTcp (put your AmiTcp location here)
in my user-startup sequence. the iNTERiNSTALL script was adding it to the end
of my sequence but I had added a "endcli" line. This was stopping the
user-startup script before it did the absolutely necessary ASSIGN.
Hope this helps if not ask again. You might also want to try running SnoopDos
first (save to a file) then looking to see where it is failing. If the script
asks for a file and can't find it, you have your first clue. 🙂
Roy Nash 70662,747
A500 Flyng High on AutoPilot
SnoopDOS! I Like It!
It told me I was failing to load bsdsocket.library…wonderful. Now where do I
find/get this library?!
I'm going to Tahoe this Friday night. Maybe I'll have better luck there!
Thanks for the SnoopDos suggestion. It looks like a pretty good utility.
Robert Fisher
I'll give 'er a shot…Thanks!
Robert
No dice! My Amiga Prefs (for the SERIAL PORT) only lets me go up to 31,250. I
tried it…nothing happened. The INIT string doesn't even make it to the modem.
(I can tell by looking at the Carrier Detect. The init string should shut it
off yet it stays on. I've sent the string using this terminal program and it
works that way.)
Shouldn't there be a file somewhere containing the init string and the phone
number? I can't find any such beastie.
I'm getting ready to throw in the towel…
Robert
Wait a minute here, something doesn't sound right. Are you saying that you get
a carrier detect light on when you haven't done anything? Just when you switch
the computer and modem on? That isn't right. BTW I also have a maximum of 31500
baud in my Prefs but that's what I set it at and then when interinstall asks
for baud rate, i type in 38400. serial.device, 0 for device number,
Compuserve's local access number and of course when interinstall is first run,
Compuserve from the selection menu. OK with all that said, do you run the
software from a cold start or like this:
Turn on computer, turn on modem, open a shell and type internet OR don't open
a shell and double click on the INTERNET icon that was supplied with
interinstall. Which should then open it's own window and start the init and
dialup proceedure. In other words, your not running a terminal program first
before running internet? I'm not trying to sound condescending it's just that
I've often forgot to do some of the most basic proceedures that everyone else
took for granted. It's just that having your carrier detect on before you even
start doesn't make any sence.
Keep trying..
MDEVOE
The Carrier Detect Forced ON is one of the modem's default settings.
As for procedures, what I usually do is turn on the modem, turn on the
computer, open a shell, type INTERNET, wait for the PPP Failed error message to
pop up, swear, clear the message, swear again, type stopnet, swear some more…
You get the idea. The ASSIGNS are correct. I took the advice of ??? (can't
think of his name at the moment) who replied to you earlier in this string. I
ran SnoopDos and found I was missing the bsdsocket.library. I guess I need to
dredge that up now.
I Just got back from Tahoe a few hours ago and am feeling pretty relaxed.
Tired, but relaxed. Maybe the clear skies and thinner air cleared some of the
cobwebs out of my brain…I'm off to hunt libraries!
Robert
I don't have a bsdsocket.library either in my SYS: LIBS: or in the LIBS: in the
AmiTCP directory. IDO have a plain "socket.library" which isn't needed when I'm
making a connection in the AmiTCP LIBS: directory. I've dialed on disabling
this file and flushing the memory. still ok. Methinks it has to do with the
carrier detect being on if you say that you get a report that the serial port
is busy. Try ATZ&C1 for your init string. Hope this helps…MDEVOE
I started thinking about the CD light too…So I tried typing INTERNET when the
modem was OFF. Lo and Behold… I got the DIALLING window! (This is the first
time I've seen it.) I tried again, this time with the modem ON and alreadt set
with the CD light off…it dialed. I still have a few bugs to squash. The silly
thing doesn't send the INIT string properly. It err's after attempting the INIT
string. I suspect the use of ACCESS! to send the AT&C1 command may have
introduced some other strange things into the modem. I'm going to try setting
up the modem to DEFAULT to the settings required on power up. It acts like
maybe the speed is incorrect.
Well, it's progress! Now, it's time for SLEEP! Maybe by Wednesday night I'll
get this thing straightened out.
Thanks for the ideas… Robert
MdeVoe,
<< I had the same problem with PPP failed and was told to set the baud rate in
both the Amiga Prefs. and when iNTERiNSTALL asks, to 38400. >>
The "Serial" prefs program on WB 3.1 will only offer 31250 as highest possible
entry, so how do I get the serial device to conect to my modem at 38400?
A4000/040 WB3.1
Alex
Alexander Schwassmann // EMail: aschwassmann@art-line.art-line.de
my personal opinions … \X/ … will probably by different from yours
Alex,
>> so how do I get the serial device to conect to my modem at 38400? <<
Most of the comm-programs don't use the system-settings. They usually have
their own setup-screens where you can change the baudrate to 115200.
Karl Van Hoyweghen on AutoPilot 1.80
Z7 A4000/40-Tower (karl.vanhoyweghen@ping.be)
That is what I set it at, 31200 on my WB Prefs. And I set it at 38400 in
iNTERiNSTALL. Seems to work for me.
MDEVOE
>>That is what I set it at, 31200 on my WB Prefs. And I set it at 38400 in
iNTERiNSTALL. Seems to work for me.<<
I tried setting iNTERiNSTALL to 31250, same as my prefs setting and it DIDN't
work! Setting things as you have worked fine. This might be a problem for some
people??? (it was for me)
/ / / //ANDRE
Strange stuff…I have to set iNTERiNSTALL to 19200 otherwise I just get
garbage. BUT, I finally managed to get thru to the Internet! The modem
initialization is pretty picky on mine. I still need to iron out a few things
to make it easier to connect.
Robert Fisher