A sparse image or sparse bundle question in relation to a NAS

Hi all,
I want to create a sparse image or bundle on my Synology DS713+ NAS to store my iPhoto and Aperture libraries.
The reason for a sparse image or bundle lies in the fact that both iPhoto and Aperture very much like a solid Mac Journal formatted drive to operate on.
Because I use an iMac and a MacBookPro I want these libraries available for both computers, and while they reside on a NAS they are 'automatically' backed up, and acessible to both computers.
I've tried storing the iPhoto library on the NAS directly (not Mac formatted but some Linux format, nót FAT32 anyway), but this was performing very poor (copying the library took hours and hours), and I've read on many NAS and Synology forums that this is not the way to go. The best solution I've read from these forums is to create a Sparse Image or Bundle on the NAS to benefit fully form an iPhoto or Aperture Library.
Now I have created a Sparse Image, and mounted it, and moving (copying) an iPhoto Library to it is done in a snap (amazing).
But having the Sparse Image mounted on my iMac, I cannot acess it on my MacBookPro unless I first umount it on the iMac, and then mount it on the MacBook.
Is there a way that such a Sparse Image can be mounted on more than one computer at the same time. In my case, mounted on both the iMac and the MacBook?
Or must it specifically be a Sparse Bundle to accomplish this, or maybe some Terminal wizzardry to get this done?

I'm a little confused here, but what you did answer did help quite a bit. Thanks for that. Anyway, I'm having problems adding to the array. It keeps telling me 'cannot find symbol - method add (double). I'm assuming that this method should be defined in the AuditRecord class, which has been given to me but there seems to exist no method in that class called 'add'. I suppose I could make one, but my professor said that we shouldn't be modifying the AuditRecord class at all, which leads me to believe I'm on the wrong track again. Anyway, here's my updated code in the hopes that it's a simple mistake that I'm making once again:
public class AuditTrail
    private ArrayList<AuditRecord> auditTrail;
    //ArrayList<AuditRecord> auditTrail = new ArrayList<AuditRecord>();
    //private double amount;
public AuditTrail()
   auditTrail = new ArrayList<AuditRecord>();
* Add a record
public boolean add(double amount)
       if (amount > 0)
       //create auditrecord and add to audit trail (array list)      
       AuditRecord auditTrail = new AuditRecord(amount);
       //auditTrail.AuditRecord(amount);
       auditTrail.add(amount);
       System.out.println("Amount of "+amount+" added.");
       return true;// similar behavior to a collection
    else
        System.out.println("Invalid deposit amount.");
        return false;
}

