InTheWayBoy

Okay, so this is a little funky...I'm setting up an RIS server, and have used the correct tools setup a new image using an XP Pro SP2 disc. I then created a new install image using a new unattended file, in which I edited to suit my needs. Everythings gravy...just like the many times I've done this before. However, I am having a slight problem during the GUI Setup section...it gets to 39 minutes and then prompts me with the Windows Logo error for the Battery! I've never seen this before...I've seen it with other hardware, but not for the battery! It's safe to say that I'm sure I goofed something, but I really haven't done any configuring other than the unattended setup...I'm sure the CD on it's own works great, and I've used the same disc for previous RIS images with nothing like this. I really just want to know where to look...any log files, or were is the actual battery driver that is causing me grief. I'm sure it would be in the I386 dir, but what files relate to this?

You'll have to find a way to convert the EXE install into an MSI install...Group Policy Software Installs can only be done using an MSI. Now you can accomplish this, but I have to say with a complicated application such as Photoshop, it's going to be a very hard time for you. I don't have any links right now, but there are several tools that may aid you in this process. I've tried several times before with lesser programs and usually just gave up...it's a pain in the rear! At least for me...

Also, since it's snapshot based, certain 'extra' packages an installer might need won't be installed. Lets say the Program installs one way on an Intel system, but on an AMD system it also has to add a few extra registry changes to fix a compatibility issue. If you were to run a snapshot of the Intel installation, then when you install the new unattended application on an AMD system it might not work right. That's a very simple explanation...lots of software installs, at least recent ones, configure the necessary install on-the-fly...and there is where snapshots suck. Of course for simple program installations then this works fine!

I just so happened to be playing with a few 922's this weekend...looks like Dell has made their setup routine obscenely too complicated, relying on many scripting functions instead of your standard exe setup. Also note that the setup, in it's original form, WILL NOT RUN FROM ANYWHERE OTHER THAN THE CD! This is probably due to some bonehead coding an adsolute path somewhere, so if it's not run from the root of a drive it doesn't execute. Seen it before, but I thought they got past all that. I know none of this helps, but it at least gives you some more info.

I recently decided to make an AIO CD that has XP SP2 Home, XP2 Pro, and ERD2005. Everything seemed to work fine, and I used Gosh's method to slim down the installs. I then created a winnt.sif, and edited all the files as explained. However, when I would do an install I would get random file missing errors during the text install stage. There was never really any pattern to what files were missing, and I could ESC past all of them to complete setup, but this is obviously far from unattended. After scouring the forums for a few hours I finally came across other suggestions to use a different 'expand.exe' and set out to find a better one. I finally found one in a random post (Sorry, don't have the post ID anymore), and after replacing the old with the new, now everything works fine. I just wanted to post my success with this, so that other people can hopefully use this quick fix. I've included the file I downloaded in the post. Good luck and thanx for the great forum! And just to clarify, you need to download this, then overwrite the version that is the I386 directory of your source files...and after that all should be well if this was your problem. expand.exe

http://www.macromedia.com/shockwave/downlo...=ShockwaveFlash

I really tried to figure this one out on my own, and I have a few Microsoft KB's that might help. Searches here yielded nothing, even for just "cdkey" I'm trying to put together an unattended install for WinXP Home SP2. The serial number I'm using is valid, so I'm sure the setup will work. But what about afterwards? Is there an easier way to changing the cdkey other than registry editing and activation? Any thoughts here would be much appreciated, if only to point me in the right direction. And just to clarify I need to change the cdkey to customers cdkeys, but I want a fully unattended install. Thanx in advance!