🚀 go-pugleaf

jsburger@xmission.com (John S. Burger) writes:

>Has any one tried the AmiTCP patch to version 4.3 yet. It showed up on Aminet
>today but all of the patches fail. The installer runs OK it just says it could
>not patch each file. All 29 of them. :<(

>Anyone out there have any ideas?

Well, on mine it only did not patch 2 files, which I think were
amigaguide files which I deleted awhile ago.  I've gotten static slip to
work, but cannot, at least after two hours, get dynamic slip with or
without bootp to work.  The program does not even DIAL as claimed.
Right now I'm simulating a dynamic slip connection with an arexx script
to dial in and process the bootp output to automate the connection as I
did in 4.2.

The only thing I can think of for you to do is to 1) make sure that all
files are in the original state (e.g. not compressed by powerpacker,
deleted, etc), or if all files are not modified as far as you can tell,
2) reinstall a clean copy, and run the patch on that to see what you
get.  Good luck.

Another odd thing also happened: none of my daemons are working!  I no
longer have ftpd or telnetd functional.  They are defined in inet.conf
and as far as I can tell they are as before.

If anyone gets dynamic slip with/with out bootp to work, please email me
or post here.  Thanks!
--
John Chen
jwcj@rlb6000.scs.uiuc.edu
Be happier!

jwcj@rlb6000.scs.uiuc.edu (John Chen) writes:

>If anyone gets dynamic slip with/with out bootp to work, please email me
>or post here.  Thanks!

Silly me, read the manual first!  To do slip with bootp, load the file
amitcp:db/Provider.conf into your favorite editor, do the following:

1) delete the command ManualConsole and replace it with ShowConsole
2) add the line 'call Dial' after ShowConsole
3) add the line 'ManualConsole'

that's it!  Of course this will require you to log in to your provider
and activate the slip or ppp service manually.  For those of you who
like to automate that, do the following:

1) after call Dial, add the line
       WaitFor "Username: " 
or whatever your provider asks for the login.
2) add the line
       SendLn "YourUserNameHere"
3) add
       WaitFor "Password: "
       SendLn "YourPasswordHere"
       WaitFor ">" 
(or whatever prompt you get after you successfully logged in)
       SendLn "slip default"
(or whatever is needed to get slip to work)

that's it.  Do not add ManualConsole.  AmiTCP will then start bootpconfig
and send the BOOTP command to get connection information.  Once you have
everything working you might even get rid of the 'ShowConsole' command
so you don't have to see the login info.  It's works well and fast, at
least for me.  I like it!

Now I still can't get my daemons to work.  Also, napsaterm doesn't seem
to support TEK anymore, which was one of the best features for me about
it.  I guess I'll go back to reading the manual and see if it's there
before I email NSDi to complain and whine.  :)

But so far I'm encouraged with this new released!
--
John Chen
jwcj@rlb6000.scs.uiuc.edu
Be happier!

>Has any one tried the AmiTCP patch to version 4.3 yet. It showed up on Aminet
>today but all of the patches fail. The installer runs OK it just says it
>could not patch each file. All 29 of them. :<(

I just installed it.  I had version 4.2 previous to this and it all
installed fine.

>Anyone out there have any ideas?

One thing that I have heard, is that there are different versions of the
"installer" program.  The version I have is 2.15


        Kane            --------------------------------------------
        Peterson       -- "Kane's World" World Wide Web Home Page: --
                       --      http://www.mcs.net/~kanep/www/      --
        kanep@mcs.com   --------------------------------------------

>Now I still can't get my daemons to work.  Also, napsaterm doesn't seem
>to support TEK anymore, which was one of the best features for me about
>it.  I guess I'll go back to reading the manual and see if it's there
>before I email NSDi to complain and whine.  :)

It seems that AmiTCP 4.3 doesn't have inetd running by default anymore.  If
you run it, then all your daemons will work again.

>But so far I'm encouraged with this new released!
>--
>John Chen
>jwcj@rlb6000.scs.uiuc.edu
>Be happier!


        Kane            --------------------------------------------
        Peterson       -- "Kane's World" World Wide Web Home Page: --
                       --      http://www.mcs.net/~kanep/www/      --
        kanep@mcs.com   --------------------------------------------

