Cloning a screen

I have a screen I have already done a bunch of work on a screen for Medication Orders. I want to copy that screen and just change a few of the labels for a Medication Assessments Screen. Is there a way to clone what I already have to a new screen.

See:
AIDE 2013 for Visual Studio - Xpert360
Unleash the Power - Get the LightSwitch 2013 HTML Client / SharePoint 2013 book
http://LightSwitchHelpWebsite.com

Similar Messages

Cloning & Healing Screen Issues

I'm using CS5, and today anytime I try to use the Clone Stamp tool or Healing Brush, after I "alt-click" my reference point, when I move the cursor, the whole screen moves. I've tried updating my video driver thinking maybe it was that, but Windows says the driver is up to date. Help needed!
Thanks,
Scott A. Breaux

Awesome! You're welcome!
Thank you for checking back and marking the solving answer correct. This makes it easier for other users to find solutions for similar issues.
Benjamin

Good tutorials for FCE HD please?

books mainly and i know our own Tom is an author of a few
so i was gonna go and grab a couple books today re FCE HD, i wanted one to cover some basic stuff, and the other more advanced SFX etc like cloning, green screen techniques etc
(have been messing around and managed to make some cool scenes with light sabers, laser blast etc )
was looking at 50 Fast Final Cut Express Techniques but its dated 2003 so as i have FCE HD 3.5.1 would this be outdated please?
thanks for any suggestions including toms own books!

You can get it from Amazon
http://www.amazon.com/Class-Demand-Educational-Training-Tutorial/dp/B000JJ3Y6Y/r ef=sr113?ie=UTF8&s=dvd&qid=1218821521&sr=8-13
or directly from Class on Demand
http://www.classondemand.net/ClassOnDemand/final-cut-training/fcehd.aspx

Boot Camp won't boot Win 7 DVDs /Cloned disks - White cursor flashes once then Black Screen of Death.

Hi Guys,
I am having a serious issue with my machines ability to use boot camp. Here's what happend: I had Win 7 installed on the BOOTCAMP partition for a long while, then one day my HD crashed. So naturally I got my HD replaced from Apple and got Lion reinstalled and wokring flawlessly. Then I planned to get my Boot Camp going again, but my computer has a will against it I swear. So I run Boot Camp Assistant , create the parition and reboot. At this point I have my Win 7 disk burned using Disk utility in the drive, I am using a dvd disk image from Microsofts online store. I reboot and the computer hangs at the "pick a harddrive" grey for a second. Then the DVD drive spins up and I get a black screen, then for ever so slight a moment there is a flash of a white _ a the top left, then flash , nothing, the screen remains illumniated. Now I tried this multiple times , let it run over night , and nothing. Its almost as if my laptop will no longer boot the style of dvd that win 7 is.
Being a diagnostics first type of a person I tested all the variables, the win 7 cd works fine in other macbook pros. My computer boots other mac os x DVDs without a problem. I also tried using winclone to create a copy of another machines Boot Camp and flash it to my BOOT CAMP drive but this has the exact same result! Therefore it seems that the underlying system that runs my Macs ability to boot from Windows-style? partitions and dvd is broken. I also tried installing rEFIt, but that doesn't seem to help. I also tried booting off of an external USB drive with the same result. I tried zapping p-ram , scm and doing all software updates.
Has anyone expereinced anything like this? Anyone found resolution to a similar issue? Any other tricks related to Macs EFI and boot process that I could use to debug this? Anywhere that EFI stores logs possibly?
I went to the Apple's Genius Bar and they were stumped on my issue. I felt that they should be able to fix it considering it booted fine before I had Apple replace my HD.
Thanks to any responders, I'm really hitting my head on the table now and would love some help.

