Commands listed parsed for "incorrect command" can be found at http://www.scoundrelz.net/~moose/wine.parse.log On a side note, I really appreciate the time. Regards, Jade On Thu, 2003-03-06 at 17:30, Duane Clark wrote: > Jade E. Deane wrote: > > The following is the output from the suggested command: > > > > bash-2.05b$ wine --debugmsg +exec "D:\\disk1\\setup.exe" > > fixme:reg:GetSystemInfo not yet supported on this system > > fixme:dosfs:GetDiskFreeSpaceExW no per-user quota support yet > > fixme:ntdll:NtOpenThreadToken > > (0xfffffffe,0x0000000f,0x00000001,0x294de060): stub > > fixme:ntdll:NtOpenThreadToken > > (0xfffffffe,0x00000008,0x00000001,0x29782414): stub > > fixme:ntdll:NtQueryInformationToken (0xcafe,8,0x29782408,4,0x2978240c): > > stub > > fixme:advapi:SetThreadToken (0x0, 0xcafe): stub (NT impl. only) > > fixme:ntdll:NtOpenProcessToken (0xffffffff,0x00000028,0x29782418): stub > > fixme:advapi:LookupPrivilegeValueW > > (L"",L"SeShutdownPrivilege",0x29782420): stub > > fixme:ntdll:NtAdjustPrivilegesToken > > (0xcafe,0x00000000,0x2978241c,0x00000000,0x0,0x0),stub! > > fixme:ntdll:NtOpenProcessToken (0xffffffff,0x00000028,0x29782418): stub > > fixme:advapi:LookupPrivilegeValueW > > (L"",L"SeIncreaseQuotaPrivilege",0x29782420): stub > > fixme:ntdll:NtAdjustPrivilegesToken > > (0xcafe,0x00000000,0x2978241c,0x00000000,0x0,0x0),stub! > > Nothing starting "trace:exec..." so apparently the dialog is coming from > somewhere else. > > I find these next two errors rather odd, since msi.dll is native (there > is no Wine version). I don't know enough to know whether it is a real > problem. > > > err:win32:PE_fixup_imports No implementation for msi.dll.228 imported > > from C:\windows\system\msiexec.exe, setting to 0xdeadbeef > > err:win32:PE_fixup_imports No implementation for msi.dll.222 imported > > from C:\windows\system\msiexec.exe, setting to 0xdeadbeef > > fixme:reg:GetSystemInfo not yet supported on this system > > fixme:ntdll:NtQueryInformationProcess > > (0xffffffff,0x0000001a,0x28670a2c,0x00000004,0x0),stub! > > Since you appear to be willing to go through this step by step :-) I > guess I will continue with how I would go about debugging this. The next > step I would do would be to run: > > wine --debugmsg +relay,+text -- setup &> wine.log > > That will likely create a very large file, perhaps several 100MB. Also, > it will make the program run much slower, so give it awhile. Then > typically I would do > > split --bytes=2m wine.log > > The will create a bunch of 2MB files. I do that just to create files > that are manageable in a text editor. > > Then I would see if any of those files has the error message in it: > > grep "Incorrect command" x* > > Assuming that appears in one of them, I would open that file in a text > editor and try to take a look at what was happening prior to the > message. You could also post a couple hundred lines here if you want. > > > _______________________________________________ > wine-users mailing list > wine-users@winehq.com > http://www.winehq.com/mailman/listinfo/wine-users > _______________________________________________ wine-users mailing list wine-users@winehq.com http://www.winehq.com/mailman/listinfo/wine-users