John Chen (jwcj@rlb6000.scs.uiuc.edu) wrote:
> Another odd thing also happened: none of my daemons are working!  I no
> longer have ftpd or telnetd functional.  They are defined in inet.conf
> and as far as I can tell they are as before.
> 
Reading the Startnet script it can take two arguments DEBUG/S,SRV/S,
It requires the SRV argument before it will start inetd or localhost.
The default 'Start AmiTCP' script is just 'AmiTCP:bin/startnet' you
have to change this to 'AmiTCP:bin/startnet SRV', I don't know why.

I did get it to dial by modifying the AmiTCP:providers/FIN_PersonalEunet
script as and together with the AmiTCP:db/Provider.conf to look similar
to my old dialscript.

Sug
--
Peter Suggitt <peter@apsayton.demon.co.uk> | Suggitt's Quality Ices
                                           |      Great  Ayton
  Warped A4000 -- "Multimedia by design"   |    North  Yorkshire

John S. Burger wrote on 02 Apr 96 13:45:58 +0500 the following article:
> Has any one tried the AmiTCP patch to version 4.3 yet. It showed up on
> Aminet today but all of the patches fail. The installer runs OK it just
> says it could not patch each file. All 29 of them. :<(

I had the same problem, but I tried several times so maybe this was the
problem. I solved it by installing the whole AmiTCP to another partition
and then manually installed the files which were differently.

To configure you have to use the Configre_AmiTCP skript (best is to make
backups of your startnet/stopnet scripts before). I meanwhile managed to
get it to run and to dial up automatically though there are still some
problems when setting up the aslip.device.

> Anyone out there have any ideas?

- Reinhard Katzmann

---
E-Mail: suamor@student.uni-tuebingen.de

One day I hope to finish my RPS Pertergrin
Concept for Pertergin (yet in german) avalaible on Request
Current Amiga-Project: GuideTool (GUI) V1.1BETA

=John Chen wrote on 3 Apr 1996 05:28:23 GMT to me:

> jsburger@xmission.com (John S. Burger) writes:
> jb> Has any one tried the AmiTCP patch to version 4.3 yet. It showed up on
[...]

> Well, on mine it only did not patch 2 files, which I think were
> amigaguide files which I deleted awhile ago.  I've gotten static slip to
> work, but cannot, at least after two hours, get dynamic slip with or

I got Dynamic IP to run but strange enogh when I log in Bootp (or whatever)
wants to have an IP adress.. I also found out that the OwnDevUnit switch shows
up on error.. Seems it is not implemented or a typo.

> without bootp to work.  The program does not even DIAL as claimed.

Of course it does. You have to call the Dial slip and then it calls flawlessly.
From my Provider.conf:

<snip>
Set WaitForTimeout 30
retries = 10

call Dial

Status "Waiting for login prompt..."
<snap>

> Right now I'm simulating a dynamic slip connection with an arexx script
> to dial in and process the bootp output to automate the connection as I
> did in 4.2.

I earlier used IPDial to log in and now I have "translated" the login script
to ARexx. Only log off does not seem to work (it seems serial set up does
not work as described in the "Readme First" file).

[...]

> Another odd thing also happened: none of my daemons are working!  I no
> longer have ftpd or telnetd functional.  They are defined in inet.conf
> and as far as I can tell they are as before.

You have to use startnet SRV so that the LOOPBACK works (try ping localhost,
it should not work if you omit the SRV switch). I personally would prefer
though that  it would work by default.

> If anyone gets dynamic slip with/with out bootp to work, please email me
> or post here.  Thanks!

Done.

- Reinhard Katzmann

---
E-Mail: suamor@student.uni-tuebingen.de

One day I hope to finish my RPS Pertergrin
Concept for Pertergin (yet in german) avalaible on Request
Current Amiga-Project: GuideTool (GUI) V1.1BETA

On or about 03-Apr-96 20:11:50 Kane Peterson typed the following words about
"Re: AmiTCP Patch 4.3".  My reply is thus...

 Hi Kane,


>>Has any one tried the AmiTCP patch to version 4.3 yet. It showed up on
>>Aminet today but all of the patches fail. The installer runs OK it just says
>>it could not patch each file. All 29 of them. :<(

 KP> I just installed it.  I had version 4.2 previous to this and it all
 KP> installed fine.

>>Anyone out there have any ideas?

 KP> One thing that I have heard, is that there are different versions of the
 KP> "installer" program.  The version I have is 2.15
                                                 ^^^^

Hmm.... I have ADOS 3.1 and the Installer version is 1.24. There is a comment
at the beginning of the patch install script that says it was tested with
V1.24 of Installer. The default tooltype in the Patch2AmiTCP_4.3.info icon is
bin/installer. There is an installer file in the bin/ directory of the patch
distribution but it has no version string and is only about half the size of
V1.24 in SYS:Utilities.

Any other ideas????

--
      //        -= John =-    jsburger@xmission.com    BIX: jburger
    \X/                                                                 Via
                             Amateur Radio   KB0ES                       T
 Amiga  2000                                                             H
 A2630 A2632            John S. Burger       Hooper, UT                  O
2+14megs  RAM                                                            R
  850meg HD             This message was composed on...                2.23ß
 Iomega  ZIP                  4-Apr-96 09:39:28
--

Where there's a will, there's an Inheritance Tax.

On or about 04-Apr-96 04:16:05 Reinhard Katzmann typed the following words
about "Re: AmiTCP Patch 4.3".  My reply is thus...

 Hi Reinhard,


 RK> John S. Burger wrote on 02 Apr 96 13:45:58 +0500 the following article:
>> Has any one tried the AmiTCP patch to version 4.3 yet. It showed up on
>> Aminet today but all of the patches fail. The installer runs OK it just
>> says it could not patch each file. All 29 of them. :<(

 RK> I had the same problem, but I tried several times so maybe this was the
 RK> problem. I solved it by installing the whole AmiTCP to another partition
 RK> and then manually installed the files which were differently.

How did you do that? The files in the distribution are just patch files not
complete executables. I renamed my V4.2 directory and reinstalled from the
original 4.2 disks and the patch failed again with the same results. Something
is really screwy here. As I said the installer program runs fine. It seems to
be something with the patch process. It goes through every file and returns
with a could not patch file error.


 RK> To configure you have to use the Configre_AmiTCP skript (best is to make
 RK> backups of your startnet/stopnet scripts before). I meanwhile managed to
 RK> get it to run and to dial up automatically though there are still some
 RK> problems when setting up the aslip.device.

I wish I could get that far.

>> Anyone out there have any ideas?

Again! :<)

--
      //        -= John =-    jsburger@xmission.com    BIX: jburger
    \X/                                                                 Via
                             Amateur Radio   KB0ES                       T
 Amiga  2000                                                             H
 A2630 A2632            John S. Burger       Hooper, UT                  O
2+14megs  RAM                                                            R
  850meg HD             This message was composed on...                2.23ß
 Iomega  ZIP                  4-Apr-96 09:46:30
--

We have engaged the Borg.  The wedding will be Friday.

>Has any one tried the AmiTCP patch to version 4.3 yet. It showed up on Aminet
>today but all of the patches fail. The installer runs OK it just says it
>could not patch each file. All 29 of them. :<(

>Anyone out there have any ideas?


>--
>      //        -= John =-    jsburger@xmission.com    BIX: jburger
>    \X/                                                                 Via
>                             Amateur Radio   KB0ES                       T
> Amiga  2000                                                             H
> A2630 A2632            John S. Burger       Hooper, UT                  O
>2+14megs  RAM                                                            R
>  850meg HD             This message was composed on...                2.23ß
> Iomega  ZIP                2-Apr-96 13:43:01
>--
>WINDOWS = Will Install Needless Data On Whole System

Have you WSHELL as your User Shell in s:User-startup?
then comment out the line "resident Shell l:wshellseg system pure"

I think it has to do with the backticked commands in some of the
dos-scripts that installer runs.


<sb>Patrick Delaere - Patrick.DeLaere@hookon.be

On or about 03-Apr-96 10:28:23 John Chen typed the following words about "Re:
AmiTCP Patch 4.3".  My reply is thus...

 Hi John,

...... *STUFF DELETED* ......

 JC> The only thing I can think of for you to do is to 1) make sure that all
 JC> files are in the original state (e.g. not compressed by powerpacker,
 JC> deleted, etc), or if all files are not modified as far as you can tell,
 JC> 2) reinstall a clean copy, and run the patch on that to see what you
 JC> get.  Good luck.

I did a complete reinstall from the original 4.2 disks and got exactly the
same result. None of the files got patched. :<(

--
      //        -= John =-    jsburger@xmission.com    BIX: jburger
    \X/                                                                 Via
                             Amateur Radio   KB0ES                       T
 Amiga  2000                                                             H
 A2630 A2632            John S. Burger       Hooper, UT                  O
2+14megs  RAM                                                            R
  850meg HD             This message was composed on...                2.23ß
 Iomega  ZIP                  5-Apr-96 13:24:02
--

Psychoceramics:  The study of crackpots.

John S. Burger wrote on 04 Apr 96 09:53:21 +0500 to me:

>  RK> I had the same problem, but I tried several times so maybe this was
>  RK> the
>  RK> problem. I solved it by installing the whole AmiTCP to another
>  RK> partition
>  RK> and then manually installed the files which were differently.
>
> How did you do that? The files in the distribution are just patch files
> not
> complete executables. I renamed my V4.2 directory and reinstalled from
> the
> original 4.2 disks and the patch failed again with the same results.

4.1 Disk for sure ? You first install 4.1 Disk then the 4.2 patch after that
the 4.3 patch (4.3 _requires_ 4.2 being installed as you can see from the
patch filenames)

> Something
> is really screwy here. As I said the installer program runs fine. It
> seems to
> be something with the patch process. It goes through every file and
> returns
> with a could not patch file error.

I'm not sure but I don't think that 4.2 ever came on disk.

- Reinhard Katzmann

---
E-Mail: suamor@student.uni-tuebingen.de

One day I hope to finish my RPS Pertergrin
Concept for Pertergin (yet in german) avalaible on Request
Current Amiga-Project: GuideTool (GUI) V1.1BETA

On or about 05-Apr-96 13:25:44 John S. Burger typed the following words about
"Re: AmiTCP Patch 4.3".  My reply is thus...

 Hi John,


I got my problem with installing the AmiTCP patch to V4.3 fixed thanks to
Patrick Delaere. I use WShell and you have to comment out the following line
from your user-startup for the installer script to work.

resident Shell l:wshellseg system pure

Thanks again Patrick!!

--
      //        -= John =-    jsburger@xmission.com    BIX: jburger
    \X/                                                                 Via
                             Amateur Radio   KB0ES                       T
 Amiga  2000                                                             H
 A2630 A2632            John S. Burger       Hooper, UT                  O
2+14megs  RAM                                                            R
  850meg HD             This message was composed on...                2.23ß
 Iomega  ZIP                  6-Apr-96 16:04:26
--

"Who would *ever* want to use more than 640 KB of RAM" (Bill Gates)

On 05 Apr 96 13:25:44 +0500, John S. Burger articulated:
<> On or about 03-Apr-96 10:28:23 John Chen typed the following words about "Re:
<> AmiTCP Patch 4.3".  My reply is thus...
<>  JC> The only thing I can think of for you to do is to 1) make sure that all
<>  JC> files are in the original state (e.g. not compressed by powerpacker,
<>  JC> deleted, etc), or if all files are not modified as far as you can tell,
<>  JC> 2) reinstall a clean copy, and run the patch on that to see what you
<>  JC> get.  Good luck.
<> 
<> I did a complete reinstall from the original 4.2 disks and got exactly the
<> same result. None of the files got patched. :<(

Same here.

-- 
---------------------------------------------------
 Bill    ////\           wnear@epix.net
 Near   ////\\\ A2000/030@50/Picasso II/Supra V.34
       //// \\\\              _____  __      _
 \\\\ ////___\\\\ //// |\  /|   |   /  \    / \
  \\\\///-----\\\\///  | \/ |   |   |  __  /---\
   \\\\/       \\\\/   |    | __|__ \__/  /     \
    Contributing Editor @ Amiga Report Magazine
---------------------------------------------------

Howdy,

>How did you do that? The files in the distribution are just patch files not
>complete executables. I renamed my V4.2 directory and reinstalled from the
>original 4.2 disks and the patch failed again with the same results.
>Something is really screwy here. As I said the installer program runs fine.
>It seems to be something with the patch process. It goes through every file
>and returns with a could not patch file error.

 RK>> To configure you have to use the Configre_AmiTCP skript (best is to make
 RK>> backups of your startnet/stopnet scripts before). I meanwhile managed to
 RK>> get it to run and to dial up automatically though there are still some
 RK>> problems when setting up the aslip.device.

>I wish I could get that far.

>>> Anyone out there have any ideas?

>Again! :<)

