On Wed, 21 Nov 2001 16:16:32 -0500, Brett Simpson <simpsonb@hillsboroughcounty.org> wrote: >I'm trying to run the 32bit version of Groupwise. So far I can install it >without any major hickups but when I actually start to run the Grpwise.exe >it will prompt me to login to the groupwise mail server but bombs out with >a debug xterm. It appears to be able to connect to the groupwise server ok >for verifying the password. If I put in a bogus one it will tell me I have >used the wrong password. What sort of debuging information should I look >for and how can I obtain debug info? The app use probably winsock, so -debugmsg +relay,+winsock > If I use --debugmsg +relay it put out >a hug amount of stuff. Yes, that's an annoying problem. I have a workaround for it but I did not succeed in getting it into Wine :-/ For now the only way is to gzip the whole trace, put it on a web site and post the address here (after removing your password if it appears in the trace of course) in the hope that someone will examine it. > I would like to learn how to troubleshoot these sort >of things so that I can start working on getting several of our winblows >applications (here at work) running on linux. > >Here's a break down of what I have. >Redhat 7.2 >Wine release 20011004 & the Wine-Devel via RPM >A full Windows 98 second edition install located under /usr/share/wine-c (I >pulled all of this from a ghost image). To do debugging you need to compile from source, at least to be able to change the code. Then you need to have a reference for Windows Api to understand something of what is happening in the traces. At some time it was possible to download a help file from the Borland site. Then there is the msdn on Ms site. Gerard
