Discussion:
eCS 2.2 beta?
(too old to reply)
A.D. Fundum
2014-12-20 13:13:10 UTC
Permalink
[cp in c.o.o.apps]
What about the old IBM dialer?
FWIW. There's more old OS/2 software there, updated or not, in several
directories. AFAIK this the newest IBM dialer:

ftp://ftp.attglobal.net/pub/ibm/OS2_Client/install.exe

It may be restricted to ibm.net -> attglobal.net ( -> ISPs using
IBM's/AT&T's former infrastructure).


--
Shmuel (Seymour J.) Metz
2014-12-21 14:51:50 UTC
Permalink
Post by A.D. Fundum
It may be restricted to ibm.net -> attglobal.net ( -> ISPs using
IBM's/AT&T's former infrastructure).
The documentation for OS/2 referred to the included PPP and SLIP
dialers as being for AT&T, but I've used them with others and they
worked well, other than not having a status display.
--
Shmuel (Seymour J.) Metz, SysProg and JOAT <http://patriot.net/~shmuel>

Unsolicited bulk E-mail subject to legal action. I reserve the
right to publicly post or ridicule any abusive E-mail. Reply to
domain Patriot dot net user shmuel+news to contact me. Do not
reply to ***@library.lspace.org
A.D. Fundum
2014-12-21 15:26:26 UTC
Permalink
Post by Shmuel (Seymour J.) Metz
The documentation for OS/2 referred to the included PPP
and SLIP dialers as being for AT&T
The link refers to the latest AT&T dialer (AKA ATTDIAL170.EXE). An ISP
may not be aware of OS/2 nor the former ibm.net anymore, but one may
be able to use this "silently" updated "ibm.net" dialer. Nowadays it's
AT&T's, FWIW:

AT&T Global Network Dialer
Version 1.70.0
Copyright (C) 2000 AT&T.


--
Barbara
2014-12-22 00:05:39 UTC
Permalink
Post by A.D. Fundum
Post by Shmuel (Seymour J.) Metz
The documentation for OS/2 referred to the included PPP
and SLIP dialers as being for AT&T
The link refers to the latest AT&T dialer (AKA ATTDIAL170.EXE). An ISP
may not be aware of OS/2 nor the former ibm.net anymore, but one may
be able to use this "silently" updated "ibm.net" dialer. Nowadays it's
AT&T Global Network Dialer
Version 1.70.0
Copyright (C) 2000 AT&T.
A few years ago, I had it working with other ISPs as long as you have all the
required informtion: incoming-outgoing servers, com port etc. There's nothing
automatic about it!