I too am STILL having the patch problems. I've deleted, renamed, installed,
uninstalled, check versions, ran SNOOPDOS, you name it. I've patched and
installed a lot of programs over the years and I've never seen anything like
it. I know it's probably something very simple, but there just don't seem to
be any clues. Are the people having trouble with the patch only in the U.S.?
That's about all I can come up with, till I dig some more.

Later,
Kirk

--
···········································································
  Kirk A. Hans                 |> 2D & 3D Terrain Modeling and Animation <|
  khans@wave.sheridan.wy.us    |>     For Video, Print, Multi-media &    <|
  Electronic Video Imaging     |>         Business Presentations.        <|
  P.O. Box 6386                |>                                        <|
  Sheridan, Wyoming  82801     |> 800.482.8336              307.672.5939 <|
···········································································
<tsb> -- 07-Apr-96 11:44:07 --
I quit school because it was interfering with my education.  - John Brunner

In article <860.6666T825T2917@xmission.com> jsburger@xmission.com (John S. Burger) writes:
> Has any one tried the AmiTCP patch to version 4.3 yet. It showed up on Aminet
> today but all of the patches fail. The installer runs OK it just says it could
> not patch each file. All 29 of them. :<(
> 
> Anyone out there have any ideas?

Install all the patches manually. Thats how I did it. The installer program
failed completely for me to and someone else I know. Sure it ran but the
patches failed.

simply go to the patches draw and for every file in there that has the 4243
end on it. Run bin/spatch -onewname -ppatchfile oldname

eg for Amitcp:bin/arp

bin/spatch -oAmitcp:bin/arp -ppatch/arp.4243 Amitcp:bin/arp

Beware though that this overwrites the old file. Nothing happens if it
fails to patch
---
johnv@tower.actrix.gen.nz |      Re-work        |PGP FingerPrint
johnv@voyager.co.nz       |    in progress      |2A 41 F4 EC 7C D7 D3 DC
PGP Public Key available  |                     |57 DE 64 9A 4E 9E D3 E8

Reinhard Katzmann wrote in comp.sys.amiga.networking about "Re: AmiTCP
Patch 4.3":
RK> 
RK> I'm not sure but I don't think that 4.2 ever came on disk.
RK> 

But I received AmiTCP/IP Release 4 - Version 4.2 on disk. And I am sure it
is 4.2 (but I did not install the patch to 4.3 yet).

Regards, Edwin.

Edwin Cikan (cikan@edi.ping.at) wrote:
> Reinhard Katzmann wrote in comp.sys.amiga.networking about "Re: AmiTCP
> Patch 4.3":
> RK> 
> RK> I'm not sure but I don't think that 4.2 ever came on disk.
> RK> 
> 
> But I received AmiTCP/IP Release 4 - Version 4.2 on disk. And I am sure it
> is 4.2 (but I did not install the patch to 4.3 yet).

     Yep, so did I.  I bought my copy of AmiTCP in the store just before
New Years, it was distributed by VillageTronic.


                         Scott

On 07-Apr-96 07:51:03 Kirk Hans wrote:

 KH> I too am STILL having the patch problems. I've deleted, renamed,
 KH> installed, uninstalled, check versions, ran SNOOPDOS, you name it. I've
 KH> patched and installed a lot of programs over the years and I've never
 KH> seen anything like it. I know it's probably something very simple, but
 KH> there just don't seem to be any clues. Are the people having trouble with
 KH> the patch only in the U.S.? That's about all I can come up with, till I
 KH> dig some more.

No I'm in Sweden and had the same problem with 29 files not beeing patched.

A4000/18mb, kick 40.70, wb 40.42


---

 http://www.algonet.se/~olafur

 MicroSoft Network may not carry this message without license
 to do so.  License to carry this message requires a fee of
 $1000, payable within 30 days to Olle Viksten.  Appearance of this
 message on MicroSoft Network constitutes an agreement to terms.

On Sun, 07 Apr 1996 17:29:55 +0100, Edwin Cikan articulated:
<> Reinhard Katzmann wrote in comp.sys.amiga.networking about "Re: AmiTCP
<> Patch 4.3":
<> RK> 
<> RK> I'm not sure but I don't think that 4.2 ever came on disk.
<> 
<> But I received AmiTCP/IP Release 4 - Version 4.2 on disk. And I am sure it
<> is 4.2 (but I did not install the patch to 4.3 yet).

My 4.2 came on disk direct from Finalnd.

-- 
---------------------------------------------------
 Bill    ////\           wnear@epix.net
 Near   ////\\\ A2000/030@50/Picasso II/Supra V.34
       //// \\\\              _____  __      _
 \\\\ ////___\\\\ //// |\  /|   |   /  \    / \
  \\\\///-----\\\\///  | \/ |   |   |  __  /---\
   \\\\/       \\\\/   |    | __|__ \__/  /     \
    Contributing Editor @ Amiga Report Magazine
---------------------------------------------------

On 05-Apr-96 08:43:41, Reinhard Katzmann (Suamor@student.uni-tuebingen.de) posted: 


> I'm not sure but I don't think that 4.2 ever came on disk.

4.2 was the version that I purchased 6 months ago, and is what the
retailers would still have in stock. (At least we do.)

Regards,
John Crookshank
MicroTech
--
      ______________________________________________________________
     /    MicroTech Sales Staff    | Raptor3 DEC Alpha Workstations \
    |  MicroTech Solutions, Inc.   | Lightwave 3D, Toaster/Flyer     |
    | Desktop Video Systems Dealer | JVC Professional Video Products |
    | NewTek Systems Group Dealer  | PVR, Speed Razor, Amiga Dealer  |
    |------------------------------|---------------------------------|
    |     sales@mt-inc.com              http://www.mt-inc.com/       |
     \______________________________________________________________/

>I'm not sure but I don't think that 4.2 ever came on disk.

>- Reinhard Katzmann

It is !! I have bought it January '96 :)
The patch worked for me.
Only big hassle to get it working again at start.
But I managed to establish login. :)
Anybody knows how I get AmiTCP to not dial again if I
just rebooted my machine and want to establish connection again
without disconnecting first ??
It used to work on 4.2

