Tripredacus

Citrix is a remote access/vpn client. An example is Citrix Metaframe, now called XenApp I guess. http://en.wikipedia.org/wiki/Citrix_metaframe

Based on my limited knowledge of this topic, looking at the benchmarks it seems the DDR2-844 is a better option. Your memory latency is higher, but also notice that with the higher clock speed memory, the L2 cache is doing more work than the other. However, you need to be careful, since it looks like you do not have the BIOS set up properly to use the slower clock memory, since you are also overclocking the CPU and FSB! Actually now that I see that, I can't say for sure. Your CPU and FSB speeds are different with each type of memory, so it is not a fair comparison!

The CPU Fan obviously connects to CPU_FAN. As far as the other one, I don't think it matters. All three fan pin blocks should be powered when the computer turns on. Those inputs will match the respective listing in the BIOS if you look at the monitoring page. The CPU fan should go the CPU_FAN. If the BIOS is set up to control fan speed, it can change the speed of them at different temperature threshholds. it is important for the CPU fan. The other ones likely operate much the same in comparison to each other. For the case fan, connect it to the pin-block that has the same amount of pins as the connector. In the future, I recommend you note which pinblocks you disconnect from to make it easier later. And the motherboard supplies the power to the fans. There are some cases where the fan has a molex connector (some high-powered fans) but if you didn't use this setup before, you shouldn't have to use it now.

Well... Windows PE v2.1 x86... http://www.msfn.org/board/index.php?showtopic=133392 I posted this question here because I was looking for more general information about DirectX and DXDIAG, not so much just getting it to work in PE. Its difficult to search for "blank messagebox dxdiag" because the results are so all over the place. I imagine that it would be possible to get DXDIAG to do this in any OS. I also used the Au3info tool on the messageboxes that open up, but they are devoid of any particular information that is helpful in any way. I used depends on DXDIAG while in XP, I didn't think of running it from the PE. I will try that next. UPDATE: Running Depends in the PE has worked out well, except I am left with 2 errors (one error): I am guessing that a DLL needs to be registered?

I've recently discovered how to monitor the partition creation process, but I haven't the time to play with it.

Try taking out those run commands so those programs do not install and see if it still fails.

I will admit I am not familiar with the environment you are using. I do all my WDS work and testing in a physical environment, so I do not know the intricasies (sic) of virtual environments. I can tell you that there is a firewall activated in the PE, which is probably what is stopping you from pinging the client. Check your DHCP logs to see if you can find instances of this other IP scope. You can also run a Wireshark (or similar tracing program) to see where the client is getting that IP from.

I do not see a problem with the drive size. Its something you'll just have to try out, make sure you have your raid driver floppy ready, hopefully you have an onboard floppy drive. Sometimes newer hardware doesn't like USB floppy drives for example, but you'll have to find out. Your first step is see if you can download the XP 32bit F6 RAID driver. If this driver is available (probably on Dell's website) then it should work for you.

I hope there is at least one of them being the member of that forum, so I can have the best help! But, again I wonder if it is legal or illegal to ask someone for someone else's email here? Please let me know, IcemanND. I'll follow your suggestion only if I really have no other solutions.Off topic: why there are so many members banned on MFSN these days? There is no reason to have an account removed from any forum. The simplest solution is to just not go to the site anymore. The members table of any forum usually has no problem with the number of entries, or to say it does not impact the server in such a way. There is no harm in registering on a forum just to be able to contact someone. I have done this before and forgot about it later. Or if you know someone else that is already a member of that forum, perhaps you can talk to them in some other method and they can get that information for you. Regarding off topic: the reasons why members get banned is not up for public discussion. I can tell you that we face a large amount of spammers and bots that we deal with on a daily basis.

Yes, if you happen upon a fix of some sort, please let us know.