One ISP refused to work because the old dialer didn't have the required security
settings.
--
Barbara
Dave Yeo
2014-12-22 04:28:40 UTC
Permalink
Post by Barbara
Post by A.D. Fundum
Post by Shmuel (Seymour J.) Metz
The documentation for OS/2 referred to the included PPP
and SLIP dialers as being for AT&T
The link refers to the latest AT&T dialer (AKA ATTDIAL170.EXE). An ISP
may not be aware of OS/2 nor the former ibm.net anymore, but one may
be able to use this "silently" updated "ibm.net" dialer. Nowadays it's
AT&T Global Network Dialer
Version 1.70.0
Copyright (C) 2000 AT&T.
A few years ago, I had it working with other ISPs as long as you have all the
required informtion: incoming-outgoing servers, com port etc. There's nothing
automatic about it!
One ISP refused to work because the old dialer didn't have the required security
settings.
Probably only supported the Microsoft way. IIRC MS had a slightly
different way to automatically log in, CHAP vs PAP or such. Linux did
support it but was even more primitive to set up to use the builtin PPP
Dave
Dave Yeo
2014-12-22 04:25:39 UTC
Permalink
Post by A.D. Fundum
[cp in c.o.o.apps]
What about the old IBM dialer?
FWIW. There's more old OS/2 software there, updated or not, in several
ftp://ftp.attglobal.net/pub/ibm/OS2_Client/install.exe
It may be restricted to ibm.net -> attglobal.net ( -> ISPs using
IBM's/AT&T's former infrastructure).
Problem is I need NAT so that my son can share the connection. Anyways
DOIP didn't work with eCS 2.2b2, it seems the weird included dialer
hijacks some interfaces. I'll have to revisit, make note of the errors
and try to trace the problem down.
Dave
Doug Bissett
2014-12-22 17:03:07 UTC
Permalink
Post by Dave Yeo
Post by A.D. Fundum
[cp in c.o.o.apps]
What about the old IBM dialer?
FWIW. There's more old OS/2 software there, updated or not, in several
ftp://ftp.attglobal.net/pub/ibm/OS2_Client/install.exe
It may be restricted to ibm.net -> attglobal.net ( -> ISPs using
IBM's/AT&T's former infrastructure).
Problem is I need NAT so that my son can share the connection. Anyways
DOIP didn't work with eCS 2.2b2, it seems the weird included dialer
hijacks some interfaces. I'll have to revisit, make note of the errors
and try to trace the problem down.
Dave
Have you tried InJoy? Years ago, I was using DoIP (or whatever it was
called before that), and it quit working when AT&T took over the IBM
internet stuff. InJoy just worked.
Post by Dave Yeo
http://www.fx.dk/injoy/
It looks like you might need one of the more advanced versions for
NAT.
--
From the eComStation of Doug Bissett
dougb007 at telus dot net
(Please make the obvious changes, to e-mail me)
Dave Yeo
2014-12-23 01:12:23 UTC
Permalink
Post by Doug Bissett
Post by Dave Yeo
Post by A.D. Fundum
[cp in c.o.o.apps]
What about the old IBM dialer?
FWIW. There's more old OS/2 software there, updated or not, in several
ftp://ftp.attglobal.net/pub/ibm/OS2_Client/install.exe
It may be restricted to ibm.net -> attglobal.net ( -> ISPs using
IBM's/AT&T's former infrastructure).
Problem is I need NAT so that my son can share the connection. Anyways
DOIP didn't work with eCS 2.2b2, it seems the weird included dialer
hijacks some interfaces. I'll have to revisit, make note of the errors
and try to trace the problem down.
Dave
Have you tried InJoy? Years ago, I was using DoIP (or whatever it was
called before that), and it quit working when AT&T took over the IBM
internet stuff. InJoy just worked.
Post by Dave Yeo
http://www.fx.dk/injoy/
It looks like you might need one of the more advanced versions for
NAT.
That's what I'm using. Doesn't work in eCS 2.2b2 as it doesn't get a
needed interface.
Dave
Doug Bissett
2014-12-23 04:35:39 UTC
Permalink
Post by Dave Yeo
Post by Doug Bissett
Post by Dave Yeo
Post by A.D. Fundum
[cp in c.o.o.apps]
What about the old IBM dialer?
FWIW. There's more old OS/2 software there, updated or not, in several
ftp://ftp.attglobal.net/pub/ibm/OS2_Client/install.exe
It may be restricted to ibm.net -> attglobal.net ( -> ISPs using
IBM's/AT&T's former infrastructure).
Problem is I need NAT so that my son can share the connection. Anyways
DOIP didn't work with eCS 2.2b2, it seems the weird included dialer
hijacks some interfaces. I'll have to revisit, make note of the errors
and try to trace the problem down.
Dave
Have you tried InJoy? Years ago, I was using DoIP (or whatever it was
called before that), and it quit working when AT&T took over the IBM
internet stuff. InJoy just worked.
Post by Dave Yeo
http://www.fx.dk/injoy/
It looks like you might need one of the more advanced versions for
NAT.
That's what I'm using. Doesn't work in eCS 2.2b2 as it doesn't get a
needed interface.
Dave
What interface? It needs a COM port configured with COM.SYS, or
PSCOM.SYS (which is probably REMed by the eCS 2.2 b2 installer,
whether you have a COM port, or not) with a modem attached (may be one
part). I can't fully test Injoy because I no longer have a telephone
line to connect my modem to, but I can make the modem attempt to dial,
and it fails because there is no dial tone. The only other thing that
it needs is the TCPIP stack. Also, don't forget that dialup uses the
RESOLV file, not the RESOLV2 file in %etc%.
--
From the eComStation of Doug Bissett
dougb007 at telus dot net
(Please make the obvious changes, to e-mail me)
Dave Yeo
2014-12-23 06:37:21 UTC
Permalink
Post by Doug Bissett
Post by Dave Yeo
Post by Doug Bissett
Post by Dave Yeo
Post by A.D. Fundum
[cp in c.o.o.apps]
What about the old IBM dialer?
FWIW. There's more old OS/2 software there, updated or not, in several
ftp://ftp.attglobal.net/pub/ibm/OS2_Client/install.exe
It may be restricted to ibm.net -> attglobal.net ( -> ISPs using
IBM's/AT&T's former infrastructure).
Problem is I need NAT so that my son can share the connection. Anyways
DOIP didn't work with eCS 2.2b2, it seems the weird included dialer
hijacks some interfaces. I'll have to revisit, make note of the errors
and try to trace the problem down.
Dave
Have you tried InJoy? Years ago, I was using DoIP (or whatever it was
called before that), and it quit working when AT&T took over the IBM
internet stuff. InJoy just worked.
Post by Dave Yeo
http://www.fx.dk/injoy/
It looks like you might need one of the more advanced versions for
NAT.
That's what I'm using. Doesn't work in eCS 2.2b2 as it doesn't get a
needed interface.
Dave
What interface? It needs a COM port configured with COM.SYS, or
PSCOM.SYS (which is probably REMed by the eCS 2.2 b2 installer,
whether you have a COM port, or not) with a modem attached (may be one
part). I can't fully test Injoy because I no longer have a telephone
line to connect my modem to, but I can make the modem attempt to dial,
and it fails because there is no dial tone. The only other thing that
it needs is the TCPIP stack. Also, don't forget that dialup uses the
RESOLV file, not the RESOLV2 file in %etc%.
It needs an interface for the dial on demand, serial interface dod is
what netstat -n reports and injoy uses ppp1 instead of ppp0 so it needs
both of them available. As well injoy actually does use resolv2 IIRC. It
wouldn't work at all on a new 2.2b2 install until I added a name server,
then it would dial out but fail to set the interfaces.
I'll reboot into 2.2b2 later and make a note of the actual failure error
messages.
I also have to re-enable pscom.sys as my USR Robotics USB modem died
during the big storm the other night and my backup modem is really a
serial port modem with a USB serial port tacked on and it doesn't work
well with our USB stack.
May be USB problem with the weird dialer included with 2.2B2 as well
(and maybe now my Warp 4 partition) as it would work for maybe 5 minutes
and then stop while pretending to still work.
Once they get credit cards working at Arca Noae I'll have to upgrade.
Dave
Doug Bissett
2014-12-23 21:14:43 UTC
Permalink
Post by Dave Yeo
Post by Doug Bissett
Post by Dave Yeo
Post by Doug Bissett
Post by Dave Yeo
Post by A.D. Fundum
[cp in c.o.o.apps]
What about the old IBM dialer?
FWIW. There's more old OS/2 software there, updated or not, in several
ftp://ftp.attglobal.net/pub/ibm/OS2_Client/install.exe
It may be restricted to ibm.net -> attglobal.net ( -> ISPs using
IBM's/AT&T's former infrastructure).
Problem is I need NAT so that my son can share the connection. Anyways
DOIP didn't work with eCS 2.2b2, it seems the weird included dialer
hijacks some interfaces. I'll have to revisit, make note of the errors
and try to trace the problem down.
Dave
Have you tried InJoy? Years ago, I was using DoIP (or whatever it was
called before that), and it quit working when AT&T took over the IBM
internet stuff. InJoy just worked.
Post by Dave Yeo
http://www.fx.dk/injoy/
It looks like you might need one of the more advanced versions for
NAT.
That's what I'm using. Doesn't work in eCS 2.2b2 as it doesn't get a
needed interface.
Dave
What interface? It needs a COM port configured with COM.SYS, or
PSCOM.SYS (which is probably REMed by the eCS 2.2 b2 installer,
whether you have a COM port, or not) with a modem attached (may be one
part). I can't fully test Injoy because I no longer have a telephone
line to connect my modem to, but I can make the modem attempt to dial,
and it fails because there is no dial tone. The only other thing that
it needs is the TCPIP stack. Also, don't forget that dialup uses the
RESOLV file, not the RESOLV2 file in %etc%.
It needs an interface for the dial on demand, serial interface dod is
what netstat -n reports and injoy uses ppp1 instead of ppp0 so it needs
both of them available. As well injoy actually does use resolv2 IIRC. It
wouldn't work at all on a new 2.2b2 install until I added a name server,
then it would dial out but fail to set the interfaces.
I'll reboot into 2.2b2 later and make a note of the actual failure error
messages.
I can't get that far, without a telephone line.
Post by Dave Yeo
I also have to re-enable pscom.sys as my USR Robotics USB modem died
during the big storm the other night and my backup modem is really a
serial port modem with a USB serial port tacked on and it doesn't work
well with our USB stack.
I will send private mail...
Post by Dave Yeo
May be USB problem with the weird dialer included with 2.2B2 as well
(and maybe now my Warp 4 partition) as it would work for maybe 5 minutes
and then stop while pretending to still work.
I used the dialer (don't remember what it was called) for a short
period. It worked, but it was a pig to set up.
Post by Dave Yeo
Once they get credit cards working at Arca Noae I'll have to upgrade.
Dave
Ithought I saw a notice about that, but it may not work yet.
--
From the eComStation of Doug Bissett
dougb007 at telus dot net
(Please make the obvious changes, to e-mail me)
Dave Yeo
2014-12-23 21:38:58 UTC
Permalink
Post by Doug Bissett
Post by Dave Yeo
Once they get credit cards working at Arca Noae I'll have to upgrade.
Dave
Ithought I saw a notice about that, but it may not work yet.
Lewis figured a week or so, with xmas I could see it taking until next year
Dave
Dave Yeo
2014-12-24 18:31:38 UTC
Permalink
Post by Doug Bissett
Post by Dave Yeo
Post by Doug Bissett
Post by Dave Yeo
Post by A.D. Fundum
[cp in c.o.o.apps]
What about the old IBM dialer?
FWIW. There's more old OS/2 software there, updated or not, in several
ftp://ftp.attglobal.net/pub/ibm/OS2_Client/install.exe
It may be restricted to ibm.net -> attglobal.net ( -> ISPs using
IBM's/AT&T's former infrastructure).
Problem is I need NAT so that my son can share the connection. Anyways
DOIP didn't work with eCS 2.2b2, it seems the weird included dialer
hijacks some interfaces. I'll have to revisit, make note of the errors
and try to trace the problem down.
Dave
Have you tried InJoy? Years ago, I was using DoIP (or whatever it was
called before that), and it quit working when AT&T took over the IBM
internet stuff. InJoy just worked.
Post by Dave Yeo
http://www.fx.dk/injoy/
It looks like you might need one of the more advanced versions for
NAT.
That's what I'm using. Doesn't work in eCS 2.2b2 as it doesn't get a
needed interface.
Dave
What interface? It needs a COM port configured with COM.SYS, or
PSCOM.SYS (which is probably REMed by the eCS 2.2 b2 installer,
whether you have a COM port, or not) with a modem attached (may be one
part). I can't fully test Injoy because I no longer have a telephone
line to connect my modem to, but I can make the modem attempt to dial,
and it fails because there is no dial tone. The only other thing that
it needs is the TCPIP stack. Also, don't forget that dialup uses the
RESOLV file, not the RESOLV2 file in %etc%.
OK Injoy dials in when I attempt to ping something and after connecting
gives this
Err 10038 defining interface parameters - try #1
Err 10038 removing interface route
...
Repeats for a few more tries then does all the negotiation. Nothing
happens if I try to ping something and eventually when hanging up it does
...
DOD: Adding default route :Err :10038

Now that I have the com drivers installed, eCSoNET for eComstation 1.1
does work more consistently and it uses interfaces sl0 and ppp1, I guess
using the slip interface for dial on demand much like the really old
Linux did.
I'll have to play more with the eCSoNET program to get DHCP etc working
so my son can connect.
Dave
Doug Bissett
2014-12-24 19:23:53 UTC
Permalink
Post by Dave Yeo
Post by Doug Bissett
Post by Dave Yeo
Post by Doug Bissett
Post by Dave Yeo
Post by A.D. Fundum
[cp in c.o.o.apps]
What about the old IBM dialer?
FWIW. There's more old OS/2 software there, updated or not, in several
ftp://ftp.attglobal.net/pub/ibm/OS2_Client/install.exe
It may be restricted to ibm.net -> attglobal.net ( -> ISPs using
IBM's/AT&T's former infrastructure).
Problem is I need NAT so that my son can share the connection. Anyways
DOIP didn't work with eCS 2.2b2, it seems the weird included dialer
hijacks some interfaces. I'll have to revisit, make note of the errors
and try to trace the problem down.
Dave
Have you tried InJoy? Years ago, I was using DoIP (or whatever it was
called before that), and it quit working when AT&T took over the IBM
internet stuff. InJoy just worked.
Post by Dave Yeo
http://www.fx.dk/injoy/
It looks like you might need one of the more advanced versions for
NAT.
That's what I'm using. Doesn't work in eCS 2.2b2 as it doesn't get a
needed interface.
Dave
What interface? It needs a COM port configured with COM.SYS, or
PSCOM.SYS (which is probably REMed by the eCS 2.2 b2 installer,
whether you have a COM port, or not) with a modem attached (may be one
part). I can't fully test Injoy because I no longer have a telephone
line to connect my modem to, but I can make the modem attempt to dial,
and it fails because there is no dial tone. The only other thing that
it needs is the TCPIP stack. Also, don't forget that dialup uses the
RESOLV file, not the RESOLV2 file in %etc%.
OK Injoy dials in when I attempt to ping something and after connecting
gives this
Err 10038 defining interface parameters - try #1
Err 10038 removing interface route
...
Repeats for a few more tries then does all the negotiation. Nothing
happens if I try to ping something and eventually when hanging up it does
...
DOD: Adding default route :Err :10038
Now that I have the com drivers installed, eCSoNET for eComstation 1.1
does work more consistently and it uses interfaces sl0 and ppp1, I guess
using the slip interface for dial on demand much like the really old
Linux did.
I'll have to play more with the eCSoNET program to get DHCP etc working
so my son can connect.
Dave
Err 10038 seems to be a sockets error. Do you have the TCP/IP updates?
I am not sure, but I think there was a problem with what got included
in eCS 2.2 b2. The updates come with the later ACPI packages
(including the one from Arca Noae).

eCSoNet. Yes, that is the other dialer. I got that to work pretty
well, after much messing around, but I never used it very much. I also
never used it to let another system access the net. You may need to
use fixed IP addresses, in your local network, to get that to work.
--
From the eComStation of Doug Bissett
dougb007 at telus dot net
(Please make the obvious changes, to e-mail me)
Dave Yeo
2014-12-24 20:36:01 UTC
Permalink
Post by Doug Bissett
Post by Dave Yeo
Post by Doug Bissett
Post by Dave Yeo
Post by Doug Bissett
Post by Dave Yeo
Post by A.D. Fundum
[cp in c.o.o.apps]
What about the old IBM dialer?
FWIW. There's more old OS/2 software there, updated or not, in several
ftp://ftp.attglobal.net/pub/ibm/OS2_Client/install.exe
It may be restricted to ibm.net -> attglobal.net ( -> ISPs using
IBM's/AT&T's former infrastructure).
Problem is I need NAT so that my son can share the connection. Anyways
DOIP didn't work with eCS 2.2b2, it seems the weird included dialer
hijacks some interfaces. I'll have to revisit, make note of the errors
and try to trace the problem down.
Dave
Have you tried InJoy? Years ago, I was using DoIP (or whatever it was
called before that), and it quit working when AT&T took over the IBM
internet stuff. InJoy just worked.
Post by Dave Yeo
http://www.fx.dk/injoy/
It looks like you might need one of the more advanced versions for
NAT.
That's what I'm using. Doesn't work in eCS 2.2b2 as it doesn't get a
needed interface.
Dave
What interface? It needs a COM port configured with COM.SYS, or
PSCOM.SYS (which is probably REMed by the eCS 2.2 b2 installer,
whether you have a COM port, or not) with a modem attached (may be one
part). I can't fully test Injoy because I no longer have a telephone
line to connect my modem to, but I can make the modem attempt to dial,
and it fails because there is no dial tone. The only other thing that
it needs is the TCPIP stack. Also, don't forget that dialup uses the
RESOLV file, not the RESOLV2 file in %etc%.
OK Injoy dials in when I attempt to ping something and after connecting
gives this
Err 10038 defining interface parameters - try #1
Err 10038 removing interface route
...
Repeats for a few more tries then does all the negotiation. Nothing
happens if I try to ping something and eventually when hanging up it does
...
DOD: Adding default route :Err :10038
Now that I have the com drivers installed, eCSoNET for eComstation 1.1
does work more consistently and it uses interfaces sl0 and ppp1, I guess
using the slip interface for dial on demand much like the really old
Linux did.
I'll have to play more with the eCSoNET program to get DHCP etc working
so my son can connect.
Dave
Err 10038 seems to be a sockets error. Do you have the TCP/IP updates?
I am not sure, but I think there was a problem with what got included
in eCS 2.2 b2. The updates come with the later ACPI packages
(including the one from Arca Noae).
It's mostly the stock install though I did update the USB drivers. Once
I get a subscription at Arca Noae I'll try updating.
Post by Doug Bissett
eCSoNet. Yes, that is the other dialer. I got that to work pretty
well, after much messing around, but I never used it very much. I also
never used it to let another system access the net. You may need to
use fixed IP addresses, in your local network, to get that to work.
According to the documentation it should work and previously I did have
it working for a short while. Once again need to reboot to 2,2b2 and
play more. Right now I'm trying to build a debug version of Firefox and
that is likely to take a day :) (5 hours to build a regular release here
now, used to be closer to an hour)
Dave
Doug Bissett
2014-12-25 04:48:32 UTC
Permalink
On Wed, 24 Dec 2014 20:36:01 UTC, Dave Yeo <***@gmail.com>
wrote:

