Clint

If my memory aint fooling me I beleive there is a util that you can drop in your source when installing OS that will allow you to display high resolution. I believe it was an small executable that you simply dropped in the rot and then called upon. Anyone has a clue? Thanks!

Never mind, I took a different approach to it...now solved.

When I run the Runonceex.cmd that comes with the latest WPI in win2000 no entry are applied in Runonceex....in XP it shows up alright... Code looks like this: cmdow @ /HID @ECHO OFF for /f "delims=: tokens=1" %%i in ("%~dp0") do set drive=%%i: set wpipath=%drive%\wpi SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx REG ADD %KEY%\999 /V 1 /D "%wpipath%\WPI.hta" /f EXIT I've run it on a W2K SP4, and still nothing happens...no entry..nothing. ...do the SET KEY and REG ADD commands not work now suddenly?? ..am I still sleeping?

Yes, I did look around a bit...saw something that caught my eye.. For example in ZZZZZ_TOTAL_REMOVER_IE.REM I found that INETCPL.CP is removed, but within that control panel extension resides network connections settings and windows internet program choices...so they goes as well. Correct me if I'm wrong here..but do we not need that...oh well, just a reflection. Not really needed to discuss here

Sure, I've read them both from top to bottom...lots of info, but not what I'm looking for right now

I have spent a couple of hours on documenting exactly wich textbased files (SIF, INF, INI, CMD and so on) that is changed or replaced by nLite. I'm about to make a list on each file and what line is changed/moved/deleted and such. Because I'm working on my oldie that has been altered by an old nLite version I think I better make a documentation of a XP source that has been altered by either the latest nLite or any of your choice. Personally I don't touch the newer versions of nLite..(nor the older either) so I need input here. What should I use and how heavy should I go on the removal in nLite? Perhaps removal of all components available in nLite would generate the biggest source of documentation? I don't know, but I think that is the best way to start. When I have that input a documentation should be done in a few hours I do NOT consider this reversed engineering or infringment of any rights...simply editing textbased files when trying to get HFSLIP working properly can never be that. Nor am I trying to crack nLite or anything...ok? That said, input welcomed.

FDV fileset, which removes IE and a bunch of other crap in Win2k, editing registry and IE cleanup. Not sure how it compares to what you do for IE removal, but FDV's fileset is very stable. I've installed lot of programs with FDV fileset and only had problems with programs that are IE dependent. http://www.vorck.com/data/sp5files.zip Link to HFCLEANUP filesets and instructions for Win2k, WinXP and Win2k3 Server. The readme in the zipfile contains more detailed instructions. The names of the HFCLEANUP files correspond pretty well to nLite options, but there are a few where I have no idea what's going on, such as the GOSH files. http://www.vorck.com/hfexpert.html#hfcleanup According to TommyP, only the Win2k cleanup set works well, the other two need work. As for hive editing, TommyP will have to chip in. I remember trying to add some reg files into an HFSLIP folder to mod the registry but could never make it work so now I just do it manually after install. That looks nice, there are a few ways of doing things there Thanks!

For the moment I wanna finish of that win2000 that I've left lying around, but the future lies within the x64 2003 family for me. I'm one of those that wil NEVER use Vista due to all it's crap (DRM, TCP and so on..) that comes with it. As we goes towards multiple cores and more "RAM" we non-Vista users will have to get the 2003 machinery going where we want it I will look in my notes and see what I can contribute with, my time is limited these days but I might be of help here and there. I'm gonna try find out what binaries and other possible files that are modified when using nLite, it's not that hard to monitor How does the HFCLEANER procedure looks like? Is it only removal of binaries and editing entries in TXTSETUP.SIF and perhaps DOSNET.INF? Do you have any scripting tools for editing hives as well? The sweetest thing would be a nice script for editing binaries, then we REALLY could get some serious work done...if you look at nLite for example it's kinda sloppy when you have "dead" dialogs and non-working MMC snapins....

Yeah, and if we only new wich binaries... then it would be a piece of cake. It's just so friggin annoying that you can't get a decent word out of Nuhi... Oh, well...I'm gonna dump it then...can't be bothered dealing with that. I might as well do a whole new non-nLite rebuild, but I will pluck bits and pieces here and there

And lookin' better than ever... As far as I know, it's because HFSLIP takes over SVCPACK.INF and because HFSLIP doesn't know what you removed with nLite. HFSLIP assumes you're providing a standard source so it only adds stuff into TXTSETUP.SIF for new things, meaning that if nLite stripped the references from TXTSETUP.SIF for specific files that normally reside in the source, they are not copied over during setup. If I'm wrong or this is incomplete, TommyP should be able to jump in. Yes, I saw that in SVCPACK.INF...and the fact that nLite is removing the whole entry does mess things up..(instead of just mark it with";" as we all do). But that would still allow SVCPACK.INF to run (HFSLIP owned) because the Nlite SVCPACK.INF (nLite owned) did run before.. So there must be something critical to HFSLIPS run that has been removed by nLite, or perhaps some dependant stuff in DOSNET maybe...hard to tell. Lets hope TommyP has some more info on this, this must be taken care of..

