Tripredacus

Welcome to the MSFN! If you want more than 4GB (or 3.2GB) of RAM, you need to upgrade to a 64bit version of Windows. XP, Vista and 7 32bit will only see 4GB even if you have more than that installed. Its a waste of money on RAM. Your other option is you can get the RAM now, knowing full well you can't use it, and then get a 64bit OS later.

I've got a monopoly on this name, almost. You won't find any tripredacus@x.com (not x.com, that's paypal! Using an example) email addresses that are me. I never got any of those. Also I think I do not have this name on Hulu, LiveJournal and a couple other places. Or maybe I do and lost the passwords... I've made it so no one would want to pretend to be me. I'm not sure if that's something to brag about tho...

I have this function here, which works properly: Sub RunFull Set objShell = CreateObject("WScript.Shell") objShell.Run "fscommand\full.exe" On Error Resume Next Set objShell = Nothing Call confirmation2() End Sub However, the problem is that the last item, "call confirmation2()" happens right away. In other words, I need it to have the following procedure: 1. run full.exe 2. when full.exe is done, call confirmation2() What happens is that it runs full.exe, and then executes the call. This confirmation makes a msgbox appear on the screen. In addition, it may be helpful for me to have it do 3 things, but I do not have the code for it. 1. run full.exe 2. while full.exe is running, show an animation or splash screen 3. when full.exe is done, hide the splash screen and call confirmation2() I'm currently trying to get AutoIT to display the splash screen while it is running, but it isn't working out properly.

Update: the problem I had with launching the program was with the program itself, not the HTA.

That's a very strange DLL name. What is the make and model of this modem?

Well that's an interesting little trick that I didn't know about. What I normally do is "change the way security center alerts me" by unchecking the anti-virus and windows updates boxes.

Welcome back!

Those are all the instructions you should need. You also need your Windows CD I think, it always wants to copy files every time you go into TCP/IP properties it seems like.

I will try using another path. So far I am not happy with how buggy WSIM is when making the file. No, I can't post the batch file, it is used for OA. The batch file works fine if run locally on a system.

Autounattend.xml is used for a CD based setup. Unattend.xml is used for the boot image in a WDS install Technically, the boot image based setup can use any name for the XML file. Unattend.xml is the best practice name.

It would appear that for some reason on your computer, OneCare is the last thing to complete loading itself and advertising itself to the system. It may not even be the last thing that is supposed to load, but ends up being that way. The warning you get is because the portion of XP that the Security Center is built on has completed loading before OneCare has. It does not have any "understanding" of things so it acts very simply. Security Center knows that OneCare is installed and checks to see if it is running. It is not running (completely) yet so it shows you the message. It will keep checking once every x seconds, and shortly, OneCare has finished loading and Security Center sees this and the warning goes away. This may not be something often talked about because everyone's computer is different. It could load up totally different on another person's computer than yours. As long as it is working and you do not get any real errors, you should be fine. However, it is not possible for me to know whether or not your system is vulnerable for those first few minutes before OneCare loads. The engine components may be active and protecting your system, but OneCare not registered to the system. It could be at any stage during that time. Think of a similar thing when you could have a broken Zone Alarm, uninstall it or close it and it would still be protecting the system. So unless you try to debug OneCare you won't know exactly.

1. What packages are in your PE? 2. Also which PE or WAIK version are you using? 3. When you say PE, did you make a winpe.wim with the WAIK or are you referring to the Vista Boot.wim file?

The Killers - Somebody Told Me

Yes I see the information that says 8 beeps is missing video adapter. It may very well be a motherboard issue, but you should first try different system memory to see if that helps.

OK, its because the batch file uses the standard command interpreter. I wonder if its possible to run a batch file through the PE cmd, since it contains the valid path information.

Only on a Tivo!

Are they failing because your XP drives already have NTFS on them?

I see alot of these walkthroughs contain a change directory. Are you guys running this through the regular command prompt instead of the Win PE Tools Command Prompt?

Alternatively, he could also use the Q. option to run 'wpeutil reboot' correct?

I am back to working on my Vista Unattend project, and I got further than before. Now I am getting a parsing error in [auditUser] and [Microsoft-Windows-Deployment]. There is only one thing in auditUser, and that is where I need it to run a batch file using RunSynchronous. But this is failing. I checked the setupact.log and there are no errors or warnings relating to this. Also the setuperr.log is empty. The path to the file is as specified in the walkthrough in the OPK tools for this type of install. <settings pass="auditUser"> <component name="Microsoft-Windows-Deployment" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <RunSynchronous> <RunSynchronousCommand wcm:action="add"> <Order>1</Order> <Path>E:\Distribution\$OEM$ Folders\unlock\business.bat</Path> </RunSynchronousCommand> </RunSynchronous> </component> </settings> Any ideas?

Also, if you have volume licensing, you need to log into the partner portal, the open portal or moo.

Let's call them "Wallbooks"

XP, 98 and then NT 3.51.

http://most-expensive.net/computer-world