--
Michael Mommertz             Heerlen, The Netherlands
michaelm@cuci.nl      Connecting To The InterNet With An
       Amiga 2000/68030/25Mhz/17MB/Picasso II/CyberGraphX/AmiTCP/PPP.device
 Author Of: Taper and FujSetup.  Both On Aminet --> text/print

John Veldthuis (johnv@tower.actrix.gen.nz) wrote:

: Install all the patches manually. Thats how I did it. The installer program
: failed completely for me to and someone else I know. Sure it ran but the
: patches failed.

I did that also. But I can't get PPP to work-. I dials and gets
a connection. But when i tries to get a hostname it waits a while
and then run stopnet.

michaelm@cuci.nl (Michael Mommertz) writes:

>Anybody knows how I get AmiTCP to not dial again if I
>just rebooted my machine and want to establish connection again
>without disconnecting first ??
>It used to work on 4.2

I've emailed the authors and they said they'll think about it.  But I've
come up with a temporary solution.  Write a script that does the
following:

amitcp:amitcp.020
bootpconfig slip IP $HOSTIP DEST $DESTIP
mount TCP: from amitcp:devs/inet-mountlist
run >NIL: <NIL: inetd

This should do it.  The only wrinkle is that you must know what the old
ipnumber and the connection address before you rebooted.  this is the
problem I have.  I want to be able to do it automatically.  If we can
get AmiTCP to store the ip addresses after it established connection in
some environment variable and copy it to ENVARC: then we are set.
--
John Chen
jwcj@rlb6000.scs.uiuc.edu
Be happier!