Have you reset the PRAM? It should usually be done when replacing any hardware. Have you got the latest EFI firmware for your Mac?
Not knowing what model /YEAR your MBP is (not that it would help me too much but the other fellas probably would) it's hard to guess as there are issue's for different models. The only thing I could find was it's usually caused by a non-conforming video driver. Microsoft had a page on it I found by accident and now I can't find it!
WinClone hasn't been updated by the original author in over a year, others have tweeked it a little to work with W7 but seems to be semi reliable, so the be aware.
Unless the other MBP's are identical in Model AND year your putting older or incompatible drivers on your MBP. Boot Camp, (especially if your using the drivers on the original install disks, like 10.6 and earlier) will only install for that specific computer. Just like the OS installer.
EDIT:
Oh yeah, are you sure you have the partition formatted the right way, thats another black screen problem.
Message was edited by: Jaygyver

After cloning, OAM dashboard screen doesn't come immediately,why?

Hi
Created instance using rapidclone. Login page ok,when i click on OAM Dash Board didn't showup, why? Does it need to restart all services once again or any workaround solution?
When i see database datafile directory, it shows only 45 data files where demo instance has 199 data files.
Please clarify?
Thanks
Ateeq

Does it need to restart all services once again or any workaround solution? Please bounce the application services and check then (before doing any modifications).
Login page is ok but problem with Dashboard only. Do you mean you do not see the link? Or the services are down even all the components are up?
Please review the following notes:
Note: 413067.1 - No OAM Application Manager Link in R12 after a fresh installation
https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=413067.1
Note: 419823.1 - OAM: Web Components Status: Shows Down Even When The System Works Fine
https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=419823.1

Screen Sharing/network problem seems confined to 1 volume. What's the fix?

I am having a networking problem on one of the volumes of my multi-volumed, three-Mac local area network, and I need a networking guru to identify the specific software file(s), application(s), or system configuration that is the cause of the problem. I have already spent several hours checking and re-checking the various hardware and system preference settings involved, and I have narrowed the problem down to a software corruption issue and/or system configuration issue on one volume.
I now need someone to identify specifically what the nature of the problem is, and how to eliminate it. I am not looking for a sledgehammer solution that says I should re-install all of the Mac OS X software on the problem volume. That may be held in reserve as a last resort. I'm looking for a more elegant approach, one that points out the specific corrupt files to remove without disturbing everything else.
Here's some background to set the context. I have a MacBook Pro laptop; a PowerMac iMac G5; and a PowerMac G4 hooked up in a network. All are running Leopard 10.5.8. All have file sharing and screen sharing enabled. Besides being able to connect to each other using registered users, my goal here is for each of the Macs to be able to share the screen of the others upon my demand. Since each of the 3 Macs can theoretically share the screens of the other 2, that makes a total of six possible connections. Five succeed; one does not. That's the problem. I am trying to determine why the iMac G5 cannot share the screen of the MacBook Pro.
The iMac G5 has no problem sharing the screen of the PowerMac G4. That connection is fast and immediate. But, every time that I hit the Share Screen button on the iMac G5 to try to connect to the MacBook Pro, I get a window with the blue barber pole spinning for two or three minutes as it is allegedly "Connecting to Mac Book Pro," followed by a window with a headline telling me that "Connection Failed to MacBook Pro." The text within that window goes on to say: "Please make sure that Screen Sharing (in the Sharing section of System Preferences) is enabled on the computer to which you are attempting to connect. Also make sure that your network connection is working properly."
Well, as I indicated, the PowerMac G4 has no problem sharing the screen of the MacBook Pro, so the Screen Sharing settings on the laptop are correct; and the iMac G5 can share the screen of the PowerMac G4, so its network connection is working properly in that regard. It is only in regards to sharing the screen of the MacBook Pro that the iMac G5 is not working properly.
The reason why I say that the issue must be unique to the one volume in question, let's call it "iMacG5 Music," is that another Leopard volume on the same computer has no problem whatsoever in sharing the screen of the MacBook Pro. Whenever I boot up in that volume, let's call it "iMacG5 JMB," it makes a network connection with a registered user name immediately, and it is able to share the screen of the MacBook Pro within a second of my issuing the command. In sharp contrast to the success of the iMacG5 JMB volume, the iMacG5 Music is unacceptably slow (several minutes slow!) in making a network connection with the MacBook Pro, and it always fails to share the screen of the MacBook Pro, preferring instead to take about three minutes to attempt the connection, before announcing its failure.
Since the iMacG5 Music volume makes an immediate network connection to the PowerMac G4, as well as sharing the screen of the PowerMac G4 the moment I ask it to, I have concluded that the hardware of the iMac G5 is just fine. The problem seems confined to the system software and/or associated networking files that are unique to the iMacG5 Music volume. I just don't know what those files could be, or where the problem lies, so I've issued this call for help.
Let me add one more little twist to this puzzle which baffles me even more. I use external LaCie Firewire drives as clone backups of my Macs. As part of my trouble-shooting process, I booted up from the cloned versions of the iMacG5 JMB volume and the iMacG5 Music volume. What I learned surprised me!
The iMacG5 JMB clone worked just fine in making a fast network connection to the MacBook Pro, as well as sharing the screen of the MacBook Pro. I expected that. What I did not expect was that the iMacG5 Music clone was also able to make a fast network to the MacBook Pro, as well as share its screen!
Yes, that's right. It's weird! Screen sharing works OK when I start-up from the clone of the iMacG5 Music volume, but it does not succeed when I boot up on the source itself! I was surprised to find that out, but I'm glad I did.
(Over the past few days since I executed the last clone, I did use Drive Genius to de-frag the source volume, and maybe that has contributed to the problem I am now encountering. But it's hard to say, since nothing else seems to be amiss.)
One solution, I suppose, would be to sync the clone back to the source. But, before I do that, I'm just wondering if anyone has a clue as to the nature of this problem on the source volume and what I might do to remedy it—short of re-installing the system software or restoring from the clone. Anyone have any insight to this problem?

CORRECTION #2:
Ignore the previous "CORRECTION" post.
Oops, excuse me, I wrote that sentence correctly the first time.
I was trying to point out that the ability of the iMac G5 computer to connect quickly and effectively to the PowerMac G4 when booted up into the iMacG5 Music volume was an indication (to me, anyway) that there is nothing wrong with the computer's hardware, nor its network connection ability, but that the problem lay somewhere in the files/settings used to connect to the MacBook Pro, which it cannot accomplish.
This is what happens when I get engrossed in one of these technical morasses and it ***** me into its vortex all through the night... time for bed.

MS-RDP black screen connecting to VDI

I just finished configuring a new install of VDA 3.4. Everything went well, no issues. VDI runs on a OEL 5.7 box, and VBox is running on a secondary OEL 5.7 box. I have one XP install, one Pool and one user accessed via LDAP. I've setup the pool and the XP vm (bridged) for host networking and Windows RDP. I've setup the user to be assigned to the pool and the desktop. I can see the desktop console within the VDI admin website. I have no firewall or port issues.
When I attempt to connect via MS-RDP all I get is a black screen, and eventually a timeout/failure. Looking at the cacao logs, it shows the access to the desktop...
Preparing....
Registering...
Starting....
Successfully started
Waiting for VirtualBox addtions
VirtualBox additions running
Waiting for IP address
Got IP address
Waiting for RDP connection...
and then...many minutes later
Error preparing desktop for use....Timeout expired waiting for RDP connection on desktop
Attempting to change state...
and then the MS-RDP client finally comes back with an error. BTW, the same log messages are posted when using vda-client -u myuser.
Any ideas why it wont finish the connection?
ron

Hi Ron,
This suggested that the desktop assigned to the the user does not have the RDP service enabled (which should have been enabled in the template if cloned from one), or there may be a firewall/routing issue between the SunRay server the user is connected to (if using Sun Ray Client).
Note that the desktop console view used by the VDI admin console is using VRDP, so this is not dependent on the MS-RDP service running on the Xp desktop.
It could also perhaps be an issue where the user you are using does not have RDP access, which could point to a AD policy setting if using AD, etc.
Try connecting to the VM IP address directly using a rdesktop or microsoft client to see if the problem is with the XP desktop itself or not.
Regards,
Ryder

After getting the dreaded gray/blue screen, I tried to run disk repair on the internal disk. I got an error message saying "Disk Utility can't repair this disk and restore your backed-up files. The volume Macintosh HD could not be verified completely

After getting the dreaded gray/blue screen, I tried to run disk repair on the internal disk. I got an error message saying "Disk Utility can't repair this disk and restore your backed-up files. The volume Macintosh HD could not be verified completely." What do I do now? This is an iMac and I'm running 10.6.8.

Clean Install of Snow Leopard
Be sure to make a backup first because the following procedure will erase
the drive and everything on it. See below for how to clone a drive.
     1. Boot the computer using the Snow Leopard Installer Disc or the Disc 1 that came
         with your computer. Insert the disc into the optical drive and restart the computer.
         After the chime press and hold down the "C" key. Release the key when you see
         a small spinning gear appear below the dark gray Apple logo.
     2. After the installer loads select your language and click on the Continue
         button. When the menu bar appears select Disk Utility from the Utilities menu.
         After DU loads select the hard drive entry from the left side list (mfgr.'s ID and drive
         size.) Click on the Partition tab in the DU main window. Set the number of
         partitions to one (1) from the Partitions drop down menu, click on Options button
         and select GUID, click on OK, then set the format type to MacOS Extended
         (Journaled, if supported), then click on the Apply button.
     3. When the formatting has completed quit DU and return to the installer. Proceed
         with the OS X installation and follow the directions included with the installer.
     4. When the installation has completed your computer will Restart into the Setup
         Assistant. Be sure you configure your initial admin account with the exact same
         username and password that you used on your old drive. After you finish Setup
         Assistant will complete the installation after which you will be running a fresh
         install of OS X. You can now begin the update process by opening Software
         Update and installing all recommended updates to bring your installation current.
Download and install Mac OS X 10.6.8 Update Combo v1.1.
You may be able to backup your data if you have an erased external drive you can use. Before you do the above but after you have opened Disk Utility you can try to clone your drive:
Clone using Restore Option of Disk Utility
1. Open Disk Utility.
2. Select the destination volume from the left side list.
3. Click on the Restore tab in the DU main window.
4. Select the destination volume from the left side list and drag
       it to the Destination entry field.
5. Select the source volume from the left side list and drag it to
      the Source entry field.
6. Double-check you got it right, then click on the Restore button.
Destination means the external backup drive. Source means the internal startup drive.
Now this will only work if the drive is accessible and can be cloned by Disk Utility. Otherwise, you would need to access your drive from another Mac that you can connect via Firewire - Target Disk Mode.

After upgrading to Lion blue screen appears at start up have to reboot to log in

I have been having issues when I first downloaded and installed Lion it installed then when it rebooted a blue screen would appear and nothing would happen. I rebooted the system and it came up. Now I installed the latest software update and the same thing happend did the same steps. Yesterday I had to boot my computer up twice for it to get to the lion login screen. I have called apple and their resolution is to wipe out and restore from time machine. Has anyone else seen this issue?

Sounds like directory damage of some sort. A few options.
1) Buy Diskwarrior. Probably the premier tool for directory repair. There's a download version but it needs to be run from a booted drive which it seems you don't have. You can wait for delivery of the disc which will allow you to boot from the disc and run the application.
2) Buy an external firewire hard drive. Get one big enough for future backup use. Meanwhile, install a new version of the operating system on that drive, boot from the drive and see if you can even see the files on the main rive. If directory damage isn't too bad you may be able to copy critical ones, though the problem with directory damage is you don't know if you're copying a damaged file. That's when just getting Diskwarrior first may just make more sense.
OSX doesn't let you make a bootable disc just by copying files onto a CD the way OS9 used to. There's a utility called CloneX that does this, but I haven't tried it. Usually what you can do is clone hte internal drive to an external drive as part of backup. The cloning places a bootable copy of the OS onto the external. Simply dragging OS files across no longer works.
By the way, the external drive has to be Firewire in order for it to be boootable. USB is okay for backup but you can't use it to boot an older computer in an emergency (new Macs are okay).

