iamtheky

REG DELETE should work fine from the cleanup.cmd REG DELETE HKLM\software\microsoft\windows\currentversion\run /v "%value name%"

Other than deleting the keys from HKLM\software\microsoft\winodws\currentversion\run? and HKCU respectively? I believe common startup group means it is located in the c:\program files\common files and you can always open a run box, type 'msconfig', and uncheck "Load Startup Items."

If you have a user account on both systems why not just open an explorer window and type \\%computername%\c$ and drag and drop what you need? - Or mapping a drive to the 'shared' folder on the destination system. - Or cuteFTP or any other FTPclient and pull it over a dedicated port. I get a much better rate doing mgets than dragging from a remote. And I think the max rate you are going to get in your scenario is the upload rate of the device you are pulling from, but that could be very limited to my experiences.

When I attempt to run a silent install of .Net 3.5 from the runonceex on server 2k3 it throws an error indicating that my certificate service would need to be re-ran. After clicking 'OK' (the only option other than the x) the load finishes normally. Any way to remedy this on the install side? -The same exact silent install works fine on windows xp from the runonceex I am searching for a way to get the install to ignore this moreso than manipulating the O/s or service, but am absolutely hunting any solutions. Update 11/25 am: CrtSrv= OFF CrtSrv_Client=OFF CrtSrv_Server=OFF resulted in the same symptoms. I was hoping that if it was explicitly OFF I would get different results, i did not. Update 11/25 pm: CrtSrv= ON CrtSrv_Client=ON CrtSrv_Server=ON resulted in the same symptoms. I was hoping that if it was explicitly ON I would get different results, i did not.

I get a critical battery warning error during the runonce portion of my server 2k3 install. I can install my modded XP off the same iso (eliminates the image) clean with no battery warning. When I install on a physical drive there is no warning (eliminates the first piece of software in the runonce), so I keep leaning back towards it being a product of the Vbox. So anybody else have an issue with virtualbox throwing erroneous critical battery errors, or any idea of what I am missing?

You can also look in the registry under HKLM\Software\Microsoft\Updates\Windows XP\

I was just talking the difference between your sum and the actual 536870912. If you were getting [Actual - reported sum = +/- 1mi] than that is some seemingly more accurate data than I receive.

You had like 360mb available to the system in your last shot. I believe the 8mb cluberti was referencing was the difference between the Total Ram and the Sum. and if you are down to a 1MB variance you are getting far better readings than I.

in my sif file i add the following to install default ftp pieces only. [Components] ;Internet Information Services iis_common=on iisdbg=off iis_nntp=off iis_nntp_docs=off iis_pwmgr=off iis_smtp=off iis_doc=off iis_ftp=on iis_htmla=off iis_inetmgr=on iis_smtp_docs=off iis_www=off

my bad, i thought the only issue was syntax. create runonce.cmd in your $oem$ and point your cmdlines.txt at it. I have $oem$ Folder root I have cmdlines.txt with two lines [Commands] ".\Install\RunOnce.cmd" I then have an $oem$\install folder that contains the runonce.cmd.

This would install two seperate sets of hotfixes in a window named "hotfixing" during the runonce. SET REGKEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx REG ADD %REGKEY% /V TITLE /D "Hotfixing" /f -pretty title for the window REG ADD %REGKEY%\001 /VE /D "Installing These 2 hotfixes" /f -pretty bold name with an arrow by it showing its being processed REG ADD %REGKEY%\001 /V 1 /D "%path%\KB######.exe /passive /norestart" /f -silent install of KB#1 REG ADD %REGKEY%\001 /V 2 /D "%path%\KB######.exe /passive /norestart" /f -silent install of KB#2 REG ADD %REGKEY%\002 /VE /D "Installing This hotfix" /f REG ADD %REGKEY%\002 /V 1 /D "%path%\KB######.exe /passive /norestart" /f -silent install of KB#3 in its own grouping

Media Player Classic - Home Cinema

This wouldnt be a keyboard that has the numpad bound to the standard keys (like an integrated laptop keyboard)? if so maybe scroll lock or numlock is on by default in the BIOS?

