Xref: utzoo comp.os.msdos.programmer:3810 comp.windows.ms.programmer:1229 Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!rex!samsung!interlan.InterLan.COM!interlan.interlan.com!dave From: dave@interlan.Interlan.COM (Dave Goldblatt) Newsgroups: comp.os.msdos.programmer,comp.windows.ms.programmer Subject: Re: How can I get BCX to work inside of Windows? Message-ID: Date: 8 Mar 91 04:44:44 GMT References: <1991Mar4.150257.422@ccad.uiowa.edu> <1991Mar7.151918.21996@isis.cs.du <1991Mar7.180233.3362@aplcen.apl.jhu.edu> <91066.163143LIBCRN@BYUVM.BITNET> Sender: news@interlan.Interlan.COM (No News is BAD News) Reply-To: dave@interlan.interlan.com Organization: Racal InterLan, Inc., Boxborough, MA (1-800-LAN-TALK) Lines: 31 In-Reply-To: LIBCRN@BYUVM.BITNET's message of 7 Mar 91 23:31:43 GMT Nntp-Posting-Host: slam.interlan.com The question was asked as to how to get BCX to work under Windows. The answer: You can't. The reason: BCX (and BCCX) incorporate built-in DOS extenders. Said DOS extenders are VCPI-compliant. Windows is DPMI-compliant. The two are mutually exclusive. Because BC[C]X is VCPI-compliant, however, it will run under QEMM and the like. Just now Windows. TASM 2.5 _is_ DPMI-compliant, however, and will run just fine under Windows. DPMI support will be forthcoming; however, it was not deemed necessary at release time (according to the reports I've seen; I very much agree with that assessment -- No matter what, compiling under Windows will be slower that compiling under DOS). To speed up BC's operation under Windows, set up a PIF file allocating lots of _expanded_ memory, and have BC run with the /e switch (to use expanded memory). That should speed up its operation significantly. Overall, though, I think you'd be better served by compiling under DOS; it will be _much_ faster. -dg- -- "Hey, Copperfield! * Dave Goldblatt [dave@interlan.com] Suck on this!" * - Penn Jillette, of * (No longer working for, and certainly Penn & Teller * not representing, Racal InterLan)