jrzycrim

After installing to a virtual machine, I pinned all the items I wanted to the start menu, logged off then back on, and then exported this key: [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\StartPage]

For my computer: [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\HideDesktopIcons\NewStartPanel] "{20D04FE0-3AEA-1069-A2D8-08002B30309D}"=dword:00000000 You can search the forums for quick launch. It's been done to death...

You're welcome. It's nice that they don't use up a lot of space.

Along with placing the font in the Fonts directory, you have to add your font here: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts] "Font Name"="Font file" I think you can even add fonts that reside some place other than the fonts directory if you give a full path to the file.

Try ProductKey instead of ProductID. nevermind, was looking at the wrong winnt.sif...

The recovery console has nothing to do with repair installs. The recovery console is just a utility that loads from CD which lets you access your system; it's useful if you can't boot from your hard drive for whatever reason. An unattended CD does not give you the option of doing a repair install. You could just make a regular CD with SP2 to use for repairs. I've heard you can make a pseudo multi-boot CD which will let you choose between a regular install or a unattended install. So far, I haven't found any threads which contain details on this.

Just place it in $OEM$\$$\System32\ Or you can just copy it from somewhere else or extract it from an archive. Just as long as it ends up in %systemroot%\system32.

It installs the recovery console onto your hard drive. It does add an entry to your boot menu. Making a CD unattended does away with the Recovery console option. You can always use your original CD if you need the recovery console. What kind of boot error are you talking about?

You also might want to add the /dudisable switch. That will disable dynamic update and keep setup from trying to connect to the internet for updates while installing the console.

You might still have a problem from within vmware. See this thread: http://www.msfn.org/board/index.php?showtopic=23429&st=20

I believe it's the Update Rollup (826939) that contains the new kernel.

First thing to check is that you haven't actually named Winnt.sif as Winnt.sif.txt. It's a common problem when saving from notepad or other text editors. To check, you should make sure that 'Hide extensions for known file types' is not checked in folder options and then look at winnt.sif in the i386 directory. Although this shouldn't account for the reason your unnattended installation is asking for your information, you should remove the one you don't want. That determines whether your OEM drivers and programs get copied over.

I haven't tested on my unattended CD since I don't install anything that requires it. It should work though... Hopefully rootfixxxer will let us know if it does.

Did you ever get this to work?

I use the 'ChromEdit Extension". It adds 'Edit User Files' to the tools menu and allows you to edit Chrome.css, userContent.css and user.js. http://cdn.mozdev.org/chromedit/

Check out the last post of this thread: http://www.msfn.org/board/index.php?showto...=0entry115068

If I remember correctly, XPCREATE compresses SVCPACK.INF. It's in the I386 directory as SVCPACK.IN_. You could just expand it (expand -r SVCPACK.IN_) and edit that. You might want to make a copy to work with. After your done with editing, you'll need to delete the old SVCPACK.IN_. Wonder why it was deleted from Newfiles... Do you endup with the log file and DOSNET.INF?

No problem. Feel free to post any other questions. Good Luck

That should be OemPreinstall=Yes. That would explain why your files are not being copied over.

It just struck me as funny...

Hello, war59312, First, post your entire winnt.sif. Use code tags when you post it; makes it easier to read: [code] text here [ /code] Don't put the space in the end code tag. Second, cmdlines.cmd should be cmdlines.txt Third, where exactly did you place your $OEM$ folder?

*lol REBOOT=REALLYSUPPRESS When your really serious about suppressing reboots...

In your winnt.sif, make sure you have AutoPartition = 0. [Data] AutoPartition = 0 MsDosInitiated = 0 UnattendedInstall = Yes

After installing Firefox and setting up my extensions and other settings, I 7zipped the Firefox directory and my profile directory and exported the Software\Mozilla keys from the registry. During setup, I just extract everything back to the proper place. When I launch Firefox, all my settings and extensions are intact. The only thing I left out was the Cache in the profile directory although I did include an empty folder named Cache in my archive.

You could place a a self deleting batch file in each user's startup menu that imports the appropriate settings.