Successful BC 2.1 in XP

I just installed BC2.1 on my other MBP running XP.
The download appeared in the Apple Software Update app and installed by itself, requiring a single reboot.
No problems whatsoever.
Some new hardware was recognized (BlueTooth) but other than that, I see nothing different.
This update is necessary for XP SP3.

Paula in Wisconsin wrote:
Ditto Nerowolfe, I installed it without a problem either same as you. Paula
Sadly, my Vista Ultra 64-bit did not go as well. See my other post.
I don't think it's me. I think there is something wrong with the Vista 4-bit update.
At least it didn't do any damage - it just sat there and did nothing

Similar Messages

Adobe Cloud is installed on my desktop and one laptop computer. Upon noticing updates were available yesterday, I successfully installed them on my laptop. Today, I cannot get Abobe Cloud to open on my desktop.

Adobe Cloud is installed on my desktop and one laptop computer. Upon noticing updates were available yesterday, I successfully installed them on my laptop. Today, I cannot get Abobe Cloud to open on my desktop.

We don't know what Apple plans on doing to change this (and it may not be just Apple but more likely the publishers, since Apple would, of course, do whatever it could to maximize sales/profits). Right now you can only read Apple books on mobile devices. Sure, buy them from Amazon if you want to read them on the computer. We don't work for Apple so we're pretty impartial on this kind of advice.
You might also see what your library can offer. My wife can browse the county library from her iPhone, borrow e-versions, and read books on it too. Free!

Whenever i try and open a social network app it comes up with an error message sayinng "Connect to itunes to use Push Notifications" I have successfully conntected to itunes via phone and computer however this message is still appearing and will not go?

Whenever i try and open a social network app it comes up with an error message sayinng "Connect to itunes to use Push Notifications" I have successfully conntected to itunes via phone and computer however this message is still appearing and will not go, therefore i cannot use the apps?HELP PLEASE

http://support.apple.com/kb/TS3281

15" i7 Macbook Pro from early 2011.takes the mac laptop two or three tries to boot successfully. It would turn on, show gray screen, shut down, turn on again, show gray screen, shutdown, and then turn on, show gray screen, before it can finally get

Hello All,
I have a 15" i7 Macbook Pro from early 2011. The past few weeks, it has been getting increasingly difficult to get on my computer. It takes the mac laptop two or three tries to boot successfully. It would turn on, show gray screen, shut down, turn on again, show gray screen, shutdown, and then turn on, show gray screen, before it can finally get to the dark gray log-in screen. Even when I finally get logged in to start working, thinking it would be okay now, it shuts down randomly.
I've ruled out the possibility of a software problem because I've just done a clean re-install of Mac OS X Mavericks on my computer just yesterday.
I did upgrade the RAM recently, about a month and a half ago, from 4GB to 16GB, I went to the apple store four days after that upgrade to have them do a hardware test, and clean the inside of my laptop, which helped with previous heat issues. When they did the hardware test, the hardware was all registered as fine from their system.
I've tried resetting the SMC, PRAM, and doing the internet recovery hardware test, but to no avail. I thought I could at least find out what parts needed to be replaced from the hardware test but it seems that when the hardware test is almost finished, the computer just shuts down, So I am unable to see the results.
My computer is also having battery issues, under battery condition, it says "replace now," parts have been ordered, waiting for arrival. But if the battery health is low, it should still boot up fine, it would just hold a significantly less charge.
Could this be a hard drive issue?
Has anyone had similar symptoms and how was it resolved?
Does anyone know what I can do to alleviate this issue?
I haven't had time to take it to Apple because I'm currently taking a 21 credit semester academically. I'm an art and design student so my computer is basically the bane of my existence. Help! Any constructive advice is welcomed!
Thank you so much for your input!
-Christina C.