You are in for a treat if you are patching it to work with the
ppp-device and PAP password connection. I solved it by manually
editing the db/autointerfaces to the settings in the ppp-manual.
Seems like Config AmiTCP leaves out the = in "PAP=dh1:whatever/".

I'd like an example-dial-provider script of a provider with 
several phonenumbers. Why didn't NSDi think of that ;)? I also
think leaving out the "inetd startup" as a default was pretty
stupid, bet it made a lot of people puzzled.

Anyway, good luck. _I_ got it running, you can too. :)

ps. You should have seen the look on my face when I first clicked
    on Start AmiTCP and a blank window was popped up with "Login
    manually". Like: Wow! This is really great, now I have to start
    typing in AT-commands too...what an advanced program.

-- 
+--------------------------------------------------------------------+
| Anders Ruohio <aruohio@clinet.fi> - talk aruohio@aruohio.clinet.fi |
|              WWW - http://www.clinet.fi/~aruohio                   |
+--------------------------------------------------------------------+

I (aruohio@clinet.fi) wrote:
: You are in for a treat if you are patching it to work with the
: ppp-device and PAP password connection. I solved it by manually
: editing the db/autointerfaces to the settings in the ppp-manual.
: Seems like Config AmiTCP leaves out the = in "PAP=dh1:whatever/".
: 

