Re: Win32 port.
- Original Message - From: John Fortin <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, December 20, 1999 1:23 PM Subject: Re: Win32 port. > You need to use mingw32. I needed to stay away from using cygwin1.dll for > licensing > reasons. However, the snapshot is really old at this point. I have changed it > alot, > and added gii support, which I am debugging. There are some things to be done. > > - I have to fix the 8-bit support. > - Occasional trapping during initialization. > - Verify keyboard mapping... > > I also need to create an NT version. The current version will only run on > win95/98/2K. Is this due to DirectX issues? Are you using features specific to DirectX 6 or higher? (DirectX 7.0 is supported on 2k, right?) I'd likely be working in NT 4.0. Jeff
Re: Win32 port.
You need to use mingw32. I needed to stay away from using cygwin1.dll for licensing reasons. However, the snapshot is really old at this point. I have changed it alot, and added gii support, which I am debugging. There are some things to be done. - I have to fix the 8-bit support. - Occasional trapping during initialization. - Verify keyboard mapping... I also need to create an NT version. The current version will only run on win95/98/2K. John Jeff Muller wrote: > What's the current status of the win32 port? I tried to build from a > snapshot a week or so ago and I ran into some problems. I was wondering if > it was because it (the win32 port) was broken or because I was using > cygwin32 where I should have been using mingw32. > > If it is in fact broken or incomplete, what remains to be done? > > Jeff
Win32 port.
What's the current status of the win32 port? I tried to build from a snapshot a week or so ago and I ran into some problems. I was wondering if it was because it (the win32 port) was broken or because I was using cygwin32 where I should have been using mingw32. If it is in fact broken or incomplete, what remains to be done? Jeff
