Skip navigation

Bootcamp assistance

412 Views 9 Replies Latest reply: May 7, 2012 11:15 AM by Aahzmandeus RSS
Aahzmandeus Calculating status...
Currently Being Moderated
May 6, 2012 1:49 AM

Hello all!

 

I have a general war with Bootcamp, as it seems that this program is very good at not doing what it is supposed to do

 

But, step by step.

 

So, one day I decide to put W7 on my macbook, because I need to work with some programs in the Windows environment.

 

I start up bootcamp, and choose the option to do the needed windows updates to prepare the mac for windows. Sure, do it!

 

...a few minutes later I'm told that no updates are available. Erm, okay? A look through the forums tells me that this can be bypassed.

 

So, I choose the second option  and proceed to partition the drive. I have a healthy 80 gigs of free space, so I leave 40 gigs to windows.

 

Alas, "not enough space on your hdd". Google, apple forums and 1 hour later present me with these options:

 

1)Reinstall macosx  - Well, thanks, but no. I don't have a drive to back up the complete data, and generally will not spend hours at fixing a problem this way.

1a)use less space for windows. Went as low as it allowed me (20gigs) to no avail.

 

2) Disk utility and disk repair - tried that via the single user mode and performed the disk check and repair a few times. However, this did not help bootcamp do its job.

 

3)Use ipartition or a third party software to partition the drive - won't do it, it costs money.

 

4)Check the "messages.app" for error messages from the bootcamp assistant - this seemed like the way to do it. Apparently, bootcamp assistant sends an error messages to the messages.app with an ID of the file that's giving bootcamp troubles. Unfortunately, it seems that messages.app has no log of bootcamp reporting any error.

 

So, with all of this in mind, is there any other solution to this problem?

 

My machine: 2009 non unibody macbook pro, Intel Core Duo, 4 gigs of RAM, macosx 10.6.8

  • Csound1 Level 7 Level 7 (32,385 points)
    Currently Being Moderated
    May 6, 2012 5:13 AM (in response to Aahzmandeus)

    5) Clone your drive, erase your drive, copy clone back to drive.

     

    40G is barely enough for Windows 7, 60G is better.

     

    You are modifying partitions with no way to backup? I advise that you stop where you are and get an external drive.

  • Csound1 Level 7 Level 7 (32,385 points)
    Currently Being Moderated
    May 6, 2012 5:48 AM (in response to Aahzmandeus)

    Do as you wish,

  • Csound1 Level 7 Level 7 (32,385 points)
    Currently Being Moderated
    May 6, 2012 8:31 AM (in response to Aahzmandeus)

    Until you get enough contiguous space you will fail, nothing to do with installing W7, you can't make the partition needed to install it in.

     

    I have given you the fastest, safest and most reliable method, ignoring it is your choice.

  • The hatter Level 9 Level 9 (58,595 points)
    Currently Being Moderated
    May 6, 2012 8:38 AM (in response to Aahzmandeus)

    Wrong.

     

    An SSD should have 15% space for over provisioning.

    any OS needs 15% minimum free space to function.

    an update like SP1 takes 9GB free space

    page file - up to you size

    hibernation - handy but again

    core OS is 20GB

    temp cache and otherr items

    applications and data

     

    34GB of actual used space but 48GB more reasonable as a minimum for Windows 7 64-bit

     

    not out of thin air

     

    anyone that doesn't have the time to do a full backup erase and restore, doesn't belong near computers.

     

    Apple does not have or support iDefrag or iPartiion or consolidating free space which being fragmented is one question over last 5 yrs I get tired of. The error messages peple see often has nothing to do with the problem or where to resolve "the volume has to be mac externded journaled.... but it is of course already.

     

    please don't bother us, we just give of our free time and don't need to do this.

  • Csound1 Level 7 Level 7 (32,385 points)
    Currently Being Moderated
    May 6, 2012 10:33 AM (in response to Aahzmandeus)

    Aahzmandeus wrote:

     

    @Csound1: What does that even mean? I have 80 gigs of free space. I want to dedicate 20 gigs of that space to an OS (whether the OS will function or not is my own problem). OSX obviously is having trouble moving the files around into the 60 gigs of free space area that it still has for reasons that are unclear.

     

    Bootcamp apparently used to report what the problematic files were, but it doesn't anymore.

     

    @The hatter: That is your way of running an OS. I am not sure where you are taking your numbers, but core W7 is NOT 20 gigs and I've no idea where you came up with that size. Like I said, I had W7 run on a 32gb SSD perfectly fine. With enough space for all the software I needed and plenty of free space to boot and mighty fast at that, too. It wasn't just the initial setup, but a system that performed very well for the two years that I had the netbook.

     

    Whether you choose to believe that or not is up to you.

     

    About backup erase and restore and not belonging to computers: that's just a hypocritic way of viewing the problem. I'm past those types of solutions, because it's kind of like hitting a nail with a 20 ton sledgehammer.

     

    If you feel like I'm bothering you, then you don't need to reply or even read this thread.

     

    The topic is that there is an app (bootcamp) that is malfunctioning in OSX in two ways. One, it fails to pull an update for W7. Two, it fails to create a partition, even though there is plenty of space. Now, other useful people have highlighted that the program used to report which files are causing it problems to move the files, and for those people, it was usually the problem of just a few files that needed to be removed.

     

    For some reason, that feature is gone or is malfunctioning, too.

     

    I am writing this in the hopes that there is someone out there who has figured this out, much like someone before figured out that there was a way to diagnose this problem and move the problematic files.

     

    What I don't need is someone who lectures me on the space requirements of an OS or rolls the eyes and tells me the problem is known for five years and that there is no sensible solution for it besides nuking the OS or applying third party solutions.

    Then I will step out of this discussion while you apply your own skills to sort this out, good luck.

Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.