The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024

Latest message you have seen: Co-located TV, RJ45 & Power sockets/Interference


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: XM10E driver for linux


  • To: ukha_d@xxxxxxx
  • Subject: Re: XM10E driver for linux
  • From: "K. C. Li" <li@xxxxxxx>
  • Date: Wed, 10 May 2000 11:10:12 +0100 (BST)
  • Delivered-to: rich@xxxxxxx
  • Delivered-to: mailing list ukha_d@xxxxxxx
  • Mailing-list: list ukha_d@xxxxxxx; contact ukha_d-owner@xxxxxxx
  • Reply-to: ukha_d@xxxxxxx

> If anybody's interested in beta testing, please drop me a line. You
> need a 2.2.X kernel (or later), an XM10E or equivalent, and the
> RJ11<->DB25 lead to play.

We all them all and would be pleased to act as beta testers.

> There are a few rough edges and other caveats, but I can explain those
> by email to anyone interested. I expect to have beta code available
> sometime this week (once I've figured out why I can't drive it from
> my ECP-mode motherboard parallel port ;).

Yes, our MS-DOS TSR device driver for the TW523/TW7223 is having similar
problems with the newer parallel ports. We have the MASM source code for
the TWDRV50 driver and would be happy to release it to you for reference
if required.

Regards,

Kwong Li
li@xxxxxxx
Laser Business Systems Ltd.
http://www.laser.com


------------------------------------------------------------------------
*--- FREE VOICEMAIL FOR YOUR HOME PHONE! ---*
With eVoice Now you can keep in touch with clients, vendors, co-workers,
friends and family ANYTIME, ANYWHERE. Sign Up Today for FREE!
http://click.egroups.com/1/3426/7/_/2065/_/957953362/
------------------------------------------------------------------------




Home | Main Index | Thread Index

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.