Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 

Tomcat76

HFSLIP64 v1.1.5 released

Recommended Posts

sabregreen    0

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.

Share this post


Link to post
Share on other sites
johndoe74    0

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 ;)

Share this post


Link to post
Share on other sites
sabregreen    0

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.

Share this post


Link to post
Share on other sites
Tomcat76    1

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.

Share this post


Link to post
Share on other sites
Tomcat76    1

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.

Share this post


Link to post
Share on other sites
Tomcat76    1

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.

Share this post


Link to post
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Recently Browsing   0 members

    No registered users viewing this page.

×