Sponsored Content
Operating Systems Linux Fedora Creating Windows 7 image to run in VirtualBox Post 302741585 by jimbob01 on Sunday 9th of December 2012 08:32:28 AM
Old 12-09-2012
Thanks for your reply, DukeNuke2.

I've read that before, and found it a good starting point. However, I am still a bit confused!

My hard drive is 500GB, and I only need say around 50GB for the image for Windows. But, if I use the 'dd' command, then am I right in thinking that this will copy the entire drive and not only the partition where Windows is installed ? Is it possible to only image the partition that contains Windows or am I better using a third party utility for this ?

Thanks for any help

Jim
 

5 More Discussions You Might Find Interesting

1. Solaris

help needed in creating an image from a 7za compressed file

Hi all, I have been working on a few files that have been 7za compressed.(which are a part of an OS) Now after extracting the file and doing manipulations i did a putback. But when i create an image and burn it onto the disk to check if my changes are working... I get error at boot time. Now... (0 Replies)
Discussion started by: wrapster
0 Replies

2. Solaris

Creating an image of a mirrored disks

Hi guys, I havent done this before but iam trying to create an image of a mirrorred drive. Correct me if iam wrong, but when i have two disks setup in raid configuration and have them mirrored in solaris. It then defines at one entity. How would i create a "flar" image of that one entity... (3 Replies)
Discussion started by: tlee
3 Replies

3. Virtualization and Cloud Computing

Creating VirtualBox-Image as "harddisk" by shell-script

Hello, I'm trying to create a VirtualBox "harddisk" and put an dd-image into it. This image shoudn't work as a virtual maschine, I just want to be able to mount it to an folder. How can I do this with an shell script? Sebi ---------- Post updated at 10:36 AM ---------- Previous update... (0 Replies)
Discussion started by: Sebi0815
0 Replies

4. Solaris

Creating soalris 9 ISO image with use of downloaded OS

Hi Folks, I have downloaded OS on one of my server and i want to create bootable solaris 9 ISO image with use of this...I need to use this image to other server.,Could you please let us know how we will create ISO image with below OS image.. # cd solaris_9 # ls -alrt total 128 drwxr-xr-x ... (3 Replies)
Discussion started by: susindram
3 Replies

5. Red Hat

Trouble creating RHEL 6.5 bootable image with custom kickstart file

Hi everyone, I have a custom kickstart file from a software vendor and I'm trying to package that with a RHEL 6.5 and then attach it to a VM and install RHEL with the settings in the kickstarter file. I'm doing this from a windows PC using an app called InfraRecorder. I've extracted the... (0 Replies)
Discussion started by: 911Eric
0 Replies
FD(4)							     Kernel Interfaces Manual							     FD(4)

NAME
fd - floppy disk DESCRIPTION
The fd* devices refer to the Floppy disk driver using the NEC PD765 floppy disk controller. These diskettes are arrays of 512 byte sec- tors, although Minix always works with two sectors at a time due to its 1024 byte block size. You can read or write any number of bytes however, Minix takes care of cutting and pasting incomplete blocks together. The driver is normally configured for two floppy disk devices fd0 and fd1. It can handle two more, but it is unlikely that the average PC can. On the first access to an fd device (by open(2) or mount(2)), the driver will execute a series of read tests to determine the floppy type. This works ok for all floppy types except the true 360k type, because it is indistinguishable from the 720k type. This only means that the size of the floppy is not estimated right. Bits 2-6 of the minor device number may be set to the floppy disk type to make it known to the driver what type of diskette it is reading or writing. The non-auto devices should be used for formatting, or when one wants to be absolutely sure that the device is accessed right. These devices exist for drive 0: type device minor media 0 fd0 0 autodetect 1 pc0 4 360k, 5.25" 2 at0 8 1.2M, 5.25" 3 qd0 12 360k in a 720k, 5.25" drive 4 ps0 16 720k, 3.5" 5 pat0 20 360k in a 1.2M, 5.25" drive 6 qh0 24 720k in a 1.2M, 5.25" drive 7 PS0 28 1.44M, 3.5" Type 4 may also be used for the rarely seen 720k, 5.25" floppies (type 2 made them obsolete fast.) Note that these "types" only describe the floppies from a software point of view, type 1 and 4 drives use the same parameters. If the format bit (bit 7) is set, then the driver interprets write commands as track formatting requests. This is used by the format(1) command. If the type bits are set to 28, 29, 30, or 31, then the driver uses a partition table found in sector 0 to partition the floppy. The par- titions of fd0 may be accessed as fd0a through fd0d. See hd(4) for a description of the partition table, and associated ioctl commands. FILES
/dev/fd[0-3], /dev/pc[0-3], /dev/at[0-3], /dev/qd[0-3], /dev/ps[0-3], /dev/pat[0-3], /dev/qh[0-3], /dev/PS[0-3], /dev/fd[0-3][a-d] SEE ALSO
format(1), hd(4), part(8). BUGS
The driver does not know the size of a 360k diskette in a 360k 5.25" drive, because it uses the 720k parameters for it. So it will happily try to read past the end making all kinds of interesting noises. It's a good thing these drives are practically obsolete. The partition table is only read when the drive motor is off and only for an auto or partition device. The driver assumes that a floppy in a drive with a running motor can't have been replaced all of a sudden. AUTHOR
Kees J. Bot (kjb@cs.vu.nl) FD(4)
All times are GMT -4. The time now is 12:48 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy