homiebrah

StyleXP modifies the uxtheme.dll in order to allow unsigned, third-party themes to be used. Not real sure what you're looking for, but here is something that will allow you to create your own themes: http://www.tgtsoft.com/prod_sb.php

I would imagine its because %userprofile% is mapped to the currently logged in user. Try using "c:\docuements and settings\all users" ...

That way will work, but if you include your profile settings when creating the .mst file, you won't need the second command line.

Read the ref.chm file located in the deploy.cab file. It will be in the Support\Tools folder on your CD.

Have you tried rebooting in safe mode and tried to remove any suspicious apps? Also, this topic is needs to be moved, as it does not deal with Unattended installs. NOTE: Norton is not a sure-fire way to catch everything that comes across. Use a combination of anti-virus, firewall, and spyware remover. And be way of websites when using IE, as they like to use ActiveX to install little nasties in the background. Another good source would be the task manager. Check it out and Google the processes you see running for more infromation.

I sense some confusion here. Try this: 1. Download the Office 2003 Resource Kit. 2. Install it on your machine. 3. Configure your Outlook exactly the way you want it to. 4. Run the Profile Wizard to export a copy of your settings. It will save itself as a .ops file. 5. Run the Custom Installation Wizard, using an administrative install of Office 2003. 6. Sometime during the process, it will ask you about your profile. You can create a new profile, or import a settings file (that .ops one you created in step #4 above. The steps above are used on an administrative install of Office 2003. If you just install Office the normal, unsilent way, you can use the Profile Wizard to restore your settings. In the same window as you would export your settings, click the radio button to restore a .ops file. Hope I didn't confuse anyone.

If you use the Custom Install Wizard, you will be able to specify your email accounts. You will still have to manually enter password, though. Your accounts are located in the following registry location: HKCU\Software\Microsoft\Office\Outlook\OMI Account Manager\Accounts Export this key and have it merged using cmdlines.txt.

Try changing your cmdlines.txt file to this: [COMMANDS] ".\RunOnceEx.cmd"

Amen to that. I found the correct location for it on GreenMachine's site. http://greenmachine.msfnhosting.com/READING/cmdlines.htm

That's correct. I run five commands from that .txt file and neither worked. After adding the .\, it worked like a champ.

Did you create an admin install point for Office 2003? If not, then you will need to. http://unattended.msfn.org/xp/officexp_advanced.htm

I had to put a .\ in front of the command: [COMMANDS] ".\runonceex.cmd" At the same time, I had regedit open watching to see if it dropped into the right key.

You need to use the Profile Wizard, which comes with the Office 2003 Resource Kit. http://www.microsoft.com/office/ork/2003/tools/default.htm Additionally, you can use the Custom Installation Wizard to create a silent install of Office, which can incorporate your profile settings.

Notepad or any other text editor. Make sure when you are saving the CMD file, it is done with a .cmd extension. Notepad will default to .txt files, so in the Save As Type box, you change it to all files and put in the name of the file with a .cmd, i.e. mainbatch.cmd.

http://vortex2050.dyndns.org:8080/

Increase your AutoLogonCount. With it's current setting, it will auto login once, then prompt from that point on.

DELETED.

This should be moved to the Application Switches forum. WinRAR: http://www.msfn.org/board/index.php?showtopic=12657

First off, namimg the driver folder does not make a difference, as long as it matches what is specified in winnt.sif. As for placing the .inf's, all you need to do is make sure that all of the files for a particular device are in the same place. For instance, I have an nVidia GF4 MX440 card. The driver set I use is installed using InstallShield. Using WinRAR, I extract the setup.exe to the folder: $OEM$\$1\drivers\video. In my winnt.sif, I made the entry specifying that location. During the hardware detection phase, it installed those drivers. For my MB, I did the same. I extracted the setup.exe, and moved the onboard LAN and audio drivers to their own folders. EDIT: Now I see why you asked this question. But, maybe it should be confined to this thread, as it refers more to it than this one originally did. http://www.msfn.org/board/index.php?showtopic=19931

Break your drivers down into sections, i.e. Audio, Video, LAN, USB, etc. Then, copy the corresponding drivers to those folders. $OEM$\1$\Drivers\Audio $OEM$\1$\Drivers\\Video $OEM$\1$\Drivers\LAN $OEM$\1$\Drivers\USB And so on. Your winnt.sif file should have the following entries in them: [unattended] OemPreinstall=Yes DriverSigningPolicy=Ignore OemPnPDriversPath="drivers\audio;drivers\lan\;drivers\video;drivers\usb" If you're still not sure, post the MB info and I can check out the driver package for you.

Create a batch file called office.cmd and save it in the same directory as cmdlines.txt ($OEM$). Enter this line in office.bat d:\office2k3\setup.exe TRANSFORMS=d:\office2k3\Unattended.MST /qb- d:\office2k3\ will be the location where your Office files are. In this example, I have an administrative install point for Office 2003 on my separate D drive. This command will work for Office XP as well. IMPORTANT: make sure that the command above points to YOUR install point, not mine. Then in cmdlines.txt, enter the following command: [COMMANDS] ".\office.cmd" At the T-13 stage, cmdlines.txt will run office.cmd, which will in turn run your unattended install of Office.

Click the link below and read the information. It will get you started. It will work for Office 2003, as well. http://unattended.msfn.org/xp/officexp.htm Where you put the command is entirely up to you.

I received the same error message when running the following commands straight from cmdlines.txt: "rundll32 setupapi,InstallHinfSection XP 128 runonceex.inf" "rundll32.exe iernonce.dll,RunOnceExProcess" The location of runonceex.inf was in the $OEM$ folder, but it was not being read for some reason. The second command generated the error message you saw. To fix it, I modified the path of the first command by adding a .\ in front of runonceex.inf and having both command run in a .cmd file called upon by cmdlines.txt. It ran flawlessly with no errors. I would check your command lines for any quote, if you are running it the same way. I'm not sure if the quotes in cmdlines.txt drive the two command crazy or not.

Stupid question, but did you check the extension to see if it is .sif and not .sif.txt?

Autologon is specified in the winnt.sif: [GuiUnattended] AdminPassword=********** AutoLogon=Yes AutoLogonCount=99 There is no difference in MDAC between 2K and XP. Syntax is: ENG_Q832483_MDAC_X86.EXE /C:"dahotfix.exe /q /n" /q