Thread: XP UltraLite (0.1.0a) - It Begins...

does this actually remove anything? When I try to remove anything no matter what it is I always get an error saying "Runtime error '13': Type mismatch" I click ok and xpul is crashes

Nice work, as for bugs, I'm getting the following,

Runtime Error 13 Type mismatch (pops up in a window)

The app crashes once I hit ok.

It takes close to 2 minutes to load or conduct an analysis (don't know if this is just the way it is or if it is slower on my system)

It would be nice if we could resize the component removal window. Many of the entries are are only partially visible (complete entry does not fit in the window width).

A running count of the size of all components selected would be helpful so we can gauge how much space we stand to gain by removing the selected components.

Auto changing units on the component size (i.e. greater that 1024 bytes - 1 kb etc) would be nice too.

I'm really looking forward to experimenting with this tool. Great work guys.

-momanz

I think using the XPe database info would be more valuable right before making the nLite ISO rather than in post-intallation. I took an inventory of all the files in the I386 directory and used that to get the info from the DB. With that info we could modify the nLite intall even further by editing the setup files. I only tested one component so far just to see if it worked or not and it seems pretty straight forward. Getting to the right registry entries is pretty easy since the hive files are named appropriately. My old app also queried for a list of components dependent on the component you want to delete that way you can see if it'll break anything. That might be useful in your app as well.

sorry for the noob question but this does work on Windows XP PRO right? im running SP1

I think using the XPe database info would be more valuable right before making the nLite ISO rather than in post-intallation

I don't think there's really a difference. The data file I create for Odyssey obviously uses the destination information for the components. It just seems like, no matter what you do with nlite, there's always a bunch of stuff that can be deleted post install.
The two apps combined should allow for the smallest possible install. I don't think it can all be done just pre or post install.
As for depenants, you're right on the money. That's part i'm looking into now.

Come to think of it, I only have XPe SP1 installed on my system. I had trouble installing SP2 after I formatted my system.
Sorry everyone. I'll try and get that figured out tomorrow and post the new files.

Well, the difference would be that by removing the components before installation it would create an ISO pre-configured to be as "lite" as we want. It would also make for more fine tuning needed for projects like ours. A lot of the stuff left over after nLite can easily be removed using the resources data from the XPe database and all it takes is simply commenting out a few lines in the proper files so the components aren't installed at all.

I just did a few more tests removing some of the LDAP stuff and a few other small components. The only thing is that some drivers share common inf's so it's not always possible to get rid of them, but at least the sys files can be removed. It'll be interesting to see how small we can get an installation.

Well i'm also getting Error 13 'Type Mismatch'.

EDIT: To be more specific i found it does it when removing [ Windows Logon (standard) ]. It removes some components, then reports 'Type mismatch' on the Windows Logon component.

EDIT: 'Windows Picture and Fax Viewer' & 'Users Control Panel' are a few others that casue the error.

You shouldn't remove Windows Logon otherwise your system won't boot anymore, but that's not what's causing the Type Mismatch. It's gotta be some dependency that is missing or is a different version than what they used in development.