I would like to aim towards the Command Prompt or whatever the " true " terminology is for entering in command line commands in XP and newer Versions of Windows.
It's not DOS anymore. The current Windows prompt is Windows CMD.
Quote:
I " presume " that there is other Directories on the disk besides #C:\
These other Directories could be in the form of partitions, i do not know.
Other disks, if present, will be available as d:\, e:\, and so forth. Windows Vista and 7 and probably 8 make special recovery/boot partitions that they won't normally show you but should be visible to other operating systems.
Network paths like \\server\path\to\folder are invalid in CMD.
In Windows XP and newer, you can manually assign a drive letter to a share however:
In older versions, I think it's accomplished with the NET SHARE command.
Quote:
So i will point the question to the whole 110 percent of the Disk that Microsoft resides on, and just what is the true and correct terminology and way to work with the white text on black background is.
I would like to actually see with my eyeballs what there is on the Disk. I am working towards installing Linux on a HP Mini and would like to preserve the XP and its dependencies and associates.
Thank you.
Using Linux is an excellent way to do so actually, since it will not be using any of the usual Windows filters on what you see and will not restrict you from system folders.
I'd suggest booting a Knoppix livecd instead of installing Linux, at least at first, so you can get some experience with it.
Lately I've been trying to fix a 1991 Packard Bell, it's been running fine, but it's eating my memory for fun and taking away my pages. Is it worth my time trying to fix it, and is it possible to put new programs on it? thank you (9 Replies)
Hi, In my MSDOS version on windows'98, many keys are not working. I feel that my version is old and I wnt to update it. Can anyone tell me how can i do so.
Please tell me soon.
Thanks a lot.
-Kinnaree
:confused: (1 Reply)
I know nothing of unix and didn't know where to start. I've heard of a DOS to Unix translator, and since I know DOS pretty well, I thought that this program would be perfect. Any help you could give me would be appreciated.
Bryan (1 Reply)
I had just recently experienced, a bad experience... Apperently, a worm got into my computer a created itself in my MS-DOS. No serious damage was done, but I did a little study on it, through my computer. The virus got thought my scan, by coding itself as an HTML file. Don't know why it did that,... (2 Replies)
I have navigated every DOS and UNIX FAQ to find the DOS equivalent of the UNIX ps command (ps -f would be even better) but all listings of DOS<>UNIX commands do not have it (they all have the same basic commands listed). DOS must have a way of detecting running processes and TSRs. mem /c is the... (7 Replies)
Hi
I have a dos batch file in window server where I call a cmd command for creating some db.
this cmd commad is located in e:\data\abcd\xyz.cmd.
Now I call this batch file from unix ssh.sh but my access point is D in window server here I want to change the dos prompt to e:\data\abcd.
in... (3 Replies)
Hello ;
I have a problem running some script on dos .
when i run :
C: ls /temp
ls: cannot access /temp: No such file or directory
but when i run
C: ls \temp
windriver backup remotebackup
also when i run
C: ls temp
windriver backup remotebackup
The... (4 Replies)
Dear all, I am trying to write a unix shell with C++ that is similar to Windows command line. I planned to call it Dosh (DOS-sHell).That means you can directly run dos or win32 console programs with it. It will be distributed according to the license g GPL. Any advice? (This is my first c++ program... (3 Replies)
About 3 days ago our Apache logs started filling with the following errors:
mod_ssl: SSL handshake failed (server <weberver>:443, client 41.235.234.172) (OpenSSL library error follows)
OpenSSL: error:1408A0B7:SSL routines:SSL3_GET_CLIENT_HELLO:no ciphers specified
These initially were... (1 Reply)
Discussion started by: ccj4467
1 Replies
LEARN ABOUT OSF1
mren
mren(1) General Commands Manual mren(1)NAME
mren - mtools utility to rename an existing DOS file
SYNOPSIS
mren [-v] sourcefile targetfile
OPTIONS
Specifies verbose mode. The new file name is displayed if the name supplied is invalid.
DESCRIPTION
The mren command renames an existing file on a DOS file system. You can also use the mren command to rename directories. Reasonable care
is taken to create a valid DOS file name. If an invalid DOS targetname is specified, the mren command changes the name and, if the -v
option is specified, prompts the user to accept or reject the new name.
The path component of the targetfile argument, if supplied, is ignored. That is, you cannot use the mren command to move a file from one
subdirectory to another.
DOS subdirectory names that contain the '/' or '' separator are supported. If you use the '' separator or wildcards, you must enclose
file names in quotes to protect them from the shell.
The mcd command can be used to establish the device and the current working directory (relative to DOS), otherwise the default is A:.
Not all UNIX file names are supported in the DOS world. The mren command may have to change UNIX names to fit the DOS file name conven-
tions. The following table shows some examples of file name conversions:
-----------------------------------------------
UNIX name DOS name Reason for the change
-----------------------------------------------
thisisatest THISISAT file name too long
file.stuff FILE.STU extension too long
prn.txt XRN.TXT PRN is a device name
.abc X.ABC null file name
hot+cold HOTXCOLD illegal character
-----------------------------------------------
RESTRICTIONS
You cannot use the mren command to move a file from one subdirectory to another.
EXIT STATUS
The following exit values are returned: Success. Failure.
ENVIRONMENT VARIABLES
The following environment variables affect the execution of mren: If set, this variable names the file that contains the name of the cur-
rent mtools working directory as established by the mcd command. If this variable is not set, the file $HOME/.mcwd is used.
FILES
Contains the name of the current mtools working directory as established by the mcd command. If this file does not exist, the default
mtools working directory is A:. Executable file
SEE ALSO
Commands: mcd(1), mtools(1)mren(1)