🚀 go-pugleaf

I don't suppose you got another 2d card you could try.....

--
Neill Smith
Lincolnshire
England

Email Neill@nrsmith.freeserve.co.uk

scorch56 heeft geschreven in bericht
<SNIP
>The reason I'm posting this in the 3dfx.opengl group this time as well
>is because I hope to get a Monster card soon (I have a pentium non-MMX
>166 and a Voodoo II would be over-kill) and the people at Diamond have
>always assured that the old Monster works quite nicely with an old
>Stealth card; but i was wondering if anybody already had that setup
>and could confirm it for me. Also; as always... I was hoping anybody
>with a Stealth/M3d combo could tell if they ever had any problems.
>I've almost given up; and although a fix would be great; I'd just like
>to know that it does happen so I'd know I'm not alone in this. Oh
>yeah; I've tried shifting the boards around in all the PCI slots as
>well... and no, there aren't any IRQ conflicts under Device manager
>either. Thanks to everyone for your attention.

Hi,

I used to have a Diamond stealth 3D2000 2MB ('old version' OEM) and a
Monster 3D. Later I upgraded the stealth to 4MB. Never had any problems with
this setup in different motherboards (Intel Zappa, Soyo HX and TX boards and
Abit AX5). Also a Monster 3D II card will work fine with the stealth.

greetz,

Raapionix

Hi!

Have you tried 3DCC (3D Control Center)?
It's a utilty that lets you choose which card should be used for D3D.
I use it for my Matrox Mystique 220 / Matrox m3D combination, so I know for
sure that the Mystique enhanced games use the Mystique and the PVR games use
the m3D.

Leo

I had a similar problem with Quake 1 crashing after about 15 minutes
of play.  It turned out that my sound card, Creative Ensoniq AudioPCI,
was configured for DOS legacy support and was sharing and IRQ.  I
disabled the interrupt sharing, and that seemed to eliminate the
problem.  However, I never had a problem with Quake 2.  My system was
(I now use a Banshee) : VX chipset, AMD K6200, 80 MB RAM, Stealth
S220, m3D.  Incidentally, the Quake 1 framerates with the m3D were mid
20's.  With a Banshee card I now get high 40's to low 50's.

>On Sun, 13 Dec 1998 19:49:36 GMT, burn@babyburn.com (scorch56) wrote:

>Every couple of months I wander into these groups and ask if anyone
>who has the same setup as me has had this problem. As of yet; I
>haven't gotten any replies. I can't be the only person in the world
>with these two cards together though.
>
>Here's my problem... I have a 1st pre-1st generation; semi-quasi;
>pseudo- 2D/3D card the old Diamond Stealth 3D 2000 w/ 2 megs of ram
>(the very 1st model with the original Virge chip). I also have a
>Matrox M3d accelerator card with 4 mb of dedicated texture ram (uses
>the PCX2 Power VR chip).
>
>Normally; these two cards work together just fine. They rarely
>conflict; and when they do... it's usually game specific and results
>in the game recognizing the Stealth when I want to use the Matrox for
>D3D.
>
>My problem is... as far as I can tell... I cannot ever play any game
>based on the Quake I or Quake II engine for more than 10 minutes or so
>without it crashing. Sometimes it just exits out to my desktop with no
>errors all of a sudden. Sometimes there is an error message; but with
>no set pattern. Sometimes the damn thing just re-boots the PC on it's
>own. I get the same exact behavior with Quake I; Quake II; and now...
>with both SiN and Half-Life! I  have plenty of RAM (64 megs) and
>plenty of free space on my HD for virtual memory (3 gigs); so I don't
>think it's a memory issue. I used to think it only happened with the
>GL versions; but it seems to more prerequisited on just any Quake
>engine game. Oh yeah... Hexen and Heretic too; of course.
>
>I have gone round and round with Activision; Matrox and the Diamond
>people about this. No one seems to have a clue. I have tried using the
>Matrox M3d mini-gl drivers for Quake games; it makes no difference
>either. I have tried using non-Matrox and non-Stealth drivers and just
>used the generic S3 Virge and Power VR drivers respectively...S.O.S..
>I'm beginning to think it's just a compatibility conflict between the
>two cards that only manifests itself when trying to play these types
>of games. As I remember; I never had any problem like this before I
>got the M3d and just ran the Diamond alone. The M3d is not a
>pass-through card; it is a stand-alone accelerator though. I could
>chuck the M3d and go back to the Diamond; but then these games look
>pretty crappy using it; and forget playing GL versions. The Matrox
>definitely has better D3D graphics.
>
>The reason I'm posting this in the 3dfx.opengl group this time as well
>is because I hope to get a Monster card soon (I have a pentium non-MMX
>166 and a Voodoo II would be over-kill) and the people at Diamond have
>always assured that the old Monster works quite nicely with an old
>Stealth card; but i was wondering if anybody already had that setup
>and could confirm it for me. Also; as always... I was hoping anybody
>with a Stealth/M3d combo could tell if they ever had any problems.
>I've almost given up; and although a fix would be great; I'd just like
>to know that it does happen so I'd know I'm not alone in this. Oh
>yeah; I've tried shifting the boards around in all the PCI slots as
>well... and no, there aren't any IRQ conflicts under Device manager
>either. Thanks to everyone for your attention.