doing a search for use of the runonce, runonceex, and guirunonce will yield massive results. quick and dirty: under i386 built an $oem$ in the root of the $oem$ placed the following File Name: cmdlines.txt File contents -------------------------------- [Commands] ".\Install\RunOnce.cmd" -------------------------------- Then made an "$oem$\install' folder and placed the runonce.cmd and added these lines ------------------------------------------------------------------------------------------------------------------------------------------------------- SET REGKEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx REG ADD %REGKEY%\012 /VE /D "Playing with Users and Groups" /f -group title strictly cosmetic, nice little arrow next to active set REG ADD %REGKEY%\012 /V 12 /D "net localgroup auditors /add" /f -creates an auditors group REG ADD %REGKEY%\012 /V 13 /D "net localgroup auditors admin /add" /f -adds user 'admin' to the auditors group REG ADD %REGKEY%\012 /V 14 /D "CACLS c:\windows\system32\config /E /T /C /G "auditors":F" /f -grants rights to auditors on the config folder REG ADD %REGKEY%\012 /V 15 /D "NET USER guest /passwordreq:yes" /f -makes the guest account require a password REG ADD %REGKEY%\012 /V 16 /D "NET USER IUSR_%computername% /passwordreq:yes" /f -makes the IUSR require a password --------------------------------------------------------------------------------------------------------------------------------------------------------- If all you are doing is removing users then its probably easier to test on your production box. build the .cmd first, add the runonce lines, execute, and reboot. You should see it fire off when you log in, I use the runonceex because it makes a pretty dialog that lets the user know something is occuring. Also the /VE helps when you are doing many minutes worth of various loads and the user might believe something has gone awry, also helps with troubleshooting.

I run my NET and CACLS during the runonceex portion, that way I dont have to take stabs at where in the install the pieces are created and able to be manipulated. *you managed to spell helpassistant wrong in both examples, make sure that is not the case in your cmd.*

Probably dont want to dupe your question all over the board, its bad practice. Ive had cleaner loads installing WMP11 and its hotfixes from the runonce.

That number minus the RAM your Hardware utilizes. Try the Performance tab and look at the Physical Memory block. That available number is probably a little more accurate. The 'Total' in that block already subtracts your peripherals. Peak MEM USAGE= the max amount of RAM that application has allocated at any one time during the session? System Cache= System Cache tells you how much memory is being used as disk cache (memory acting as the hard disk essentially, much faster access)

I use a combo of command line arguments from diskpart (to partition, naturally) and sdelete (to offer formatting options). I would be suspect of anyone who said there was a preferred method of disk preparation. I also throw my vote to SUN virtualbox. I have to build and test many different operating system configurations, and vbox routinely offers the most flexibility and a more responsive community - for $0.

http://factormystic.net/utils/defaultprogramseditor/ This utility seems to pretty much own file extensions and associations.

load them from the runonce? it aint pretty but it would eliminate Nlite. And if you install symantec prior to them, it should pop when/if the culprit driver loads.

The chipset is the first entry, that entry ends with a space. My bet goes on the space. DriverPolicySigning=ignore only gets rid of the prompts. If you were not receiving prompts during install they were never being loaded.

Try ".\oeminf.cmd"

I install them from the runonce. There is no need for dotnet2 or 3 as 3.5 installs everything from 2 up. I recommend the net stop between as I had problems with the msiexec hanging after install and blocking any subsequent installs. REG ADD %REGKEY%\014 /VE /D "installing dotnet11" /f REG ADD %REGKEY%\014 /v 14 /D "path:\dotnet11.exe /q /norestart" /f REG ADD %REGKEY%\015 /v 15 /D "net stop msiserver" /f REG ADD %REGKEY%\016 /VE /D "installing dotnet35" /f REG ADD %REGKEY%\016 /v 16 /D "path:\dotnet35.exe /q /norestart" /f Some hotfixes in my load are done in the same manner, like WMP11's, since it is not present until after the load. REG ADD %REGKEY%\019 /v 19 /D "path:\KB954154.exe /passive /norestart" /f I imagine you could do something similar for the ones that will not integrate.