Tripredacus

I think you need to do a repair install. A normal reinstall will do just what you are saying is happening.

How I image XP with WDS: 1. Boot to winpe.wim via PXE 2. use imagex to capture image ie. imagex /capture c: z:\xp-pro_standard.wim "boardname Drive C" /compress fast 3. boot new pc to winpe.wim via pxe 4. use diskpart to format drive 5. use imagex to redeploy image ie. imagex /apply z:\xp-pro_standard.wim "boardname Drive C" c: 6. reboot For native-mode WDS, it can see an install Image for Vista or 2008. If you want XP to be an install image you need to run WDS in mixed mode to have RIS support which you can make install images for XP. http://social.technet.microsoft.com/Forums...1-d149bc90f498/

The only main difference between a restart and shutdown is that a shutdown totally removes power from memory, erasing it 100%. On a restart, the system is supposed to empty out memory. You might have some lingering memory issues but this is the only thing that comes to my mind.

What gets authority, users over computers? Perhaps these 20% have users that over-ride the computer policy?

I looked into doing this when trying to install the latest iTunes. The registry hacks do not work, as described after the reboot they get changed back. I determined that (iTunes installer at least) checked the version info in winlogon, kernel32 and another file. You'd have to reshack those files to update the SP2 version. I tried it but since my computer at home can't boot off USB (to use NTFSDOS) i didn't bother trying to do it.

In the future, you can note this. The "wrong OS" message was coming from the installer for the drivers. In most cases, you can unpack the installer with WinRaR, which *may* allow you to get the actual drivers out of it. Then you can manually update the driver in Device Manager and have it look at those drivers and see if it can install. I've had to do this a couple times.

Make sure your sleep setting in the BIOS is set for S3 (suspend to RAM).

There is but it involves modifying Windows system files. These methods are not published by Microsoft and I am not certain if it is legal or allowed to discuss here.

http://technet.microsoft.com/en-us/library/cc731279.aspx

Our installer called a script from the network after install. I think it uses the guirunonce, not sure. Anyways, we keep a batch file on the server that silently installs all the updates. So when new updates come out, we download them, put them on the server, and update the script, so the installer runs the current updates every time. It isn't the best way, but we use it for now until we figure something else out.

That's probably the limit... i hope

As posted in the old one, I use Limewire primarily, and have the BT client for other stuff as required.

Is your profile over 2GB?

You mean this? http://www.microsoft.com/downloads/details...;displaylang=en

I am getting a Code 43 (driver conflict) on the onboard video controller in the Device Manager on Vista Business RTM and SP1. The image was created on the same computer. Here is the history: - Start with a PC with a GeForce video card in it. - install Vista Business RTM (or SP1) and set up GPOs - do not install any software or drivers - sysprep and generalize and capture Now I want to make a different image that will be more hardware specific. I use the same computer but I take out the video card. After I drop the image, there is a Code 43 in the Device Manager. There is no other software installed. If I do a hand-load of Vista again, there is no flag. If I put XP on there, there is no flag. There is something in Vista that makes it think there is a problem with the video because it is on the PCI bus instead of the PCI-E bus? There is no trace of the video card's hardware ID in the registry, and no matter what drivers I use this does not go away. Onboard video is Intel Graphics. I have the last 3 driver versions to use. Any ideas?

Do your normal setup as the admin, and one of your programs that you call at the end can change the registry settings and then force a reboot. You may need to preauth the computer into your AD tho.

I don't think it matters if it is a card or onboard. But you might try the software option if your board allows you to do it.

WDS isn't designed to deploy XP images in that way. I redeploy XP via WinPE and not the WDS boot loader.

I remember MAKING MP3s... It would take 30 seconds to record the WAV Audio, 40 minutes to compress to a layer 3 wave and 20 minutes to convert to MP3. And that was just for a 30 second audio clip on a 133MHz PC... I was so happy when making MP3s became so much easier! ps: I use LimeWire and have the BT client (not full app) installed.

http://www.practicallynetworked.com/sharin...filesharing.htm http://www.practicallynetworked.com/sharin...aring/index.htm

You can use diskpart to reveal the hidden partition, that is, as long as it can see it. You would need to post a full info about the volume/disk/partition before I could tell you what commands to use.

That software boots into a Linux shell. You are right, you can't run the setup.exe from there. And you can't run it from the DOS prompt. Did you follow the rest of the instructions to make the Windows installation source? It seems pretty staight forward, you should get a menu and pick what you want to install.

You need to specify a few other registry keys. DefaultUserName DefaultPassword DefaultDomainName http://www.mydigitallife.info/2008/06/15/h...-domain-member/

I was the one who reported this issue as well. I have not resolved it and am instead going to (attempt) migrate our XP install to PXE via WinPE 2.0 instead. If it helps, this is my operating environment Server 2003 Standard x32 Windows OPK Tools (Vista SP1 release) WDS BDD2007 original thread: http://www.msfn.org/board/index.php?showtopic=123611

Welcome to the work of non-certified hardware. Unless you can get a 32bit 2008 driver in there, you might just be SOL. I'm encountering a similar problem with a 3ware 9550. Its a hope for the best situation to be honest. Typically, the Vista 32bit drivers should be good enough. You might have to edit the INF so you don't have to force the driver to be installed tho.