"Roy Griffiths" <roy.gr...@supportservices.it> wrote in message
news:070601c35508$45329cb0$a401...@phx.gbl...
I've noticed when installing DirectX 9.0a / 9.0b from
either microsoft.com/directx or windowsupdate that it
stops half way through with the "not passed windows logo
testing" etc. (Although subsequently windowsupdate
history shows that file installed correctly & doesn't
offer it for donwload again). I've followed the support
guides to try scanning installed files, successfully (no
errors). Checked that crypto services are not running
Renamed catroot2 to oldcatroot2 etc.
Eventually installed XP as an upgrade over the full XP
install, and downloaded all patches again from
windowsupdate. All went well except...
When it came to install DX9.0a, the same problem with "not
logo certified" ocurred again, half way through... so I'm
a little stuck, as I thought from posts here that this was
the definitive-last-chance-get-ot-of-jail-free-card
solution...and it didnt work.
Hope you can help!
>.
>
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Roy Griffiths" <roy.gr...@supportservices.it> wrote in message
news:070601c35508$45329cb0$a401...@phx.gbl...
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Roy Griffiths" <roy.gr...@supportservices.it> wrote in message
news:0ad301c355c6$6912a120$a301...@phx.gbl...
07/28/03 14:16:11: dsetup32: Installed file
C:\WINDOWS\Driver Cache\i386\kswdmcap.ax
07/28/03 14:16:11: dsetup32: Installed file
C:\WINDOWS\Driver Cache\i386\wstcodec.sys
07/28/03 14:16:15: dsetup32: Installed file
C:\WINDOWS\System32\DLLCache\msvidctl.dll
07/28/03 14:16:16: dsetup32: ExecuteInf():
SetupInstallFromInfSection() failed, file is not signed
properly.
07/28/03 14:16:16: dsetup32: Installation of 'C:\DOCUME~1
\ADMINI~1\LOCALS~1\Temp\DX19A.tmp\dxbda.inf -
[WINXP_INSTALL]' failed, continue...
07/28/03 14:16:18: dsetup32: ExecuteInf(): Unable to
install C:\DOCUME~1\ADMINI~1\LOCALS~1
\Temp\DX19A.tmp\dxntunp.inf - [WINXP_BDA_MIGRATION], error
= 995
07/28/03 14:16:18: dsetup32: ERROR: Installation
of 'C:\DOCUME~1\ADMINI~1\LOCALS~1
\Temp\DX19A.tmp\dxntunp.inf - [WINXP_BDA_MIGRATION]' failed
07/28/03 14:16:21: dsetup32: ExecuteInf(): Unable to
install C:\DOCUME~1\ADMINI~1\LOCALS~1
\Temp\DX19A.tmp\dxntunp.inf - [WINXP_MIGRATION], error =
995
07/28/03 14:16:21: dsetup32: ERROR: Installation
of 'C:\DOCUME~1\ADMINI~1\LOCALS~1
\Temp\DX19A.tmp\dxntunp.inf - [WINXP_MIGRATION]' failed
07/28/03 14:16:21: dsetup32: start finalizing: phase: 321 -
203, total: 447 - 329
07/28/03 14:16:21: DXWSetup: DSetupCallback(): Phase = 3,
Steps = 0
07/28/03 14:16:21: dsetup32: SetupForDirectX: Restoring
Backups
07/28/03 14:16:21: dsetup32: Installation ended with
value -5 = File not copied
07/28/03 14:16:22: DXWSetup: WM_APP_ENDINSTALL
07/28/03 14:16:22: DXWSetup: ~CDXWSetup()
07/28/03 14:16:23: DXWSetup: Deleted file
C:\WINDOWS\System32\directx\websetup\dsetup.dll.
07/28/03 14:16:24: DXWSetup: Deleted file
C:\WINDOWS\System32\directx\websetup\dsetup32.dll.
07/28/03 14:16:24: DXWSetup: Deleted file
C:\WINDOWS\System32\directx\websetup\inseng.dll.
I hope this helps...
Regards,
Roy Griffiths
>.
>
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Roy Griffiths" <roy.gr...@supportservices.it> wrote in message
news:486101c35679$c96c85f0$a001...@phx.gbl...
Went to the DirectX website at Microsoft and tried to
install the DX9.0b runtime. It fell over installing
the "ipsink" file, which unfortunately is the same place
it always falls over at. Same error - "not Windows
certified" problem...
Maybe I'm doing something wrong, but I have been closely
following the guides that have been available. What next?
I ran through the upgrade Windows XP over installed
Windows XP scenario & added SP1. Then ran through DX9.0b
install (unsuccessfully). Then thought"let's do some
checks" - checked crypto services were running (they were)
but restarted the service through the Systems panel in
Control Panel. Ran DX9.0b runtime install again...and it
worked fine.
I'm certain this didn't work before but can't think what
else has been changed on the machine that might have
permitted the install this time, and not any other!
Regardsless, thank you all for your help with this issue.