MSFN Forum: Are DirectX and Windows Installer slipstreamable ? - MSFN Forum

Jump to content



  • 3 Pages +
  • 1
  • 2
  • 3
  • You cannot start a new topic
  • You cannot reply to this topic

Are DirectX and Windows Installer slipstreamable ? Rate Topic: -----

#1 User is offline   Camarade_Tux 

  • MSFN Addict
  • PipPipPipPipPipPipPip
  • Group: Members
  • Posts: 1,760
  • Joined: 22-May 05

Posted 05 March 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. :)


#2 User is offline   Tomcat76 

  • MSFN Junkie
  • Group: Developers
  • Posts: 3,171
  • Joined: 08-August 05

Posted 05 March 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

#3 User is offline   Camarade_Tux 

  • MSFN Addict
  • PipPipPipPipPipPipPip
  • Group: Members
  • Posts: 1,760
  • Joined: 22-May 05

Posted 05 March 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.

#4 User is offline   Tomcat76 

  • MSFN Junkie
  • Group: Developers
  • Posts: 3,171
  • Joined: 08-August 05

Posted 05 March 2006 - 08:09 AM

View PostCamarade_Tux, on Mar 5 2006, 02:38 PM, said:

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.

#5 User is offline   Camarade_Tux 

  • MSFN Addict
  • PipPipPipPipPipPipPip
  • Group: Members
  • Posts: 1,760
  • Joined: 22-May 05

Posted 05 March 2006 - 08:33 AM

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

#6 User is offline   Camarade_Tux 

  • MSFN Addict
  • PipPipPipPipPipPipPip
  • Group: Members
  • Posts: 1,760
  • Joined: 22-May 05

Posted 05 March 2006 - 01:36 PM

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

#7 User is offline   bionicman 

  • Junior
  • Pip
  • Group: Members
  • Posts: 51
  • Joined: 20-December 04

Posted 09 March 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!

Attached File(s)


This post has been edited by bionicman: 09 March 2006 - 06:02 PM


#8 User is offline   Tomcat76 

  • MSFN Junkie
  • Group: Developers
  • Posts: 3,171
  • Joined: 08-August 05

Posted 09 March 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?

This post has been edited by Tomcat76: 09 March 2006 - 07:37 PM


#9 User is offline   bionicman 

  • Junior
  • Pip
  • Group: Members
  • Posts: 51
  • Joined: 20-December 04

Posted 09 March 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.

#10 User is offline   tommyp 

  • MSFN Addict
  • Group: Developers
  • Posts: 1,664
  • Joined: 09-January 04
  • OS:none specified
  • Country: Country Flag

Posted 09 March 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

#11 User is offline   clintb 

  • Newbie
  • Group: Members
  • Posts: 44
  • Joined: 22-September 05

Posted 09 March 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.

#12 User is offline   bionicman 

  • Junior
  • Pip
  • Group: Members
  • Posts: 51
  • Joined: 20-December 04

Posted 09 March 2006 - 11:00 PM

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

Attached File(s)



#13 User is offline   Tomcat76 

  • MSFN Junkie
  • Group: Developers
  • Posts: 3,171
  • Joined: 08-August 05

Posted 10 March 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.

This post has been edited by Tomcat76: 10 March 2006 - 06:05 AM


#14 User is offline   bionicman 

  • Junior
  • Pip
  • Group: Members
  • Posts: 51
  • Joined: 20-December 04

Posted 10 March 2006 - 12:01 PM

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

Attached File(s)


This post has been edited by bionicman: 10 March 2006 - 12:02 PM


#15 User is offline   Camarade_Tux 

  • MSFN Addict
  • PipPipPipPipPipPipPip
  • Group: Members
  • Posts: 1,760
  • Joined: 22-May 05

Posted 11 March 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 ?

:)

#16 User is offline   tommyp 

  • MSFN Addict
  • Group: Developers
  • Posts: 1,664
  • Joined: 09-January 04
  • OS:none specified
  • Country: Country Flag

Posted 11 March 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.

#17 User is offline   Camarade_Tux 

  • MSFN Addict
  • PipPipPipPipPipPipPip
  • Group: Members
  • Posts: 1,760
  • Joined: 22-May 05

Posted 15 March 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.images...6/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 ?

This post has been edited by Camarade_Tux: 15 March 2006 - 07:41 AM


#18 User is offline   Tomcat76 

  • MSFN Junkie
  • Group: Developers
  • Posts: 3,171
  • Joined: 08-August 05

Posted 15 March 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.

This post has been edited by Tomcat76: 15 March 2006 - 08:29 AM


#19 User is offline   Camarade_Tux 

  • MSFN Addict
  • PipPipPipPipPipPipPip
  • Group: Members
  • Posts: 1,760
  • Joined: 22-May 05

Posted 15 March 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: :P )

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

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

#20 User is offline   Camarade_Tux 

  • MSFN Addict
  • PipPipPipPipPipPipPip
  • Group: Members
  • Posts: 1,760
  • Joined: 22-May 05

Posted 15 March 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. :rolleyes: )


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

Attached File(s)


This post has been edited by Camarade_Tux: 15 March 2006 - 03:01 PM


Share this topic:


  • 3 Pages +
  • 1
  • 2
  • 3
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users



All trademarks mentioned on this page are the property of their respective owners
Copyright © 2001 - 2011 msfn.org
Privacy Policy