fdv

If you want to make a win7 hotfix list and stay committed to it, sure. As with others, you have complete free reign in making it however you like, then email it to me when the monthly patch cycle happens. You have leeway but try to be timely (within that week). Right now there may be win7 lists elsewhere... but trust me, in no time at all, they'll simply die. It seems odd but my site is the only one I have EVER seen that tracks 2000, XP, and 2003 hotfixes and keeps them current. Every other list I have ever seen stops dead at some point.

2003 Server fileset updated. You have to figure out where you want to go with this, I guess. It's a versatile OS; personally, its more useful to me with the maximum of stuff in it (except for true garbage like MS Outlook). Just to see where I could go with reducing based on what I know, I did a 275mb (see graphic). nLite ain't got nothin' on that -- believe it. But of what use it? That would make a great embedded music player for my car, maybe. I expect to reduce 2003 further and make it more flexible by putting more files into components (for example, in TXTSETUP, all of the IE files would install in SYSTEM32 because they have = 1,,,,,,,2,0,0 after their filenames. If you switch this to = 1,,,,,,,,3,3 and call the files from the separate IE.INF, then IE has become componentized -- it only installs if IE.INF is called by SYSSETUP. I did this for my XP fileset -- look at TXTSETUP and LAYOUT). Anyway, expect periodic updates. I feel like addressing a topic from another thread: 99.9% of forum participants are gems. But if you act like an a** about what I choose to spend time on, you're not speeding things along any. I wouldn't drop what I was doing out of spite, but if you're tempted to get on my case about something -- fine, but a gentle tap on the shoulder goes way further than acting demanding.

Let's say you do. Then in a month you try to install hotfixes... and they won't install, because they look for a specific build number. What good has this version hack done? You've only prevented yourself from patching your own OS.

I will need to do more work on 2003 to offload IE from TXTSETUP and fully into IE.INF. I didn't get around to that. Same deal as my XP fileset. Send me an email tomorrow to remind me to update 2003. I have not yet compartmentalized IE yet but do have some other fixes. How is powershell installed? INF? Need more detail.

In order to prevent future confusion here I "fixed" this by removing the extra driver calls. In other words, re-download the fileset. Remember, if you want to get rid of IE in the XP set, you must comment the IE.INF line out in the SYSSETUP file.

Build a MAME version that runs your favorite arcade games? MAME is now quite large if you download precompiled binaries so you'll need to roll your own. I am personally a Galaga fan and have a MAME I compiled with just a few cores in it (nothing after the 90's) and it ran on my crappy little notebook on Win98 great (the notebook happened to have a TV out RCA jack, which made it even better!)

The install routines run detection and don't see an actual, valid, full install of WMP9? That's what the installers actually do, but that's just a guess as to why these hang.

As others have said -- difficult. Depends on what you want back. I created, and have somewhere, an Outlook restorer (for example). If you post what you want back you might have someone tell you how to do it. (If it's COM, MDAC, DTC, etc then you're out of luck, those are way too labor intensive.)

Two things. One, you might be in luck in some sense; MS released a few critical fixes for NT4 after its EOL. It is possible however that since the NT and 2000 architectures were similar that it wasn't terribly much to ask of MS. Two, the real problem -- there isn't a lot of similarity between XP and 2000 and so hotfixes for 2000 really cannot be ported. As an example, I don't know how true this is though, MS issued TCP protocol stack hotfixes for all OS's -except- Win2000. Someone will have to help me find the KB, but MS made a note that they essentially weren't going to go through the effort since the threat was deemed minor, not critical. But it does point to the problem that 2000 is different enough from XP that porting fixes would probably not be something that's doable. Unfortunately, because I agree it's a great embedded OS at this point.

(board posted twice)

The URL contains a slang term for "to urinate" "top issue" parses like "to p?ss" ;-)

Remove C:\Users\Public\windows hotfixes\IE8-WindowsXP-KB976662-x86-ENU.exe C:\Users\Public\windows hotfixes\IE8-WindowsXP-KB980182-x86-ENU.exe C:\Users\Public\windows hotfixes\WindowsMedia11-KB929399-v2-x86-INTL.exe C:\Users\Public\windows hotfixes\WindowsMedia11-KB939683-x86-ENU.exe C:\Users\Public\windows hotfixes\WindowsMedia11-KB954154-x86-ENU.exe

