[Joseph_sw]

a fews days ago i decided to download the latest known directX redist (Aug 2009)
download link: http://www.microsoft.com/downloads/details...b1-442d8712d553

after installing it on other winxp, a thought to see if it would still exhibit the same type of error as previous redist on win98se, occured to me.
i followed the thought and proceed to install it on my win98SE system, and to my surprise it said "Installation Complete" !

couldn't believe my eyes, then as confirmation i look for DirectX.log file, it also have this following lines:

11/16/09 13:32:13: DXSetup: No command line switch
11/16/09 13:32:13: DXSetup: StartWizard()
11/16/09 13:32:14: dsetup32: IsWow64(): Windows 2000 or Windows 9x.
11/16/09 13:32:16: DXSetup: CDXWSetup()
11/16/09 13:32:17: DXSetup: start installation
11/16/09 13:32:17: DSETUP: DirectXSetupA(): hWnd: 00000554 dwFlags: 02010098


11/16/09 13:32:17: dsetup32: === SetupForDirectX() start ===
11/16/09 13:32:17: dsetup32: Sep  4 2009 17:32:16
11/16/09 13:32:17: dsetup32: DXSetupCommand = 0.
11/16/09 13:32:17: DXSetup: DSetupCallback(): Phase = 0, Steps = 0
11/16/09 13:32:17: dsetup32: DirectXSetupIsJapanese == 0
11/16/09 13:32:17: dsetup32: DirectXSetupIsJapanNec == 0
11/16/09 13:32:17: dsetup32: Installing on Win98
11/16/09 13:32:17: dsetup32: IsWow64(): Windows 2000 or Windows 9x.
11/16/09 13:32:18: dsetup32: CLR version number = 2.0.50727
11/16/09 13:32:18: dsetup32: Checking the version: HKLM\software\microsoft\directx\Version
11/16/09 13:32:18: dsetup32: Version in registry = 4.09.00.0904
11/16/09 13:32:18: dsetup32: Version in DLL	  = 4.09.00.0904
11/16/09 13:32:18: dsetup32: RC in registry = 00, RC in DLL = 00
11/16/09 13:32:18: dsetup32: Core components have been installed already, core installation is skipped.
11/16/09 13:32:18: dsetup32: IsIA64(): Windows 2000 or Windows 9x

... ( *abridged* )

11/16/09 13:33:13: dsetup32: SetupForDirectX: InstallPlugIn() Succeeded.
11/16/09 13:33:13: dsetup32: start finalizing: phase: 62 - 62, total: 0 - 62
11/16/09 13:33:13: DXSetup: DSetupCallback(): Phase = 3, Steps = 0
11/16/09 13:33:14: dsetup32: Installation ended with value 0 = Installation succeeded
11/16/09 13:33:14: DXSetup: WM_APP_ENDINSTALL
11/16/09 13:33:14: DXSetup: ~CDXWSetup()

my system:
win98SE with 98SE2ME (Option 2)
unofficial MSVC redist
MS .Net2
Previous DX-9 redist that installable on win9x
RP9
KernelEx Final-2
MD IE 6sp1 Component Update (2.9)
M()zart' userenv.dll


i found it weird, that it doesn't end up like those unsupported dx redist before.

[jimmsta]

When the latest redist came out, I looked through the cab files, and it looks like there's nothing new for 9x, but they still include all the compatibility stuff for 9x/2k/XP gold/XP SP1/XP SP2+, as well as updated dx9c_xx files for Vista and 7. I do find it interesting that the installer is compatible with 9x. Could be kernelex though.
<img style="position: absolute; left: 0px; top: 0px; right: 0px; bottom: 0px; margin: auto;">

[MDGx]

Must be KernelEx that provides compatibility with 98/ME, because MS has removed 9x support from the DX installer long time ago. [December 2006 ?]

Anyway, even if the installer works ok with 9x OSes, there are no new files to be installed since Dec 2006.

[Offler]

the image is not dx redist, it is software development kit. Some sort of libraries which can be used for SW development. They might install new files.

Also DX redist from dec 2006 was the last one which was able to be installed on new fresh installation of Win98, but when you already had any previous DX9 installed you was also able to install newer package until november 2007. From my experience some new files were still available from this package, but i am not sure about it now.

