Creating more than 2 partitions after Boot camp

Original bootcamp setup requires one partition from which it creates an additional windows volume. We would like to have 4 partitions to allow for student storage on each platform in addition to Mac and Win OS volumes. Prior to image deployment in a lab situation, can you partition client machines so there are more than 2? Would having 4 partitions somehow interfere with Bootcamp functionality?
Thank you!

You don't HAVE to use Boot Camp Assistant to create the Windows partition, it's just easier. A number of threads describe alternative approaches (which I've never tried myself). Look in particular for threads regarding three-way booting, especially in the Boot Camp beta forum. The Windows partition may have some constraints on it; if so, the posts probably describe the process.
You MIGHT also consider virtualization, such as VMware Fusion or Parallels, depending on what you needs/requirements are. They don't use a partition at all, so there's no issue of 2 versus N.
Doug

Similar Messages

Not able to create More than 1 Partition in USB Drive using kernel32 and DeviceIoControl

I have successfully created 2 or more partitions in USB drive using DeviceIoControl in C++. Now I am trying to convert this code into C# using kernel32 and DeviceIoControl. But I am not getting more than 1 partition. Can anybody tell me what is wrong
with this code?
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Threading.Tasks;
using System.Diagnostics;
using System.Runtime.InteropServices;
namespace PartitionWrapper
public class IOWrapper
public static bool CreatePartitions(string selectedDrive)
bool RetCode = false;
try
bool bSuccess = false;
uint dwBytesReturned = 0;
IntPtr hDisk = OpenVolume(selectedDrive);
if (hDisk == null || hDisk == FSConstants.INVALID_HANDLE_VALUE)
RetCode = false;
goto FINAL;
bSuccess = FSStructures.DeviceIoControl(hDisk, FSConstants.IOCTL_DISK_DELETE_DRIVE_LAYOUT, IntPtr.Zero, 0, default(IntPtr), default(uint), ref dwBytesReturned);
// Get the partition information
uint PartitionInfomations = (uint)(Marshal.SizeOf(typeof(FSStructures.DRIVE_LAYOUT_INFORMATION_EX)) + 3 * Marshal.SizeOf(typeof(FSStructures.PARTITION_INFORMATION_EX)));
byte[] DBuffer = new byte[PartitionInfomations];
GCHandle handle = GCHandle.Alloc(DBuffer, GCHandleType.Pinned);
FSStructures.DRIVE_LAYOUT_INFORMATION_EX pDriveLayout = (FSStructures.DRIVE_LAYOUT_INFORMATION_EX)Marshal.PtrToStructure(handle.AddrOfPinnedObject(), typeof(FSStructures.DRIVE_LAYOUT_INFORMATION_EX));
IntPtr pDriveLayoutPtr = Marshal.AllocHGlobal(Marshal.SizeOf(pDriveLayout));
Marshal.StructureToPtr(pDriveLayout, pDriveLayoutPtr, false);
// bSuccess = FSStructures.DeviceIoControl(hDisk, FSConstants.IOCTL_DISK_GET_DRIVE_LAYOUT_EX, default(IntPtr), default(uint), pDriveLayoutPtr, PartitionInfomations, ref dwBytesReturned);
pDriveLayout = (FSStructures.DRIVE_LAYOUT_INFORMATION_EX)Marshal.PtrToStructure(pDriveLayoutPtr, typeof(FSStructures.DRIVE_LAYOUT_INFORMATION_EX));
if (bSuccess || dwBytesReturned != PartitionInfomations)
RetCode = true;
else { RetCode = false; goto FINAL; }
pDriveLayout.PartitionEntry = new FSStructures.PARTITION_INFORMATION_EX[0x16];
pDriveLayout.PartitionStyle = FSStructures.PARTITION_STYLE.MasterBootRecord;
pDriveLayout.PartitionCount = 4;
pDriveLayout.DriveLayoutInformatiton.Mbr.Signature = 0xA4B57300;
pDriveLayout.PartitionEntry[0] = new FSStructures.PARTITION_INFORMATION_EX();
pDriveLayout.PartitionEntry[0].PartitionStyle = FSStructures.PARTITION_STYLE.MasterBootRecord;
pDriveLayout.PartitionEntry[0].Mbr.BootIndicator = true;
pDriveLayout.PartitionEntry[0].Mbr.RecognizedPartition = true;
pDriveLayout.PartitionEntry[0].Mbr.PartitionType = 0x0B;
pDriveLayout.PartitionEntry[0].PartitionNumber = 1;
pDriveLayout.PartitionEntry[0].StartingOffset = 32256;
pDriveLayout.PartitionEntry[0].PartitionLength = 3221225472;
pDriveLayout.PartitionEntry[0].RewritePartition = true;
pDriveLayout.PartitionEntry[0].Mbr.HiddenSectors = 32256 / 512;
pDriveLayout.PartitionEntry[1] = new FSStructures.PARTITION_INFORMATION_EX();
pDriveLayout.PartitionEntry[1].PartitionStyle = FSStructures.PARTITION_STYLE.MasterBootRecord;
pDriveLayout.PartitionEntry[1].Mbr.BootIndicator = false;
pDriveLayout.PartitionEntry[1].Mbr.RecognizedPartition = true;
pDriveLayout.PartitionEntry[1].Mbr.PartitionType = 0x0B;
pDriveLayout.PartitionEntry[1].PartitionNumber = 2;
pDriveLayout.PartitionEntry[1].StartingOffset = 32256 + 3221225472;
pDriveLayout.PartitionEntry[1].PartitionLength = 2147483648; //2147483648;//3221225472;
pDriveLayout.PartitionEntry[1].RewritePartition = true;
pDriveLayout.PartitionEntry[1].Mbr.HiddenSectors = 32256 / 512;
for (int i = 0; i < pDriveLayout.PartitionEntry.Length; i++)
pDriveLayout.PartitionEntry[i].RewritePartition = true;
try
bSuccess = FSStructures.DeviceIoControl(hDisk, FSConstants.IOCTL_DISK_SET_DRIVE_LAYOUT_EX, ref pDriveLayout, PartitionInfomations, default(IntPtr), default(uint), ref dwBytesReturned);
catch (Exception ex)
if (bSuccess)
RetCode = true;
else { RetCode = false; }
bSuccess = FSStructures.DeviceIoControl(hDisk, FSConstants.IOCTL_DISK_UPDATE_PROPERTIES, IntPtr.Zero, 0, default(IntPtr), default(uint), ref dwBytesReturned);
if (bSuccess)
RetCode = true;
else { RetCode = false; }
FINAL:
// Close the disk handle.
if (hDisk != null && hDisk != FSConstants.INVALID_HANDLE_VALUE)
FSStructures.CloseHandle(hDisk);
catch { return false; }
return RetCode;
private static IntPtr OpenVolume(string DeviceName)
try
IntPtr hDevice;
hDevice = FSStructures.CreateFile(
@"\\.\" + DeviceName,
FSConstants.GENERIC_EXECUTE | FSConstants.GENERIC_READ | FSConstants.GENERIC_WRITE | FSConstants.FILE_SHARE_READ | FSConstants.FILE_SHARE_WRITE,
FSConstants.FILE_SHARE_WRITE,
IntPtr.Zero,
FSConstants.OPEN_EXISTING,
0,
IntPtr.Zero);
if ((int)hDevice == -1)
throw new Exception(Marshal.GetLastWin32Error().ToString());
return hDevice;
catch { return FSConstants.INVALID_HANDLE_VALUE; }
internal static class FSConstants
public const uint FILE_SHARE_READ = 0x00000001;
public const uint FILE_SHARE_WRITE = 0x00000002;
public const uint OPEN_EXISTING = 3;
public const int GENERIC_EXECUTE = 0x10000000;
public const uint GENERIC_READ = (0x80000000);
public const uint GENERIC_WRITE = (0x40000000);
public static IntPtr INVALID_HANDLE_VALUE = new IntPtr(-1);
public const uint IOCTL_DISK_GET_DRIVE_LAYOUT_EX = 0x00070050;
public const uint IOCTL_DISK_SET_DRIVE_LAYOUT_EX = 0x7C054;
public const int IOCTL_DISK_UPDATE_PROPERTIES = 0x70140;
public const int IOCTL_DISK_DELETE_DRIVE_LAYOUT = 0x0007c010;
public const int IOCTL_DISK_CREATE_DISK = 0x7C058;
internal static class FSStructures
[DllImport("kernel32.dll", EntryPoint = "CreateFile", SetLastError = true)]
public static extern IntPtr CreateFile(
string lpFileName,
uint dwDesiredAccess,
uint dwShareMode,
IntPtr lpSecurityAttributes,
uint dwCreationDisposition,
uint dwFlagsAndAttributes,
IntPtr hTemplateFile);
[DllImport("kernel32.dll", SetLastError = true)]
public static extern int CloseHandle(IntPtr hObject);
[DllImport("kernel32.dll", SetLastError = true)]
public static extern bool DeviceIoControl(
IntPtr hDevice,
uint dwIoControlCode,
[Optional]ref DRIVE_LAYOUT_INFORMATION_EX lpInBuffer,
uint nInBufferSize,
[Optional] [Out] IntPtr lpOutBuffer,
uint nOutBufferSize,
[Optional] ref uint lpBytesReturned,
[Optional] IntPtr lpOverlapped);
[DllImport("kernel32.dll", SetLastError = true)]
public static extern bool DeviceIoControl(
IntPtr hDevice,
uint dwIoControlCode,
IntPtr lpInBuffer,
uint nInBufferSize,
[Optional] [Out] IntPtr lpOutBuffer,
uint nOutBufferSize,
[Optional] ref uint lpBytesReturned,
[Optional] IntPtr lpOverlapped);
[StructLayout(LayoutKind.Sequential)]
public struct DRIVE_LAYOUT_INFORMATION_EX
public PARTITION_STYLE PartitionStyle;
public int PartitionCount;
public DRIVE_LAYOUT_INFORMATION_UNION DriveLayoutInformatiton;
[MarshalAs(UnmanagedType.ByValArray, ArraySubType = UnmanagedType.Struct, SizeConst = 0x16)]
public PARTITION_INFORMATION_EX[] PartitionEntry;
[StructLayout(LayoutKind.Sequential)]
public struct PARTITION_INFORMATION_EX
[MarshalAs(UnmanagedType.U4)]
public PARTITION_STYLE PartitionStyle;
public long StartingOffset;
public long PartitionLength;
public int PartitionNumber;
public bool RewritePartition;
public PARTITION_INFORMATION_MBR Mbr;
public PARTITION_INFORMATION_GPT Gpt;
[StructLayout(LayoutKind.Sequential)]
public struct PARTITION_INFORMATION_MBR
public byte PartitionType;
[MarshalAs(UnmanagedType.U1)]
public bool BootIndicator;
[MarshalAs(UnmanagedType.U1)]
public bool RecognizedPartition;
public uint HiddenSectors;
[StructLayout(LayoutKind.Sequential, CharSet = CharSet.Unicode)]
public struct PARTITION_INFORMATION_GPT
public Guid PartitionType;
public Guid PartitionId;
[MarshalAs(UnmanagedType.U8)]
public EFIPartitionAttributes Attributes;
[MarshalAs(UnmanagedType.ByValTStr, SizeConst = 36)]
public string Name;
[Flags]
public enum EFIPartitionAttributes : ulong
GPT_ATTRIBUTE_PLATFORM_REQUIRED = 0x0000000000000001,
LegacyBIOSBootable = 0x0000000000000004,
GPT_BASIC_DATA_ATTRIBUTE_NO_DRIVE_LETTER = 0x8000000000000000,
GPT_BASIC_DATA_ATTRIBUTE_HIDDEN = 0x4000000000000000,
GPT_BASIC_DATA_ATTRIBUTE_SHADOW_COPY = 0x2000000000000000,
GPT_BASIC_DATA_ATTRIBUTE_READ_ONLY = 0x1000000000000000
[StructLayout(LayoutKind.Explicit)]
public struct DRIVE_LAYOUT_INFORMATION_UNION
[FieldOffset(0)]
public DRIVE_LAYOUT_INFORMATION_MBR Mbr;
[FieldOffset(0)]
public DRIVE_LAYOUT_INFORMATION_GPT Gpt;
[StructLayout(LayoutKind.Sequential)]
public struct DRIVE_LAYOUT_INFORMATION_GPT
public Guid DiskId;
public long StartingUsableOffset;
public long UsableLength;
public int MaxPartitionCount;
[StructLayout(LayoutKind.Sequential)]
public struct DRIVE_LAYOUT_INFORMATION_MBR
public uint Signature;
public enum PARTITION_STYLE : int
MasterBootRecord = 0,
GuidPartitionTable = 1,
Raw = 2

Hello,
in the links below you can found many informations to help you:
https://msdn.microsoft.com/en-us/library/windows/desktop/aa365730(v=vs.85).aspx
http://www.codeproject.com/Articles/696388/Recover-Data-From-Corrupted-Drives-File-Systems-FA
http://www.functionx.com/vcsharp/fileprocessing/drives.htm
http://forums.codeguru.com/showthread.php?548305-partitioning-USB-Falsh-drive
http://forums.codeguru.com/showthread.php?548169-USB-Flash-drive-Partitioning

Mystery partition after boot camp fail

I'm on an iMac, OSX 10.10.1. The entire 3TB Fusion HD was a single partition.
I attempted to install Windows using the Boot Camp Assistant, but Boot Camp froze while partitioning the HD. After rebooting, my HD now has a second Macintosh HD partition (~800GB) with a bunch of files in it (which I can't access), and which I'm unable to modify or remove using the Disk Utility (both in OSX and Recovery).
And of course, my HD now shows only 2.3TB.
Is there any way to resolve this short of reformatting the HD? And if that's necessary, any tips on how to go about doing that, plus reinstalling the OS and my Time Machine backup (I'm new to Macs, so I'm a little unfamiliar).
Thanks in advance.
Jed

Thanks for the quick response, Eric.
When I get to this step -- "Select the top level hard drive, not one of the partitions (as shown in screen shot)" -- the only option I have is to select the partition, not the entire HD. Note in the screenshot, the capacity is 2.3TB, which is only one partition of the two.
If I try to select the entire HD, I don't have the option to erase.
(These screenshots are from Disk Utility in OSX, not the Recovery one, but that's just so I could get a screenshot of what I saw in Recovery).
If I click to Erase, it notes that I'm only erasing the one partition. If this will, in fact, reset the drive to a single partition, I'll go ahead and do it, but I'm hesitant to reformat and reinstall if I don't have to.
It appears this might be a result of the way the Fusion drive operates combined with Bootcamp. Looking at this thread, there's a possible solution, but before I take that step, another new-Mac-user question -- is the reinstallation of the OS pretty reliable? Meaning if I go crazy with formatting things, am I always going to be able to reinstall the OS as long as I have a Recovery partition or have an Internet connection to do the Internet Recovery?
Thanks,
Jed

I can't create a USB booteable Windows in Boot Camp Mavericks that actually boots

Hi everyone... I have an issue that is apparently very common and yet I haven't found a working solution... I'm trying to install windows 7 using boot camp on my iMac 8,1 it is running Mavericks... I've got as far as creating the windows USB but after boot camp attempts to restart the computer I get that "no bootable device -- insert boot disk and press any key" message. My DVD unit is not working so I decided to try with the USB option but I'm stuck... I've tried using different (very different) pen drives (brand and sizes) but I always get this. I have also tried holding the alt/option key when I turn the computer on but it does never shows the USB, I've tried with different .iso files 32 and 64 bits, original and "questionable"... I hope you guys have a working solution for this. Thanks in advance, have a nice day.
Alberto Temich

Windows will not boot from USB if the Mac has an internal optical drive. This is something that Microsoft implemented.

Why does Boot Camp Assistant already think I have more than one partition on my hard drive?

Greetings...
I'm surprised I've found no remedy for this problem in my searches so far. My symptom is that when I run the Boot Camp Assistant app, I get the following error message:
"The startup disk cannot be partitioned or restored to a single partition." The instructions that are provided along with the error message are: "Back up the disk and use Disk Utility to format it as a single Mac OS Extended (Journaled) volume. Restore your information to the disk and try using Boot Camp Assistant again."
When I try to follow the instructions, I see that Disk Utility shows my drive as having a single partition. Nevertheless, I've backed up my Macintosh HD volume, re-artitioned the drive into a single Mac OS Extended (Journaled) volume (once using the Snow Leopard Installation disk and once using Drive Genius 3), and restored my Macintosh HD volume. After all that, I still get the same error message. I even defragged my hard drive, which seems to have helped some users I've read about, but it hasn't helped me.
Something worth noting is that I recently upgraded to a bigger internal hard drive, and before doing so, I deleted the Boot Camp volume. I innocently thought I'd just do a fresh install sometime after replacing the hard drive, but hindsight tells me that I might have fallen victim to my own ignorance.
Is there a value stored in a register somewhere that's telling my OS that I have more than one partition when I really don't? Can someone out there help me do battle against my ignorance?
I'd be grateful for any help that can be sent my way...

I used DG3 to initialize the HD, which essentially erases the disk if I understand correctly. I haven't used Superduper before, so perhaps that's worth looking into.
I did mentioned the use of DG3 to ensure that I had a single disk partition. I guess the restore from a clone or Time Machine was implied...
;o)
Thanks for putting some effort into helping me. I'll look at Superduper and let you know if that gets me anywhere...

Why does Boot Camp think I have more than one partition on my hard drive?

I'm surprised I'm finding no remedy for this problem in my searches so far. My symptom is that when I run the Boot Camp Assistant app, I get the following error message:
"The startup disk cannot be partitioned or restored to a single partition." The instructions that are provided along with the error message are: "Back up the disk and use Disk Utility to format it as a single Mac OS Extended (Journaled) volume. Restore your information to the disk and try using Boot Camp Assistant again."
When I try to follow the instructions, I see that Disk Utility shows my drive as having a single partition. Nevertheless, I've backed up my Macintosh HD volume, re-artitioned the drive into a single Mac OS Extended (Journaled) volume (once using the Snow Leopard Installation disk and once using Drive Genius 3), and restored my Macintosh HD volume. After all that, I still get the same error message. I even defragged my hard drive, which seems to have helped some users I've read about, but it hasn't helped me.
Something worth noting is that I recently upgraded to a bigger internal hard drive, and before doing so, I deleted the Boot Camp volume. I innocently thought I'd just do a fresh install sometime after replacing the hard drive, but hindsight tells me that I might have fallen victim to my own ignorance.
Is there a value stored in a register somewhere that's telling my OS that I have more than one partition when I really don't? Can someone out there help me do battle against my ignorance?
I'd be grateful for any help that can be sent my way...

Your welcome and good luck finding the solution. BTW as a newbie you benefit from:
Switch 101 & Mac 101.
Also you may want to reassess to see if you really need Windows on your computer. Remember if you install it you have all the issues every Windows users has to deal with. When I switched almost 4 years ago I installed Windows too but now I only turn it on to see if it still works. Of course your situation is different you may have proprietary software only designed for Windows and have to have it installed.

Can you use Windows 7 to partition a Boot Camp created drive (not just a PC partition on a Mac drive) into multiple PC partitions?

Can you use Windows 7 to partition a Boot Camp created dedicated PC drive (not just a PC partition on a Mac drive) into multiple PC partitions?

Can you download this utility, it is a close equivalent of the gpt command, but has more features? (It is more than likely that Windows took over and converted this to an MBR disk).
http://sourceforge.net/projects/gptfdisk/
Once you have it installed you run it as follows. You can execute using either /dev/disk1 or /dev/rdisk1 as the parameter.
type gdisk
gdisk is /usr/sbin/gdisk
sudo gdisk /dev/disk0
Password:
GPT fdisk (gdisk) version 0.8.9
Warning: Devices opened with shared lock will not have their
partition table automatically reloaded!
Partition table scan:
MBR: hybrid
BSD: not present
APM: not present
GPT: present
Found valid GPT with hybrid MBR; using GPT.
Command (? for help): p
Disk /dev/disk0: 1954210120 sectors, 931.8 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 6ED0C429-00D1-4759-B50E-04B6FB80D0E3
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 1954210086
Partitions will be aligned on 8-sector boundaries
Total free space is 1293 sectors (646.5 KiB)
Number Start (sector)    End (sector) Size       Code Name
   1              40          409639   200.0 MiB   EF00 EFI System Partition
   2          409640      1452940543   692.6 GiB   AF00 Customer
   3      1452940544      1454210079   619.9 MiB   AB00 Recovery HD
   4      1454211072      1954209791   238.4 GiB   0700 BOOTCAMP
Command (? for help): q

I'm trying to create a Windows partition using Boot Camp. An error comes up telling me that I need to reformat my current partition(s) into one single partition. However, it's already formatted in the correct format, and is already a single partition.

As made clear in the title:
I'm trying to create a Windows partition using Boot Camp. An error comes up telling me that I need to reformat my current partition(s) into one single partition. However, it's already formatted in the correct format, and is already a single partition.
My computer recently had a kernel panic, which apparently the corruption was in the system and needed to be erased and re-installed. I have a complete back-up using an external hard drive, and I am definitely not willing to do another one of those to reformat a partition that is already singular. I restarted the computer after ejecting my back-up, and after turning off time machine (thinking that boot camp was recognizing it as a secondary partition), however the error still occurs.
Is there any way to get around this?

diskutil list:
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *750.2 GB   disk0
   1:                        EFI                         209.7 MB   disk0s1
   2:                  Apple_HFS Macintosh HD            749.3 GB   disk0s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
/dev/disk1
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            Windows7               *2.9 GB     disk1
diskutil cs list:
No CoreStorage logical volume groups found
mount:
/dev/disk0s2 on / (hfs, local, journaled)
devfs on /dev (devfs, local, nobrowse)
map -hosts on /net (autofs, nosuid, automounted, nobrowse)
map auto_home on /home (autofs, automounted, nobrowse)
/dev/disk1 on /Volumes/Windows7 (udf, local, nodev, nosuid, read-only, noowners)
From my very basic knowledge - it still looks as if there is only one partition (not including the windows 7 CD necessary to install the windows partition).

Partition Manager is creating more than double number of partitions .

Dear Team,
I am facing a very weird scenario .
For one of my product , one of the section is the Partition Manager executing for the Tables . Now I am facing a problem and it is really getting difficult for me to get to the root cause and thus posting in the forum ...
I am having two Linux systems , in one of the system, installation of the product goes fine , and partition manager is doing the partition as intended .
In another Linux lab , ( with some extra application installed ) , the same product is failing to install , and the problem is Partition Manager is doing the partition more than double as compared to first Lab and because of this it ends up using all the space in the system .
My Concern is do we have any global setting for this Partition Manager in the Oracle Database , and because of this I am seeing the difference in this 2 labs ..I will be really thankful for any of the inputs and suggestion ...
With Very Best Regards,
Shail...
Edited by: 999908 on 13 Apr, 2013 9:27 PM

Hello Justin,
First of all thanks a lot for your patience ... :) , in looking into my problem ..
But I guess it is using Oracle partitioning Concept only...I dont think , my product is using the third party partition tool ( I will recheck this once to confirm )
What I understand is that , if for any table the number of partitions is almost thrice in one system as compared to other , then it will end up consuming more space for the table in the system where it is creating more number of partitions ...
I guess memory usage for any table also depends on the number of partitions ( Please do correct me if I am wrong here ) , if more number of partitions are there then more memory will be consumed , I guess..With Very Best Regards,
Shail

Data sharing between OSX and WinXP/Vista partition in boot camp

Due to software and external hardware issues, i need to revert back to an XP/Vista setup but would like to keep 1 computer to minimise having multiple copies/versions of data e.g. music, video, photos and office related docs.
If i perform a boot camp install, will the following scenarios work?
1) Have 1 large OSX partition which will store all my data. Will WinXP be able to read/write/delete data on the OSX partition
2) Have 1 large WinXP partition which will store all my data. Will OSX be able to read/write/delete data on the WinXP partition (Assuming i have the NTFS-3g software installed)
3) Have 1 (for arguments sake) 30GB OSX, 1 30GB WinXP and a third partition formatted as NTFS to hold my data.
Scenario 3 would appear to be the most sensible option as it keeps data away from the OSess so if i loose one, the data will be intact regardless.
Which brings me to my final question:
If i have to reinstall OSX, would i loose the WinXP partition in the process?
Many thanks!