Problem description:
The Hard Disk is failing.
EtreCheck version: 2.0.11 (98)
Report generated November 4, 2014 at 7:59:28 AM EST
Hardware Information: ℹ️
MacBook Pro (15-inch, Early 2011) (Verified)
MacBook Pro - model: MacBookPro8,2
1 2.2 GHz Intel Core i7 CPU: 4-core
16 GB RAM Upgradeable
BANK 0/DIMM0
8 GB DDR3 1600 MHz ok
BANK 1/DIMM0
8 GB DDR3 1600 MHz ok
Bluetooth: Old - Handoff/Airdrop2 not supported
Wireless: en1: 802.11 a/b/g/n
Video Information: ℹ️
Intel HD Graphics 3000 - VRAM: 512 MB
Color LCD 1440 x 900
AMD Radeon HD 6750M - VRAM: 1024 MB
System Software: ℹ️
OS X 10.9.5 (13F34) - Uptime: 0:3:43
Disk Information: ℹ️
TOSHIBA MK7559GSXF disk0 : (750.16 GB)
S.M.A.R.T. Status: Verified
EFI (disk0s1) <not mounted> : 210 MB
HDV4 (disk0s2) / [Startup]: 749.30 GB (712.10 GB free)
Recovery HD (disk0s3) <not mounted> [Recovery]: 650 MB
MATSHITADVD-R   UJ-898
USB Information: ℹ️
Apple Inc. FaceTime HD Camera (Built-in)
Apple Inc. BRCM2070 Hub
Apple Inc. Bluetooth USB Host Controller
Apple Inc. Apple Internal Keyboard / Trackpad
Apple Computer, Inc. IR Receiver
Thunderbolt Information: ℹ️
Apple Inc. thunderbolt_bus
Gatekeeper: ℹ️
Mac App Store and identified developers
Kernel Extensions: ℹ️
/Library/Application Support/Avast/components/fileshield/unsigned
[loaded] com.avast.AvastFileShield (2.1.0 - SDK 10.9) Support
/Library/Application Support/Avast/components/proxy/unsigned
[loaded] com.avast.PacketForwarder (1.4 - SDK 10.9) Support
Launch Agents: ℹ️
[not loaded] com.adobe.AAM.Updater-1.0.plist Support
[loaded] com.avast.userinit.plist Support
Launch Daemons: ℹ️
[invalid?] com.adobe.SwitchBoard.plist Support
[loaded] com.avast.init.plist Support
[loaded] com.avast.uninstall.plist Support
[loaded] com.avast.update.plist Support
[invalid?] com.perion.searchprotectd.plist Support
User Launch Agents: ℹ️
[invalid?] com.avast.home.userinit.plist Support
[loaded] com.google.keystone.agent.plist Support
[invalid?] com.jdibackup.ZipCloud.autostart.plist Support
User Login Items: ℹ️
None
Internet Plug-ins: ℹ️
AdobePDFViewer: Version: 10.1.1 Support
QuickTime Plugin: Version: 7.7.3
JavaAppletPlugin: Version: 14.9.0 - SDK 10.7 Check version
Default Browser: Version: 537 - SDK 10.9
User Internet Plug-ins: ℹ️
TroviNPAPIPlugin: Version: 1.0 - SDK 10.9 Support
Google Earth Web Plug-in: Version: Unknown
Safari Extensions: ℹ️
Avast Online Security
Trovi Search for Safari
3rd Party Preference Panes: ℹ️
None
Time Machine: ℹ️
Time Machine not configured!
Top Processes by CPU: ℹ️
      16% mds
      7% WindowServer
      1% loginwindow
      1% fontd
      1% com.avast.daemon
Top Processes by Memory: ℹ️
120 MB com.avast.daemon
86 MB Google Chrome
52 MB Finder
52 MB WindowServer
41 MB Google Chrome Helper
Virtual Memory Information: ℹ️
13.45 GB Free RAM
1.34 GB Active RAM
944 MB Inactive RAM
1.43 GB Wired RAM
1.11 GB Page-ins
0 B Page-outs

E61i no longer connects successfully

