07-13-2007
I was in this situation a little while ago. I removed the C drive, installed another disk and reinstalled XP on the new disk. Then I mounted the old C drive as a D drive. The old drive was in bad shape from a hardware standpoint, but I was able to copy some files that I wanted from it.
8 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi.
I need to run old full-screen text-mode application under X-Windows. (By the way it is touch-screen calibrator firmware). The screen resolution is to be 1280x1024 exactly. The program expect text-mode geometry 80x25. Running xterm (no window manager) I have adjusted the font pararameters to... (3 Replies)
Discussion started by: shestero
3 Replies
2. SCO
I am unbale to uncompress a file which was compress then moved to another pc in ascii mode instead of binary mode. Is there any way to recover it. Please help us. While uncompress it is giving corrupt input. (3 Replies)
Discussion started by: raj2610
3 Replies
3. HP-UX
hi,
i figured why i need to boot in MMB,some of which are missing or corrupt LABEL (LIF labeL ,i guess) on the boot disk.
To explicitly corrupt this entry i think a simple dd will work.
ok let me elaborate this issue:
i need to check this functionality.
so i have one LVM boot disk
and one... (0 Replies)
Discussion started by: mxms755
0 Replies
4. Filesystems, Disks and Memory
My CD drive isn't working. So, is there any way to create windows recovery/repair software in flash drive/usb. This is the s/w which we use if system fails to boot. (1 Reply)
Discussion started by: ravisingh
1 Replies
5. Boot Loaders
I successfully created a bootable windows 7 repair usb.
Please clarify me:
I rebooted my system via USB. windows repair window appeared. There were 5 options. I opted 'windows memory diagnostic' and it worked fine. There was an option named 'start up repair'. This option can be used if windows... (2 Replies)
Discussion started by: ravisingh
2 Replies
6. Boot Loaders
I need to make a bootable usb of windows 7 repair disc iso file so that I can use it in case my system doesn't boot up. On net I am getting complete windows 7 OS iso but I need only the repair disc for making bootable iso. I am not sure whether I used right word by using the word disc here... (3 Replies)
Discussion started by: ravisingh
3 Replies
7. Windows & DOS: Issues & Discussions
Getting error while creating windows recovery disc
Please see attachment (5 Replies)
Discussion started by: ravisingh
5 Replies
8. Windows & DOS: Issues & Discussions
I have a 1TB HD, suspect it had bad sectors and blocks...
it was pre-installed with windows 8.0..
I was able to boot up ubuntu and looked at the partitions and run a badblocks comand to verify secotors, after getting a serious of Input and Output errors mounting the partition and doing any... (2 Replies)
Discussion started by: ppchu99
2 Replies
HD(4) Linux Programmer's Manual HD(4)
NAME
hd - MFM/IDE hard disk devices
DESCRIPTION
The hd* devices are block devices to access MFM/IDE hard disk drives in raw mode. The master drive on the primary IDE controller (major
device number 3) is hda; the slave drive is hdb. The master drive of the second controller (major device number 22) is hdc and the slave
hdd.
General IDE block device names have the form hdX, or hdXP, where X is a letter denoting the physical drive, and P is a number denoting the
partition on that physical drive. The first form, hdX, is used to address the whole drive. Partition numbers are assigned in the order
the partitions are discovered, and only nonempty, nonextended partitions get a number. However, partition numbers 1-4 are given to the
four partitions described in the MBR (the "primary" partitions), regardless of whether they are unused or extended. Thus, the first logi-
cal partition will be hdX5. Both DOS-type partitioning and BSD-disklabel partitioning are supported. You can have at most 63 partitions
on an IDE disk.
For example, /dev/hda refers to all of the first IDE drive in the system; and /dev/hdb3 refers to the third DOS "primary" partition on the
second one.
They are typically created by:
mknod -m 660 /dev/hda b 3 0
mknod -m 660 /dev/hda1 b 3 1
mknod -m 660 /dev/hda2 b 3 2
...
mknod -m 660 /dev/hda8 b 3 8
mknod -m 660 /dev/hdb b 3 64
mknod -m 660 /dev/hdb1 b 3 65
mknod -m 660 /dev/hdb2 b 3 66
...
mknod -m 660 /dev/hdb8 b 3 72
chown root:disk /dev/hd*
FILES
/dev/hd*
SEE ALSO
chown(1), mknod(1), sd(4), mount(8)
COLOPHON
This page is part of release 3.27 of the Linux man-pages project. A description of the project, and information about reporting bugs, can
be found at http://www.kernel.org/doc/man-pages/.
Linux 1992-12-17 HD(4)