[Prev][Next][Index][Thread]
Re: Windows 3.1 PIF for Executor/DOs
>>>>> "Josh" == Josh Vanas <jdvanas@iac.net> writes:
Josh> Yes....Win 3.11 Does cause Executor to "lock" and the only
Josh> solution is to ctrl-alt-delete ( that I have found ). This
Josh> puts a real damper on Multi-tasking. I was wondering if
Josh> Cliff could shed some light on the subject? Are there plans
Josh> ( WAYS ) to fix this problem?
Josh> With my knowledge of how windows works, I wouldn't be
Josh> supprised if Cliff said that the problem can't be solved.
Josh> It is possible that ARDI has put Executor in a video mode
Josh> that Windows doesn't recgonize as valid, and therefore, is
Josh> unable to restore the mode. What I don't know is if
Josh> Executor can "know" that it has been swaped, and then reset
Josh> its own video mode when it returns. Couldn't you put some
Josh> kind of 386Enh driver in windows to track such events?
Hot-keying back and forth with SVGA apps in Windows has problems,
because Windows doesn't know how to save and restore all SVGA state
appropriately. I don't think this is an Executor problem.
The UniVBE authors just released a free package that lets programs
interact nicely with Windows (hotkeying back and forth without
trashing the screen, etc.). It may not turn out to be useful, but
I'll look into it.
-Mat
References: