Tripredacus

In the recovery console, I believe you should be able to run diskpart. Try it out, like this: DISKPART LIST VOL EXIT that will show you the drive letter. Find the one that is your hard drive, let's say it shows up as C: Then use this CHKDSK C: /F It may give you an error but you can press Y to get past it and it will run.

It looks like this is controlled in here: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU

Welcome to the MSFN! Please read our forum rules, especially #12. Try moving or deleting from an elevated command prompt and post the output.

So do you want to change the password for the built-in Administrator account or the one you created that is in the local Administrators group?

It looks like you can modify the registry keys to tell it not to scan. Look here: http://msdn.microsoft.com/en-us/library/aa382546%28v=VS.85%29.aspx

The thing about boos is you don't know whether to hug them or be scared. But just don't run away!

"It says choo choo choo choose me, and there's a picture of a train!" - Ralph Wiggum Oh wait, what kind of engineer?

Jaclaz I find it funny you tell people to search then post a bunch of boot land links. Anyways, moving this to Install Windows from USB.

Both Mini XP and Hiren's Boot CD contains warez. If you are in-fact asking about how to create a Windows XP for Thin Clients, that is another story. I suppose it is possible with WinPE (I think BS Explorer is like this) but likely a better option is XP Embedded. If you are asking about Mini XP or Hiren's Boot CD, then that is another story.

I just use Adobe Reader on one system and on the other I actually have Acrobat Pro on it. I never really noticed but then again I haven't tried using those advanced features before.

I'll have to see if this method is supported or not. But even so, since you have to specify the drive info, wouldn't it be different for different hard drives?

No fix for Windows 98?

I'm not really certain how the memory works on this type of P4. My P4 experience has only been on D850M series (both V and D) boards from Intel which uses RAMBUS. So on those, the RAM runs at 800MHz but FSB at 400MHz. But RAMBUS has direct access to the CPU so the speed is different in relation to DDR2. However, since you can fix it in Task Manager, I'm going to bet it is not just a hardware difference involved. But I too have seen changes in performance when changing memory speeds.

I think it was the same guy that said there was a taskbar that spanned extra monitors.

Yesterday I got Starcraft II and checked the minimum specs, and it says 1.5GB RAM for 7. That is how much I actually have, so I plugged in a 1GB USB key and set it for ReadyBoost. Both Windows (Computer Properties) and Starcraft II still only show that I have 1.5GB RAM. How can I see if anything is even using the ReadyBoost? Based on the Windows 7 training I had before it came out, it said ReadyBoost is basically a cheap RAM upgrade, but I haven't been able to see any difference.

Yes this is an annoying problem. Consider this scenario: Boot to PE and create partitions as C:\OS, D:\ODD, E:\HDD2 Install OS to C, format E Boot system, C is primary Boot drive, system is AOK. Boot to PE and parts are C:\OS, D:\HDD2, E:\ODD so in this situation, WinPE changed the drive letters because C and D are both hard drive partitions but E is the CD Drive. I can fix this by using WMI to find the CD Drive letter, set it to F, sel vol D and set to E, sel vol F and change to E. But if I don't do this and reboot into the OS again, the drive letter arrangement that WinPE detected stays! This means if you have anything on the HDD2 volume, all your permissions, links and programs are broken! Let's not think about making matters worse by having a USB key plugged in when you boot. If there was a way to set a drive letter in WinPE and have it always be that letter no matter what you do, that would be awesome. But yes, I know you could say "just make the ODD a letter after HDD parts" but sometimes I don't get this option.

If it were me, I would make a master install image... well I've done this anyways. I am pretty sure you can recreate an install DVD with this type of image, but I use WDS and WinPE for imaging Vista, so I have no experience with creating install DVDs. Here's my basic workflow (for Windows 7 and 2008 also): 1. Use DVD with unattend to install Vista to a PC and make sure autounattend puts the system in Audit mode. 2. Install updates (since you have SP2 in this already, I'll leave out the prep steps) 3. Sysprep /audit /generalize /shutdown Capture image with imagex, make sure to use /flags option. Then you have some choices now. If you aren't going to care what the install does, such as boot to welcome you would: 4a. boot the system back up and sysprep /oobe /generalize /shutdown Capture image again, same was as above. Or if you want to unattend your install, this instead: 4b. boot the system back up. Copy unattend.xml to the HDD, run sysprep /oobe /generalize /shutdown /unattend:unattend.xml Capture image again, same as above. What ends up happening if you have the original Audit image that will give an extra chance to recreate a deployment image. Or you can just deploy the Audit mode one and sysprep it when you are done. Now it should be possible to take the image made in 4a and put it back into the DVD, replacing the install.wim in sources and run an unattend against it. Well hope that helps.

OK first let's look at a few things. Old CPU: Pentium 4 2.8GHz (SL7PK-E0) L2 Cache: 1MB FSB: 533MHz New CPU: Pentium 4 3.2GHz (SL6WG-D1) L2 Cache: 512KB FSB: 800MHz System memory: 3GB DDR2 667GHz CL5 So in the old config, you were underclocking your memory from 667MHz to 533MHz. Now with the new CPU one of the following is happening (you'll have to check the BIOS to be sure) 1. New CPU is overclocking memory from 667MHz to 800MHz 2. Motherboard is underclocking the CPU because FSB can't run faster than 667MHz Both CPUs appear on the CPU compatibility chart: http://asia.msi.com/index.php?func=prodcpusupport&maincat_no=1&prod_no=1525#menu So check your BIOS to see what speed the memory and what the ratio for the CPU is. As noted on this list, your ratio should be 16. There is no BIOS update required for either CPU. If you have any 800MHz RAM, try putting that in there to see if you can see a difference.

Well what you initially described from the alt+tab definately can happen in games, especially if the game does not leave enough resources available for Windows to draw certain aspects of the screen. The part it recommended about booting off the Vista CD is equivalent to using another tool. If you have access to a WinPE or the Recovery console, you should run CHKDSK /F on the drive you think has a problem. Of course, you should probably back up your data if possible, but the improper power down could have done something to the drive that can't be fixed so we'll see.

I think this is one of the few older Star Wars games I don't actually own, so I couldn't even recreate it on my own system.

I believe that the cell phone SMS signal actually interferes with the speaker itself, and no amount of wire shielding will make a difference. That is just my experience at testing different audio cables when I used to have a phone like that.

I've got no idea, but under no circumstances can it be an .inf file! Don't you think so? Yes it is possible. Info on this type of file is pretty slim, so I am guessing real info on creating them are on websites behind password, such as Partner level access for Microsoft sites. I found one post on MSDN Social where someone was creating a Vista sidebar gadget and this sort of code was present in his post. Unfortunately, I'm not about to log into MS Partner to search around for you, since everything in there is NDA anyways.

Welcome to the MSFN! You won't need to worry about posting French translations of your post anymore, this is an English only forum.

I keep reading about some official patch you can get for the game (i can't go to lucasarts.com from work) that you copy into the data folder that might fix this.

All my PEs will automatically detect USB Keys without a problem, even if inserted after boot. The thing is that it won't pop up anything, but behind the scenes it will assign it a drive letter if a file system is found on it. After you insert, it is usually going to be the next available drive letter, but you can open diskpart and type LIST VOL to see a full list. Other possibility is that USB for mass storage has and option in the BIOS (I've seen this on some boards) and it is disabled.