Date:	Sat, 12 Dec 1992 15:32:08 MST
From:	"Bob Hood" <thor AT arrakis DOT denver DOT co DOT us>
To:	csaba AT vuse DOT vanderbilt DOT edu
Cc:	djgpp AT sun DOT soe DOT clarkson DOT edu
Subject:	Re: SUIT problems

Believe it or not, Csaba A. Biegl wrote:
>
> This is in response to various questions about SUIT.
> 
> > Hello,
> > I have trouble in running the port of SUIT on DJGPP. I am running DJGPP
> > 1.09 on a 486 clone with 386MAX as memory driver. I compile the 3 examples
> > of the tutorial with no warning but they all hang my computer when staring
> > them. I tried with go32 1.09 and with go32 1.09 patched by Csaba.
> > Is it a problem with go32, 386MAX or do I missed something?
> >                            ^^^^^^
> > (I am running with a Tseng 4k and all the tests coming with Libgrx compile
> > and run fine).
> > Thank's for your help.
> > Jean-Francois Rouanet.
> 
> My patched GO32 fixes the keyboard problem only for non-VCPI (no EMS)
> situations. Try without 386MAX or using the 1.08 extender. Does the 
> mouse work? If so then the computer did not really hang -- the program
> just does not get the keystrokes.
> 
> > Hi everyone
> > 
> > I just loaded down the SUIT port for djgpp, installed
> > it on my PC and ran the makefile. After all was done
> > (without any problems !!!) i started the tutorial demo
> > progs (demo 3cell ..) awaiting the wonderful things that
> > might come. But the only thing happend was that the color
> > of the letters on the screen turned form gray to orange
> > and i had to reboot the computer. (im using go32 1.08)
> > So, what did i wrong ???
> > 
> > Thanks in advance for any suggestions
> > 
> > peter
> 
> The orange text is quite normal for error messages. SUIT happens
> to initialize its color table in a way that color index 7 (the
> regular low-intesity white DOS text color) is mapped to orange.
> AFter this anything written to the screen using DOS and the BIOS
> appears in this color. The text on the screen should be some fatal
> error message from the extender or the program. If unreadable
> (Some SVGA BIOS-es don't handle text output properly in HiRes modes)
> try redirecting both the standard output and the standard error to a
> file. Once you know what the problem is, correct it. Things which
> can possibly go wrong:
>  
>    no 387 and 387 emulator. (SUIT uses some floating point arithmetic)
>    wrong graphics driver, card (try the GRX tests, if you haven't done so)
>    make sure you are using GRX version 1.02.
>    make sure that the GRX font path is set up properly.
> 

Andreas Wandelt also writes:

> On my system (486/33, 8MB, ET4000, GO32 1.08) all the SUIT demos work fine
>
> (and they are looking REAL GOOD :-) .
> However, i also had this text-turned-orange-and-computer-hung-up problem
> once. It turned out that i had just forgotten to run my gcc-init batch
> file, which sets all the necessary environment variables for gcc and go32.
> When i get back
> home, i can try and find out which setting (or rather, which omission)
> causes that kind of error.

I'm sorry, but no dice.

I am running on a '486/33, 8MB, Diamond SpeedStar SVGA (TSENG4K), DJGPP 1.08,
QEMM 6.02 (I cannot find a version on my GRX library, but I got it at about
the same time that I downloaded DJGPP 1.08), and I have 5MB available on
my hard drive.

Here is my environment (these variables are *always* in my environment):

rem DJGPP 1.08 variables
set COMPILER_PATH=/develop/djgpp/bin
set C_INCLUDE_PATH=/develop/djgpp/include
set CPLUS_INCLUDE_PATH=/develop/djgpp/cplusinc;/develop/djgpp/include
set OBJC_INCLUDE_PATH=/develop/djgpp/include
set OBJCPLUS_INCLUDE_PATH=/develop/djgpp/include
set LIBRARY_PATH=/develop/djgpp/lib
set TMPDIR=/windows/temp
set GO32TMP=/windows/temp
set GO32=ansi driver /develop/djgpp/drivers/tseng4k.grd gw 800 gh 600
       tw 80 th 50 nc 256
set BISON_SIMPLE=/develop/djgpp/lib/bison.simple
set BISON_HAIRY=/develop/djgpp/lib/bison.hairy
set FLEX_SKELETON=/develop/djgpp/lib/flex.skeleton
set GRXFONT=/develop/djgpp/contrib/libgrx/fonts

(note that the above "GO32" line was re-formatted in the editor for clarity, 
but is one entire line in the environment)

I experience the *exact* same symptoms.  I have tried changing my driver
(VGA.GRD), running with and without QEMM, recompiling GRX and then SUIT.

I can run the GRX "test" applications with no difficulties with the above 
settings.  With SUIT, I get the same "orange" glow as the other individuals, 
but I never get into graphics mode and nothing appears on my screen. I have 
tried redirecting stderr and stdout with 4DOS (">& demo.err" and ">&> 
demo.err"), but because the computer stops and I cannot end the program, the 
output is never flushed and I end up with a 0-length file after a reboot.

It's probably some kind of configuration setting, I'm sure (since somebody
else with a similar setup is running it).  I have spent more than a full day
trying to figure this thing out, and it is really becoming frustrating.

Bob

P.S. Sorry for the size of this message, but I am really looking forward to
seeing SUIT, and I'd like to find a solution to this problem.
--
Bob Hood   thor AT arrakis DOT denver DOT co DOT us      H: 303-980-8392   W: 303-623-2180
-----------------------------------------------------------------------------
                  I'm not an expert, but I play one at work....
-- 
Bob Hood   thor AT arrakis DOT denver DOT co DOT us      H: 303-980-8392   W: 303-623-2180
-----------------------------------------------------------------------------
                  I'm not an expert, but I play one at work....

- Raw text -