10.6.2 Died - Blue screen of death for Snow Leopard?

OK. I upgraded Tiger via the SL Boxed Set yesterday. The install went pretty flawless - no hiccups or issues at all. It is a clean install. I had cloned Tiger to an external USB drive - that's why I'm able to type this message now. I upgraded to 10.6.2 this morning and still everything seemed fine.
I had the migration pretty much complete. I was getting used to some of the new features, I had moved/installed everything, etc. I have played games, used mail, internet, photo software, etc. with no problems. Today while using the computer, I noticed I would attempt to start a program, but the icon would just bounce in the dock and would not open. The programs that were already open were working fine - Safari, Apple Mail, and Google SketchUp. So, I finished up what I was doing and restarted my computer. That restart was the last time I ever saw the 10.6.2 desktop.
Upon reboot, I get the Apple logo with gray screen, then the blue screen, then it freezes. I disconnected all connected devices (USB/Firewire, etc.) and unplugged for 30 minutes - no luck. Booted from the SL CD and ran Disk Utility. Disk Utility found no errors and said all was great! I verified the disk and repaired it even though it said it didn't need it. Still no luck. Just the blue screen of death.
Any ideas where to go from here? I can boot via my USB external drive with 10.4.11, but that doesn't really correlate to my problem. I REALLY don't want to have to reinstall everything all over again - it took me ALL DAY to get it all moved over and I still have some to do. Thanks for any tips or tricks.
Model Name: iMac
Model Identifier: iMac5,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2.16 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache (per processor): 4 MB
Memory: 3 GB
Bus Speed: 667 MHz
Boot ROM Version: IM51.0090.B09
SMC Version: 1.9f4

moze229 wrote:
I suppose the new install just wrote over all the files, and it appears to have left all of my settings in tact. Now, if I just knew which one or few files was the problem, I'd be really satisfied.
It might help to understand that the procedure affects primarily OS files, for instance by replacing the existing copies of the binaries the OS contains with fresh ones from the installer disc. It does not affect user created files & settings at all, except possibly for some system-wide settings that might have become corrupt. It won't affect third party items either, except that it may move a few of them known to be incompatible with Snow Leopard in a root level "Incompatible Software" folder, as explained in Mac OS X v10.6: About incompatible software.
So, the most likely cause of your problem was a damaged or missing OS domain file that the installer replaced. How the file got damaged or which one(s) were involved is hard to say. Some third party software can do this, especially hacks & so-called system enhancements that ignore Apple's Developer Guidelines for appropriate entry points into the OS. Improper shutdown, like from a sudden loss of power, can sometimes do it. User error may be involved, especially if you use the Terminal to modify system files & settings or otherwise make changes to the root level folders normally managed by the OS (/System, /Library, & the ones not normally visible from the Finder).

24" Intel iMac - Intermittent lack of screen image

I have a friends 24" iMac which has some performance issues.
It has been crashing and hanging a lot and occasionally has lines on the screen.
This could be a logic board or graphics issue, but my first thought was to reinstall the OS from scratch and during this process I have discovered a weird screen issue.
I began by booting using the original install disc and resetting his password
I then cloned the internal drive using superduper in preparation for wiping and reinstalling Leopard on the internal drive.
To achieve this I plugged the iMac and the external drive into my MacBook as a firewire target disk
(The firewire logo displayed normally on screen)
I then connected the external drive directly to the iMac and booted from the new clone to test it.
The apple logo appeared and then the login screen, after entering the password the desktop appeared, but the menu bar was halfway down and only part of the screen was actually displaying anything other than the original blue colour from startup. (It didn't look like a resolution issue)
I forced a restart and booted from the original internal drive, I was able to hold option and see and select the internal drive, but the computer then proceeded to startup with a black screen
This behaviour then persisted as I tried to repeat each of the following multiple times
Reboot while holding C to bootfrom the leopard dvd
Reboot, choosing external clone drive by holding option
Reboot while holding option and choosing internal disk
Reboot while holding option and choosing install dvd disk
Reboot without holding anything to automatically boot from the internal disk
At this point I called it a night
Today I turned on the machine and reset the pram followed by a successful boot using the clone drive and another successful boot using the internal drive so I proceeded to boot from the install disk, erased the internal drive and installed leopard.
The install proceeded without issue until the progress bar was nearly all the way there at which point I left the room for about half an hour
On my return the screen was black and I was forced to hold down the power button to restart at which point the grey screen appeared, followed by the apple logo and then the black screen again, but this time I could hear the leopard intro movie playing - it appears that everything is working normally apart from the screen
I have since held down Command and S to boot into single user modem where the terminal displays correctly on screen.
I suspect allowing the machine to cool was the reason I had initial success this evening, but what could cause this problem?
I am thinking a graphics card issue, but does that mean the graphics card is not involved in displaying the firewire target disk logo, single user mode or the different hard disk options available at startup?

Update:
Waiting several hours again allowed booting, but something is corrupted because the machine hangs badly (frozen screen and only the cursor moves)
I think there are BOTH hardware and software problems
At this moment;
•The iMac has performance issues with the original setup as received from my friend
•The iMac has performance issues with the new install of leopard and system migrated user account
•The iMac no performance issues and only minor graphics performance issues when booted from my MacBook as a Target Disk
I am posting from it right now and the only issue, which occurred on boot, was some lines on the screen
I am planning to boot again into the new leopard install, but with a new user account if I can get far enough to create one, otherwise I will enable root and see if that allows the system to run with any stability
I am expecting an hour or so of use to result in the blank screen issue again.

11.5.10.2 cloned instance; responsibilities are missing

11.5.10.2 instance.
ATG Rollup 3.
OS: IBM AIX , 5.2.0.0
Java: 1.3.1
User logs in. All resps (responsibilities) are displayed. Clicks on 'System Administrator' responsibility. Chooses 'Security/Define' , User define form pops up.
Queries his own id. Adds a new resp OR end_dates a resp. Clicks on "Navigotor" button on top of the form. He finds his actions (adding or removing resp) were taken care. He closes all form screens. Comes back to homepage (jsp version, main page). Clicks on refresh button of Internet explorer. Changes are not affected. Still he can see old resps. He logs out. Logs in. No use. Still he finds those changes did not take palce. ADDED TO THIS, FOR SOME USERS, 'SYSTEM ADMINISTRATOR' resp is gone.
BUT, if you login as "/f60cgi/dev60cgibin" , everything is fine. You can see expected changes taken place.
In short, users resps are missing when one adds or removes resp.
Any thoughts? Replies are highly appreciated.
Thanks,
GKM

See responses on other forum: 11.5.10.2; Cloned instance. Missing responsibilities

Help needed in file tx from MBP with blacked out screen to ext. HDD

just got off the phone with Apple .... seems like I might have a cursed NVIDIA graphics card in my Macbook Pro 2007 model (2.4GHz core2duo)
had basically kept my MBP ('07 model) in sleep mode when I went to office. When i came back, the white light in the front wasn't pulsing anymore and it was replaced by a bright constant white light - proceeded to open the lid... and the screen was totally dark ... tried a few key combinations in random to get it up and running but to no avail .. then checked a few forums on this issue... seems like lots of ppl have the issue but a lot of them also managed to get the screen back on by resetting the SMC and PRAM (which I proceeded to try) ... unfortunately hasn't worked for me despite multipe resets of the SMC and PRAM. Gave Apple a call and all things point to the graphics card having conked out ... this ***** big time!! ...
The worst thing is that after switching on my machine, I can still load software by doing the keyboard shortcut for spotlight and typing the application ... e.g. itunes is working and I'm still managing to play songs through myh machine.. only issue is that the display is totally dark...
Now.. my big issue before I send it across to the service centre is backing up my "Downloads" folder....
Can someone help me with how I can go about doing this through terminal ? I think I just might be able to pull it off with the keyboard if I get sufficient and specific help!!!!
basically I'm looking for transfer of all contents from "Downloads" folder to an external hard disk with the name "Active" ...
help would be greatly appreciated!
Any suggestions on methods of backing up my data would be great!!...
Also, are there any precautions I should be taking/ things I ought to be wary of when sending my machine in to an authorized service centre?

Welcome to Apple Discussions!
Does your hard drive spin up? And do you have access to another MAC?
If so, you could see if you could mount your Mac's hard drive on the other Mac's desktop using FireWire Target Disk mode:
http://support.apple.com/kb/HT1661
Also mount an external drive equal or larger than your internal drive on the host Mac. Then use a cloning utility like Super Duper on the host Mac to clone your internal drive onto the external drive. This will give you a backup of everything that is on your internal drive--it will be an exact copy. This would take some time, but would likely be the best way to back up everything on your drive.
http://www.shirt-pocket.com/SuperDuper/SuperDuperDescription.html
It is especially important to back up everything on your drive, because when your Mac goes in for repair, sometimes the drive is erased and the OS reinstalled in the process of troubleshooting. Also, they will likely elect to thoroughly test the machine and do any repairs that are necessary, which could possibly include replacing the hard drive. If you have any sensitive data on the drive, you may even want to erase it before sending it in just on general principles.
Good luck!

Problem cloning hard disk for 10.6 setup

Hi all,
I just got Snow Leopard for my office MacBook Pro and for my home MacBook. On both machines I got an error message when trying to install it that my partition scheme is not GUID, so 10.6 won't install.
First I worked on the MBP. It has a 250 GB internal HDD of which 105 GB were used. So I grabbed a 160 GB USB disk, booted from the SL DVD and cloned the internal HDD to the USB one (using Apple's Hard Disk Tool). I enabled the "Delete target volume" option, which worked fine. After re-partitioning the internal HDD with a GUID volume and cloning all the stuff back, SL installed without any problems.
Now I tried the same on my home MacBook. It has an internal 500 GB HDD of which 97 GB were used. When I tried to clone it to the external 160 GB drive, the program complained that there is not enough space ("Delete target volume" switched on). So I switched off the Delete... option (the drive was empty anyway) and copying started, however I ended up with only 92 GB on the USB drive.
I assumed that some indices whatsoever were not copied and - since I still have a Time Machine backup of the internal HDD - decided to copy the stuff back to it after GUID-partitioning the internal drive. This went through last night (all the 92 GB were returned to the hard disk), but now the MacBook won't boot up. It stops with a grey screen.
Any idea what gives that? Why did I end up with 5 GB less on the USB drive?
I will now have to start from scratch, install 10.6 on the internal drive after deleting it and do a migration of my data from the Time Machine backup. This should give me a clean environment but preserve all my data and settings (at least this is what I read so far...
Any comments, anyone?
Thanks & best wishes,
Thomas.

solved. Got home this evening and switched on the MacBook while holding "alt" down, selected the internal volume and it booted up fine. So far I see nothing that is missing, Spotlight is indexing the hard drive, so I guess this was the resaon for 5 GB less on the copy. Anyway, I will install the SL upgrade soon, just over Leopard which is installed on the MB now.
Best,
Thomas.

Cloned hard drive does not boot

I have an old G4 Cube which I decided to upgrade with some spare parts. The HDD I replaced was a 5400rpm 20GB Maxtor that appears to be the original, and the replacement drive is a 7200rpm 30GB Quantum Fireball that was pulled out of a Windows machine. Both are IDE, obviously.
I used an external USB to IDE adapter to mount the new hard drive, formatted it to "Mac OS Extended (Journaled)", and restored the original hard drive to the new one using Disk Utility.
The new hard drive doesn't want to boot when I put it in the system. It started up, chimed, restarted for some reason, then froze at the screen with the apple and the spinning circle.
If this were a Windows computer, I'd suspect the MBR didn't get cloned properly. I'm not sure if there's a similar problem with Macs.
And I'm not too keen on using Carbon Copy Cloner or SuperDuper when I can have a free alternative.
Does anyone have a solution? I've tried resetting the PRAM, etc. Is my HDD incompatible?
Thanks in advance

Hi-
Disk Utility images are difficult to get right for most people.
If this were a Windows computer, I'd suspect the MBR didn't get cloned properly. I'm not sure if there's a similar problem with Macs.
You are probably correct in your thinking. Different, yet similar in function.
And I'm not too keen on using Carbon Copy Cloner or SuperDuper when I can have a free alternative.
Huh?
CCC is voluntary shareware and the basic full clone version of SD! is freeware.
SD! is the better of the two, and definitely worth having.
Both are much better than Disk Utility.
Does anyone have a solution?
Use SuperDuper!.

Cloning a screen

Similar Messages

Maybe you are looking for