No. Instead, open HIVESFT.INF find "Time Zones" Delete all the crap there add this If you want to just use it right now, add it to an INF file, etc etc etc etc etc etc etc. timezones-for-hivesft.txt

With what, Internet Explorer?

bphlpt has great advice for you. I'm in graduate school, I work (in IT!) up to 10 hours a day, I have two young kids at home. Lots going on. There are other guys on MSFN that gave up their projects because of a lot less -- "just" getting married or "just" having a kid. And, of course, just as Tom does, I work for "free" (at a personal cost only to me). So, yeah. It's probably something you can file under don't really care. I'll get to it, but I'm kinda busy ATM, and it's something I'd last worked on AGES ago. So it's not like the material is fresh in my mind. I have to go back and retrofit 2000 Pro material to Server and I thought it wouldn't take so long. I was wrong, it will take some time, and it won't be as thorough as 2000 Pro was. It will be more like my 2003 set that I just released a few days ago and linked to in another post. Traveling to NYC tomorrow until Monday then working late Mon-Wed so I will not be able to look at any of that for a while. It's complex, my friend. It's not just deleting files referenced in INFs like nLite. It's careful testing and a LOT of isosizing. When most guys around MSFN have a fire under their chair they take a do it yourself approach. It IS possible if you edit SYSOC and SYSSETUP and work to compare my TXTSETUP files. If YOU want to do it, I'll host it. Otherwise it's a waiting game since no one else would use it, it's had maybe less than 20 downloads in years, and I'd be doing the work essentially for just you. So I'm putting out a welcome mat for you to give an assist. This is something I'll have to do largely from the top down all over again. So you will no doubt understand why I am in no rush and do this catch as catch can.

Windows Server 2003 Notes: feel free to do your own editing. If filecopy says that there is a file missing, it is up to you to edit TXTSETUP and LAYOUT so that it's commented out. I made this set from files that I use and there is no guarantee that I didn't put a file in that I forgot to edit back out for this set. To add or subtract components, use: expand -r sysoc.in_ expand -r syssetup.in_ Make your edits to the INF files and save. When done, del sysoc.in_ del syssetup.in_ makecab sysoc.inf makecab syssetup.inf Windows XP, updated Notes: updated to 2010 timezones Windows 2000, updated Notes: updated to 2010 timezones

I actually do have a little something, but it leaves a lot in, because I like a middle ground (lots of functionality). The best thing to do might be for me to put up some basic files and let you guys go from there. I'll get back to you on this.

Trustee, the Spanish was only for you since your English is rusty So you download this, put it in HFSLIP, and run the binary to check if all hotfixes are present. I think one should probably do this BEFORE running HFSLIP, not after. (Antes de, no despues de).

Agent Ransack is a free version of FileLocator Pro. FileLocator integrates 100% into the search function if you choose. Agent Ransack installs in the context menu as well as the Start menu right under the Windows search. I prefer Ransack muhself.

Interesting, but where do I put it? Does it run on HF? We need instructions. ¿Interesante, pero donde debe ponerlo? ¿Funciona en el HF? Se necesita instrucctiones.

We have fully transitioned to a new maintainer (bristols) and the 2000 hotfix list is back in operation. At this point we have maintainers for 2000, XP, and 2003 and all are fully up to date. http://www.vorck.com/windows/hotfixes_2000.html http://www.vorck.com/windows/hotfixes_xp.html http://www.vorck.com/windows/hotfixes_2003.html

New IE cumulative's added for 2003 and xp in the lists, and 2000 as well. (Muppet, I got you covered, since this was sprung out of cycle) There will be an announcement regarding the 2000 hotfix list shortly.

Hi all, because Tom and I stopped using 2000, the updates to the 2000 hotfix list here have stopped. We keep XP (courtesy of Muppet Hunter) and 2003 (by me) active of course, but we don't want to let the 2000 list go too long (the list stopped in January 2010). Remember, End of Life is only a few months away. It would be nice to have someone finish this up until MS stops issuing updates. You can modify the existing layout however you wish (as you can see, my 2003 list looks radically different from 2000. Make it how you like). Any takers, reply here and PM me so I am 100% sure to see your post. Thanks FDV

Try the nLite forum, not this one http://www.msfn.org/board/forum/89-nlite/

Blackviper is still the go-to guy for this data. Here's where you need to see: http://www.blackviper.com/WinXP/servicecfg.htm