Ok, I've tried all the suggestions more or less, I haven't tried the initscripts as of yet because I'm not entirely comfortable with them. The linux setup program didn't have anything about modems, I did fix the network card though so that's got me somewhere. I got an error message that may be of use to some of you: spurious 8259A interrupt: IRQ7. Any ideas what that's about? It happened as I was mounting my fat32 drive. I was about half way threw the line and it came up. Wvdialconf still isn't working, it still cant find anything. I tried typing wvdialconf /etc/wvdial.conf create but it says first of all that there is no configuration file, then it says that it cant access /dev/modem: it says this could be because the path is missing or in use. I looked for /dev/ttyS0 to 2 but couldn't find it. It said that the directory didn't exist. When I launched minicom it said that the default configuration file was missing then as it was entering the program it said loading default settings. I got the messages telling me to press control A to Z to access special keys or something like that but they didn't work. I'm going to read over some more manuals to see if I find anything new. Thanks again Jinksed as always Darragh ----- Original Message ----- From: "L. C. Robinson" <lcr@onewest.net> To: <blinux-list@redhat.com> Sent: Wednesday, August 21, 2002 9:56 AM Subject: Re: Connecting to the Internet ; editing LIO; setting up the sound card > On Wed, 21 Aug 2002, Darragh wrote: > > > Again nothing, I used the command setserial -a <cr> and > > You probably don't need setserial, unless you need to set up a > serial port other than the the standard first 2 (ttyS0 and ttyS1, > linux equivalent of com1 and com2). > > > I've being trying to decompress the rpm's for linuxconf but > > I've had no luck, > > Good: linuxconf is poorly maintained junk, with security > problems, and hard to follow menus, and is only included for > backward compatibility in later RedHat versions. I have deleted > it from my systems. > > > speakup method of reading the man pages is taking some getting > > use to. Its pronouncing some words as broken words example > > house is hou se. Its very distracting. To make things worse, > > I cant use the up and down arrows to read the man pages as > > speakup reads SS in front of every line, I've found from > > experimentation that the E key will do the same thing without > > The man command uses the "less" pager by default, and the > lowercase e key moves down a line at a time in that utility. > Use the the h key from within "less" (better than "more") for > help on other ways to move around (use "y" to move up a line): > "less" uses vi editor conventions for movement where possible. > > > calling out the SS string. Also, I cant read in pico with the > > arrow keys, I have to use the speakup navigation keys. that > > pico -- ugh. Many other choices: vi is widely used, and of > course emacspeak uses -- emacs. > > > makes it nearly impossible to edit text and incert text into > > certain parts of configuration files. I'll probably get use to > > it but for the moment its frustrating. Back to the modem > > though, this is getting on my nerves, I specifically asked for > > a hardware modem when buying this computer to make it as easy > > Did I miss a message? I saw nothing to indicate you have a > winmodem (which is not the same as having an internal modem). > Have you tried minicom (a terminal emulator program) to see if > you can talk directly to the modem with "AT" commands, and get an > "OK" response? > > Now, concerning the previous messages concerning wvdial, and the > RedHat ppp setup help page: > > There were a great many ways invented to set up ppp, probably > still in some aging directory in the linux archives on ibiblio > (formerly metalab), and it's many mirrors around the world (see > /pub/Linux/system/network/serial/ppp/*): wvdial obsoleted many of > these by making things easy for the average user in the most > common situations. But as it's man page says, it doesn't cover > every situation. If it doesn't work for you, you are probably > better off using one of the old dated text based scripts, which > may still work, even though not well maintained. Failing that, > it may be easiest to configure by hand editing config files: the > pppd documentation may help, though terse, but the PPP-HOWTO is > probably your friend here (skip the first sections on the newer > GUI config programs, and the sections on kernel compiling and the > like -- RedHat has already done that stuff for you). You > probably have installed the HOWTO package on your system, and can > find it by doing something like: > > locate PPP-HOWTO > > Resulting in a path something like: > /usr/share/doc/HOWTO/PPP-HOWTO > for the ascii version. > > or > locate PPP-HOWTO.html > returning something like: > /usr/share/doc/HOWTO/other-formats/html/PPP-HOWTO.html > > The most recent HOWTOs are always on www.linuxdoc.org > > If you want to configure things with the Red Hat style network > config files, see the initscripts package, (do: > rpm -qd initscripts > ) > which should lead you to a terse file giving info on the > textmode config files used in their GUI utilities: > /usr/share/doc/initscripts-6.67/sysconfig.txt > for RH7.3, > and you can edit them by hand, as I do (easier and more flexible > than the GUI -- which I can use, but dislike -- too limited). > They are: > /etc/sysconfig/network-scripts/chat-ppp0 > /etc/sysconfig/network-scripts/ifcfg-ppp0 > (see attached examples) > You may have to create the ifcfg file by copying and changing > one of the other ifcfg files in that directory. > > Then you could use the Redhat utils to bring up and take > down your ppp connection: > /sbin/ifup ppp0 > /sbin/ifdown ppp0 > > LCR > > -- > L. C. Robinson > reply to no_spam+munged_lcr@onewest.net.invalid > > People buy MicroShaft for compatibility, but get incompatibility and > instability instead. This is award winning "innovation". Find > out how MS holds your data hostage with "The *Lens*"; see > "CyberSnare" at http://www.netaction.org/msoft/cybersnare.html >