August 2003 - Wine-Devel - list.winehq.org

Re: [antony@antgel.co.uk: .msi files]

by Gregory M. Turner

On Friday 01 August 2003 08:50 pm, Antony Gelberg wrote: > I've also grepped the GetProcAddress calls at > http://www.antgel.co.uk/compsci/linux/cm4_debug_GPA - don't know if > that's any use. Based on this, I have a hunch: update to the latest cvs wine and you are good to go. I think the fix just went in very recently. It's cabinet stuff. -- gmt "Congress has not unlimited powers to provide for the general welfare but only those specifically enumerated." -- Thomas Jefferson

Aug. 2, 2003

Re: [antony@antgel.co.uk: .msi files]

by Antony Gelberg

On Fri, Aug 01, 2003 at 08:21:52PM -0500, Kelly Leahy wrote: > maybe you have an NT version of MSI installed? > > It seems to be trying to access the NT security APIs. Maybe the problem is > that it may be testing for existence of these APIs by trying to call > GetProcAddress on them. Wine's native DLLs are likely going to be a problem > for any app that tends to do this for testing for the existence of an API. > I've seen a lot of apps do this in the past, though I never really thought > about it as a problem until I started looking at wine. Of course, this > process of "looking up" a function to see if it exists works fine in > windows, since MS doesn't provide (stub) the function in versions of DLLs > that don't have it. > > Kelly > I definitely had the 98 version of MSI installed. I just tried again with a fresh ~/.wine directory, and got the same problem. I've put the log at http://www.antgel.co.uk/compsci/linux/cm4_debug if anyone is interested. I've also grepped the GetProcAddress calls at http://www.antgel.co.uk/compsci/linux/cm4_debug_GPA - don't know if that's any use. Any other comments or ideas? Antony

Aug. 2, 2003

Re: [antony@antgel.co.uk: .msi files]

by Kelly Leahy

