Tripredacus

Hallo, welcome to the MSFN!

Welcome to the MSFN!

An interesting development regarding launching the HTA from a button. Let's consider the following: I can launch an HTA via winpeshl.ini using mshta, but i can't use it from the button. Here is the main difference, winpeshl.ini code: %SYSTEMDRIVE%\Windows\System32\mshta.exe, "%SYSTEMDRIVE%\Windows\System32\recovery1024x600.hta" compared to before, the difference is the full path there. I tested by trying to launch an HTA using MSHTA from CMD but it would not open. It would only open once the full path argument was used. I am guessing that this is because MSHTA uses a relative path from its location, rather than the location from where the command is run from. Think PHP includes, the idea is similar! I'm going to run a recompile after using the full path and see how that goes.

I don't think I'd be able to handle Q3 on a netbook. The screen is way too small!

You need to post the error on the BSOD, at least the STOP code. Follow these steps if possible: http://www.msfn.org/board/index.php?showtopic=130004

COPYPASTA! http://www.msfn.org/board/index.php?showtopic=134397

Doesn't look like it. Google Groups MVP response Some app examples are: hideoe Iconic Tray PowerMenu

In my experience, this is caused by a resource allocation or ramdisk error. It can be caused by bad media, or cd drives or cables. Also any large amount of network traffic if using TFTP.

I've gotten around it in the past by using NTFSDOS or a PE to unlock and replace the "backup" files. This way, when I boot back into Windows and delete a file, WFP replaces it with the "original" which happened to be the file I replaced. I suppose your way is easier.

I'm sure some documentation will get released on how to do it. They always send us DVDs with the SP on it but we didn't get this one yet. I hope they just send us a whole new media because its annoying to make new Vista images. Right now it takes over 2 hours to make an SP1 image, but hopefully I'll figure out that WDS thing.

Its hard to tell from that picture but it looks like the inactive windows are blurry. Are you at the native resolution for your display?

Are you sure its a PE 2.x? The website does indeed talk about Win PE, but then right next to it has this Which makes me think it is the 1.x series instead. Especially since it talks about booting to the PE using RIS.

I can't find anything specific, it seems Diskpart can't rename a volume. You might have to do this by editing the BCD for the ramdisk.

I need some help as searching for this is not very easy for me to find results. I need to limit a user from being able to delete a volume in Disk Management in Windows XP Pro SP2 with either Local Computer Policy or by use of PowerShell. If you have no idea, is there a good place to find out how to make custom GPOs for the local system? Or any good PowerShell reference concerning limiting MMC options? I already have Windows PowerShell Scripting Guide by Ed Wilson (2008) pn X14-15140, but it is a hard read to find this kind of specific info. Thanks Update: It looks like using i/x/CACLS would be the best, to deny all permissions to the volume which should stop users from deleting the partition. However, the volume has no drive letter. Is there a way to assign an ACL to a GUID or other system level descriptor for the volume?

Revised restart.exe code in AutoIT. Switch MsgBox(1, "Restart", "You have chosen to restart the computer. Click OK to continue.") Case 1;OK pressed RunWait (@ComSpec & " /c c:\mbr 0 1 /h") RunWait (@ComSpec & " /c x:\windows\system32\wpeutil reboot") Case 2;CANCEL pressed Exit() EndSwitch Note that it does more than restart. It hides the recovery partition again... and I forgot that the recovery partition will appear as the C Drive, so the drive letter changing script isn't going to work for me in this case. I will have to do a lot of pilot testing to verify that the recovery partition is always the C Drive. The Card Reader issue may only appear during deployment and not during recovery, and if this is the case then I'm not going to have to worry about it. It has already been accepted that if the recovery partition fails to work in the field, it will come back on RMA to get redone anyways. This is good news at least! Now here is a big issue. When the recovery partition loads, it resets the MBR via winpeshl.ini. This is required otherwise after the restart, it won't go back to the system partition. One of my concerns is a big "what if" such as a user boots into the recovery partition and then powers off the machine, the battery dies, etc. This will leave the recovery partition visible in Windows which is a big no-no. I may end up having it hide the partition during winpeshl.ini as well to eliminate this issue. Any ideas about this possible problem? I'll work on the admin prompt code after lunch and hopefully post a revised version of that as well. I wanted to add that I've found an additional issue. While testing to see how Windows sees the recovery partition, I realised that it is possible for the end user to delete the partition from Disk Management. Any ideas of how I can change the image so that this option is not available? Here is the test code for the admin prompt. Also in AutoIT. It hasn't been tested but it passes Beta Compile. $GUI = GUICreate("Login",210,80,-1,-1,0x16C80000,0x00000181) $USERNAME = GUICtrlCreateInput("Username",5,5,200,20,0x01) $PASSWORD = GUICtrlCreateInput("Password",5,30,200,20,0x21) $LOGIN = GUICtrlCreateButton("Login",50,55,100,20) GUISetState(@SW_SHOW,$GUI) While 1 $MSG = GUIGetMsg() If $MSG = $LOGIN Then If GUICtrlRead($USERNAME) == "username" And GUICtrlRead($PASSWORD) == "password" Then Run(@Comspec & " /c cmd.exe") Exit Else MsgBox(0,"Login","Incorrect username or password.") EndIf ElseIf $MSG = -3 Then Exit EndIf WEnd Exit

