• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

DOS/command line commands

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
Originally posted by: cubby1223
Run this:
%Windir%\Help\ntcmds.chm

This will show you all commands with instructions, so you don't have to reference a website. My favorite is of course: format c: /u
Click to expand...

RTFM, I love it!!!

Do take a sec to turn your autocompletion (ala *nix) on though. It's the way to go.
 
Originally posted by: hopejr
Originally posted by: Nothinman
Frankly the windows CLI tools are terrible. Grab a copy of Knoppix or Gnoppix and boot into Linux, get a feel for what real CLI tools should be like. Sometimes even when the tools are the same the Windows ones find areas to suck in, like traceroute (tracert on Windows) on unix takes 0.5s to go 8 hops but on Windows that would take easily 10s.
Click to expand...

:thumbsup:
Click to expand...

:thumbsup:

You might try Pathping instead of tracert. Depending on what you're trying to accomplish it works much better.

couple commands I like simply because they are more usefull or powerful than their GUI counterparts:

diskpart (especially with the 'extend' sub command)
cacls (especially with the /E switch)
ntdsutil
pushd (for that quick jump to a UNC path without doing a Net Use *)
popd
net start, net stop (Pretty much all the net commands actually)
runas (to leverage your admin account)
start (launch stuff with pre-set priorities etc)
xcopy (especially with the /X and implied /O switch. It's rare I need robocopy anymore)

I use a lot of commands from the run line that aren't necessarily dos too.
compmgmt.msc
gpedit.msc
etc..



 
netsh

useful for network config scripts

netsh interface ip set address local static 192.168.XXX.XXX 255.255.255.0 192.168.XXX.XXX 1 (sets the IP address, subnet mask, and gateway. HINT: replace the X's : )
netsh interface ip set dns local static 192.168.XXX.XXX primary (sets your primary DNS to a static address)
netsh interface ip add dns local 192.168.XXX.XXX index=2 (sets your secondary DNS)

netsh interface ip set address local source=dhcp - sets local area connection to obtain IP automatically
netsh interface ip set dns local source=dhcp - sets local area connection to obtain DNS automatically

couple notes:

I'm not sure why you have to use the command add instead of set for the seconadry DNS....I just couldn't get it to work any other way.
The word 'local' in the command refers to the name of the connection 'local area connection' if you have it named something else like 'my lan connection' you'll have to specify that

I've used these commands to create a script that will allow people to easily go from our network that uses static IP's to their home connection or hotel connection where most people use DHCP....That way they don't have to remember their settings or even know how to change them.






 
I think "net file" was forgotten? I believe it tells you what files on your computer are being accessed by other people on your network/domain. Correct me if I'm wrong. Just one I didn't see int he list.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top