Are DirectX and Windows Installer slipstreamable ?

**tommyp** · March 11, 2006

Camarade_Tux - It is best to run hfslip of your source first, and then nlite the sourcess folder. There are some files to keep when doing this. The files to keep list is on FDV's site.

**Camarade_Tux** · March 15, 2006

I've done that (hfslip then nLite).

It seems to integrate well but then Dxdiag says DirectX 8.1.

edit: bad example, I missed this on fdv's page : ';wm codec stuff'

Have a look at this screenshot:

(on the left, slipstreamed Dx in VMWare

on the right, not slipstreamed but installed

botton, WMP10Lite package that updates some files.)

screenshot : http://img96.imageshack.us/img96/9276/25nh.pn

dxdiag in VM and not in VM:

http://img116.imageshack.us/img116/9971/25hv.png

It seems the files are simply not updated.

But I've seen during textmode copy some files that come from dx9.

Is it impossible to slipstream Dx9 on french WinXP SP1 ?

Edited March 15, 2006 by Camarade_Tux

**Tomcat76** · March 15, 2006

HFSLIP supports slipstreaming DX9 into WinXP SP1. Do you have the same problem when not nLiting the SOURCESS folder?

Be sure to include the cd tag file in the SOURCE folder.

Edited March 15, 2006 by Tomcat76

**Camarade_Tux** · March 15, 2006

I'll check without nLite but I don't see how nlite could revert some files to an older version.

(oh, no, a full XP install, :evil: )

I think I'll try something like 'hfslip.bat >> d:\debug_hfslip_dx.txt'.

(...trying Slax, seems to be a nice Linux LiveCD )

**Camarade_Tux** · March 15, 2006

I just made a new try.

I didn't try in VM : files are simply not updated.

For example I expanded SOURCESS\I386\dxdiag.ex_

dxdiag is version 5.01.2600.0000 when it should be 5.03.0001.0904.

I'm using latest DirectX redist from February and not simple 9.0c.

Could it be the cause ?

The DirectX redist installation includes all the latest and previous released DirectX runtime. This includes the bi-monthly D3DX, XInput, and Managed DirectX components.

http://www.microsoft.com/downloads/details...&displaylang=en

