Tomcat76

LOLI'll need it

@Yzöwl I'm stumped. I really don't know what's going on there. The only thing I can suggest is that you make an HFSLIP run without XPize and the hotfixes that aren't on our lists to find out what's causing this. Ah, OK. I'll change this in the next test I've been thinking about it. I'm hesitating because I believe the name is quite long already. The intention behind the use of the date and time was to allow people to keep previously created ISO files in the same folder (and to allow HFSLIP to successfully create a new ISO when people forgot to take out the old one) so those have to stay. I'm open to suggestions, but I prefer not to touch the volume label.

Well... Apparantly it is because that's Yzöwl's problem. I'm trying to figure out if he needs those entries in TXTSETUP.SIF or not. But IF they are needed, they should be in all three sections involved. Are you sure about that?Check out my posted sif, my WXP source is using the data you've stated for W2k3! HFSLIP is using "1,,,,,,3_,4,1,,,1,4" for every OS. Some people say it's like this, others say it's like that... Let's first see if this works out. There's no need for extra coding if it isn't necessary to use different settings per OS.

Thanks, the_guy. I'm in the process of implementing WMP11 slipstreaming into HFSLIP and can always use other methods to see if I covered everything. I have yet to come across an addon that slipstreams IE7, though. What I've seen so far is only SVCPACK/RunOnceEx stuff which is not what HFSLIP is all about...

Yzöwl... Are jgogo.sys and SiWinAcc.sys required files? Check if they exist on your system. If they do, there's an easy way to test if you should add extra stuff into STORAGE.INI or not: put both files in the FIX folder instead and run HFSLIP again. If this works and the drivers are installed correctly, you can keep doing this. Otherwise, you'll have to edit STORAGE.INI to add the missing info. The iaStor/iaAHCI problem is a bit more complex. There are two installation INFs but they refer to the same SYS file. To my knowledge, this can't be done from TXTSETUP.SIF because of the way [sCSI], [sCSI.Load] and [HardwareIdsDatabase] communicate with each other, unless you duplicate iaStor.sys to iaAHCI.sys and edit iaAHCI.inf so it looks for the "new" SYS file instead.

1) I don't know. You can use the following but I'm not sure that would get rid of the System Restore dialog too: wmfdist11.exe /passive /norestart /nobackup wmp11.exe /passive /norestart /nobackup 2) I'd do it the other way 'round (unless the WM 11 codecs can't be applied to a system that has WMP10) 3) Those are for WMP10 Just an FYI... One of the INFs does a command that involves the sync playlists. So I hope nothing goes wrong if you don't include them.

@Yzöwl... That looks all right to me. The only person that could tell us if XPize can be responsible for this is Kiki because he's using it as well. I'd like to see your HFSLIP.LOG and SYSOC.INF files next, please...

It is *supposed* to be in HFSLIPWU.INF. I can't check it right now but if it isn't in there... Let me know.

Wow... So much bloatware... The playlists aren't needed and I believe those extra files you mentioned aren't either. I will attempt to include everything (except for the graphics) with HFSLIP. I already did a thorough examination of this proggie and the only question that remains is what to do with the KB925749.cab file...

@Yzöwl... It's a bit difficult for me to diagnose the problem without being able to duplicate it. Can you please post the content of the "new" AU.INF here?

Yes. Please read the changelog for HFSLIP 1.0. You naughty boy...

There is no "SiWinAcc" line under the [sCSI] section. Could that be the reason?

It's difficult for me to diagnose the problem without an HFSLIP.LOG file from the run with v1.0.1. The files you mentioned are DirectX files and they are slipstreamed with version 60810 as well.

No. It'll come soon...

Using IExpress and two files less, the installer is 107KB bigger.

Hmmm... I really have no idea what you guys are talking about... @NtegrA: No problem. Glad it's working again for you

While there's a new test release?

slap

Well... yeah. The early test releases for HFSLIP 1.0 (including the one that "works" according to you) used to instruct Windows to copy the files that should end up in Program Files to the hard disk first, during text-mode copy. They are placed into a Windows Setup temporary folder, the one that's reflected in the screenshot of the error message you got. Another INF copied them into the final destination at about T-25. During my tests from CD and in a VM, I found out that it wasn't necessary to have them copied over into the temporary location at the beginning of Windows setup as the extra INF is configured to pick them up from the CD directly. I had no idea this would break a network install. My guess is that the "msoobci.dll" error is coming from wmfdist95.exe as it is handled in the same way as WMP 10.I'll come up with a new test release An addon for DirectX? HFSLIP can slipstream these DX components on Server 2K3:- DX 9.0c core (BDAXP.cab and dxnt.cab) - the *d3dx9*x86* cab files (optional binaries used by some games) - the *input* and *xact* cab files (current usage unknown to me) The DX9.0c core files can be obtained from the standard DX9.0c release as well as all the updates as they were never updated thus far. The others are to be taken from the October release (if you want to have the latest versions). These cabs should be placed in HFCABS. If you need more than this, you'll have to find an addon but I don't know of any that's modded to do a proper installation on 2K3. Messenger... Same thing: I don't know of any addon. But if Messenger 8.0 can be installed on 2K3 at all, you can try this: 1) Download the Live Messenger program 2) Extract it and place MsnMsgs.msi into HFSVCPACK_SW 3) I'm not 100% sure but you may need wllogin.msi as well; Messenger appeared to be working fine without it on an XP test install, though Hope this helps...

@Super-Magician... If it's a regular MSI file, you can get away with it by dumping it in HFSVCPACK_SW. Any MSI file in that folder will be installed silently at T-13 using the /qn /norestart switches. @NtegrA... Something strange is going on there. Do you have the CD tag (WIN51 in your case) in the root of the CD from which you are installing?

That doesn't surprise me. Errors like that come and go. Why are you putting that hotfix in HF in the first place? It's the IE cumulative update from over 2 years ago... You should be using v3 of KB918899...

@TAiN: Basically, I made the installer for nothing... @NtegrA: Please remove at least these: gdidettool.exe (blocked) scripten.exe (you have the newest version too) Windows-KB890830-V1.14.exe (you have the newest version too) Windows-KB890830-V1.19.exe (you have the newest version too) If that doesn't help, remove ALL hotfixes that aren't on MY list. @Kiki: Don't delete the CATs and remove these: SFC_OS.DL_ (from FIX) gdidettool.exe (blocked) every hotfix that isn't on my list (including the Sri Lanka timezone update) What you should know is that HFSLIP used to put most hotfix binaries on the CD, but only those which are also in "officially supported" hotfixes were copied to the hard disk during Windows setup. The current versions DO copy most files to hard disk during Windows installation. So if a hotfix adds blahblah.exe, 60810 would put it on the CD but it was never copied during Windows installation because none of the "officially supported" hotfixes contain such a file. HFSLIP 1.0, however, makes Windows setup copy it to the hard disk, into SYSTEM32.

NP

VPCAdditions.zip (link changed)

Got a working one. Need to see where I can upload it...