>From what I've been told (and had success with), as root, run winsetup,
and configure devices.  Somewhere in there is a list of custom devices or
something like that.  You need to configure the ecp1 device.  Set the port
and IRQ to what linux reports them to be (or if you already know them).
See /proc/interrupts and /proc/ioports.  Once that is set, you need to
make sure all users can use them (Should be set to usable by all).

You may need to run winsetup as the normal user too, I forget.  Then start
up windows, and run add new hardware from control panel.  It should detect
the parallel port just fine.  Note that while windows is running, using
the parallel port, the lpd program reports in the syslog that the printer
is "on fire" and printing will not work.

I'll try to get more details if need be.  There are some others here that
know it better than I.

Michael


On Fri, 19 Jan 2001, John Hiemenz wrote:

> Running Win4Lin2 on Caldera eDesktop kernel 2.2.14w4l
>
> I'm trying to enable a Hasp parallel dongle to use a
> software package my company developed.
>
> Anything special I may need to do in regards to installation or Win4Lin or
> the dongle software to get windows to 'see' the dongle?  Everytime I get the
> Hasp dongle software installed and try to run the application, Windows
> crashes with a blue screen.
>
> Perhaps the fact that Windows sin't showing as seeing a parallel port has
> something to do with it?  I have a parallel port and activate it using
> 'insmod lp' prior to running Win4Lin, but windows still does not see it.
>
> Running the 'Install new hardware' wizard in windows doesn't even see a
> parallel port.
>
> Now what?  Can this work or did I get the wrong software for my needs?
>
> _______________________________________________
> Win4Lin-users mailing list
> [EMAIL PROTECTED]
> https://lists.netraverse.com/mailman/listinfo/win4lin-users
>

_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users

Reply via email to