IcemanND

No need to change to the system32 directory. And your complaining about getting better compression? nVidia may have used something else to compress it or who knows. All you should have to do is go to the folder that contains the file you want to recompress and enter: makecab filename.ext makecab is in the system path being in the system32 directory so windows will find it. After running the command above you will end up with filename.ex_ in the same folder you ran the command from.

use it from a CMD window. In the simplest form: makecab myfile.dll

Is it any port you plug you iPod and thumbdrive into or do you always use the same one?

This is precisely the reason why I refuse to upgrade from any version of Windows to any other version every since Win 3.1. Something you might try is to bring up the boot menu sometimes you will get the option there to turn off the automatic reboot on BSOD. You may also try booting into safe mode, won't tell you a whole lot but you can check the event viewer and setup log files, and you can turn off the automatic reboot. Is the software installation the same between the gateways and the beige boxes, excluding drivers? I have found that some software, like virusscan products don't like OS upgrades. Also some drivers will cause you issues, especially of the beige box company was cutting corners and building Intel images on AMD or vice versa and deploying via images.

I believe what you are after is makecab.exe in the sytem32 folder.

I have a system with Office 2007 ent. that when any user launches outlook and tries to either create a new message or read a new/existing message the message portion of the window does not render. It is like that piece of the program is hung, if you open a window over it when you close that window whatever was on the display is still in the mail text portion of the window. I had found a post somewhere about office not displaying the customize office box where you put in your name and initials causing a similar problem. But when I log into the machine with an account that was not there before and that box comes up I can not type into it. So this is likely the issue but how do I fix the user info box? I've uninstalled office, made sure all updates where there, tried multiple accounts, it's machine related not account related. Anyone have any ideas?

If you can boot to safe mode you can change your page file settings, both drive and size. With 2gb of memory a 4gb swap file s overkill.

Poorly create INF, but yes that file would have to be there.

Sorry, vmware, had vlite on the brain last night. Processor Check for 64-Bit Compatibility: http://vmware.com/download/ws/drivers_tools.html

vlite has a utility for testing your system to see if you can run a 64 bit guest os on your system. Run it and it will tell you.

Better yet what make/model of laptop are you looking to replace the drive in?

the boot from your xp cd to the recovery console. Once in the recovery console type the following, except what is in italics: c: cd \windows\system32\config md backup copy *.* backup del SAM del SECURITY del SOFTWARE del SYSTEM del DEFAULT cd \system volume information dir /a {you will see a directory that the name begins with _restore follow by q unique ID number replace {guid} in the next line with this id number} cd _restore{guid} dir /ad rp*.* {in the list of directories select the second to last one listed RPxxx where xxx is a number, replace xxx with that number in the next line} cd RPxxx\snapshot copy _REGISTRY_MACHINE_SAM c:\windows\system32\config\SAM copy _REGISTRY_MACHINE_SECURITY c:\windows\system32\config\SECURITY copy _REGISTRY_MACHINE_SOFTWARE c:\windows\system32\config\SOFTWARE copy _REGISTRY_MACHINE_SYSTEM c:\windows\system32\config\SYSTEM copy _REGISTRY_USER_.DEFAULT c:\windows\system32\config\DEFAULT {reboot}

is everyone using the same local account to log onto the computer? If so you will need to prompt for the users domain account and password in your script.

There's a couple of ways to possibly fix it. though all require that you have not turned off System Restore. Easiest, you need a BartPE cd or equivalent. Boot form the cd, launch your preferred file explorer i.e. A43. browse your hard drive to: c:\windows\system32\config make a new directory in this folder named backup. copy the file contents from c:\windows\system32\config to c:\windows\system32\config\backup now go to c:\system volume information\_restore{GUID}\RPxx\snapshot where GUID is a unique ID, and xx is the second to last RP folder. From the snapshot folder copy the following to c:\windows\system32\config: _REGISTRY_MACHINE_SAM _REGISTRY_MACHINE_SECURITY _REGISTRY_MACHINE_SOFTWARE _REGISTRY_MACHINE_SYSTEM _REGISTRY_USER_.DEFAULT Go back to c:\windows\system32\config delete SAM, SECURITY, SOFTWARE, SYSTEM, DEFAULT Rename the copied files _REGISTRY_MACHINE_SAM to SAM _REGISTRY_MACHINE_SECURITY to SECURITY _REGISTRY_MACHINE_SOFTWARE to SOFTWARE _REGISTRY_MACHINE_SYSTEM to SYSTEM _REGISTRY_USER_.DEFAULT to DEFAULT Reboot system and it should boot up assuming your SAM file was not corrupted in the restore point you just restore from. Hard way, do all this copying and deleting and renaming by hand in the command window from the recovery console.

check the app. switch list. http://unattended.msfn.org/unattended.xp/page/list/switch/

sysprep is used before you capture an image, not after you deploy the image.

At what point are you settings these settings?

What exactly are you trying to do? WIM is not an installation method, it is an imaging technology. So if you were to create a WIM containing your UA and deploy it to a system all the system would have on it is an exact copy of your UA.

what are your reg tweaks? Some need to be applied at different points during the UA setup.

I've not used the SCCM but if you can push a WIM to a machine I don't see why not.

Working for me.

KeyDecoder: http://www.msfn.org/board/Decoding-Microso...st&p=383775

Depends, do you wan tall of the cr** software installed along with the drivers or just the hard ware drivers?

the IDE drive should be set to master. The version of the OS doesn't really matter.

Change the boot order in the bios each time you want to switch.