Hi,
I'm having a very frustrating problem with my E61i, which has worked perfectly with Bluetooth File Exchange, Nokia Multimedia transfer etc., but now fails to connect. It seems something is corrupted on the phone such that this no longer works. Rebooting the phone / Mac achieves nothing. Here are the details:
- From a clean start (after rebooting both systems), Bluetooth File Exchange successfully connects to the phone, but any attempt to transfer a file leads to a "connection failed or closed" error. It doesn't matter whether the file is on phone memory or the memory card.
- thereafter, Bluetooth File Exchange is not even able to connect to the phone ... I get this same error message. On the phone screen I see parentheses appear for about a quarter second around the bluetooth symbol (indicating a connection), but then vanish. It is trying, but immediately fails.
- via USB cable, Nokia Multimedia Transfer has a similar problem. After starting the "connect and transfer" from NMT, I then connect the USB cable from phone to Mac; the Data vs. PC Suite choice is offered to me by the phone; I choose PC Suite, briefly see the PC Suite connection symbol, which immediately vanishes. NMT works for a bit (i.e. NMT icon on the menu bar shows activity for a few seconds) then nothing further happens -- no iPhoto or iTunes launch as would normally be expected. Trying to connect via bluetooth gives the same behavior: a brief flash of the parentheses around the bluetooth symbol on the phone indicating a connection, which immediately vanishes, and NMT acts as if nothing happened (no connection).
- iSync via bluetooth works just fine at transferring contacts and appointments back and forth between phone and mac.
- USB data transfer to access files the memory card (E also works just fine. My understanding is that this is just a direct USB access to the memory card, effectively disconnecting the phone from the memory card.
It looks like the functionality on the phone that supports file transfer to outside applications like PC Suite, Bluetooth File Exchange and Nokia Multimedia Transfer has corrupted some of its data files, so that it fails whenever it tries to start. I've searched quite a bit on the web, and lots of people have similar problems with Nokia file transfer, but no solutions that seem relevant.
The problem is that the system is so damn opaque! If only I could see a log file like on linux I could presumably track down the meaning of the error messages and resolve the cause of the problem. But I haven't found any info that would indicate even where to start -- I can't even find out whether there are useful log files, let alone where to look for them.
This problem started after transferring a 7 MB file from phone to Mac via Bluetooth File Exchange: during the transfer a GSM call came in (from a telemarketing idiot!); while I took the call, the transfer continued fine but a bit slower, and completed with no apparent problem. The transferred file seems fine. However, afterwards I'm having all these problems that I never had before.
firmware 1.0633.86.02 14-03-07 RM-227 Nokia E61i-1
MacBook Pro 1st generation, OS 10.4.11
Help!
-- Chris Lee

I think I have solved my problem after a frustrating week. I traveled last week and changed time zones. I then changed the time zones on both my MacBook and E61i. However, once that was done, everytime I tried to synchronize my phone and iCal and Address Book, I kept getting a SYSTEM ERROR message, and the two would not sync.
When I returned to home, and reset the times, I still got the System Error message, and no synchronization. Emailing the help desk here, they just told me to download the plug in! Not very "helpful" as I'd already done that!
This morning then, I deleted all the calendar entries from my phone, and tried to sync again. Finally successes!
Seems there's some kind of glitch if you change the time zone settings. Just delete all the entries on the phone, and then re-sync.

Successful Windows 7 install (mostly)

I would like to report that I have been successful at installing Windows 7 RC on a dedicated drive on a Mac Pro (early 2008) using the following procedure:
1. Downloaded the ISO (Windows 7 RC 32-bit) from Microsoft and burned the image to DVD using Nero 6 in the XP environment (using the lowest burn speed available for best results).
2. Booted to OS X and ran the Boot Camp Assistant to select the drive and have it partition the drive (which results in a drive with a mini 200 MB partition used for the boot process and a main partition for installing the OS on).
3. Inserted the Windows 7 RC DVD in optical drive and waited as usual for the disc to appear on the desktop and clicked ‘Continue’ in Boot Camp Assistant.
4. After the Window 7 RC DVD loaded files, I was presented with a list of partitions that the Windows installer sees. Being careful not to select the 200 MB partition, I selected the proper partition to install Windows on and then clicked the ‘Options’ link below the list of partitions.
5. After clicking the ‘Options’ link, I clicked on the ‘Format’ option and once that finished, I proceeded with the installation which was nothing more than clicking the button at the lower right corner of installer dialog and letting Windows install itself (which includes rebooting a couple of times).
6. Once the installer finished, I was presented with the ‘User Name’ options followed by the ‘Password’ and ‘Window Update’ options (I entered a password for security and selected the ‘Recommended’ update option for ease of process).
7. Windows then prepared the desktop by running the hardware evaluation sequence and I finally arrived at the desktop.
Note – I used the included thin aluminum full sized USB keyboard to enter data in step #6 and a USB mouse to click in all other steps.
I attempted to run the Boot Camp installer off the OS X install disc included with the Mac Pro, but Windows 7 promptly informed me that Boot Camp had known issues with this version of Windows.
I quit the installer and then opened Windows Explorer by clicking the folder icon on the taskbar. Selecting ‘Computer’ allowed me access to the optical drive icon which I could right-click to use the ‘Open’ option to view the contents of the disc. Opening the ‘Boot Camp’ folder and then the ‘Drivers’ folder gave me access to the individual driver installers which can be installed as needed (if needed).
I found the following issues while installing the drivers referred to above:
1. Installing the Apple keyboard drivers did install the Apple keyboard driver file to the correct location (‘:\WINDOWS\System32\Drivers\’) but did not enable the Eject key on the keyboard. The other keys all seemed to work correctly for Windows commands although I have not tried all variations, just the typical Ctrl, Shift, Alt modifier combinations.
2. Installing the other ‘Apple’ drivers did not enable the Eject key either.
3. Attempting to run the ‘BootCamp.exe’ file by itself resulted in the compatibility error message again, which convinced me that it is this file creating the problem and not the individual driver files. Note – this meant that the Boot Camp applet was not available to select a boot drive from in the Windows 7 RC environment (I had to use the ‘Option’ key during boot to change the boot drive away from Windows 7 RC).
4. Running the individual Realtek audio installer resulted in improved audio functionality over the audio drivers included in the Windows 7 RC image.
5. Running Windows Update offered an update to the nVidia 8800 GT card in the Mac Pro which installed and worked correctly.
6. Looking in Device Manager (right-click Computer \ select ‘Properties’ \ click Device Manager link) – I saw only one missing driver listed as a base device which I believe is the PCI bridge for the data controller enabling the SATA data transfer.
The end result is that I have access to running Windows 7 RC with the following missing functionality:
1. No use of the ‘Eject’ key on the full sized aluminum Apple keyboard (work-around is to use the optical drive context menu ‘Eject’ command and close tray by hand).
2. No full speed data transfer on SATA controller (still using the UDMA mode ‘5’ as in both XP and Vista).
3. Maximum RAM access is still limited to 2 GB (same as XP and Vista 32-bit) although Windows 7 RC sees all 8 GB. If I understand correctly – which I admittedly may not – this has something to do with the 200 MB boot partition and the resulting communication restrictions imposed by the differences between BIOS and EFI.
Note – I have not tried to connect the Bluetooth thin aluminum Apple keyboard yet, but will try later today after work.
Note #2 – this Mac Pro machine has had successful and problem free Windows XP (32-bit) & Vista Business (32-bit) installations with the exception of items #2 & #3 above which seems to be driver / firmware related.
I have read that a number of people are having problems with installing Windows 7 RC when upgrading an existing Vista install. Due to the incompatibility with the current version of Boot Camp and / or other Vista specific files that may be in conflict, it may be worth trying to do a clean install using the Boot Camp Assistant in OS X to repartition and prepare the drive for install (although you would obviously need to reinstall all apps into the Windows environment and backing up your email, favorites and personal files to copy to Windows 7 RC after install).
I would also recommend burning your Windows 7 RC image using the lowest speed possible. Until about 18 months ago, I was a PC power user and have seen failed installs of various Beta and RC versions due to corrupt files created during high speed burns.
I apologize if this is long winded post, but I thought it might help some people and also might help any Apple tech’s dropping by that are trying to identify the issues popping up with running Windows 7 RC on a Mac.
A special thanks to ‘The Hatter’ for taking the time to create this great ‘FAQ \ information link’ post http://discussions.apple.com/thread.jspa?threadID=1866970&tstart=0 on the Windows 7 Beta install process for Mac users.
Peace.

Okay,
Here is the balance on the Windows 7 RC (32-bit) installation:
1. I checked on the (32-bit) beta drivers from the link above and they turn out to be the same as the pre-release version offered by Windows Update under the 'Optional' category, which is a good thing IMHO.
2. I had to run the Boot Camp installer and select the 'Run Program' button to bypass the compatibility warning message in order to test on the keyboard issue. During the installation, I received a second compatibility message towards the end of the process concerning the chipset drivers, so I quit the installer and rebooted at that point. The result was that the Boot Camp applet was installed (allowing selection of the boot drive from in Windows 7 RC environment) and the 'Eject' key working on the USB full sized aluminum keyboard (as well as all other Windows related keyboard functionality).
3. I had to use the following procedure to pair the Apple Bluetooth aluminum keyboard:
a) Turn on keyboard so light blinks indicating sending of a signal.
b) Click on notification area 'Bluetooth Devices' icon and select 'Add a Device' which displayed a window where found devices are listed as Windows searches. (Note - the other option to get to this windows is 'Control Panel > Add a device link' found under Hardware and Sound category).
c) Once the keyboard is displayed, right-click device and select 'Properties' (or select device and press Alt+Enter) to display the device properties.
d) Click on the 'Services' tab and wait for the list to populate, which will result in one check box next to 'Drivers for keyboard, mice, etc (HID)'.
e) Place a check mark in the box and then click 'Apply', which will start the install process for that service and should result in a notification balloon at the right end of the taskbar. Click this balloon to see the progress as Windows Update checks for any updated drivers and then indicates completion of the install.
f) The device should disappear from the 'Add a device' list and should now work.
Note - the Bluetooth keyboard pairing is a bit counter-intuitive (not a huge surprise there) in that normally the user should only need to select the device in the list and then click 'Next' to pair (and probably would work if the services were already installed and/or enabled).
That seems (at least to me) to be a generally pain free install process, with the exception of the Boot Camp compatibilty messages making troubleshooting Windows 7 RC on a Mac a bit more ambiguous.
Thanks again for the tips, Hatter.
I will report back to this post once I complete a Windows 7 RC (64-bit) installation using the same drive and procedure to see if all goes well and to verify that Windows 7 RC can access all 8 GB of RAM.
Peace.
Message was edited by: CorkyO