[CharlesF]

MDGx, on Nov 16 2009, 09:22 PM, said:

there are no new files to be installed since Dec 2006.

Hi MDGx,
what about the Unofficial DX 9.0c August 2007 Redist Full + MDX you link on your site?

What does it provide more?

[MDGx]

CharlesF, on Nov 21 2009, 03:49 PM, said:

what about the Unofficial DX 9.0c August 2007 Redist Full + MDX you link on your site?

What does it provide more?

I have received a PM from some1 who actually took time to analyze that file at my site, and he said it does not contain anything useful, because the last official MS update as of Dec 2006 already contains/installs all necessary files. So I removed the link to it from my DX9 page.

But the file itself is still available [I won't remove it], if any1 cares to test it:
http://www.mdgx.com/files/DX90C.EXE


HTH

[CharlesF]

MDGx, on Nov 22 2009, 02:55 PM, said:

he said it does not contain anything useful

I have compared the two files ('DirectX_Dec2006_redist' & your 'Unofficial DX90C'):
-> there is 4 different files

• dsetup32.dll
  
• dxdllreg_x86.cab
  
• DXSETUP.exe
  
• dxupdate.cab

but well, could be only because of the new files,
-> and 11 new files (with new content)

• APR2007_d3dx10_33_x86.cab
  
• APR2007_d3dx9_33_x86.cab
  
• APR2007_XACT_x86.cab
  
• APR2007_xinput_x86.cab
  
• AUG2007_d3dx10_35_x86.cab
  
• AUG2007_d3dx9_35_x86.cab
  
• AUG2007_XACT_x86.cab
  
• FEB2007_XACT_x86.cab
  
• JUN2007_d3dx10_34_x86.cab
  
• JUN2007_d3dx9_34_x86.cab
  
• JUN2007_XACT_x86.cab

but to say they are useless ...

[MDGx]

CharlesF, on Nov 22 2009, 04:41 PM, said:

MDGx, on Nov 22 2009, 02:55 PM, said:

he said it does not contain anything useful

I have compared the two files ('DirectX_Dec2006_redist' & your 'Unofficial DX90C'):
-> there is 4 different files

• dsetup32.dll
  
• dxdllreg_x86.cab
  
• DXSETUP.exe
  
• dxupdate.cab

but well, could be only because of the new files,
-> and 11 new files (with new content)

• APR2007_d3dx10_33_x86.cab
  
• APR2007_d3dx9_33_x86.cab
  
• APR2007_XACT_x86.cab
  
• APR2007_xinput_x86.cab
  
• AUG2007_d3dx10_35_x86.cab
  
• AUG2007_d3dx9_35_x86.cab
  
• AUG2007_XACT_x86.cab
  
• FEB2007_XACT_x86.cab
  
• JUN2007_d3dx10_34_x86.cab
  
• JUN2007_d3dx9_34_x86.cab
  
• JUN2007_XACT_x86.cab

but to say they are useless ...

From what I remember from way back when...

Dxsetup.dll + dxsetup.exe are from a previous DX install package, in order to allow unattended install [command line switches are enabled]. That's because the newer dxsetup.* files from official MS DX9 package won't allow unattended install [command line parameters are disabled]. More info here:
http://www.appdeploy...l_pf.asp?id=169
and here:
http://www.msfn.org/board/directx-9c-silen...allation-t.html
and here:
http://www.msfn.org/board/index.php?s=&...st&p=157335
and here:
http://www.msfn.org/board/index.php?s=&...st&p=163905

Actually those cab files [xact, dx9 x64 + dx10] apply only to NTx OSes [2000/XP/2003/Vista/2008]. They have no meaning for Windows 9x/ME.
And I don't think APR2007_d3dx9_33_x86.cab, AUG2007_d3dx9_35_x86.cab + JUN2007_d3dx9_34_x86.cab [managed dx9 newer than December 2006] work with 9x OSes either. Unless some1 would like to test them, and *if* they do work, please post here. Tx!

But you are right [thanks for reminding me], looks like the unofficial DX 9.0c package is not that useless after all...
Dxsetup.exe + dxsetup.dll allow unattended install with command line switches.
So I just put back the link to unofficial DX installer:
http://www.mdgx.com/files/DX90C.EXE
here:
http://www.mdgx.com/dx.htm#DX9

HTH

This post has been edited by MDGx: 26 November 2009 - 10:28 PM

[Advanced User]

MDGx, on Nov 22 2009, 04:55 PM, said:

I have received a PM from some1 who actually took time to analyze that file at my site, and he said it does not contain anything useful, because the last official MS update as of Dec 2006 already contains/installs all necessary files. So I removed the link to it from my DX9 page.

Yes, it was me. I have checked this file and it really does not includes any new files for 9x since last October 2006 release. It was just compilation from old 9x cabs from October release and other cabs from later releases until August 2007, but really no files after October 2006 is installed. Last installed file is d3dx9_31.dll, d3dx9_32.dll and other new files are skipped. All the same for December 2006 release, which is considered the last, but it not last really, as it also does not installs any new files after October release. It was just fault of MS to include cabs for 9x in that release. And even more, web installer of DirectX also installs files in 9x only prior to October 2006 versions. Therefore latest release of DirectX for 98/ME is October 2006. I have attached log of installation of August 2007 in 98SE if you interested.

And about unattended install, this package does not contain any old or tweaked files for unattended purposes, all setup related files from it (dsetup32.dll, dxdllreg_x86.cab, DXSETUP.exe, DSETUP.dll and dxupdate.cab) were taken from original August 2007 release, and digital signs of it dated by 20.07.2007. I have compared both files from unofficial and original packages in WinHex and it completely identical, therefore its looks like this package is totally useless.

Attached File(s)

•  Directx.rar (6.8K)
  Number of downloads: 8

This post has been edited by Advanced User: 09 February 2010 - 10:07 PM

[CharlesF]

Advanced User, on Feb 10 2010, 04:58 AM, said:

Last installed file is d3dx9_31.dll, d3dx9_32.dll and other new files are skipped.
... therefore its looks like this package is totally useless.

Hi Advanced User,

could you read here Post #17:

RetroOS, on Jul 10 2008, 06:17 AM, said:

you need .NET Framework 1.1 and/or 2.0 installed, otherwise the updates won't even install...

and here Post #22:

RetroOS, on Jul 14 2008, 06:58 AM, said:

Any DirectX releases after December 2006 require .NET Framework installed, otherwise nothing much will install in Windows 9x from the DirectX update.

Is it possible that it is the reason why those updates are skipped?

[MDGx]

From what I recall, .NET is needed only for Managed DirectX (MDX) [DX.NET] installation.
"Normal" DX APIs should install properly no matter if NFR is installed or not.

But with your (guys) help [tx!], now I know exactly what that old unofficial DX update contains.
And because it's buggy + obsolete, I'll make a new one with Iexpress, to include all MDX libraries [up to date], delete all NTx libraries, and add a better dxsetup.exe with support for unattended command line parameters [which was the primary role of that update].
I just need to find that dxsetup.exe 1st.

[submix8c]

You need DXSETUP ver 4.8.1.901 (attached).

Was used in the (defunct) UBCD/AutoPatcher for Win98SE topics.

HTH (attached ZIP)

Attached File(s)

•  dxsetup.zip (25.14K)
  Number of downloads: 11

[Advanced User]

CharlesF, on Feb 10 2010, 09:35 PM, said:

Is it possible that it is the reason why those updates are skipped?

No, it is not reason, because last version of Managed DirectX was included in April 2006 release of DirectX, later it was deprecated and has been replaced by Microsoft XNA, therefore all releases after October 2006 are totally useless for 9x, in spite of it can be installed with Framework or without it. Seems like August 2007 pack was created only by reason that it is latest version which can be installed normally in Windows 98 (not considering that it useless), newer releases have repacked cabs incompatible with Windows 98, but it installs ok in Windows ME although (i did not check February 2010). Author of topic says that June 2008 release supports Windows 98 but he forgot specify that it related only to Web Installer but not to full redist. Web Installer actually supports Windows 98 but does not install any new files than October 2006 release.

[PROBLEMCHYLD]

MDGx, on Feb 10 2010, 03:29 PM, said:

From what I recall, .NET is needed only for Managed DirectX (MDX) [DX.NET] installation.
"Normal" DX APIs should install properly no matter if NFR is installed or not.

But with your (guys) help [tx!], now I know exactly what that old unofficial DX update contains.
And because it's buggy + obsolete, I'll make a new one with Iexpress, to include all MDX libraries [up to date], delete all NTx libraries, and add a better dxsetup.exe with support for unattended command line parameters [which was the primary role of that update].
I just need to find that dxsetup.exe 1st.

Will you add the KB904706 update and the DX9CPL.EXE?

[MDGx]

PROBLEMCHYLD, on Feb 12 2010, 03:46 PM, said:

MDGx, on Feb 10 2010, 03:29 PM, said:

From what I recall, .NET is needed only for Managed DirectX (MDX) [DX.NET] installation.
"Normal" DX APIs should install properly no matter if NFR is installed or not.

But with your (guys) help [tx!], now I know exactly what that old unofficial DX update contains.
And because it's buggy + obsolete, I'll make a new one with Iexpress, to include all MDX libraries [up to date], delete all NTx libraries, and add a better dxsetup.exe with support for unattended command line parameters [which was the primary role of that update].
I just need to find that dxsetup.exe 1st.

Will you add the KB904706 update and the DX9CPL.EXE?

Yeah, that's a good idea.
May take a while, thou.
I'll post it here when it's done.

HTH

[RFMaster]

I can tell you something about DX9
1 or 2 years ago i install Call of duty 4 on XP
(but thes days i have only DX9 feb 2006)
and when i try to play game shows me some message
the file d3dx9_3x.dll(x i don't remember what number was) so
i just copy d3dx9_31.dll and rename to d3dx9_32.dll,d3dx9_33.dll
and d3dx9_34.dll and is work believe you or not

i can't see any diffetrence between d3dx9_31.dll and d3dx9_33.dll
only diffetrence is:
d3dx9_33.dll try to use EncodePointer and DecodePointer from XP kernel

you can test this
but don't be critic before test.

sorry if my english bad

This post has been edited by RFMaster: 27 May 2010 - 05:44 AM

[HardDriv'n]

since this thread has been bumped already...

Not sure if it's pertinent, but until recently all I could get to install on Windows ME was the 'Dec, 2006' redistributable. After downloading, and installing the latest from 'Feb, 2010' on XP, I tried the same version on ME.

It installed correctly, and seems to be working fine.

[MDGx]

Must be KernelEx that adds necessary NTx API functions for the newer DX installers to work properly.
But even if those installers work ok [with help from KernelEx], that doesn't mean that DX libraries [DLLs] actually install, because 9x [98/98SE/ME] DLLs have been removed by M$.
"Virgin" [without any "tweaks" installed] 98/98SE/ME OSes stop with an error [OS not supported] message and do not proceed with installation. This is the default behaviour built into the installer by M$ to detect 9x OSes and abort.

FYI, all DX installers newer than Dec 2006 do not add anything to 9x [98/98SE/ME] OSes.
All DX installers past Dec 2006 removed support for all 9x [98/98SE/ME] OSes.
More info here:
http://www.mdgx.com/dx.htm#DX9

And even if one gets some newer DLLs [the MDX ones newer than D3DX9_32.DLL] extracted and copied manually into %windir%\SYSTEM , those will not work with 9x OSes, because they are designed specifically for NTx OSes [2000/XP/2003/Vista/newer], and I don't believe KernelEx has those functions implemented [pls correct me if I'm wrong] to make them work.
But there's hope, maybe there are ways KernelEx can implement those APIs in the future.

HTH

[CharlesF]

RFMaster, on 27 May 2010 - 05:41 AM, said:

i just copy d3dx9_31.dll and rename to d3dx9_32.dll,d3dx9_33.dll
and d3dx9_34.dll and is work believe you or not

Hi RFMaster,
Welcome to MSFN Forums

your trick is very interesting indeed!

Read here for a similar advice: D3DX9_XX stubs