Oops, I forgot about that .

When I didn't provide the full path, that Advanced INF Install error occurred. Does that mean I do need it for Windows 2003? It worked fine without on XP.

I'd think not since it's newer than Windows XP, but try it. You don't need to run HFSLIP again for that; just edit your CMD in SOURCESS\I386\SVCPACK.

You mean try installing with the full path in the CMD? OK, will report back.

With CMD files that are processed during setup, it is good practice to specify the full path to the files you are working to. Using system variables also helps. To get an idea of what variables are available open a cmd window and type in SET.

@FDV,

You could do the same to the link on your 2K SP5 page. http://users.telenet.be/tc76/winup/_win2k.html

But, thanks for updating the link on your XP page.

@Tomcat76,

Does it matter that I put 'START /WAIT' at the beginning of the main line in my script? I won't be able to test my 2003 install with the modded CMD until maybe Thursday.

START /WAIT should work. I can't see a problem with that.

Those link problems are really strange. About a month ago, someone said FDV had the wrong links on his site and I apologized a few messages later for not alerting FDV of this. I can't find that thread anymore, though. And now three times in a row. How many links does FDV have on his site?

@FDV: the correct links are in my signature. They were all changed simultaneously a long time ago. I thought you were already aware of that for quite some time but apparantly not. Sorry if I got you confused.

That someone was me actually . After you *apologized*, I thought that FDV had seen my message. But the links were never changed (until now). When I posted that original message in the other thread, browsing to the links on your old server would turn up an error message (page not found). Now I see you have the redirect link on the page.

Maybe you should have the pages redirect automatically to the new links. That way, it'll be easier. FDV only has two links to your update pages - one on the XP/2003 page (for XP only; he has Bilou's link for 2003) and one on the 2000 page.

-- Super-Magician

in any case it's always best to pm me

I'll keep that in mind...

Hello
1. I have big problem. My setup stops in 9 minute near end of installation.
In spite it removal the content of catalogs: HFSVPK and HFAAO. Problem steps out from several version hfslip, but I had not time about this to write :>

2. After generating folder SOURCESS creates file MPDIR1.TXT with content : wpdmtp.inf

Until you can get some real advice from the devs, I can offer a bit of unqualified tester advice

You have lots of stuff in FIX. Is that OK with XP? I am a 2k user and I don't put nearly that much stuff in FIX...but I also don't have things like the theme support.

Has everything in your HF folder been used to generate a good ISO before?

Try running w/o HFCABS as well. Not sure how well-tested the support for those DX cabs is

I don't have a freakin' clue about mpdir1.txt

Good luck!

@dziubek,

The current test release has a few problems that have not been ironed-out yet. Please test it with 60317, the most recent final release.

The MPDIR1.txt is left over from an earlier version of the WMP script section and is useless. Tomcat forgot to remove the line that creates the file.

@dziubek:
You're clearly mixing things. According to your ERROR_REPORT.TXT file, you're using 60322a but that version does not create MPDIR1.TXT. You surely forgot to remove it when you did a test with 60321a-wmp or 60321b-wmp before.

Try removing things from the FIX folder.

BTW... You got mplayerc.exe in APPREPLACEMENT. I could be wrong, but shouldn't it be named mplayer2.exe?


@TAiN:
The DX cabs are fully tested.

I'd like to release a final this weekend if there are no new issues with the latest test release. Nothing was changed in the way hotfixes or addons are handled so it's enough if you let Windows setup get through the initial file copy stage.

@dziubek:
Please try the latest test release. Hopefully your T-9 problem is resolved.

By no means is this version final.
2k/ie6/hfdrv and no driver merge and no cleanup. OK
2k/ie6/hfdrv/driver merge and no cleanup. Not OK. (txtsetup error).

Fixed. Thanks.

I came across this problem once before, when I did the slipstreaming section. When you set a setter within a wrapper, it isn't yet "ready to be used" inside that wrapper. Really a stupid limitation of DOS...

*bump*

