At 11:35 PM 8/11/2004 +1200, Bart Oldeman wrote:
There's one FD incompatibility that's been there for some time:
OpenWatcom wd /tr=rsi and wd /tr=cw appear to run just fine when you
debug a program but a crash occurs (black screen, reset only way out, or
invalid opcode) when you exit the debugger.
At 02:22 PM 8/11/2004 +0300, Luchezar Georgiev wrote:
HiNTOS is a DOS extender and Windows emulator that converts Windows
console programs into programs that run in both Windows and DOS. It's the
only one that can convert *fixed* PE executables (WDOSX can't!). It's
available at http://www.alex-h
dos_crit_sect:
mov [_Int21AX],ax ; needed!
pushax ; This must be here!!!
mov ah,82h ; re-enrty sake before disk
stack
int 2ah ; Calling Server Hook!
p
Wed, 11 Aug 2004 23:46:27 +1200 (NZST), Bart Oldeman
<[EMAIL PROTECTED]>:
On Wed, 11 Aug 2004, Luchezar Georgiev wrote:
HiNTOS is a DOS extender and Windows emulator that converts Windows
console programs into programs that run in both Windows and DOS. It's
the only one that can convert *fixed*
On Wed, 11 Aug 2004, Luchezar Georgiev wrote:
> HiNTOS is a DOS extender and Windows emulator that converts Windows
> console programs into programs that run in both Windows and DOS. It's the
> only one that can convert *fixed* PE executables (WDOSX can't!).
Just in case you didn't know, there's
On Tue, 10 Aug 2004, Michael Devore wrote:
> And with that, I'm at the end of the list for finding FreeDOS
> incompatibilities unrelated to kernel, shell, and stand-alone FD utilities
> again.
There's one FD incompatibility that's been there for some time:
OpenWatcom wd /tr=rsi and wd /tr=cw appe
Hello Michael,
Last not least, since it modifies the SFTs, the HiNTOS DOS extender (or
Windows to DOS converter) doesn't work at all in FreeDOS.
This is either a really obscure extender or else also known under a
different name, as even Google Usenet search doesn't pick up a hint of
it. But it
On Wed, 11 Aug 2004, Bart Oldeman wrote:
Hello Bart,
The section is not from me, but it simply is to inform a multitasking
scheduler that something bad happens currently -- in a simple case it's
just an extended InDOS flag.
ASSIGN has to issue these calls, too, I believe to inform a protected mo