Hot sync says Palm Zire has successfully synced but no data (using Windows 7 32 bit)

We have a Win XP desktop on which an older version of Palm Desktop has been working for years and been able to sync with my Palm Zire and my husband's Palm Z22. Now that we have to decomission Win XP desktop have installed Palm Desktop by Access v6.2.2 and Hotsync v7.0.2 on Win 7 32bit laptop.
My husband has a Palm Z22 and has had no problems setting up user and syncing using Palm Desktop by Access when using Windows 7. However, although the Palm Desktop has correctly indentified by device as a Zire and hotsync via cable says it completes successfully no data appears on the Desktop. In reverse, when I add a new contact on Palm Desktop and sync it does not appear on the handheld.
Have tried downloading and installing driver from:
http://aceeca.com/support/sales-support/downloads/product/drivers-32-bit-usb-windows-driver-for-palm...
However, when I followed the instructions provided with teh 64 bit download my laptop said I already had most up to date driver!
Please help as I rely on my Zire and need it to back up successfully.

Hello, and Welcome to the HP Support Community!
The Aceeca drivers are ONLY for 64-bit Operating Systems. Since yours is 32-bit, it's not needed.
Try right-clicking on the shortcut for Palm Desktop, then choose "Run as Administrator". See if the data appears.
Another suggestion would be to turn off "UAC" or User Access Control. Control Panel/Users/Turn off UAC.
WyreNut
I am a Volunteer here, not employed by HP.
You too can become an HP Expert! Details HERE!
If my post has helped you, click the Kudos Thumbs up!
If it solved your issue, Click the "Accept as Solution" button so others can benefit from the question you asked!

Success: moving bootcamp partition to an external drive

