#Textwrangler for mac 10.6.8 how to
#Textwrangler for mac 10.6.8 install
#Textwrangler for mac 10.6.8 full
#Textwrangler for mac 10.6.8 verification

Use Disk Utility to make a read/write DMG of a 10.6.7 install disk for a MacBook Pro or iMac.We are are going to unlock a 10.6.7 DVD and make it a universal Installer. Version 10.6.7 was the last version released on DVD, but the DVDs were locked to specific machines.

Early 2011 MacBook Pros fall in this category. If you have an Apple computer made after the Core 2 Duos, the 10.6.3 retail disk may not boot, and the 10.6.0 version won't boot at all.

#Textwrangler for mac 10.6.8 full

After that, close everything, eject the Time Machine Image disk and start a new backeup.Why do we need this? Because Apple quit releasing full retail versions of Snow Leopard with 10.6.3.

#Textwrangler for mac 10.6.8 verification

→ Change the value of the key Verification State from 2 to 1 → I use TextWrangler, but you can use another text editor (Maybe it’s also working with the 'cmd + i' command ? Never tried it). → You can drag your Time Machine backeup image in the Terminal for the path → Type “chflags nouchg /Volumes/pathToSparseboundleimagefile/token” to remove the locker (Hope it’s the right translation because I have a french version od OS X) Select again your Time Machine backup icon, right clic and then select “Show Package Contents”.→ Select it, then “cmd + i” and uncheck the locked check box The Icon of your Time machine backup may have a locker.→ At this state, you will have a drive on your desktop, called Time Machine → In the Finder, Go To : AFP://ip_adress_of_the_MBL Here is the procedure to recover your backup after the message ' Issues with Time Machine - new backup must be created ' : Hope it helps someone and I’ll see in the following days if it keeps working like a charm I recomend you to use a wired connection.Ģ - From the popup window select TimeMachineĤ - Wait some minutes so it loads the information, then you can navigate within your backups In finder press Cmd+K and enter “afp://NAS//” where NAS is the ip or name of my book live. I’ve also forced some backup verifications, and everything is ok, at least until now…ġ - Connect manually to TimeMachine backups. Since that, I’ve been running Time Machine for over a week without a problem!!! If I have to reinstall all over again, I won’t mind to wait 1 or 2 hours for it to sinchronize again. That sparrow db, is the same as every info that I have in Gmail. I’ve added that folder (and some others) to the exclude list, now each hourly backup is 30mb or so.įolders that are used as cache for applications are good candidates for the exclude list, I’ve added some. I’ve noticed that the sparrow mail app which I use for Gmail has a huge 2gb database file, and since time machine is a bit stupid and backups the entire file every time a modification is done, then each hourly backup was over 2gb.

#Textwrangler for mac 10.6.8 how to

With this program you can view exactly which files Time Machine is backing up (see how to use at the bottom). I started wondering what files were in each backup and found the following app: TimeTracker ( around the middle of the page, a bit hidden). I’ve noticed that each hourly time machine backup was over 2gb, way too much! I’ve had the same issues… Every two or three days I had to start over with backups. So - some type of incompatibility exists with the MBL and Time Machine at least in OS X Snow Leopard 10.6.8 and later. At this point I assumed the backup was corrupt and returned to backing up where I left off on the Time Capsule and all was fine. After 10 minutes into the validation process - the validation slowed to a crawl - then basically stalled - and finally failed in the validation step with some type of cryptical numeric error.

There was a week or more delay before a subsequent backup was done - and the Time Machine decided to perform a validation of the existing backup. However when the size of the backup exceeded several gig - the MBL started struggling and appeared to just stall. I only did weekly backups and they were quick. I switched the backup over to the MBL - by copying the existing sparse bundle from the Time Capsule to the share on the MBL. However I had been backing up the neighbors MacBook Pro (on Snow Leopard 10.6.8) on my Time Capsule. To KC5MZR - I don’t have this specific issue - meaning that I don’t get the new backup must be created message - I am on Lion 10.7.2.