Jump to content

Can't find the file .....


hulkviper
 Share

Recommended Posts

I slipstreamed SP2 on a SP1a install and got the message Can't find the file.

see on the pic,

translated it to english from swedish do not know if the english message is exactly like that.

Is this serious or normal?

Edited by hulkviper
Link to comment
Share on other sites


I rather not try, I think I am missing some required files in system32 folder or regitrys entries .

What are the required files for HFSLIP?

The windows I am on now is a strip down version I made for myself with nLite, about 130MB was the final CD size.

At first I was missing findstr.exe, and that I copied from a XP SP2 CD.

Get also a error window with no message when trying with nLite or manually.

In EventLog it's like this:

Source: vmauthd

Message description: Failed to read registry perf object Memory\Cache Bytes

Will try with the test releaese if this doesn't work.

Also maybe noteable, I don't have Virtual Memory/Pagefile enabled

Isn't it because of Virtual Memory, tried it.

Edited by hulkviper
Link to comment
Share on other sites

The only change in the test release I believe would be related to your problem is some code cleanup to try to get rid of such extraneous error messages.

I would recommend that you do not try running HFSLIP on an nLited source because nLite often removes components required for an HFSLIPed install to work if you're not careful enough. I believe there is some page on Fred Vorck's site regarding nLite and HFSLIP, but I can't remember exactly.

Link to comment
Share on other sites

Well, try the test release and see if you still get that error message.

By the way, I see you are running HFSLIP on a computer installed with an nLited source. Now, is the source you are using with HFSLIP (i.e. in your SOURCE folder) also previously nLited? If not, you can disregard the last sentence in the post I made above.

Link to comment
Share on other sites

I always use HFSLIP first to integrate DirectX latest release with some other updates and then nLite.

Never nLite first.

Edit:

It seems like the new version is workin as it should :)

Edited by hulkviper
Link to comment
Share on other sites

1

HFSLIP always says to restart after install.

I do it anyway but is it really needed for slipstreaming also?

2

Whats the difference with the manual slipstreaming and HFSLIP slipstreaming?

3.

How should I integrate DirectX, is it safe to do it the same time as slipstreaming sp2 or do it later?

4

Hotfixes:

I use nlite to integrate most of the hotfix, whats actually better, HFSLIP or nLite?

I need direct integration, does HFSLIP do that?

Why is the original name of the update/hotfix really needed?

nLite supports changed names, why not HFSLIP to?

Thinking about changing coz nLite does not support all hotfixes, does HFSLIP?

Edited by hulkviper
Link to comment
Share on other sites

(1) It's good to restart anyway, but it's required if you decide to include Internet Explorer 7.

(2) HFSLIP is automated and deals with the many problems that often arise in Microsoft's hotfixes. It's much cleaner and doesn't leave extra junk. Plus, you only have to run one file! ;) HFSLIP has other advantages too, including advanced features like HFEXPERT and HFAAO (application addons), and the ability to slipstream components other than pure hotfixes.

(3) XPSP2 already includes DirectX 9.0c. However, if you wish to slipstream the advanced Direct3D gaming binaries that Microsoft releases bimonthly, HFSLIP supports it through the HFCABS folder. Check out Tomcat's XP SP2 update list for more information (look for DirectX on the page).

(4)

a. Like I said above, HFSLIP has many advantages, more about which you can read at HFSLIP's website. While some people still prefer nLite because it has a GUI and can remove components, HFSLIP can also remove stuff from your source through HFCLEANUP.

b. Yes, HFSLIP does direct integration (otherwise known as pure slipstreaming) for most hotfixes. For those that can't be slipstreamed, HFSLIP integrates the hotfix through SVCPACK.

c. HFSLIP uses the original name (containing the string "Windows") to determine whether a hotfix is Type 1 or Type 2. Hotfixes that contain the word "Windows" are usually Type 1; there are some that break this rule and such hotfixes are given special treatment. The same applies to those that don't contain the word "Windows"; these are usually Type 2. The main difference between the two types is the command used to extract them.

d. As above.

e. As mentioned above, HFSLIP supports most hotfixes. In the rare case that it doesn't, the script is modified to include support, whether it's through the SVCPACK folder or through "special treatment."

I hope this helps :). If you would like to learn more, be sure to check out the website. And since the script is open-source, you can take a look at it, and I'm sure you'll discover all the advantages of using HFSLIP and everything it does.

Edited by Super-Magician
Link to comment
Share on other sites

thanx

But I have to stay with nLite, the hotfixes do not have the original names. I rather not redownload or rename about 300 hotfixes :P

Gonna try with HFSLIP anyway, if it goes it goes :)

About DirectX, can I do it the same time as slipstreaming SP2 and all the hotfixes.

Integrated all 3 at the same time?

Edited by hulkviper
Link to comment
Share on other sites

hehe, good to know :)

thanx!

But if I slipstream sp2.

Can I keep that WindowsXP SP2 source for the future updates?

Maybe it's best if I manually slipstream SP2 if I want to keep the source?

See the new text file if I have set it right :)

I'm not user about the IE7 setup, where it goes and if it is better if I integrated it with nLite.

I read on the HFSLIP page it doesn't do direct integration on IE7.

Edited by hulkviper
Link to comment
Share on other sites

The service pack is slipstreamed into the source in the SOURCE folder directly so you can keep using it. Next time, HFSLIP won't slipstream the service pack again.

What are these files doing in your HFCABS folder?

directx_dec2006_redist.exe

WindowsXP-Windows2000-Script56-KB917344-x86-sve.exe

Link to comment
Share on other sites

=================TommyP's 2K3/XP/W2K/IE HOTFIX SLIPSTREAMER===================

************ Refer to the instructions for more details *************

File and Folder Format:

FDVFILES - FDV'S Fileset (W2K only)

FIX - WINNT.SIF, Boot Files, See instructions

HF - Non-renamed hotfix and critical updates files

HF - The Service Pack installer.

HFCABS - CAB Files: IE6 (2K only), DX9, LegitCheckControl, Flash Player

HFSVCPACK - Switchless installers (to be installed at T-13)

HFSVCPACK - REG files, INF files and CMD files (to be installed at T-13)

HFSVCPACK_SW - Installers that need a /Q:A /R:N switch (Installed at T-13)

HFSVCPACK_SW - MSI files (to be installed at T-13 with /qn /norestart switch)

HFAAO - Application Addons (SVCPACK.INF and SYSOC.INF types)

HFTOOLS - HFSLIP Tools

HFTOOLS -CMDOW.EXE (to hide DOS box that pops up at T-13)

HFTOOLS -EXTRACT.EXE (needed for application addons)

HFTOOLS -HFANSWER.INI (optional HFSLIP answer file)

HFTOOLS -modifype.exe

SOURCE - Dump your installation CD source here

==============================================================================

as you can see HFCABS - CAB Files: IE6 (2K only), DX9, LegitCheckControl, Flash Player

Or are the hfslip instructions wrong? :)

Probably me :D

Only cab extensions in HFCABS?

Edited by hulkviper
Link to comment
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
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.


×
×
  • Create New...