Background
Due to the relatively small, non-exchangable SSD on my Mac, I'd limited the bootcamp partition to 50GB when installing Windows. I needed to install new software in Windows, but was running out of space fast and didn't have the necessary space on the Windows side. I don't use Windows that often and for that reason, I wanted to move the Bootcamp partition to an external hard drive, freeing up space for the Mac side on the internal SSD. I'd read many conflicting reports on the web, some claiming they'd done it successfully, while others said it would be impossible, because Windows 7 wouldn't run from an external drive. I had a HDD in a USB 3 enclosure, and first tried to install Windows to this (using various guides on the web). I was very close to success with this USB 3 drive, but Windows would fail during start-up. Most reports claiming to have successfully been able to run Windows 7 from an external drive, had used Thunderbolt drives, so I decided to get myself a Lacie Rugged USB 3/Thunderbolt series Solid State Drive.
Hardware used
MacBook Pro 15" Retina Display (mid 2012), 2,3 GHz Intel Core i7, 8GB RAM, 250GB SSD
Lacie Rugged USB 3/Thunderbolt series, 120GB Solid State Drive
Software used
Mac OS X Mavericks, 10.9.2
Windows 7 Ultimate
Plus several free downloads from the internet, see description below.
Procedure
Step 1: Get the Thunderbolt drive to work under your Bootcamp Windows 7 installation.
This should be simple enough, but proved to be a little tricky. Here’s what I did (assumes you are running Mac OS X before you begin):
1. Make sure your Thunderbolt drive is disconnected before proceeding.
2. Restart your Mac and hold down the option key (alt key on some keyboards) during startup.
3. Choose the Windows drive to start up Windows 7 on your Bootcamp partition.
4. After log in to Windows 7, download the necessary driver software for your Thunderbolt drive (find it at the manufacturer’s homepage of your Thunderbolt drive - in my case lacie.com).
5. If the downloaded driver installer is in a compressed format (like zip for example) be sure to decompress it before running the driver installer.
6. Shut down your computer.
7. Connect your Thunderbolt drive to your computer.
8. Start up in Windows 7 (see items 2 & 3 above) and if it all went well, you should now be able to see your Thunderbolt drive under Start>Computer.
Step 2: Format your Thunderbolt drive in NTFS-format.
Still running Windows 7 with your Thunderbolt drive connected and visible to the system, it is now time to format your external Thunderbolt drive in NTFS-format. There are several ways of doing this. I used the procedure described here at tedhhack.co.uk.
Step 3: Follow the directions at intowindows.com to clean install Windows 7 onto your external Thunderbolt drive.
As described at intowindows.com, this involves downloading Windows Automated Installation Kit (WAIK) and running command line tools. At step 9 in the described process at intowindows.com, at the point where the installer asks if the drive you are installing to is a USB hard disk, the correct input is Y for yes, even if your external drive is a Thunderbolt drive (and obviously not a USB hard disk).
At step 10 in the described process at intowindows.com (Reboot your PC), remember to hold down the option (or alt) key at every restart in the installation process, so as not to start up in Mac OS X. Also, since your machine now has two Windows 7 installations, Windows Boot Manager will appear and ask you to “Choose an operating system to start” and there is a list of two Windows.
I don’t know how to tell which one is on the external drive and which one is on the internal drive at this point, but I started with the top one on the list and this turned out to be the one I wanted (the newly installed one on the external drive). If you pick the wrong one (on the internal drive) at first, simply restart the computer and choose the other one. You know you got the right one when the installation process continues and asks for further input.
After the Windows installation is complete (there will be at least one other restart required - remember to hold down the option (alt) key to start up in Windows, and choose the same Windows on the list in the Windows Boot Manager), you’ll be running a freshly installed, but crippled Windows 7, as you still haven’t installed the specific drivers for your hardware. But don’t worry, that will be fixed in the next step.
Step 4: Clone your Bootcamp partition from your internal drive to the external Thunderbolt drive.
In this step you will copy all the software, drivers, settings and other files from your Bootcamp partition on your internal drive to your external Thunderbolt drive. The easiest way to do that is to clone your Windows partition - and to that end you’ll need to download some free software: AOMEI Backupper Standard 2.0 fits the bill perfectly, as it will let you clone at the same time as resizing the partition to fit your external Thunderbolt drive (I went from a 50GB internal Bootcamp partition to a 120GB external Thunderbolt SSD).
1. Download AOMEI Backupper Standard 2.0 (I used the 17MB download for Windows 7), install it, and run it.
2. In the left column choose “Clone” and in the right column choose “Partition Clone”. By choosing Partition Clone instead of Disk clone, you won’t ruin the newly created (but invisible) boot partition on the external Thunderbolt drive.
3. Press Next and choose your internal Bootcamp partition as the Source Disk.
4. Press Next again and choose your external Thunderbolt drive (your newly installed Windows 7) as the Destination Disk.
5. Press Next again and you’ll get a warning that you will erase the contents of the destination partition and it asks if this is what you really want to do. Press Yes to this question.
6. Next screen is an Operation Summery. Toward the bottom of the Operation Summery screen there are a few interesting options: Edit Size of Partition, Clone Sector by Sector and Align Partition to Optimize for SSD.
7. If your destination partition is larger than your source destination like mine was, press Edit Size of Partition. This will take you to another screen, where you can drag to resize the partition. I dragged this all the way to the right to give Windows 7 the full size of my external Thunderbolt drive.
8. Leave the checkbox Clone Sector by Sector unchecked.
9. If your external Thunderbolt drive is an SSD, put a check in the checkbox entitled Align Partition to Optimize for SSD.
10. Now press the Start Clone button.
11. When the cloning process is done, exit AOMEI Backupper and restart your computer (holding down the option or alt key) to start up in your new clone of your old Windows 7 with all the same software, drivers, settings and files.
Step 5: Enjoy running all your Windows 7 applications from your external Thunderbolt drive!
Step 6: Here is where I need help/advice – can I remove the Bootcamp partition on my internal drive now?
I am reluctant to entirely remove the Bootcamp partition from my internal drive, as I am unsure whether this will disable me from starting up in Windows. I would love to hear from anyone here with insight on the matter.

