3094 and Bootcamp

Discussion in 'Parallels Desktop for Mac' started by martycat, Dec 26, 2006.

  1. martycat

    martycat Bit poster

    Messages:
    1
    I just updated from 3036 to 3094 and was very excited to boot my Bootcamp on FAT32.
    It works pretty nice after some keyboard-go-thru Parallels Tools installation. However, when I tried to go back to Bootcamp, it freezes at the profile selecting screen and the keyboard does no response.
    How can I fix it and get my Bootcamp back? Thanks!
     
  2. kenny113

    kenny113 Bit poster

    Messages:
    5
    Well, I know what caused the problem, but I don't know how to fix it... Only reason I know is because I did the same thing :(

    If you installed the new beta without uninstalling Parallels Tools for Boot Camp while booted under Boot Camp, this appears to be the outcome. I have tried messing with the Boot.ini and hardware profiles for hours trying to get my Boot Camp partition bootable again to no avail.

    I REALLY wish that Parallels would have included this little memo in the Read Me on the DMG or on the Installer notes. They made this note on the download page, but that doesn't help those of us who hit the link through VersionTracker or MacUpdate.

    Has someone had any luck recovering from this error?

    Parallels, is it possible to recovery from this mistake? If so, can you tell us what we need to do? Or even at least tell us what the newest beta did to cause this to happen so we might figure out a resolution on our own? I know it is explicitly stated not to use the betas in a production environment, but we end users generally expect application usability issues in these scenarios--not unbootable partitions.

    Any help would be appreciated.

    TIA
     
  3. nycruza

    nycruza Hunter

    Messages:
    224
    The board CLEARLY states, "VERY IMPORTANT" in bold and RED, "Remove Parallel Tools For Boot Camp . . ."

    http://www.parallels.com/products/desktop/beta_testing/

    ajm
     
  4. Chris Price

    Chris Price Junior Member

    Messages:
    17
    I did uninstall Parallels Tools for Boot Camp 1.0.3 before installing Build 3094. Same result here... my system will not boot properly with Boot Camp.

    And yes, FAT32 formatted just like everyone else.
     
  5. kenny113

    kenny113 Bit poster

    Messages:
    5
    Good call.. And if you would have read my entire post:
    Didn't your mama ever teach you?? If you don't have anything nice to say, don't say anything at all. :rolleyes: At least read someone's entire post to see their point before you try to flame them. Obviously we can read, so if we would have seen the beta download page, we would have followed its instructions.

    Anyone with any suggestions, feel free to post. Thanks!!!
     
  6. kenny113

    kenny113 Bit poster

    Messages:
    5
    Hmmm... We'll that's intriguing. It gets all the way up to the login screen (or desktop if you have autologin setup)? I just appears that it cannot detect the mouse and keyboard on systems that have not uninstalled Parallels Tools for Boot Camp, but the OS is not actually locked up. Is this the same behavior your system is exhibiting Chris?

    On my other Intel system, I uninstalled Tools for Boot Camp, and I did not experience this issue. Pretty much identical setups...
     
  7. cobrafang

    cobrafang Bit poster

    Messages:
    9
    I have the same issue except I NEVER installed the tools. Mine is set for auto login, but I get stuck at the "freakin reactivate window" which comes up right before you would be prompted for a login. I can't hit yes or no, because system does not recognize the keyboard or the mouse.

    ANY IDEAS?
     
  8. mindful

    mindful Bit poster

    Messages:
    2
    I am having the same problem.
    MacBook Pro 17 Core 2 Duo, 2.33GHz, 2 Gig RAM

    On restart, holding option key, I can select to boot into Boot Camp Windows but I then get to the same black screen to chose a configuration and cannot select any options via keyboard. It does not seem to work. I must do a hard shut down with the power button.

    This was the order of my installations/updates.

    1. Installed Boot Camp and Windows XP Pro.
    Booting into Windows with Boot Camp back and forth, no problem.

    2. Installed Parallels. Latest regular build from download.
    Did not create any VM or Windows installation. DID NOT install Parallel Tools into Windows.

    3. Updated Parallels with latest Beta. THEN installed Parallel Tools into Windows after booting through Boot Camp as instructed.

    4. Back to Mac OS and created VM from Boot Camp Hard Disc. Initailly got an error that it couldn't find disk but then after a black screen for several minutes, windows started popping around and Windows started up in Parallels. Worked in Windows XP for a while with no problem. Very cool.

    5. Shut down Windows through Start button as recommended and Windows proceeeded to install 64 updates.

    6. Restarted Windows through Parallels with no problem. On shut down Windows installed 1 update.

    7. Tried to boot into Windows through Boot Camp and after selecting Boot Camp icon I got to the current situation with the black config screen and no further progress into WIndows.

    NOTE: At one point, and I'm not sure exaclty when, probably after the first launch of WIndows through Parallels as stated above, I got the error that the hard disc Windows XP Pro couldn't be found, but all started up anyway.

    Then when I went to restart I noticed that the partition disc was no longer mounted on the Desktop; but then appeared on next restart.

    Hope this is all clear and I didnt't leave anything out. I would love to know what to do next so I don't have to trash all my installs and restart everything fressh.

    Thanks,
    J Lynn
     
  9. mindful

    mindful Bit poster

    Messages:
    2
    Found solution

    OK. It ultimately worked so here is what I did.

    1) Restart your Mac and hold down option key to enter Mac/Boot Camp chooser screen.

    2) Select Windows disk and click arrow underneath as you would normally to boot into Windows.

    3) IMMEDIATELY hold down the F8 key. I have set my Mac System Preferences to not require holding the fn key. You may need to hold the fn + F8. It has to be fast.

    4) This should allow you to choose from a number of modes for startup. You can choose Safe Mode and then go into "C/program files/Parallels" and move the "Parallel Tools for Boot Camp" to the trash.

    I was then able to restart from my Windows partition. I then had to go back into trash and restore the "Parallel Tools for Boot Camp" so I could run the Parallels Tools for Boot Camp installer to uninstall it. Now all seems fine in Boot Camp.

    I'm new to all this and found the clue in the post for the Parallels Beta at the top of the forums. Hope this is helpful.

    J Lynn
     
  10. brokenbottle

    brokenbottle Bit poster

    Messages:
    9
    Does anyone have any clues about this? I'm having the same issue, no keyboard or mouse response when I boot into Bootcamp. Unfortunately I misread the Beta2 warning and did not uninstall the utilities before installing and booting on Beta2. Everything works fine when I boot he bootcam partition via parallels under OSX but the keyboard and mouse aren't recognized when I do a boot directly into bootcamp. It's weird because it just acts like the USB drivers don't load. I can get the "safe mode" options menu on boot when I hit F8 but all te options lead to the same result: no keyboard or mouse response. I'm really hoping there's a way to fix this without having to do a bootcamp reinstallation just because it's so time consuming... :(
     
    Last edited: Dec 27, 2006
  11. kenny113

    kenny113 Bit poster

    Messages:
    5
    Booting into safe mode doesn't get me keyboard/mouse access either.
     
  12. cobrafang

    cobrafang Bit poster

    Messages:
    9
    Ok for me.

    I have no issues if I boot into bootcamp. Everything works fine.

    When I start parallels and try to use bootcamp...that is when I have the problems. I have nothing from parallels on my windows partition. I even got rid of any reference in the registry.

    So ANY IDEAS?
     

Share This Page