DirectX8 hack/ 98lite hack: Please read

SonyEPM wrote on 3/29/2001, 4:10 PM
Some users have report that they are having trouble
installing Microsoft DirectX8 and the Microsoft DV updater,
both of which are REQUIRED to be installed before you can
install Vegas 2.0d.

We offer the following advice, and suggestions...

1)Run the hack posted earlier in this forum, and you will
be running an unsupported version of Vegas 2.0d. We cannot
provide tech support or otherwise help you if you remove
mandatory system components. Just because you can bypass
the component check doesn't mean things our application
will work correctly.

2) Those of you still having problems installing the 2
DirectX components could try this:

http://download.microsoft.com/download/win2000pro/redist/8.0
a/W9X2KMe/EN-US/DX8a_redist.exe

It is a much bigger download (@25Mb)than the separate
components we link to from our site, but this single
package listed above has all needed components for all
supported OSs. Download it, install it, reboot, and try re-
installing Vegas 2.0d. This is the exact same file we use
on our 2.0d disc image, but to lighten the download we
opted for the separate DX components for web-updaters, as
suggested by Microsoft.

We have run many hundreds of install tests of DirectX8 and
the DV updater on the supported OSs and have not seen the
problems reported here. Obviously there IS a problem
somewhere, and we continue to monitor this issue closely.

3) I see that some of you are using a modified version of
Windows 98 known as 98Lite. This is an unsupported OS.
Again, even if you are able modify the registry/other OS
components and install our products, they are officially
unsupported. All SF apps should be used only with the
supported OSs as defined in the requirements.

----------------------
To recap:
Hack the OS registry or our software and all bets are off.

Thank you for you patience- I believe once you have
successfully completed a valid installation of Vegas 2.0d
and its required components, you will feel the update is
worth the trouble. I hope the above is helpful and
informative. Good luck.



Comments

danrawls wrote on 3/29/2001, 8:14 PM
Having been in software development myself I agree 100
percent.
FormerSOFOguy wrote on 4/5/2001, 1:59 AM
Hey. heh. I'm not running a hack. This is a new install of
Win2000 (no 'lite' or anything), and I'm still getting the
problem. DX 8.0a runtime installed, then the DV updater
installed (Five times to try to get around this.) ... No
go. VidCap and Vegas still insist I haven't installed the
updater.

Really. I swear I'm doing nothing special or out of the
ordinary. Clean Win2000pro, DX 8.0a runtime, DV Updater,
from the links provided. Then the regular, un-hacked vegas
MSI.

Clean, pure, 100%.

Still won't do it.

I still live in Madison, I can come down to 1617 Sherman
with my box and show ya. :)

FormerSOFOguy wrote on 4/5/2001, 2:02 AM
P.S., the redist file, the whole 25mb shebang, didn't fix
it either.
SonyEPM wrote on 4/5/2001, 9:32 AM
Try running setup and not the MSI.
Scott Sorkin wrote on 5/7/2001, 11:21 PM
I've followed the advice posted by Sonic Foundry in this
thread; I'm running Win98 (4.10.1998) I have installed the
full MS Redist of DirectX8, and rerun the Vegas Install.
It's not working. I continue to get the message that I must
install DirectX8 before installing Vegas. Please post the
information I need to install Vegas 2.0d if there's a way
to do it.
Sunray wrote on 5/8/2001, 9:09 AM
One issue that we've seen on some systems, is that the DV
Updater from Microsoft doesn't really do what's expected.
Our installer is looking not only for an installation of
DX8 or higher...it also looks for the existence of the file
msdv.sys in the folder [WindowsFolder]\system32\drivers.
Normally, the DV Updater installs this file in the
appropriate location. However, not always. Occasionally,
this file is placed in the folder [WindowsFolder]\Driver
Cache\i386 on Win2k systems, or an equivalent location on
ME and 98 systems.

If you're still having problems with DX8 detection after
following our earlier advice, I'd recommend doing a file
search in your Windows folder for the file msdv.sys. If
found, copy it into your [WindowsFolder]\system32\drivers
folder. Then try to install our software again. Please
let us know if you still have problems after this.
DaveP wrote on 5/9/2001, 12:31 PM
Hello Wesley:


Correct me if i am wrong but i do not beleive that Windows
98 4.10.1998 is Windows 98SE. I beleive that 98SE is
denoted with 4.10.2222. Since 98SE is a requirement to the
2.0d update this could potentially be the problem in your
case. I have only seen this problem happen in this
scenario.