Camarade_Tux Posted March 5, 2006 Share Posted March 5, 2006 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. Link to comment Share on other sites More sharing options...
Tomcat76 Posted March 5, 2006 Share Posted March 5, 2006 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 Link to comment Share on other sites More sharing options...
Camarade_Tux Posted March 5, 2006 Author Share Posted March 5, 2006 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. Link to comment Share on other sites More sharing options...
Tomcat76 Posted March 5, 2006 Share Posted March 5, 2006 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. Link to comment Share on other sites More sharing options...
Camarade_Tux Posted March 5, 2006 Author Share Posted March 5, 2006 I'm running WIHU at T-12.I should be able to try it in a few minutes. Link to comment Share on other sites More sharing options...
Camarade_Tux Posted March 5, 2006 Author Share Posted March 5, 2006 Indeed, it doesn't work at T-12. Link to comment Share on other sites More sharing options...
bionicman Posted March 9, 2006 Share Posted March 9, 2006 (edited) 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!DxDiag.txtERROR_REPORT.TXT Edited March 10, 2006 by bionicman Link to comment Share on other sites More sharing options...
Tomcat76 Posted March 10, 2006 Share Posted March 10, 2006 (edited) 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? Edited March 10, 2006 by Tomcat76 Link to comment Share on other sites More sharing options...
bionicman Posted March 10, 2006 Share Posted March 10, 2006 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.DLLADVPACK.DLLW95INF32.DLLBy 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-8db1bc10b16eIt's the same as in your list of Hofixes & Updates.WMEncoder9http://www.microsoft.com/Downloads/details...&displaylang=enI'm thinking perhaps I should experiment & use an earlier versionof DX9 & drop the games bineries. Link to comment Share on other sites More sharing options...
tommyp Posted March 10, 2006 Share Posted March 10, 2006 Umm, sometimes it helps to read instructions. It's clearly obvious that you don't like step 3. http://www.vorck.com/2ksp5.html Link to comment Share on other sites More sharing options...
clintb Posted March 10, 2006 Share Posted March 10, 2006 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. Link to comment Share on other sites More sharing options...
bionicman Posted March 10, 2006 Share Posted March 10, 2006 Remade using Secondary Drive D:\Tested & the error still remains.DxDiag.txtERROR_REPORT.TXT Link to comment Share on other sites More sharing options...
Tomcat76 Posted March 10, 2006 Share Posted March 10, 2006 (edited) 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. Edited March 10, 2006 by Tomcat76 Link to comment Share on other sites More sharing options...
bionicman Posted March 10, 2006 Share Posted March 10, 2006 (edited) That's fixed it!Cheers for your help & support.Regards. DxDiag.txt Edited March 10, 2006 by bionicman Link to comment Share on other sites More sharing options...
Camarade_Tux Posted March 11, 2006 Author Share Posted March 11, 2006 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 ? Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now