Metzen

I'm looking to do it so I don't have to do that. This is something lots of people will be using and that makes it a point of failure.

What I'm looking to do sounds simple (to me) but I can't figure it out. I want to take a web page we use internally within our company that is generated by ASP and pipe the HTML file it generates to a text file on the desktop. I want to be able to execute this from the command prompt so I can use it in a batch file. Does anyone here know of a trick to get IE to do that. I've tried "iexplore.exe http://www.google.ca >> test.txt" to no avail. Thanks

Well it IS like that, a cat file points to the fact that it's signed... So I don't understand why Windows says it isn't signed... I'll redownload the Marvell driver and add it again... Bâshrat the Sneaky I've talked to my MS engineer on this one and the Marvell CAT file is the wrong one for that driver. Marvell updated the driver but not the CAT file but kept including the CAT file. What Windows does when you "sysprep -reseal" is remove networking all together. If you launch the sysprep application and set the "shutdown method" to "Quit" and then click Reseal it the computer will reseal ready to be shutdown/rebooted. After this happens simply go into the Device Manager and "scan for new hardware". Windows will detect the network drivers and install the drivers. It will popup saying that the drivers are unsigned, click continue or whatever it is and the drivers will install. Once that's done you can reboot/shutdown for imaging and your network drivers will work successfully on the next boot. The new Marvell driver posted just a couple posts above this one is signed correctly.

setup.exe -k -s -s = must always be last (silent option) -k = no reboot

That's only partially correct or worded really strangely. The BIOS contains a encrypted text string that your SLP files on the recovery media look for. It has to find that string within a specific HEX range in order for SLP to work.

You have to make sure you use a Windows MCE 2005 product key, not a Windows XP Pro product key.

I've only ever seen it in a winbom.ini file, so I don't know if it works in a unattend.txt or winnt.sif file (I suspect it doesn't)...

I use devcon to output all the devices in your system to a text file and then grep for whatever hardware I want to install. It goes something like this: @cd "%userprofile%\desktop" @devcon findall hwids * > hwids.txt @egrep -o -e -E "PCI\\VEN_10DE" hwids.txt @if errorlevel = 1 then GOTO NOFIND @path-to-device-install-executable.exe /silent-switch :NOFIND ECHO "Did not find device blah blah blah >> installlog.txt You can find your device ID code by examining the hwids.txt file or using the Device Manager in SP2 and getting properties on your hardware device > details tab. The beauty of this method is by manipulating the amount of data in your grep string you can search for a company, the device family, or the specific device if you include the whole string. In my example above, egrep searches just for anything with an "Nvidia" hardware ID tag, beit graphics card or chipset and it will attempt an install for both unless I include more information. By including something like PCI\\VEN_10DE\&DEV_4A49\&SUBSYS_00021002" I narrow down the search to only Nvidia Geforce 4 MX graphics cards (this example is fake BTW).

Everest (formerly AIDA32) is better

I guess I can't really help you all that much... Using the english version of XP SP2, I integrated Q834707 by either pointing it to the i386 folder or just one level above it and it did work. Did you download the correct language for the patch?

Could you give the full string that you used to try and integrate the hotfixes into your distribution? ie "KB834707 /integrate:D:\i386" ?

What about Dynamic Updates? That's supposed to do something similar to what your proposing (I've never used it though).

I use msinfo32 to generate a report file and grep the memory size out of that.

nm... I didn't read it correctly the first time. So the /K will install this? I'll have to try that when I get home. Works perfectly.

Bootvis will measure the difference in startup speeds for you.

The product key is checked upon entry. Typing a MCE 2005 product key will install MCE 2005. Typing a XP Pro product key will NOT install MCE components, but will install XP Pro.

I've tried this and it doesn't seem to work. Yes, the product key is legal. Make sure the Product key matches the version of the CD. My MCE2005 media will not work with Retail keys/volume keys, etc. but does work with OEM keys. That is your problem.

You turn it into Pro by entering a Windows XP Professional product key. No messing of files is necessary. Windows XP checks the product key you enter on your Windows MCE media -> if it's a MCE key, it installs MCE, if it's Pro, it installs Pro.

I have not gotten a custom XP theme to work with the "Royal" theme either. Mine has different icons and wallpaper though, I will post it tomorrow and maybe someone can spot where I'm going wrong... This really p***es me off. :/ I guess I should mention that I have not had a problem installing custom themes on XP, it's MCE 2005 that I cannot install custom themes for

I have not gotten a custom XP theme to work with the "Royal" theme either. Mine has different icons and wallpaper though, I will post it tomorrow and maybe someone can spot where I'm going wrong... This really p***es me off. :/

update.exe is not a Windows service file for Automatic Updates...

What RAM Disk did you use to accomplish this? Christian's?

I use an AutoIt Script that terminates all *.cmd windows, this forces a reboot.

What type of motherboard do you have?

Use the following line at the end of your script: EXIT I am assuming that your install script is the STARTNET.CMD file. If it's not, you'll have to find a way to get your batch file to terminate STARTNET.CMD to reboot automatically.