Re: Delete version sniffing logic

2005-06-06 Thread Stefan Dösinger
> Well, Win98 was a deliberate choice. Just before WineConf we set > the Crossover nightlies to Win2k by default and all our tests immediately > went RED FAIL ;) > > Basically, when you set win2k by default, tons and tons of stuff breaks > because apps become a lot more demanding. For now it makes

Re: Delete version sniffing logic

2005-06-06 Thread peter
On Sun, 05 Jun 2005 21:24:10 +0200, Andreas Mohr <[EMAIL PROTECTED]> wrote: Still, I think we should at least target Winver=winxp and fix broken apps. yup, I think we should try to go for that for now, despite some quite system specific programs overwhelming us in case of an NT version. If

Re: Delete version sniffing logic

2005-06-05 Thread Mike Hearn
On Sun, 05 Jun 2005 21:24:10 +0200, Andreas Mohr wrote: > yup, I think we should try to go for that for now, despite some quite system > specific > programs overwhelming us in case of an NT version. Well, Win98 was a deliberate choice. Just before WineConf we set the Crossover nightlies to Win2k

Re: Delete version sniffing logic

2005-06-05 Thread Andreas Mohr
Hi, On Sun, Jun 05, 2005 at 09:03:21PM +, Stefan Dösinger wrote: > > This patch defaults us to Win98 mode. > Shouldn't we default to WinXP? I know no apps except Win98 specific system > files like InstMsiA.exe and dcom98.exe which fail with Winver=winxp. Contrary > many apps need winver=winx

Re: Delete version sniffing logic

2005-06-05 Thread Stefan Dösinger
> The rationale for this change is simple: the version sniffing > code is unreliable and gets it wrong frequently. Out of the box, > you can't run "WINEDLLOVERRIDES=msi,msiexec.exe=n wine InstMsiA.exe" > because of this code. You just get silence. It turns out that even > though this is the Win98