Along with MacFUSE, take a look at MacDrive7 for Windows to read/write to HFS Extended volumes.
WinClone to backup Windows XP/Vista
Reinstall or restore? either way, and you really should never need to reinstall if you take an hour to backup (clone) or use TimeMachine (or combination of both).
I think Boot Camp Assistant is far too much of one-way only in not allowing or supporting more than one partition for OS X and one for Windows.
You can shrink OS X volume and create a partition out of free space. Or you can shrink Windows Vista (probably XP also) and partition that (but that can confuse OS X startup disk or boot manager "Option key.").
MacFUSE has had the side effect of making "Windows" volume not show up in OS X Startup Disk also.
I'd say MacDrive7 is your best bet without requiring an external drive (but do have one or two for your backups).

Not all free disk space available for windows partition in Boot Camp

Hi,
I want to install Windows 7 via Bootcamp on my MacBook (2009, Mavericks OS, BootCamp Assistant 5.1.2) and unfortunately it has been a huge struggle until now to achieve that. The whole reason for this is that I had Windows XP as the second OS on my MacBook, but I wanted to increase the Windows partition with Disk Utility. Unfortunately this permanently damaged my Windows partition so I couldn't use it anymore.
What I did next? I decided to delete the old Windows XP (which isn't supported anymore by Mavericks) with Disk Utility, which afterwards tells me that I have 1 partition left: The Mac partition.
From there on I wanted to install Windows 7 with the newer Boot Camp. The problem is that in fact Finder tells me that my Macintosh HD has 58,54 Gb free space, so I would like to assign at lease 30 Gb to the to-be Windows partition. However, Boot Camp only gives me the option to assign 20 until 24 Gb, other values I can't assign.
Can anyonetell me why this happens or what could be the problem? I need to have more than 24 Gb available for my Windows as this was the whole reason why I once wanted to increase my old Windows partition, that's where all the problems came from.
I appreciate your help, thank you!
Here is what Disk Utility tells about my partitions:

TTBOMK the only way you can increase the Windows partition is to repartition the drive back to a single partition
Then reinstall Mountain Lion
Restore all data from backup
Create new larger partition with Boot Camp
Install Windows
Restore data from backup
Allan

Create more than 8 loop devices on 2.63.32-300.10.1-el5uek kernel

Hello
I cant create more than 8 loop devices on 2.63.32-300.10.1-el5uek kernel, althought i have specified options loop max_loop=64 to /etc/modprobe.conf
how should i proceed ?
Thanks

It should work if you add max_loop=64 to the kernel boot parameter line or add it to the appropriate kernel in /etc/grub.conf (after rhgb quiet) for a permanent fix

How can I create more than one main window in a page of SAP SCRIPT?

How can I create more than one main window in a page of SAP SCRIPT? If anybody helps me I will be obliged.
Regards,
Subhasish

Hi Ganguly,
It is possible to have more than one main window in a same page.
You create a main window and simply you copy and past it in the same page.. it will create first main window name as MAIN and other main windows as MAIN01,MAIN02.... up to MAIN99.
Contets flow from MAIN , MAIN01, MAIN02.......................MAIN99. contents after filling the current window it flows to next window(by default, you skip as well with some keyword not sure could be NEW-WINDOW)
you want print the main window data twice? or you want to create two main window in the same page ?
1. give two copies in the no of copies in the output type screen ( Which pop up is coming after excute the program ).
2. create two page with the same script form.
3. you can write the coding inside the program to print twice the same page.
Hope this information use full to you..

How can I force mount a dvd that isn't even seen by Disk Utility? I can see it on the Mac when using my Windows 7 partition via Boot Camp, but not in Lion, which is how I would rather be running.

How can I force mount a dvd that isn't even seen by Disk Utility? I can see it on the Mac when using my Windows 7 partition via Boot Camp, but not in Lion, which is how I would rather be running.

Well if there is a EFI block, then running a program in OS X isn't going to do a lick of good.
After all EFI was designed for Trusted Computing and Digital Rights Management, to act between the OS and hardware, can read drives, contact the Internet and everything.
Windows doesn't use EFI, will have UEFI in Windows 8 though.

Boot Camp error: The startup disk cannot be partitioned or restored to a single partition. The startup disk must be formatted as a single Mac OS Extended (Jounraled) volume or already partitioned by Boot Camp Assistant for installing Windows.

Hi!
I am getting the error:
"The startup disk cannot be partitioned or restored to a single partition. The startup disk must be formatted as a single Mac OS Extended (Jounraled) volume or already partitioned by Boot Camp Assistant for installing Windows."
I read up some on google, but all of them says that they have crated a partition and that is the problem, I only have the standard "Macintosh HD".
I tried to create a partition manually in disk utility but then the error message: "Partition failed with error message: Could not unmount disk."
Can anyone help me? It's driving me crazy.
Thanks.

This message, and threads like yours got asked daily for over two years, now it is only a couple times a week!!
Is it so hard to follow through? you were to have backup already, clones are best, then erase/format and restore.
Then partition.
Some have been able to use Disk Utility booted from OS X DVD or another drive, and repair the drive.
You have to use Boot Camp Assistant (99.9% anyway) to create and achieve a proper Windows Master Boot Record partition.

Creating more than 2 partitions after Boot camp

Similar Messages

Maybe you are looking for