scorch56 wrote:
> Here's my problem... I have a 1st pre-1st generation; semi-quasi;
> pseudo- 2D/3D card the old Diamond Stealth 3D 2000 w/ 2 megs of ram
> (the very 1st model with the original Virge chip). I also have a
> Matrox M3d accelerator card with 4 mb of dedicated texture ram (uses
> the PCX2 Power VR chip).

D3D is a moot point when playing QuakeII. It *ONLY* uses the M3d
assuming you have powervr gl selected. It does not use D3D at all. Any
problems in QuakeII are either 1) because you have a virus, your win95
is screwed up whatever, or 2) Your matrox m3d card is toast or
incompatible (hardware problems) with some other aspect of your system.

l8r
Ryan

-- 
-+-+--+-+-> http://home.bc.rogers.wave.ca/borealis/ryan.html <-+-+--+-+-

 Ryan Haksi                     "Hah, that makes six shots I counted!"
 cryogen@infoserve.net              -famous last words
                                "I re-loaded..." -the rebuttal

Oh yeah; I've been using 3D control center for a long time. It works
most of the time; but sometimes... even when I switch D3D support to
the M3d; in the game... all it recognizes and uses id the Stealth's
D3D. And sometimes; it's just the opposite. You see... I can disable
the M3d's D3d support using the control center. Waht I'd like to do;
and I've asked Diamond... it can't be done... is to totally disable
all of the Stealth's 3D support and just use it as a 2D card (which it
works excellent at). But it's all or nothing when it comes to the
stealth.


On Sun, 13 Dec 1998 23:11:42 +0100, "Leo Middendorp"
<mad@DEL-THIScomports.com> wrote:

>
>Hi!
>
>Have you tried 3DCC (3D Control Center)?
>It's a utilty that lets you choose which card should be used for D3D.
>I use it for my Matrox Mystique 220 / Matrox m3D combination, so I know for
>sure that the Mystique enhanced games use the Mystique and the PVR games use
>the m3D.
>
>Leo

Well... I think I'm gonna' get an old Voodoo I. I only have a pentium
166 and I hear that a Voodoo 2 isn't utilized to it's full capability
on such a machine.