maybe you have an NT version of MSI installed? It seems to be trying to access the NT security APIs. Maybe the problem is that it may be testing for existence of these APIs by trying to call GetProcAddress on them. Wine's native DLLs are likely going to be a problem for any app that tends to do this for testing for the existence of an API. I've seen a lot of apps do this in the past, though I never really thought about it as a problem until I started looking at wine. Of course, this process of "looking up" a function to see if it exists works fine in windows, since MS doesn't provide (stub) the function in versions of DLLs that don't have it. Kelly ----- Original Message ----- From: "Antony Gelberg" <antony(a)antgel.co.uk> To: "Robert Shearman" <R.J.Shearman(a)warwick.ac.uk> Cc: <wine-devel(a)winehq.org> Sent: Friday, August 01, 2003 8:05 PM Subject: Re: [antony(a)antgel.co.uk: .msi files] > On Fri, Aug 01, 2003 at 10:52:03PM +0100, Robert Shearman wrote: > > > Date: Fri, 1 Aug 2003 16:03:01 +0100 > > > From: Antony Gelberg <antony(a)antgel.co.uk> > > > To: wine-devel(a)winehq.com > > > Subject: [antony(a)antgel.co.uk: .msi files] > > > > > > Does Windows Installer work? > > > > Yes, I have installed MSN Messenger using it. > > > > > I've tried installing bout the 98 and 2K versions under wine, but only > > > get: > > > > > > cdrom $ /usr/local/bin/wine ./instmsiw.exe > > > fixme:win32:PE_CreateModule Security directory ignored > > > fixme:process:CreateProcessA (X:\IXP000.TMP\msiinst.exe,...): > > > NORMAL_PRIORITY_CLASS ignored > > > > This is your problem. Only the Win9x version of MSI works at the moment and > > only if your version is set to Win9x in your config file. I submitted a few > > patches a while ago to get the WinNT version a bit further but it needs a > > load of security functions which aren't implemented (properly) yet. There > > was talk a while ago about reimplementing MSI in Wine, but we rejected the > > idea on the grounds that it was undocumented, very complicated and not > > needed yet. > > > > > On another note, I'm really surprised that the wine-users list is so > > > quiet as it's such an important bit of software. > > > > I apologise for this. We do have a few developers that regularly post there > > (including me on occasions), it just seems you caught us at a busy moment. > > > > Rob > > > > Thanks Rob. It installed straight away. I've changed "Windows" = > "win98" in my config now. I suppose it doesn't matter that much as long > as I can run apps - I had it set to winxp from a stability point of > view, which seems a little stupid, the more I think about it. > > However, my app (Championship Manager 4) still won't install. > > src $ wine /cdrom/setup.exe > fixme:ntdll:NtOpenThreadToken > (0xfffffffe,0x00000004,0x00000001,0x406907f4): stub > fixme:advapi:SetThreadToken ((nil), (nil)): stub (NT impl. only) > fixme:ntdll:NtOpenProcessToken (0xffffffff,0x00000008,0x406907f0): stub > fixme:ntdll:NtQueryInformationToken (0xcafe,1,0x4069062c,80,0x4069067c): > stub > fixme:advapi:SetThreadToken ((nil), 0xcafe): stub (NT impl. only) > wine: Unhandled exception (thread 0009), starting debugger... > err:seh:start_debugger Couldn't start debugger ("debugger/winedbg 8 68") > (2) > Read the Wine Developers Guide on how to set up winedbg or another > debugger > src $ > > I then ran it with winedbg, producing this: > Stopped on breakpoint 1 at 0x00415d7f (setup.exe.EntryPoint in > setup.exe) > Wine-dbg>cont > No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\MSI.DLL' > (0x410d0000) > fixme:ntdll:NtOpenThreadToken > (0xfffffffe,0x00000004,0x00000001,0x406907f4): stub > fixme:advapi:SetThreadToken ((nil), (nil)): stub (NT impl. only) > fixme:ntdll:NtOpenProcessToken (0xffffffff,0x00000008,0x406907f0): stub > fixme:ntdll:NtQueryInformationToken (0xcafe,1,0x4069062c,80,0x4069067c): > stub > fixme:advapi:SetThreadToken ((nil), 0xcafe): stub (NT impl. only) > No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\CABINET.DLL' > (0x410e0000) > Loaded debug information from ELF '/usr/local/lib/wine/cabinet.dll.so' > (0x410d0000) > First chance exception: page fault on read access to 0xfffffff5 in > 32-bit code (0x004036e1). > Register dump: > CS:0023 SS:002b DS:002b ES:002b FS:008f GS:0000 > EIP:004036e1 ESP:4068ec1c EBP:00000001 EFLAGS:00010246( R- 00 I Z- > -P1 ) > EAX:00000000 EBX:40ec5040 ECX:4068e8bc EDX:400d5d84 > ESI:00000001 EDI:00000000 > Stack dump: > 0x4068ec1c (NTDLL.DLL.sqrt+0x36986c): 00000000 0040365e 00403683 > 40690bc8 > 0x4068ec2c (NTDLL.DLL.sqrt+0x36987c): 0041ec48 ffffffff 40690bd4 > 00407d0c > 0x4068ec3c (NTDLL.DLL.sqrt+0x36988c): 4068fd60 000003e8 40ec5040 > 00000001 > 0x4068ec4c (NTDLL.DLL.sqrt+0x36989c): 00690000 00700000 00000000 > 00000000 > 0x4068ec5c (NTDLL.DLL.sqrt+0x3698ac): 00000000 00000000 00000000 > 00000000 > 0x4068ec6c (NTDLL.DLL.sqrt+0x3698bc): 00000000 00000000 00000000 > 00000000 > 0x4068ec7c (NTDLL.DLL.sqrt+0x3698cc): > > 0011: sel=008f base=400e9940 limit=00000fff 32-bit rw- > Backtrace: > =>0 0x004036e1 (setup.exe..text+0x26e1 in setup.exe) (ebp=00000001) > > 0x004036e1 (setup.exe..text+0x26e1 in setup.exe): movl > 0xfffffff4(%ebp),%ecx > Wine-dbg> > > I have since run it (within script) with -debugmsg +relay, but the > output file was 3 megs, and I don't even know exactly what I'm looking > for. Doesn't help that the stack trace gets interspersed with the > function calls. > > Having said that, there are lots of calls like: > 0009:Call kernel32.GetStdHandle(fffffff5) ret=4049f965 > in the log. > > I have no idea about Windows programming (but I learn fast!). I'd > understand if it fell over because 0xfffffff5 was protected, but as it's > been doing that all the way through, I'm a little confused. Also, I > don't know why it's using NTDLL.DLL when I am running as win98? > > I know I'm kind of in at the deep end, but I'd really like to get this > to run, so if anyone can give me some pointers that would be great (no > pun intended!). > > Antony >

