Sponsored Content
Full Discussion: Anatomy of DOS
Special Forums Windows & DOS: Issues & Discussions Anatomy of DOS Post 302597270 by cowLips on Thursday 9th of February 2012 09:34:09 PM
Old 02-09-2012
Anatomy of DOS

Hello
Where is there a good source to receive an understanding of MS DOS.
I have tried google books " MS DOS ", no luck.
i did try " command prompt " , no luck.
the subject " seems " to be dry. no water flowing in that creek.
what would be good search terms.
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.
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.
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.

Last edited by cowLips; 02-09-2012 at 10:49 PM.. Reason: expand on question
 

10 More Discussions You Might Find Interesting

1. Windows & DOS: Issues & Discussions

What if I have a really, really, really, old DOS?

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)
Discussion started by: Saz43
9 Replies

2. Windows & DOS: Issues & Discussions

DOS Keys not working

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)
Discussion started by: kinnaree
1 Replies

3. UNIX for Dummies Questions & Answers

DOS to Unix translator

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)
Discussion started by: bferguson
1 Replies

4. Windows & DOS: Issues & Discussions

Viruses sneeking through MS-DOS?

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)
Discussion started by: hdk_mkr
2 Replies

5. UNIX for Dummies Questions & Answers

DOS command for ps

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)
Discussion started by: dancingfool
7 Replies

6. Windows & DOS: Issues & Discussions

Ms-DOS Download

Please where can i get the origanal MS-DOS, I need it. Not mandatory but botting from a floppy is best. (9 Replies)
Discussion started by: Irish Jimmy
9 Replies

7. Shell Programming and Scripting

how I change dir in dos

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)
Discussion started by: Jamil Qadir
3 Replies

8. Linux

dos-path / un-dos-path compatibility with cygwin

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)
Discussion started by: mulder20
4 Replies

9. Linux

Dos shell

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)
Discussion started by: elgarteo95
3 Replies

10. Cybersecurity

What I think is a DoS attack

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
idisk(1M)																 idisk(1M)

NAME
idisk - create partitions for disks on an Integrity system SYNOPSIS
partition_description_file}] device DESCRIPTION
creates operating system partitions for disks on an Integrity system. It reads in the partition information from a data file that may be specified in the command string or redirected from stdin. By default, operates in read-only mode and displays the partition information that is currently on the disk. To write new partition infor- mation on the disk the user must specify the option. Options recognizes the following options: Print the primary EFI partition header and partition tables. Print the alternate EFI partition header and partition tables. Print the legacy partition table that resides in the master boot record. writes partition information for the first four partition in the partition table in used by legacy DOS and Win- dows. This information is used as a backup in the event all the EFI information is corrupted. Print the first usable and last usable block numbers that are available to create partitions. First usable is the first block a partition can start on. Last usable is the last block that can be contained in a partition. These numbers are relative to the whole disk and do not take into account any partitions that may exist. They represent the total disk space that can be partitioned. Use the option to only print the values without headings. Work silently. No user prompts or warnings. For use in shell scripts. Validate EFI partition information. Does the same checks the driver does verifying that both the primary and alternate EFI partition headers and tables are correct. Returns two if either is bad and zero if both are correct. Restore the EFI partition headers and tables. This option checks both the primary header and tables and the alternate header and tables. If one is found bad it is restored from the other good ver- sion. One of either the primary or alternate header and tables must be good for this option to succeed. The option must be specified for information to be written to the disk. Remove all EFI partition headers and tables from the disk. This option also destroys the information contained in the MBR (master boot record). The option must be specified for information to be written to the disk. The partition_description_file contains the number of partitions to be created and the type and requested size of each partition. The filename may be specified here or redirected from stdin when the dash is used. Enable write mode. By default operates in read-only mode. To create and write partition information to the disk you must specify the option. Partition Description File The first entry in the partition description file is the number of partitions to create. The maximum number of partitions allowed is 12. This is followed by a line containing the type and size for each of the partitions. Recognized partition types are: and At least one EFI partition is required to create a valid partition table. Size may be specified in megabytes or as a percentage of the whole disk. Internally, creates the partitions whose size is specified in MB first then creates those whose size was specified as a percentage. Those partitions specified as a percent are assigned space from what is available after the MB partitions are created. If the size of a parti- tion is specified as 100% then all space remaining is assigned to that partition. An example partition description file is shown below: The first entry specifies the number of partitions to create. The second specifies an EFI partition of 100 megabytes. The last entry specifies a HPUX partition consisting of all the remaining space on the disk after the EFI partition has been created. When creating partitions, the device file name must be that of the whole disk. Legacy device files must not have any partition number bits set in the minor number. For legacy disk devices, the last eight bits of the minor number represent the option bits. For Integrity system disks, the last four option bits are used to indicate the partition number. Since there are only four bits for parti- tion number, only one to fifteen partitions are supported. For example, a device node with a minor number of 0x008001 would indicate a disk at target eight, partition number one. A minor number of 0x00500F would indicate a disk at target 5 partition fifteen. A minor num- ber with no partition bits set would indicate the whole disk (for example, 0x008000 would be the same disk as above but represent the whole disk and not a partition). Persistent device special files do not use or contain minor number information. A detailed description on persistent device special files can be found in intro(7). Note: For partitions created by device special files must be created for each legacy hardware path to the disk and for the LUN hardware path using or (see intro(7) for details on legacy and agile modes). If legacy mode is disabled (see the descrip- tion of the option in rmsf(1M)), device special files must only be created for the LUN hardware path. Note has been ported to Windows NT 4.0 and 2000. RETURN VALUE
Exit values are: Successful completion. Error condition occurred. EXAMPLES
Create the partitions specified in the above description file, printing only the primary partition information: Create the partitions specified in the above description file, printing only the primary partition information using a persistent device special file (see intro(7)): Create the partitions specified in the above description file, printing all available information (default), redirecting input from stdin: Only read the disk, printing all tables (default) on the disk: Get the first and last usable block for partitioning on the disk: Destroy all partition information on the disk: Restore partition information from either a good primary or alternate header or table to the header or table that is bad: AUTHOR
was developed by HP. SEE ALSO
insf(1M), mksf(1M), efi(4), intro(7). Integrity Systems Only idisk(1M)
All times are GMT -4. The time now is 09:27 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy