jdeboeck
Content Type
Profiles
Forums
Events
Posts posted by jdeboeck
-
-
you can remove iexplore.exe and clean up all the shortcuts, but explorer.exe will still be able to work as a browser, because the mshtml dll's are still there. You would have to cripple windows to get that out.
I can't tell how WindowsUpdate or hotfixes or IE6+ setup will react when IE is missing. They may do what they should do and copy updated files. Or they may choose not to and not copy files that aren't presently installed. It depends on some switches inside the hotfix/setup INF file.
0 -
dosnet.inf is only used during setup from windows... maybe your cd only supports installaing from cd boot... if so don't bother about dosnet.inf, its not needed for cd oot install
0 -
I am currently working on new batchfiles for a small Windows XP SP2. A lot of new things will be removed (such as servicepack localization, language groups, 16bit dll files, sounds, scsi boot drivers, slipstreaming leftovers wmp8, moviemk ...) and I am confident SP2 will turn out just as small as SP1
Some features I plan to include:
- Do everything from a single batchfile, requiring user interaction
- Separate file lists from the actual program, for easier modification
- Remove individual components, without removing the group
- Remove files for installation from windows
Please let me have your suggestions, ideas, improvements...
0 -
first of all they are not icons, they are 13x13 bitmaps. there color is logically anded to the color of the menu (if the menu is white you'll see their actual color, if the menu is dark gray, the bitmap will show all dark and colorless)
and finally it can only be done with a shell extension dll, just like winzip and winrar. You can't easily do it yourself. There is an all purpose shell extension that you can customize to your needs though... try google "context menu extension dll"
0 -
I have the same thing in my registry but no virus or problems.
(also on xp sp2 rc1 btw)
0 -
pci express graphics cards are expected to launch in may, so the new mobos and cases should too. I'm not sure about 64bit intel, it might be limited to the xeons in the beginning...
ATI chipset has a cool feature... if you plug in an ATI video card, you can continue using the onboard video and have THREE monitors
, anyway ati has an integrated graphics core which you won't be needing...The sis 648FX is single channel memory and the 661FX as well but with integrated graphics. From SiS I would only go for the 655FX, which is I believe somewhere inbetween i865 and i875 performancewise. Forget the i848 all together.
EDIT: the boards that say 3DDR actually mean 3x PC2700 or 2x PC3200, the chipset can't handle three fast memory sticks apparently
EDIT: i think you need a pair of identical memory sticks for the dual channel memory thingy
0 -
sound like your ready to spend some cash there... If you buy desktop components now I'm affraid you wont be able to upgrade anything later on.
AGP and PCI will be replaced by PCI Express. Next generation Nvidia or ATI will still be released as AGP cards as well, but its PCI Express after that.
The socket 478 is maxed out at 3.4Ghz, anything higher will be on the LGA775 socket. Those new mainboards will probably be BTX form factor, so they won't fit in the ATX case you buy right now. And then there's DDR2 around the corner...
Or should I just buy you one of these
http://www.go-l.com/desktops/index.htm
(I'm kidding - stop dreaming)
EDIT:
If you have to buy right now I'ld go for Northwood 3.0/3.2/3.4 HT on a Canterwood 875P mainboard, with two 512MB sticks of PC3200... Two sticks because the chipset has a dual channel memory controller. You won't feel the difference but you'll see it in benchmarks.
I see no reason to buy the newer Prescott 3.0/3.2/3.4, what speed it gains from the extra cache, it loses due to the longer pipeline.
0 -
the components that are hidden are hidden for a reason. Some don't have uninstallers, so you can show them, but uninstalling them won't remove anything. Even though the component may be marked as not installed afterwards.
0 -
weird, my list only includes the commonly known [Components] not CoreFonts, CoreSounds or anything else that is not in the sysoc.inf structure
EDIT: and I doubt this would actually work in winnt.sif... for instance zipfldr.dll is copied during textmode setup, and registered from syssetup.inf... so its always there. Media_Utopia is a known mistake, its documented by MS, but simply isnt included. Is anybody else seeing this list ?
0 -
media player 9 and directx 9 will probably be integrated
everything in sp1 and all post SP1 hotfixes will be there
bluetooth and pentium m support
improved firewall, new security center
0 -
check the XP Minimal install thread i started....
http://www.MSFN.org/board/index.php?showtopic=10497
its about removing components and drivers BEFORE windows setup
save space on your CD, really remove messenger (not just hide the link)
0 -
dos anybody know how to remove "Tour windows xp" ?
you can remove the files
pro_*.*
xpth*.*
tourw.*
tourstrt.*
this will save you about 15mb on your xpcd, remove them from dosnet.inf and layout.inf as well.
I just don't know where tourstart.exe is added to the start menu, and what makes it startup in the system tray when you start windows
0 -
Just some things I discovered...
SysOc.inf contains a list of optional windows components to be installed.
For each entry there is "the component_name" and "component.inf" in the [Components] section.
I guess you can use all of these "component_names" in your winnt.sif under [components] but only a few are documented in ref.chm, others are
AutoUpdate = Off
Fp_extensions = Off ; frontpage extensions
msmsgs = Off ; messenger
commapps ; dialer, chat, hypertrm
IEaccess = Off ; IE link
OEaccess = Off ; OE link
netfx= Off
msnexplr = Off
Some of the "component.inf" files have an [OptionalComponents] section, and the subcomponent names in here can be disabled in winnt.sif as well.
spider = Off
hearts = Off
I only tried this for a few components but it seems to work. There are also options for installing Freestyle (media center) en .NET (netfx) in here but i guess these are not for xp pro...
I guess you could also check all the inf files referenced from sysoc.inf and delete the files they copy from your xp cd. also remove the filenames from the inf and dosnet.inf and layout.inf
0 -
I wanted to start building my own theme, but StyleBuilder only allows you to modify the values of an existing style. Not much else.
In the msstyles file i found a series of textfiles, which you can extract and modify any way you want. I found that if you leave parts out, like say remove everything about buttons. You will have a visual style with old-style windows buttons. Or you can set background images for controls that dont have them in luna.msstyles.
Removing styles from everything but windowframes and startbar seems like a good midpoint between a fresh look and performance...
0 -
right, we know the driver is certified and we understand why its no longer certified when we modify it. this is probably just what dell, compaq are doing to the drivers anyway, except that they can get the result certified again.
if you like messing with inf files, you can also remove the registry keys about driver uninstallation, which i find to be plain unnecessary; or toss out anything you dont like installed along with your driver, such as control panel applets, autorun stuff, system tray icons...
0 -
i'm sorry if i dit not see your line about "without hassle"
0 -
I had the same problem with my GeForce4 420 Go..
What I did was modify the .INF file from the NVIDIA Drivers (NV4_DISP.INF i believe) This will make your driver uncertified to start with.
You will also need you old drivers .INF file. Open it and look around in it. You will find a series of strings near the end ([strings] section), one of them is the name of your driver. Besides it is a code (something like NV4_GO_420.Desc). You will find the same code near the front of the file (something like %NV4_GO_420%).
When you have found it in the front of the file you will notice a PnpId on the same line, it looks like (PCI\VEN_1039\SYS_2382\SUBSYS_439847). This is how your hardware identifies itsself.
Now go to the .INF file of your new drivers that dont show as compatible. Rename the GeForce MX driver you want in the [strings] section to Geforce Go and modify the corresponding pnpid in the beginning to the PnpId you found on your old driver.
NOW: this should do the trick if you 'update' your driver. Windows will find compatible hardware, newer version and install it automatically and all will be well. I have tried homemade this driver for an unattended install and it all went wrong.
Although the driver was installed, windows apparantly chose an incompatible refresh/resolution combination for my laptop. I'm not sure what went wrong exactly, but i could not get anything better to work than 640x480x16colors (not 16bit)
Feel free to try it out, but beware your unattended installation may fail. Let me know if it doesnt though
0
XP SP2 slimming batchfiles
in Unattended Windows 2000/XP/2003
Posted
patience young finnish...
I will be removing things from intl.inf, such as the indexing files, nonwestern fonts, and msagent done right. But because intl.inf is a lot more complex than most others, a batchfile will not make foolproof modifications: don't try to install what you removed here. I will also be removing services (thanks to nuhi for the idea there) and indexing service is on the list there as well, along with about twenty others.
I see a lot of strong feelings for the volume control: you guys know you can just put sndvol32.exe in $OEM$\$$\SYSTEM32 and it will work just the same...