From: Alex <garbanzo@hooked.net>
To: Charles Curley <ccurley@wyoming.com>
Cc: gnu-win32@cygnus.com
Subject: Re: Using GCC
Date: Sun, 26 Oct 1997 14:51:00 -0000 [thread overview]
Message-ID: <Pine.BSF.3.96.971026154828.25590A-100000@zippy.dyn.ml.org> (raw)
In-Reply-To: <3.0.2.32.19971026140841.00992cd0@mailhost.wyoming.com>
On Sun, 26 Oct 1997, Charles Curley wrote:
> Ah, *that* explains the Republicans since 1994.... :-)
No, nothing can explain those. ;-)
> Well, if I were doing it, I'd start with MS VC++ Professional edition,
> *unless* the tools are available here on Cygwin. I'd read up on VxDs and go
> from there.
Visual C++ is the biggest piece of crap I've seen in a long time. It's a
pitty they call that a C++ compiler.
> I for dang sure wouldn't use a beta OS for testing it, esp. with the
> problems I've had with NT 5. Go to a recent W95 or NT 4 for this. Note that
> device drivers are very different for WNT and W9[5|8].
I like most of the changes made to Win98, however the latest CD sent to me
was really unstable (more so than any previous ones). However I don't
have the patience to "downgrade" to OSR2. The WDM aims to create uniform
drivers for 98 and NT (note the latest WDM driver I used was for my SB32,
which was horribly written).
> >> If the inputs to the device driver are port or port and count (for reads)
> >> and port and datum or port, pointer to data and count (for writes) I think
> >> you would have a nice generic testbed driver. I think I'd put some range
> >> checks on it so I don't shoot myself in the foot with it.
> >
> >If there was some way to check to see if Windows is reserving that port,
> >that'd probably be pretty helpful. Although I wonder if it'd work on NT.
>
> I don't know if there is an OS call you could make, but the program
> winmsd.exe (on NT 4) and its equivalents can find these things out, so it
> has to be in the os omewhere.
[...]
> >> Next question, for the folks who know Cygwin better than I: does Cygwin GCC
> >> include the tools necessary to make a device driver?
> >
> >Most probably yes.
>
> We will see if anyone else answers this. If not, I'd go to MS VC++. I've
> ameliorated it considerably by integrating NT Emacs into it.
How'd you manage that?
- alex
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
next prev parent reply other threads:[~1997-10-26 14:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-20 6:00 Kevin Sheehan
1997-10-25 12:02 ` Fernandes, Hilton
1997-10-25 13:18 ` Alex
1997-10-26 6:25 ` Charles Curley
1997-10-26 11:07 ` Alex
1997-10-26 13:12 ` Charles Curley
1997-10-26 14:51 ` Alex [this message]
1997-10-27 6:39 ` Charles Curley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.BSF.3.96.971026154828.25590A-100000@zippy.dyn.ml.org \
--to=garbanzo@hooked.net \
--cc=ccurley@wyoming.com \
--cc=gnu-win32@cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).