FIXED!! I figured out how to fix the Creative Dxr3 Win2k dr

[JediBaron 0]

After the crappy release of Creative's Dxr3 Win2000 drivers, I was rather discouraged that I would ever get my DVD running outside of the NT4 drivers with beta Hollywood drivers. Well today I finally decided to experiment with them and I figured out how to get them to work.

 

First thing is to install and then remove the NT4 drivers. I'm not sure how neccesary this step is, but I did it just to make sure I'd have the registry entries for the Creative DVD player. You'll have to reboot after that.

 

Second thing - using the Win2k device manager install the Creative Win2k Beta drivers. (you'll have to reboot again)

Now as all of us know who tried this driver when it came out, this now completely f**ks up the media player.

 

So what you have to do next is literally 'break' the Win2k supported drivers. That's the device that allows Win2k to play DVD's natively. You do this by running the registry editor. Search all the data values for 'dxr3'. Now in my registry this was the first one. A classid key with 4 parameters:

default= . . .

CLSID= . . .

FilterData= . . .

FriendlyName='Creative Labs Encore Dxr3 Filter'

Just delete the entire key with all 4 parameters. This will fix the media player (you can verify by trying a couple of mpeg movies in it)

 

Lastly, just install the Creative PC-DVD Player. The autocalibrate doesn't work right anymore, but you can just manually adjust it to get your screen right.

 

Well, that's it. I'm now running DVD's without any adverse affects using the Creative drivers.

 

If anyone needs the driver package please let me know and I can ICQ or email it to you

[DeadCats 0]

Congrats on getting them hacked!

 

Personally, I think I'll just stay with the beta Sigma/Dxr2/Dxr3 hack until some Creative gets off their collective arse and publishes some good drivers (waiting...waiting...).

 

------------------

"While it is true that technology waits for no man;

stupidity will always stop to take on new passengers."

[JediBaron 0]

Well I have an interesting little update. I just installed it on a fresh copy of Win2k. First off, the NT4 drivers HAVE to be installed and then un-installed. This gives you the needed registry entries for the player to install. After that, I installed the Creative Win2k drivers (I actually installed these first to test it out, but had to install them again to overwrite the NT4 driver files which have some of the same file names)

One interesting side note on the clean install was that the autoconfigure on the screen worked just fine, so maybe it was just all my experimenting that caused it not to wok before.

 

Later,

JediBaron

[DeadCats 0]

Quote:

Originally posted by JediBaron:
Well I have an interesting little update. I just installed it on a fresh copy of Win2k. First off, the NT4 drivers HAVE to be installed and then un-installed. This gives you the needed registry entries for the player to install. After that, I installed the Creative Win2k drivers (I actually installed these first to test it out, but had to install them again to overwrite the NT4 driver files which have some of the same file names)
One interesting side note on the clean install was that the autoconfigure on the screen worked just fine, so maybe it was just all my experimenting that caused it not to wok before.

It would be interesting to note what effect the Creative beta drivers would have on a truly clean install of Win2k, doing the NT4 install/uninstall, then the Creative beta drivers install, WITHOUT doing the first Creative beta install/uninstall.

------------------
"While it is true that technology waits for no man;
stupidity will always stop to take on new passengers."

[JediBaron 0]

Well, from all my monkeying around on my other system with the drivers. I can say with a 99.9% confidence rate that it would make absolutely no difference at all. The NT4 drivers don't react at all with Win2k drivers. They simply manually add all the registry entries and then manually copy all of the driver files into the system32 and system32/drivers directories.

The NT4 drivers never interact with Win2k or the Dxr3 card at all. Win2k will not even run them. They simply just add the registry entries so that the Creative DVD player's install program thinks that the dxr3 is installed. The card is actually run by the Win2k driver.

But you MUST install the Win2k drivers after the NT4 drivers because many of the file names are the same and the Win2k driver can not run with the NT4 files as they don't work at all in Win2k (as I said above, win2k is unable to run them at all).

 

PS: Actually I should rephrase that. The actual driver files (the *.drv files in the system32/drivers directory) for NT4 will run in Win2k as they are nearly the same files. The files that don't work are the dll's and support drivers in the system32 directory. Those are the ones that have to be overwritten by the Win2k driver. - Just thought I should clarify that

 

[This message has been edited by JediBaron (edited 16 July 2000).]