Sp0iLedBrAt

Updated to version 0.7.43 for 32-bit versions

It teaches a man how to fish. Nice little app, that Beyond Compare.

To make a screenshot: open what you need, hit the PrintScreen button on your keyboard, open MS Paint and paste it there. 1. Yes. 2. The Office files need to be on the CD, so they can copy themselves to that file path. Otherwise the Windows install will delete them (while formatting the HDD before installing Windows). 3. We are trying to install Windows and Office unattended, meaning with no work on your part, which means while the install CD is still in the tray, setup will install Windows, restart, begin first logon, install Office, restart. At this point you can remove the CD.

Or install XP to Virtual machine on Win7 and do all your work there (provided you have enough resources) Cheers

One step at a time. Please try to post in the proper forum next time http://www.msfn.org/board/forum/89-nlite/ Look at pic #1 here http://win-x.co.cc/nliteimages.html; do you see that edition of Win2K listed here? It is possible it is not supported by nLite. If you are using nLite, then you have a Last Session.ini file in the Win2000 working folder on your PC; please attach it. When you say , you mean older/newer versions of the appropriate SATA drivers, right?Please report back with this information so we can help you Cheers

Start the application. It will extract several folders. Close it. Put the driver packs in the DriverPacks folder. Start it again. Also point the application to your folder with XP to get additional settings. After that, click Slipstream. That's the simplest method, but you can also customize the other options. The DriverPacks applications can also be localized in several languages. Cheers

The order of things should be like this: 1. you call (through nLite) the batch file from the CD; 2. the batch file calls Office's setup.exe (from the HDD). I was really hoping to avoid all this; that's why I suggested you run everything from the CD Once you start Windows install from the CD, it becomes %source% (meaning the source of Windows). The last post is a bit confusing to me, so I'd ask you to take a screenshot of the folder where your XP install resides (your working folder). If possible, make a screenshot after opening the folder through Windows Explorer (press WinLogo-key+E). I just want to make sure of the proper paths and that $OEM$ is not inside of I386, but next to it. Cheers

You need to download the application for DriverPacks as well http://driverpacks.net/applications/latest. Try and report back if you're having problems. Cheers

You have instructed nLite to run the batch file (batch.cmd) from the HDD (H:\), but the batch file isn't copied to the HDD, so you should instruct it to run from the CD. Try with %source% instead (pic #20 here http://win-x.co.cc/nliteimages.html)

It doesn't matter which HDD you're working from at the moment, what matters is the drive letter of the HDD you will install Windows on. That's where the Office folder will be copied to, so you need to get it right. To use that batch.cmd (as you requested), inside the $OEM$ create a folder $1, inside it a folder install, inside it Applications, inside it OfficeXP. Within OfficeXP copy the Office setup files. As explained, you won't use Office2003, but the other instead, so you can delete it.Cheers

Could it be that they just haven't tested that processor to be able to recommend it? Otherwise, if it fits the socket, why not be able to use it? Cheers

Use this REM Office 2003 start /wait H:\install\Applications\OfficeXP\setup.exe TRANSFORMS=unattended.mst /qn (assuming H:\ is the HDD where the files are copied; If it is C:\, change the letter in the command as well). To modify the command inside the batch file, right-click it and click Edit. Don't forget to save after that Yep. nLite won't touch them; in fact, nLite even creates the $OEM$ folder if you don't already have it, for some of its own operations.As I said, it was very late and I could have overseen adding a few things here and there, but you're getting there Don't forget to test, and more importantly, to report back. Cheers

It's all OK now. I copied the .dll to Desktop (to add it to quarantine and send it to their lab) and Avast! cleaned it right away. As it wasn't deleting the one in System32, I used Unlocker and saw it was connected to winlogon.exe, services.exe, explorer.exe and lsass.exe. After unlocking those processes, it was also deleted and recognized as Win32:Small-DKF Trojan Thanks and cheers

By using this H:\XPCD\$OEM$\$1\install\Applications\OfficeXP you are making the Office folder copy to the system hard drive (C:\) and install from there. What I showed you is a way to install directly from the CD, without copying to HDD, which saves a bit of time. As to how to create a batch file, yes, open Notepad, enter the lines and, after clicking save as..., enter batch.cmd as a title. It is the same one, the one and only Cheers

