Date: Fri, 1 Aug 2003 16:03:01 +0100 From: Antony Gelberg antony@antgel.co.uk To: wine-devel@winehq.com Subject: [antony@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
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@antgel.co.uk To: wine-devel@winehq.com Subject: [antony@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
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@antgel.co.uk To: "Robert Shearman" R.J.Shearman@warwick.ac.uk Cc: wine-devel@winehq.org Sent: Friday, August 01, 2003 8:05 PM Subject: Re: [antony@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@antgel.co.uk To: wine-devel@winehq.com Subject: [antony@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
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
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.
On Fri, Aug 01, 2003 at 09:19:05PM -0500, Gregory M. Turner wrote:
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
Just upgraded to latest CVS, but still no dice. Any idea where the fix went?
It's 4AM here now, so I think I'll stop for the night, but thanks all for your help. Hopefully we can get it resolved!
Antony
On Friday 01 August 2003 09:56 pm, Antony Gelberg wrote:
On Fri, Aug 01, 2003 at 09:19:05PM -0500, Gregory M. Turner wrote:
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
Just upgraded to latest CVS, but still no dice. Any idea where the fix went?
It's 4AM here now, so I think I'll stop for the night, but thanks all for your help. Hopefully we can get it resolved!
Antony
o maybe, perhaps probably, it's still cabinet.dll's fault! try cabinet.dll=n with a native cabinet.dll. If this works, please let me know.
On Sat, Aug 02, 2003 at 01:44:13AM -0500, Gregory M. Turner wrote:
On Friday 01 August 2003 09:56 pm, Antony Gelberg wrote:
On Fri, Aug 01, 2003 at 09:19:05PM -0500, Gregory M. Turner wrote:
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
Just upgraded to latest CVS, but still no dice. Any idea where the fix went?
It's 4AM here now, so I think I'll stop for the night, but thanks all for your help. Hopefully we can get it resolved!
Antony
o maybe, perhaps probably, it's still cabinet.dll's fault! try cabinet.dll=n with a native cabinet.dll. If this works, please let me know.
-- gmt
Great, I'm getting much further now! I also had to install DCOM98.
However, I get 1628: Failed to complete installation, in a dialog box. This is before any files are copied as part of the installi, and before any questions are asked. The log with -debug +relay is only 107MB - any more pointers?
Antony
On Sat, Aug 02, 2003 at 09:31:21PM +0100, Antony Gelberg wrote:
On Sat, Aug 02, 2003 at 01:44:13AM -0500, Gregory M. Turner wrote:
On Friday 01 August 2003 09:56 pm, Antony Gelberg wrote:
On Fri, Aug 01, 2003 at 09:19:05PM -0500, Gregory M. Turner wrote:
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
Just upgraded to latest CVS, but still no dice. Any idea where the fix went?
It's 4AM here now, so I think I'll stop for the night, but thanks all for your help. Hopefully we can get it resolved!
Antony
o maybe, perhaps probably, it's still cabinet.dll's fault! try cabinet.dll=n with a native cabinet.dll. If this works, please let me know.
-- gmt
Great, I'm getting much further now! I also had to install DCOM98.
However, I get 1628: Failed to complete installation, in a dialog box. This is before any files are copied as part of the installi, and before any questions are asked. The log with -debug +relay is only 107MB - any more pointers?
Antony
Don't know if this is any help:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/e...
Error 1628 maps to ERROR_INVALID_TABLE.
Antony
On Sat, Aug 02, 2003 at 09:40:55PM +0100, Antony Gelberg wrote:
On Sat, Aug 02, 2003 at 09:31:21PM +0100, Antony Gelberg wrote:
On Sat, Aug 02, 2003 at 01:44:13AM -0500, Gregory M. Turner wrote:
On Friday 01 August 2003 09:56 pm, Antony Gelberg wrote:
On Fri, Aug 01, 2003 at 09:19:05PM -0500, Gregory M. Turner wrote:
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
Just upgraded to latest CVS, but still no dice. Any idea where the fix went?
It's 4AM here now, so I think I'll stop for the night, but thanks all for your help. Hopefully we can get it resolved!
Antony
o maybe, perhaps probably, it's still cabinet.dll's fault! try cabinet.dll=n with a native cabinet.dll. If this works, please let me know.
-- gmt
Great, I'm getting much further now! I also had to install DCOM98.
However, I get 1628: Failed to complete installation, in a dialog box. This is before any files are copied as part of the installi, and before any questions are asked. The log with -debug +relay is only 107MB - any more pointers?
Antony
Don't know if this is any help:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/e...
Error 1628 maps to ERROR_INVALID_TABLE.
Antony
I know it's bad form to keep replying to my own posts, but I get the same error when trying to install Nokia PC Suite 5, which also uses Windows Installer.
Any help gratefully appreciated.
Antony
On Sun, Aug 03, 2003 at 11:25:40PM +0100, Antony Gelberg wrote:
I know it's bad form to keep replying to my own posts, but I get the same error when trying to install Nokia PC Suite 5, which also uses Windows Installer.
Any help gratefully appreciated.
Antony
Anyone care to help me follow this issue up? I'm happy to do any debugging, but I need a helping hand.
Antony
what kind of help you need? if its running the prog on a windows pc, i can do that, if the eula allows for redistribution, or if there is a trial somewhere
--- Antony Gelberg antony@antgel.co.uk wrote:
On Sun, Aug 03, 2003 at 11:25:40PM +0100, Antony Gelberg wrote:
I know it's bad form to keep replying to my own posts, but I get the same error when trying to install Nokia PC Suite 5, which also uses Windows Installer.
Any help gratefully appreciated.
Antony
Anyone care to help me follow this issue up? I'm happy to do any debugging, but I need a helping hand.
Antony
===== -- Dustin Navea
Minor Contributor, http://www.winehq.com Bugzilla Janitor, http://bugs.winehq.com Network Admin, irc://irc.blynk.net (down)
__________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com
On Wed, Aug 06, 2003 at 06:21:22PM -0700, Dustin Navea wrote:
what kind of help you need? if its running the prog on a windows pc, i can do that, if the eula allows for redistribution, or if there is a trial somewhere
Hi Dustin,
Did you not get the first part of the thread? If not, and you can't find it in the archives, I'll repost the juicy bits. Basically whenever I try to install a Windows Installer program, I get quite far, then just before it copies files, I get a dialog box up with error 1628.
Antony
--- Antony Gelberg antony@antgel.co.uk wrote:
On Wed, Aug 06, 2003 at 06:21:22PM -0700, Dustin Navea wrote:
what kind of help you need? if its running the prog on a windows pc, i
can
do that, if the eula allows for redistribution, or if there is a trial somewhere
Hi Dustin,
Did you not get the first part of the thread? If not, and you can't find it in the archives, I'll repost the juicy bits. Basically whenever I try to install a Windows Installer program, I get quite far, then just before it copies files, I get a dialog box up with error 1628.
Antony
Yea I got the whole thread, but I was just wondering what sort of actual things would you need to be done by the people who volunteer to help.. You said you would do the debugging, what does that leave? Checking MSDN docs (if any) for correctness of the code, etc, if it's something that doesnt me requiring access to a box with linux on it, I can do it (mom's office wont allow me to install even lindows on this comp lol)
===== -- Dustin Navea
Minor Contributor, http://www.winehq.com Bugzilla Janitor, http://bugs.winehq.com Network Admin, irc://irc.blynk.net (down)
__________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com
On Thu, Aug 07, 2003 at 06:00:52AM -0700, Dustin Navea wrote:
--- Antony Gelberg antony@antgel.co.uk wrote:
On Wed, Aug 06, 2003 at 06:21:22PM -0700, Dustin Navea wrote:
what kind of help you need? if its running the prog on a windows pc, i
can
do that, if the eula allows for redistribution, or if there is a trial somewhere
Hi Dustin,
Did you not get the first part of the thread? If not, and you can't find it in the archives, I'll repost the juicy bits. Basically whenever I try to install a Windows Installer program, I get quite far, then just before it copies files, I get a dialog box up with error 1628.
Antony
Yea I got the whole thread, but I was just wondering what sort of actual things would you need to be done by the people who volunteer to help.. You said you would do the debugging, what does that leave? Checking MSDN docs (if any) for correctness of the code, etc, if it's something that doesnt me requiring access to a box with linux on it, I can do it (mom's office wont allow me to install even lindows on this comp lol)
I'm new to this, so when I say I'll do the debugging - I stil need someone to tell me what to look at and possible ways to solve the issue. Put another way, I'll do the investigating myself, but I don't know what to investigate!
A
-----Original Message----- From: Antony Gelberg [mailto:antgel@brain.pulsesol.com]On Behalf Of Antony Gelberg Sent: 02 August 2003 02:06 To: Robert Shearman Cc: wine-devel@winehq.org Subject: Re: [antony@antgel.co.uk: .msi files]
Having said that, there are lots of calls like: 0009:Call kernel32.GetStdHandle(fffffff5) ret=4049f965 in the log.
Ignore those. Thread 0009 is the debugger thread and it is just getting a handle for stdout or stderr. If you do a "grep -v 0009 cm4_debug" on the log then that will hide the debugger function calls. Like Greg said, it looks like a cabinet problem as the last two calls before it crashed were FDIIsCabinet and CloseHandle.
Rob
-
Antony Gelberg -
Dustin Navea -
Gregory M. Turner -
Kelly Leahy -
Robert Shearman