Aug. 2, 2003

Re: Trackbar size fixes

by Kelly Leahy

> Hmm... well I wrote a small test case on Windows. For me on WinNT, > GetSystemMetrics(SM_CYCAPTION) returns 19 (which is also what Wine > returns for me), while the initial trackbar thumb size is 21. On Win2k, > GetSystemMetrics(SM_CYCAPTION) returns 20, but the the initial thumb > size is still 21. So am I doing something wrong? It does not appear to > me that the trackbar thumb size is related to SM_CYCAPTION. > > By the way, for me, changing to > [Version] > "Windows" = "win2k" > > still returns 19 for SM_CYCAPTION for me on Wine. I am assuming that > should return 20? > I imagine the result on XP even depends on whether you are using the "new style" or "old style" window title bars. Maybe not though. Kelly

Aug. 2, 2003

Re: [antony@antgel.co.uk: .msi files]

by Antony Gelberg

On Fri, Aug 01, 2003 at 10:52:03PM +0100, Robert Shearman wrote: > > Date: Fri, 1 Aug 2003 16:03:01 +0100 > > From: Antony Gelberg <antony(a)antgel.co.uk> > > To: wine-devel(a)winehq.com > > Subject: [antony(a)antgel.co.uk: .msi files] > > > > Does Windows Installer work? > > Yes, I have installed MSN Messenger using it. > > > I've tried installing bout the 98 and 2K versions under wine, but only > > get: > > > > cdrom $ /usr/local/bin/wine ./instmsiw.exe > > fixme:win32:PE_CreateModule Security directory ignored > > fixme:process:CreateProcessA (X:\IXP000.TMP\msiinst.exe,...): > > NORMAL_PRIORITY_CLASS ignored > > This is your problem. Only the Win9x version of MSI works at the moment and > only if your version is set to Win9x in your config file. I submitted a few > patches a while ago to get the WinNT version a bit further but it needs a > load of security functions which aren't implemented (properly) yet. There > was talk a while ago about reimplementing MSI in Wine, but we rejected the > idea on the grounds that it was undocumented, very complicated and not > needed yet. > > > On another note, I'm really surprised that the wine-users list is so > > quiet as it's such an important bit of software. > > I apologise for this. We do have a few developers that regularly post there > (including me on occasions), it just seems you caught us at a busy moment. > > Rob > Thanks Rob. It installed straight away. I've changed "Windows" = "win98" in my config now. I suppose it doesn't matter that much as long as I can run apps - I had it set to winxp from a stability point of view, which seems a little stupid, the more I think about it. However, my app (Championship Manager 4) still won't install. src $ wine /cdrom/setup.exe fixme:ntdll:NtOpenThreadToken (0xfffffffe,0x00000004,0x00000001,0x406907f4): stub fixme:advapi:SetThreadToken ((nil), (nil)): stub (NT impl. only) fixme:ntdll:NtOpenProcessToken (0xffffffff,0x00000008,0x406907f0): stub fixme:ntdll:NtQueryInformationToken (0xcafe,1,0x4069062c,80,0x4069067c): stub fixme:advapi:SetThreadToken ((nil), 0xcafe): stub (NT impl. only) wine: Unhandled exception (thread 0009), starting debugger... err:seh:start_debugger Couldn't start debugger ("debugger/winedbg 8 68") (2) Read the Wine Developers Guide on how to set up winedbg or another debugger src $ I then ran it with winedbg, producing this: Stopped on breakpoint 1 at 0x00415d7f (setup.exe.EntryPoint in setup.exe) Wine-dbg>cont No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\MSI.DLL' (0x410d0000) fixme:ntdll:NtOpenThreadToken (0xfffffffe,0x00000004,0x00000001,0x406907f4): stub fixme:advapi:SetThreadToken ((nil), (nil)): stub (NT impl. only) fixme:ntdll:NtOpenProcessToken (0xffffffff,0x00000008,0x406907f0): stub fixme:ntdll:NtQueryInformationToken (0xcafe,1,0x4069062c,80,0x4069067c): stub fixme:advapi:SetThreadToken ((nil), 0xcafe): stub (NT impl. only) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\CABINET.DLL' (0x410e0000) Loaded debug information from ELF '/usr/local/lib/wine/cabinet.dll.so' (0x410d0000) First chance exception: page fault on read access to 0xfffffff5 in 32-bit code (0x004036e1). Register dump: CS:0023 SS:002b DS:002b ES:002b FS:008f GS:0000 EIP:004036e1 ESP:4068ec1c EBP:00000001 EFLAGS:00010246( R- 00 I Z- -P1 ) EAX:00000000 EBX:40ec5040 ECX:4068e8bc EDX:400d5d84 ESI:00000001 EDI:00000000 Stack dump: 0x4068ec1c (NTDLL.DLL.sqrt+0x36986c): 00000000 0040365e 00403683 40690bc8 0x4068ec2c (NTDLL.DLL.sqrt+0x36987c): 0041ec48 ffffffff 40690bd4 00407d0c 0x4068ec3c (NTDLL.DLL.sqrt+0x36988c): 4068fd60 000003e8 40ec5040 00000001 0x4068ec4c (NTDLL.DLL.sqrt+0x36989c): 00690000 00700000 00000000 00000000 0x4068ec5c (NTDLL.DLL.sqrt+0x3698ac): 00000000 00000000 00000000 00000000 0x4068ec6c (NTDLL.DLL.sqrt+0x3698bc): 00000000 00000000 00000000 00000000 0x4068ec7c (NTDLL.DLL.sqrt+0x3698cc): 0011: sel=008f base=400e9940 limit=00000fff 32-bit rw- Backtrace: =>0 0x004036e1 (setup.exe..text+0x26e1 in setup.exe) (ebp=00000001) 0x004036e1 (setup.exe..text+0x26e1 in setup.exe): movl 0xfffffff4(%ebp),%ecx Wine-dbg> I have since run it (within script) with -debugmsg +relay, but the output file was 3 megs, and I don't even know exactly what I'm looking for. Doesn't help that the stack trace gets interspersed with the function calls. Having said that, there are lots of calls like: 0009:Call kernel32.GetStdHandle(fffffff5) ret=4049f965 in the log. I have no idea about Windows programming (but I learn fast!). I'd understand if it fell over because 0xfffffff5 was protected, but as it's been doing that all the way through, I'm a little confused. Also, I don't know why it's using NTDLL.DLL when I am running as win98? I know I'm kind of in at the deep end, but I'd really like to get this to run, so if anyone can give me some pointers that would be great (no pun intended!). Antony

