Yahoo Groups archive

Lpc2000

Index last updated: 2026-04-28 23:31 UTC

Message

Re: [lpc2000] Problem with Crossworks

2006-01-19 by Michael Johnson

Hi Xtian,

I can't find your request on our support site - here's an extract from 
our linux faq.

Regards
Michael

Failure to connect to parallel port target interfaces may be caused by 
the following problems:

    * The user does not have read permission for the parallel port
      device driver (e.g. /dev/parport0). Linux typically does not grant
      all users access to the parallel port device drivers by default.
      To permit a user to access to the parallel port device drivers the
      user can either be added to the *lp* group, or alternatively the
      read permissions of the parallel port device driver can be changed
      to allow all users to have read access to it. Either of these
      actions require super user level permissions.
    * Another application or device driver already has exclusive control
      of the parallel port device driver.


>Hello guys
>
>I am trying to work with Crossworks under Linux and Windows. It runs fine, but 
>when I try to access my Wiggler attached at the parallel port, it says (under 
>Linux and Windows give me the same message) "The port is already in use by 
>another program", but nobody is using it (under Linux I can check this with 
>the fuser command, under Windows I dont know).
>Somebody knows ehat kind of problem can this be? (I asked about that in the 
>support site from Rowley but I didnt get any answer in one week).
>
>Thanx in advance for any help
>
>With best regards
>Xtian Xultz
>Curitiba - Brazil
>
>
> 
>Yahoo! Groups Links
>
>
>
> 
>
>
>
>  
>

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.