However I was pretty luck, here is what the "read me" file from Delorme
has to say about folks who choose the "wrong" display card:
* Do not install DirectX if you have a card that uses the S3 Trio64V+
Installation of DirectX with this chipset may result in video driver
corruption. If this happens, you may need to reinstall Windows 95 to
restore the video driver. Users of this chipset should obtain updated
drivers from your card manufacturer that support DirectX 3.0.
* Do not install DirectX if you have a Number Nine GXE or a Number Nine
Imagine 128 Video card.
Installation of DirectX may result in video driver corruption. If this
happens, you may need to reinstall Windows 95 to restore the video
driver.
Users of this chipset should obtain updated drivers from your card
manufacturer that support DirectX 3.0.
The "read me" file warnings are pretty useless of course, because the
damage has already been done by the time someone is able to read these
warnings.
Be curious in hearing folks who have had problems with DirectX. Has anyone
had their Windows 95 system corrupted as Delorme claims is possible?
Anybody know what is being down about these problems?
Richard
I have had to re-install my Diamond 64 VRAM drivers once after
accidentaly
installing DirectX 2 video drivers. Now I know there is no need for
this,
I just keep the latest Diamond drivers that are DirectDraw compatible.
What makes me mad are the applications that dont ask, and just install
right over your drivers!
Troy
--
Note that my email address is mangled to avoid advertising spam!
Email me at: mailto:tba...@skypoint.com
Visit my www page at: http://www.skypoint.com/~tbarlow/
<snip>
>
>The "read me" file warnings are pretty useless of course, because the
>damage has already been done by the time someone is able to read these
>warnings.
>
>Be curious in hearing folks who have had problems with DirectX. Has anyone
>had their Windows 95 system corrupted as Delorme claims is possible?
>Anybody know what is being down about these problems?
>
>Richard
>
Richard : I installed 3.0 and found a very subtle, yet pleasent
improvement to my overall system. One of the areas that was supposed
to be addressed according to Looking Glass Software (where I got the
3.0) was joystick support. Indeed my joystick (MSSW Pro) works far
better in A-10, Flanker, etc
As far as video, on my setup program it gave the option to leave sound
and video drivers (which is just what I did for video...Herc Dynamite
128, ver 1.07) as they are. If your's did not, I suggest you check
out the LG site and get thier version
Braun
>What's the story on DirectX 3.0? Is it safe?
Who knows? I've found it to be a complete pain in the arse.
On one machine it trashed my Millennium drivers without asking, then I
spend about an hour messing around trying to re-install 3.18 drivers
and getting the system to actually use them.
On another machine it installed once and didn't overwrite video
drivers when I told it not to. Then I was messing with SB32 drivers
and re-installed DX3 and it seems to keep overwriting the audio
drivers and when I run it again it just keeps re-installing. If you
run DXSetup it is supposed to show a list of what drivers it found and
which are certified? well it did once on that machine but now it just
keeps installing things and restarting.
As I said DX3 install from Microsoft is a complete pain in the arse
and typical of Microsoft's design software for morons policy.
Cheers Terry...
Scott
i have had NO probs with DX3.. i have installed 4 different cards with
differing sound cards in the SAME pc using win95.. each time i install the
card and drivers. then reinstall dx3. it works fine and i have had no probs
--
Brett I. Holcomb
bre...@slinknet.com
Braun Tacon <br...@pacifier.com> wrote in article
<32a9b5b3...@news.pacifier.com>...
nik
--
>
> "Richard M. Smith" <r...@pharlap.com> wrote:
>
> >What's the story on DirectX 3.0? Is it safe?
>
> Who knows? I've found it to be a complete pain in the arse.
>
> On one machine it trashed my Millennium drivers without asking, then I
> spend about an hour messing around trying to re-install 3.18 drivers
> and getting the system to actually use them.
>
> On another machine it installed once and didn't overwrite video
> drivers when I told it not to. Then I was messing with SB32 drivers
> and re-installed DX3 and it seems to keep overwriting the audio
> drivers and when I run it again it just keeps re-installing. If you
> run DXSetup it is supposed to show a list of what drivers it found and
> which are certified? well it did once on that machine but now it just
> keeps installing things and restarting.
>
> As I said DX3 install from Microsoft is a complete pain in the arse
> and typical of Microsoft's design software for morons policy.
>
God dammit, people, how hard is this to understand? It's very simple.
WHENEVER DIRECTX ASKS TO REPLACE YOUR DRIVERS, SAY *NO*.
End of discussion. I've installed tons of DirectX games recently (Diablo beta,
Red alert, Rocket Jockey, etcetera) and all you have to do is follow that ONE
SIMPLE RULE and you will have no problems.
Heck, even if you screw up and let DirectX overwrite your new drivers with older
ones, just go to control panel, system, device manager, video card, and click
the UPDATE button. Then you can load whatever video driver you want.
Now, there are some games that DON'T ASK and just OVERWRITE your video drivers.
This is a horrible policy and my only advice is that if you see directX being
installed (version checking blah blah blah dialog) click the "Cancel" button.
Then proceeed with the install. Monster Truck Madness can be handled this way.
>What's the story on DirectX 3.0? Is it safe? The reason I am asking is
>that I recently purchased Delorme's new 3D Explorer CD-ROM. It uses
>DirectX 3.0. The installation program for DirectX blew away my
>WinProtrait driver and broke VDOPhone and PBTV. I am running
>a brand-new Pentium system with a display adapter card that use
>the S3 Virge chipset.
>
>However I was pretty luck, here is what the "read me" file from Delorme
>has to say about folks who choose the "wrong" display card:
>
> * Do not install DirectX if you have a card that uses the S3 Trio64V+
>
> Installation of DirectX with this chipset may result in video driver
> corruption. If this happens, you may need to reinstall Windows 95 to
> restore the video driver. Users of this chipset should obtain updated
> drivers from your card manufacturer that support DirectX 3.0.
I had a Diamond Stealth 2001 using the S3 and I didnt bother to read
the readme.txt. Anyhow, it setup fine and 2 days later I installed a
3D Blaster. Now, being a couple days since then, I can honestly say
that I have experienced NO problems and I am confident in Directx 3.
My system as of this week is a pentium 100 with 32 megs of ram, ESS 16
sound card, generic 15 inch monitor (non plug and play). Dont know if
it helps you any, but alls good from here....
This is a good idea, but you miss the point! Sure, you
and I may know better, but 95% of "average joe users" that
buy games dont have a clue! Any application that trashes
someones device drivers (without warning them) has a poorly
written install. You must think about the people who
will run the software, and most of them are clueless ;-)
>Directx 3.0 just installed itself on my system after I installed MOO2.
>I have a Diamond Stealth 3D 2000 w/ 4Megs should I be conserned? I
>haven't noticed any problems but...
>
>Scott
I installed DX 3.0 with my Diamond 3D 2000/ w. 4MB, and on reboot, my
screen had 256 colors, and 640x480 display, and no other options!!
So, I had to reinstall the Diamond 3D drivers, and reboot, and
everything was aok again, with the DX 3.0 drivers still there.
Scary for a moment....;)
Gunn
Hangar 5O, Gunn's Flight Shop; Mission Debriefs
http://www.radix.net/~gunn/hangar50.html
Do not taunt Happy Fun Ball.
The new SoundBlaster 16/32 drivers from Creative Labs will not work
properly with DirectX 3.0. You'll need to have setup overwrite them
with the drivers that originally came with Windows95.
>is it safe? you make it sound like yer gonna have sex with it or something. it's
>not gonna blow your system up if that's what ya mean.
Hey, I didn't write the subject line, I just responded to it.!
Thanks for the pearls of wisdom regarding my question.
>
>nik
>
>In article <32a9e15f...@nntp.ix.netcom.com>, qui...@ix.netcom.com (Scott Padulsky) writes:
>|> Directx 3.0 just installed itself on my system after I installed MOO2.
>|> I have a Diamond Stealth 3D 2000 w/ 4Megs should I be conserned? I
>|> haven't noticed any problems but...
>|>
>|> Scott
>
>--
> The "read me" file warnings are pretty useless of course, because the
> damage has already been done by the time someone is able to read these
> warnings.
Microsoft have been doing that particular dumb trick for years. Which
is one reason why I have a utility that reads and writes the boot sector
of my hard drive. I have a dual-boot into Linux, and the various DOS 6
upgrades would totally re-write the boot sector without _any_ warning.
--
David G. Bell -- Farmer, SF Fan, Filker, Furry, and Punslinger..
The latest versions are 4.03.00.2105 (not 2101) for the 3D 2000.
The latest creative labs SB16/AWE drivers (version 5 and 6) do not
work with DirectX3. (I think someone said this).
Note: you lose the ability to save treble/bass settings. All other
functionality is there.
hCS <mom...@earthlink.net> wrote in article
<01bbe486$1e711a60$c9cc...@mickey.phantasmic.com>...
> Richard M. Smith <r...@pharlap.com> wrote in article
> <01bbe467$2398c700$a781...@tiac.net.tiac.net>...
> > What's the story on DirectX 3.0? Is it safe? The reason I am asking
is
> > that I recently purchased Delorme's new 3D Explorer CD-ROM. It uses
> > DirectX 3.0. The installation program for DirectX blew away my
> > WinProtrait driver and broke VDOPhone and PBTV. I am running
> > a brand-new Pentium system with a display adapter card that use
> > the S3 Virge chipset.
>
Anyone know where I can get a copy of DirectX 3.0???
>
>Anyone know where I can get a copy of DirectX 3.0???
>
>
Well, if a game needs it, it'll be on the CD somewhere. It is also on
the GAmes Domain WWW site.
These are my personal views and not those of The Bank
of Scotland.
Ben Robinson
LAN Manager (Bank of Scotland)
SimCopter requested an installation of DirectX 3.0. Funny since their
readme says that DirectX1.0 is OK!
FSFW95 installed DirectX 2.0 with no problem other than to require a
reload of my Matrox Powerdesk Display Drivers. So I thought 3.0 would
be the same.
However, it seemed that DirectX 3.0 installed the standard Win95
IDE/ESDI drivers, in addition to my currently and peacefully existing
Bus Mastering IDE Drivers.
This caused an IDE driver conflict, whereby the system BIOS did not see
any of my three IDE devices. Upon bootup, I was asked for a command.com
disk. When booting to A:, typing c: or d: gave the message "Invalid
Drive Specification"
I thought I blew my motherboard, so Gateway swapped a new one, I
installed it and booted up fine, and then into Win95. Seems that Win95
read the IDE driver conflict, since on my next reboot, the IDE devices
were again missing!
With the help of a very capable Gateway tech, we cleared the NVRAM,
rebooted successfully this time, and I went straight into device
manager. The Harddrive controller section read like a Chinese
Restaurant menu. There were now 9 items, with 6 yellow exclaimation
marks. Not only had directX installed the standard IDE/ESDI controller,
it had also installed a controller for the unused IDE port on my SB 32
PnP.
I deleted all of the unused items in device manager and rebooted OK.
The moral of the story is that this Win95 conflict caused my system BIOS
not to read the IDE devices.
Go figure...
--
Larry Schachter
lrs...@carroll.com
>Richard M. Smith wrote:
--------------------snip------------------------
>I deleted all of the unused items in device manager and rebooted OK.
Whoa......I guess it's a good thing I always check the device manager
after an install, or this could have very well happened to me.
>
>The moral of the story is that this Win95 conflict caused my system BIOS
>not to read the IDE devices.
>
>Go figure...
I've seen it do stranger things than that when combined with minor
hardware problems! >|-)
Kev
>
>Anyone know where I can get a copy of DirectX 3.0???
Buy Red Alert.
--
Benedict Walmisley - Reality is Insanity
Warning: When sending email remove the * at the end. (Junk Email Knobbler)
>What's the story on DirectX 3.0? Is it safe? The reason I am asking is
>that I recently purchased Delorme's new 3D Explorer CD-ROM. It uses
>DirectX 3.0. The installation program for DirectX blew away my
>WinProtrait driver and broke VDOPhone and PBTV. I am running
>a brand-new Pentium system with a display adapter card that use
>the S3 Virge chipset.
<snip>
>Be curious in hearing folks who have had problems with DirectX. Has anyone
>had their Windows 95 system corrupted as Delorme claims is possible?
>Anybody know what is being down about these problems?
I installed DirectX 3.0 from the Command & Conquer: Red Alert CD, and
it screwed my Dynamite 128/Video drivers - so I reloaded them (version
1.07) - then couldn't get C&C:RA to work - the screen was all
corrupted and didn't get updated properly.
So, I thought I'd test it out properly and reformat my machine &
reload Win95 (had to do this anyway, too much crap on there). I
installed 1.07 Herc drivers again, installed DirectX 3.0, C&C:RA
worked, but my display was awful in Win95. Reinstalled 1.07 drivers,
back to the original problem ! Tried this a few times, no joy.
So I reinstalled Win95, downloaded & installed the beta version of the
1.12 drivers, and thank god, this fixed the problem !
Anyone else experienced this with the Hercules ?
You can download it from Microsoft. Search under "software development"
or something. My advice is don't get it, or get only part of it.
The files are arranged such that different components are separated into
different portions. The largests are 2 of them - DirectX3 executables
and ActiveX (ActiveMovie). They are 28Mb and 29Mb respectively. Even
on 28.8kbps connection, it takes a few hours just for one file. Other
portions are smaller, around 10Mb max.
I installed DirectX3 and it gave me plenty of "invalid dynamic link"
error. I had to remove all DLL files and reinstall them to get rid of
whichever particular file that's doing it. The ActiveMovie at first
lets me view Video CD, but now it doesn't. I wonder what's wrong.
And with the installation of new games like Microsoft Flight Simulator
for Win95, DirectX3 is installed together, anyway. Makes me feel
cheated of $200+ of connection time I wasted on downloading DirectX3.
The download is over 6MB though...
Benedict Walmisley <BWalm...@wolf.demon.co.uk*> wrote in article
<32ad7439...@news.demon.co.uk>...
jul...@netcom.com (Julius Robinson) scribed:
>
>Anyone know where I can get a copy of DirectX 3.0???
Buy Red Alert.
Bunboy
>
>Anyone else experienced this with the Hercules ?
With the MGA Powerdesk 3.18 drivers on my Mystique 4MB RETAIL ..
.. DDraw apps work correctly when DirectX 3.0 is on the system..
.. but any Direct3D apps freeze up the whole system !!!
So I had to re-install the whole Win95 and put in the DirectX 2.0 .. !! Sigh!
I'm waiting for DirectX3.0 compliant drivers from Matrox .. I've already
explained them the problem twice !
It's really silly that those at Microsoft haven't written a simple un-install
feature for the DirectX libraries.. !!! Sigh.. !!
This is the bad thing of having all the PC with MS OSes.. ! It's bad
for users like us..sigh!
Huh? What's wrong with Start->Settings->Control Pannel->Add/Remove
Programs->Install/Uninstall->DirectX Drivers? Left the DXSDK directory
intact last time I ran it, but that was fixed by simply dragging it into
the bin.
Mark Feldman
> On 7 Dec 1996 23:28:50 GMT, nom...@nospammers.com (Smoke Crack and
> Worship Satan) wrote:
> >God dammit, people, how hard is this to understand? It's very simple.
> >
> >WHENEVER DIRECTX ASKS TO REPLACE YOUR DRIVERS, SAY *NO*.
> >
> >End of discussion. I've installed tons of DirectX games recently (Diablo
beta,
> >Red alert, Rocket Jockey, etcetera) and all you have to do is follow that ONE
> >SIMPLE RULE and you will have no problems.
Jeff, if this is a good simple rule that will
<a> allow the titles to run correctly
<b> still get the performance and
"reduced support cost" benefits of DirectX
<c> is easy to implement inside DirectX itself
Why not just flat out add it to DirectX? Instead of assuming that each
user knows to never press that "replace" button, why not just get rid of it
altogether? Conversely, if there is never any good reason for it to be
there, what do you suppose motivated MS to put it there in the first place?
[ I suspect it is there for a perfectly good reason, and therefore it
may be silly to tell people "don't ever use that, it's bad". If the
"badness" springs from not being able to predict in advance how badly one's
system may get screwed up when the button *is* pushed, this is a separate
problem isn't it? ]
Rob Barris
Quicksilver Software Inc.
rba...@quicksilver.com
* Opinions expressed not necessarily those of my employer *
Roger
>In article <32acc426...@news.dial.pipex.com>, terry....@dial.pipex.com
>(Terry Harris) wrote:
>
>>
>> "Richard M. Smith" <r...@pharlap.com> wrote:
>>
>> >What's the story on DirectX 3.0? Is it safe?
>>
>> Who knows? I've found it to be a complete pain in the arse.
>>
>> On one machine it trashed my Millennium drivers without asking, then I
>> spend about an hour messing around trying to re-install 3.18 drivers
>> and getting the system to actually use them.
>>
>> On another machine it installed once and didn't overwrite video
>> drivers when I told it not to. Then I was messing with SB32 drivers
>> and re-installed DX3 and it seems to keep overwriting the audio
>> drivers and when I run it again it just keeps re-installing. If you
>> run DXSetup it is supposed to show a list of what drivers it found and
>> which are certified? well it did once on that machine but now it just
>> keeps installing things and restarting.
>>
>> As I said DX3 install from Microsoft is a complete pain in the arse
>> and typical of Microsoft's design software for morons policy.
>>
>
>God dammit, people, how hard is this to understand? It's very simple.
>
>WHENEVER DIRECTX ASKS TO REPLACE YOUR DRIVERS, SAY *NO*.
>
>End of discussion. I've installed tons of DirectX games recently (Diablo beta,
>Red alert, Rocket Jockey, etcetera) and all you have to do is follow that ONE
>SIMPLE RULE and you will have no problems.
>
>Heck, even if you screw up and let DirectX overwrite your new drivers with older
>ones, just go to control panel, system, device manager, video card, and click
>the UPDATE button. Then you can load whatever video driver you want.
>
>Now, there are some games that DON'T ASK and just OVERWRITE your video drivers.
>This is a horrible policy and my only advice is that if you see directX being
>installed (version checking blah blah blah dialog) click the "Cancel" button.
>Then proceeed with the install. Monster Truck Madness can be handled this way.
No kidding, it USNF 97 went ahead and installed all portions of
DirectX3 including overwriting my video drivers. Of course, I've lost
lots of functionality now such as been able to set monitor refresh
rates!
---------------------------------------------------------------------------
Andrew Chiang 5th year Computer Science
and...@seas.ucla.edu "Real programmers don't document. If it
http://www.seas.ucla.edu/~andrewc was hard to write, it should be hard
to understand."
>> On 7 Dec 1996 23:28:50 GMT, nom...@nospammers.com (Smoke Crack and
>> Worship Satan) wrote:
>> >God dammit, people, how hard is this to understand? It's very simple.
>> >
>> >WHENEVER DIRECTX ASKS TO REPLACE YOUR DRIVERS, SAY *NO*.
>> >
>> >End of discussion. I've installed tons of DirectX games recently (Diablo
>beta,
[snip]
> <a> allow the titles to run correctly
> <b> still get the performance and
> "reduced support cost" benefits of DirectX
> <c> is easy to implement inside DirectX itself
> Why not just flat out add it to DirectX? Instead of assuming that each
>user knows to never press that "replace" button, why not just get rid of it
>altogether? Conversely, if there is never any good reason for it to be
>there, what do you suppose motivated MS to put it there in the first place?
While I don't have detailed knowledge of the inner workings of
DirectX, this much I have glimsed:
In order for DirectX to work, you have to have a couple of things.
First, you need the DirectX core libraries. Second, you need drivers
that support DirectX specific to your hardware. Now, not all
manufacturers have included DirectX support in their drivers, so
Microsoft has kindly (When was the last time you heard that word in
respect to MS?) provided some that do. When the question regarding
replacing drivers is asked, Microsoft wants to know if you want to use
Microsoft's drivers instead of those provided by the manufacturer (ie,
the ones that are currently installed). Of course, if the
manufacturer included DirectX support in their drivers, you neither
need nor want MS's drivers, so you should answer NO.
Clear as mud, eh?
[snip]
Patrick Pilon
zoa...@mbox.vol.it wrote in article
<32ad3464...@nntpserver.vol.it>...
What type of video card do you have? I work at Origin Product Support
and would be happy to try and help you get things going. If you tell
me the brand of the card, I'll see what I can do.
You can Email me at : cmcm...@origin.ea.com
Hope to hear from you soon.
Later,
Irasthmus
Origin Product Support
Why do you people not learn? Just goto the place where it was
developed, Microsoft. It is availible for download or if you have the
cash you can get a Subscription to MSDN which will give you all those
nice little SDKs...
MS SDK Main Page
http://www.microsoft.com/msdn/sdk/default.htm
DirectX 3.0 SDK (Official SITE!)
http://www.microsoft.com/msdownload/directx3.htm
Last time I am doing this. Get it from MICROSOFT AT:
http://www.microsoft.com/msdownload/directx3.htm
It's all they're just pick what parts you want.
Uh 28MB? My version (with every stupid thing) is 86MB...
Todd.
to...@netgate.net
Richard M. Smith wrote:
>
> What's the story on DirectX 3.0? Is it safe? The reason I am asking is
> that I recently purchased Delorme's new 3D Explorer CD-ROM. It uses
> DirectX 3.0. The installation program for DirectX blew away my
> WinProtrait driver and broke VDOPhone and PBTV. I am running
> a brand-new Pentium system with a display adapter card that use
> the S3 Virge chipset.
>
> However I was pretty luck, here is what the "read me" file from Delorme
> has to say about folks who choose the "wrong" display card:
>
> * Do not install DirectX if you have a card that uses the S3 Trio64V+
>
> Installation of DirectX with this chipset may result in video driver
> corruption. If this happens, you may need to reinstall Windows 95 to
> restore the video driver. Users of this chipset should obtain updated
> drivers from your card manufacturer that support DirectX 3.0.
>
> * Do not install DirectX if you have a Number Nine GXE or a Number Nine
> Imagine 128 Video card.
>
> Installation of DirectX may result in video driver corruption. If this
> happens, you may need to reinstall Windows 95 to restore the video
> driver.
> Users of this chipset should obtain updated drivers from your card
> manufacturer that support DirectX 3.0.
>
> The "read me" file warnings are pretty useless of course, because the
> damage has already been done by the time someone is able to read these
> warnings.
>
> Be curious in hearing folks who have had problems with DirectX. Has anyone
> had their Windows 95 system corrupted as Delorme claims is possible?
> Anybody know what is being down about these problems?
>
> Richard
Hugh Smith <hu...@vnet.ibm.com> wrote in article
<32AF99...@vnet.ibm.com>...
28--86Mb ??? Mine is 6Mb and behaving well!
i.e. Asking before replacing drivers... Not a single f..kup ...yeat.
--
Regards, (-0-)
--- Martin
m...@pma.dk
Hi There,
For people with a S3 Trio64V+ or VU+ card, there are new drivers (10 Dec.)
on the s3 site (www.s3.com) which are claimed to be compatible with
directx 3.0. I can't try them, have a S3 Virge and am waiting for direct3D
drivers (if they will ever come).
CU, Robert
Seems not really safe... I just found out that Destruction Derby is
fucked up... probably by DirectX3
John Mueller
John Mueller
>Quik wrote:
>>
>> Julius Robinson wrote:
>> >
>> > Anyone know where I can get a copy of DirectX 3.0???
>> Me too
>> =)
>> I just had to ala AOL posts hehehe I have been looking all over for DX3.
>> found the DX3 developers kit but its 28 megs!!!! does it have the DX3
>> drivers in it? alos is the twist test included in the SDK?
>> l8r
>> Quik
>Uh 28MB? My version (with every stupid thing) is 86MB...
Hm...that's bigger than Win95 :)
Unless off course 'with every stupid thing' means with win95 :)
Mark
>And with the installation of new games like Microsoft Flight Simulator
>for Win95, DirectX3 is installed together, anyway. Makes me feel
>cheated of $200+ of connection time I wasted on downloading DirectX3.
Geez you still have an online service that you have to pay by hour ???
Can you say stoneage :)
I'm sure for 200$ Bill Gates would have delivered it to you in
person :)
Mark
It seems he lives in Singapore. Not all phone companies give out free
local phone calls. Just be glad they have not started charging local
by the minute YET here in the US.
Chris Hudgin
>Hi There,
>
>For people with a S3 Trio64V+ or VU+ card, there are new drivers (10 Dec.)
>on the s3 site (www.s3.com) which are claimed to be compatible with
>directx 3.0. I can't try them, have a S3 Virge and am waiting for direct3D
>drivers (if they will ever come).
>
>CU, Robert
S3 already has a virge dirver out for Windows 95 which supports
Direct3d.
They work fine with Directx 2 or 3.
You can find them at ftp://ftp.s3.com/pub/bbs/325drv/index.htm
Some people, like me, got the drivers by downloading the DirectX SDK.
In my case it's not a big deal since I need the SDK. I found another
site, the one that you apparently used, that offers the DirectX drivers
alone in a 6 MB package.
John Mueller
On Mon, 09 Dec 1996 23:07:06 GMT, sp...@netcomuk.co.uk (Jean Bishop)
wrote:
>I installed DirectX 3.0 from the Command & Conquer: Red Alert CD, and
>it screwed my Dynamite 128/Video drivers - so I reloaded them (version
>1.07) - then couldn't get C&C:RA to work - the screen was all
>corrupted and didn't get updated properly.
>
>So, I thought I'd test it out properly and reformat my machine &
>reload Win95 (had to do this anyway, too much crap on there). I
>installed 1.07 Herc drivers again, installed DirectX 3.0, C&C:RA
>worked, but my display was awful in Win95. Reinstalled 1.07 drivers,
>back to the original problem ! Tried this a few times, no joy.
>
>So I reinstalled Win95, downloaded & installed the beta version of the
>1.12 drivers, and thank god, this fixed the problem !
>I have no problems Direct3 supposedly came with a sampler given away with
>PCGamer in the UK - it didn't even overwrite my display adapter driver -
>will double check tonight to see if it reallis ver 3.0
>
>Hugh Smith <hu...@vnet.ibm.com> wrote in article
><32AF99...@vnet.ibm.com>...
Oh oh, this smells. Ive just bought a PC ( a week ago ) which uses the S3
Virge chipset ( cheap and probably very nasty ). In went newly purchased MS
Sidewinder Pro joystick software along with FS6 which did mention it was
loading DX stuff ( probably 3.0 knowing my luck ) and guess what, no sound
card , video errors etc etc. Why did I buy this shit when all my Mac chums
warned me to keep my cash?
Along side my Mac which Im typing this on is one sick pile of DOS shit that
will have to wait till my PC guru friend ( ex ? ) comes back from his
holidays to fix ( hopefully).
My old Amiga 1000 ran Sub Logic FS with a joystick back in 85, it was easy
to set up as is my Mac with it's flight sims ( thanks for nothing MS for
not updating to Mac FS 6 ), you could of saved me the hassle of this PC
pile of junk.
signed, cheesed off sucker who cant wait to get back to his Mac full time.
>Oh oh, this smells. Ive just bought a PC ( a week ago ) which uses the S3
>Virge chipset ( cheap and probably very nasty ). In went newly purchased MS
>Sidewinder Pro joystick software along with FS6 which did mention it was
>loading DX stuff ( probably 3.0 knowing my luck ) and guess what, no sound
>card , video errors etc etc. Why did I buy this shit when all my Mac chums
>warned me to keep my cash?
>Along side my Mac which Im typing this on is one sick pile of DOS shit that
>will have to wait till my PC guru friend ( ex ? ) comes back from his
>holidays to fix ( hopefully).
>My old Amiga 1000 ran Sub Logic FS with a joystick back in 85, it was easy
>to set up as is my Mac with it's flight sims ( thanks for nothing MS for
>not updating to Mac FS 6 ), you could of saved me the hassle of this PC
>pile of junk.
>signed, cheesed off sucker who cant wait to get back to his Mac full time.
Well, anyone who has been into computers for over a year could tell
you that Motorola and RISC based systems beat any Intel/Cyrix
system hands down when it comes to reliability and user friendliness.
In the long run (for most people already in the short run) you will
encounter numerous problems with any PC.
I had more problems in the first month i owned a PC than i had in all
the years i owned an amiga.
But most people (me included) can't really do without a PC in the long
run either...
Maybe you just got a bad system from a bad dealer (BTW solve your
problems before the warranty expires !!! There is 0 service after
warranty expired !!! )
Mark
You can download both from http://www.x-plane.com
or http://www.picketfence.com/x-plane/
--
_________ __ |Mark Stotzer-Assistant Editor, FSNews
/ __/ __/ |/ /__ _ _____|http://www.erols.com/fsnews/
/ _/_\ \/ / -_) |/|/ (_-<|See my "ATP/Pro Pilot Corner" pages at:
/_/ /___/_/|_/\__/|__,__/___/|http://www.erols.com/fsnews/news/atp.html
FSNews: "All the latest flight simulation news-without a subscription!"
Hehe...I got my copy of DirectX 3.0 from my Beta Test CD of
battle.net/Diablo.... :)
Warmaker -- Forever a Roamer, For I Can't Stand to Rest
The ATI cards use ATI chip sets. You should try reinstalling your video
drivers for the ATI card.
I've noticed when running Red Alert with DirectX3, that my refresh rate
is 85MHz. In "normal" Win95 my refresh rate is 75MHz - reported by OSD
from Sony 15" SF2. My video card is a Millenium 4mb, and my monitor is
set to the matrox Sony SF2 definition - not plug and play. However my
Win95 definition IS DDC, so does DirectX3 ignore the Matrox setting and
use the Win95 one ?, or does it just get it hopelessly wrong ?
Also when running RAC Rally (DOS game) from Win95, if the screen saver
kicks in, when I restore the game I get an OUT OF FREQUENCY RANGE error
on my screen. Glad my monitor recognises this, otherwise broken
monitor.
So there IS a problem which can blow a monitor - but is it my Matrox
drivers, Win95 or DirectX ???
From my experience, it is a Direct X 3.0 problem. I received Lords of
the Realm II with Direct X 3.0 and installed it. It totaly screwed my
video card and modem drivers. After about 4 hours I had my system
restored, but I had to figure it out on my own. I called Sierra and
they had no idea about what was causing the problem, but stated that DX
3.0 has a bug in it. They are putting cards in all of their games
saying not to install DX 3.0 because of the bug. I also tried Microsoft
for help, since it is their friggin API. They didn't know anything, as
usual. Luckily, I had a copy of DX 2.0 in a folder on my drive and
chose to restore my old drivers, a feature 3.0 doesn't have. It wrote
over the DX drivers, but I had to replace my video card, a new Steath 3d
2000 XL, due to what DX 3.0 did to it. Bottom line-don't use DX unless
you absolutely have to. Run that game in DOS!
Keith Groves
"If ain't broke, don't fix it."
Has anyone been able to get the GUS to work properly under DirectX3
games? (ie. HoMM2 and Red Alert).
It functions perfectly under Win95, however, under DirectX3 games, the
sound is always garbled, and "echoed" (ie. under RA:
"affir...fir..fir..fir..mative..mative..mative").
Would appreciate any suggestions to correct this problem.
Regards,
Jon.
So is there any way you can tell up-front whether your hardware can handle
it? Has anyone compiled a list of known monitors, video cards, and/or
drivers that simply do not work with DirectX 3.0?
--
========================================================================
"Villains, I say to you now: | Mike Carmack
KNOCK OFF ALL THAT EVIL!" | Vulcan Dragon -==(UDIC)==-
S P O O N !!!! - The Tick | mcar...@freenet.columbus.oh.us
Thanks
Gary
Thanks in advance...
Peter
Q:>Andre Susanto <an...@supra.com> wrote:
Q:>Hate to add more to the pot. But I recently blew up a mag monitor
on
Q:>running a direct-x game. It was on a mode switch from 800 x 600 to
Q:>640 x 480. The monitor made a high pitched squeal then a loud
...
[snipped to save bandwidth]
---
...Netscape is unable to locate the server proxy.m.tempest.com.au:80
That's why I changed to Microsoft Internet Explorer 3.01 |)...
Jonathan MUN <e...@alphalink.com.au> wrote in article
<32BA2B...@alphalink.com.au>...
> It functions perfectly under Win95, however, under DirectX3 games, the
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> sound is always garbled, and "echoed" (ie. under RA:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> "affir...fir..fir..fir..mative..mative..mative").
Steven E. Fritz <fri...@ohsu.edu> wrote in article
<597ph5$h...@fremont.ohsu.edu>...
> I installed DeLorme's 3DExplorer USA with DirectX on a Pentium 90mhz
> system using an ATI Mach 64 ProTurbo card. I chose YES when asked by the
(snip)
Patrick Ellerd <patr...@ipass.net> wrote in article
<01bbeeff$d97debc0$8f354fc6@Pat'sGateway.duke.edu>...
I finally gave up and started playing HOMM2 solely in DOS. It sucks,
because I can't play Internet multiplayer through DOS HOMM2 (those options
were left out of the DOS version). I can't stand all this DirectX crap,
everything I've seen seems to run better in DOS.
-=Gabriel=-
Does anyone know when Prima's book about Flight Sim 95 is going to hit
the stands?
Regards,
Joe
>In article <32acc426...@news.dial.pipex.com>, terry....@dial.pipex.com
>(Terry Harris) wrote:
>
>>
>> "Richard M. Smith" <r...@pharlap.com> wrote:
>>
>> >What's the story on DirectX 3.0? Is it safe?
>>
>> Who knows? I've found it to be a complete pain in the arse.
>>
>> On one machine it trashed my Millennium drivers without asking, then I
>> spend about an hour messing around trying to re-install 3.18 drivers
>> and getting the system to actually use them.
>God dammit, people, how hard is this to understand? It's very simple.
>
>WHENEVER DIRECTX ASKS TO REPLACE YOUR DRIVERS, SAY *NO*.
But now Microsoft has announced directx 3a I read it fixes :-
"Setup changes to correct a display driver install problem. When
DirectX 3 is installed over the OSR2 version of Windows 95 with
certain OEM drivers installed, DirectX 3 setup didn’t prompt the user
to ask if setup should replace the drivers. "
There.... it wasn't hard to understand - just pretty difficult to do
for some people.
Cheers Terry...
>You guys are scaring the crap out of me with these DirectX horror stories.
>It seems that most people have no problems, but a handful are completely
>blowing their monitor! I certainly cannot afford to take that chance;
>$700 to replace my monitor is not at all feasable for me.
It would be a good idea to
(1) Use the DOS utilities that came with your video card and program
your video card to reasonably safe defaults
(2) If you're running Windows 95 Service Release 2 (OSR2), make sure
you use the Windows 95 supplied drivers and program in a compatible
monitor, or to be safe, the Standard 800x600@60hz display rate. Don't
set your 15" monitor to be a 21" compatible, some higher display modes
may have sync rates that you're monitor cannot handle.
OSR1 or the retail upgrade version of Windows 95 had the monitor
refresh rate programming disabled. OSR2 was meant to be set up by
dealers to their hardware, but many of them aren't bothering to tweak
anything that the default setup didn't detect, or write their own
MSBATCH.INF to either setup the correct settings, or putting an ADDREG
section to rewrite the registry on the first bootup.
If you want to use the funky drivers that come with your video card
and that can also re-program your video card, then do so, after
programming the Windows 95 default display driver and monitor.
From my observations with a Diamond Stealth 64 DRAM (S3 764 chipset),
if you don't program in defaults, when you switch to a Direct-X mode,
it jumps out of the Diamond In-Control tools to the monitor specified
with the Windows 95 driver. I didn't have one specified and I got
85Hz (interlaced) at 1024x768, which was the default my video card was
programmed to.
Once I reprogrammed the video BIOS defaults, it was okay.
YMMV.
- Jimbo
>Well, anyone who has been into computers for over a year could tell
>you that Motorola and RISC based systems beat any Intel/Cyrix
>system hands down when it comes to reliability and user friendliness.
Ever tried running AIX on a PowerPC? Oh yeah, user friendly;
whatever.
DirectX 3.0 has also caused me major headaches. It seems now
ANY dos game I try to load now, I get some stupid popup question
telling me that the game may not work well under windows, and if
I would like it to edit it to run in dos only mode... what a joke....
Most all my games before with Directx 2.0 loaded and played
just fine under Windows95...
I guess someone needs to sue Microsoft over this... they have no
right to install something thats impossible for us to uninstall... there
has to be some law against that.
I also see that Microsoft has come out with a directx 3.0a now,
although it only fixes some mmx bug and thats it... and on top of
it they appologize for coming out with a bug fix so soon... what
a joke... if anything they need to be coming out with fixes every
week.
If someone could write a DirectX UN-INSTALLER, I'm sure
people would be willing to PAY for it.... I know I would.
run setup (should be in your temp dir..err folder, or folder you
executed from. Or it is in the folder directX creates.) it will
install from the backup directX makes when it installs. Things will be
as they were before you installed. For what its worth I have installed
directX & running it for some time now, without any problems.Things
you might want to look into is your vid card & directX, also, maybe
the driver for your sound card.
Chuck
Check to see if there is a patch for the game. If it uses direct-x
1.0 chances are that you are using DX2 and there are some
incompatablities. I am basing this on the fact that firefight had the
same problem. I wouldn't work with DX2, only with the supplied driver
DX1. Even with DX1 I had to switch the color depth to 256 colors. I
recently downloaded the patch now everything works fine.
>DirectX 3.0 has also caused me major headaches. It seems now
>ANY dos game I try to load now, I get some stupid popup question
>telling me that the game may not work well under windows, and if
>I would like it to edit it to run in dos only mode... what a joke....
>Most all my games before with Directx 2.0 loaded and played
>just fine under Windows95...
>I guess someone needs to sue Microsoft over this... they have no
>right to install something thats impossible for us to uninstall... there
>has to be some law against that.
>I also see that Microsoft has come out with a directx 3.0a now,
>although it only fixes some mmx bug and thats it... and on top of
>it they appologize for coming out with a bug fix so soon... what
>a joke... if anything they need to be coming out with fixes every
>week.
>If someone could write a DirectX UN-INSTALLER, I'm sure
>people would be willing to PAY for it.... I know I would.
Hi Tim
I dont know where you got your DirectX 3.0 from but the version I have
which I got on a MSoft games sampler CD has a built in uninstaller.
All you have to do is run the Setup Program again and it offers the
option ti uninstall the DirectX drivers.
This version seems to work fine with my D/S 3d 2000.
All the Best
Andy
Peter
IBM had the same problems (only worse) with their PS1 series. The PS1's
would not accept DX4 overdrive chips OR large hard drives (even with
DiskManager or EZ-Drive) because of the BIOS chip, which was
irreplaceable.. IBM's (including Aptiva's) also have that neat
mainboard design where the expansion card slots are themselves connected
to a slot on the mainboard. Basically this means that upgrading your
motherboard with the existing case is NOT an option.
After my PS1 debacle, I vowed never to buy IBM again. They are truly
incompatible.
Later, John Gary AKA RxMAN
pag...@tempest.com.au wrote in article
<32bf0d7c...@news.m.tempest.com.au>...
However, DirectX 3 has new instructions that were not included
in previous versions of DirectX. If the software you installed that
included DirectX 3 then the chances are that that software uses
some of the new features of DirectX 3 and wont run on an older
version.
As for those people who claim that DirectX 3 blew up their monitors,
what a lot of B.S. ! There is no way that a new software driver can
physically damage a monitor. My guess is that people have had
dodgy monitors already. If you get a blank screen after installing
DirectX 3, re-boot in safe mode (standard VGA) and change the
display type in control panel as its probably just a case of WIN95
choosing the wrong adapter or monitor (just like it does if you ever
try to reinstall win95).
Jonathan MUN <e...@alphalink.com.au> wrote in article
<32BA2B...@alphalink.com.au>...
> Just an aside question:
>
> Has anyone been able to get the GUS to work properly under DirectX3
> games? (ie. HoMM2 and Red Alert).
>
> It functions perfectly under Win95, however, under DirectX3 games, the
> sound is always garbled, and "echoed" (ie. under RA:
> "affir...fir..fir..fir..mative..mative..mative").
>
> Would appreciate any suggestions to correct this problem.
>
> Regards,
>
> Jon.
>
Here's what I know for the GUS situation and DirectX 3.0:
The GUS Classic will NOT work properly with DirectX 3.0, even though it may
work well in Win95. Gravis said the GUS Classic, ACE and MAX were NOT
designed for Win95 (!?) and said they were in the PLANNING (?!) stages for
new Win95 drivers compatible with DirectX, and SUGGESTS (?!) you buy a GUS
PNP instead!
The GUS PNP, as far as I know (a friend of mine), works well with DirectX
(like RA, for ex.). But he hasn't tested it with many games, so I don't
know much more.
Having been a FAITHFUL GUS owner since the very beginning, this
announcement was the last straw. I just bought a SB16 PNP last week and
after a little bit of tweaking, EVERYTHING (a word I haven't used for many
years) works fine.
I hope it helps.
Andorian
Q:>IBM is working to make Direct X work on the Aptivas.
Q:>
Q:>pag...@tempest.com.au wrote in article
Q:><32bf0d7c...@news.m.tempest.com.au>...
Q:>> Oh by he way, DirectX 'Will not run on an Aptiva' Our local
Q:>> IBM techs tell us so! So to all those out there, sorry, but
Q:>> for 'hardware reasons it is not possible'. Funny how big blue
Q:>> can make IBM incompatables (remember the PC Jnr).
Q:>>
"Direct X will not crash your monitor. If you don't have good DirectX
video support or if the version of Direct X has a problem you will not
have the desired video performance. It will not, however, damage your
monitor, it is only a software problem.
Direct X is an interface developed by Microsoft to give programs direct
access to specific pieces of hardware, hence accelerating the programs.
Basically it gives a program in Win95 the same access to the hardware it
has in DOS, a little overly simplified but it is the basis of Direct X.
One of the problems with Direct X is that it requires support from Win95
(this comes in the form of the Direct X install) and support from the
hardware also. The hardware support comes from device driver updates.
You want to continually check for these every couple of months right
now.
I hope that gives you a little help, and answers some of your questions
and reservations."
Happy Holidays to all,
Don
--
=================================================================
A mans got to know his limitations. DON CANNELL
Harry Calahan dcan...@ix.netcom.com
=================================================================
>On 24 Dec 96 19:55:43 GMT, "Nobby" <ne...@tongue-tied.co.uk> wrote:
>I really think software can blow up the monitor's tube. Have you ever
>ran display doctor 5.3 from scitech? When it configures your monitor
>it says to turn it off because it changes to some funky modes to test
>the monitor and could blow the tube
It doesn't say it could blow your tube.
It says there is a rare change it could damage your monitor.
Jonathan MUN <e...@alphalink.com.au> a écrit dans l'article
<32BA2B...@alphalink.com.au>...
> Just an aside question:
>
> Has anyone been able to get the GUS to work properly under DirectX3
> games? (ie. HoMM2 and Red Alert).
>
> It functions perfectly under Win95, however, under DirectX3 games, the
> sound is always garbled, and "echoed" (ie. under RA:
> "affir...fir..fir..fir..mative..mative..mative").
>
All owners of GUS sound card have this shitting bug under windows 950 with
directx 3.0.
the only solution at this time is to use windows 950b (OSR2) which have
directx inside with no bug !!!!
;-))) bye gusman ...
I read somewhere that the way to fix that problem was to reinstall DirectX
2.0 then reinstall the game with the DirectX 3.0. This was from some tech
support guy on another DirectX game so maybe it will work for you too.
Bill
> >On 24 Dec 96 19:55:43 GMT, "Nobby" <ne...@tongue-tied.co.uk> wrote:
> >I really think software can blow up the monitor's tube. Have you ever
> >ran display doctor 5.3 from scitech? When it configures your monitor
> >it says to turn it off because it changes to some funky modes to test
> >the monitor and could blow the tube
> It doesn't say it could blow your tube.
> It says there is a rare change it could damage your monitor.
>
I have blown up two Goldstar 1505 monitors, using a) Univbe (which I ran in
error.... the default video
chip seemed to be wrong, and when it went into test my monitor started
hissing, then before I could reach the on/off switch there was a large bang
a fat blue spark from the inards and a nice smell of ozone - anyone who
thinks I am imagining this can call up my on-site monitor swap out people.
Now that was a bit of a low level dodgy thing to do.... BUT the second time
I blew one up is a much more serious issue :-
There I was playing DukeNukem (in MSDOS mode) in Win95 - with my newish
(and VBE 2.0) Matrox Millenium card performing wonderfully. (Note 800X600
mode in both dos and windows), when I exited the game, I had the msdos mode
options set to return to Win95 immediately, the screem went blank, fuzzy
then hiss/crackle, then not so dramatically as before - dead monitor.
Nowdays I still play the same games but I do all the mode switching
manually - or not at all - after a game of Duke3d I re-boot before I go
back into windows.
Anyone have any ideas why this sort of thing can happen? [not all my
refresh rates are set correctly.]
Bill Pinnell, Epsom, Surrey
I think its just because of the quality of the driver. Gravis makes very
shitty Windows drivers. They said on their website that they emulate
Direct Sound and also said that a true Direct Sound driver may not be
possible. Not possible?! Whoa?! What the heck!!! I own a GUS for a long
time now (I have a rev. 2.4 card and I bought it new way back when). But
upon reading that, I promptly gotten a SB16 and the Yamaha daughter
board. I love the GUS, but heck, I'm not going to torture myself just so
I can run demos twice a year (I generally only get the Assembly and The
Party demos). BTW, changing DMA buffer size might cure the problem.
Hope that helps.
Ciao.
Muljadi Budiman.
: chip seemed to be wrong, and when it went into test my monitor started