Camarade_Tux

This is hosted on a PC, not a server : myvnc.com = no-ip.com

I see. Add them on the RunOnce page.

They used to have a cleaner... Here is the longest way but at least, you'll get rid of NAV : http://service1.symantec.com/SUPPORT/ent-s...1914291648?Open

I think this setting is stored in a file : reduce the number of connections and then, set the file to read-only/remove write rights if on NTFS.

I was told it would, but only if it's delivered with a pizza.

I'm sorry jcarle, it's not. I hope you did not took too much otherwise you may have heart problems.

And donation link sends to mozilla.org

Imagine you have 10 times the *same* file in different folders of your CD. The -o switch will only write this file once and will redirect to it the other times. It will save space. As far as I remember, ntdll is required in i386\SYSTEM32 and the files in i386\SYSTEM32 and i386 are not the same (maybe because of one hotfix). So instead of having 716KB (uncompressed) + 400KB (compressed), -o you will give you 716KB only. NTPRINT and intl.inf are mainly text : they can be highly compressed. On these two files, you can easily save 1MB or more. regedit.exe is already pretty small. For the other ones, I can't remember. I just know my script reduces my source folder by 4 to 5MB after heavy nlitement. edit : if you disable system file checker, you still need the sp1.cat OR sp2.cat (according to your SP level, not both) but they can be 0-bit. There's no need fo ra SVCPACK folder : it is directly in i386.

The process name of WPI = mshta.exe So if you use WPI you can't remove this? Indeed.

Thanks a lot prathapml

What does your OEM folder cotnains ? Files like DP*.7z ? Can you copy/paste the content of your cmdlines.txt ? How big are $OEM$ and OEM folders ? Are there *oobe* files on the CD/on your hard drive ?

I may be wrong but imapi.sys is not necessarilly only related to IMAPI Burning. Oh, and, see : ntprint.inf/.cat, spX.cat, 0-bit sfcfiles.dll, cab more i386 files

Website, in english : http://www.crystalxp.net/bricopack/en.htm

You're talking about a warez edition but since you seem to want something legal, I think we can speak go on. Do you have oembios* files in i386 folder ? is there a file called last session.ini or so on the CD ? Is there a nlite.inf/nlite.in_ in i386 ? Maybe it's corporate edition (not regular). Why not instead port the additions from this windows edition to your own-made CD ? What other folders do you have on the root of your CD ? $OEM$ ? Is there a cmdlines.txt in this $OEM$ folder ?

Right, happy birthday. Now you can go out and get drunk, no ?

DX packs are cumulative : they contain the whole thing. These bi-monthly updates are bigger not only because they are multinlingail but also because they contain some Dx10 parts. link

Let's do our own. And don't think about nvu : it has some bad habits.

Bittorrent and ed2k maybe ?

That is "the work" he is referring to; not necessarily publishing an exhaustive product. Since I've already done that for my own purpose (see sig, thanks Notepad++), I may redo it in a cleaner way (I deleted some entries that didn't fit) ATM, I have: Associations.reg context menu explorer IE kernel ie logon network search service a special file to switch caps on/off with shift or CAPS LOCK start menu user relateds visuals Jein, Ja/Nein : don't really know if they are good or bad Other softs.reg Others and others I have deleted cause they are bad (iopagelocklimit, alwaysunloaddll and another one have no effect on NT) Is everybody OK with this sorting ? Having the tweaks spread over different files let me find nearly all duplicates, if only I had noted them.

Hi everybody, Last year, some friends told me about tons of XP mods. As usual, I first read and learned. What I found did not make me so happy : pure illegality, no way to decide which softwares to install, bad tweaks, stupid nlitement, eye-candy before functionnality, branded computer name and workgroup name and no documentation, only 'this is good'. Therefore I decided to start my own. If I has to sum up the project in two words, these would be legal and modular. The project relies on: HFSlip nLite WIHU I prefer HFSlip over nLite because slipstreaming is its main feature (it is permanently updated and checked for this) and it can integrate things such as DirectX (a post-install would be >25MB), Windows Installer... For me WIHU wins over WPI because it has some features I need (user-related and computer/workgroup names), runs at T-12 (1), INI format editing is easier to automate than for xml, has an interface I like, doesn't rely on anything else and so on (but that's just imho). The idea is to give people a place to download MS's updates, a 'lastsession.ini' for nlite, an 'install.ini' for WIHU and tons of apps. The whole thing is multilingual (nearly done with it) and of course, everything can be modified (how do you want to maintain something noone can change ? ) Some facts and figures: -all critical updates except MDAC SP1 slipstreamed, plus DirectX 9.0c October 2006 (on all OSes I mean, not only XP SP2), Windows Installer 3.1, Flash 9 -I386 size after nlite : from 130MB to 150MB -$OEM$ size for WIHU : 250MB, probably more than 120 apps that can be auto-installed and auto-set -documentation is coming, 'code' is commented and tidy What I have to do before releasing: -some apps are not really multilingual (remember, I'm french) -have to ask some people if I can redistribute their work -must not forget studies (I work from 8a.m. to 10p.m.) What I have to do after initial release: -start asking opensource devs what they think about me reditributing their work for such a project (I'll respect their decision) -finish documentation (->DokuWiki) and apps comments (reasons why install such app) Is anyone interested in such a project ? I'm not asking for contributors at the moment, I just want to know if there's a point finishing what I mentionned earlier in this post and releasing it publicly. Otherwise, I'll keep this for my friends (my work won't be lost anyway). (1) I may reconsider running WIHU at T-12 because if ran later on, installations may be (much) faster, but I also want my tweaks to be applied to default_user... (Seymeline)

WIHU only runs *after* windows is installed (or when it is fast installed). As far as I understand your problem, WIHU has absolutely no use for you. Sorry.

Dreamweaver... *arghhhh* edit : 2000 posts. opening Notepad++ now Already feeling better.

http://www.ocaml-tutorial.org/ A pleasure to read. Et en français aussi. I hope I'm not the only one learning (o)caml.

I'll get a new computer as a replacement for my old laptop that was defective. Do you think it could be shipped with nlite ?

Indeed : search for "installer" on this page