Aug. 2, 2003

Re: Trackbar size fixes

by Duane Clark

Jon Bright wrote: > Duane Clark wrote: > > > From the Wine include file: > > > > winuser.h:#define SM_CYCAPTION 4 > > > > So I don't think we want to use that value. > > That's just the value for passing to GetSystemMetrics. The actual value > returned will be either: > > sysMetrics[SM_CYCAPTION] = 20; > > or > > sysMetrics[SM_CYCAPTION] = SYSMETRICS_GetRegistryMetric(hkey, > "CaptionHeight", 18) > + 1; /* for the separator? */ > Hmm... well I wrote a small test case on Windows. For me on WinNT, GetSystemMetrics(SM_CYCAPTION) returns 19 (which is also what Wine returns for me), while the initial trackbar thumb size is 21. On Win2k, GetSystemMetrics(SM_CYCAPTION) returns 20, but the the initial thumb size is still 21. So am I doing something wrong? It does not appear to me that the trackbar thumb size is related to SM_CYCAPTION. By the way, for me, changing to [Version] "Windows" = "win2k" still returns 19 for SM_CYCAPTION for me on Wine. I am assuming that should return 20?

Aug. 1, 2003

Re: [antony@antgel.co.uk: .msi files]

by Robert Shearman

> Date: Fri, 1 Aug 2003 16:03:01 +0100 > From: Antony Gelberg <antony(a)antgel.co.uk> > To: wine-devel(a)winehq.com > Subject: [antony(a)antgel.co.uk: .msi files] > > Does Windows Installer work? Yes, I have installed MSN Messenger using it. > I've tried installing bout the 98 and 2K versions under wine, but only > get: > > cdrom $ /usr/local/bin/wine ./instmsiw.exe > fixme:win32:PE_CreateModule Security directory ignored > fixme:process:CreateProcessA (X:\IXP000.TMP\msiinst.exe,...): > NORMAL_PRIORITY_CLASS ignored This is your problem. Only the Win9x version of MSI works at the moment and only if your version is set to Win9x in your config file. I submitted a few patches a while ago to get the WinNT version a bit further but it needs a load of security functions which aren't implemented (properly) yet. There was talk a while ago about reimplementing MSI in Wine, but we rejected the idea on the grounds that it was undocumented, very complicated and not needed yet. > On another note, I'm really surprised that the wine-users list is so > quiet as it's such an important bit of software. I apologise for this. We do have a few developers that regularly post there (including me on occasions), it just seems you caught us at a busy moment. Rob

