Error - template LAYOUT-DATA-WRAPPER not found

A configuration error was detected in the CGI script; the LAYOUT-DATA-WRAPPER template could not be found.

Error - template STYLE-SHEET not found

A configuration error was detected in the CGI script; the STYLE-SHEET template could not be found.

Error - template SUB-TOP-BANNER not found

A configuration error was detected in the CGI script; the SUB-TOP-BANNER template could not be found.
Subject:
From:
Hugh Vandervoort <[log in to unmask]>
Reply To:
PCSOFT - Personal Computer software discussion list <[log in to unmask]>
Date:
Sat, 3 Jul 1999 04:12:27 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (62 lines)
*************************Reply*********************************************
I was premature in declaring SETI@home to be working-it now crashes after
1-3 hours of operation, and when it begins crashing it gives me the BSOD
after a minute or two. I wondered about heat, but all seems to be well
inside the box, and lengthy sessions of Descent run flawlessly.
I am not certains what approach to take.
****************************************************************************
************************************************
I am not certain how the FIC handles aperture (the manual is choppy English
and quite foggy on the issue), but for Riva 128 cards, set aperture at
lesser of system memory or max aperture setting available in BIOS (64M
unless system RAM is less, then set at system RAM).  For most other cards,
set from 4M to 16M range, typically based on system memory and video card
driver recommendations.  Anyone else know what the aperture actual is /
does?
The uncertified driver is not a problem if the system runs fine in 3D & GL.
Does Descent 3 still crash with the new BIOS setting?
Martin Kurr
email [log in to unmask]
> From:         Hugh Vandervoort[SMTP:[log in to unmask]]
> Subject:      Re: [PCSOFT] Descent 3/Seti@Home
>
> *************************Reply********************************************
> **
> Thank you. I had already run DXdiag-the only anomaly was an uncertified
> driver, which is allgedly Creative's latest. I did look at the BIOS,
> however, and noticed that the primary display was set tp PCI. I changed
> this
> to AGP, and SETI is apparently running OK now.
> I got this card on the recommendation of a friend, and it seems to perform
> very well, but there is nothing in the material supplied about aperture
> size-what is it? If the BIOS setting was wrong, why haven't I had other
> troubles ?
> **************************************************************************
> **
> Run DirectX diagnostics.  I had Seti crashing with Riva 128ZX AGP on
> similar
> system until I installed DirectX 6 and fixed PCI2AGP bridge in device
> manager.  DirectX diagnostics showed a glitch that pointed me this route.
> Also make sure you set BIOS for FIC mobo to match Banshee recommendations
> (AGP 1x vs. 2x, Aperture size).  For example, with the Riva card, AGP 2x
> with 64M aperture, but Viper550 uses 1x and 4M in BIOS best on the FIC
> board.
> Martin Kurr
> email [log in to unmask]
> > From:         Hugh Vandervoort[SMTP:[log in to unmask]]
> > Subject:      Re: [PCSOFT] Descent 3/Seti@Home
> > System is Win 98, AMD K6-2/350, Blaster Banshee AGP,FIC  VA 503+ 64 Megs
> > PC100 RAM.  Ever since I installed Descent 3,the SETI@Home screensaver
> > crashes after a few seconds of operation. I've also had problems with
> > Descent 3 crashing, but that seems to have been solved (New Video
> > Drivers).  I'm not getting any error messsage, just a reboot whenever
> the
> > program runs.  Has anyone else experienced this?

                         PCSOFT's List Owner's:
                      Bob Wright<[log in to unmask]>
                       Drew Dunn<[log in to unmask]>

         PCSOFT only works if you contribute. Send your messages
              to be posted to: [log in to unmask]

ATOM RSS1 RSS2

LISTSERV.ICORS.ORG Secured by F-Secure Anti-Virus CataList Email List Search Powered by LISTSERV