(note that you don't need WGA on this page. )

/attached 'hfslip.bat >> debug.txt'

hfslip_dx_debug.7z

Edited March 15, 2006 by Camarade_Tux

**Tomcat76** · March 15, 2006

Just an FYI...

These files are not parsed by HFSLIP when dealing with Windows XP:

BDA.cab

BDANT.cab

These files are not parsed by HFSLIP at all:

Apr2005_d3dx9_25_x64.cab

Aug2005_d3dx9_27_x64.cab

Dec2005_d3dx9_28_x64.cab

Dec2005_MDX1_x86.cab

Dec2005_MDX1_x86_Archive.cab

DirectX.cab

dxdllreg_x86.cab

dxupdate.cab

Feb2005_d3dx9_24_x64.cab

Feb2006_d3dx9_29_x64.cab

Feb2006_MDX1_x86.cab

Feb2006_MDX1_x86_Archive.cab

Feb2006_xact_x64.cab

Feb2006_xact_x86.cab

Jun2005_d3dx9_26_x64.cab

Oct2005_xinput_x64.cab

Oct2005_xinput_x86.cab

I'm still not convinced you have the CD tag file in your SOURCE folder.

Edited March 15, 2006 by Tomcat76

**tommyp** · March 16, 2006

Broken record mode on... hehe. Please post your error_report file so we can take a look.

**Camarade_Tux** · March 16, 2006

I'm still not convinced you have the CD tag file in your SOURCE folder.

What do you mean by this ?

Could you explain a bit more ?

As or the files, I was using a lighter set of files before but I thought it could be the cause so I redownloaded the whole package an expanded it.

COMPLETE THIS FILE AND ATTACH IT TO THE MESSAGEBOARD IF YOU RUN INTO PROBLEMS.  

	http://www.msfn.org/board/index.php?showforum=129 

=======================YOU MUST COMPLETE THIS SECTION========================== 

- Make a hfnetchk log - this is the COMMANDLINE HFNETCHK -V -F C:\WU.TXT  
- Other errors, not reported by HFNETCHK 
- Zip the information above and this file and post the info on the board listed on top.  

=========================DO NOT ALTER THE SECTION BELOW======================== 

HFSLIP Version - 
HFSLIP_60225.CMD

Your path - D:\Adrien\Sources\hfslip\ 

OS you are slipstreaming - XP 

Language you are working with - Français 

============================================================================== 
The files in your FIX folder - 

Names of the files in your HF folder: 

Names of the files in your HFCABS folder: 
Apr2005_d3dx9_25_x64.cab
Apr2005_d3dx9_25_x86.cab
Aug2005_d3dx9_27_x64.cab
Aug2005_d3dx9_27_x86.cab
BDA.cab
BDANT.cab
BDAXP.cab
Dec2005_d3dx9_28_x64.cab
Dec2005_d3dx9_28_x86.cab
Dec2005_MDX1_x86.cab
Dec2005_MDX1_x86_Archive.cab
DirectX.cab
dxdllreg_x86.cab
dxnt.cab
dxupdate.cab
Feb2005_d3dx9_24_x64.cab
Feb2005_d3dx9_24_x86.cab
Feb2006_d3dx9_29_x64.cab
Feb2006_d3dx9_29_x86.cab
Feb2006_MDX1_x86.cab
Feb2006_MDX1_x86_Archive.cab
Feb2006_xact_x64.cab
Feb2006_xact_x86.cab
Jun2005_d3dx9_26_x64.cab
Jun2005_d3dx9_26_x86.cab
Oct2005_xinput_x64.cab
Oct2005_xinput_x86.cab

Names of the files in your HFSVPK folder: 

Names of the files in your HFSVPK_SW folder: 

Names of the files in your HFTOOLS folder: 

==============================================================================

(not using Windows Update )

**tommyp** · March 16, 2006

Can we take a look at your sourcess\i386\hfslipwu.inf file? Just attach it as a file and not like you did above. Thanks!

**Camarade_Tux** · March 16, 2006

Sure.

(I know about attachements, but that one was short enough IMHO)

HFSLIPWU.INF

**Tomcat76** · March 16, 2006

Based on your post in the other thread it's clear that you don't have a proper CD tag file. Check in SOURCE\I386 if there's a file called SP1.CAB. If it's there, download the attached ZIP and extract the content into your SOURCE folder. You seem to be using Professional so I included the tag file for XP Pro SP1.

If you don't have SP1.CAB, your source was never patched or wasn't patched properly.

Edited March 16, 2006 by Tomcat76

**Camarade_Tux** · March 16, 2006

I patched my source (which is Pro indeed) with nLite about 10 months ago.

I never had any problem with it.

However, I don't have SP1.cab until I run nLite to remove things (including drivers).

Then my SP1.cab gets created.

Also, MBSA reports SP1 and does not ask for hotfixes older than SP1.

I added your tag file to my source (it is a blank file, nothing more, right ?) and it already seems to be helpful.

I'm still waiting for hfslip to end but it seemed to me some more things happened.

**Super-Magician** · March 16, 2006

Camarade_Tux:

The tag files are actually 10 bytes long and contain the string "Windows " plus some blank lines (at least for XP and 2003).

You should not be using an nLite source for HFSLIP. According to the directions, you should have a clean source. HFSLIP, I believe, also uses the SP1.cab file to check for a few things.

Edited March 16, 2006 by Super-Magician

**Camarade_Tux** · March 16, 2006

Thanks.

It's not an nLited source.

I only used the service pack option. Nothing more.

hfslip finished its work and that time, dxdiag.exe got updated.

I'll nlite it on tomorrow and test it.

And ddraw.dll also got updated.

:woot:

**Super-Magician** · March 16, 2006

Great!

However, when I said "nLited source," I was referring to the fact that nLite, no matter what you do, will (I think) add some *extra* files to your source.

HFSLIP can slipstream your service pack easily, and without adding extra files, thanks to an addition generously provided/created by Tomcat76. Read the directions to it here. I would recommend using this, not nLite, but that's just my opinion.

Sign In

Are DirectX and Windows Installer slipstreamable ?

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Create an account or sign in to comment

Create an account

Sign in

Recently Browsing 0 members