Dos newbie

[Flux]

hi there, i'm a beginner in Dos tho i learned some in my class, ya know intermediate commands like cd, md, rd but what i'm really interested in are commands that i could really use. i wanna be a DOS expert.   

[BC_Programmer]

"commands you could really use"...


gee I wonder what that means. Last time I checked managing files was something that could be used.

[mikel]

low meg musta kana????wahahahaha

[BC_Programmer]

low meg musta kana????wahahahaha

I tried my best to make sense of this, but the best I can come up with is it is some sort of off-topic reference to muskeg.

[Flux]

"commands you could really use"...


gee I wonder what that means. Last time I checked managing files was something that could be used.

what i mean is that,commands that are used by experts.

[Flux]

low meg musta kana????wahahahaha

I tried my best to make sense of this, but the best I can come up with is it is some sort of off-topic reference to muskeg.

u got any ideas??...  a list would be helpful.

[Dusty]

Flux - Welcome to the CH forums.

Get used to it - you cannot access Dos in Win XP, Win XP is not built on Dos.  What you can use is a Windows program named Cmd.exe which is a Dos emulator and runs in a window so to call it Dos is a misnomer.  You can, however, run things like DosBox.

Here is a list of NT commands for use at the XP Command Line or in scripts.  Some are available only in XP Pro, others must be extracted from the Resource Kit.

Good luck.

[xcharge50]

type in the cmd (assuming you want to use the virtual dos):
help

It will show you some basic command

[BatchFileCommand]

Google for loops. Those are useful.

[macdad-]

ping -n 1 -w 1000 1.1.1.1 >nul

can be used as a wait command, or just to ping a computer or server on your network.

the 1000 is the timeout, that makes PING a excellent wait command.
and the 1000, is in milliseconds so that would make PING wait for 1 sec.

[BC_Programmer]

the thing I've never really liked about the "ping" method of "sleeping" is that it's a kludge- It works, but it's sort of like how you used to be able to print files in DOS using COPY DOC.TXT PRN.

[fireballs]

I use timeout for pauses but that only works in Vista i think.

FB

[macdad-]

Ping is good as a Wait command, if you have a computer with Win 2000 or older that doesnt have Sleep

[BC_Programmer]

Ping is good as a Wait command, if you have a computer with Win 2000 XP or older that doesnt have Sleep

Fixed 

[Dias de verano]

Ping is good as a Wait command, if you have a computer with Win 2000 XP or older that doesnt have Sleep

And you don't know how to download & deploy a Resource Kit.

[macdad-]

*Smack head*
didnt know you could get it on Microsofts website. 

[Dias de verano]

*Smack head*
didnt know you could get it on Microsofts website. 

http://www.microsoft.com/downloads/details.aspx?familyid=9d467a69-57ff-4ae7-96ee-b18c4790cffd&displaylang=en

[macdad-]

dang thats got a lot of tools 
and they are all command line?

[Dias de verano]

dang thats got a lot of tools 
and they are all command line?

Many of them are.

[macdad-]

awesome, gotta download this.
and thanks for the link 

[Flux]

Flux - Welcome to the CH forums.

Get used to it - you cannot access Dos in Win XP, Win XP is not built on Dos.  What you can use is a Windows program named Cmd.exe which is a Dos emulator and runs in a window so to call it Dos is a misnomer.  You can, however, run things like DosBox.

Here is a list of NT commands for use at the XP Command Line or in scripts.  Some are available only in XP Pro, others must be extracted from the Resource Kit.

Good luck.

dude thanks for the link. i really appreciate your help. im sure these would do.

[GuruGary]

ping -n 1 -w 1000 1.1.1.1 >nul

can be used as a wait command, or just to ping a computer or server on your network.

the 1000 is the timeout, that makes PING a excellent wait command.
and the 1000, is in milliseconds so that would make PING wait for 1 sec.

It is actually a very bad practice to ping an IP address that you don't administer or have control over.  Besides not being polite (depending on how it is used and how often it could be considered a denial of service attach which I know is not your intent), it is not reliable.  For example, I assume by your example that your are expecting 1.1.1.1 to not respond to your ping (ICMP echo request). If the owner of that IP decides to one day enable ICMP echo for that IP address, then your command above would only pause for a few milliseconds.  It is much better to ping something that you have control over, such as localhost, or 127.0.0.1.  You can use

Code: [Select]

ping -n 2 localhost >NULto pause for about 1 second (the number should be n+1 where n is the number of seconds to pause because the 1st reply should be instant, and the others will wait 1 second by default).

I hope nobody takes offense to this ... just trying to point out a better way.

[macdad-]

good point