Step 6: Here is where I need help/advice – can I remove the Bootcamp partition on my internal drive now?
To answer my own question in Step 6 above, no, or at least I haven't found a way yet...
Here's what I've done so far:
Used the Bootcamp Assistant to remove the bootcamp partition on my internal drive.
Booted the system with the option (alt) key pressed down and now there was NO Windows drive to choose.
Therefore I used the Bootcamp Assistant to install Windows back onto my internal drive (including installing Bootcamp drivers in the Windows environment). This time I chose the minimum partition of 20GB for the Windows installation on the internal drive.
Booted into the new Windows on the internal drive and installed the drivers for my Thunderbolt drive.
Restarted with the option (alt) key pressed down, chose the Windows drive, but Windows Boot Manager still didn't pop up to allow me to choose the Windows installation on the external Thunderbolt drive.
Booted from the Windows DVD and chose Repair.
Restarted with the option (alt) key pressed down, chose the Windows drive, and now Windows Boot Manager finally popped up, which allowed me to choose the Windows installation on the external Thunderbolt drive again, phew!
So, I can run Windows 7 from the external Thunderbolt drive, but I have to use 20GB of my internal drive for a Windows installation I'll never use. Not the best solution, but at least I've saved 30GB of space compared to my previous Bootcamp partition - and I now have enough space to install the Windows 7 software I need on the external Thunderbolt drive...

Friends, MacBook Pro 8,1 – Intel Core i5 – 2.23 GHz (early 2011) New MB Pro with OSX 10.6 – current on all updates. I successfully installed rEFit. I used Boot Camp to install Win 7. All was great. Then installed debian 6. Somehow after the debian i

MacBook Pro 8,1 – Intel Core i5 – 2.23 GHz (early 2011) New with OSX 10.6 – current on all updates.
I successfully installed rEFit. I used Boot Camp to install Win 7. All was great.
Then installed debian 6. Somehow after the debian install and restart (I know this sounds crazy) but I am now reduced to Win 7 only. rEFit is not present when rebooting nor is OSX or debian. Further, I am unable to force the install DVD to launch when rebooting, by holding C, D or F8. The Option key brings me to the grey screen with a padlock. I have attempted the root and local pw- no go. Restart holding D takes me to the windows boot manager. I have attempted several options within the Advanced Options; including – Repair Your computer, safe mode and “last known good config,” All of which did nothing.
I can see all my OSX files within win7. I tried to install the OSX within windows. Ya right, that did nothing..
I only desire to get back to OSX...
What are my options??

Yes, you royally hosed up your machine.
You should first try to get your files off, any way you can to a external drive.
Your going to need to hold c and boot from the disk that came with your computer and a couple of screens in under the menu is a option for Disk Utility.
Select your drive and Erase with Security Option Zero, format the drive HFS+ Journaled and when that's finished (about a hour or so) then quit and install OS X from the installer.
I hope this works, but I suspect it won't. Others have hosed their machines trying to use a Linux disk without proper partition formatting too.
Another option might be to use another Mac to c boot off the Snow Leopard disk and install OS X onto a external drive, take that to the problem Mac and try holding option and booting off of it to erase your internal drive.
You could replace the drive.
frederick s wrote:
The Option key brings me to the grey screen with a padlock.
Is this holding option while booting?
There was someone else around here who hosed their Mac with a Linux disk too. Try to find it.

On my macbook pro when opening a page i can not save it as a pdf only give me the option of saving it as a web page can any body help me on this I have tryed so many times without success

on my macbook pro when opening a page on safaryi can not save it as a pdf only give me the option of saving it as a web page can any body help me on this I have tryed so many times without success?

Just select Print in Safari and then, in the bottom left-hand corner, select PDF and you can save it to whichever flavor pdf file you like.
Clinton

FCP 6.0.2 - Capture Successful - Clips not saved! Help!

I'm running FCP 6.0.2 on OS X 10.4.11
I have a Sony HDR-FX1 camera and do most of my filming in SD DV.
I'm trying to capture footage on several tapes (about an hour per tape) using the Log and Capture method. The camera is plugged into my front firewire port. I've logged the tapes (as 1 hour clips) and have tried doing a batch capture several times.
Here's the problem:
The clip is captured for the entire hour and I'm presented with the message that the capture was successful. I proceed to click "Finish" and my clip stills shows as "offline" in the final cut pro browser. Also, when I look in my FCP "Capture Scratch" folder, the respective project folder is completely empty.
In other words, FCP is not saving my captured clips for some reason.
I'm happy to answer any other questions you may have and am willing to try anything at this point!
Thanks in advance for your help.

Yeah - oddly enough, I don't run into this problem with shorter clips - just captured one that was 30 minutes long. But I really don't want to split these long clips up - it's easier to sync up the multiple angles when I'm dealing with clips that are all the same length.
You would think that if FCP encountered a problem while capturing these clips, it would give me some sort of warning - but no, it says successfully captured and then just doesn't save the darn clips! So frustrating to sit here for an hour watching it capture and have nothing to show for it. It's failed 8 times so far (that's 8 hours I'll never get back!)

How I successfully upgraded from iPhoto '09 to iPhoto '11 - Glitch Free.

