Welcome, Guest. Please login or register.

Author Topic: Path to insanity with Path command  (Read 6575 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline paul1981Topic starter

Path to insanity with Path command
« on: May 17, 2011, 09:28:35 PM »
Hello,

This is the first time I have been stumped when it comes to my Amiga, but I AM stumped, and it's time I learned to ask for help when needed!

Okay, I have a problem with the script below. Those commands used to be on the end of my user-startup file, but I found that it was causing problems with WHDLoad games, ie causing them to freeze etc. so I decided to just run the whole lot seperately in a script which I called "Enable-Networking" and I saved this script into s:
See below...

;
;BEGIN PCMCIACARD NETWORK SETUP
SetPrism2Defaults SSID BTHomeHub2-P32N KEY 9583218079
;END
;BEGIN AmiTCP/IP
assign AmiTCP: Workbench:Expansion/AmiTCP
path AmiTCP:bin add
;AmiTCP:bin/login -f amiga_user >"con:*/*/*/200/AmiTCP-IP Login/AUTO/CLOSE/WAIT"
AmiTCP:bin/umask 022
AmiTCP:bin/startnet
;END AmiTCP/IP
;BEGIN AmiSSL
Assign AmiSSL: "Workbench:Expansion/AmiSSL"
If Exists AmiSSL:Libs
   Assign LIBS: AmiSSL:Libs ADD
EndIf
Path AmiSSL: ADD
;END AmiSSL
;

I gave the script a project icon, and made the default tool "IconX".
I then "left it out", so I could click on it from the desktop to turn on whenever I needed to use the internet with IBrowse.
I also added an entry into ToolsDaemon too which executes the script.

The problem I have is that none of the Paths are set up after the script has run, whether it be from "execute s:enable-networking" in ToolsDaemon, or clicked on from it's icon I created, although everything else in the script appears to work. So the AmiSSL path and AmiTCP/bin path just don't appear to set up. I verify this by typing "path" in a new shell. So I can't use the command ping for instance. Of course, I could just stick those back in the user-startup and they'd be there but I prefer to keep things neat and together.

I did find though that if I "execute s:enable-networking" from the shell, then the paths do get set up.
I'd just like to know why the path commands don't work unless I execute the script from the shell....It's driving me up the wall! :madashell:
Thank you in advance.

P.S. I'm running Workbench/Kickstart 3.1 on an A1200.
 

Offline paul1981Topic starter

Re: Path to insanity with Path command
« Reply #1 on: May 18, 2011, 01:17:44 AM »
Thanks Piru.  Weird...I wonder why AmigaDOS/Path was designed that way?  I'm not clever enough to answer that but I'm sure lots are. So it seems I'll have to add those paths back into my user-startup after all.
Everything else in the script worked, including the assigns of course...that's what stumped me....but thanks for answering my question.