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:
Code:
REM assign a network folder to drive X
x: \\server\path\to\folder
REM detatch the network folder
x: /delete
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 REDHAT
sd
SD(4) Linux Programmer's Manual SD(4)NAME
sd - Driver for SCSI Disk Drives
SYNOPSIS
#include <linux/hdreg.h> /* for HDIO_GETGEO */ #include <linux/fs.h> /* for BLKGETSIZE and BLKRRPART */
CONFIG
The block device name has the following form: sdlp, where l is a letter denoting the physical drive, and p is a number denoting the parti-
tion on that physical drive. Often, the partition number, p, will be left off when the device corresponds to the whole drive.
SCSI disks have a major device number of 8, and a minor device number of the form (16 * drive_number) + partition_number, where drive_num-
ber is the number of the physical drive in order of detection, and partition_number is as follows:
partition 0 is the whole drive
partitions 1-4 are the DOS "primary" partitions
partitions 5-8 are the DOS "extended" (or "logical") partitions
For example, /dev/sda will have major 8, minor 0, and will refer to all of the first SCSI drive in the system; and /dev/sdb3 will have
major 8, minor 19, and will refer to the third DOS "primary" partition on the second SCSI drive in the system.
At this time, only block devices are provided. Raw devices have not yet been implemented.
DESCRIPTION
The following ioctls are provided:
HDIO_GETGEO
Returns the BIOS disk parameters in the following structure:
struct hd_geometry {
unsigned char heads;
unsigned char sectors;
unsigned short cylinders;
unsigned long start;
};
A pointer to this structure is passed as the ioctl(2) parameter.
The information returned in the parameter is the disk geometry of the drive as understood by DOS! This geometry is not the physical
geometry of the drive. It is used when constructing the drive's partition table, however, and is needed for convenient operation of
fdisk(1), efdisk(1), and lilo(1). If the geometry information is not available, zero will be returned for all of the parameters.
BLKGETSIZE
Returns the device size in sectors. The ioctl(2) parameter should be a pointer to a long.
BLKRRPART
Forces a re-read of the SCSI disk partition tables. No parameter is needed.
The scsi(4) ioctls are also supported. If the ioctl(2) parameter is required, and it is NULL, then ioctl() will return -EINVAL.
FILES
/dev/sd[a-h]: the whole device
/dev/sd[a-h][0-8]: individual block partitions
SEE ALSO scsi(4)
1992-12-17 SD(4)