SlimShady

Ofcourse I saw that schedule. But as he said: I just wanna know the status and in which week it'll be finished.

How is it going? Is it almost finished? I'm going to start playing with nLite after that I'll create a new XP Pro CD. I was just wondering: When do you think the new version is finished? You don't have to tell us what day exactly, give us a week number.

I made the list and I tested once. Results: - Three hotfixes were not installed or not found (by me) The file contains only hotfixes that were succesful. XPCTHLST.TXT

Allright. Downloading/finding all the hotfixes will take time. I have work to do so I will do it this weekend and post the XPCTHLST.TXT file.

I didn't understand the last part. Do you mean I have to do this (download hotfixes) on a clean install of XP?

I'm going to do the Dutch version... I was wondering: should the hotfixes be in one folder or should they be placed like XPCREATE wants them? Thank you for this great application.

, we're all human. Human make mistakes.

An alternative way to enable the quicklaunch bar. Save the following text in a textfile and save with a .vbs extension: Dim WshShell, objShell Set WshShell = WScript.CreateObject("WScript.Shell") Set objShell = CreateObject("Shell.Application") objShell.TrayProperties WScript.Sleep 1000 WshShell.SendKeys "%q" WshShell.SendKeys "~" Set WshShell = nothing Set objShell = nothing WScript.Quit()

I don't understand what you mean by Is it something illegal or secret? (sorry, I'm just curious)

I recommend PowerArchiver, Microsoft does too.

FDISK isn't included in WinXP. WinXP has diskpart.exe. Look for it in your system32 folder.

Tip: If you want to find your tweak instantly, search for it on http://www.TweakXP.comhttp://www.winguides.com/registry http://www.google.com I bet you'll find 99% of the tweaks you want.

I think you can leave this out: DEVICEHIGH=A:\NET\DLSHELP.SYS

Don't you have to enter the full path in a command? I mean this: Replace .\registreerwinzip.reg with the full path.Maybe that'll help. BTW: Or, did you miss-spell it, and it should be: "registerwinzip.reg"? Perfect translation . But I don't think that's the problem. Good luck.

Maybe you should get rid of the quotes between the password... You could create a new batch file and test each command line. Good luck.

You can find it here It's a registry key you can change.

C:\>COLOR /? Sets the default console foreground and background colors. COLOR [attr] attr Specifies color attribute of console output Color attributes are specified by TWO hex digits -- the first corresponds to the background; the second the foreground. Each digit can be any of the following values: 0 = Black 8 = Gray 1 = Blue 9 = Light Blue 2 = Green A = Light Green 3 = Aqua B = Light Aqua 4 = Red C = Light Red 5 = Purple D = Light Purple 6 = Yellow E = Light Yellow 7 = White F = Bright White If no argument is given, this command restores the color to what it was when CMD.EXE started. This value either comes from the current console window, the /T command line switch or from the DefaultColor registry value. The COLOR command sets ERRORLEVEL to 1 if an attempt is made to execute the COLOR command with a foreground and background color that are the same. Example: "COLOR fc" produces light red on bright white Above command you can use in batch file or manually in a dos prompt. If you want to make it the default color: start REGEDIT browse to this key: [HKEY_CURRENT_USER\Software\Microsoft\Command Processor] double click on DefaultColor enter the color as mentioned above (the two characters) export the key Good luck!

I didn't see which date you posted that issue. When I see/read issues that I have experience with, I post the solution. And... No problemo

You need to complete the 'verysilent' switch; C:\path_to_application\program.exe /VERYSILENT /SP- Optional: /NORESTART Good luck!

I haven't tried it yet, but it looks perfect! Exactly what I needed

I can't answer your question, sorry. But I have a workaround: - Copy the contents of the ASCII XML file - Create a new textfile - Paste the content into the file - And save as Unicode

Yeah. But it's still a great tool. The best thing (and the idea) about this tool is: - You can import user-specific settings. Because it's alot of work to do it differently, this is perfect because you only need to write one command line. Perfect!

I think this is a stupid question... Say there is a user called Jim. During the unattended install you want to import some settings. (During cmdlines.txt) So, if I: - create the user Jim with password (During cmdlines.txt) - use this tool to import some settings for the user But the the user has never logged in before. Would it work? edit: typo

Do you have any idea when this service pack will be officially available?

??What is this supposed to mean?? It kinda sounds like you are insinuating that you have some "inside" information that non-legit copies of xp are gonna crash hard drives? Yeah, I read that too... Can you inform us....