CompuServe Thread

#socket.library

5 messages in this thread
#216803From: Niels Grundtvig NielsenOct 27, 1995 3:15 AM
Greetings from Belgium! (en Dag, Karl …) I'm trying to install the new beta of AMosaic, and not getting very far. First I needed socket.library, so I found and installed that. Then I added an assign to a mythical inet:libs, and the next fail – thank goodness for SnoopDOS – told me I need another library called bsdsocket.library. Has anyone else had these problems? can anyone tell me where to find this second library? I have been using AMosaic Nonet, because with carte blanche and an ISDN connection at work – writing Web pages, among other things – I don't need a live Internet connection at home. A better Amiga browser might make me change my mind, of course … Thanks in advance for any tips. Niels Grundtvig Nielsen
#216830From: Gracia M. LittauerOct 27, 1995 10:06 AM
PMFBI, I had the same problem & no one believes me <G>. I took sockt.library out of the TCP libs (nothing would work when it was there). Just run IINTS151.LHA to install everything & it will take care of that problem. I don't yet know the answer why it works, but it does! Gracia, on AutoPilot from Cooleemee, NC
#216851From: Joachim SondermannOct 27, 1995 1:15 PM
Niels, maybe I did get you wrong, but AMosaic is supposed to work only if AmiTCP is up and running. You have not to connect to the net, though. Just start AmiTCP form a shell (the program, not the startnet script, as is <g>). BTW, just to add to the confusion <g,r&d>: I have neither socket.library nor bsdsocket.library anywhere in my system. AmiTCP had usergroup.library with it, so it's there. AmiTCP and for that reason AMosaic or Gui-FTP work pretty well, though (I recall dimly that somewhere in the docs they mention that socket.lib was not needed anymore with AmiTCP higher than 2 or 3something). Don't know for Thor (sorry, Gracia) since I failed to find the time to set it up 'til now. Joachim Sondermann-Bieker on Amiga AutoPilot 1.80 from Cologne, Germany
#216986From: Gracia M. LittauerOct 28, 1995 2:59 PM
Joachim, Thanks, you explained the great socket.lib mystery <G>! I knew I had read the answer from Chris but forgot what it was. I'll figure out Thor's use. One of these days someone will say the magic words or I'll play around with it 'til I get something useful. Gracia, on AutoPilot from Cooleemee, NC
#216950From: Pete DenomyOct 28, 1995 9:42 AM
Niels, I had problems with AmiTCP v4.2 last spring.It concerned the bsdsocket.library not being found. Upon contacting NSDI tech support I was told that the bsdsocket.library is create dynamically by the AmiTCP binary when the program is started by the 'startnet' script. The startnet script uses the Arexx 'WAITFORPORT' command to pause long enough to wait for the bsdsocket.library to be formed and installed. Check and make sure that you have the 'WAITFORPORT' Arexx command in RexxC and check that your Shell-startup script has a PATH command pointing to the same or similar command dirs that your startup-sequence script points to. When you start a newshell it DOES NOT inherit the command pathways from Workbench; you have to set these Paths seperately in the shell-startup. This was what my problem was with the bsdsocket.library. Hope this helps. Pete, / / Flying the A3000 on AutoPilot 1.80 \/\/ from Durham,Ontario.