Diablo 2 with Battle.net - another step closer again

[wine at scabserver.com]

I've tried your patch, it seems to look about right, but when I start wine 
with --dt -debugmsg +all, not all messages are inital suppressed, I can't see 
why, and pressing alt + F12 didn't start debuging more.... also I'm not sure 
why but wine performs differently with -debugmsg +all than without, I'm not 
talking about the slowdown, I was expecting that, but for example DLoad.exe 
normaly comes back with a box indicating that it can't find the file it's 
looking for with a ok button.  But with the debugin on it dosn't get that far, 
it get's to about 27Mb into debuging, and then just sits there, I suppose it 
could be just that something inside the code is timing out waiting for 
something else but I don't know if that'd be in the wine code or in DLoad.exe, 
probably the latter but I don't know my way arround the Wine source code well 
enough to work this out (I'm learning but finding it slow <G>)
With regards to the problem at hand, having looked at what the exe's do in 
windoze it seems that wine is doing everything that windoze is with 
game_crk.exe, the problem is something to do with DLoad.exe, I'm not sure what 
seems to be related to the way it's trying to execute game_crk.exe, maybe cos 
DLoad is the same for 98/2k but there are different game_crk.exe files for 
each.  I can't seem to get either to work tho, maybe it's the way DLoad.exe is 
trying to work out how to handle the different OS's?  what OS would wine look 
like, is it trying to be all of them and therfor upseting things?  anyway 
that's all my thoughts for the moment.
Rob

Quoting gerard patel <g.patel at wanadoo.fr.invalid>:

> On Sat, 11 Aug 2001 20:12:09 -0400, Robert Laverick
> <csujo at scabserver.com> wrote:
> 
> <snip>
> >looking, is there anyway to start and stop debug messages while the app
> is 
> >running?
> 
> Try this patch (beware of folding lines). Traces you select from
> the command line are started by using Alt F12
> 
> Gerard
>