Ugh! This was of course my own mistake, leaving out the =. I think
there was some other problem with Config AMiTCP putting the arguments
all wrong tho, so if anyone gets "could not find ppp0" the best place
to look is in the autointerfaces.
-- 
+--------------------------------------------------------------------+
| Anders Ruohio <aruohio@clinet.fi> - talk aruohio@aruohio.clinet.fi |
|              WWW - http://www.clinet.fi/~aruohio                   |
+--------------------------------------------------------------------+

Michael Mommertz wrote on 8 Apr 1996 19:36:42 GMT the following article:

> Anybody knows how I get AmiTCP to not dial again if I
> just rebooted my machine and want to establish connection again
> without disconnecting first ??
> It used to work on 4.2

I already answered this question in the "AmiTCP4.3 offline" article but
to complete it here is what I changes in the startnet script:

.key PRVCNF/F,DEBUG/S,NOSRV/S,UMS/S
.bra {
.ket }
;
; "NOSRV" if servers are not used, _nothing_ otherwise
.def NOSRV
.def PRVCNF provider

Note: I prefer having running servers by default than not having running
them. The UMS switch is only for me private when I want to download news
and mail (it only starts a script). You can now specify the "PRVCNF"
option to start with a different config file, f.e.
> startnet offline

Of course you need then a offline.conf to be able to run it.

