Tripredacus

Yes -

1. Your first install you should not create a user account. Sysprep may/can remove it on you. 2. Drivers should be added into the install.wim, not afterwards. Otherwise you run the risk of Sysprep removing some thing. For example (in my experience) a Sysprep /generalize removed all video drivers i had installed. However if you added the drivers ahead of time, they would not get removed. 3. Note my instructions are modified from what I actually use. I use WinRE so I just left that part out. As us OEMs go, we boot the computer in Audit mode, then reseal (OOBE and no generalize) before sending to the end-user. You may have to adjust your own methods at this point. In my business, we send PCs to end-users, not a corporate environment like some others. So note this when reading my posts. 4. all of the Diskpart commands I listed in the "code" was actually typed by me. It is only part of my diskpart script. If using diskpart like in my example, it does not assign a letter at all. I do not know why your way gets a letter. Also about the 64 bit part. I was going to post about that but I didn't. See, my Windows 7 deployment platform is x64 not x86. You need x64 to deploy x64. I had to copy the x64 bcdboot file from an existing install and put it in my PE. Since this topic is more PE related (from my standpoint), I recomend you check this out: http://www.msfn.org/board/imagex-hta-win-p...64-t138048.html

Cheaper or not, I'd like a PC game anyways. Some exceptions like I'd rather play a baseball game on a console, but not a hockey game or a FPS. Also I like the modding ability for a PC game as well. If my computer was good enough to play GTA San Andreas when it came out, I would have gotten it for that instead of PS2.

If you don't see it, read my response here: http://www.msfn.org/board/getting-error-fi...er-t138790.html

It is possible to backup the MBR but reapplying it won't re-activate the partition. Its because their MBRinst.exe does not capture the license string which is put someplace else in the boot sector. Although there are tools that may let you capture the entire boot sector, and this may work. However the problem is that the particular license installed in the recovery partition must match up or identify that string and if it doesn't, then you won't be able to use the partition.

So far, our installs of Pro and Home Premium do not create the System partition. I am now working on Ultimate, which does. In this case, I captured only the OS partition. I will test redeploying it in a little bit, so I'm not even sure if what I have done will work or not. Here ya go dude! 1. Install your OS. 2. install your programs etc, make sure to reboot afterwards 3. open up c:\windows\system32\sysprep\sysprep.exe 4. Choose OOBE and check Generalize and shutdown. Then make it go! Now at this point, I'm going to use imagex instructions. I also will use example of saving to network share. So you may end up capturing to a USB drive or so, but the following is just an example! 5. Boot into your PE 6. We capture the OS partition, PE will see a C and D drive. D drive should be where your OS is (thats how it appeared to me). So run this: imagex /capture /compress fast d: z:\install.wim "Windows 7 Pro OOBE" That's basically it for capture, let's pretend now we can deploy to another (or same) computer. So say you already booted the client PC into the PE. 7. Run this diskpart script: ie diskpart.exe /s diskpart.txt sel disk 0 clean create part pri size=500 sel part 1 active format fs=ntfs label="System" quick create part pri sel part 2 format fs=ntfs label="OS" quick assign letter=c exit 8. Now we can put the image on the computer and run the other steps imagex /apply z:\install.wim 1 c: c:\windows\system32\bcdboot.exe c:\windows Now reboot that guy and you should be set. You can see in this instructions, at the time of capture, I ignore the System partition, and at the time of deploy, I only create the partition but don't actually do anything with it.

I use Imagex and Windows Deployment Services.

If one stick works, and both do not. Try just using the second stick as your "one" stick and see if you still get errors. If you are lucky, maybe one of the sticks is bad. Do NOT crosspost! http://www.msfn.org/board/adding-ram-my-la...lp-t138792.html

Ooo Maybe I'll pick it up next week then. That would be easier I think. So the PC is cheaper? really? It has more benefits than the other versions. Obviously the fact you can mod it or get third-party mods for it.

It seems at least, with Deep Freeze, you are on the right track as far as administration goes. If the problem is that your students are using USB Keys, are these allowed or used for the actual class? I mean are they required for the curriculum? If not then this wouldn't necessarily have to have an IT solution.

Yes it is. Set objShell = CreateObject("WScript.Shell") Set objFso = CreateObject("Scripting.FileSystemObject") Original source located here, v71: http://www.msfn.org/board/winpe-2-0-gimage...tml#entry652594

