From: Russ Magee Newsgroups: comp.os.msdos.programmer,comp.os.msdos.djgpp Subject: Porting DJGPP DPMI Apps-->Borland C++5.x Date: Thu, 07 Dec 2000 17:38:01 -0700 Organization: Mount Royal College Lines: 25 Message-ID: <3A302D69.8020107@home.com> NNTP-Posting-Host: 142.109.110.34 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Trace: news.mtroyal.ab.ca 976235860 23852 142.109.110.34 (8 Dec 2000 00:37:40 GMT) X-Complaints-To: abuse AT mtroyal DOT ab DOT ca NNTP-Posting-Date: 8 Dec 2000 00:37:40 GMT User-Agent: Mozilla/5.0 (Windows; U; Win95; en-US; m18) Gecko/20001010 X-Accept-Language: en To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Hi all, I'm an Instructional Assistant at my local college who's been asked by a prof to evaluate porting a curriculum in systems programming from DJGPP to Borland C++ 5.xx (mostly because of better integration with Borland's TASM and TDEBUG). All the code examples for assignments use DJGPP with the DPMI interface, and we're wondering if it's feasible to port these to Borland C. (Students will only have to compile DOS apps, no Win32 stuff.) Is this going to be a problem? My (limited) understanding is that DPMI is just an API for accessing DOS calls from protected mode. What changes, visible at the C-language level, will typically have to be made to make a DJGPP/DPMI app compile in Borland C? Specifically, setting up registers, pointer declarations, data struct size limits... (This didn't look to be covered in the FAQ; if it was, my apologies for missing it. I'm a 68000 hack, this x86 stuff is pretty foreign to me.) Thanks, -Russ