If you've already gone through ORK (Office Resource Kit), then you almost have a silent unattended install of Office. Now, 1. create a batch file and name it, say batch.cmd 2. Put it in the root of the folder (next to I386) and inside add the following line REM Office 2003 start /wait %Source%$OEM$\Office2003\setup.exe TRANSFORMS=unattended.mst /qn shutdown -r -t 70 -c "Restarting in..." -f and save it. The last line will allow restart of the PC in 70 sec. to allow the applying of all settings. 3. Next to batch.cmd and I386 create the $OEM$ folder and inside it make a folder called Office2003 (no spaces) where the setup files will be. This is all done before you start nLite. 4. In nLite (pic #20 of the picture guide from my previous post) paste this command cmd /R %source%batch.cmd and click Add. That's about it; it tells nLite to run the batch file which will install Office during first logon. I know it sounds a bit complicated, but it's really late here. Take it step by step and you can't miss. Cheers N.B. This procedure presupposes that you call the batch file batch.cmd, the ORK unattended file unattended.mst and the files location is just as described.

To be honest, we don't often come by programming errors in nLite here. Your Last Session.ini is quite simple with no room for errors. Try doing another ISO while implementing the changes I suggested and see if you get the error again. Please report back. Edit: I see you are no longer mentioning the lsass.exe error, so I presume it is now resolved. Cheers

Welcome to MSFN. Give nLite the command to find the CD and copy the files itself to a working folder(if you have copied them manually). Try that first and then report. Cheers

Welcome to MSFN. It is recommended to have nLite copy the CD to the PC in a working folder. Did you try that or you copied the files manually? nLite looks for a directory with an I386/AMD64 folder to copy from. What kind of CD do you have? Cheers

In this picture guide http://win-x.co.cc/nliteimages.html, look at pic #21, the Regional tab (pic #25); this is where you set them. Click on the appropriate Language group and that should be it. If not, also choose English (for e.g.) manually, as well as the time zone. On pic #21, Desktop themes tab (pic #29) to your right, you set the default theme and style. Well, the point is that nLite is for personal use and you create one CD with one product key for use with one computer.As a solution for the other updates, see this page http://win-x.co.cc/updates.html (the add-ons are available for download, and the explanation is in the footnotes) Cheers

Yes and Yes. You can do the copying yourself, or let nLite do it for you, which is recommended. Cheers

And to pick up where GrofLuigi left, there are quite a few ready-made add-ons for IE8 and all versions of .NET Framework on RyanVM's site. You could also download a great tool called "Nonno Fabio and OnePiece Update Pack/Addon Creator INTL" (the file name is DXUPAC.exe) which creates add-ons for many useful applications like DirectX, IE8 (put the IE8 install file and the updates in one folder and it will merge them into one file), Open Office, WMP11, Adobe Reader, etc. I've successfully used many of them. You can also find some add-ons in my signature and loads more here http://www.winaddons.com/nlite-addons I also agree on his note about a clean source; copy a clean source, modify with nLite, create an ISO and test it in a virtual machine. If not satisfied, start all over with a new copy/source. Import the settings of what you did previously from the Last Session.ini file and make appropriate changes until you are happy with it. Cheers

http://support.asus.com/download/download.aspx?SLanguage=en-us The model is listed and there are driver downloads for both 32 and 64-bit versions of Win7. I don't think you'll have any luck with asking someone to upload a utility CD. Cheers

The path HKEY_CLASSES_ROOT\CLSID\{3CD3DEAF-9679-7405-EF14-098E67FFF229}\InProcServer32 leads to C:\WINDOWS\system32\sbvp.dll, which is a small .dll file (32KB), which is not signed (no version) and is dated 29/10/2009 14:06. There is another REG_SZ value Apartment present in the same folder. A google search of the DLL reveals nothing. Cheers

I'm getting this registry path with value data {3CD3DEAF-9679-7405-EF14-098E67FFF229} on startup and it is trying to connect with various system files, such as winlogon.exe, explorer.exe, lsass.exe, services.exe etc. Should I be worried? A google search on "CsGxeNz" reveals absolutely nothing.Cheers

Welcome to MSFN. I'll just give you the really obvious ones: 1. Do not add back-ups of MS files as drivers (there's probably a setting in DriverMax not to back them up). This may well be the reason File Protection was alarmed; 2. Do not rename Windows updates and hotfixes. nLite checks the file version and replaces only with newer ones (so the order is not important at all). Also, use search and find a post by -X- on Windows Media updates that do not integrate with nLite (and how to fix it); 3. Disable this ; people say it exposes some kind of bug in nLite.Now, this is only about nLite. We can't really say what happened later without some kind of a log or a more detailed explanation. Cheers