rec.autos.simulators

anyone know the easy way to uninstall directx5 ?

It has *totally* messed up my Nascar2 play in win95....
steering now has a huge dead zone....
and the frame rate is awful now.... worked fine before....
helllllllp !  :)

--

 Handy^Man                                    
 IVGA 4924              ~~pulling for #8 in 1998 ! :)~~
 ICQ 3551448                    GOoooo #3 !!

 Information is stored in the Win95 registry about which version  
of DirectX is installed and other parameters/settings relating to
DirectX.
 The procedure outlined below allows you to remove enough of DirectX
(although not every single bit of it)  to let you reinstall it...any
older
 version, all the way down to DirectX1.

 Be warned: the following procedure involves deleting certain Win95
registry keys that, if done incorrectly, -could- render your nicely
running Win95 useless and you'll have to reinstall it and all your other
applications. Do the following at your own risk. I won't be held
responsible if you***up your system. If you don't know about
"regedit" or "regback", you probably shouldn't be doing the procedure.

*Win95 OEM Service Release 2 (OSR2) Update 9/9/97
 I have obtained a copy of OSR2 and have tested this procedure with it.
It works the same as indicated below. The only problem I had was with
 deleting the dsound*.* files. Since I did a clean install of OSR2, I
was not using any updated drivers except for the Matrox Millennium 3.70
 drivers. I did not install updated drivers for my Sound Blaster AWE64
Gold and was using the original drivers that were installed along with
OSR2 (if any -were- installed...DirectX2 was "automatically" installed
 along with OSR2 and I suspect that the AWE64 was using DirectSound
exclusively). When I deleted these two files, I got the "blue screen
of death" upon rebooting. The fix was to boot into "safe mode", go
into "system properties/device manager/sound, video and game
controllers"
remove anything AWE64 related from the system, then redetect the AWE64
using "add new hardware" and install the current drivers. This problem
does
 -not- happen if you already have updated drivers on your system before
removing DX5.

Using regedit, regback (included on the Win95 cd), or Norton registry
editor, back up your entire registry to a backup folder/disk. Also
backup the all files listed below. If something happens, at least you'll
have the backups to revert to.

Using regedit or Norton registry editor, delete the following entries
(delete the whole key/folder):
 HKEY_LOCAL_MACHINE/Software/Microsoft/Direct3D
                                      /DirectDraw
                                      /DirectPlay
                                      /DirectX

*Update 9/6/97
To get rid of the DirectX5 OEM controllers list, (different controllers
are listed when DirectX3.0b or below is installed) delete the following
 registry key:
HKEY_LOCAL_MACHINE/System/CurrentControlSet/Control/MediaProperties/
PrivateProperties/Joystick/OEM
This rids the Control Panel/Joystick/Joystick selection list of the new
controllers such as  the "ThrustmasterT1T2 with adapter/without
adapter".
You -will- have to reinstall your joystick drivers if you delete this
registry key. Reinstalling DirectX3.0b or below will restore the old
controllers list.  If you want to keep the newer DirectX5 controllers,
don't delete this registry key.

Using Explorer, delete the following folder:
C:\Program Files\directx

Then shut down to MS-DOS mode and delete the following files:
C:\win95\system\ddhelp.exe
               \ddraw*.*
               \dsound*.*
               \dinput*.*
               \d3d*.*
               \dplayx.dll
               \dpmodemx.dll
               \dpwsockx.dll

*Update 9/6/97
The previous release of this procedure left  "Old DirectPlay" from an
early version of DirectX still installed. These files don't have to be
deleted if you only want to get rid of DirectX5.  Old DirectPlay is
still used by some games, (I have no idea which ones) so the choice is
 up to you if you want these removed or not. Reinstalling DirectX3 or
above will -not- reinstall old DirectPlay. Delete the following files:
C:\win95\system\dplaysvr.exe
                             \dpwsock.dll
                             \dpserial.dll
                             \dplay.dll

If you also installed the new DirectX5 control panel, delete the
following file:
C:\win95\system\directx.cpl
If you delete DirectX 5 and reinstall an earlier version, the file
"joy.cpl" (the joystick control panel applet) will not be overwritten,
 and it will not work with earlier versions of DirectX. This
is the problem that some are describing as not being able to calibrate
in Win95 because the program "flashes on, then immediately disappears".
Delete:
C:\win95\system\vjoyd.vxd
               \joy.cpl

Now, restart the system and install the DirectX version of your choice.
I have successfully reinstalled DirectX 1 through DirectX 3.0b (and also
the dreaded DX50. You may also need to re-install your newest
Monster3D/R3D drivers. If you use a combo 2D/3D card like the Intergraph
Reactor, Sierra Screamin' 3D or Hercules Stingray 128/3D, then it
-seems- likely you'll have to reinstall those drivers also (I am -not-
sure of this since I have not tested these cards).

 The above procedure was created because installing DX5 introduced
severe
 stuttering and a performance drop in iF22 (Imagic). The only way to
restore
the prior performance was by doing a full restore of Win95 (and my C:
drive)
from a previous backup with DirectX3.0b on it. All my other apps
performed
 about the same after installing DX5.

Thanks go to JD for the joystick info/testing and Eric J. Joiner Jr. for
some Win95 OSR2 info.

--
Sergey Zakharov

To reply, replace "nospam" with my organization.

BZZZZZZZ...
   sorry, wrong answer...... but thanks for playing  :)

hehee...I thought it would be this easy, too... but found differently.
in Reality...I ended up hacking the ***outta the registry, and deleting
the pertinent files, and doing a re-install of directx3.

 Handy^Man                                    
 IVGA 4924              ~~pulling for #8 in 1998 ! :)~~
 ICQ 3551448                    GOoooo #3 !!

--

 Handy^Man                                    
 IVGA 4924              ~~pulling for #8 in 1998 ! :)~~
 ICQ 3551448                    GOoooo #3 !!

Pardon the intrusion, but since you seem to be a DirectX guru, I thought I'd
 pose a question that I posted in a Win95 ng, and maybe you could help:
I have a peculiar problem with DirectX since I had to reinstall Win95.  When I
 go to open anything using DirectX I get an error "ddraw.dll cannot start.
 Check the file to determine the problem."  Dxinfo.exe gives me the same error.
 If I check the drivers with an OLD 3.0 program it shows direct draw not
 certified.  BUT if I use a new game progam (like Jedi Knight DirectX 5.0
 install) or run Dxsetup.exe from Win95, I get a screen flash and all the
 drivers, including direct draw, come up certified.  Then, WITHOUT reinstalling
 DirectX, progams work!  Something about running Dxsetup.exe is loading the
 certified driver.  I have reinstalled DirectX 5.0 several times from several
 sources, all with the same results.  Is there something missing from an .ini
 file or my register?  Can I add something to autoexec.bat or config.sys?  It's
 a real pain to have to run setup every time I want to use a direct x program.