Path: utzoo!attcan!uunet!cs.utexas.edu!sdd.hp.com!uakari.primate.wisc.edu!aplcen!news From: tcs@mailer.jhuapl.edu Newsgroups: comp.binaries.ibm.pc.d Subject: Re: Borland BGI question Message-ID: <1990Dec10.201548.4671@aplcen.apl.jhu.edu> Date: 10 Dec 90 20:15:48 GMT References: <1990Dec7.121658.25371@aplcen.apl.jhu.edu> , Sender: news@aplcen.apl.jhu.edu (USENET News System) Organization: Johns Hopkins University Lines: 25 In article , dd26+@andrew.cmu.edu (Douglas F. DeJulio) says: > >I've gotten several programs that use BGI files and can choose between >different display types when they start up. They're *supposed* to >auto-detect the correct display type and use it. On my machine they >don't. I've got an AT&T PC6300 which should use the ATT400 BGI >module. Programs that autodetect invariably choose CGA. Ugh. I own >Turbo-C and I've checked the manuals, but I couldn't find a way to >force a particular display type at run time. Can it be done with an >environment variable or something? Any help would be appreciated. >-- >Doug DeJulio >dd26@andrew.cmu.edu If the programs are ones that you didn't write, then you probably can't fix it. The programmer probably looked over the code and decided that *he didn't want to try to implement the displaytype and if it is detected, default to CGA instead. In the programs that I write I try to default to a driver that I can write in. Of course, I always link in the drivers and don't want to have an 80k program that prints "Hello, world!" :) :) :) Carl Schelin tcs@mailer.jhuapl.edu