relay=-relay=rtlentercriticalsection:RTLleavecriticalsection:rtldeletecriticalsection:initializecriticalsection:interlockedincrement:interlockeddecrement:kernel32 > > (all one line) That should filter out those messages. Could you further clarigy this construct. I'm not exactly sure what to do with that line, and it would be great to get rid of those messages. Thanks. On Mon, 06 Sep 2004 10:33:23 -0700, Duane Clark <dclark@xxxxxxxxxxx> wrote: > Emmanuel Charpentier wrote: > > Duane Clark wrote: > >> > >>Probably what you will need to do is to run the setup something like this: > >> > >>WINEDEBUG=+relay wine setup.exe &> wine.log > >>... > > > > > > Tried that. The resultant file is "only" 467 Mb, mostly made of messages > > similar to : > > 000d:Call ntdll.RtlEnterCriticalSection(4a99f8f0) ret=4a98ccd3 > > 000d:Ret ntdll.RtlEnterCriticalSection() retval=00000000 ret=4a98ccd3 > > I wonder why ... > > That is common, and probably doesn't convey anything useful. It can be > reduced by setting a different environment vaiable, which I have > permanently sent so I forgot to mention it. > > relay=-relay=rtlentercriticalsection:RTLleavecriticalsection:rtldeletecriticalsection:initializecriticalsection:interlockedincrement:interlockeddecrement:kernel32 > > (all one line) That should filter out those messages. > > > > > (Curiously, whent piping through tee, Setup stops with a *different* error > > message, stating that the install engine could not be starded. Heisenbug ?) > > Unfortunately turning on relay traces alters the breakage all too often. > Makes debugging a real pain. Maybe if the relay messages are filtered > out, it will go back to the original problem (but I doubt it). > > >>Hopefully that shows up in one of the files. Open the file and see what > >>was happening before the error message. If it is not clear, try deleting > >>obviously irrelevant or repeated lines, and maybe post a few hundred of > >>the lines before the error message. > > > > Hmmm ... Seems that Wine is detected as being Windows NT, but without > > administrator privileges (btw, the wine config file tells it to eulate > > win98. See posted files ...). Does this rings a bell ? > > It might be worth trying to run Wine emulating win2k. I know several > programs that won't work without that. > > > I can send the relevant 3 file(s) (2 Mb apiece) if you like... > > > > Sure, I'll take a look, though I am by no stretch a Wine guru. Compress > them with bzip2; that should make them substantially smaller. It may > take a significant amount of time for bzip2 to finish the compression, > so give it awhile. > > Elsewhere... > > Resolutioon was OK but a lot of characters were lost (replaced by "?"). > > > > You might be missing a font that the installer was expecting. If you > have a copy of Windows around somewhere, try copying all the fonts from > c:\windows\fonts into the corresponding Wine directory (assuming you > haven't already). > > > [DllOverrides] > > "oleaut32" = "native" > > "ole32" = "native" > > ... > > I would suggest setting most of the DLLs to builtin by default. Had you > tried the installer that way? About the only native ones normally used > should be: > [DllOverrides] > "msvcrt" = "native, builtin" > "mciavi.drv" = "native, builtin" > "mcianim.drv" = "native, builtin" > "msi" = "native, builtin" > "*" = "builtin, native" > > You can always add application specific overrides in the config file for > applications that require it: > [AppDefaults\\dcom98.exe\\DllOverrides] > "ole32" = "native" > > > > _______________________________________________ > wine-users mailing list > wine-users@xxxxxxxxxx > http://www.winehq.org/mailman/listinfo/wine-users > -- James Hawkins _______________________________________________ wine-users mailing list wine-users@xxxxxxxxxx http://www.winehq.org/mailman/listinfo/wine-users
