Tripredacus

I have not heard it would update to Windows 8.1 automatically. That update come from the store and you have to actually click on it. It does not get served up in the normal Windows Updates window or from automatic updates. Other than looking in My PC Properties, you can launch a cmd and run ver to get the version number. Windows 8 is 6.2.9200 Windows 8.1 is 6.3.9600 The Windows Store may not work if the PC is not activated or if you signed into a local account. If Windows is not activated, the Windows version should appear on the desktop.

They recommend a different size for SSDs, but 260MB not 200. http://technet.microsoft.com/en-us/library/dd799232%28v=ws.10%29.aspx

I recommend that some *better* sources be had for the information. I've been using this site for the past couple of years. http://enenews.com/ PS: Make sure to keep politics out of this topic.

Yes you should just be able to match the "bitness" of the PE you are using. Presuming that is a portable application, it should be fine unless it needs a .Net Framework or DirectX file.

The message you get from CPU-Z is because the architecture for the EXE does not match that of the PE you have built. Here is one example of how to get it from AutoIT: $mem = MemGetStats()$pmem = ( Round ($mem[1] / 1024000, 3) & " GB" )MsgBox (4096, "Memory Total", $pmem )

To be fair, this scenario is only one of a few different ones. Whoever made your computer is to blame for your PC only having that type of recovery.

Welcome to the MSFN.

Few ( ) years ago,music from audio CDs was transmitted to the computer through an additional thin cable connected to the audio output of optical drives. I think that cable was not needed anymore starting Win2k (or was it ME) but I'm not sure it could still work that way or not with later OSs.The motherboard had to have that connector as well. It could be that yours was "working" like that (for audio only)? Have you tried a pressed (data) CD ? It wasn't. Or if it was, then the cable was not there. I know what cable you mean because my Win98 PC uses such a thing. But even if it were the case, Windows would still detect that a disc was in the drive, you just would not have any sound.

Its all in the UEFI 2.3.1 specifications. Any hardware with UEFI 2.3.1 only supports 64bit Vista, 7, x86 or x64 Windows 8, x64 Linux/other stuff. Its in the spec. Everyone agreed to stop caring about 32bit (remember when there originally wasn't going to be a 32bit Windows 8?) and since XP is EOL in the OEM Channel, it didn't make sense to bother keeping up the support. As far as the Intel platform goes, pretty much anything starting at the 6 series will have UEFI 2.3.1 and doesn't support XP anything... You might be able to get XP x64 on them but it doesn't seem to be very common.

What will the computer be used for?

Confirmed this is caught up in the swear filter for some reason.

In my experience with ATI and nVidia drivers, DISM does not support all the INF functions that those drivers use. This is why DISM fails. The one way I've found to actually get those drivers in there is to deploy the image without the drivers. Then manually install the driver. You would need to use a driver extractor program, one that can take the installed device and build an INF package. Then you can integrate that INF. Due to support reasons, I don't bother with that method.

The non-target audience always kills the social networking site. Myspace was for the music industry and Facebook was for college students. Although, if they stuck to those demographics I doubt either of those sites would have made as much money as they had.

Oops, I forgot to update this. In the BIOS, the secondary slave was set to disabled, but enabling it did not help. Neither did removing and redetecting the device. Interestingly enough, Windows had a 0x7B STOP error when trying to boot in Safe Mode. I ended up replacing the drive. I did not test the original drive to see if it is a drive problem, maybe I can remember to pick it up tomorrow.

The HDD is at the end. I remembered that part about IDE at least. There are 2 IDE connectors on the board. The case, being a Dell, is not ideal for hard disk expansion. There is only 1 HDD bay, 1 floppy and 2 5.25" bays. The second DVD drive that was not working was due to... um... physical damage. (It didn't open one day and the guy used a knife to get his CD out... ) Technically, the "working" DVD drive was moved. I had to take it out in order to properly align the bracketted HDD into teh 5.25" bay. The user had purchased the parts himself but did not get the recommended bracket. The one I recommended would have made the HDD the size of an ODD but whatever. So it is possible that this drive was damaged while the case was open. I can still test it on its own and with the original cable. Due to orientation (taking into account IDE cable lengths) the only place to put an additional HDD was into the 5.25" bay. And then, the only way it could connect was to the DVD drive. In order to have both HDDs on the same cable would have required using one longer than the ATA spec allows. I know they make them (why, who knows) but since I'm the "pointman" for problems with his computers, I'd rather not take shortcuts on fixing it.

Windows XP does not support SecureBoot. If you are using 32bit XP sources (like BartPE) then you should disable all UEFI boot options and only use the Legacy one in the CSM. For XP with an SSD, you need to make sure the SATA type is set to AHCI. I would not recommend trying to install XP from the SSD, why not use an install disc? If you are unable to disable SecureBoot, maybe you can post what board you are using.

You can put in a generic waiting process or have it wait until a certain process exists. For example, if one of the last processes that loads at boot is Trillian, you can have your app wait until trillian.exe process exists before executing. It looks like Task Scheduler already supports these types of advanced options with what is called triggers: http://technet.microsoft.com/en-us/library/cc748841.aspx You can even have it wait for a certain event to be logged.

Yeah, like I said, I don't think that is what it is. Instead that is what Apple is calling it.

Welcome to the MSFN!

I suspect your Macbook Pro 2.1 has a 64bit UEFI 2.3.1 firmware that is modified to prevent 64bit code to run on it. I've seen other manufacturers make their BIOS work this way to prevent their systems to be used for things they do not support. For example, by default, some ECS embedded motherboards come with this type of BIOS. Either way, the tool you are reading about (nvrboot.efi) is for the Itanium platform. So you would find this file in an Itanium edition of Windows. Unfortunately, Itanium's EFI boot code is incompatible with the current UEFI 2.3.1 hardware. Even forcing Itanium or IA-32 boot roms to run on a modern EFI system will result in a hard lock of the system.

Yes I meant 80-wire. I will try some things out when I go there again and report back.

Do you mean the EULA that is displayed? Do you get an error, or see something else?

Well I can't see why you'd need that program, but I'd probably use Make_PE3 or WinPESE to determine compatibility for it in a stock PE.

SkipMachineOOBE and SkipUserOOBE are not valid for Windows 7. SkipReArm will only work if the install image was created using that setting.

You have everything low, it seems, in your config except for Draw Distance. Changing that will also help your performance, however maybe not gameplay wise.