MSFN Forums > Are DirectX and Windows Installer slipstreamable ?

Full Version: Are DirectX and Windows Installer slipstreamable ?

MSFN Forums > Member Contributed Projects > HFSLIP

Pages: 1, 2

Camarade_Tux

Mar 5 2006, 04:19 AM

I'm pretty new to HFSLIP but I know it's a powerful tool.

I'm currently playing with WIHU and nLite.
I want to install the .net framework 2 (RyanVm's switchless) but it also needs Windows Installer 3.
Is it possible to slipstream it just as any hotfix or will it be post-installed ?

I have the same question for DirectX.

Thanks guys.

PS: I'll make a new iso on next week : nLite RC7 out on Monday.

Tomcat76

Mar 5 2006, 04:53 AM

DirectX 9.0c and WI 3.1 can be slipstreamed, yes.

RyanVM's switchless installer won't work. Some people (including me) have had success with Zxian's switchless installers: International / English

Camarade_Tux

Mar 5 2006, 07:38 AM

Ok, thanks a lot.

btw I'm installing .net with WIHU so it shouldn't be a problem.

I'll report as soon as I test my new iso.

Tomcat76

Mar 5 2006, 08:09 AM

QUOTE (Camarade_Tux @ Mar 5 2006, 02:38 PM)

btw I'm installing .net with WIHU so it shouldn't be a problem.

If it works in WIHU, it means that program is installing .NET 2.0 post-setup. HFSLIP doesn't do that; any additional programs are installed through SVCPACK, before the final reboot.

Camarade_Tux

Mar 5 2006, 08:33 AM

I'm running WIHU at T-12.
I should be able to try it in a few minutes.

Camarade_Tux

Mar 5 2006, 01:36 PM

Indeed, it doesn't work at T-12.

bionicman

Mar 9 2006, 05:51 PM

I didn't want to start a new thread for what is probably an obvious mistake by me slipstreaming DirectX 9c (Feb) on Windows 2000.
Everything has gone great. Everything I put in is there but when I checked dxdiag to ensure DirectX had installed I found the following error:
DirectX Files Tab: The file msdmo.dll is an old version, which could cause problems. You should reinstall DirectX to get the latest version.

Please find the my HFSLIP error report & DxDiag report at bottom of this post.
Thanx Guys & keep up the good work!

Tomcat76

Mar 9 2006, 07:36 PM

I bet msdmo.dll is part of the WMEncoder.exe package you got in your HFSVPK_SW folder. If that's the case, it replaces the "good" version of msdmo.dll at the end of Win2K setup. This is beyond HFSLIP's control...

Where did you get the installer from?

bionicman

Mar 9 2006, 08:42 PM

It's not the encoder because I added that as an after thought & I wanted to replicate the error report that I had stupidly deleted before creating my first ISO which also had the DX9 error.
DLL's in Encoder are:
W95INF16.DLL
ADVPACK.DLL
W95INF32.DLL

By Installer do you want to know where I got the DX9 from or the Encoder?
Anyway will give both links:
DX9c (Feb)
http://www.microsoft.com/downloads/details...c9-8db1bc10b16e
It's the same as in your list of Hofixes & Updates.

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

I'm thinking perhaps I should experiment & use an earlier versionof DX9 & drop the games bineries.

tommyp

Mar 9 2006, 08:53 PM

Umm, sometimes it helps to read instructions. It's clearly obvious that you don't like step 3. http://www.vorck.com/2ksp5.html

clintb

Mar 9 2006, 09:06 PM

I've found an all-in-one installer that does both .Net 1.1 sp1 and .Net 2.0 in one go. The .inf inside says it was created by "HyPo" and the filename is "nLite_dotnet.cab". I *think* it came from RyanVM's forums and was posted on RapidShare. Anyway, I've used it in nLite the normal way (a Hotfix) and it's flawless.

bionicman

Mar 9 2006, 11:00 PM

Remade using Secondary Drive D:\
Tested & the error still remains.

Tomcat76

Mar 10 2006, 06:03 AM

Well, what do you know... Our very own wmfdist.exe is spoiling the party...

You know what the problem is? The msdmo.dll that's contained in the wmfdist.exe package is older than the one contained in dxnt.cab, yet it has a newer file date.

In any case, download the March 9 version from the other thread (HFSLIP_60309c.CMD). I inserted an extra line the other day which happens to work around this problem.

bionicman

Mar 10 2006, 12:01 PM

That's fixed it!
Cheers for your help & support.
Regards.

Camarade_Tux

Mar 11 2006, 08:13 AM

Thanks all.

I have an nLite source.
Is it a good idea to slipstream DirectX over it or should I build a new iso and integrate Dx before using nLite ?

tommyp

Mar 11 2006, 08:21 AM

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

Mar 15 2006, 06:57 AM

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 ?

Tomcat76

Mar 15 2006, 08:27 AM

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.

Camarade_Tux

Mar 15 2006, 08:35 AM

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

Mar 15 2006, 03:00 PM

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 ?

QUOTE

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'

Tomcat76

Mar 15 2006, 03:39 PM

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.

tommyp

Mar 15 2006, 06:18 PM

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

Camarade_Tux

Mar 16 2006, 01:09 AM

QUOTE (Tomcat76 @ Mar 15 2006, 10:39 PM)

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.

CODE

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

Mar 16 2006, 03:40 AM

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

Mar 16 2006, 03:02 PM

Sure.

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

Tomcat76

Mar 16 2006, 03:26 PM

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.

Camarade_Tux

Mar 16 2006, 03:42 PM

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

Mar 16 2006, 03:48 PM

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.

Camarade_Tux

Mar 16 2006, 03:53 PM

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

Mar 16 2006, 04:03 PM

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.

tommyp

Mar 16 2006, 07:36 PM

QUOTE (Super-Magician @ Mar 16 2006, 05:03 PM)

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.

Tomcat76 is adding far more to this effort. He really deserves a round of applause.

Super-Magician

Mar 17 2006, 06:18 AM

QUOTE (tommyp @ Mar 16 2006, 08:36 PM)

Tomcat76 is adding far more to this effort. He really deserves a round of applause.

Hooray for the Tomcat!!

Camarade_Tux

Mar 18 2006, 01:08 PM

Another congrats from France.

My install is now looking OK.
I have one problem which appears to be normal ( http://www.msfn.org/board/index.php?showtopic=16070 ) but I wanted to say exactly what happened to my uAXP.
Setuperr.log reports

CODE

Error:
Setup could not register the OLE Control E:\WINDOWS\System32\dpnaddr.dll because of the following error:
GetProcAddress returned error 127 (the specified procedure could not be found).

***

Error:
Setup could not register the OLE Control E:\WINDOWS\System32\dpnlobby.dll because of the following error:
GetProcAddress returned error 127 (the specified procedure could not be found).

and dxdiag does not complain about anything.

:woooooooooooooooooooooooooooooooooooooooooooooot:

Tomcat, you're added to my donation list. :x

Tomcat76

Mar 18 2006, 01:17 PM

Yeah, those errors are normal. Don't worry about them

Donation list? What donation list?

tain

Mar 18 2006, 01:42 PM

I'd be willing to donate as well. There needs to be an HFSLIP-DEV paypal acct that sends cash to tommyp/FDV/Tomcat among others.

Much love!

erm...straight love

tain

Mar 21 2006, 06:27 AM

Happy Birthday to Tux!

QUOTE

Birthday 21 March 1988

Super-Magician

Mar 21 2006, 07:46 AM

QUOTE

Birthday 21 March 1988

Happy 18th at that!

Camarade_Tux

Mar 22 2006, 02:39 PM

QUOTE (TAiN @ Mar 21 2006, 01:27 PM)

Happy Birthday to Tux!

QUOTE

Birthday 21 March 1988

QUOTE (Super-Magician @ Mar 21 2006, 02:46 PM)

QUOTE

Birthday 21 March 1988

Happy 18th at that!

Thank you guys.

I'd never thought somebody here would notice it.
Thanks a lot.

Gouki

Mar 22 2006, 02:45 PM

I made a new Thread just for you!

LOL

(Located at General Discussion)

Camarade_Tux

Mar 22 2006, 03:13 PM

QUOTE (Gouki @ Mar 22 2006, 09:45 PM)

I made a new Thread just for you!

LOL

(Located at General Discussion)

/me have answered.

Camarade_Tux

May 6 2006, 02:07 PM

Today I found my SOURCESS folder after nLite was definitely too big.
117MB !

I would have been happy but a clean XP -SP0- goes down to 110MB.
Of course, I add functionnalities with SP1 and other updates but 7MB is IMO too much.

I compared files present with and without HFSlip in I386 after nlite and I found that some or rather many DirectX files are present in both I386 and driver.cab. I think this should be cleaner.
And it seems it also happens with other files (ntkrnl*.exe)

Files in driver.cab and directly in i386 seem to have the same version but I'm not 100% positive.

PS: I used "dir /S /B >> dir.txt". If needed, I can provide those listings.

Camarade_Tux

May 6 2006, 02:52 PM

I made a quick and maybe dirty AHK app:

CODE

FileSelectFolder, I386,,, Select I386 folder
FileSelectFile, files, M3, %I386%, Select all the files comming from driver.cab
Loop, parse, files, `n
{
    StringTrimRight, A_LoopField2, A_LoopField, 1
    IfExist, %I386%\%A_LoopField2%_
        FileAppend, %A_LoopField%`r`n, c:\hfslipdriver.cabi386.txt
    FileGetSize, fsize, %I386%\%A_LoopField2%_, K
    size+=fsize
}

FileAppend, `r`nSpace lost on the CD : %size%KB`r`n, c:\hfslipdriver.cabi386.txt
MsgBox, %size%KB
return

You need to extract driver.cab somewhere.
Then, at the second dialog, enter the folder you extracted driver.cab to and select all files (ctrl+A).

I have 2.2MB of duplicates in my nlited SOURCESS.

NB: ntkrnlmp.exe has to be in I386.

http://sharpnet.ai-network.net/camarade/duplicates.exe
(don't, at least for the moment, it will go public and legal [I hope] later)

yazee01

May 6 2006, 03:27 PM

Are DirectX and Windows Installer slipstreamable ?

yes, i don´t have any problem. HFSLIP is good slipstreamable tool. (win2k).

Super-Magician

May 6 2006, 03:48 PM

Yes. DirectX CABs go in HFCABS (only the *d3dx9* ones) and Windows Installer goes in HF.

Tomcat76

May 6 2006, 07:05 PM

@Camarade_Tux

Yes, there are a couple of dupes. It's just that so far nobody ever tried to figure out which files can be deleted and which not. There are several files that have to be both in SOURCESS\I386 and in DRIVER.CAB/SPX.CAB. It's very time consuming to check this for all OS versions and all SP levels so it's not really "top priority".

tommyp

May 6 2006, 08:21 PM

FYI, Nlite doesn't remove some things when selected. I'm not sure if this is by design or what. I have asked Nuhi a bunch of times to remove some additional files, but the requests fell of deaf ears (or maybe eyes). This is why I created HFCLEANUP. With HFCLEANUP, I can create a ultra slim and updated 2k with no need for nlite. Total duration is about about 8 minutes.

. It was my answer to fixing a fully slipstreamed 2k with the least amount of keystrokes and programs to install on my system. HFCLEANUP can be tailored to XP too, a majority of the reducers can be used on 2k/xp/2k3 at this point. All I can say is that if you won't need something in your source, don't slipstream it in the first place. For example, why slipstream wmp10 and then remove it with nlite? Seems foolish IMO.

Also, FWIW, an NLITEd HFSLIP works best when selecting the merged cabs (A, B or C). This will eliminate a bunch of dupes in the cabs and produces the smallest footprint i386 folder.

Camarade_Tux - OT - What is your favorite flavor of linux?

Tomcat76

May 6 2006, 08:42 PM

QUOTE (tommyp @ May 7 2006, 03:21 AM)

FWIW, an NLITEd HFSLIP works best when selecting the merged cabs (A, B or C). This will eliminate a bunch of dupes in the cabs and produces the smallest footprint i386 folder.

Just to be sure that we're on the same page... Camarade_Tux correctly noticed that all new driver cab binaries are copied "loose" into SOURCESS\I386 as well even though some of them (possibly the majority) don't have to be. HFSLIP doesn't delete them from the working folder after they are added into DRIVER.CAB or SPX.CAB.

Camarade_Tux

May 7 2006, 02:06 AM

Quickly, with only SP1 slipstreamed (will check with no SP slipstreamed later):

Files in driver.cab AND in i386
CODE
acpi.sys
acpiec.sys
adpu160m.sys
aha154x.sys
aic78u2.sys
aic78xx.sys
aliide.sys
amsint.sys
asc3350p.sys
asc3550.sys
asc.sys
atapi.sys
binlsvc.dll
cbidf2k.sys
cd20xrnt.sys
cdrom.sys
cmdide.sys
cpqarray.sys
dac2w2k.sys
dac960nt.sys
disk.sys
dpti2o.sys
fdc.sys
flpydisk.sys
ftdisk.sys
hal.dll
halaacpi.dll
halacpi.dll
halapic.dll
halmacpi.dll
halmps.dll
halsp.dll
hidclass.sys
hidparse.sys
hidusb.sys
Files present in i386 AND in sp1.cab
CODE
1394bus.sys
acpi.sys
atapi.sys
ati2dvaa.dll
ati2dvag.dll
ati2mtaa.sys
ati2mtag.sys
ati3d1ag.dll
ati3d2ag.dll
atinbtxx.sys
atinmdxx.sys
atinpdxx.sys
atinraxx.sys
atinrvxx.sys
atinsnxx.sys
atinttxx.sys
atintuxx.sys
atinxbxx.sys
atinxsxx.sys
cdrom.sys
disk.sys
dxg.sys
flpydisk.sys
hal.dll
halaacpi.dll
halacpi.dll
halapic.dll
halmacpi.dll
halmps.dll
hccoin.dll
hidclass.sys
hidir.sys
i8042prt.sys
imapi.sys
intelide.sys
irbus.sys
kbdclass.sys
mrxsmb.sys
mutohpen.sys
ntkrnlmp.exe
ntoskrnl.exe
ohci1394.sys
pci.sys
pciidex.sys
pcmcia.sys
sbp2port.sys
scsiport.sys
serial.sys
sfloppy.sys
tffsport.sys
usbccgp.sys
usbehci.sys
usbhub.sys
usbohci.sys
usbport.sys
usbstor.sys
usbuhci.sys
viaide.sys
wacompen.sys

It seems SP1 itself adds lots of duplicates.

Tomcat76

May 7 2006, 03:37 AM

See how difficult it is?

Camarade_Tux

May 7 2006, 11:59 AM

I just wanted to make my list complete :
Duplicates on a DELL XP SP0 CD:

CODE

1394bus.sys
1394vdbg.sys
abp480n5.sys
acpi.sys
acpiec.sys
adpu160m.sys
aha154x.sys
aic78u2.sys
aic78xx.sys
aliide.sys
amsint.sys
asc3350p.sys
asc3550.sys
asc.sys
atapi.sys
binlsvc.dll
cbidf2k.sys
cd20xrnt.sys
cdrom.sys
cmdide.sys
cpqarray.sys
dac2w2k.sys
dac960nt.sys
disk.sys
dpti2o.sys
fdc.sys
flpydisk.sys
ftdisk.sys
hal.dll
halaacpi.dll
halacpi.dll
halapic.dll
halmacpi.dll
halmps.dll
halsp.dll
hidclass.sys
hidparse.sys
hidusb.sys

Space lost on the CD : 932KB

I'll see what can be removed, probably next week.

And my favorite flavor of Linux is ... the one that lets me use my Radeon mobility X700 on my 16/10 screen at its native resolution.
I used to run SuSe. I sucked my install and could not install again because of *dead* HD.

This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.