greywolf83

So, I've been using AveDesk for my icons (and hid the desktop icons), and I've gotten used the idea of 64x64 or bigger icons, but since AveDesk doesnt really represent what is currently in my desktop directory, I've decided to try and get XP to do the job for me. I was hoping to size up the icons to look better, but when I use the Desktop Icon Size in XPize Settings (or manually in display properties), it seems to resize everything on my Start Menu and other places too. Is there any way to upsize icons ONLY on the desktop? Alternately, if you are familiar with any other program that replaces the desktop icons (I've looked at all the widget program and have yet to find a solution that dynamically shows what is in my desktop folder, so when I download things to the desktop, they actually show, to my knowledge AveDesk and Yahoo/Konfabulator and Object Desktop don't do this. Anyone have any general tips for getting my Desktop icons to look great? Thanks everyone! Rob

I think I'm going to leave it on the drive (by removing the cleanup.cmd entry). I just have the network installs for on-demand deployment, mostly of other Office apps like Visio and Project, but the suite is up there too for reinstall purposes. Thanks. Anyone have a more realistic fix, let me know. Custom Installation Wizard should have SOMETHING.

So...after many hours of working on an Unattended DVD, I finally deployed it on a computer here at work. I have it installing a custom installation MST of Office2003 Pro (volume liscence) during RunOncEx.cmd. The cleanup.cmd deletes the installation source afterwards. The problem is, I deployed the computer to a user. I logged on to thier domain user account, and opened Outlook. It popped up with the installing MS Office crap...instead of its usual dialog asking you for settings it gave me an error and said it couldn't find the network installation source. A box with only one option "C:\install\Applications\Office2003" came up. All of the crap in the install folder was deleted during cleanup.cmd. So I copied the Office2003 disc off of our network (should have been the same exact MST and everything) to that directory. It gave me some sort of error and quit out. I tried this as an Administrator and it didn't even do the install thing, it went directly into Outlook. I eventually uninstalled Office 2003 and reinstalled it via a networked drive. Any ideas on how to avoid this? My only thought is to hold off on the automatic deletion of the install folder until the computer is deployed. Or maybe switch to RunOnceEX from DVD.

By the way, many of the PCs I am installing this on will be laptops...no floppy drive. I'm sure there is a solution that will run from CD alone.

The process of creating a WINNT.SIF is well known to me. It is not a viable solution for my deployment. I am creating a CD that will be installed on MANY computers. Using the WINNT.SIF method, when I install it on 50 PCs, they will all have the same product keys and name. Not a good thing. Any ideas? Please don't assume im a total n00b. I have read the enitre MSFN unattended guide.

I'm setting up an unattended disc to be deployed on all kinds of machines, and I need a way to input the product key and pc-name before the installation...This way I can insert the information and walk away and return with a fresh install of XP, instead of waiting for it to ask me somewhere in the middle. Any ideas? Thanks!

Bump...anyone?

While testing my Unattended Disc, I installed Windows Update to check to make sure my hotfixes were correctly installed... and to my suprise (no critical updates found last week, same disc) I got a new critical update, Genuine Windows Validation Tool. I installed it see what was up. I think this is part of the new M$ policy of forcibly making you validate before you get updates. Anyhow is anyone getting this on Windows Update? By the way, I have yet to integrate Windows Update, all i've done is hotfixes. I'm looking for a method to integrate this new tool as a hotfix with svcpack.inf. If this can be accomplished, all you'd have to do is set up auto-activate to make this disappear completely.

Okay, so I am using GuiRunOnce in Winnt.sif. [GuiRunOnce] Command0="rundll32 printui.dll,PrintUIEntry /in /n \\MHFSERVER\TOSHIBA" When I tested this, it correctly added to the domain, and the printer, but on first login (which is automatically going to the Administrator account which is obviously a local account) it asked me for my credentials to connect to the printer. Is there any way to get windows to automatically grab my credentials from somewhere? Thanks, Rob