Setres has the ability to set resolution, color depth and refresh rate. That being said, I've only seen it work properly with the first two options. I use setres to set a refresh rate of 1Hz, which it seems either the PE rejects and uses its default for the selected resolution, or that it doesn't support that feature at all. In any case, you may want to try playing with that program to see if it helps you at all. It supports a cli method as well as the gui. I've never used the gui method myself. http://www.softpedia.com/get/Multimedia/Vi...ls/SetRes.shtml

The actual updates or programs you added for your setup to run.

Also take a look in the Event Viewer to see if there is anything suspicious in there.

I am doing some software testing, and it is hard to search for this specific issue. When I open DXDIAG, the initial messagebox that opens asks you if you want to check the WHQL signatures on the drivers. It gives you an option of yes or no. In my testing, This msgbox has no text in it, but does have a yes or no button. If I click either yes or no, it then comes up with another blank msgbox with an OK button. When you click OK, DXDIAG.EXE process closes. I am imagining that a file is not available, a service not running or a DLL is not registered. Where can I find detailed information about how DXDIAG (or DirectX itself) works?

NoScript RikaiChan 1.05 Java Quick Starter 1.0 Microsoft .NET Framework Assistant 1.0 Names Dictionary for rikaihcan 1.04 *compatibility issues Wikipedia Lookup Extension 0.3.1

I am guessing one of the packages you are trying to install is an online installer and not a redistributable or self contained installer. It has nothing to do with the namespaces and format declarations in the XML file. Do not change or remove those.

Welcome to the MSFN!

Windows always goes to manufacturers first. This is why you can go to the store and get an HP with a new OS before the retail copies are available. Or they try for a simultaneous release, so that new PCs hit the stores the same time as the new media does.

Yes it is as I feared. You can tell from the HwID, that items starting with PCI/ are physical devices, while any others (in most cases, or like the others you listed) are virtual. Which means they are controlled by software, or the BIOS, or are emulated. This is true. These types of adapters do not work in Win PE 1.x or 2.x so far that I have been able to determine. The Device I mentioned earlier also uses the Virtual Bus. The problem is that the device is not enumerated in a way that the PE can make use of it. I have no solution for this issue, and have yet to find any hope. We ran into these types of NICs a while ago, and we made a good note to stay away from them when possible until a solution could be found. In case I do have to work with one, I have to use an additional PCI NIC if possible, or worst case scenario image the drive in another computer, then move it back and boot it up in its own hardware.

PCISCAN can be found here: http://www.nu2.nu/utils/ use pciscan -v switch for full info.

I have a partial guide with partial success... To install DirectX 9.0c: - Download the DirectX 9.0c redistributable. - extract the contents of DXNT.CAB. - copy all DLL and SYS files to System32 - create the path System32\DirectX\DInput and copy all PNG and INI files into there. I need to also put the August 2008 component. Errors now battling: - Error Initializing DirectDraw - DirectX Direct3D version required is unavailable.

Not in a way to make the WinPE an operating system, but in my quest to use it as a Burn program. I would like to find information on how to enable sound in Win PE 2.x as well as be able to display 3d graphics. This would entail getting portions of the DirectX 9.0c redistributable into the PE and be recognized by it. Any help or ideas would be appreciated. Oh also, I've researched sound at least. The problem is that the PE does not contain the files in KB888111, so it is not possible to install the driver for the soundcard because the Hardware ID does not match the INF files for the device. I am not certain how to get around this. I am more concerned on getting video to work more-so than sound.

Yes I think I have the code down. It seems to work either with button or input objects. The symptom I am having now is that the program it launches does not stay open. I was testing in VirtualBox, and I think this is an issue. Nevertheless, this post has allowed me to clean up my code a bit at least.

You can use PEIMG to put the Broadcom driver into the boot.wim. Be aware that I have had issues with the B57 driver from them. Make sure to use the Vista 32bit driver. If you are not sure about the driver, grab the Vista LAN pack from Driverpacks.net.

Server 2008 x86 will display 4GB RAM if you have PAE enabled, but it will still make use of about 3.2GB.