Xref: utzoo comp.os.msdos.programmer:3817 comp.windows.ms.programmer:1243 Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!m.cs.uiuc.edu!ibma0.cs.uiuc.edu!ux1.cso.uiuc.edu!usenet From: tmkk@uiuc.edu (Scott Coleman) Newsgroups: comp.os.msdos.programmer,comp.windows.ms.programmer Subject: Re: How can I get BCX to work inside of Windows? Message-ID: <1991Mar8.190821.22675@ux1.cso.uiuc.edu> Date: 8 Mar 91 04:44:44 GMT References: Sender: usenet@ux1.cso.uiuc.edu (News) Organization: University of Illinois at Urbana Lines: 27 In article dave@interlan.Interlan.COM (Dave Goldblatt) writes: > >The question was asked as to how to get BCX to work under Windows. > >The answer: You can't. Wow, really? Guess I'll have to run right home and delete all that stuff from my Development .GRP ;-) Seriously, you most certainly CAN run BCX under Windows. Follow this procedure (which is outlined somewhere in the manuals, but I've forgotten exactly where): 1. Run TKERNEL.EXE from DOS before starting windows. 2. Start windows in either Standard or Real mode. Note: Your statement above is correct *only* if you add the words "in 386 Enhanced mode." 3. Start BCX from the Program manager as you normally would. Works just fine for me. As to why you would want to run BCX from within Windows, I don't know about you, but I often need to switch quickly from "edit the source code" mode to "run the program" mode, and starting/exiting Windows every time gets to be a REAL drag.