Xref: news-dnh.mv.net comp.os.msdos.djgpp:3436 Path: news-dnh.mv.net!mv!news.sprintlink.net!newsfeed.internetmci.com!news.sesqui.net!rice!news!sandmann From: Charles Sandmann Newsgroups: comp.os.msdos.djgpp Subject: Re: Porting from v1 to v2 Date: Sat, 25 Nov 1995 23:39:48 CST Organization: Rice University, Houston, Texas Lines: 22 References: Reply-To: sandmann AT clio DOT rice DOT edu Nntp-Posting-Host: clio.rice.edu To: djgpp AT sun DOT soe DOT clarkson DOT edu Dj-Gateway: from newsgroup comp.os.msdos.djgpp > - easy : (shame on me) how do I call 387 emulation with v2 ? NT reports "Warning > Coprocessor not present and DPMI setup failed" and cwsdpmi reports "Exiting due > to signal SIGNOFP" Should be automatic. EMU387.DXE contains the emulator. Location found using directory of exe image or environement variable EMU387 (which is defined in djgpp.env). Bugs in early betas in this area. NT is a particular problem - the DPMI server is buggy and limited in this aspect - it won't work. It would be nice if MS would fix it. > - go32 functions : I use some _go32_dpmi_... functions (allocating interrupts), > have they been renamed in v2 ? These functions should continue to work. There are some new lower-level functions which may be a bit faster in V2. > - vga hardware : I use vga IO registers, and NT doesn't let me access them, is > there a way ? (same for IO addresses #40-#43 (timer), #60 (keyboard), #3F8-#3FF > and #2F8-#2FF (serial ports)) NT doesn't allow any port accesses without special driver support. It's DOS compatibility box isn't very compatible.