Microsoft DirectX 9.0c End User Runtime June 2010 (x86)

Discuss & post Update Pack addons here.
Zephyr
Posts: 49
Joined: Sun Nov 22, 2015 4:53 pm
Location: London

Re: Microsoft DirectX 9.0c End User Runtime June 2010 (x86)

Post by Zephyr » Sat Jan 07, 2017 12:36 pm

I assume that this addon is intended to install the June 2010 updates for DirectX 9.0c

When I included it as the last addon to be processed by RVM_Integrator_1.6.1b2.1 it generated this error message:

Code: Select all

File Not Found! - File Not Found! F:\Windows XP Source [.NET]\I386\rvmtemp\svcpack.inf
Inspection of the i386 folder in my source revealed that the svcpack.in_ file had been overwritten with a new version whose only entry was:

Code: Select all

[SetupHotfixesToRun]
directx32.exe
When I examined the entries_directx32.ini file inside the addon it contained these entries:

Code: Select all

[EditFile]
I386\SVCPACK.INF,SetupHotfixesToRun,AddProgram

[AddProgram]
directx32.exe
Am I right in assuming that the entries_directx32.ini file is directing the integrator to look for the temporary file svcpack.inf in the wrong location so that

Code: Select all

[EditFile]
I386\SVCPACK.INF,SetupHotfixesToRun,AddProgram
should be instead:

Code: Select all

[EditFile]
I386\RVMTEMP\SVCPACK.INF,SetupHotfixesToRun,AddProgram
XP FOREVER!

Zephyr
Posts: 49
Joined: Sun Nov 22, 2015 4:53 pm
Location: London

Re: Microsoft DirectX 9.0c End User Runtime June 2010 (x86)

Post by Zephyr » Tue Jan 24, 2017 5:59 am

Having made a second attempt to build a CD with this addon I have concluded that the the problem may be due to an error in the svpack.ini file in the i386 folder of the source files. It may be advisable to edit the svcpack.ini file after the update pack and all the addons have been integrated to avoid similar scenarios recurring.
XP FOREVER!

User avatar
=[FEAR]=JIGSAW
Posts: 389
Joined: Mon Feb 18, 2008 11:54 am
Location: Cape Town, South Africa

Re: Microsoft DirectX 9.0c End User Runtime June 2010 (x86)

Post by =[FEAR]=JIGSAW » Fri Jan 27, 2017 4:27 am

I've never had that error back when I used to use this.

I've moved on to Win10 and im not looking back, so can't really test again

Dibya
Posts: 467
Joined: Sat Sep 12, 2015 9:34 am
Location: India

Re: Microsoft DirectX 9.0c End User Runtime June 2010 (x86)

Post by Dibya » Fri Jan 27, 2017 7:36 am

=[FEAR]=JIGSAW wrote:
Fri Jan 27, 2017 4:27 am
I've never had that error back when I used to use this.

I've moved on to Win10 and im not looking back, so can't really test again
Wow! Gonna be seen by MS Prying eyes and your personal datas will be sold to agencies like FBI.
What a bloody way ms found to earn money.
Using 10 remember put Spyware fixes

User avatar
=[FEAR]=JIGSAW
Posts: 389
Joined: Mon Feb 18, 2008 11:54 am
Location: Cape Town, South Africa

Re: Microsoft DirectX 9.0c End User Runtime June 2010 (x86)

Post by =[FEAR]=JIGSAW » Mon Jan 30, 2017 2:23 am

LOL, you people are funny that panic so much :D

Dibya
Posts: 467
Joined: Sat Sep 12, 2015 9:34 am
Location: India

Re: Microsoft DirectX 9.0c End User Runtime June 2010 (x86)

Post by Dibya » Mon Jan 30, 2017 11:19 pm

=[FEAR]=JIGSAW wrote:
Mon Jan 30, 2017 2:23 am
LOL, you people are funny that panic so much :D
:P

byrongaw
Posts: 6
Joined: Tue Apr 30, 2019 10:57 pm
Location: Norway
Contact:

Microsoft DirectX 9 0c End User Runtime June 2010 x86

Post by byrongaw » Mon May 13, 2019 12:15 am

All Microsoft system components, such as msiexec, use the system CRT, and this addon never touches the system CRT. Furthermore, this specific error is generally not caused by the CRT, but rather by a user of the CRT. So Im 99.9 sure that this error is unrelated to this addon.

Post Reply