I've been eagerly reading the forums PRIOR to installing iPhoto '11 and I'm about to dive in. I have an iMac 2.8 GHz Intel Core 2 Duo with 6GB RAM running Snow Leopard OS X 10.6.4.
I'm currently running iPhoto '09 (version 8.1.2) with 1403 events, 41,133 photos, 24 Faces and 29 Places. I have dozens of Albums and Smart Albums, Mobile Me Galleries, as well as 5 Keepsakes-3 cards and 2 books. The library itself is 185 GB in size and resides in an Admin User account in /Users/User/Pictures
Here is what I've done PRIOR to installing iPhoto '11
_*Fixed Permissions:*_
1. Holding down OPTION+COMMAND keys and then launching iPhoto '09 and selecting "Examine and repair iPhoto Library file permissions." I also rebuilt the small thumbnails but nothing else.
2. Opening disk utility and repairing disk permissions on Macintosh HD
3. Downloaded BatChmod and changed all the permissions as suggested in the links below. Initially the checkmark for apply to enclosed folders and files was not available. I selected another file then returned and it was available.
Also my permissions for the iPhoto library (and a quick survey of the package contents -right click with mouse to do this) were set to Read Write for my User account, for Group (_unknown in my case) and for Everyone without running BatChmod. Select your iPhoto library and press COMMAND+I to check this. I chose to run BatChmod anyways to ensure every file was indeed wide open as far as permissions go.
http://www.macchampion.com/arbysoft/ *-BatChmod link*
http://discussions.apple.com/message.jspa?messageID=12507401#12507401
http://iphoto11.wordpress.com/
_*Repaired Fonts*_
1. Opened Font Book and selected all the fonts then from the menus:
-Edit > Resolve Duplicates
-File > Validate Fonts
I then deleted the most severely affected fonts marked with red. I still had several marked yellow "minor problems were found. Proceed with caution."
Backups
1. Time Machine Backup on External Drive, plus another Time Machine Backup on another drive but it's about a week out of date.
2. Copy of iPhoto '09 application on a different External Drive then the Time Machine Backup (Usually found at the folder /Applications)
3. Copy of iPhoto '09 library folder on a different External Drive then the Time Machine Backup (Usually found in the folder /Users/User/Pictures )
This way I've got two ways of going backwards to iPhoto 09 if necessary - using the Time Machine backups (which appears to be painful for some) and failing that option simply dragging back actual untouched copies of iPhoto '09.app and iPhoto '09 library with photos, preferences, keepsakes, events etc all intact. (iPhoto '11 makes changes to the iPhoto '09 library files and removes the '09 app as well).
I then turned off Time Machine to prevent it from backing up further.
Install
Then in went the iLife '11 disc. No problems with the installation. After the install I *immediately opened Software Update from the Apple menu, and did not open iPhoto.*
iPhoto Update 9.1 came up and I installed it. A restart was not required but I did one anyways. Interestingly enough when I did a COMMAND+I to get info on the new iPhoto '11 library it showed different permissions of User -read/write, and Everyone -read/write. No groups listed.
I then opened iPhoto '11 and got the following message with the options to Quit or Upgrade. I clicked Upgrade.
" *The photo library needs to be upgraded to work with this version of iPhoto* Your photo library will not be readable by previous versions of iPhoto after the upgrade. The upgrade process for very large libraries may take an hour or more to complete."
My fairly _*large 185 GB library took 28 minutes to upgrade*_ and showed a progress bar as well as the monochromatic spinning wheel.
Success! All of my photos, events, places and albums, smart albums, MobileMe books and cards and slideshows are present and I can even edit a book I started. My iPhoto library is the same size give or take a MB.
Was all this necessary? We'll never know. I certainly wouldn't expect a first time Mac user to do the BatChmod steps or the Font Book steps, or even the Permissions steps, however I would expect everyone to do the backup steps of at least Time Machine.
We are talking valuable photos which are not replaceable, some people run into burning buildings to save their photos, so a quick backup seems reasonable. Turns out I didn't need my backups but I had no hesitation doing the upgrade with them in place.
In Summary:
1. Repair Permissions on your hard drive and iPhoto Library (see above for specifics)
2. Remove duplicate Fonts and Validate and Remove trouble fonts in Font Book
3. Backup, Backup, Backup. If possible with Time Machine and also separate exact copies of iPhoto library folder and iPhoto app itself.
4. Install iLife '11 and restart.
5. _*DO NOT OPEN iPhoto '11 YET*_, but DO OPEN Software Upgrade and install iPhoto version 9.1 (iPhoto '11 is version 9 of the software, iPhoto '09 is version 8)
6. Open iPhoto '11 and wait patiently for the upgrading of your previous library.
This process worked seamless for me, and was headache free. I'm now also going to keep an offsite backup of my computer either in the cloud or at a friend, family or work location.
Hope this helps!

Thanks so much - Iphoto has been driving me nuts for a while now. Permanent spinning wheel in Places and requiring force quit almost everytime. Following the advice to repair Iphoto permissions removed the spinning wheel from Places and Iphoto is completely back to normal

How to log successful logins to a syslog server in NX-OS

Does anyone know how to do this in NX-OS? I do it in IOS with the following commands:
login on-failure log
login on-success log
logging x.x.x.x
With that I get a syslog message that I can then log to a file to track who has logged into which device and when. But I can't find the syntax to do the same thing in the Nexus switches that we have. Does anyone know what the equivalent commands are?
Thanks,
Ben

