Tripredacus

Wow that was uncalled for Ripken

OK I am starting to think we can make this easier. I don't think we have to worry about sysfolder. There is another sub that controls applying the images. See this snippet: If Radio.Checked = True Then myInput2 = window.confirm("Would you like to apply the selected image?") If myInput2 = false Then MsgBox "Aborted" Exit Sub So if I choose to apply an image, it needs to get a var back from window.confirm. Since we have already established that window.confirm isn't working, this value would be "false" thus generating the "aborted" message. So if there is a way to simply replace window.confirm, this may solve this problem. Update: Another user confirmed that window.confirm does not work in the x86 version either. I have safely replaced that code, here is a new example: Dim Answer, objShell, objFso Set objShell = CreateObject("WScript.Shell") Set objFso = CreateObject("Scripting.FileSystemObject") Answer = MsgBox("Do you want to install XP Apps?",1,"XPapps") If Answer Then objshell.run("xp_pe_selector.exe"),0 Else End If So the new PE must have something that was changed from last version. Perhaps the Cscript program was changed? We may never know.

Yay! May today be a day where you don't have to work in the database.

I had that earlier today at work! Fortunately today only 2U servers. Those 1U fans are really loud with the cover removed. And in case anyone is wondering, when the servers are in my room, we disable the chassis intrusion alarms! Then it would be worse! Frank Zappa - Hot Plate Heaven at the Green Hotel

This project is on hold. I'm fully in Windows 7 mode right now. Got a deadline to keep an eye on!

It happens to most of us, getting stumped about something.

Welcome to the MSFN!

Sorry Atheros. Currently I am not going at it on my own (or with help from people here) yet as I have an SR open with Microsoft about it. But ok, so the sysfolder, is defined here: Set SysFolder = Objfso.GetSpecialFolder(1) But yes, looking at this code, you may be on the right track! Because obviously the code after this, which sets the dimensions of the HTA, does in fact work... So is this "GetSpecialFolder" a global variable? It isn't defined anywhere in the HTA. So I am understanding that when it looks at SysFolder in x64, the PE returns Syswow64, instead of System32. How can it be (easily) changed to return System32? Update: Nope this is a dead end, going after SysFolder. I got this code written up real quick, to find out what variable is being returned: Dim fso, tempfile, tfolder, tname, tfile Set fso = CreateObject("Scripting.FileSystemObject") Set tfolder = fso.GetSpecialFolder(1) MsgBox(tfolder) Saved as test.vbs, and executed as cscript test.vbs. The messagebox that comes up says: X:\Windows\System32 So this object isn't referring to syswow64. There must still be something missing. I was hoping it would have been that simple!

regsvr32 /s misc/gimagex_com.dll

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.