You see... I use 3D control center; and while it can utilize 3 cards;
I just don't think there is a 3 card solution that covers all the
APIs! It allows for one Primary card (2D or 2D/3D; doesn't matter);
one stand alone accelerator (like my M3d) and one pass-through
accelerator (like a Voodoo card). But all 3D Control Center does is
let you pass along the D3D work to any card (most of the time). If I
were to get a Monster card; that would take care of 3DFx or glide; but
even if I kept all three of the cards it still wouldn't solve my
openGL problem because none of them do so well at openGL.

I think I have to go this route... buy a Monster; that will take care
of 3DFx. Chuck the M3d (Which I really hate to do because it
definitely does D3D better than the Stealth) and try and upgrade the
Stealth to 4 megs for now until I can get a better 2D/3D card (like a
Stealth based on the Verite or a Riva card). OOORRR... I can keep the
M3D and chuck the Stealth and get a good quality 2D only card as my
primary driver. Of course; like I said... none of these will cure my
OpenGL-Quake based game woes since none of these cards do OpenGL very
well. But even though neither of the two cards I have right now are
good GL cards; I still can't help but think that their co-existing on
my machine is the cause of my Quake-based engine game problems. I
mean... I can't think of what else it could be. 

After all... all the game and card manufacturers say that the games
should work when used with their cards alone. Just to try something
different; I did switch SiN over to "software rendering" today and
played it for a half hour without a crash. I'm at a loss for words...
or ideas... once again... <sigh>.


On Sun, 13 Dec 1998 22:40:49 +0100, "Raapionix"
<news@raapionix.demon.NS> wrote:

>
>scorch56 heeft geschreven in bericht
><SNIP
>>The reason I'm posting this in the 3dfx.opengl group this time as well
>>is because I hope to get a Monster card soon (I have a pentium non-MMX
>>166 and a Voodoo II would be over-kill) and the people at Diamond have
>>always assured that the old Monster works quite nicely with an old
>>Stealth card; but i was wondering if anybody already had that setup
>>and could confirm it for me. Also; as always... I was hoping anybody
>>with a Stealth/M3d combo could tell if they ever had any problems.
>>I've almost given up; and although a fix would be great; I'd just like
>>to know that it does happen so I'd know I'm not alone in this. Oh
>>yeah; I've tried shifting the boards around in all the PCI slots as
>>well... and no, there aren't any IRQ conflicts under Device manager
>>either. Thanks to everyone for your attention.
>
>Hi,
>
>I used to have a Diamond stealth 3D2000 2MB ('old version' OEM) and a
>Monster 3D. Later I upgraded the stealth to 4MB. Never had any problems with
>this setup in different motherboards (Intel Zappa, Soyo HX and TX boards and
>Abit AX5). Also a Monster 3D II card will work fine with the stealth.
>
>greetz,
>
>Raapionix
>
>

No... but I've thought of that. See my reply to Raapionix below. I'm
actually thinking of just chucking the Stealth and getting a real good
quality 2D only card as my primary driver (Actually; they are getting
very hard to find anymore). Then I get a Voodoo for glide support and
keep my M3d for it's excellent D3D support. But that still leaves me
without a decent card for OpenGL; which was my original problem in the
first place. My head hurts... I'm so confused! ;-)

On Sun, 13 Dec 1998 20:23:30 -0000, "Neill Smith"
<neill@nrsmith.freeserve.co.uk> wrote:

>I don't suppose you got another 2d card you could try.....

I am also cruising these groups looking for answers.  I played the first
half of Half-Life with almost no problems, with my ATI All-InWonder card,
and standard Win98 drivers.  Then I tried to update the drivers.  I have
spent longer than I played the game to make them (kinda) work.  Very similar
problems.
1.  The properties on the video card seem to require, that I allow the
driver to select the refresh rate.  If I select it myself, it crashes
anytime I need it to work away from the "required" refresh rate.  I believe
the driver uses more or less video memory depending on the refresh rate, and
doesn't properly allocate / de-allocate it.
2.  D3D doesn't work anymore for more than about 10-15 minutes.  Then crash.
Not a heat problem as the video chip never gets more than "warm"
3. I have heard rumors that DirectX 6.1 is a possible answer, but you must
be a MSDN DirectX beta tester to get in to download them.
4.  According to my DirectX diagnostic tool, DirectX 6 is OK, but I notice
that Hardware rendering of the DirectX Test screen is only about 10% faster
than the software version of the test.  Kind of makes me wonder what my
hardware is doing for me. (not much)
5.  The decals in Half life never work properly with all the versions of
OpenGL / D3D / beta that I can find (5 - 6 different drivers.)  The Win98
drivers work OK with D3D, but are so slow as to make software rendering the
prefered way to play.

scorch56 <burn@babyburn.com> wrote in message
news:3675143e.39447663@news.supernews.com...
>Every couple of months I wander into these groups and ask if anyone
>who has the same setup as me has had this problem. As of yet; I
>haven't gotten any replies. I can't be the only person in the world
>with these two cards together though.
>
>Here's my problem... I have a 1st pre-1st generation; semi-quasi;
>pseudo- 2D/3D card the old Diamond Stealth 3D 2000 w/ 2 megs of ram
>(the very 1st model with the original Virge chip). I also have a
>Matrox M3d accelerator card with 4 mb of dedicated texture ram (uses
>the PCX2 Power VR chip).
>
>Normally; these two cards work together just fine. They rarely
>conflict; and when they do... it's usually game specific and results
>in the game recognizing the Stealth when I want to use the Matrox for
>D3D.
>
>My problem is... as far as I can tell... I cannot ever play any game
>based on the Quake I or Quake II engine for more than 10 minutes or so
>without it crashing. Sometimes it just exits out to my desktop with no
>errors all of a sudden. Sometimes there is an error message; but with
>no set pattern. Sometimes the damn thing just re-boots the PC on it's
>own. I get the same exact behavior with Quake I; Quake II; and now...
>with both SiN and Half-Life! I  have plenty of RAM (64 megs) and
>plenty of free space on my HD for virtual memory (3 gigs); so I don't
>think it's a memory issue. I used to think it only happened with the
>GL versions; but it seems to more prerequisited on just any Quake
>engine game. Oh yeah... Hexen and Heretic too; of course.
>
>I have gone round and round with Activision; Matrox and the Diamond
>people about this. No one seems to have a clue. I have tried using the
>Matrox M3d mini-gl drivers for Quake games; it makes no difference
>either. I have tried using non-Matrox and non-Stealth drivers and just
>used the generic S3 Virge and Power VR drivers respectively...S.O.S..
>I'm beginning to think it's just a compatibility conflict between the
>two cards that only manifests itself when trying to play these types
>of games. As I remember; I never had any problem like this before I
>got the M3d and just ran the Diamond alone. The M3d is not a
>pass-through card; it is a stand-alone accelerator though. I could
>chuck the M3d and go back to the Diamond; but then these games look
>pretty crappy using it; and forget playing GL versions. The Matrox
>definitely has better D3D graphics.
>
>The reason I'm posting this in the 3dfx.opengl group this time as well
>is because I hope to get a Monster card soon (I have a pentium non-MMX
>166 and a Voodoo II would be over-kill) and the people at Diamond have
>always assured that the old Monster works quite nicely with an old
>Stealth card; but i was wondering if anybody already had that setup
>and could confirm it for me. Also; as always... I was hoping anybody
>with a Stealth/M3d combo could tell if they ever had any problems.
>I've almost given up; and although a fix would be great; I'd just like
>to know that it does happen so I'd know I'm not alone in this. Oh
>yeah; I've tried shifting the boards around in all the PCI slots as
>well... and no, there aren't any IRQ conflicts under Device manager
>either. Thanks to everyone for your attention.

Ok, well if you've tried the OpenGL mini driver (the Half-Life One) for the
PowerVR, it has to be downloaded, that should work Ok, but other possible
troubles:

Motherboard, some MB's don't work well with the PowerVR it causes too much
PCI traffic.
Graphics Driver conflicts.
My suggestion would be to try native OpenGL for your ATI card, or Direct3D
Native, and avoid the PowerVR, I can't remember if you can select this
directly though.

Download all of the latest drivers for all cards......

--
Alan Shepherd
news@awshepherd.demon.co.uk

Calvin E. Thomas wrote in message
<77hmcg$bvc$1@holly.prod.itd.earthlink.net>...
>I am also cruising these groups looking for answers.  I played the first
>half of Half-Life with almost no problems, with my ATI All-InWonder card,
>and standard Win98 drivers.  Then I tried to update the drivers.  I have
>spent longer than I played the game to make them (kinda) work.  Very
similar
>problems.
>1.  The properties on the video card seem to require, that I allow the
>driver to select the refresh rate.  If I select it myself, it crashes
>anytime I need it to work away from the "required" refresh rate.  I believe
>the driver uses more or less video memory depending on the refresh rate,
and
>doesn't properly allocate / de-allocate it.
>2.  D3D doesn't work anymore for more than about 10-15 minutes.  Then
crash.
>Not a heat problem as the video chip never gets more than "warm"
>3. I have heard rumors that DirectX 6.1 is a possible answer, but you must
>be a MSDN DirectX beta tester to get in to download them.
>4.  According to my DirectX diagnostic tool, DirectX 6 is OK, but I notice
>that Hardware rendering of the DirectX Test screen is only about 10% faster
>than the software version of the test.  Kind of makes me wonder what my
>hardware is doing for me. (not much)
>5.  The decals in Half life never work properly with all the versions of
>OpenGL / D3D / beta that I can find (5 - 6 different drivers.)  The Win98
>drivers work OK with D3D, but are so slow as to make software rendering the
>prefered way to play.