Tripredacus

I've seen some video cards report below their value, but I believe this is just a reporting issue. I bet if you go into Device Manager, you will find that the ATI driver is not installed, but instead a Microsoft or Unknown driver. Getting the correct driver in there should fix the problem, although it may still report the incorrect value.

Welcome to the MSFN!

Alec Empire - Hard Like Its A Pose

Old score above. Upgrade motherboard (DQ35JO), RAM (4GB DDR2 800) and CPU (Q9300) New scores: Base Score: 5.0 CPU: 7.2 RAM: 7.2 Graphics: 5.0 Gaming Graphics: 6.1 Primary Hard Disk: 5.7 Next upgrade could only be video card, but I don't see that happening any time soon.

Finally, something I learned in college I can apply in real life! I have seen ONE operating system that required a small partition (like 8MB perhaps) in order to boot. That is because said operating system wasn't an operating system at all, it is a shell. You know it, Novell sold NetWare Server 4 (and lower) as an "Operating System" but actually the setup required you to create two partitions. One very small partition (maybe 8MB if you like) where you install... DOS! Then of course you install NetWare in the second, larger partition. PC would boot, load up DOS, launch a program that started NetWare up. This was true for Netware 3 to 4.1, not sure about 4.11. Refs: http://en.wikipedia.org/wiki/Novell_NetWare#Strategic_mistakes http://www.myboogpages.com/2009/02/installing-netware-41-on-vmware.html

Winders 95? Hallo Hallo

I'm sorry Dave, I can't do that.

First before doing all that work, post the command you are using, and verify that the files are in those locations. Here is an example command I have used in the past: DISM /IMAGE:c:\winpe_x86\mount /ADD-DRIVER /DRIVER:D:\Drivers\Intel\DQ57TM\PROWin32\PRO1000\Win32\NDIS62\e1k6232.inf EDIT: there is no space before e1k6232.inf as it appears in my example. That is a formatting error with the forum.

You can try this, it was designed for Win PE 2.0, so some code may be deprecated.

The error I see is that it can't find PEIMG.exe. If you read the first post there is this: By that description, it may not be a critical error, but I have not used this program before.

It needs to create a user account. You can just have it create an account, and put your CMD into the FirstLogon Commands. The problem is that once you change the password on the Administrator account, you will still log in with the created account. You could also run a script that adds the Auto Logon keys into the registry for the Administrator account, so on a reboot that is the account that logs on instead of the new one. There is no harm to have another account on the machine to use in case of emergency, or by your technical staff.

There are a couple bugs to note here. One is with Server 2008 and the other with Windows 7. The Windows 7 bug is that if you choose a Network Location other than Public and then run sysprep, the image will become damaged. I'm not sure why it wouldn't let you choose the Work option, but as a precaution, I set Network Location to Public on everything I work on, even my work and home PCs. So try specifying Public to see if that is any different. Also validate your answer file in WSIM, it is possible that Setup doesn't understand what option you have chosen. The valid options are: Home Work Other <-- Other = Public The bug in Server 2008 is with WDS not clearing out the client database properly. Someone else posted a thread about this.. When I use WDS, I never use the options to add computers into an object, and just let the server approve everything. Although the reasons for this is that my imaging servers have/were/are (I'm not sure what their exact status is nowadays) are on separate networks that do not contain any standard client machines, so all clients that attempt a PXE boot are doing so to get imaged. I haven't had the opportunity yet to setup and operate a WDS Server from within a corporate domain... It is interesting to me, especially MDT 2010 but I'm not licensed to use it

Just a question, was the original OS from an OEM like Dell? What type of CD did you reinstall with, was it a recovery CD with a company's name on it or was it the Microsoft hologram disc?

May you find many large trees underneath your present this year!

When I've done these types of deployments, I've used the install key to install Windows, and not worrying that Sysprep will remove that key. Then use another XML for the sysprep /unattend which has the activation key in it. Of course you are using a deployment solution I have no experience in, so hard to translate that.

Nice summary! Stay awhile and chat a bit first before you link to your tool, Boyans...

I want to think you can set TCP settings in the registry. I remember reading about such things when I was troubleshooting a Server 2008 issue, so it might not be related. I do not remember much more than that though.

Welcome to the MSFN! Use the normal font when you post, check out our rules too!

I figured, I'll have to wait until IE9 has an x64 peice to view the file.

The two "locations" are for the two different WIMS. But the Install.wim and the Boot.wim use different XML. The XML you attach to the boot.wim are for Setup passes, the install.wim uses the oobeSystem, Specialize, etc. Look up the term WDSClientUnattend, this is for the install.wim. Here is a start: TechNet

Why not just leave the Administrator account disabled and create a new user account in the Administrators group? If you use the built-in Administrator account, you run the risk of bricking the OS if the account gets corrupted.

I would suggest that you re-create the answer file with WSIM. It is obvious you did not use WSIM to create it (there was no name space specified for example). After some modification, i was able to get WSIM to open it, however there was still an error in the XML Parser "Cannot find Windows image information in answer file." I have not seen this message before and do not know what it means. I compared it against install_Windows 7 ENTERPRISE.clg from the Sources folder.

OK!

Welcome to the MSFN!