Achdine

Haha, yeahhhhhh...or you could just turn off that bar by going to the Start Menu properties and turning on "Show Small Icons in Start Menu."Here's the registry tweak for it: [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Advanced] "Start_LargeMFUIcons"=dword:00000000

Edited for...also being wrong.

...I think you need to read the Guide, and try to get at least a basic understanding of the registry, file paths, and unattended cds.

The quote you gave assumes you have a basic understanding of the command line. Edited for being wrong. Anyway, let's break down the quote you were having trouble with: What this means is you're supposed to use the command line to navigate to where the file you want to modify is. You can either do this by "typing in the entire path," for example, CD "%UserProfile%\Desktop\ModifyPE" or by "navigat[ing] to the folder" using multiple CD commands: CD "%UserProfile%" CD Desktop CD ModifyPE "If you have the ability to open a command prompt by right clicking on a folder, that's even easier." This is referring to a tweak that adds the ability to right-click on a folder in Windows Explorer and open a command line directly to this folder. It is the same thing as typing either of the above commands. Lastly, the actual command and modifying the file. Make sure ModifyPE.exe is in the same folder as the file you want to modify, then type ModifyPE.exe <filename> -c where <filename> is the name and extension of the file you want to modify, which will usually be a dll (but doesn't have to be). You should see "No Error occurred, have a nice day" in the command line. If you get an error, please post it here and someone can give you more specific help.

There may be a way to do that, but it's going to waste a sizeable chunk of space on your hard disk, for what's likely to be a marginal speed increase. If you really want to have two versions of Office available for install, I would just make an installer for each, and leave the installer itself, in .exe form, on the hard disk. Put it somewhere like C:\Installers, and maybe even make shortcuts to the installers in a special folder in the Start Menu. Have the shortcuts delete whichever installer is not used.

This is not a "cracking" forum. However, if you have a legal copy of Windows XP and a legal CD key, you can enter it in place of the X's and it will be entered automatically. That's why it's there, and I don't know how that could possibly be any more clear. If the serial is not correct, it will prompt you for a correct one. You cannot install Windows without a correct serial key.

Wow...it looks like you're copying over a ton of stuff to the hard disk. I recommend you just run the installers off of your CD drive instead of wasting all that time (and space) to copy the files. Look at this topic for a wide variety of different ways to find the CD drive as a variable to use in your RunOnceEx.cmd file. For your first and second errors, when I look at the screenshots you posted, there is no "Unattended" folder. Change your install path to C:\Install, and it should be able to find everything. For the third error, make sure that you aren't importing an autologin registry key. Oh, and lastly... The classic theme is wayyyyyy better than Luna

That's his problem Gouki...you can't delete them from %UserProfile% before the user account is created. You could make a little script that executes the first time the new user logs in which deletes the links...but that's pretty messy and annoying. I'll be very interested to hear if someone knows a way to prevent them from being created at all.

;Call this from a batch file to force the window to be on top NirCMDc.exe win settopmost title "Folder Options" 1 ;And this if you want to make it act regularly again NirCMDc.exe win settopmost title "Folder Options" 0 You can find NirCMD here.

NirCMD does everything you could ever want. Ever. This would give you a messagebox with the message "Network Share not Accessible" and the title "Error" NirCMDc.exe InfoBox "Network Share not Accessible" "Error" Also, this would give you a dialog box with "Yes" and "No" buttons, where yes would call your RunOnceEx.cmd again NirCMDc.exe QBox "Network Share not Accessible. Try again?" "Error" "RunOnceEx.cmd" In the same vein, this would give the same message, but when it calls the .cmd file again it would run it without opening a command window NirCMDc.exe QBoxCom "Network Share not Accessible. Try again?" "Error" Exec Hide "RunOnceEx.cmd" I wrote all of these off the top of my head, I may have typoed somewhere, but the idea is there. Refer to the documentation on the website. Alternatively, if you don't want to use a seperate tool you can just use Windows Messenger. The window isn't as pretty, but still gets the message across Msg "%UserName%" "Network Share not Accessible"

ChkDsk (CheckDisk) is a command line utility for repairing low-level hard disk problems. The /F flag just means fix the errors instead of just finding them. You can find a little more info at the Microsoft Website. Since this is the first time you've used this hard disk, I would say it's unlikely that it is defective; it's much more likely that there was a small problem formatting it for the first time. Probably a bad sector just needs to be remapped. There are a bunch of ways you could fix this. You could boot to your Windows CD and use the Recovery Console to run ChkDsk /F, or you could use one of the numerous low-level detect and repair utilities on the 'net, such as SeaTools from Seagate, or PowerMax from Maxtor. Most of the tools are not brand-specific. Also, you could try running the Windows install again and reformatting the disk. I see that you weren't able to enter the setup when you tried the second time, but probably if you change the boot order so that the CD-ROM is first you'll be able to boot to it. I assume what happened there is that Windows queried the hard disk to see if it was bootable before even checking to see if there was a CD in the drive. If you do manage to boot to it, choose the regular format (ie, not the "quick" format) for either NTFS or FAT32, and it will run a checkdisk automatically beforehand. This is the only difference I am aware of between the quick format and the regular format, and would be the first/easiest thing to try.

I'm not familiar at all with the installation of the Novell Client software, so I can't give you specific advice. Possibly if you provided a bit more information on the type of installer, someone here could give you a switch or help you create a transform or something of that sort. The easy/cheap way out of this is with AutoIt. Use the WinWaitActive function to wait for the shutdown messagebox, then use ControlClick to click "No." You can find a lot of example scripts that you can easily modify for your purpose in the AutoIt Scripts Sticky.

Sorry man, I'm not into that.Hotfixes are really, really easy to integrate. Use RyanVM's Post SP2 Update Pack and integrate via NLite if you're too lazy to edit the files yourself. Also, Firefox 1.4 does not exist, and isn't even scheduled on the Firefox roadmap As Zxian said, OpenOffice and the versions of Firefox that exist have been discussed in detail all over this forum. Do a little searching before posting.

To change the computer name: Reg Add /f HKLM\SYSTEM\CurrentControlSet\Control\ComputerName\ComputerName /v ComputerName /t REG_SZ /d <NewComputerName> Red Add /f HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters /v "NV Hostname" /t REG_SZ /d <NewComputerName> Or you can use the ever-handy CompName.exe to dynamically generate and set a computer name. To change workgroups, use the NetDom utility (from the Windows XP Support Tools): NetDom Member "<NewComputerName>" /JoinWorkgroup "<NewWorkgroup>" Admin password is almost too easy: Net User Administrator "<NewPassword>" You could just code those into a batch file with a few prompts, and you're good to go (look at this topic for some help with user input) Alternatively, you could use WISCON, BryanH's Windows Initial System Configurator, which can do all of that for you, in a nice little GUI that you can run from CMDLines.txt. Hope this helped!

1. Create the task on your computer using the Windows Task Scheduler. 2. Copy <taskname>.job from %WinDir%\Tasks\<taskname>.job 3. Put <taskname>.job into $OEM$\$$\Tasks\ That should do ya for.

If it looks too much like an error to you, try adding a comment to it (shows up in the Message section of that window). Just add a -c switch, and the comment you want to show. REG ADD %KEY%\015 /VE /D "Finalise & Reboot Computer" /f REG ADD %KEY%\015 /V 1 /D "shutdown.exe -r -f -t 60 -c \"Finalizing installation process. Please wait while your system reboots.\"" /f (On a side note, at first I thought you misspelled "Finalise," but Dictionary.com actually lists both "Finalize" and "Finalise." I think it's more common to see it with a z, however.)

You did a good job remembering to remove your serial the first time, but forgot about it the second time

You need to put a [ CODE] statement at the beginning and a [ /CODE] statement at the end of what you want selected (remove the space inside the brackets). The end result looks like this

That's correct, assuming Windows is installed on the C:\ drive. More info about the $OEM$ folders is, of course, at the guide. There are other ways to copy files over as well. I have some large files that I copy over by making a cab or 7zip archive beforehand, then using Extract.exe or 7za.exe, respectively, from the commandline with the path to extract. This is only really worth it if the file/files are large, and it looks like most of yours are not, but I figured I would throw it out there. Also, keep in mind that if you're trying to bypass Photoshop activation by copying over the dat file (that's what it looks like, I'm just guessing), the file is hardware specific and will only work on the PC it was created on.

First of all, I'm going to assume you mean RunOnceEx, not RunOnce. They are slightly different, to quote Alanoll, I can't help you with RunOnce or RunOnce\Setup, but RunOnceEx is easy enough.There are any number of methods to implement it, although by far the most common is a simple batch file. All you're doing is adding the data to "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx" in the registry, using numbered subfolders to indicate the order. You can get more help on the batchfile method of implementation on the UnAttended Guide and by typing "Reg Add /?" into a command window. Once you understand the concept and the method, you can try using Eagle00789's RunOnceEx creator to create the batch file for you.

This is not entirely correct. While many people do use CMDLines.txt or GUIRunOnce to implement the RunOnceEx method of installing programs, you certainly do not need to do it this way. The RunOnceEx method is popular because it's easy to install multiple programs and since the data is stored in the registry info can be added at a number of different times during the install.However, you can actually install programs at CMDLines.txt just by calling the installer. This is not the method that I use, but to the best of my knowledge you don't have a User Profile loaded yet, and it's possible that the installer may require something in it and fail to install. If you have VMWare or Virtual PC you should be able to just test all your programs and see if they can be installed at this point. GUIRunOnce is run (at the same time as RunOnceEx) right before the desktop loads on your first login. The only limitation to installing with GUIRunOnce and RunOnceEx is that the user will need to be an Administrator. All users created at the OOBE screens will be Administrators, so you can log on to any one of the accounts that you created. It is best to actually integrate the hotfixes into the installation CD, so that they are included in the install. There are several easy methods to do this:1) Get RyanVM's Post SP2 Update Pack, which includes all the hotfixes and whatnot you should need. You can integrate it manually (instructions on his website) or with NLite. 2) Download all the hotfixes you want to integrate and use IcemanND's integration script to integrate the packages.

++And it's even easier if you use LaptoniC's Silence of the Foxes to make the Firefox installer; just put them in the plugins folder before you compile everything.

You could have tried looking for it: http://unattended.msfn.org/global/downloads.htm It's right at the top.

That's the Shutdown Interface. It comes up when you use the -i flag on the shutdown statement. Very handy when you're doing remote computer stuffs, but you definitely don't need it for a UA installation.

It sounds like you are using WPI, so you may want to create the shortcuts in the start menu according to what the end user chooses to install, rather than put all the possible shortcuts in the menu. You can use Shortcut.exe or NirCMD to create them using the command line.