DX9, Win2K and OHCI (1394/Firewire/iLink)

[David Winter]

Offline prepped msg - will be checking Google when logged on.

I recall some threads a while back about DX9 screwing up folk's capture
tools - especially OHCI.

I've just had occasion to load Ulead VS7 SE DVD as a basic editor for MPEG
files, but I think it installs DX9 - or it could have been DVD Factory that
installed it. I have a PC that's managed to go terminal on me (fatal STOP
screen on boot up), and while I have used the repair console and fast repair
utilities - can't fix it. I'm in the process of putting in an A06 which will
serve as a back-up unit ... but the need has overtaken me - oops. I don't
mind the rebuild - it's sometimes good, but I loathe the authentication
calls that become necessary.

I understand that DX9.1 solved the probs with 9.0. Could someone please post
a URL for a D/L (non auto install) site for DX9.1 or later.

Many TIA

Cheers

David Winter
Armadale
Western Australia

[Paul Bowlay]

"David Winter" <winterdspammertrap@icenet.com.spamtrapper.invalid> wrote
I understand that DX9.1 solved the probs with 9.0. Could someone please post a URL for a D/L (non auto install) site for DX9.1 or later.

Is DirectX 9.1 a beta version? I can only find the full download of 9.0b for
download, at the following URL: http://tinyurl.com/hwco

I'll install 9.0b before going back to 8 to see if it fixes my capture problem.

[Scott Alfter]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In article <3f3b5316$1@usenet.per.paradox.net.au>,
David Winter <winterdspammertrap@icenet.com.spamtrapper.invalid> wrote:I recall some threads a while back about DX9 screwing up folk's capturetools - especially OHCI.I've just had occasion to load Ulead VS7 SE DVD as a basic editor for MPEGfiles, but I think it installs DX9 - or it could have been DVD Factory thatinstalled it. I have a PC that's managed to go terminal on me (fatal STOPscreen on boot up), and while I have used the repair console and fast repairutilities - can't fix it. I'm in the process of putting in an A06 which willserve as a back-up unit ... but the need has overtaken me - oops. I don'tmind the rebuild - it's sometimes good, but I loathe the authenticationcalls that become necessary.

I have a couple of Orange Micro iBot FireWire webcams that cause the
computer to bluescreen when a filter graph using them is stopped under Win2K
SP3 and SP4. The problem is a buggy FireWire driver (ohci1394.sys)
introduced with SP3. If you replace this file with the version included
with SP2, the camera works properly. If you're capturing from a FireWire
device (like a DV camcorder), maybe you're running into a similar problem.

The version of %systemroot%\system32\drivers\ohci1394.sys should be
5.0.2195.2924 or earlier. If you have a newer version, you can extract the
file from the full SP2 download available from Microsoft...or you can get
just the one file you need here:

http://alfter.us/files/Win2KSP2ohci1394.zip

Unzip it into the root directory, reboot into "safe mode with command
prompt," and overwrite %systemroot%\system32\drivers\ohci1394.sys with the
unzipped file. This patch will hold until the next service pack, at which
time you might need to reapply it if Microsoft still hasn't fixed it;
overwriting the file in safe mode keeps Win2K from immediately replacing the
downloaded file with the newer (buggy) version. Uninstalling/reinstalling
your FireWire card might also necessitate reinstalling the older file (could
be an issue with notebooks where you're constantly plugging/unplugging a
CardBus FireWire adapter, but it shouldn't be such a big deal with
desktops).

_/_ Scott Alfter
/ v \ salfter@salfter.dyndns.org
(IIGS( http://alfter.us Top-posting!
\_^_/ pkill -9 /bin/laden >What is the most annoying thing on Usenet?

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/O9ysVgTKos01OwkRAtDYAKCUxri+ebgiItULhT8PLO6oA6SPZgCeJagD
5myzR1HIJRFYlsH4sEJ0cag=
=pzS5
-----END PGP SIGNATURE-----

[Keith Clark]

Paul Bowlay wrote:
"David Winter" <winterdspammertrap@icenet.com.spamtrapper.invalid> wrote I recall some threads a while back about DX9 screwing up folk's capture tools - especially OHCI. Now THIS is interesting! I connected my Panasonic camcorder to my firewire port a few weeks back to do some capturing and it didn't work anymore. And yes, the only difference to my setup was that I installed DirectX 9 recently. I'll have to restore an old snapshot of my system (DirectX 8) to see if 9 was the culprit! Stay tuned...

What I'm hearing on the Nvidia newsgroup is that the bug affects PAL users. Of course,
that's just hearsay.

In my case, NTSC capture still works fine with the onboard OHCI Firewire on my
motherboard...

Win2K, DirectX 9b.

YMMV....

--Keith

[Paul Bowlay]

> What I'm hearing on the Nvidia newsgroup is that the bug affects PAL users

Which I am. :) I've read another post here about using an older version of
the firewire driver, so I'll try that first before testing the DirectX route.