I changed my Aperture to 128MB and I got a measly 2+ FPS average increase on Far Cry 2 benchmark. So it seems OK for now I guess, as long as that extra 128MB is only used once the 512MB is filled up. It may be a couple years before a game comes out that would do that!

You could also disable autorun, which may save you from some of those USB Key issues.

It looks alright, what command do you run to install Windows on the C drive?

I only added the " to my path because it contains spaces in the path. You don't need them otherwise. There are quite a few differences between the OPK/AIK from Vista and Windows 7. Its annoying now I have to type more than I'm used to! Oh also, you have the same version installed on both machines? Also make sure you are running your PE Tools Command Prompt as admin.

One of the errors you are getting is "parameter incorrect". which means you missed a step. Alas your package adding command is not complete. Here is your failing line: c:\dismtool2\cmd\dism.exe /image:c:\dismtool2\mount /add-package /packagepath:c:\dismtool2\updates Here is a working example: Dism /image:c:\winpe_amd64\mount /Add-Package /PackagePath:"C:\Program Files\Windows OPK\tools\PETools\amd64\WinPE_FPs\winpe-hta.cab" The main difference is that in your Dism command, you specify a folder, but in my command, I specify an actual file.

If you see my referral link, this was already done.

This is in referral to this project: http://www.msfn.org/board/imagex-hta-win-p...64-t138048.html I have determined that VBScript processing is not happening at all in Win PE 3.0 x64. The HTA itself is working fine except you can't do anything with it. None of the functions that require VBScript will work properly. Is there perhaps a file missing that I need? For example, running this function (its launched by clicking an image link) does nothing at all: Sub Unmount Dim Answer Answer = window.confirm("Click OK to install Vista apps") If Answer Then objshell.run("vista_pe_selector.exe"),0 Else End If End Sub And it should create a msgBox to show an OK box. When you click OK, it runs the EXE shown there or else Cancel and it does nothing. I have recompiled the programs for x64, so its not that it can't launch the programs. Now, the following code does something different. For some reason (if I am reading the code properly), the var for myInput = 7 because the "Aborted" box shows up right away. Sub doTask(doMe) Dim myInput Dim myError If doMe = "1" Then MsgBox "You must select image to apply first." Else If Instr(1, doMe, "1", 1) > 0 Then myInput = 1 If myInput = 7 Then MsgBox "Aborted" Else Call DiskPart() If objFso.FileExists(Sysfolder & "\1.txt") Then objShell.Run doMe,1,True Call confirmation2() On Error Resume Next Objfso.DeleteFile(Sysfolder & "1.txt") On Error Goto 0 Else End If End if Else myError = objShell.Run(doMe, 1, True) End if End if End Sub However, the link object with the following code to open the Command Prompt DOES work properly, and it still uses the doTask sub. onclick=doTask('%comspec%') So what could be the reason that VBScript is not functioning in this PE? Edit: I forgot to add that I have tried the following as well. Each of them succeed but offer no change. x:\windows\system32\regsvr32 vbscript.dll x:\windows\syswow64\regsvr32 vbscript.dll

Welcome to the MSFN!

SP3 on the technician computer shouldn't be a problem. Make sure you install the pre-requisites first if you are having a problem.

Is there even the ability to get to a command prompt in WinRE? Does it use a startnet.cmd or winpeshl.ini file? I haven't gotten to look at it too much so far.

What reads 248mb? PC Mark 05 does on the DirectX Display Device info. It has: Description Radeon X1650 Series Manufacturer ATI Technologies Inc. Total Local Video Memory 516 MB Total Local Texture Memory 516 MB Total AGP Memory 248 MB Which makes me think of another question. I've been leery of using Anti-aliasing for a long time. I haven't tried it in a while (definately not with this or my last card) but it always seemed to bring a performance hit. Can these cards handle AA without making things slower? My only point of reference is that my Voodoo 5500 can use its full AA ability and there is no performance hit.

By PE builder, do you mean the WAIK or some other 3rd party program?

I got a new video card, and I was all stoked about it but suddenly I might have made a blunder! My old video card was an ATI Radeon 9800XP 256MB. My new one is an ATI Radeon X1650 512MB. My concern is that my motherboard has a maximum aperture setting at 256MB in the BIOS. Does this mean I'm only going to be able to use 256MB? It actually reads in at 248MB, but honestly I bought this card for the chipset, not so much the memory.

I will, thanks!