Mime-Version: |
1.0 |
Sender: |
|
Date: |
Thu, 8 Apr 1999 10:16:08 +0100 |
Reply-To: |
|
Subject: |
|
From: |
|
In-Reply-To: |
<001801be8169$32dac5a0$aa97a6d1@celeron> |
Content-Type: |
text/plain; charset="us-ascii" |
Comments: |
RFC822 error: <W> MESSAGE-ID field duplicated. Last occurrence
was retained. |
Parts/Attachments: |
|
|
Thanks for the post, very clear :) I'm gonna have to resort to using both
cards I think, shame really, I wanted the m3d for my daughters machine. I
also wanted the mystique 220 for the same purpose, but I can't get the
onboard card here (pc-chips M571 mobo, 4mb agp onboard) and the voodoo1 to
coexist peacefully at all. Reading the mobo manual, the onboard is a 2d/3d
card, which explains the clash I guess (not a board I'll buy again, the
mike wont work either, with or without a sb16). There's no way I can see of
disabling/overriding the inbuilt 3d, but if I've gotta open me box up to
fit the m3d I might just try again...
>You must use the Properties screen to "disable" the m3D when playing
>Gluide/VooDoo games, and reinitialize it when you want to use the m3D. You
>must use the m3D OpenGL patches, (not the VooDoo), for OpenGL games
Regards
Steve Harrison
PCBUILD only works if you contribute. Send your messages
to be posted to: [log in to unmask]
|
|
|