Mail Archives: djgpp/1998/06/02/02:00:32
Eli and John,
I have tried increasing the memory allocated for DPMI but that made no
difference. I also brought my version from work (that runs fine on an NT machine)
on a CD-R and it would not run either.
I enclose the output from a run stoped with cnrl-break (as you have asked, Eli).
Thanks for your help,
Noam Arbel
C:\WINDOWS>gcc -v
Exiting due to signal SIGINT
Control-Break Pressed at eip=0000b9e8
eax=01b63a67 ebx=001a291c ecx=01b63a24 edx=01b63a30 esi=0000ba39 edi=01b63a10
ebp=001a290c esp=001a28f8 program=C:\DJGPP\BIN\GCC.EXE
cs: sel=00a7 base=830eb000 limit=01b67fff
ds: sel=00af base=830eb000 limit=01b67fff
es: sel=00af base=830eb000 limit=01b67fff
fs: sel=0087 base=000080c0 limit=0000ffff
gs: sel=00bf base=00000000 limit=ffffffff
ss: sel=00af base=830eb000 limit=01b67fff
Call frame traceback EIPs:
0x0000b9e8
0x0000bb1b
0x0000bb7e
0x00005983
0x000072ba
0x0000a1bf
0x0000d2ee
John M. Aldrich wrote:
> 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 -