fdv

ratba_tardly what happens when you type d:\sp\i386\update\update.exe /? i KNOW this sounds insulting, but often when a service pack does not slipstream, there is either a typo (not the case here) or the files are not in the directory they're supposed to be in. your windows 2003 files are in D:\i386, right? your expanded service pack is in D:\SP, right? i am sure you would have checked these things, but just in case you did not, make sure on those.

rat-astardly, i have not developed IE removal for XP or Win2k3. i suppose i would gladly do 2k3 some day but i just have not had the time yet. anyone is of course welcome to apply my information and make their own fileset for XP or 2k3. i could host them if necessary. as for yzowl, what he posted is an addition to HFSLIP that implements what you request -- adding ASPI. the instructions are in the first few lines. HFSLIP is open source and tommyp is not the least bit uptight about suggested mods, additions, changes (he might not implement everything, but examine the code, you'll see he does adopt input from users here). unlike, you know, other software offerings who don't want you looking at their source

hey gents, as i suspected, the IEXPLORE copy problem had two possible solutions: 1. remove the copy file from IE.INF 2. comment out IEXPLORE.EXE in TXTSETUP (and LAYOUT too). as Oleg_II has tested, option2 works fine. i'll file that away for when i get home and update the fileset. COM and DTC -- the OS should install without any BSODs without them. I am finding generally that there are very few apps that need these (apparently, not even MS Office?) anyway, my ADD-COM BAT file can add COM and DTC later if a user wants them. i guess i'll leave them out by default next time. fdv, who is still in washington...

dirtwarrior, we've gotta see your ERROR_REPORT.TXT, zip it and upload and we'll have a look. as for what happens to the files in i386, they are replaced.

a stripped down version of win2k powered the xbox. it was not an out of the box product, but the os did come from win2k. that's why people tend to answer this question with "Windows 2000." whether that is true any more (that it is best) is not a call i am qualified to make as i'm a MAME guy

hi saugatak and Oleg_II and crash&burn, thanks for the info. saugatak: no, this is a normal error message, just click okay and process explorer will run on the second launch. i do not removing debugging, it is not installed by default in windows -- the user has to install it manually and since process explorer will work without it, it's a waste of space. the error has nothing to do with my fileset.

hey gents! this is unsubstantiated rumor, but Bart L. of BartPE project was busy doing some work for the german computing magazine C'T. here is the rumor: he is doing or did a version of BartPE for them and microsoft got on his case again. the rumor is that they are going to do a new, fresh round of legal attacks on BartPE. although Bart will, i am sure, successfully defend his work, he might have to take it down if micro$oft decides to do battle, so it might not be available for a little while. get it while it's still up: http://www.nu2.nu/pebuilder/ again, i might be full of hot air here, but microsoft threatened him once and he's still up, but the forums where he and others post (i dont have the link) does mention whispers or micro$oft jumping on him all over agin. so, take this with a grain of salt, but definately download BartPE as soon as you can, it is an AMAZING utility! BTW Oleg_II and saugatak thanks for the recommendations of my files. you two and obviously many others here are perfect examples of guys who "get it" -- techy enough to understand how my stuff works, and wise enough to appreciate simplicity (and being able to see the source files with full comments, because learning the guts benefits everyone and moves this whole project forward) so dirtwarrior i know you have checked out my screenshots, etc... and of course i am going to be biased and recommend my own fileset (laughs) the only think i can't promise is a pretty interface like XP (or the sexy look of xpero's interface project for xp). i could include DLLs with all sorts of icons if there were enough demand i guess, but i am such a fan of old-school windows nt 4 that i never went in that direction, so that's the only thing i really can't promise you. if someone wants to make a DLL of flashy XP style icons, i would link to it on my site for folks to use if they wanted though. but you are on the right track, wanting to use win2k, IMO. it's easier to clean up (and doesn't try to be "helpful" to you with adding a few extra steps to things that are simple in win2k, adding dozens of services when i turn most off by default, making easy things hard like simple filesharing, moving icons for you automatically without your asking, cluttering up the start menu, forcing terminal services on you when RunAs works for 90% of what you want to do, throwing wizards and dogs at you, etc ) as an aside, many of you know that when tommyp first contacted me, his project was only slipstreaming IE6 (this was about a year ago). my thought then was 'well, i'll link to his thread, but since i do the opposite by taking ie out, we won't really have much to offer each other (LOL)'. thanks to tommyp's hard work (98% of the project) and my INF writing and random tips here and there (2% of the work), here we are it's great to have a forum filled with folks who spend the time to read, debug, and make suggestions instead of whiners who refuse to read instructions Oleg_II yes, please comment them out, it was a slip on my part if uncommented! i was rushing i guess. BTW, still no headway on that IEXPLORE.EXE copy error as i am away from home and no ideas have really struck me on that. yeah... i think i might have to force-install it inside of another INF. maybe its not multimed. maybe it was ACCESSOR, which i did comment out? anyone know what exact file it is? saugatak wanna work some of your process explorer watching? maybe its lots of files... see what i mean though, you change one little thing and windows setup process just does really weird things...

oleg_ii had this also. not sure whats going on there; i think a problem with my own INF. have a look at the INF too, maybe you'll see an error i didn't? you're not -- its the test fileset, remember its not final... tommyp thanks for the note on fixing the volume with MULTIMED*.INF. saugatak these should be removed already (well, wordpad will be... defrag is now only one line in SYSSETUP to comment out; editing TXTSETUP is no longer necessary. correct. should i remove them, do you think? many thanks, i need to build a list and this forum's my fave place to do that well, we'll leave that out, because i think we all know what type or program that is my version of this INF only alters the default behavior. i disable because its a security risk. i will look into writing an INF that can maybe maintain security and still allow WSH to work unimpeded. that's definately the hope -- remember this is a test fileset to work bugs out. i cannot overemphasize how flaky windows can be when twiddling around with its setup files. Crash&Burn as oleg points out, this is a recommended dll, not removed. if you dont find it in TXTSETUP, then it isn't part of windows! (even if i remove something, i will always comment it out so people can see whats getting removed). i would believe M$ has simply overlooked this. i install this file separately with HFEXPERT, personally.

i have read also as suryad that ms has warned users against this binary. BUT. if you REALLY want to try it... put it in the HF folder and give it a name of an XP hotfix. this will "trick" things. of course, this faux sp3 has to be in the form of an EXE file. this is not recommended, and HFSLIP is set up to prevent people from going too wild -- which means that we don't really want to support questions having to do with things HFSLIP really isn't meant for (in other words, yeah, it CAN do this, but we are not saying you should, so if there are problems, we warned ya).

TAiN - allright, thanks. Oleg_II and I have tried it. So far it works and has things removed people asked to remove and a few additions people asked for. I am mainly looking for compatability problems. Running without COM and trying out some of the major packages would help out. BTW general info, I will be available less next week because I'll be travelling on business but will be popping in nights (washington dc time). Thanks all for help on this next version.

Oleg_II, i have a strong suspicion that the file is corrupted, or gdkehl once ran nLite on the source as you note might be a possibility. if nLite has ever been run, it probably ran driver integration and merged his CABs.

gdkehl - welcome aboard. please post your ERROR_REPORT.TXT file, zipped. also, there is no need to use an older version of HFSLIP (Oleg_II, version Oct 17 is not a beta, it is a compatability fix based on Oct 16th to work with my new fileset. 99.9% is unchanged. the only change was fixing "ACCESSOR.IN_" so that HFSLIP looks for "IE.IN_" in FDVFILES.) i don't know if you mean you replaced the i386 folder in SOURCE. don't. leave SOURCE unmodified. also, as Oleg_II points out, something appears wrong with your DRIVER.CAB. be sure to recopy it from CD. the released version of HFSLIP does nothing to this file, so something is wrong with the original file, it would seem.

allright, good to know, thanks saugatak. perhaps to prevent problems, uncomment the COM and DTC lines in SYSOC and try that. i am more interested in getting the other stuff ironed out anyway right now.

This set is a preliminary to see how it works out. www.vorck.com/data/test-set.zip This is important: to use this fileset you need to: 1. download the files, expand into FDVFILES 2. download latest HFSLIP, a minor compatability fix with my files was added 3. run HFSLIP October 17th version, tell me how it goes 4. you probably have HFSLIP Oct 16th, so check step 3 5. thanks to tommyp, oleg_ii, and saugatak for all sorts of help it works fine for me. Here are some changes. help files removed wordpad and converters removed POSIX subsystem removed OS/2 subsystem removed all bitmaps removed reference to hticons commented out of HIVECLS.INF optional components like accessability removed all accessories like clipboard and packager removed, except for CALC and PAINT APCOMPAT.INF removed ACCESSOR.INF removed defragger files removed from automatic installation in TXTSETUP DFRG.INF has been rewritten to install Defragger separately (not installed by TXTSETUP any more) MSHTML.INF has been rewritten to install MS HTML and Help system AU.INF has been rewritten to install auto update, but needs MSHTML.INF SHELL.INF has been rewritten to install a shortcut that's actually useful IE.INF now installs an internet explorer dummy file IEXPLORE.EXE dummy file Copyright Johnathan Howell of datafreak.org. add/remove windows components has been added to Accessories a few things i have to leave in for fileset users: MDAC, COM (COM, DTC have been removed from this test set to see how things go). a lot of my fileset users need these components for all sorts of obscure stuff as well as MDAC for databases... which i need too... so for sanity's sake, i am leaving this. as for COM and DTC, i guess that's up for you folks to tell me since i probably don't run all of the apps you do P.S. hey! how's everyone doing on the logo contest???!!?

WSH.INF - you will have to continue to delete this file Menu Groups in SYSSETUP.IN_ - done Defrag - moved to a separate INF. to remove it, comment out the dfrg.inf line in SYSSETUP.IN_ Accessibility - shortcuts removed SYSOC.IN_ - COM and DTC will be omitted for now, but i need more data! MDAC - i am a heavy database user as are many fileset users (not on MSFN), so for my own sanity, that's staying help files - 99% gone (some are left in TXTSETUP and LAYOUT to avoid 'file not found' errors when installing some drivers. because these files end in 3,3 they are NOT installed by default. trust me on this.) cleanmgr - gone wordpad - gone welcome - gone (no one wanted to replace it with something?) kept - notepad (i havce used LOTS of replacements and they tend to screw up my INF files due to their handling of linebreaks you will see that sometimes, INF files are left though the files are gone. this is so i can easily replace an INF file's contents if i want to and have it install without suddenly remembering "oh crap, i forgot to uncomment it in TXTSETUP!!!" 0s/2 and POSIX - gone

actually, commenting out just the CAT from these 3 files should leave DTC alone, i believe. if the file is commented out of SYSSETUP, windows won't think it needs a CATalog file, and will, i think, install DTC anyway. as saugatak discovered of course it doesnt seem to make much difference. (ahh, quickbooks, bane of our existence)

well, let's do a runaround the problem. 1. open SYSSETUP.IN_ 2. find [ProductCatalogsToInstall] 3. comment out DTCSETUP.CAT with a semicolon 4. open TXTSETUP.SIF and LAYOUT.INF 5. comment out DTCSETUP.CAT with a semicolon in both 6. save and close them all i don't know what the cause of the problem is, but this should take care of it for now.

1. put this in an INF somewhere: HKLM,"SYSTEM\CurrentControlSet\Services\Atapi\Parameters","EnableBigLba",0x10001,01,00,00,00 like in a HIVE*.INF. 6. autopatcher is fine but if you want to install a complete windows that is slipstreamed, go here.

acrobat reader all versions work without problems. acrobat 7 (the program acrobat, not reader, but acrobat) does not work without ie. acrobat 6 (the program acrobat, not reader, but acrobat) works fine without ie. i don't know yet how to trick it as i have not had time to waste screwing around with adobe's products either their creative suite (well, indesign and photoshop) doesn't need ie, yet acrobat does. something's screwy.

no, DCOM is disabled by default. everyone who has been using my fileset (since 2003 in fact) has been running without DCOM an excellent question. Oleg_II just gave me some reworked files. i took out POSIX and OS/2. i just punched up MSHTML.INF and am about to remove wordpad and disk cleaner. i'd say, give me til thursday. i know how much it sucks to wait believe me gotta put the dummy IEXPLORE.EXE into IE.INF now. WSH.INF is windows scripting. delete WSH.INF from FDVFILES and use the default Windows INF and it will install.

hey dirtwarrior, beforehand. then run hfslip and then nlite last of all. we will make this clearer a little later when we work some things out. i don't want to put it into the documentation just yet, i have some things to figure out yet.

s.p.a.m net - what Crash&Burn is talking about is this: i typed the hotfix URL and the board software automatically changed it! i guess a filter for certain urls is in place because perhaps someone from that domain tried to do some spamming? i am not really sure but i fixed the url... (i'm not sayin' how!) it's only for reference and i'll be taking the link down in a little bit, because i am sure that even though the filter is a well-intentioned move against spammers, it's probably there for a reason to prevent any traffic to their site, and i don't want to mess with what the mods have decided is a good idea.

all, i have recieved permission from jonathan howell to redistribute the 'dummy' iexplore.exe that loads whatever browser you choose. it will be in my next fileset. not all related to internet explorer, really more to do with what you see in my posts, and other mundane things nuhi did not want to get too heavily into eradication like i do. he prevents the ie files from installing, but nlite isn't meant to clear out the registry, keep urls from loading in explorer, or apply security fixes like closing ports, etc. its just not that kind of proggie. i am pleased that my fileset is working with nlite (it didn't used to in previous versions) but its aim was really always something different than nlite. to be honest i think that even though i link to nlite in several places, this is a key reason why my files remain very, very popular -- some prefer to do things in 5 clicks, and some very knowledgeable people like to get deep into windows and see everything up close.

For those unfamiliar... the site: http://www.thehot...0;.net/sp3.html the backstory: http://www.pcworld.com/resource/article/0,...,RSS,RSS,00.asp

for my own edification. uses info listed here among other places. btw, i will not ever disable MDAC by default, sorry, i need it, and yes, i know it can be downloaded here. it's easy enough to comment out of SYSSETUP.INF. anyway, can folks give me some personal experience with COM and DTC? it's easy to comment these out in SYSSETUP but i am curious and it's time for a simple thread detailing what relies on just these two windows components. Requiring COM (Component Object Model) System Restore Requiring DTC (Distributed Transaction Coordinator) Microsoft SQL Server Microsoft Message Queuing Microsoft Exchange Server