Re: Bug 2131 - 16-bit support?

2005-05-10 Thread Dustin Navea
Andreas Mohr wrote: Sure, but that's a moot point, since everybody will work as much on stuff as he wants to see it progress, and that won't be too much in the Win16 case since it's of not too much interest as compared to Win32 (or probably even Win64 relatively soon). So, if john wants to play

Re: Bug 2131 - 16-bit support?

2005-05-09 Thread Lionel Ulmer
On Mon, May 09, 2005 at 05:06:31PM +0200, Andreas Mohr wrote: People are often migrating to Linux PRECISELY BECAUSE newer Windows versions are no alternative to them any more (old machines with insufficient performance/compatibility with newer Windows versions). And we better make sure we

Re: Bug 2131 - 16-bit support?

2005-05-08 Thread Andreas Mohr
Hi, On Sat, May 07, 2005 at 08:09:39PM -0500, Dustin Navea wrote: I was wondering, since I have been away for so long, are we still implementing functionality for 16-bit programs? The reason I ask is because the freecell and solitaire from Win98/ME will not load in wine, while the ones

Re: Bug 2131 - 16-bit support?

2005-05-08 Thread Shachar Shemesh
Andreas Mohr wrote: Hi, On Sat, May 07, 2005 at 08:09:39PM -0500, Dustin Navea wrote: I was wondering, since I have been away for so long, are we still implementing functionality for 16-bit programs? The reason I ask is because the freecell and solitaire from Win98/ME will not load in wine,

Re: Bug 2131 - 16-bit support?

2005-05-08 Thread Alexandre Julliard
Shachar Shemesh [EMAIL PROTECTED] writes: A real PE file has an NE header, which has a MZ header. Usually, these headers just tell whoever is trying to run the application that this is a 32 bit application. One can, however, generate a DLL which is both a 32 and a 16 bit DLL. No, there's no

Re: Bug 2131 - 16-bit support?

2005-05-08 Thread Dustin Navea
Andreas Mohr wrote: Hi, As has been mentioned before on WD, cards.dll is a very obvious Microsoft screwup, since both 16bit and 32bit DLL carry the same name, which is a big no-no. I really don't think we want to patch our loader like mad to accomodate for such a stupid mistake. Figures.. they

Re: Bug 2131 - 16-bit support?

2005-05-08 Thread Andreas Mohr
Hi, On Sun, May 08, 2005 at 03:47:52PM -0500, Dustin Navea wrote: Figures.. they are always FUBAR'ing things lol.. That's just normal in software development. But MS does seem to have some special skills there ;) Instead, maybe we should implement cards16.dll and cards.dll. Then maybe there

Re: Bug 2131 - 16-bit support?

2005-05-08 Thread Dustin Navea
Andreas Mohr wrote: Do we want to throw out the baby with the bath water? In this case it's an obvious conflict between 16bit and 32bit, and note that it's even with a very rarely used DLL, thus it's easy to give up on it. In all other cases in which 16bit and 32bit can happily co-exist I don't

Re: Bug 2131 - 16-bit support?

2005-05-08 Thread Michael Stefaniuc
Dustin Navea wrote: Andreas Mohr wrote: Do we want to throw out the baby with the bath water? In this case it's an obvious conflict between 16bit and 32bit, and note that it's even with a very rarely used DLL, thus it's easy to give up on it. In all other cases in which 16bit and 32bit can

Bug 2131 - 16-bit support?

2005-05-07 Thread Dustin Navea
I was wondering, since I have been away for so long, are we still implementing functionality for 16-bit programs? The reason I ask is because the freecell and solitaire from Win98/ME will not load in wine, while the ones from 2k/XP will. This is obviously due to the fact that our cards.dll

Re: Bug 2131 - 16-bit support?

2005-05-07 Thread Felix Nawothnig
On 05/08/2005 03:09:39 AM, Dustin Navea wrote: Basically, I just need to know for the purposes of resolving this bug, should I leave it open and confirmed so that someone knows to implement the 16-bit functions (32 - 16 bit conversions?), or should I just go ahead and close it as WONTFIX?