PDA

View Full Version : winnt.exe & winnt32.exe useful command switches


View Full Version : winnt.exe & winnt32.exe useful command switches


infringer
March 4th, 2005, 07:48 PM
---------------------------------------------------
WinNT And WinNT32 Useful switches for installation.
---------------------------------------------------

/a
---

The /a switch commands the setup utility to enable accessibility options.

/e or /cmd
-----------

The /e switch for winnt.exe and the /cmd switch for winnt32.exe allows you
to specify a command to execute at the end of the setup process.

/s
----

The /s switch, followed by the path to a source file allows you to specify
where you want the setup utility to locate Windows 2000/XP source files.
This is used for installations accross a network.

/t or /tempdrive
-----------------

The /t switch for winnt.exe or /tempdrive switch for winnt32.exe allows you
to stipulate the drive that the setup utility uses for temporary installation
files.

/u or /unattend
-----------------

The /u switch for winnt.exe or the /unattend switch for winnt32.exe allows you
to specify an answer file for the setup utility to use instead of being prompted.

This is used to partially or fully automate the install process with windows
2000/XP.

/udf
-----

The /udf switch allows unique values to be set in the case that you install the
operating system on many machines using the automated features.

---------------------------------------------
Useful switches available only to winnt32.exe
---------------------------------------------

/checkpgradeonly
-----------------

The /checkpgradeonly switch runs all steps of upgrade test saving the file in a
.txt file so you can determine if issues will occur before running the installation.

/debug
-------

The /debug switch allows you to trouble shoot issues that occur during an upgrade.

/makelocalsource
-----------------

The /makelocalsource switch to allow for easier updates at a later stage stipulates
that the system copies i386 directory from the cd to the hard drive.

cpugeniusmv
March 4th, 2005, 10:12 PM
Another cool one documented here (http://support.microsoft.com/kb/307654): winnt32.exe /cmdcons

That installs the recovery console as an option in the ntldr...it's convenient to have available without booting from the CD. (Especially on my laptop that has no CD or Floppy drives.)

ferrarimodena360
March 5th, 2005, 04:44 AM
i deleted my ntldr once

no twice

=(

Stownplayer
March 5th, 2005, 05:30 AM
i deleted my ntldr once

no twice

=(



Funny, I'v done that twice also. Don't know how the hell i did it either. So i'm about to get a backup hard drive just for a 1:1 copy of my c drive. All my music is on a seperate hard drive and important docs are on another drive. Still, i would love to know what i did to screw my system up.

infringer
March 5th, 2005, 03:22 PM
NTLDR is the first thing called in the boot process of NT based systems and serves as the bootstrap loader it is the windows the equivilant of the io.sys file it loads the OS into memory and then passes control to the OS it is located in the root directory C:\ it is quite possible that you may have had the folder option set to show system files and show hidden files and folders as well and deleted it when cleaning out the root directory not paying attention to what you were doing. For example deleting all the .chk files from scandisk or chkdisk you may have highlighted this file.

Otherwise I dunnot see how you would have had an issue aside from volume fragmentation or emi or a physical hdd problem such as bad sectors as to why you would have lost this file...

Unless there is some program that was scrpted to do so after you installed it it ran a deletion of this file...

To be on the safe side simply back up your system files in the root directory to a CD so then you can use the DOS copy command to reinstate the system files you lost.

-infringer-

Stownplayer
March 5th, 2005, 04:36 PM
NTLDR is the first thing called in the boot process of NT based systems and serves as the bootstrap loader it is the windows the equivilant of the io.sys file it loads the OS into memory and then passes control to the OS it is located in the root directory C:\ it is quite possible that you may have had the folder option set to show system files and show hidden files and folders as well and deleted it when cleaning out the root directory not paying attention to what you were doing. For example deleting all the .chk files from scandisk or chkdisk you may have highlighted this file.

Otherwise I dunnot see how you would have had an issue aside from volume fragmentation or emi or a physical hdd problem such as bad sectors as to why you would have lost this file...

Unless there is some program that was scrpted to do so after you installed it it ran a deletion of this file...

To be on the safe side simply back up your system files in the root directory to a CD so then you can use the DOS copy command to reinstate the system files you lost.

-infringer-


Your exactly right. Seems like i used a new program to do a system clean, rebooted and "missing ntldr". Shit, i will make damn sure i'm more careful next time. I had a feeling that that program was the cause but i didnt know how.