[...]

If NOT Warn
  ; Log in with the default user name (ENV:LOGNAME)
  AmiTCP:bin/login -f
  ; Configure AmiTCP, configure lo0 if using servers
  If X EQ "X{NOSRV}"
    Set LOOPBACK LOOPBACK
  Else
    Set LOOPBACK ""
  EndIf
  AmiTCP:bin/bootpconfig PROVIDERFILE=AmiTCP:db/{PRVCNF}.conf $LOOPBACK {DEBUG}

[...]

    If X EQ "X{NOSRV}"
      If X EQ "X{DEBUG}"
        Run <NIL: >NIL: AmiTCP:bin/inetd
      Else
        Run AmiTCP:bin/inetd {DEBUG}
      EndIf
    EndIf

[...]

- Reinhard Katzmann

---
E-Mail: suamor@student.uni-tuebingen.de

One day I hope to finish my RPS Pertergrin
Concept for Pertergin (yet in german) avalaible on Request
Current Amiga-Project: GuideTool (GUI) V1.1BETA

Hi!

> several phonenumbers. Why didn't NSDi think of that ;)? I also
> think leaving out the "inetd startup" as a default was pretty
> stupid, bet it made a lot of people puzzled.

Are you sure you selected "Starting servers" (or something like that)
during the AmiTCP configuration?

Regards,

	Stefan