(didn't really have much effect; this is now five threads down again)

Does anyone use HFSLIP's built-in ISO creator? If you do, please give 60328a (or higher) a test run. I need to know if everything's OK with:

- CDIMAGE
- MKISOFS
- CDIMAGE + ISOconf.txt with customized settings
- MKISOFS + ISOconf.txt with customized settings

I'm gonna try to test as much as I can myself but if there are no positive responses this update won't make it into the upcoming final.

Thanks...

I don't use integrated iso creator but I know (from older tries with nLite) that mkisofs has problems when dealing with DVDs. It seems to me images can't be burned to DVDs.

I don't know what you're using but, for CDIMAGE, don't use the -o switch (encode files only once, thus sparing some space on the media), it causes some boot problems (on some computers, even recent ones, the media will not be bootable whereas it is on others).

My thoughts on CDIMAGE:

The -o switch is never a problem for me. If the disc does not appear to be bootable on some computers, it probably has to do with the BIOS settings. Optimizing the files should not mess up the boot image.

Images can indeed be burned to DVDs. I've used CDIMAGE for a multiboot DVD, and it works perfectly when I burn it with dvdburn (Microsoft command-line tool).

HFSLIP doesn't use the -o switch, but I do. I never had a problem with it.

-h -n -m -o works great for me.

Same here!

Alrighty... 60328c is gonna be the final for tomorrow unless someone finds a problem that doesn't exist in 60317. It's about time, I'd say...

I've been sharing my isos with friends.

Approximately 5/6 tried and there, 2 couldn't boot.
They are both used to install modded XP such as the LSD III (french one). They are far from being computer disabled and now I've removed the -o switch they can boot on the CD.
It used to spare 8129bytes so I disable it without any drawback.
(one is using a Centrino1 VAIO, the other one has at least a P4@3GHz)

HFSLIP_60328c.CMD with XP CORP, PRO HOME compression A & F ok
used ISOinfo w/ mksiofs ok
I don't use the HFexpert folder.
files in FIX, HF, HFKSPV, HFCAbs

New test release for Server 2K3 SP1...

groovy. building with test version now.

(even if i can get it really cleaned out, i am still going to use win2000 for a while.)

i feel like creating a win 2003 poll, to guage demand for reduction work we've been doing.

Do a poll FDV. I'd be interested in seeing if there really is a need.

This thread used to be 18 pages long. What happened to all of the original posts?

A little off topic: Just wondering - can a moderator edit a post but prevent the system from showing that the post was ever edited? Most edited posts will show something like this:

I just loaded up a test installation of IPB to try this out. Admins can do it, and mods can do it if the admin gives them the privilege.

Some possible changes/additions to HFSLIP:

1. Remove second copy of ERROR_REPORT.TXT in SOURCESS - To me, there really is no point for this second copy. I always end up deleting it before creating my ISO file (I use my own personalized batch file). I'd like to see this removed. If you disagree, please tell me why.

2. Compress ERROR_REPORT using MAKECAB - I believe TAiN floated the idea to make HFSLIP automatically compress the ERROR_REPORT after it is created. I think this would a great addition as often people simply post the TXT file on this forum without putting it in a ZIP file first. In Internet Explorer, since there is no "word wrap" setting, clicking on the file just opens up the error report with continuous text and no line breaks, and it's hard to read.

3. Automatically run a custom batch file after HFSLIP is completed - Have the capability for HFSLIP to call up a custom batch file (i.e. custom.cmd) after the slipstreaming process. As I mentioned in the first item, I use my own CMD file to automate the ISO creation process, and I would like this to run automatically after HFSLIP is completed. Maybe something like this would work:

The purpose of the error_report in the sourcess is so you could refer to the file after the cd is burned. Does this file take up too much space? hehe Perhaps we could make hfslip look at an answer file to see whether or not to include the error_report.

If you have special cmds or batches that you think would be beneficial to add to hfslip, why not just share your idea and ask us to add it? We appreciate inputs.

I use this feature. It is quite handy whenyou have lots of ISOs laying around from a lengthy bug-squashing session. Since the root error_report gets overwritten, the ISO copy provides a great snapshot of what that ISO represents.

I agree with you and would still like to see the compressed error_report

What if the version inside SOURCESS is renamed to report.txt or something?

And I can do it. But not on this board.

Stupid comment about the makecab of the error_report posting/cabbing. Without a hfnetchk run, which you must run on the sourcess, the authors really have no idea on what's wrong. Besides, 9x out of 10, noobs don't post the error report anyway (or read any of the online literature for that matter). Sorry to sound harsh. Another stupid comment on the makecab'd error_report. The first lines of the txt file tells the user what to do with the file. If it's cabbed up, the user may think that the cab file is just an artifact of running the script and they won't do what it says. Then they'll still come onto the board and not attach anything.

SuperM, Tain sees the purpose of the error_report. It can be named to other things. Is this a good compromise? One a sidenote, please remember that HFSLIP is for home use only. You see this everytime you run HFSLIP.

I do understand the purpose of the error report. Personally, I just thought that the extra copy was useless. However, I see now that some people like to have that in SOURCESS also.

I think renaming the error report would be OK. This would clarify the purpose of the file a bit since it's created every time HFSLIP is run.

My batch file is simply to just automate the ISO creation process. It has a bit of extra stuff packed into it, but I'm not sure including it in HFSLIP would add any additional functionality.

[attachment removed]

Not really. The only difference is that you're specifying a time stamp but you can do it with HFSLIP too by adding -txx/xx/xxxx,xx:xx:xx to the list of switches for CDIMAGE in the ISOconf.txt file.

Something like HFSLIP_LOG.txt may be more descriptive. It isn't *really* an error report, anyway. The output assists in diagnosing errors that come up. I haven't really seen anywhere that HFSLIP outputs useful error information...unless that is a diagnostic mode for it. It might be handy to have all of those 'file not found' and other such errors that go flying by get dumped into a real error_report.

To get all of those errors in a file, run HFSLIP from the command prompt as such:


I agree that HFSLIP_LOG.txt would be more descriptive. In the current test release, it is HFSLIP.txt in SOURCESS.

There is a diagnostic mode in HFSLIP, but I don't the exact specifics for it. I believed it is/was used by tommyp/the authors.

I'd actually prefer something in 8:3 format. HFSLIP_LOG.TXT surpasses that...


The "File not found" errors are to be avoided. They are there because HFSLIP copies/deletes/renames files but doesn't always check if they exist first. It's a split decision between seeing errors fly by and having a script that's 10 times bigger. About the only section I've "cleaned up" recently in that regard is the part that does MSXML but I only did it because I found a much better way of processing the MSXML files which resulted in a much more compact section.

I apologize so late writes back, but I had to leave.

1. It after many tests turned out that error causes file SFCFILES.DL_. When I removed from FIX folder this file, installation passed unproblematically.

Hfslip earlier run with this file unproblematically.

When I use HFSLIP_60404a.CMD and D type driver compression I had these problems:

1. "Copying file % maininf % it wasn't possible"


2. After first starting system I have 2 error:



I use only Microsoft .NET Framework 1.1 SP1 +KB886903 +polish langpack(Self-extracting switchless installer) ->> It never was with him problems.

3. WU doesn't be happy It demands to install again: KB 898461 and KB892130

4. I don't change location MY Documents in winnt.sif :>
It set locations of this catalog significantly how I have put in system on which I started hfslip.->> D:\Moje Dokumenty. Default folder should be C:\Documents and Settings\Administrator\Moje dokumenty
It causes then problem with Virtual CDROM Control Panel.


5. Only _CPL_Addons installed (still missing file-CDImage.cpi) and programs from HFSVPK folder

dziubek

dziubek - can you see what happens when you run without the application add-ons? Also, it's a bit hard to see some of those screenshots. They are too small. Or better yet, on your item number 2, what does it say (translated to english please). Thanks

Something about not being able to start the application because framedyn.dll couldn't be found. Reinstalling the application might fix the problem.

dziubek... Can I see your TXTSETUP.SIF? It appears one of the variables in an addon package slipped through the filter.

second picture:

"Starting this application did not to be successful, it because framedyn.dll wasn't found . Renewed installation application can repair this error."

third picture:
"Error stepped out during loading srclient.dll . Can't find of definite modules."


I manual reinstalled Self-extracting switchless installer but error appears still.

I created html file from links to majority addons which I use

dziubek

A sidenote - how come your start menu button came out capitalized? On XP English, it isn't.

@dziubek...

Remove Boooggy_ASPI_Addon.cab for now. I'll check what's going wrong with it tomorrow.

I'll try to fix the CDImage problem too.

I Removed Boooggy_ASPI_Addon.cab and I test now with HFSLIP_60405b.CMD. In hour I will present results

p.s in APPREPLACEMENT I should have mplayer.exe or mplayer2.exe?

dziubek

I believe it is mplayer2, but you should get Tomcat's confirmation.

First test
-----------
I used HFSLIP_HFSLIP_60405b.CMD (without folder HFAAO) and D type driver compression

----------

1. I have not problem with % maininf % already
Thanks for disinterested help :-)

2. Remaining errors aren't present also

WU is happy but :
[img=http://img401.imageshack.us/img401/6595/errr9yg.th.gif]

When it was installed the rest is all ok.

3. The problem is present with path of access to catalog MY DOCUMENTS still.

4. How I can download & integrate KB 905474 ?

Second test
-------------
I used HFSLIP_HFSLIP_60405b.CMD (with HFAAO) and D type driver compression
I Removed Boooggy_ASPI_Addon.cab
------------
1. I have not problem with % maininf % already
2.WU is happy but :
[img=http://img401.imageshack.us/img401/6595/errr9yg.th.gif]

When it was installed the rest is all ok.

3. All addons was installed correctly :-)

4. The problem is present with path of access to catalog MY DOCUMENTS still.

@Super-Magician

You were right ,thanks