homiebrah

I'm trying to find a script that will convert the current date to the three digit number for the year, i.e. Jan 5 would be 005, etc.

Really didn't feel like it. Reformatting a hard drive six times a day does not bother me. How the hell else can we learn? I only use Virtual PC at work on our Enterprise network, preparing our XP client migration. My home PC was bought was research and destruction.

No sweat. I think I pulled an all weekender when I first started messing with unattended installs. Fried a lot of CD-Rs before getting some RWs.

The only "zip" of hotfixes would be the SP1 Rollup package. However, it does not include all known hotfixes/updates for XP SP1. My advice would be to download the rollup, run it, reboot, then run through Windows Update to see what was missed. Here is a list of know hotfixes, as of May 04, put together by GreenMachine: http://greenmachine.msfnhosting.com/XPCREATE/current.htm Tidbit on getting these updates installed unattended: http://unattended.msfn.org/xp/installhotfixes.htm

If I'm not mistaken, Corp keys have a PID of 640. Something else you can check is the setupp.ini file in the \i386 directory of the XP CD. Look at the PID. It will identify the type of key you need to use.

Then post your winnt.sif file, minus your product key. And before anyone assumes anything, it is common to mistype a product key when using setpmgr. I've done it before.

What flavor of XP? Home --> ProductID=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx Pro --> ProductKey=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx If an invalid key number is in your winnt.sif, it will display the Product Key dialog box during setup as well.

Well, I figured it out. Guess I had to make my registry entries prior to the final discover process. Working like a champ.

That is the general idea. I figured out what I did wrong. Some of my smaller apps work fine. The larger ones need the .msi and accompanying folders that get created. Now I'm working on WinInstall seeing the registry entries for Dreamweaver that point to my serial # and sites.

I just recreated the path. Removing it from 84 systems was too much work for me to do in a day.

It does use InstallShield. I was trying to create an .msi of it. As for a link, it can be found on Macromedia's website. The file is too big to send via email. Just something I was playing with.

Would be nice if I could get it to work with Dreamweaver MX. Keeps asking for directories. And the .msi is only about 1.77MB in size.

A CD was never used. It was an admin install point that got moved.

Using InstallRite for Office seems like a bad idea. Office has its own custom installer tools. That would seem to be the best way to go. But to each his own. I've used the Office Reource Kit. I was trying InstallRite out to see if it would work, which it does.

Why not just make one CD for each computer?

Got a question for the masses. We had about 30 users install Office XP from a network location, call it \\server1\offcexp_usethisone. We were forced to move the software to another location , called \\server2\officexp. When the users go to install SP3, it makes the call home looking for the installation source. Since \\server1 is not around anymore, they tried pointing SP3 to look at \\server2. It tells them that these are not the proper files and refuses to continue to install. Is there a way to modify the registry to point to \\server2?

InstallRite works great with most programs. Only ones I have problems with are games over 1GB. Handles Office well also.

Ultimate Fighting Championship. Last I heard, they were up to that number.

Our country has lost one of it's greatest leaders today. http://www.foxnews.com/story/0,2933,121883,00.html

No holds barred. He should try out UFC 1,012,559.

http://www.google.com/search?sourceid=mozc...ysprep+switches

Yes, it would help to post those documents.

Why not add it to winnt.sif prior to installing?

uxtheme.dll for XP SP2 versions: http://vortex2050.dyndns.org:8080/reposito...e/Windows%20XP/

The product key is asked for during Setup. Until it's entered, booting to the desktop will not happen. Adding the key in winnt.sif bypasses the prompt during setup only.