Writing Window's device drivers from scratch is hard (much, much harder than
for DOS).
Take a look at the following link for a third party
"fill-in-the-table-cells-and-then-compile" tool:

http://www.jungo.com/windriver.html



----- Original Message -----
From: "Bagotronix Tech Support" <[EMAIL PROTECTED]>
To: "Protel EDA Forum" <[EMAIL PROTECTED]>
Sent: Friday, July 11, 2003 7:25 AM
Subject: Re: [PEDA] Re[2]: Printer Driver (was - Protel EDA Forum... was
adjacent component placement D XP)


> Phillip:
>
> I already checked the www.linuxprinting.org website.  No support for
Toshiba
> P351 in CUPS or Foomatic.  They don't even list the Toshiba brand at all.
>
> If I knew how to write a printer driver for either Linux or Windows, and
it
> wasn't too difficult, I'd do it and give the printer driver away to the
> world.  There must be a fair number of Toshiba P351, P351SX, Tandy
DMP2100,
> etc. still out there and still functional.  BTW, the Tandy DMP2100 was a
> rebranded Toshiba.  I remember one of the places I worked in college
bought
> a Tandy DMP2100 (the boss was a Tandy computer fanboy), and I was tasked
> with writing some custom printing software to print out and enumerate
> charity event tickets.  Using Tandy Basic and the DMP2100 manual, in about
6
> hours of programming I had some awesome looking tickets.  But that was ROM
> Basic, pre-PC, and oh-so-long ago...
>
> I've never written a device driver for Windows or Linux before, only DOS.
> So the learning curve might be a bit much for me, unless someone knows of
a
> "fill-in-the-table-cells-and-then-compile" approach to it.




* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* To post a message: mailto:[EMAIL PROTECTED]
*
* To leave this list visit:
* http://www.techservinc.com/protelusers/leave.html
*
* Contact the list manager:
* mailto:[EMAIL PROTECTED]
*
* Forum Guidelines Rules:
* http://www.techservinc.com/protelusers/forumrules.html
*
* Browse or Search previous postings:
* http://www.mail-archive.com/[EMAIL PROTECTED]
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Reply via email to