How about a short music when HFSLIP is finished?

[glentium]

How about a short music when HFSLIP is finished to get attention. This is specially useful when we work with multiple windows or even multiple computers (or KVMs). Most of us do other things and leave HFSLIP while it's doing it's job. So it would be helpful if it would alert us somehow that it's finished.

How about playing a small music file, MP3 or WAV, using a command-line program like MPLAYER with both mplayer and the small music file in HFTOOLS?

A simple set of beeps using ECHO ^G might not suffice if we become too busy or engrossed in what we are doing but will still be a good addition if the music file option is too much...

[tain]

This could be indicated in the answer file as well.

Does a player need to be used? I thought "the system" would be able to play a .wav file on its own or with sndrec32.

[Yzöwl]

Most of us do other things and leave HFSLIP while it's doing it's job.

Upon which data did you base that?

When you've finished with whatever else you feel like doing, whilst HFSLIP is running, there will be a cmd Window indicating that it has finished.

The script will only run for a period of around 6½ - 15minutes. If you aren't capable of remembering what else you were doing in the last quarter of a hour

[Super-Magician]

The script will only run for a period of around 6½ - 15minutes. If you aren't capable of remembering what else you were doing in the last quarter of a hour…

For people with slower computers (that is, people who don't have your computer), HFSLIP can take anywhere from 15 minutes to even an hour long to run.

[glentium]

Most of us do other things and leave HFSLIP while it's doing it's job.

Upon which data did you base that?

When you've finished with whatever else you feel like doing, whilst HFSLIP is running, there will be a cmd Window indicating that it has finished.

The script will only run for a period of around 6½ - 15minutes. If you aren't capable of remembering what else you were doing in the last quarter of a hour…

Maybe just a wild guess. I multitask. I have several windows open most of the time. I use a KVM switch to work between my production computer and test computer (which I use to connect to the internet). But I don't think I'm the only one who multitask, at least. Or am I the only one who reads a magazine while HFSLIP is running?

Besides, the CMD window is not always on top of the screen.

And HFSLIP runs for about 25 minutes in my machine withe ISO generation turned on.

And most of the time HFSLIP is finished for several minutes already before I remember that I did executed it... well, maybe it's just me. I need to upgrade my brain to duo, or quad perhaps.

Edited August 24, 2006 by glentium

[Yzöwl]

For people with slower computers (that is, people who don't have your computer), HFSLIP can take anywhere from 15 minutes to even an hour long to run.

Once again another assumption!

My HFSLIP takes around 7 minutes, 11 if I integrate XPize. It is six years old and runs on an old AMD XP+ with 1 Gb RAM. From what I have learned attending these forums over the last two years, it is reasonable to assume that my PC is not considered a 'faster computer' from an average selection of forum users. My assumption therefore is that your HFSLIP is taking longer because, for one or more of the following reasons:

1. Multitasking, which isn't a good idea considering the memory intensive work it is undertaking.
   
2. Recreating your source files from scratch on each run
   
3. Integrating many additional things such as XPize and addons into your disk
   
4. Not maintaining your PC for optimum usage.
   

[glentium]

My assumption therefore is that your HFSLIP is taking longer because, for one or more of the following reasons:

1. Multitasking, which isn't a good idea considering the memory intensive work it is undertaking.
   
2. Recreating your source files from scratch on each run
   
3. Integrating many additional things such as XPize and addons into your disk
   
4. Not maintaining your PC for optimum usage.
   

Uhmm, what do you mean in point no 2? Isn't it that HFSLIP automatically delete SOURCESS folder each run, except of course when you specify HFCLEANUP?

From: http://hfslip.org/howto.html

"When running HFSLIP once more, be advised that your SOURCESS folder will be deleted immediately in order to create a new one."

And I don't think HFSLIP will have a problem with multitasking. I tried running HFSLIP by itself and along other things (multitasking) and the difference in execution time is minimal. We all know that HFSLIP just slipstreams the newer files into a new source. If one is manually applying the hotfixes in a live Windows XP, then, I agree you should close other applications and not multitask.

But I guess the length of HFSLIP execution time is not important. If HFSLIP finishes in 5 minutes, it's really great. But I just wish I will be alerted somehow If ever I'm doing other things cause I still would not stare at the computer monitor for 5 minutes. Is an audible alert really that bad of an idea?

[tain]

Plenty of other apps have audio alerts. I would find the feature useful. I tend to multitask and lose track of the cmd window or leave the computer room altogether while it is running.

[Yzöwl]

Uhmm, what do you mean in point no 2? Isn't it that HFSLIP automatically delete SOURCESS folder each run, except of course when you specify HFCLEANUP?

SOURCE is the 'source files' SOURCESS is the resulting output.

And I don't think HFSLIP will have a problem with multitasking. I tried running HFSLIP by itself and along other things (multitasking) and the difference in execution time is minimal. We all know that HFSLIP just slipstreams the newer files into a new source. If one is manually applying the hotfixes in a live Windows XP, then, I agree you should close other applications and not multitask.

HFSLIP doesn't multitask, the PC user does. Also what do you think the script is doing?

It is copying, extracting, compressing, moving, deleting, writing and reading files, running nested for loops, storing data in memory and possibly running installers. It does all this as multiple commands in quick succession, hence the name script. I would think it fool-hardy to run anything else on top of that and expect a flawlessly produced resultant SOURCESS directory or ISO file.

Also what is the point of console output if people are not even looking at it?

I am not, and have not, stated my opinion on the main topic of discussion in this thread, just the incorrect remarks used in order to try to make a point. I find that submitting factual data is the most effective way of attempting persuasion to learned readers.

[tain]

...and I thought you were just being grumpy

[Super-Magician]

Once again another assumption!

My HFSLIP takes around 7 minutes, 11 if I integrate XPize. It is six years old and runs on an old AMD XP+ with 1 Gb RAM.

...

I am sorry that you have taken my statement to be an assumption. I based it on what I saw in many HFSLIP.LOG files that have been posted across this forum over the past few months or so. There are some computers that take about 20 minutes to run HFSLIP (similar to my box) and others that take as much as 58 minutes. Yours by far takes the shortest amount of time (~6 minutes).

I hope that you don't assume that what people say are assumptions.

[tommyp]

If your PC takes 58 minutes to run the script, you have a really slow machine and/or it's bogged down with spyware/junkware and/or your source is bloated. If I run in hfcleanup mode, it takes about 16 minutes. I'm siding with Yzowl on this. Let's keep hfslip lean and not dependant on too many windows functions and most importantly not a remedy for a computer user's short term memory loss.

[fdv]

I have a few lines of code that I cut and paste into every new version that cause Sarah Brightman to come into the room and give me a lapdance uh I mean sing me a song that HFSLIP is finished. Her airline tickets add up, though, and it usually takes her some time to get to my place, so I don't use this feature too often...

[Super-Magician]

If your PC takes 58 minutes to run the script, you have a really slow machine and/or it's bogged down with spyware/junkware and/or your source is bloated. If I run in hfcleanup mode, it takes about 16 minutes. I'm siding with Yzowl on this. Let's keep hfslip lean and not dependant on too many windows functions and most importantly not a remedy for a computer user's short term memory loss.

HFSLIP takes about 20 minutes to run on my (relatively-slower-than-some) computer (2.4GHz + 1GB RAM). Therefore, I am not saying that Yzöwl (or you for that matter) is/are wrong. I am simply stating that HFSLIP does take a long time for some people.

In agreement with what you said, I am not too supportive of this idea. I am just happy that my computer doesn't take very long (and is not bogged down by spyware and junkware...I think ) .

[glentium]

Uhmm, what do you mean in point no 2? Isn't it that HFSLIP automatically delete SOURCESS folder each run, except of course when you specify HFCLEANUP?

SOURCE is the 'source files' SOURCESS is the resulting output.

And I don't think HFSLIP will have a problem with multitasking. I tried running HFSLIP by itself and along other things (multitasking) and the difference in execution time is minimal. We all know that HFSLIP just slipstreams the newer files into a new source. If one is manually applying the hotfixes in a live Windows XP, then, I agree you should close other applications and not multitask.

HFSLIP doesn't multitask, the PC user does. Also what do you think the script is doing?

It is copying, extracting, compressing, moving, deleting, writing and reading files, running nested for loops, storing data in memory and possibly running installers. It does all this as multiple commands in quick succession, hence the name script. I would think it fool-hardy to run anything else on top of that and expect a flawlessly produced resultant SOURCESS directory or ISO file.

Also what is the point of console output if people are not even looking at it?

I am not, and have not, stated my opinion on the main topic of discussion in this thread, just the incorrect remarks used in order to try to make a point. I find that submitting factual data is the most effective way of attempting persuasion to learned readers.

Sorry, I know the difference between SOURCE and SOURCESS, I'm just not sure anyone would recreate his source from scratch each time. If ever anyone does that, it's not part of total HFSLIP run time because the user prepares the SOURCE beforehand. Unless, someone will always put a pre-SP2 source (in WXP case) and let HFSLIP slipstream SP2 each time. I guess no one does that...

Of course, HFSLIP doesn't multitask. What I was trying to say is that if ever the USER multitask, HFSLIP will not have a problem and like I said, it barely affects the total runtime of HFSLIP. And I never had a flawed SOURCESS because of me multitasking. (of course, 60810 is simply great!)

But now that TommyP has rejected the idea, I guess an audible alert is a not a good suggestion after all.

Anyway, I'll just put a string in my index finger whenever I'll run HFSLIP...