Subject: Running on a 486 To: djgpp AT sun DOT soe DOT clarkson DOT edu (gcc) Date: Fri, 21 Feb 92 20:56:18 WET From: Aldur - Creator of the Orb Original-Sender: eet DOT holden AT sequent DOT cc DOT hull DOT ac DOT uk Status: O I've only recently got gcc, and it seems to work fine on my machine, which is a Tandon 386 with 387 and 640k+4Mb extended. I've just passed it on to a collegue who has 486dx machine, and it doesn't want to know! The symptoms are that when he tries compiling, after a brief whir of the disk, the machine locks-up completely. If an invalid command line is given, then it runs ok, and reports the error. The same problem occurs if an executable (go32+a.out) from my machine is run. I've stripped everything out from config.sys/autoexec.bat (except the environment variables), and it does the same. We are both running DOS 5.0. His configuration is: Sonal PC, 486dx running at 33MHz with 4Mb total memory (640k + 3.4M extended). It uses an AMI bios, dated 3/15/91 in the rom, which reports itself as Rev. C on boot-up. Unfortunately I don't know what mother- board he has. Can anyone throw any light on why it wouldn't work? I'm guessing that since the program runs as far as command-line syntax checking, the problem lies in allocating extended memory. Off the top of my head, I can't think of why a 486 should be any different from a 386/387 combination (I even tried the set 387=YES variable). Could it be something to do with A20 gating, and if so, are there any options to select the one that's needed? I couldn't see any options to GO32 that fit into this catergory. Thanks for any help that you can provide! Graham Holden. p.s., is there an ms-dos program that can view the gcc_info files properly?