On or about 09-Apr-96 18:17:29 Anders Ruohio typed the following words about
"Re: AmiTCP Patch 4.3".  My reply is thus...

 Hi Anders,


 AR> I (aruohio@clinet.fi) wrote:
 AR>: You are in for a treat if you are patching it to work with the
 AR>: ppp-device and PAP password connection. I solved it by manually
 AR>: editing the db/autointerfaces to the settings in the ppp-manual.
 AR>: Seems like Config AmiTCP leaves out the = in "PAP=dh1:whatever/".
 AR>:

 AR> Ugh! This was of course my own mistake, leaving out the =. I think
 AR> there was some other problem with Config AMiTCP putting the arguments
 AR> all wrong tho, so if anyone gets "could not find ppp0" the best place
 AR> to look is in the autointerfaces.

I have not been able to get the 4.3 startnet to work either. I get the "could
not find ppp0" error also and there is an entry in autointerfaces for PPP. I
am just using my 4.2 startnet and the dialer built into ppp.device and it
works fine. I do wish I could get the 4.3 startnet to work though.


--
      //        -= John =-    jsburger@xmission.com    BIX: jburger
    \X/                                                                 Via
                             Amateur Radio   KB0ES                       T
 Amiga  2000                                                             H
 A2630 A2632            John S. Burger       Hooper, UT                  O
2+14megs  RAM                                                            R
  850meg HD             This message was composed on...                 2.3ß
 Iomega  ZIP                  11-Apr-96 12:21:01 MST
--

It's better to burn out than it is to rust.

>On 07-Apr-96 07:51:03 Kirk Hans wrote:

 KH>> I too am STILL having the patch problems. I've deleted, renamed,
 KH>> installed, uninstalled, check versions, ran SNOOPDOS, you name it. I've
 KH>> patched and installed a lot of programs over the years and I've never
 KH>> seen anything like it. I know it's probably something very simple, but
 KH>> there just don't seem to be any clues. Are the people having trouble
 KH>> with the patch only in the U.S.? That's about all I can come up with,
 KH>> till I dig some more.

>No I'm in Sweden and had the same problem with 29 files not beeing patched.

>A4000/18mb, kick 40.70, wb 40.42


>---

> http://www.algonet.se/~olafur

> MicroSoft Network may not carry this message without license
> to do so.  License to carry this message requires a fee of
> $1000, payable within 30 days to Olle Viksten.  Appearance of this
> message on MicroSoft Network constitutes an agreement to terms.

I had no problem in the patching, however it took me 2 days to get my
connection working again. Some how I lost all my configuration info and
had to work it out again. Also it does not like you using the PPP dialer
scripts so I had to work out how to use the new AmiTCP dialer scripts.

I would recommend backing up all your AMiTCP settup before upgrading.

Tony





-------------------------------------------------------------------------
Tony McCreath                                      mccreath@vossnet.co.uk
Telecoms Software Engineer                             Amiga4000/030,6Meg
-------------------------------------------------------------------------

>No I'm in Sweden and had the same problem with 29 files not beeing patched.

>A4000/18mb, kick 40.70, wb 40.42

Make sure to use the standard Shell as user-shell not WShell!!
>---

> http://www.algonet.se/~olafur

> MicroSoft Network may not carry this message without license
> to do so.  License to carry this message requires a fee of
> $1000, payable within 30 days to Olle Viksten.  Appearance of this
> message on MicroSoft Network constitutes an agreement to terms.







<sb>Patrick Delaere - Patrick.DeLaere@hookon.be

John S. Burger (jsburger@xmission.com) wrote:
: 
: I have not been able to get the 4.3 startnet to work either. I get the "could
: not find ppp0" error also and there is an entry in autointerfaces for PPP. I
: am just using my 4.2 startnet and the dialer built into ppp.device and it
: works fine. I do wish I could get the 4.3 startnet to work though.
: 

The error is most likely in autointerfaces, in the ppp line. Check
that the parameters are as they should according to the ppp.device
docs. You can see your configuration in the amitcp:db/Provider.conf,
it is at the top, commented out.

-- 
+--------------------------------------------------------------------+
| Anders Ruohio <aruohio@clinet.fi> - talk aruohio@aruohio.clinet.fi |
|              WWW - http://www.clinet.fi/~aruohio                   |
+--------------------------------------------------------------------+