Xref: utzoo comp.os.msdos.programmer:3832 comp.windows.ms.programmer:1257 Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!usc!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: 9 Mar 91 19:07:11 GMT References: <1991Mar8.190821.22675@ux1.cso.uiuc.edu> 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: 17 In-Reply-To: tmkk@uiuc.edu's message of 8 Mar 91 04:44:44 GMT Nntp-Posting-Host: slam.interlan.com Yeah, I realized after I posted that I should have explicitly cast Windows to (enhanced mode) Windows. I only use enhanced mode, and was only referring to the default version run on a 386 (enhanced). If you're running standard or real mode, you can preload TKERNEL and off you go. Slow, but off you go. :-) A DPMI version will be nice, because starting/exiting Windows _is_ a real drag. But then again, I feel compiling (actually, linking) in standard mode is more of one.... -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)