need to install redist. directx 9.0c? look here

[infiniti_guy]

Ok.. upon more research. from my DirectX.cab in 9.0b, I have a 1.75MB file...
From DXNT.cab, I have a 1.87MB File... Since I am running XP Pro, I suspect I need the 1.87MB file... And my Win/Sys32 quartz.dll is 1.87MB, so I'm probably ok there. (I'm going to directly replae the quartz.ll file anyway with my known 9.0b)

The only thing I can think of now then is a Sage 2.2.2 Bug. What are the performance benefits of 2.2.2? I remember reading on Cayars something about it having performance benefits... Is this for using NVIDIA VPP with FFDSHOW via the Post Processor setting in the properties file? Anything else?

[Wheemer]

Now I'm confused... I had not realized the newer 9.0c does have two versions in it. The one inside DirectX.cab is 1.75 mb and the one inside dxnt.cab is 1.87...



I think the most important thing is that this problem doesn't seem to appear with either of them... it's only apparent with the 1.22 mb version...

FYI I've always been using the verion from the directx.cab which I've attached...

[infiniti_guy]

DFA, yes, I think you are right from waht I gather... Ok... Doing the DX9.0b quartz.dll from DXnt.cab was a no go... I'm going to stick with the 9.0c redist normal install. My problem is with Sage 2.2.2, I think.

[Wheemer]

BTW you do not need to replace the file in safe mode... you can run "regsvr32 -u quartz.dll" in the run box (without the quotes) then replace the quartz.dll with the version I posted here. Then type "regsvr32 quartz.dll"

and your set...

[kny3twalker]

but my point of installing the redist. is that there may be other fixes
running the version from SP2 and the older quartz.dll may not be the only thing changed
I am having much better luck after using the directx eradicator and then install redist directx 9 c but do this carefully if you try
I just do not understand why you cannot update directx without reversing to 8.1

[Wheemer]

true... But I am having no other problems, besides that annoying jerky thing. It does seem completely pointless having these restrictions on the Directx installs. But then again, most of the quirks with Microsoft product seem idiotic. And also, with the amount of people employed by Microsoft, supposedly the brightest and best programmers, I can't believe how long it is between their updates.

[tealcomp]

I followed your suggestion and it worked great for me; I did use something called Directx9 Uninstaller but from what I can tell it just took me back to v8.1. I still had the problem with it not wanting to reinstall v9.0c, that is until I overlaid with your setup file and it worked like a champ..

-Dan

Originally Posted by kny3twalker

damn you are right I cannot get anything to work now either
I have tried to install it over the top of my current install and it would not

what a PITA

funny thing was I was sure this would work
I was trying to use a program last night to allow the install of any version of directx
DirectX Eradicator
but of course this did not work
it instead uninstalled my version of directx9.0c thats all
but I could not install the new updated version
so I finally tried changing out the first attachment file listed and
then I could install directx9.0c redist
I am not sure why it is such a pain to install the update
maybe I should contact M$ about this
this seems stupid
to need to uninstall it first
but I thought it would not be limited to my issue and sorry about that

[Wheemer]

BTW you do not need to replace the file in safe mode... you can run "regsvr32 -u quartz.dll" in the run box (without the quotes) then replace the quartz.dll with the version I posted here. Then type "regsvr32 quartz.dll"

and your set...

This comment by myself has proven to be incorrect. I was previously running my system with "Windows File Protection" turned off. I've just refommatted with a completely normal XP SP2 install and Windows is constantly replacing the quartz.dll back to the problem version.

So the instructions should return to "Please replace the Quartz.dll under Safe Mode". I've done that and it's no longer replacing the file.

Thought I should make sure the info was correct.

[salsbst]

Just "upgraded" to XP SP2 on our main HTPC. I already had DX 9.0c. I hit the stutter bug. Thanks to this thread, I was able to boot to safe mode and replace quartz.dll, register it and the problem seems to be solved.

[infiniti_guy]

Just curious, why did you upgrade? Did you upgrade from SP1? I just wonder why go through the hassle...

[salsbst]

I have no great answer to your question of why I upgraded.

I do like to stay current, and I had waited quite a while to see how others' experiences played out.

I knew I would probably face this bug, and just said to myself "What the h*ll."

I made an image of the HPTC (using Ghost) before launching SP2, so I knew that if things went badly I could go back.

I did upgrade from SP1. Again, no good reason -- it was upgrade night in our household, with several machines going through Windows Update upgrades, lots of Ghost'ing... I just felt it was time.

[jphhughes]

I would like to confirm on step in the copying of this DLL. I downloaded the 1.87MB (1,962,496) ver 6.5.1.902. In safe mode I used this dll to replace the existing version. Dxdiag report that the 1.87MB version is the one being sued. However I never registered it using the "regsvr32 quartz.dll" command , is that a necessary step?

[Wheemer]

Nope, that is not required... Any registering of files was only part of the improper directions I wrote earlier.

The safe mode replacement is all you need.

Any as far as upgrading to SP2, why wouldn't you want to keep your software current? It's not like SP2 has any drawbacks... Except for this one easily fixable problem.

[infiniti_guy]

I don't think Windows is the best tool to have for networking/firewall. I fear that it may cause network traffic interrupts within Windows that could affect Sage and Sage Clients. But I myself have no experience with SP2, so I can only speak from past experience with MS. I can say that most PC manufacturers suggest only downloading the security updates because other features, etc. have potential to cause problems. With as many issues as there currently are running Sage in Windows, why take the extra risk and run features that may not do anything good.

I would say, however, that if you don't have a HW firewall and don't know much about other SW firewalls out there, MS is better than nothing, and it integrates a few other tools like Pop-up blocker and malicious IE SW blocker, etc. From what I have seen, that seems to be the only reason to upgrade... but I just wanted to see if anyone had found some other benefit.

[cmaffia]

Does this thread have anything to do with my problem with burning sage recordings to DVD? Ever since I upgraded my workstation (seperate PC from Sage) to SP2, I get this wicked jerkiness when panning on all my DVD recordings.

[kny3twalker]

that was a weird problem I was having as well
I moved around pci cards until the pvr cards were sharing no IRQs, updated to the newest official drivers, updated to the newest beta SageTV and did this directx fix

I still have a couple recording which I have not watched yet or deleted that have this BS in it

almost every other second, right?
tick, tick, tick, (damn annoying)

[infiniti_guy]

I just built a new Client with SP2... Got a wierd DirectX Reinstall error.. Wouldn't let me reinstall... tried some other tools to no avail. Tried the DLL in the first post.. and the reinstall worked.

I'll post back here tomorrow if I still get the Sage Reinstall DirectX error.

FYI - I don't have a decoder problem (using verified HW-SW platform, the only change is SP2).