more removals will follow.
Would it be possible to put a comment in the batch file relating it back to the list in the images. There's a couple of things I want to keep, but am not sure of exactly in the batch file.
Actually, come to think of it. I'm going to write an application that will do all of this with a GUI. Kind of like the way nlite does it, but this will be post install.
If you can send me a file with each component's name and associated dlls, or just comment the batch file, I can take it from there.
What do you think?
Sweet idea, I was planning the same thing ... i'm working on the OS side of my install and this would cut a bit of time (PM me if you want to collaborate).
I'm all for giving it back to the people ...
Caputer Mk. II
'02 VX Holden Commodore Series II Executive
MII12000, 512MB RAM, 60GB HDD (5400rpm), 16X DVD, TS200V
Morex 60W DC-DC, Custom S/SDC
OS/Software: Developing...
Well it would be pretty hard task to do component by component, considering XPE consist of about 1000 components. I have another suggestion: Maybe you could try to download XPe, install it and get the list of files (and whats even more important and impossible to do manually - reg. keys) for each components directly from its SQL database?Originally Posted by knubile
Talking to the database was my choice as well.Originally Posted by mpattonm
Score!!! ... I've obtained the information from the SQL database showing the component information, dependencies, reg values, etc, etc. At first glance all the information doesn't appear to be available in the database, or maybe it is all there in the large web of interrelating tables.
I'll make some headway on it in the morning ... Time for sleep
Caputer Mk. II
'02 VX Holden Commodore Series II Executive
MII12000, 512MB RAM, 60GB HDD (5400rpm), 16X DVD, TS200V
Morex 60W DC-DC, Custom S/SDC
OS/Software: Developing...
That's an awesome idea. All that needs to be done is create some data file with all the info from the sql database. Then it can run without xpe installed.
How about I work on creating that data file, and you build the program Odyssey? I'm a C# dude and I don't think having .NET installed as a requirement is a good idea for a program that's supposed to reduce the size of your install.
I can definetly create the data file though, with some research between you and me.
Hey guys, I messed around with the DB a while ago and these are the queries I used at the time:
Code:Get the groups of components: DECLARE @RC int DECLARE @VIGUID uniqueidentifier DECLARE @VSGUID uniqueidentifier -- Set parameter values SET @VSGUID = 'B784E719-C196-4DDB-B358-D9254426C38D' EXEC @RC = [MantisSQLDB].[dbo].[GetGroups] @VIGUID, @VSGUID Get the components in a specific group: DECLARE @RC int DECLARE @PlatformVSGUID uniqueidentifier DECLARE @VSGUID uniqueidentifier -- Set parameter values SET @PlatformVSGUID = 'B784E719-C196-4DDB-B358-D9254426C38D' SET @VSGUID = 'DE57766D-9566-11D4-8E84-00B0D03D27C6' EXEC @RC = [MantisSQLDB].[dbo].[GetGroupComponents] @PlatformVSGUID, @VSGUID Get all the components in the database: DECLARE @RC int DECLARE @VIGUID uniqueidentifier DECLARE @VSGUID uniqueidentifier -- Set parameter values SET @VSGUID = 'B784E719-C196-4DDB-B358-D9254426C38D' EXEC @RC = [MantisSQLDB].[dbo].[GetComponents] @VIGUID, @VSGUID Get a specific component using a VIGUID and PlatformVSGUID: DECLARE @RC int DECLARE @PlatformVSGUID uniqueidentifier DECLARE @VIGUID uniqueidentifier -- Set parameter values SET @PlatformVSGUID = 'B784E719-C196-4DDB-B358-D9254426C38D' SET @VIGUID = '144C08A7-65B3-418F-B04D-5E35684217AB' EXEC @RC = [MantisSQLDB].[dbo].[GetComponent] @PlatformVSGUID, @VIGUID Get the dependencies for a component using the VSGUID and PlatformVSGUID: DECLARE @RC int DECLARE @PlatformVSGUID uniqueidentifier DECLARE @ComponentVSGUID uniqueidentifier -- Set parameter values SET @PlatformVSGUID = 'B784E719-C196-4DDB-B358-D9254426C38D' SET @ComponentVSGUID = 'B7761BD2-B19B-469D-9F43-11A73A53B90E' EXEC @RC = [MantisSQLDB].[dbo].[GetDependenciesByVSGUID] @PlatformVSGUID, @ComponentVSGUID Get the resources for a component using the ComponentID: DECLARE @RC int DECLARE @CompID int -- Set parameter values SET @CompID = 4 EXEC @RC = [MantisSQLDB].[dbo].[GetResourceProps] @CompID
Can do ... for simplicity and rapid development I'll throw it together with VB6 (requiring only the vb6 runtime, mscomctl dll's)Originally Posted by knubile
As for the data file:
I was thinking for each component we should require:
* Files associated (with directory locations, and file sizes)
* Reg entries associated (with paths, types and data)
* Dependencies
I started an example of a data file but can definintely be refined...
What do you think???Code:@Client Printing @Description Blah, blah, blah @Registry Data F:HKEY_CURRENT_USER\Printers\ F:HKEY_CURRENT_USER\Printers\Connections\ D:HKEY_CURRENT_USER\Printers\DeviceOld\ REG_SZ lzhuprn,winspool,Ne00: F:HKEY_CURRENT_USER\Printers\DevModePerUser\ F:HKEY_CURRENT_USER\Printers\DevModes2\ F:HKEY_CURRENT_USER\Printers\Settings\ F:HKEY_CURRENT_USER\Printers\Settings\Wizard\ D:HKEY_CURRENT_USER\Printers\Settings\Wizard\Additional Drivers REG_DWORD (1) D:HKEY_CURRENT_USER\Printers\Settings\Wizard\Default Attributes REG_DWORD (520) D:HKEY_CURRENT_USER\Printers\Settings\Wizard\From Web REG_DWORD (0) D:HKEY_CURRENT_USER\Printers\Settings\Wizard\Local Printer REG_DWORD (0) D:HKEY_CURRENT_USER\Printers\Settings\Wizard\Set As Default REG_DWORD (1) D:HKEY_CURRENT_USER\Printers\Settings\Wizard\Test Page REG_DWORD (1) D:HKEY_CURRENT_USER\Printers\Settings\Wizard\Use Existing REG_DWORD (0) F:\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\ F:\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\Printers\ D:\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\Printers\DefaultSpoolDirectory REG_SZ %51%\PRINTERS F:\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\Providers\ F:\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\Providers\LanMan Print Services F:\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\Providers\LanMan Print Services\Servers\ F:\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Forms\ F:\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\ D:\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\#10 Envelope D:\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\#6 3/4 Envelope D:\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\B5 D:\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\B5 182 x 257 mm D:\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\C5 D:\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\C5 Envelope F:\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\Choukei 3 Envelope F:\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\Choukei 4 Envelope F:\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\Com-10 @Depends
Caputer Mk. II
'02 VX Holden Commodore Series II Executive
MII12000, 512MB RAM, 60GB HDD (5400rpm), 16X DVD, TS200V
Morex 60W DC-DC, Custom S/SDC
OS/Software: Developing...
Bookmarks