TIP: Click on subject to list as thread! ANSI
echo: dos_internet
to: BOB KLAHN
from: Dan Ceppa
date: 2005-07-08 23:10:08
subject: 486sx20

On 07 Jul 05  10:17:00, BOB KLAHN got back to DAN CEPPA 
-> Re: 486sx20

 DC>> Why not?
 
 BK>> Cause it's too damn primitive. Which is also why I want to do
 BK>> it.
 
 DC> That's why I said, "why not?"

 BK> Cause it ain't fun if it's too easy or too rational.

That makes perfect sense!  I still message with BW under DOS.  

 
 BK>> Suggestions on DUN and IREX? Not familiar with them.
 
 DC> What OS are you using?

 BK> Currenly dos and WFWG 3.11. However, I could switch to
 BK> Novel/caldera/Dr dos easily enough.

What's " WFWG 3.11 "?   (Though I think I can guess!)  

IREX has a DOS version.  I'm using the WIN version as I had my ISP 
settings to [D]ial [U]p to the [N] set in there.  I've never tried 
acessing the I-net from only DOS, but I know it can be done.  

I'm getting better at using IREX.  But, I'm not an expert on it by 
a long shot.  Access the IREX Echo for more on it.  Irex handles 
the file transfers.  It calls up DUN to make your connection to 
the I-net.  

My setup is that I log onto the I-net by a basic script that makes 
the connection and only signs me in. I don't go to the Home Page 
of my ISP.  

Once that's done, IREX takes over and does the file transfers.  And, 
it's IREX that initiates the dial-up script.  IOW, if you have a means 
to get DOS to log onto your ISP, all should be well.  

BTW, though IREX looks a bit daunting at first, it's not that 
difficult once you get the hang of it.  And, there are enough 
users of it to get some good support in the IREX Echo.  


Hope this helped!  




--- OMX/Blue Wave/DOS v2.30
* Origin: Soundly on the Fault Line (1:138/666.0)
SEEN-BY: 633/267 270 5030/786
@PATH: 138/666 123/500 106/2000 633/267

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.