Mail Archives: djgpp/1999/12/31/02:34:33
> > Try this. Load CWSDPMI, then try to run the V1.x program (it will
> > use the GO32 DPMI support). This takes a pretty different path internally
> > and may be a workaround.
>
> No, It has the same result.
Okay, interesting. I'd have to think about that a bit. It may be an internal
stack size issue, or the driver trashing the upper words of extended
registers.
> BTW, It reports the version as 1.12 maint 3, which seems to be the last
> version of Go32.
The last officially released version :-)
I've provided some updates to people in the past which work under NT, and
lots of other enhancements.
> I'm not quite sure what the driver does, but it is certainly hooking
> int13 into the UMB (where it is loaded) instead of pointing at the ROM.
> Does GO32 make any assumptions about this?
If I had to guess, I'm going to say it's interrupts and the top half of
the extended registers being saved. V2 and CWSDPMI are pretty defensive
about this ...
- Raw text -