[tommyp]

If the "missing" file is indeed in the i386 folder and the filename is also part of txtsetup.sif, then I'm at a loss of words. Maybe try booting from the CD to install (i.e. clean installation), or reburning your CD. Other than that, I really can't help.

[mserbin]

Ive tried recompiling the CD a few times and in all cases I was doing a clean install from a zeroed out HDD. Here is my txtsetup.sif file. Is there some sort of a script or batch file that we could make run at the end of textmode setup or at the beginning of WindowsPE that could do the copying? Anything that could make these inf files get copied before the T-13 point in Windows PE would do the trick.

Attached File(s)

•  TXTSETUP.zip (87.24K)
  Number of downloads: 1

[tommyp]

I'm not sure what files you are missing during copymode, but like I said, the files should reside in your sourcess\i386 folder. I'm afraid you'll have to be a little more specific on what files are not getting copied. I can't check that for you on this side of the screen.

The inf files are copied right after the drive is partitioned. I'm unaware of cmd files that can be run at that point because the OS isn't installed at that point in time.

I think it's probably a better idea to post your hfslip.log file.

[mserbin]

Here is the log file. The inf files that are not getting copied are all the hfs*.inf files that are supposed to be copied into c:\windows\hfslip directory. There are 77 inf files total. Names include: HFSLIPSD.INF, HFSLIPWU.INF, HFSLP151.inf - HFSLP156.inf, HFSLP200.inf - HFSLP267.inf, and HFSLPGUI.INF. Thank you for your help on this. I'm pretty new to slipstreaming but pretty script/programming savvy. I also have a few questions about some of the Windows hotfix updates that were put into the HF folder but were missing from the installed version. I'll start a different topic under probably Muppet's forum to see if he can help, probably just have an outdated update that is overwritting the more current update.

Attached File(s)

•  HFSLIP.zip (1.27K)
  Number of downloads: 1

This post has been edited by mserbin: 28 October 2009 - 06:48 PM

[tommyp]

Your host OS is unrecognized. Did you use an XP machine when you ran HFSLIP? You'll need an 2000, XP or 2003 to run hfslip. If you have another OS, then all bets are off. If you are indeed using 2k/xp/2003, please use the latest beta, it's more up to date than the one you are currently using. The beta is stickied on this forum. You may want to clean up your hotfixes too. For starters, you can place the 4.5 installer into HF now.

[mserbin]

MY host OS is Windows XP Pro x64 edition, that is why it says it unrecognized. Will XP Pro x64 work for this or should I use HFSLIP on a XP x86 machine? I will look into cleaning up my hotfixes as well.

[tommyp]

I can't say whether or not it will work on a 64 bit machine. I know for sure it does work on a 32 bit one though. Try it out and report back.

[mserbin]

I cleaned up my hotfixes and used beta s, but still had the inf copy problem. Will recompile it from a 32 bit machine instead as the next test. Here is my logfile for this last attempt.

Attached File(s)

•  HFSLIP.zip (1.35K)
  Number of downloads: 2

[mserbin]

I ran HFSLIP on a XP x86 computer and the inf file issue still persisted. The only thing I can think is maybe it is being caused because I used a Dell XP Pro SP3 disk as my source. I read on a different forum that recompiling the Dell OS disk might help and removing some files from it. Have you had this problem with Dell or other manufacturer OS disks before?

This post has been edited by mserbin: 30 October 2009 - 11:17 AM

[tommyp]

In a SAMPLE run, try this. It appears your source is pre-modded with something.. Try this. Remove the svcpack folder in source, also remove the svcpack.in_ or svcpack.inf. This is a test case that's worth a shot.

Oh, nobody else is having the prob you are having, or at least that's what the people in the beta thread are saying.

This post has been edited by tommyp: 30 October 2009 - 01:52 PM

[mserbin]

