Tripredacus

The number one cause for a PE to fail to load or operate properly is bad memory. I always run memtest on machines that don't work with the PE as my first step. I have found some motherboards do not like the PE at all, but that was a long time ago.

I have made a PSD that I am trying to save. It saves fine, but the image is not as bright as it is in the PSD format, it is a lot duller. I have tried 24bit BMP (my target format), 32bit BMP and PNG file. They all seem dull or slightly darker than the PSD file. How can I change this? The PSD is 1024x768, RGB/8 if that helps.

I know exactly what you mean. You may want to change your tabbed browsing to have "open links in same tab" instead of new tab.

Mine doesn't have that either, but it does have the product key in there.

Did you try using relative paths? Also you might be better off using an HTML file or an HTA. Check out these forums also: Software Hangout Web Development

Welcome to the MSFN!

Ah yes, we have our Applications forum just for that. Be sure to check the sticky for the silent switch lists.

Welcome to the MSFN!

Tripredacus is also a Transformers character, so you find a lot of websites about that character and its toys as well. On page one, My influence only appears in 3 of the ten links. One is my website, one my tformers.com account page and my youtube channel.

Video card temperature is going to be hot. Do you have a fan on your video card also? It wouldn't hurt to add a 3rd case fan in there since you have an extra plug available. CPU temp is kinda warm but isn't horrible. Just keep it under 70c. Also seeing how CPU and GPU temps are the same, another reason why I wouldn't trust this programs readings. See what the BIOS says. Also, I'm not sure about those voltage readings, you can double check those numbers (and the temps) with what the BIOS says if it has that info. I don't know why it is reading the +/- 12V as such weird values... Also why Temp3 is -1c...

Well I would still use the unattend.xml but not have it install those programs. What is the source media you are using to install Vista? Also, you can make a Vista install DVD with no autounattend.xml in it, and say put that file on a floppy disk or USB key and the DVD will search for the file. This way you can easily test different unattend settings without having to rebuild you media every time. I keep a Vista Business DVD around that is set up like that for installing on weird configs that roll into here every now and then, so we can use custom unattend settings without rebuilding the media.

I'll try to remember to recommend testing in other environments when people have problems running VMs.

I am in the same boat as DigeratiPrime, except I don't keep track. I use the same username for all forums except for a handful that I joined over 10 years ago. I'm probably in the hundreds!

The original author has abandoned this project, so I am taking over its sponsorship. I cannot take any requests for adding or updating new features to the software. UPDATE Working on v9.1 update. Last available versions Version 7.1 :: download Version 9.0 :: download Cleaned up Version 2.0 by Fredledingue :: download Custom PE backgrounds Embedded by Tripredacus :: download Vista by Tripredacus :: download

You may want to dig around in the registry. You can do this by mounting your pe.wim, then use Regedit to edit an Offline Registry Hive. You will find a setup.hiv in the Mount folder someplace. I haven't done this yet and I can't remember exactly where it is, but you should be able to easily find it. The default resolution for the PE 2.x is 800x600 @ 60Hz I believe. It should be able to make due with the default display drivers. I haven't seen anything so far that leads me to believe adding display drivers does anything that the defaults can't do.

I will try that next. I am also trying to compare the results of depends on two different systems. Within the PE, the load order for the failure for IEFRAME.DLL is this: SHELL32.DLL -> BROWESUI.DLL -> SHDOCVW.DLL -> IEFRAME.DLL However, in a working environment, the load order is different. For example, in a working system, the same path is the same except SHDOCVW.DLL does not link to IEFRAME.DLL, in fact, it doesn't link to anything! Also, in the working example, IEFRAME.DLL is linked from MSHTML.DLL. OK wait, let me change this around into something more readable. Non-Working Environment 1. SHELL32.DLL -> BROWSEUI.DLL -> SHDOCVW.DLL -> IEFRAME.DLL 2. SHELL32.DLL -> SHDOCVW.DLL -> IEFRAME.DLL 3. SHELL32.DLL -> SHDOCVW.DLL -> IEFRAME.DLL -> URLMON.DLL -> SHLWAPI.DLL Working Environment 1. SHELL32.DLL -> BROWSEUI.DLL -> SHDOCVW.DLL -| <--- SHDOCVW.DLL does not link further 2. SHELL32.DLL -> SHDOCVW.DLL -| <--- SHDOCVW.DLL does not link to IEFRAME.DLL 3. see #2 4. SHELL32.DLL -> SHDOCVW.DLL -> MSHTML.DLL -> IEFRAME.DLL Also, I am now noticing that the dependency loads are totally different between both machines. For example, the working machine has MSFEEDS.DLL listed as a dependency, while it does not list that file at all in the PE. I'm done for today I think. Tomorrow I will install Vista on a machine without any .NET Framework or Windows updates in it. I am thinking part of the problem is that this computer has all the .NET Frameworks installed and a handful of VS Runtime environments installed, so this may be causing me more of a headache than I need.

I am finding that this error is because I am missing some VisualBasic or .NET runtime files, or that they are present already but need to be registered... I have no idea how to figure out which it is and or which need to be registered.

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.