Name: permtemp2003 Date: September 17, 2006 at 15:48:48 Pacific Subject: DOS Broadband Access How-To? OS: DOS 7.1 (Win98 SE) CPU/Ram: 650Mhz, 512Mb Ram Model/Manufacturer: Dell Opex
Comment:
Is there a tutorial or a walk-thru on how I setup access to my broadband via my router (I have RoadRunner). Yes I know that I can do it using Windows 9x. I have been always curous on how to do it with just DOS applications. My main goal is to have a bootable cdrom that access the internet using Arachne (and/or Lynx). I've tried Bart's Mod-boot, but it just freezes after detecting my network card. Any help would be apprecitated.
All of the bootable/stand-alone (live) CDs which i could readily connect with were always DHCP-based; this is a standard Linux feature but that's hardly available under DOS at all, as i recall, and works only if a MoDem/Router is configured to suport it.
I'm a former WatTCP user who learned to define his DOS environment variables and .CFG file to allow a number of applications to connect without the need to reconfigure... It's more desirable to make the environment capable of providing access to various applications than just load a packet-driver hoping that the client (Arachne, whatever) might be DHCP- enabled, IMHO - in short, better prepare to assign the IP address manually! Of course, if you got no idea what this is all about then i'm afraid it may be a long ride (unless you know where to look)!...
But a WatTCP setup isn't as difficult to manage as some people seem to think, this has been discussed before so i simply suggest that you search around; try this if you've acquired basic DOS user skills:
Both Arachne and DosLynx (FM's version) support DHCP period.
I do not know where the idea came from that DHCP Client is a no no in DOS Networking. The OP has a router and he only needs a Packet Driver at Vector 0x60.
As a Windows User he is not used to writing out line command config. files and in the 21st century is totally unneccessary.
I have been using routers as DHCP servers for DOS Networking for many years.......
Do> I do not know where the idea came from that Do> DHCP Client is a no no in DOS Networking.
I wonder how you came to write such a statement myself! As far as i know, DHCP makes life much simpler but many of my favourite programs often lack internal DHCP support, i'm afraid. Let me know which name i must look for in order to get a specific DOS DHCP client, please! Of course, there are a few cases where WatTCP.CFG might be required anyway and hence i'd need to do what i always done but a DHCP client would allow me to automate this task... So, i'm ready to ask you about the same DOS feature by starting a thread of my own if i must - i've been hoping for such a tool since i learned about DHCP, years ago!!!
Both Arachne and DosLynx (FM's version) support DHCP period. The client is built into these apps which the OP was interested in, providing he has a Packet Driver at Vector 0x60.
I am not talking generally I was specifically targeting the question.
Actually I believe MS Network Client 3 also has a DHCP Client built in when using the TCP/IP add-on.
I appreciate your reply. In other words, internal (built-in) DHCP support is a mandatory requirement unless the user would be willing to install a full WatTCP setup. I must confess i have a tendency to like inclusive/pre-emptive solutions but this user didn't ask for one which would allow him to define RLFossil/MS-Kermit as Arachne's TelNet client, for example... I see your point, thank you for making this effort; it would help to put a list of DHCP- enabled applications with their corresponding URLs together so that anyone looking for a quick fix is refered to it swiftly, IMHO! As for the MicroSoft scenario, i believe DHCP comes at the cost of high memory consumption, so high Arachne wouldn't begin to load even if it were NDIS-compatible, actually.
In any case, please let me know if someone happens to create some stand-alone DOS WatTCP DHCP client, i'm hardly satisfied when i try to gather the data i need from multiple versions of TCPInfo (none has proven to be entirely acurate and i tried at least four so far). I welcome any input in this matter!
Each PC had 600K+ free memory after install of Packet Driver, no sound though.
Arachne needs 550K base memory, but NeOS and DosLynx are a lot lower requirements so by sharing packet drivers / tcpip just exiting the app frees memory.
Actually both the browsers use WATTCP based networking, Arachne has a built in setup GUI, whereas DOSLynx has a .CFG file, which needs very little configuring:
I used MS-DOS 6.22 and Arachne 1.48 on a 486 DX2-66 for about 6 years, and was happy. I was persuaded to "upgrade" to a Windows XP system about 4 years ago. It's nice, but I can't run Arachne on it (??). I want to go back to a pure DOS machine, but a) I need DOS to connect to my cable Roadrunner, and b) I seem to have forgotten too much of the DOS/Arachne jargon: I could not understand your posts!
Booting into MS-DOS 6.22, can Arachne/DOS connect to my system? I have cable Roadrunner, cable to a network card from a cable modem/gateway that's connected to a wireless router using Netgear MA111 USB wireless adapters at 3 of my 4 PC's. What do I need, and what do I do?
Perhaps others will be up to it but i'm not really enthusiastic about finding you a DOS packet-driver for this Netgear MA111 WiFi USB dongle or yours...
It's possible you'd be better to simply give up on walking the trail backwards to have plain DOS INet access. Have you considered using VMWare, Virtual PC, Bochs or any other similar simulator i may not have heard of? Lets take VMWare, for example: in full-screen mode one might very well forget that's not the PC's own CMOS setup utility he will access at boot time (before DOS has even started)... DOS won't see much difference neither trying to manage with the virtual serial/parallel ports, sound-card or peripherals including an NIC or else, actually.
As long as you don't ask questions specific to the VMWare application or Windows itself i don't see a good reason not to welcome your requests. There's only one packet-driver for all of the VMWare users since it's for a virtual NIC that's independent of of hardware variations, which simplifies our lives a great deal because everyone is able to try it...
I'm no DOS purist engaged into religious enrolment or plain Windows bashing, i guess the few guys who keep reading this forum can accept DOS discussions provided that your topics are related to plain DOS (read independent from Windows at all costs). The alternative you mention is to manage with standard DOS as it used to be in the good old days, without the benefit of having modern resources handy... I am comfortable with that as well but you must know that you'll have to post elswhere if you break the Windows NT boot menu playing with partitions, etc.
The information on Computing.Net is the opinions of its users. Such
opinions may not be accurate and they are to be used at your own risk.
Computing.Net cannot verify the validity of the statements made on this site. Computing.Net and Computing.Net, LLC hereby disclaim all responsibility and liability for the content of Computing.Net and its accuracy.
PLEASE READ THE FULL DISCLAIMER AND LEGAL TERMS BY CLICKING HERE