I will test that out and let you know what happens. In the mean time though I made a change to the host OS detection code so that it properly recognizes Windows XP x64 as Windows XP instead of unrecognized. This should make HFSLIP completely compatible with Windows XP Pro x64 edition as a host OS. I have made several boot disks from my x64 host computer and it works properly other than this inf issue which is probably related to my source files as they were modified by Dell. Here is the new host OS detection code, check it out and let me know if you are going to include it in a future release

:: Find host OS - based on code posted by Yzöwl on MSFN.org
SET HostOS=Unknown
FOR /F "DELIMS=" %%I IN ('NET CONFIG WORK^|FIND /I " Windows "') DO (
ECHO %%I|FIND "2000">NUL 2>&1&&(SET HostOS=2000&GOTO :HOSD)
ECHO %%I|FIND "2002">NUL 2>&1&&(SET HostOS=XP&GOTO :HOSD)
ECHO %%I|FIND "XP">NUL 2>&1&&(SET HostOS=XP&GOTO :HOSD)
ECHO %%I|FIND "2003">NUL 2>&1&&(SET HostOS=2003&GOTO :HOSD)
ECHO %%I|FIND /I "Vista">NUL 2>&1&&(SET HostOS=Vista&GOTO :HOSD)
)

It is this line of code that detects Windows XP x64
ECHO %%I|FIND "XP">NUL 2>&1&&(SET HostOS=XP&GOTO :HOSD)

When you run NET CONFIG WORK from an XP x86 system it returns Windows 2002
When you run it from an XP x64 system it returns Microsoft Windows XP

Here is the log file showing that my OS detection modification code worked properly. This was run on my Windows XP x64 system, and the host OS now shows XP instead of unrecognized.

Attached File(s)

•  HFSLIP.zip (1.32K)
  Number of downloads: 2

This post has been edited by mserbin: 30 October 2009 - 03:18 PM

[mserbin]

In my source folder I have a svcpack.in_ and a svcpack.dl_ but there is no svcpack folder. Should I remove the in_ and dl_ or just the in_ file?

[tommyp]

Thanks for the lines of code. I'll roll that into the next beta.

Just remove the svcpack.in_. Leave the svcpack.dl_ alone. Also, open txtsetup.sif and look for svcpack.inf. Put as ; [semicolon] before that line. Rerun the script. Remember, these are test cases and you'll need to recopy the source folder once again if this doesn't work out well. IIRC, I've seen a few dell cd's that put some KB (i.e. hotfixes) into the i386 folder. You can probably delete them too, along with the apprioriate entry in txtsetup.sif.

[mserbin]

I found the problem. It is not with the svcpack.in_ file it is with the txtsetup.sif file.

Dell defines a custom folder in this line
999 = pchealth\helpctr\batch

And those inf files are being copied there instead of c:\windows\hfslip which is supposed to be referenced by folder number 999 in this line
HFSLP151.INF = 1,,,,,,,999,0,0

Therefore, I will edit this line:
[WinntDirectories]
998 = HFSLIP

Then just update all the inf entries to be like:
HFSLP151.INF = 1,,,,,,,998,0,0
HFSLP152.INF = 1,,,,,,,998,0,0
etc....

I will test this out and let you know if it works. This is finally the answer though for the guy that started this forum a long time ago

This post has been edited by mserbin: 30 October 2009 - 05:13 PM

[mserbin]

And actually, if we modify the hfslip.cmd so that it uses folder number 998 instead of 999 it will avoid the Dell disk conflict entirely. This is too many lines of code to give you to update here, but if you do a search for the number 999 in the hfslip.cmd file and replace them with 998 it should do the trick. This could also be included in the next beta. Here is the edited cmd file that contain both of my fixes.

Attached File(s)

•  hfslip_1.7.9_beta_t.zip (55.32K)
  Number of downloads: 3

This post has been edited by mserbin: 30 October 2009 - 05:40 PM

[tommyp]

Good find dudeman! Lemme test out renaming the 999s and see what happens.

[mserbin]

I just tested it, no inf problem!!!!!!!

This post has been edited by mserbin: 30 October 2009 - 06:28 PM