[NCLUG] Spy-ware and modem problems

[mike cullerton]

what is /dev/modem pointing to?

on 2/28/01 1:20 PM, Connie Seger at equinelover at earthlink.net wrote:

> I have looked in every file I can think of and also done a find and cannot
> find any lock file. That probably would have been too easy. When I run Seyon I
> get multiple error messages. One of them is >>Error: ioctl-get: Input/output
> error
>>> Error: ioctl-set: Input/output error
>>> Error: Could not get control line status for device /dev/modem
>>> Error: Consistency error in baud rate
> Warning: invalid default BPS value: 9600
> All of that is in the terminal window then two other windows pop up. One says
> - Unable to obtain modem status
> and the other -  Unable to read from the modem or tty
> I have gone into settings on Seyon and made sure everything is set the same as
> kppp.
> Yes, I am using kppp to get connected to my isp and I have no idea what dialer
> is being used. When I look up information on kppp it says "a dialer and front
> end to pppd".  As you can tell I'm struggling with this. Thanks again for your
> suggestions. What other information could I provide? I am hoping to make the
> meeting next tuesday.
> Connie
> 
> ------Original Message------
> From: Matt Clauson <mec at dotorg.org>
> To: nclug at nclug.org
> Sent: February 27, 2001 2:21:09 PM GMT
> Subject: Re: [NCLUG] Spy-ware and modem problems
> 
> 
> On Mon, Feb 26, 2001 at 08:02:09PM -0700, Connie Seger} wrote:
>> Now my problem.  I run Windows 98 and behind that I have Linux  Caldera 2.3.
>> I finally got my modem recognized and was finally able to go to the web on
>> Linux. Over the weekend I tried to go on-line with Linux and I get the
>> message that my modem is busy.  Have no idea what / where to go next. What
>> would be giving out that message.  Windows still uses the modem just fine.
>> All suggestions greatly appreciated.
> 
> Did you make any settings changes right before that?
> 
> Look in /var/lock for any modem 'lockfiles'...  I believe the filename
> you're looking for is LCK..ttySX, where X is the number of your serial
> port (or modem device.  Under DOS/Windows, ttyS0 would equal COM1,
> ttyS1 = COM2, ttyS2=COM3, ttyS3=COM4, etc...).  You may find a
> lockfile there, which means your computer may think the modem is in
> use.  Remove that 'stale lockfile' (yes, that's the proper term for
> it) and try dialing up again.)
> 
> Hope to see you at the meeting next Tuesday...
> 
> --mec
> _______________________________________________
> NCLUG mailing list
> NCLUG at nclug.org
> http://www.nclug.org/mailman/listinfo/nclug
> 
> 
> 
> _______________________________________________
> NCLUG mailing list
> NCLUG at nclug.org
> http://www.nclug.org/mailman/listinfo/nclug
> 


 -- mike cullerton