HFSLIP64 v1.1.5 released

[sabregreen]

I forgot to slipstream service pack 2 is one problem. I moved machines, I was working at home this weekend. Even after slipstreaming service pack 2, its still giving me lots of errors in setuperr.log with .exe files.

[johndoe74]

a small suggestion. don't slipstream sp2 every time, just slipstream it once and use that as your source, will save a lot of time and you obviously won't be forgetting to slipstream it again

[sabregreen]

Oh i know. I forgot to copy the source I was using at work so that I could use it at home. For whatever reason, the source im using at home is acting weird. I just checksums and everything. The exact same.

[sabregreen]

Attached is my setuperr.log. There has to be something else wrong.

setuperr.log.zip

[sabregreen]

Removed winnt.sif, plugins, and changed in hfanswer.ini installrc=1 to installrc=. I'm rerunning now.

[sabregreen]

Must be something in my winnt.sif file that it doesnt like. I removed that and it installs properly.

[Tomcat76]

I don't know much about WINNT.SIF myself, but you can always attach it here if you like (after blanking out sensitive data). Maybe there is something that catches my eye.

BTW... The INSTALLRC variable has no effect as HFSLIP64 doesn't have code that handles installation of the Recovery Console. See the default HFANSWER.INI that's linked from the first post in this thread for a list of variables that you can predefine.

[sabregreen]

Here it is. Let me know. Definitely my winnt.sif file though.

WINNT.zip

[Tomcat76]

The only thing that looks suspicious to me is the AutomaticUpdates variable. What happens if you comment it out?

[sabregreen]

Same thing. I'm commenting out oempreinstall and oemskipwelcome and rerunning.

[sabregreen]

Running out of ideas here. I don't know what it is.

[Tomcat76]

There's always the possibility that one or more hotfixes are incompatible with WINNT.SIF, just like you can no longer use the branding options if you slipstream IE7 into XP 32-bit.

Well... That's about all I can say on WINNT.SIF. I'm sorry.

[sabregreen]

I'm still testing one by one.

[sabregreen]

Removed automaticupdates and the driverpolicy parameters. No errors in setuperr.log

[Tomcat76]

Well... It isn't the AutomaticUpdates setting (at least, that's what you said earlier).

But the DriverSigningPolicy variable could be a problem now that I think about it.

HFSLIP has always set Driver Signing to "Ignore" at T-13 via a registry edit (so actually you don't need to do that) but I once tried to have it injected into the registry through an INF file that is installed from TXTSETUP.SIF (at the end of txtmode copy). When I did that, I got all sorts of error messages during Windows setup. So I think Windows setup can't handle "tampering" (as Microsoft calls it) with the Driver Signing Policy setting at such an early stage if hotfixes are slipstreamed. It seems to be OK at T-13.