Getting it to run from the main HTA is not a problem. I need to have some sort of splash screen or animation to be displayed while it is running diskpart, as well as while it is running imagex. This is why I changed to launch a separate HTA that runs those commands. Once I can get that small HTA to run properly, I can insert an animated GIF or something into there.

It seems like you've already gotten your answer on the AutoIT forums. That is the best place to go with questions about their software. http://www.autoitscript.com/forum/index.ph...xcel+quickbooks

This seems to be the popular thread of the week! No awards tho! http://www.msfn.org/board/index.php?showtopic=134397 http://www.msfn.org/board/index.php?showto...20&start=20 Those are just two examples...

As noted before, it all depends on how you use it. Most of the things the registry cleaners get rid of like orphaned keys, etc do nothing for performance. Usually only ones that let you change services and startup apps will make things faster. I typically will use a cleaner to do this because its easier than digging in the regedit every time.

In my case, if the HDD is C and I format it and make it C again, I won't care what the UFD's drive letter is because most importantly, it isn't going to be C.

I have a plan for most of those items. The HTA launching issue is in a thread in the programming forum. I am using a method from other programs I have used so am expecting the same results... maybe I am missing a peice there. http://www.msfn.org/board/index.php?showtopic=134164 The ok/cancel box is not something I need help on, its just on my checklist. As far as the password prompt, its because I have to change how I have the code arranged. Currently, after the correct credentials are typed in, it launches a program, cmd.exe. However, I need to wrap that into a funtion and add exit() to that function only. Previously I tried putting it at the end of the script but it just would taskkill itself It is written in AutoIT. I forgot an additional item, need to take into effect the Realtek Card Reader issue. http://www.msfn.org/board/index.php?showtopic=134398

I've run into the same problem on note/netbooks that have a realtek card reader in them. They get assigned the first available drive letter even if you set it in the BIOS to be recognized as a FDD. I have a theory, since I will have to do this as well, but I haven't scripted it out or tried to use it yet. Its on my list of things to do for my recovery partition project. So here is my idea and you can try it out: Use Diskpart to reassign the drive letter to something else. Example: sel vol c assign letter=s sel disk 0 clean create part pri active format fs=ntfs quick assign letter=c The first two lines are all you would need to change the drive letter. These commands are known to work in Win PE 2.x. I have not tested older or newer PE versions. You don't have to change the C to S, change it to whatever letter will be available.

Take a look into our Application Installs section.

Welcome to the MSFN! I also had problems with the Windows 7 beta version. It seems there are some bad compiles up there that do in fact work but have CRC errors. For example, I burned it to a CD but the CD could not do the install. I ended up mounting the ISO with Daemon tools and installing it that way. What version are you using? What is the filename of the ISO? What OS is on your Technician PC?

Also think of the memory hit these drives would have. Buffering the content to read the files, etc. I doubt we will see this on any form of Windows that we see today. How much memory do you need to read the thing? Imagine how bad the initial MTBF for the drives will be! Also how long to burn the disc too! The idea reminds me of this: Its funny how everything nowadays seems to all be theory, as portions of the industry are moving faster than others and there is a huge bottleneck!