Thread: XP System Builder

Originally Posted by SFiorito

Hmmm... I'm guessing it's a security issue. Laguna, is your account part of the admin group?

Yes it is In fact, I am loggin on using Administrator account.

I finally got it working.

I installed the database into sql server 2000 and made sure it was configured for windows authentication. Voila!!! It works. Now i just a list - if possible of the files that must not be deleted (like the logon one etc).

I must say, this is going to be a long ride. Lets see how small we can get it.

yeah, I just uninstalled SQL Server 2000 and reinstalled the DB using the included MSDE and it keeps giving me problems. I'll try to figure out what the deal is.

BTW, it seems the file attachment was removed from my original post, but when I go to edit post it's still showing up???

SFiorito:

Could you, PLEASE, re-attach the "XP System Builder" file?

Thanks, Pavel

Okay, here's the deal: seems MSDE (MS Data Engine, basically a neutered MS SQL Server) doesn't come configured to use named pipes by default. Most likely for security/admin reasons since it's meant for single-user and local databases. So anyways, check C:\Program Files\Microsoft SQL Server\80\Tools\Binn for an app named SVRNETCN.exe. Use that to add Named Pipes to the list of protocols. Close that app then restart MSDE using the services control panel (MSSQLSERVER is the service name). Then restart XP System Builder.

If, for some reason, you don't have that applet then you should be able to simply import these settings into your registry:

Code:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\SuperSocketNetLib]
"Encrypt"=dword:00000000
"ProtocolList"=hex(7):6e,00,70,00,00,00,00,00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\SuperSocketNetLib\Np]
"PipeName"="\\\\.\\pipe\\sql\\query"

simply create a text file in notepad, copy & paste, save as whatever.reg, double-click. restart sql server.

do you happen to know of some files which are not to be deleted. Obviously ACPI has to stay and certain other obvious ones but are there any ones that must not be deleted?

cheers

SFiorito

This software works great, but I have a request/recomendation if possible!

When removing components like graphic card drivers, it is very long winded to keep double clicking each item and then click remove component.

Would it be possible to have a tick boxes next to each item in the tree and then click remove item once at the end. The process can then scroll through the list and find the ticks and then remove the component!

Thanks

Rickster

yeah, that's one of the things I've been meaning to do. and a settings file so that you can automatically remove stuff you removed in a previous CD. but the best thing to do is use this after nLite. I use nLite to get rid of most of the stuff and then use this to get rid of all the left over items.

I can confirm it works btw, and it works very well. However, mankind always wants more, so here is my feature request : some way to check dependencies file-by-file..ie a search box where I can check the various components that depend on "foo.dll" and "helloworld.exe"