Aug. 1, 2003

Re: [antony@antgel.co.uk: .msi files]

by Zsolt Rizsanyi

On Friday 01 August 2003 17.03, Antony Gelberg wrote: > Hi Wine developers, > > I posted this to the wine-users list but no joy. I was wondering if > anyone could give me some advice? Does Windows Installer work? If it only gives those messages then maybe the installer is already installed? Did you check that? It does emit much more messages for me, and at least starts the GUI. But I have various native dlls copied over and the msiexec.exe is set to be run in desktop mode. > Sorry for posting here, but I have searched and searched and just can't > find anything helpful on the subject. > > FYI - I'm using ~/.wine/fake_windows, as I want to eventually get rid of > my Windows partition altogether. But if anything needs copying across, I > can do that. > > On another note, I'm really surprised that the wine-users list is so > quiet as it's such an important bit of software. > > Antony > > ----- Forwarded message from Antony Gelberg <antony(a)antgel.co.uk> ----- > > From: Antony Gelberg <antony(a)antgel.co.uk> > To: wine-users(a)winehq.com > Subject: .msi files > > Hi all, > > I've done some searching, but no joy. Anyone have any idea on how to > install software that needs Windows Installer to install? > > I've tried installing bout the 98 and 2K versions under wine, but only > get: > > cdrom $ /usr/local/bin/wine ./instmsiw.exe > fixme:win32:PE_CreateModule Security directory ignored > fixme:process:CreateProcessA (X:\IXP000.TMP\msiinst.exe,...): > NORMAL_PRIORITY_CLASS ignored > cdrom $ /usr/local/bin/wine --version > Wine 20030709 > cdrom $ > > Any ideas? > > Antony > > ----- End forwarded message ----- ____________________________________________________________________ Miert fizetsz az internetert? Korlatlan, ingyenes internet hozzaferes a FreeStarttol. Probald ki most! http://www.freestart.hu

Aug. 1, 2003

Re: Trackbar size fixes

by BiGgUn

> winuser.h:#define SM_CYCAPTION 4 Sorry, I was wrong. In the standard Windows Metrics, GetSystemMetrics( SM_CYCAPTION) returns 19. The thumb length equals this value + 2. infoPtr->uThumblen = GetSystemMetrics( SM_CYCAPTION) + 2; On a native platform, if you modify this value, thumb length will follow this formula. But it is not so simple, there are other conditions for computing the initial thumb length. Stephan

Aug. 1, 2003

Re: Trackbar size fixes

by Jon Bright

Duane Clark wrote: > From the Wine include file: > > winuser.h:#define SM_CYCAPTION 4 > > So I don't think we want to use that value. That's just the value for passing to GetSystemMetrics. The actual value returned will be either: sysMetrics[SM_CYCAPTION] = 20; or sysMetrics[SM_CYCAPTION] = SYSMETRICS_GetRegistryMetric(hkey, "CaptionHeight", 18) + 1; /* for the separator? */ -- Jon Bright Lead Programmer, Silicon Circus Ltd. http://www.siliconcircus.com

Aug. 1, 2003