HFSLIP (original thread)

[fdv]

Okay, tweakui 133 repacked as a Type2.

Also, that stupid "everything stops until you close the displayed help screen popup" bug should be fixed.

Get it here (tweakui.exe).

edit: made a link rather than just listing url

Edited August 3, 2005 by fdv

[Oleg_II]

fdv

Thank you for the advice with OEM folders. It worked for me either. But there were too many files and folders on my disk and I started to look for other options. I still use a self-extracting archive with the files I want to place in different locations with inf (run it from cmdlines.txt) - compression saves some space. It's not a problem, just a thought.

I've tried the programm you recommended but will write you later this evening as I need to reinstall Windows (got some work to do

Would it be suitable to ask in this topic for including one feature from XP to W2k - wireless control?

Best regards,

Oleg 2

[tommyp]

If using the OEM folder, don't you need an extra line in your WINNT.SIF file? Is it oempreinstall=yes or something like that? Or am I thinking of something different?

@gzduke5: I'll review that INF file later today when I get a chance. Thanks for posting.

@Oleg_II: What is the 2k to xp wireless control you talk about? If you're talking about the wireless service (802.11), it's already there.

@FDV: Thanks for adding in nice utilities for the SVPK folders. I guess those folders come in handy for some cool stuff.

[fdv]

If using the OEM folder, don't you need an extra line in your WINNT.SIF file? Is it oempreinstall=yes or something like that? Or am I thinking of something different?

Whoops! Yeah <smacks forehead> Oleg_II, please include this in your WIINT.SIF file. Better yet please look at mine as an example.

[dziubek]

@TommyP

Your programme would want was more yet universal,therefore these my proposals.

I apologize if I offended You, this wasn't my intention

I greet

[os2fan2]

I wonder if tommyp's slipstream will work with an older defectX 9.0. It's a 35 MB download, and i have dialup.

[Oleg_II]

tommyp

About wireless control - maybe I'm wrong. I'm using wireless access myself but a friend of mine told me some time that he finds wireless access points with standard Win XP utilities, and I have to use 3d party programs like NetWork Stumbler or Boingo to find out if there any access points nearby and configure my wireless card for it. I tried to find this functionality on my collegue's notebook today (there is only one computer with XP in our office) but she doesn't have wireless card and I can't try. I'll check it with my friend later.

Best regards,

Oleg 2

[tommyp]

@os2fan2: DefectX.... HAHAHA. Both versions of defectx install, it's your choice on which way to do it. I like the slipstream one better.

@Oleg_II: I don't plan on mixing OS's via the script. So I'll leave that up to you. Sorry dude. You may want to see which DLLs and INFs are required to install that wireless service. If you add some files into the fix folder, the xp wireless service may start. I haven't tried it. Files you would need are sfc.dll, syssetup.dll and some other ones.

[Oleg_II]

tommyp

That's Ok! Thank you for the script as it is right now anyway.

There is not so much left to slipstream to Windows 2000.

I have one more idea:

- the quantity of hotfixes will be increasing during the time, there are already more then 50MB of recomended by you not including files for IE and DirectX;

- one of the conditions for using your script is to use not altered source with SP4;

- in order to use your script in future one has to collect all needed hotfixes and run the script on increased base again for getting the most upated source;

- there are some hotfixes that just have some new binaries and there are a lot of not needed files in other hotfixes;

- may I sugest to break the script on two parts: first part for working on all hotfixes and additional files creating one (or a few) half finished BIG hotfix(es) with only files that are really needed, and the second part of the script will integrate the resulting file (or files) into the source? Next time running the script we can use created file(s) along with the new hotfixes.

Of cource, there is one more possibility if the script can be run on top of already slipstreamed source

Best regards,

Oleg 2

[samogon]

i've god w2k_sp4_rus(was sp2).

Rollup does not integrated...

IE6 -ok!!!

DX9c -ok!!!

All other patches -ok!!!

Can you help me?...plz...

tnx

Edited August 4, 2005 by samogon

[fdv]

Oleg_II - if you consolidate (for example) 10 hotfixes, and later, a bunch of hotfixes replace what you already have, you'll have the same problem again.

In other words, picture this. You make a hotfix that has an IE rollup. Then, MS issues another rollup. And, say, they do this again and again and again for a total of six (Oh wait, Microsoft actually DID issue six IE hotfixes ). Your big, merged hotfix would just be obsolete over and over. tommpy actively analyzes hotfixes for what you need and what you don't.

Of course I have zero doubt that tommyp could create a script that was a "Really Big Hotfix Creator" but as of right now there isn't all that much duplication in the hotfixes (and it would still be pretty big). While the script is running, the WORK (or is it WORKING?) directory has all the updated files; I suppose the process could stop and ask if you wanted to CAB them all into a Mighty Big Hotfix or if you wanted to go ahead and slipstream, but it seems kind of duplicative to me personally.

[fdv]

samogon, I dont see a link to Rollup for Russian language.

Can you give us a link?

[samogon]

fdv,Rollup Russian here but RUSSIAN

may be:

SCRIPTEN.exe <---Place this into SVPK_SW folder if WU gives you problems

Edited August 4, 2005 by samogon

[Oleg_II]

fdv

Maybe you are right. I don't criticize tommyp, his script works fine. And I'm not a computer specialist, maybe I don't know some things that may influence the process like outdated and obsolate .cats for hotfixes that were replaced or something like this. But I'm still thinking that it is a bit convinient to have one file instad of a banch. Next time running script with this file and new hotfixes in corresponding folders may replace old entries with new ones. I suppose something like this happens when we apply a service pack or a hotfix.

And a really big advantage of tommyp's script is that one can choose the hotfixes to be installed. This feature also can be used - one can choose to use a banch of hotfixes or one file created before along with new additions and new hotfixes.

Best regards,

Oleg 2

Edited August 4, 2005 by Oleg_II

[tommyp]

@samogon: I can help you out with your problem. I'm afraid I'll have to ask you to read the directions on how to post about errors on non-English versions. Without that, I really can't help.

@Oleg_II: I can do that request you asked about, but I'll have to ask you to find a commandline program that is a makecab equivalent. The problem with makecab is that when it makes a compressed binary, it assigns the current date. If you can find a commandline compression program that when it makes a compressed file, it doesn't change the date of the file. I suppose I could just rename the files with a "_" extension, but people will complain that their i386 folder is too big. So, if you find a utility, I can do that request. I have to question why this may be an issue. The script takes about 15 minutes to run. If you are going to be making an installation CD, why not just run the batch, go outside and breathe fresh air and when you get back its done and you're ready to make your boot cd.