Hi Ben,
By default, failed logins are logged.
You can checked the log using:
show logging logfile | last 15
and for every logging failed (by default) you will get something like this:
2012 Dec 18 14:51:08 Nexus5010-B %AUTHPRIV-3-SYSTEM_MSG: pam_aaa:Authentication
failed for user en from 2.2.2.1 - login
To get the success-login to show up in the logs we need to increase the level of the authpriv to 5 (it is 3 by default), and doing this will add a new log for failed or succesful connections.
Use the following command:
Nexus5010-A(config)# logging level authpriv 5
You can check loggin levels by using:
#show logging level
After you do this with the logging level you will see in the log something like this when a succesful login takes place:
2005 Jan 6 03:29:48 Nexus5010-A %AUTHPRIV-5-SYSTEM_MSG:    admin :TTY=unknown
; PWD=/var/sysmgr/vsh ; USER=root ; COMMAND=/usr/bin/strings/proc/18340/environ
- sudo
Now for a failed login and after increasing the authpriv level you will see the following logs:
2005 Jan 6 03:31:36 Nexus5010-A %AUTHPRIV-4-SYSTEM_MSG: pam_unix(aaa:auth):check pass; user unknown - aaad
2005 Jan 6 03:31:36 Nexus5010-A %AUTHPRIV-5-SYSTEM_MSG: pam_unix(aaa:auth):
aut
hentication failure; logname= uid=0 euid=0 tty= ruser= rhost= - aaad
For logging *****
Nexus7018(config)# logging ?
console           Set console logging
event             Interface events
ip                IP configuration
level             Facility parameter for syslog messages
logfile           Set File logging
message           Interface events
module            Set module(linecard) logging
monitor           Set terminal line(monitor) logging level
origin-id         Enable origin information for Remote Syslog Server
server            Enable forwarding to Remote Syslog Server
source-interface Enable Source-Interface for Remote Syslog Server
timestamp         Set logging timestamp granularity
You can use logging source-interface ....
Thanks-
Afroz
***Ratings Encourages Contributors ****

Service Desk NOTIF_CREATE no more success notification after saving

Hello experts
While testing Service Desk before Go-live, the transaction NOTIF_CREATE suddently started to behave abnormaly.
After fields completion, when the requester presses save and then instead of receiving the successful notification with a message number. The NOTIF_CREATE screen closes and a green arrow can be seen at the bottom of his SAP menu. Looks like OK to the user but creation was not completed successfully.
In the background, the support message was created with an appropriate number. But many other features like support team determination, automatic workflows, etc. are no more working.
I tried with different accounts even with SAP_ALL profile, doesn't look to be an authorization thing. I also searched for OSS notes without a clue.
What do you suggest me?
François

Hi,
I have upgraded to SPS17 and tried with other iBase components without success. I tried in debug mode step by step to see where it was stucked and it's hard to find since no message is returned. Looks like an exception is raised. This happen in the RDSWP_NOTIF_CREATE PROGRAM at line 15. It seems to be an exception of type "2 other". At that precise time, the debugger enters in an endless loop and a yellow exclamation sign is displayed in the status bar. (before it was a green check)
You talked about reintalling the iBase. The whole iBase with all components? How can I remove the existing iBase and then recreate it and finally have all the components attached as before?
Thanks,
Francois

IDOC not visible in IR but metadata successfully imported

Hi,
I have this wiered issue.
I want to import IDOC WPUSKR01 (cashier productivity) from BI.
But when I connect to BI system from IR to import Idoc structure, this IDOC is not visible.
But I can manually import the metadata from BI in idx2.
Now how to import this in IR?
I have imported other Idocs (like WPUBON) before and did the scenario successfully for BI.
Regards,
Anirudh Vyas.

Hi,
In BI Tcode we82 I have manually added the entries for WPUKSR01. Now Idoc is visible when importing in IR.
I have checked all the segments in we31, they are all released.
But it gives error:
Error: IDoc type WPUKSR01 contains errors (unable to read segments)
Then, I checked in R/3, there also WPUKSR01 was not there in we82. I manually added there and I was successfully able to import it in IR.
But the same thing is failing in BI. I have SAPALL permissions in all the systems.
Can I use Idoc imported from R/3 in scenario for BI?
regards,
Anirudh.

Idoc not seen in XI...sent successfully from R/3

hi guys
i have a scenario where i am emulating the outbound idoc process in a user exit. i use the FM IDOC_OUTPUT_INOTIF and it does the required work to send the idoc out. now i can see the idoc sent successfully in R/3 with a status 3, but it cant be seen in XI. now if i use that idoc number and run it thru we19, the idoc reaches XI. can someone tell me what i am missing. i have a feeling that the data is getting stuck somewhere. ironically R/3 is showing me a successful "Data sent to port OK".
please can someone put some more light on this.
Thanks everyone...

Hi Sanket;
Did you try looking in transaction IDX5 in XI? It is the IDoc adapter monitoring tool. It can show you IDocs that were received from R/3 but are not yet processed. Also, check out this artice I submitted awhile ago. It describes the process of troubleshooting IDocs through XI to AII. The first part discusses trouble shooting methods between R/3 and XI.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/technologies/rfid/sap rfid troubleshooting while uploading documents to aii.doc
Cheers,
John

Successful BC 2.1 in XP

Similar Messages

Maybe you are looking for