Re: signaling unix threads

2004-11-07 Thread Jukka Heinonen
cit signal blocking in protected code paths. But since there are quite a few ways for implementing multiplexing and fixing the resulting locking issues I probably just wait and see what the implementation turns out to be. -- Jukka Heinonen <http://www.iki.fi/jhei>

Re: signaling unix threads

2004-10-29 Thread Jukka Heinonen
fix dosvm issues with a simple mechanism and not worry about anything else. So, feel free to submit a patch, if it is simple enough it should get accepted or at least you should get some suggestions how to change the patch in order for it to get accepted. -- Jukka Heinonen <http://www.iki.fi/jhei>

Re: Disable DPMI

2004-09-22 Thread Jukka Heinonen
t does not use iret (needs changes in insert_event_check, too, because signal SIGUSR2 may be received after any instruction) Anyway, I'm quite busy for at least a few days and I really need to go sleeping right now, so I would appreciate it if you or someone else has a little time fo

Re: Drowning in FIXMEs...

2004-09-05 Thread Jukka Heinonen
much but at least I would not have pending stuff in my computer. -- Jukka Heinonen <http://www.iki.fi/jhei>

Re: int21 handling

2003-11-10 Thread Jukka Heinonen
before. So, if you want to submit patches that migrate code to winedos, I won't really mind, as long as you try to either fix or comment obviously broken code (Ralf Browns Interrupt List is really helpful) and you try to make as much use as possible of existing winedos code. -- Jukka Heinonen <http://www.iki.fi/jhei/>

Re: int21 handling

2003-11-10 Thread Jukka Heinonen
ctly with illegal drives and 8-bit character set but it works fine with wide character set. -- Jukka Heinonen <http://www.iki.fi/jhei/>

Re: Breakage in 'priviledged instructions' handling.

2003-10-11 Thread Jukka Heinonen
nyway, even with some performance issues, it looks like instruction emulation is needed for supporting some pure Win95/98/ME programs. It would seem a bit strange we try very hard to support Win31 and WinNT based programs but not those. -- Jukka Heinonen <http://www.iki.fi/jhei/>

Re: Crash in 16-bit code

2003-10-11 Thread Jukka Heinonen
On Tue, Oct 07, 2003 at 10:26:05PM +0200, André Johansen wrote: > * Jukka Heinonen wrote: > | Well, you could try using +relay debugmsg flag > > Here are some lines around the crash-point; compare it to the previous > one (I made sure some output from that one was prese

Re: Protected mode interrupt problem

2003-10-07 Thread Jukka Heinonen
that you mention it, the patch indeed does lazy intialization. I really should try to avoid doing anything that requires thinking when I'm tired... So, patch looks correct, after all and I don't think setting task vectors would be useful, either. -- Jukka Heinonen <http://www.iki.fi/jhei/>

Re: Crash in 16-bit code

2003-10-07 Thread Jukka Heinonen
an exception that is caught by winedbg. This makes running DOS programs under winedbg next to impossible. Perhaps winedbg has some command to ignore those exceptions or that kind of command should be added... -- Jukka Heinonen <http://www.iki.fi/jhei/>

Re: Crash in 16-bit code

2003-10-07 Thread Jukka Heinonen
her dlls would require some cleaning up, too. -- Jukka Heinonen <http://www.iki.fi/jhei/>

Re: Protected mode interrupt problem

2003-10-07 Thread Jukka Heinonen
ed so that those vectors are properly initialized (possibly lazily) at program startup and when new task is created (are they copied from another task or reset to default values?). And, I don't think TASK_GetCurrent() should be called from winedos and I thought use of WINE_PACKED was unnecessary and deprecated. -- Jukka Heinonen <http://www.iki.fi/jhei/>

Re: Crash in 16-bit code

2003-10-07 Thread Jukka Heinonen
On Tue, Oct 07, 2003 at 12:29:15AM +0200, André Johansen wrote: > * Jukka Heinonen wrote: > | Okay, I have posted a patch to wine-patches that > | should have fixed this bug. Let's see if that is > | the case. > > Thanks -- I've tested it, and it seems to get furt

Re: Crash in 16-bit code

2003-10-07 Thread Jukka Heinonen
EVICE" from 32-bit linear code. This is either some kind of copy protection scheme or the program really wants to call PCI BIOS, which is something I thought event Windows 95 would not allow. Have you tried running the program using different Windows versions (NT or later)? -- Jukka Heinonen

Re: Crash in 16-bit code

2003-10-06 Thread Jukka Heinonen
ould be helpful. -- Jukka Heinonen <http://www.iki.fi/jhei/>

More DOS regressions due to instruction emulation changes

2003-09-17 Thread Jukka Heinonen
x27;t probably want to decide, even if I had more time available for this. A better fix for protected mode programs would be welcome, too. -- Jukka Heinonen <http://www.iki.fi/jhei/>