> does that imply that we will need to use a different code base
> for the win32
> port? or can we get by by simply a #ifdef WIN32 thingie.
>
> we would certainly get into trouble with any assembly stuff,
> since both vc++
> as well as masm use 'intel' style instructions.
And also the inline assembly syntax/format is different. The only
thought I had here was to maybe use something like NASM or the
Mingw32 version of GAS which could at least be used by the other
host OSes as well.
> i guess the only way to find out if mingw32 does the job is to
> actually try
> and compile a driver and see if it works ok on an nt box.
Or check if it has ntddk.h! I don't know the status but I did a
search at sourceware.cygwin.com/ml/cygwin for DDK but it looks
like they're still at the discussion stage.
> > > hello,
> > > there was some talk about a win32 port some time ago. if i am not
> > > mistaken,
> > > drivers for win9x and NT HAVE to be compiled with vc++/masm.
> i remember
> > > reading about this some time ago. could anyone confirm this?
> >
> > For NT or Win2K you'd need the relevant DDK (which you can sometimes
> > download from www.microsoft.com/ddk) and VC++ (5 or 6 probably).
> > There was talk on the Cygwin mailing lists of creating a DDK for
> > Mingw32 but that's as much as I know.
> >
> > For Win95 you'd need the DDK and MASM with VC++ optional. You may be
> > able to get away with just VC++ but I wouldn't know how.
> >
> > Mike.
> >
>
>