...snip...
Post by Dave Yeo
Post by Doug Bissett
Err 10038 seems to be a sockets error. Do you have the TCP/IP updates?
I am not sure, but I think there was a problem with what got included
in eCS 2.2 b2. The updates come with the later ACPI packages
(including the one from Arca Noae).
It's mostly the stock install though I did update the USB drivers. Once
I get a subscription at Arca Noae I'll try updating.
You might try SOCKETSK.SYS from the install that works.
Post by Dave Yeo
Post by Doug Bissett
eCSoNet. Yes, that is the other dialer. I got that to work pretty
well, after much messing around, but I never used it very much. I also
never used it to let another system access the net. You may need to
use fixed IP addresses, in your local network, to get that to work.
According to the documentation it should work and previously I did have
it working for a short while. Once again need to reboot to 2,2b2 and
play more. Right now I'm trying to build a debug version of Firefox and
that is likely to take a day :) (5 hours to build a regular release here
now, used to be closer to an hour)
Dave
You need a new system, and high speed internet. :-)
--
From the eComStation of Doug Bissett
dougb007 at telus dot net
(Please make the obvious changes, to e-mail me)
Dave Yeo
2014-12-25 18:18:16 UTC
Permalink
Post by Dave Yeo
Right now I'm trying to build a debug version of Firefox and
that is likely to take a day:) (5 hours to build a regular release here
now, used to be closer to an hour)
Dave
You need a new system, and high speed internet.:-)
It takes almost as long for dmik with his fairly new quad core, (the
wonders of moving to Python for the build environment) at least building
the debug version didn't take much longer and the swap file only grew by
12 MBs (with 2GBs of Ram and nothing else running plus
virtualaddresslimit set to 3072).
As for high speed internet, I'm almost 40 miles from Vancouver and wish
my cell worked here, little well having access to high speed internet or
for the wife, working TV which vanished due to digital switch. Still
when I first moved to this area we still had party lines.
Dave

Loading...