I'm now back in the game after some absence I'm picking up some old bits and pieces that never got really finished back in the day and are also looking into the HFSLIP and what has happened with it...the HFCLEANER are a very good initiative.. My problem lies in the fact that I have a couple of things lying that has been nLite'd, and I know that it's stated that HFSLIP doesn't like to be run on a nlited source. But please tell me exactly why, I'm sure it can be easily edited if I only knew where and what is stopping the runonce process of HFSLIP. Talking to nuhi is like talking to a wall, the chap has lost it for sure... Thanks!

Yes, HFSLIP is an excellent util!! I've been using it since a long time, perfect for adding updates and whatnot to source. Yes, IE is out...that's one of the first thing that goes.

I do this for fun only, but the fun ends when posting how-to's...because either ppl can't follow guidelines given and then post negative about it...or they rip things out of context...same result. I've posted here before and will not do it again. But I will let you know when it's posted elsewhere. Anyway, the newer versions of nLite will not allow you to remove anything near as much as in the older ones...with that I mean with your own batches and edits. You will end up with a broken install for sure. ..why? ..ask Nuhi

Well, nLite can do just so much for you...it is actually very far from the complete solution. It misses a lot of dead junk, uneeded drivers and dll's...not to mention the sloppy leftovers in dialogs and snapins. My build that I posted info on has better looking UI, updated drivers, a fully working DX9c, modifed XP icons on front....and still are much much smaller and draws less than your "click on everything and now I'm an OS builder" nLiter... oh, I forgot to mention that this is a normally installed OS, no postripping, no regediting (all preedited in hives)...and the ISO is 45MB..so it fits on a businesscard-cd Just plug the disc in and 4min later you have a working OS, User rights, Group Policy, add/remove program, network, DHCP...ALL is working. And I edited the front (desktop, explorer icons) to XP style, so it looks really nice too... ..and it pulls 18MB idle.

ISO 45MB, Footprint 99MB, Memorydraw 18Mb and with DX9c

I'm sorry if it came off as teasing, it was merely some "showoff" I will not drop anything here, too many bad experiences with people taking my things and mess things up. It will get out somewhere as soon as I solved the last small things, only need some spare time

I forgot to mention that this is a normally installed OS, no postripping, no regediting (all preedited in hives)...and the ISO is 45MB..so it fits on a businesscard-cd Just plug the disc in and 4min later you have a working OS, User rights, add remove program, network, DHCP...ALL is working. And I edited the front (desktop, explorer icons) to XP style, so it looks really nice too... ..and it pulls 18MB idle.

Actually nn-step over at XS is the man to look for and he has a couple of things there running, a dedicated Bench OS and a dedicated Boinc/Dimes OS. If you look under Operativ Systems/Windows you will find a couple of threads there. I have dropped a thing called 2003 Appliance Edition in the past that is based on 2003 Web and that lands on 160MB installed, it was made with Game Hosting and FTP Server in mind...so it still has Terminal Services and Remote Desktop functional. The rest is pretty much cleaned out, also some dialogs and dead ends cleaned up. It turned out to be a really good performer. It has been released as an torrent I believe by some group, look and find If you are happy with win2000 I also have something that is kinda awesome, it's a "decent" functional 2000 installation that lands on 99MB! That in itself is pretty good, but the fact that I have ripped out DX8 and replaced it with DX9C directly on source is kinda rare It's still is in progress though, the other projects has taken over and it turned out that win2000 gives somewhat lesser performance in benches compared to XP/2003.

Yes, you are perfectly right Good initiative to try to automate reshack, will come in handy for sure

Actually it can be done, I'm doing a thing together with my friend over at XS. We have left XP due to it's incapabilities with more cores and memory. We are actually fitting a decent functional 2003 Enterprise on a 128MB stick....and I'm sure you know that 2003E means at least 30MB bigger size installed. I guesstimate I could squeeze in XP on 90MB or so. If you utilize SysPrep you can even paste a image on ANY hardware using Acronis or similar, it needs some fixing and doing but it can be done. (has been actually ) btw, nice going on your project...I admire your persistence

Reset your services configuration to default, that will be the best to start with.

After a initial lookover it looks like you have messed up a few entries. these are in shell32.dll already located under [DelRegShell]: HKCR,"CLSID\%CLSID_CDBurn%\%EXTVIEW%\%VID_WebView%" HKLM,"%PATH_EXPLORER%\CD Burning\Handlers" ..not [RegShellNamespace] as in your regsrv32.txt That would make those obsolete then. Look it over, maybe there are more...

Very nicely done, parts of this should ofcourse be taken care of with nlite. Lots of things can be done at "reshacker level" There is a BIG chunk of size to be cut down there, pretty lame that it hasnt been implemented before actually. Loads of unused bitmaps, entries and so on....well, now you are getting there.

There is a util for that here, can't remember where it's at but do use search and you will find answers

Here is a good source: http://www.xtremesystems.org/forums/showpo...341&postcount=1 And while I'm at it: ..pretty good numbers for a 680/1800MHz clock...achieved with a 1.4v mod...