www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1998/06/01/21:15:27

From: "John M. Aldrich" <fighteer AT cs DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: gcc seams to start, but then... nothing, really *NOTHING* !
Date: Mon, 01 Jun 1998 21:11:46 -0400
Organization: Two pounds of chaos and a pinch of salt.
Lines: 61
Message-ID: <35735152.6BA7@cs.com>
References: <199806012237 DOT AAA06390 AT facteur DOT in DOT grolier DOT fr>
NNTP-Posting-Host: ppp122.cs.net
Mime-Version: 1.0
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

Yann Coupin wrote:
> 
> Here is my problem (if the subject wasn't explicit enought <g>). Whenever I
> lauch gcc from rhide or directly from the command line it start, make a
> small amount of disk access (maybe it's even only windows swap mechanism)
> then it does absolutly NOTHING, this can last up to ten minutes (maybe more
> but I wasn't patient enough since on the P200 I have at work it only need 1
> second or so to compile the same .C file (btw I have a K6-233 with 64Mo
> RAM). I've tried tweaking my autoexec.bat & config.sys file without
> success. So, to quote Princess Leila "help me djgcc list member, you're my
> only help" :-)

It's the second time in two weeks that somebody's reported gcc locking
dead on their system...

Make sure that you have set Windows to provide enough DPMI memory to DOS
applications.  Type 'go32-v2' from the DOS prompt and look at what it
says.  If the total of free physical and virtual memory don't add up to
64 MB, open the MS-DOS Prompt properties sheet and manually set DPMI
Memory to 65535 KB.  Apply and close, and try running gcc again.

Also... please describe the exact command line you are using with gcc,
and try using the '-v' and '-Q' options together.  If you do get any
output from this combination, please capture it with the 'redir' utility
and post it here.

> env strings
> -----------------------------
> PROMPT=$p$g
> winbootdir=C:\WINDOWS
> COMSPEC=C:\WINDOWS\COMMAND.COM
> TMP=d:\temp
> TEMP=D:\temp
> PATH=C:\DJGPP\BIN;C:\WINDOWS;C:\WINDOWS\COMMAND
> windir=C:\WINDOWS
> BLASTER=A220 I5 D1 H5 P330 T6 E620
> ------------------------------
> NB: then temp directory exists on the disk

If that's really your environment, then the DJGPP environment variable
is never being set.  Is this an exact copy of the output of 'set' run
from your MS-DOS prompt?  Make sure that the autoexec.bat that you
copied is in fact the one that gets run when Windows 95 boots.  To test
it, you can press F8 after you see the "Starting Windows 95..." message
on bootup and step through your config.sys and autoexec.bat.

Some environment problems can be difficult to diagnose.  You might want
to try out my DJVERIFY diagnostic utility, which is designed to detect
and recommend solutions for installation problems.  It can also generate
a complete system report suitable for posting here.  The link is
available from my web page, mentioned below.

hth!

-- 
---------------------------------------------------------------------
| John M. Aldrich, aka Fighteer I  |     mailto:fighteer AT cs DOT com     |
|      ICQ UIN#:  7406319          |   http://www.cs.com/fighteer/  |
|    ObJoke:  If Bill Gates were a robber, not only would he        |
|     shoot you, but he'd send you a bill for the bullets.          |
---------------------------------------------------------------------

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019