Xref: utzoo comp.os.msdos.programmer:3815 comp.windows.ms.programmer:1237 Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!maverick.ksu.ksu.edu!rutgers!psuvax1!psuvm!cunyvm!byuvm!libcrn From: LIBCRN@BYUVM.BITNET Newsgroups: comp.os.msdos.programmer,comp.windows.ms.programmer Subject: Re: How can I get BCX to work inside of Windows? Message-ID: <91067.074952LIBCRN@BYUVM.BITNET> Date: 8 Mar 91 14:49:52 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> Organization: Brigham Young University Lines: 47 ========================================================================= >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] Well that's not entirely true (that you can't run BCX under Windows). If I wasn't such an idiot, I would have found the answer myself in the manuals but I never can seem to find something when I'm looking for it. Anyway, you can't run BCX in Windows ENHANCED mode but you CAN run it in Windows STANDARD mode. Before you run Windows, however, you need to run TKERNEL.EXE (this is all covered on pgs. 4-5 in the User's Guide). I am now running Windows in standard mode so BCX works but I have yet to decide whether its worth it to give up the advantages of enhanced mode Windows just so I can do my compiling from within Windows. Many thanks to those who responded privately to me for answering my question. Next time I promise to search the manuals more thoroughly before I waste bandwidth on the net. -- Cory (libcrn@byuvm.bitnet)