Similar Messages

  • Time Machine on NAS, sparse image bundles, etc

    I have a specific question about using Time Machine with a NAS drive. I have a NAS setup, and I just installed a 2nd drive there specifically for backups. I have 2 macs, a MBP & an iMac. I followed instructions somewhere for creating a sparsebundle disk image on the NAS drive for each machine to get time machine to work over the network, and got it to work. Since the drive is 1TB, I made 2 images at 450GB each, even though the 2 machines only currently need about 90GB & 150GB.
    Now, based on advice elsewhere, I set up Superduper to back up to the same drive. This uses a similar process of creating a sparse image on that drive. Note that I say sparse image, not sparsebundle - I tried using the existing sparsebundles already created, but superduper didn't seem to want to do that, and in fact although sparsebundle is a choice in their menu, only sparse image would work. So I went ahead and did this but only with my MBP. It indeed created a separate sparse image, and it takes up the full amount of space necessary to back up the entire drive (90GB).
    What I'm wondering is if I'm running the risk of quickly running out of room on my NAS drive, since I think TM will fairly quickly eat up as much space as you give it (450GB X 2 = 900 GB), and the superduper backup is taking up the full amount of hard drive space needed (90GB) to make a full backup (based on what I had read, I thought that somehow using superduper onto the same drive as your TM backups would mean superduper would 'piggy back' on TM's backed up files and only add the components needed to create a startup disk, and therefore not take up much space.) I was still hoping to also back up the iMac (120GB) with Superduper onto the same drive, but don't want to do that yet until I have some peace of mind about this question...
    Thanks for any insight you may have!

    doublelibra wrote:
    I have a specific question about using Time Machine with a NAS drive. I have a NAS setup, and I just installed a 2nd drive there specifically for backups. I have 2 macs, a MBP & an iMac. I followed instructions somewhere for creating a sparsebundle disk image on the NAS drive for each machine to get time machine to work over the network, and got it to work. Since the drive is 1TB, I made 2 images at 450GB each, even though the 2 machines only currently need about 90GB & 150GB.
    you should know that TM backups to 3rd party NASes are not officially supported. you used a hack to make it work. but you use it on your won risk and with no guarantees.
    Now, based on advice elsewhere, I set up Superduper to back up to the same drive. This uses a similar process of creating a sparse image on that drive. Note that I say sparse image, not sparsebundle - I tried using the existing sparsebundles already created, but superduper didn't seem to want to do that, and in fact although sparsebundle is a choice in their menu, only sparse image would work. So I went ahead and did this but only with my MBP. It indeed created a separate sparse image, and it takes up the full amount of space necessary to back up the entire drive (90GB).
    What I'm wondering is if I'm running the risk of quickly running out of room on my NAS drive, since I think TM will fairly quickly eat up as much space as you give it (450GB X 2 = 900 GB)
    no, that won't happen. TM is very economical in how it stores backups. on every backup it only backs up afresh new and changed files. everything else is *hard linked* to existing backup copies. that's why incremental TM backups are usually quite small and fast.
    , and the superduper backup is taking up the full amount of hard drive space needed (90GB) to make a full backup (based on what I had read, I thought that somehow using superduper onto the same drive as your TM backups would mean superduper would 'piggy back' on TM's backed up files and only add the components needed to create a startup disk, and therefore not take up much space.)
    NO. nothing like this is remotely true. superduper and TM backups are fully independent and don't interact at all. use separate sparse bundles for TM and superduper backups.
    I was still hoping to also back up the iMac (120GB) with Superduper onto the same drive, but don't want to do that yet until I have some peace of mind about this question...
    Thanks for any insight you may have!

  • AES-256 user home directory sparse image bundle in Lion?

    Snow Leopard and previous had file vault to protect users' home directories as, I believe, AES-128-encrypted sparse image bundles. As I understand it now, under Lion, the options are to enable AES-128 whole disk encryption, or, if upgrading an existing snow leopard machine with a legacy file vault user account, to maintain that legacy file vault user home directory. However, under this second approach, additional users' home directories cannot be individually "file-vaulted" and instead, would require that legacy file vault  be decrytped and then the entire disk be encrypted.
    I am thinking that it would be advantageous from a security standpoint if an individual user home directory could remain encrypted, if that user were not actively logged in. Then, all contents would be inaccessible to other users, including administratively privileged users, and also that user's home directory would remain encrypted when the computer was turned on and booted up because as I understand it, file vault 2's real strength lies in protecting "data at rest" versus "data on a powered up and mounted file vault 2 volume".
    To that end, I am wondering, regardless of whether file vault 2 is enabled or not, whether an existing user home directory and all of its contents be converted to an AES-256-encrypted sparse image bundle, using Disk Utility, and exist at the /Users directory space, mounting and decrypting "on the fly" from the login window at user login just like how a legacy file vault home directory is treated under snow leopard, independently of whether file vault 2 was enabled on the whole disk or not. This would also permit later addition/conversion of another "file vaulted" user account whether fle vault 2 were enabled or not.
    To recap, an AES-256-encrypted sparse image bundle that would mount upon user login just like a legacy file vault user home directory does. Does anyone know if something like that is doable, and has that road already been travelled successfully? If so, I'd love to read a step-by-step, play-by-play, set of instructions on how to do just that.

    I think I got a solution worked out.  I don't mind if things get installed in /opt as long as pacman tracks it, and I found ruby-enterprise-rmagick in the AUR as an orphan.  I adopted it, updated it, installed it, and it's working great with my code.

  • Hdiutil and creation of more then one partition in a dmg and sparse image?

    Hello,
    My main question,
    after reading the man page and googling, I can't find any way to create a DMG file with more then one partition. Is this even possible?
    My finaly goal is to attach those with -mountRandom and - nobrowse from inside a cocoa.app.
    I need the return value to get the random path to those partitions.
    hdiutil attach test.dmg -mountrandom /Users/dev/Desktop/testdmg
    /dev/disk7 GUIDpartitionscheme
    /dev/disk7s1 Apple_HFS /Users/dev/Desktop/testdmg/dmg.A43MrA
    But I see that when I use a mutli partition dmg ( here simulated ) I will have to look for one or more random paths, something like this.
    hdiutil attach test.dmg -mountrandom /Users/dev/Desktop/testdmg
    /dev/disk7 Applepartitionscheme
    /dev/disk7s1 Applepartitionmap
    /dev/disk7s2 Apple_HFS /Users/dev/Desktop/testdmg/dmg.A43MrA
    /dev/disk7s3 Apple_HFS /Users/dev/Desktop/testdmg/dmg.7IaUpK
    What is the best way?
    to grep a line wich contains '/dmg./ and then awk print $3 ?
    path=/Users/dev/Desktop
    hdiutil attach $path/test.dmg -mountrandom $path/testdmg | grep '/dmg.' | awk '{ print $3 }'
    but what when I attach f.e a sparse image not using the -mountRandom, then I have no '/dmg.' just volumes?
    Is that doable in one universal piece of code?

    I can only answer your question re:multi partition on a .dmg with:
    doug-penningtons-power-mac-g4:Desktop dougp$ diskutil list
    /dev/disk0
    #: TYPE NAME SIZE IDENTIFIER
    0: Applepartitionscheme *57.3 Gi disk0
    1: Applepartitionmap 31.5 Ki disk0s1
    2: Apple_Driver43 28.0 Ki disk0s2
    3: Apple_Driver43 28.0 Ki disk0s3
    4: AppleDriverATA 28.0 Ki disk0s4
    5: AppleDriverATA 28.0 Ki disk0s5
    6: Apple_FWDriver 256.0 Ki disk0s6
    7: AppleDriverIOKit 256.0 Ki disk0s7
    8: Apple_Patches 256.0 Ki disk0s8
    9: Apple_HFS Joe 57.1 Gi disk0s10
    /dev/disk1
    #: TYPE NAME SIZE IDENTIFIER
    0: Applepartitionscheme *10.0 Mi disk1
    1: Applepartitionmap 31.5 Ki disk1s1
    2: Apple_HFS me 10.0 Mi disk1s2
    doug-penningtons-power-mac-g4:Desktop dougp$ diskutil partitionDisk disk1 2 HFS+ leroy 5M HFS+ madge 5M
    Started partitioning on disk disk1
    Creating partition map
    Formatting disk1s2 as Mac OS Extended with name leroy
    Formatting disk1s3 as Mac OS Extended with name madge
    [ + 0%..10%..20%..30%..40%..50%..60%..70%..80%..90%..100% ]
    Finished partitioning on disk disk1
    /dev/disk1
    #: TYPE NAME SIZE IDENTIFIER
    0: Applepartitionscheme *10.0 Mi disk1
    1: Applepartitionmap 31.5 Ki disk1s1
    2: Apple_HFS leroy 5.0 Mi disk1s2
    3: Apple_HFS madge 5.0 Mi disk1s3
    Message was edited by: doug pennington

  • Disk Utility Restore from Sparse Image taking forever

    I created a sparse image backup of my MBP C2D using SuperDuper! before sending the laptop back to Apple for repair. I wiped the drive clean before shipping. I now have the laptop back and am trying to restore the sparse image to the HD.
    The sparse image file is on an HD in my G5 tower and is just over 108 GB. I booted the G5 into target disk mode and connected it to my MBP via FW800. I then booted off the Leopard install disk and launched Disk Utility to do the restore.
    The sparse image mounts fine in Disk Utility and is specified as my source for the restore.
    I started this restore last night before I checked out for the night and when I got up this morning, Disk Utility showed about 35-40% of the image had been restored and 14 HOURS were remaining. That seems a little excessive after it had already been running for well over 9 - 10 hours.
    The sparse image mounts on the MBP just fine using target disk mode from my G5 -- so as far as can tell, my backup image itself is ok.
    My question is this: is the Restore function performance of Disk Utility with sparse images really this bad or is something wrong with what I am doing? I really don't want to rebuild my laptop from scratch, but if I have to wait 34 or more hours for Disk Utility to finish a restore -- it might be quicker to rebuild it.
    Any ideas out there?
    Message was edited by: Randy Vose

    Randy Vose wrote:
    I created a sparse image backup of my MBP C2D using SuperDuper! before sending the laptop back to Apple for repair. I wiped the drive clean before shipping. I now have the laptop back and am trying to restore the sparse image to the HD.
    The sparse image file is on an HD in my G5 tower and is just over 108 GB. I booted the G5 into target disk mode and connected it to my MBP via FW800. I then booted off the Leopard install disk and launched Disk Utility to do the restore.
    The sparse image mounts fine in Disk Utility and is specified as my source for the restore.
    I started this restore last night before I checked out for the night and when I got up this morning, Disk Utility showed about 35-40% of the image had been restored and 14 HOURS were remaining. That seems a little excessive after it had already been running for well over 9 - 10 hours.
    The sparse image mounts on the MBP just fine using target disk mode from my G5 -- so as far as can tell, my backup image itself is ok.
    My question is this: is the Restore function performance of Disk Utility with sparse images really this bad or is something wrong with what I am doing?
    no the restore function is not this bad.
    something must be wrong with your sparse image. you should have tested it before sending the computer for repairs. and why did you use a sparse image at all?! you should have made (and tested) a standard clone.

  • Finder error -36 when transferring some sparse images over 100GB+

    Hi,
    I'm currently backing up sparseimages of different sizes onto backup hard drives for video editing.
    I'm using the latest iMac with Mountain Lion.
    I use Sparseimages in order to seperate FCPX projects (best way to keep organised so far in my opinion).
    Although with the amoung of footage and size of files, I need to backup them up on different drives every so often to free up some space for myself.
    While transfering the backups I noticed the error -36 would happen on the finder for some files. Specifically the larger ones sized 100GB+.This is for my work and is VERY important. So whoever can find me a good fix or explanation for this issue, will have my greatest gratitude!
    Now before I get bombarded by questions and abused by "its already been covered - google is your friend", here are the setup and the things I found out about the issue:
    iMac w/ OSX 10.8
    - Thunderbolt to Drobo 5D (with 5x 3TB drives)
    - USB 3.0 Startech Dock for 3.5" Sata hard drives - I'm using a WD 3TB internal drive on the dock
    1. In most cases transfering a file between the following locations causes the WD drive to eject and the finder to create a -36 error:
    (In every case, smaller sparseimages are copied just fine - anything 100GB+ just ejects the disk and causes the error)
    - Drobo 5D to WD - Ejection + Error -36
    - iMac Fusion Drive to WD - Ejection + Error -36
    - Drobo 5D to iMac Fusion drive: NO ERROR
    Now before you go and say that it may be an issue with the particular drive i'm using in the dock; I've swapped the WD drive I want to copy the files on with another WD drive and managed recreated the same error.
    I've used Carbon Copy Cloner and got an error saying I shouldn't modify or change the disk while transfering when attempting to transfer the larger files.
    I did find a way around it, but it's really long and would take days to do. It's to create a new sparseimage on the desktop and transfer all the content of the old sparse into the new one then transfer the new sparse into the WD docked drive. For some reason... that works, although, generally it takes a few hours to transfer one of the 100GB+ sparses, and having to copy the entire content onto the desktop then yet again copy it to the WD drive seems lenghty and unecessary. There MUST be a fix, I'm sure there's a way around it. Otherwise I'm stuck for the next few weeks with transfering alone
    Thanks in advance for help!
    Luke

    Sorry, I see what you mean, although I'm having difficulty figuring out which one it could be for the following reasons:
    1) Corrupt Directory:
    The sparse images in question, the ones giving me the errors, mount fine if I run them directly from the Drobo 5D. They also can be transfered successfully to the desktop and can run from there too. But transfering to the 3.0 USB dock causes the error.
    2) Failing Disk:
    I've used a different 2 different hard drives in the same dock and tried to transfer the same sparse images... but no luck! Although copying it straight onto the deskop is fine. So the drive hasn't failed.
    So that's why I reckon it has something to do with transfering large files to the Dock.
    Any suggestions will help! It could be the docking station but I thought it could maybe be the OS handling the large files the wrong way or perhaps an issue with USB 3.0? I don't know...
    NOTE: There are generally no errors, I can transfer many many files and folder at a time without an issue. It is ONLY when the file is very large and transfering that it EJECTS the drive and causes the -36 error
    UPDATE:
    Just saw your update! Will do a block test on the drive now, although, as I mentioned early on this comment, it seems to be that the other drives I used have the same problem.
    Also, I was wrong, it's Seagate drives I'm using, if that makes any difference?
    So many drives here, I'm getting confused! hehe

  • Time Capsule continues on wrong sparse image

    This is the second Mac I have seen this happen to and on two different Time Capsules (new feature?) Both Macs are brand new (so new MAC addresses) and were migrated from old 10.5.x machines (so they kept their Sharing names and accounts). Both new macs are running 10.6.x as they were purchased within the last month. In fact on one Mac's Time Machine even ask if we wanted to continue with the same back up file (sparse image) even tho the MAC address is different.
    However, after a reboot from Bootcamp, one Mac's user files had completely vanished. The Time Capsule back up has data but it is not all there (or accessible). The time line in Time Machine goes back six months with is not possible since the Mac was only manufactured in October. It seems that Snow Leopard has continued to use the same backup file - only we cannot access the earlier backups.
    The sparse image is 425 gigabytes and yet when we try to migrate it reports that only 9.5 GB is migrate-able. Does anyone have a clue how to access the earlier data (short of mounting the sparse image and manually recovering the data?

    Tim Mitra wrote:
    So in conclusion, Snow Leopard does continue with an existing back up sparse image (in spite of the MAC address difference.)
    Yes, this is a new feature in Snow Leopard. See #B5 in the Time Machine - Troubleshooting *User Tip,* also at the top of the +Time Machine+ forum.
    Also you can pick any restore point by booting from the Installer disk. Using Migration Utility only will work with the last back up version.
    Correct. That's how they're both designed. See #14 in the Frequently Asked Questions *User Tip.*
    Still no explanation of why the user Documents directory got empty. However he did install Bootcamp which does repartition drive -so that could explain the loss.
    It certainly shouldn't do that!

  • Time Capsule message:Unable to complete backup. time Capsule already in use. If I try to ess Time Macine, it says: that the sparse image is temporarily unavailable.acc

    Normally, my Time Capsule backups  without issue. however, recently, it failed and I was unable to either complete a backup (done automatically) or enter Time Machine. I received a message that:" Unable to complete backup. Time Capsule already in use" when backup is attempted. When trying to access Time Machine when this occcurs, The message is" sparse image temporarily unavailable". Why does this happen? How can fix it without erasing the who;e image and starting all over?
    I have Mac OS Mountain Lion.

    You might need to if the bundle is damaged.
    You can verify the bundle.
    Read A5 here http://pondini.org/TM/Troubleshooting.html
    Also try C12 and C17
    Just a reboot of the TC might get it working again.

  • Creating Sparse Image: Authentication Error

    I created an encrypted sparse image in DU and then deleted it (by highlighting in DU and pressing "delete") because I thought I had made an error in sizing and location. Now, trying to create a new one, when I press "create" it begins a progress bar of creating the file (without asking for a new password creation) and then fails with:"cannot create sparse.dmg: authentication error".
    I eliminated the original password(for the first sparse.dmg)in my keychain, ran "repair disk permissions" for my HD, and also logged out and restarted, but still get the same error message.
    Any help appreciated!
    David

    WOW, fantastic work David!
    I hope I have not done something wrong here regarding placing these files on the desktop; furthermore, what do I do with them now?
    Looks like you did right, you can trash them if everything is fine now, new ones were made on use or reboot, I suspect the keychain one myself.
    My other question is that if I eject the new formed sparse drive and then remount it by double clicking the sparse image, it does not request the password.
    Did you choose to save the password in the Keychain? It'd automatically open it with the stored Keychain password.
    in trying to keep this "vintage" imac G5 (non intel) machine going is it worthwhile or recommended to purchase OS 10.5 Leopard or am I looking at further trouble?
    Leopard should be just fine, how much RAM do you have?
    Leopard requirements/10.5.x...
    * Mac computer with an Intel, PowerPC G5, or PowerPC G4 (867MHz or faster) processor
    minimum system requirements
    * 512MB of memory (I say 2GB at least)
    * DVD drive for installation
    * 9GB of available disk space (I say 30GB at least)
    You have to call Apple & likely ask for a Product Specialist to get it, if they still have it!

  • Read/write disk image vs. sparse

    When I create a new disk image in DU, I am given image format options of read/write disk image, sparse disk image, and sparse bundle disk image.
    I understand the difference between sparse and sparse bundle, but what's read/write?

    A read/write disk image is a traditional (i.e. non-sparse) disk image.
    With sparse images, you define the maximum size, but they only consume as much disk space as the content on the disk image - a 1GB sparse disk image with 50MB of data takes (about) 50MB of space on disk and can grow to 1GB.
    In comparison, a 1GB read/write disk image will consume (about) 1GB on disk, regardless of how much data is on the disk - 1KB, 1MB or 1GB on the image will all consume 1GB on disk.

  • Mounting Sparse Image disk at boot

    I had a look a threads treating this but still I am not satisfied.
    I want my iPhoto image disk to mount automatically when I boot the iMAC or at least when I am login. For that I have added the target sparse image disk in the list of applications to launch at login of my user (in the user&account)
    Once this is done and when I login again appears the disk utility but the disk does not mount automatically I have to do it myself (by pressing the mount button in the disk utility) which is not totally satisfactory to me.
    Any clue how to make this mount totally invisible and automatic without passing through the disk utility?
    thanks in advance,
    regards

    I am not sure to understand your remark. Are you controlling what is on the computers of comunity users before answering to the question?
    To answer you: I use BitTorrentSync software to load movies I ripped onto my iPadMini without using iTunes which does not accept the format I used to rip my DVD.
    Hope this answers.

  • Why can't I open multiple sparse image files at the same time in FCPX?

    I work in a multiple editor enviroment, where we have hundreds of different projects.  They are all divided into sparse image files to keep them all separated.  I used to be able to mount multiple sparse image files and see them all in FCPx.  But recently, FCPx upon opening, will close out all but one sparse image.  The images are still mounted to the OSx but FCPx will not recognize them.  I can only open one sparse image at a time.  I am needing to export multiple projects at the end of the day, and can't batch export or send them all to compressor because I can open up multiple projects.

    I work in a multiple editor enviroment, where we have hundreds of different projects.  They are all divided into sparse image files to keep them all separated.  I used to be able to mount multiple sparse image files and see them all in FCPx.  But recently, FCPx upon opening, will close out all but one sparse image.  The images are still mounted to the OSx but FCPx will not recognize them.  I can only open one sparse image at a time.  I am needing to export multiple projects at the end of the day, and can't batch export or send them all to compressor because I can open up multiple projects.

  • How do I move a user's sparse image BACK into the correct folder

    Please help if you can!
    I accidentally moved the sparse image connected to my administrator account into the 'shared' folder. (I was trying to confirm shared settings between users, and inadvertently moved the file.) There were no error messages or warnings, the file moved easily into the shared folder.
    After it was moved, I was unable to login to that user's desktop, and the only explanation is "...because there was an error." The only thing I can think of is that it's because of the moved sparse image for that user.
    But, I can't move it back. The computer won't allow me to move the file, and when I try to copy it to the appropriate folder I get an error message that there is not enough disk space. I tried creating a new administrator account, but that didn't work. I've tried changing the file-sharing settings, but nothing I've thought of doing has worked. I've tried turning off Fire Vault for that user, but I can't seem to do it from a different user account.
    If you have any ideas of how I could log into this user account, I would be very, very grateful. It's my main desktop, and I need access to the files located there!
    Please help!!

    Dear jsd2 and William,
    Thank you both so much for your help. I cannot tell you how much I appreciate both of you taking the time to help me figure out this problem.
    William - The Library folder was basically empty. It had some Quicktime preferences in it, but nothing else. The Terminal didn't even recognize it, and I actually couldn't delete through Terminal, but simply sent it to the trash. Even so, I couldn't log in the user account.
    jsd2 - I was able to log in as root and had no problems opening the sparseimage. I then copied all of the data to an external HD. Once that was finished I verified the sparseimage mounted disk, but there were no problems found. Even so, I repaired disk, but still no problems found. Even so, I couldn't log into the user account. I did get to the point where it asked for the master FireVault password (by entering the wrong password 3 or 4 times). It accepted the master password, but then it wouldn't let me change the password and login (the master password only led me to a new-password screen).
    So, after verifying that ALL of my data was safely on the external HD (including music, pictures, mailboxes, files, etc...), I deleted the user account and home folder for the account I was locked out of. Then, I created a new account, and manually transfered the necessary files back into the user folder. Then, I restarted my computer and breathed a huge sigh of relief when my wallpaper came up on the screen. About 98% of my settings are in tact. All music, pictures, files, and e-mails survived. Although I have to re-ad the actual e-mail accounts, all of the other account settings are there.
    I will leave the copied files on the external HD for at least a few days or a week to make sure nothing important is missing, then I will set up Time Machine and start making regular backups.
    So, thank again, both of you, for your invaluable help, which led to a successful, if somewhat roundabout, solution to this problem.
    Also, jsd2, I don't remember if I turned Fire Vault off when I upgraded or not. It seems to me that the directions said I should, and in which case I would have - but the upgrade wasn't recent, so I don't really remember. (Or rather - clearly I didn't, if what you say is true.) At the moment, FireVault is off for all accounts on this computer. I want to turn it back on, but, to be honest, I'm really scared to now....Since I don't know what caused the problem in the first place, I'm leery that if the problem hasn't been fixed I might end up in the same situation again. Although I hadn't had any problems before today, and I know that I must have done something in the 'sharing' settings that created the problem.

  • Disk Utility doesn't offer sparse images

    I want to make disk images of hard drives, but Disk Utility no longer offers the "sparse image" format. Why is this?
    iMac (27-inch Mid 2011), OS X Mountain Lion (10.8.2)

    Please read this whole message before doing anything.
    This procedure is a test, not a solution. Don’t be disappointed when you find that nothing has changed after you complete it.
    Step 1
    The purpose of this step is to determine whether the problem is localized to your user account.
    Enable guest logins* and log in as Guest. For instructions, launch the System Preferences application, select Help from the menu bar, and enter “Set up guest users” (without the quotes) in the search box. Don't use the Safari-only “Guest User” login created by “Find My Mac.”
    While logged in as Guest, you won’t have access to any of your personal files or settings. Applications will behave as if you were running them for the first time. Don’t be alarmed by this; it’s normal. If you need any passwords or other personal data in order to complete the test, memorize, print, or write them down before you begin.
    Test while logged in as Guest. Same problem?
    After testing, log out of the guest account and, in your own account, disable it if you wish. Any files you created in the guest account will be deleted automatically when you log out of it.
    *Note: If you’ve activated “Find My Mac” or FileVault, then you can’t enable the Guest account. The “Guest User” login created by “Find My Mac” is not the same. Create a new account in which to test, and delete it, including its home folder, after testing.
    Step 2
    The purpose of this step is to determine whether the problem is caused by third-party system modifications that load automatically at startup or login.
    Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards. Boot in safe mode* and log in to the account with the problem. The instructions provided by Apple are as follows:
    Shut down your computer, wait 30 seconds, and then hold down the shift key while pressing the power button.
    When you see the gray Apple logo, release the shift key.
    If you are prompted to log in, type your password, and then hold down the shift key again as you click Log in.
    Safe mode is much slower to boot and run than normal, and some things won’t work at all, including wireless networking on certain Macs.  The next normal boot may also be somewhat slow.
    The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
    *Note: If FileVault is enabled, or if a firmware password is set, or if the boot volume is a software RAID, you can’t boot in safe mode.
    Test while in safe mode. Same problem?
    After testing, reboot as usual (i.e., not in safe mode) and verify that you still have the problem. Post the results of steps 1 and 2.

  • List view for folders on a sparse image disk

    I have set up a sparse image on an external disk.  I cannot get the sparse image disk folders to default to "List View".  It always opens as "Icons" and I have to click on list view everytime.  Any ideas?

    Go to the Preferences under the small box at the upper-left:
    On the General pane, check the box to "Show list views for all media".
    Regards.

Maybe you are looking for