🚀 go-pugleaf

On Sat, 18 Mar 2000 01:42:53 +0100, LC01 <se...@smail.uni-koeln.de>
wrote:

>I'm glad to see that people are trying to help seriously, thanks for
>that.
>
>Actually, the crashes occur while playing after some seconds, no
>matter...
>- which location
>- which level
>- which episode
>- if in DOSonly or in a WinShell
>- which setup-options I choose (even NO sounds and lowest resolution)
>- if I slow the PC down in BIOS

We'd like to see the hardware info, particulary the brand and model of
the computer, as well as the soundcard.

>The crash looks like this: game freezes, big letters overwrite the
>actual scene with many numbers in it and the words "code page granular"
>repeatedely.

Run Duke3d in dos mode/window, but run it with the following
parameters:

duke3d > dump.txt

When duke3d crashes, it will leave a simple c:/duke3d> prompt instead
of the entire dump.  Check the first line of dump.txt for the name of
the exception.  

If you can still type commands at the prompt, you might want to type
"mode co80" to fix the screen.  

> The DukeHelpfile says: "granular" means processors too fast. 

No, "granular limit error" means that the DRAM is too fast.  "page
granular" and "byte granular" are standard entries in the type of
register dump. 

You may need to enter the CMOS to change the DRAM settings to a lower
value.  If you are not confortable with such changes, make sure you
carefully record the old values, or to have a friend change the
settings for you.

>And before you ridicule this: you could be next!

Especially if the following three lines are in duke3d.cfg:

ScreenMode = 7
ScreenWidth = 640
ScreenHeight = 480


--
Raymond Martineau - dynamo_...@yahoo.com