100% Control Mac OS

macOS Big Sur elevates the most advanced desktop operating system in the world to a new level of power and beauty. Experience Mac to the fullest with a refined new design. Enjoy the biggest Safari update ever. Discover new features for Maps and Messages. Get even more transparency around your privacy.

  1. 100% Control Mac Os Update
  2. 100% Control Mac Os Download
  3. 100% Control Mac Os X

Chances are, your Mac can run macOS Big Sur

The following models are supported:

  • Can't control Mac OS Big Sur I remotely support someone that uses a Mac and they upgraded to Big Sur. Ever since then, I am able to see the screen with AnyDesk but cannot control keyboard and mouse and we have already granted all the permissions necessary in MacOS.
  • Mac OS Admin, 100 Remote 6+ Months Phone + Skype JumpCloud Experience Is Required. Manage the maintain the Mac environment using JAMFJumpCloud o Create auto provisioned images based on end-user's job role or responsibilities o Create and deploy packages to setupmanage Mac OS and policies o patch management o test and evaluate any new MacOS.
  • MacOS Big Sur elevates the most advanced desktop operating system in the world to a new level of power and beauty. Experience Mac to the fullest with a refined new design. We recommend that you back up your Mac. If your Mac is running OS X Mavericks 10.9 or later, you can upgrade directly to macOS Big Sur. Voice Control, and Voice Memos.

Most modern macs are dual core. Meaning essentially two processors are on one chip. In Activity Monitor on OSX each core can be used up to 100% so at full capacity, Activity Monitor will report 200-800% depending on the horsepower of your Mac.

  • MacBook (2015 or later)
  • MacBook Air (2013 or later)
  • MacBook Pro (Late 2013 or later)
  • Mac mini (2014 or later)
  • iMac (2014 or later)
  • iMac Pro (2017 or later)
  • Mac Pro (2013 or later)

To see which model you have, click the Apple icon in your menu bar and choose About This Mac.

Make sure you’re ready to upgrade.

Before you upgrade, we recommend that you back up your Mac. If your Mac is running OS X Mavericks 10.9 or later, you can upgrade directly to macOS Big Sur. You’ll need the following:

  • OS X 10.9 or later
  • 4GB of memory
  • 35.5GB available storage on macOS Sierra or later*
  • Some features require an Apple ID; terms apply.
  • Some features require a compatible internet service provider; fees may apply.

Upgrading is free and easy

Upgrading from macOS Catalina 10.15 or Mojave 10.14?

100% Control Mac Os Update

Go to Software Update in System Preferences to find macOS Big Sur. Click Upgrade Now and follow the onscreen instructions.

Upgrading from an older version of macOS?

If you’re running any release from macOS 10.13 to 10.9, you can upgrade to macOS Big Sur from the App Store. If you’re running Mountain Lion 10.8, you will need to upgrade to El Capitan 10.11 first.

If you don’t have broadband access, you can upgrade your Mac at any Apple Store.

  • OS X 10.9 or later
  • 4GB of memory
  • 35.5GB available storage on macOS Sierra or later*
  • Some features require an Apple ID; terms apply.
  • Some features require a compatible internet service provider; fees may apply.

For details about your Mac model, click the Apple icon at the top left of your screen and choose About This Mac. These Mac models are compatible with macOS Big Sur:

  • MacBook (2015 or later)
  • MacBook Air (2013 or later)
  • MacBook Pro (Late 2013 or later)
  • Mac mini (2014 or later)
  • iMac (2014 or later)
  • iMac Pro (2017 or later)
  • Mac Pro (2013 or later)

Dictation, Voice Control, and Voice Memos

Requires a microphone (built-in or external).

Gestures

Requires a Multi-Touch trackpad, Force Touch trackpad, Magic Trackpad, or Magic Mouse.

Force Touch gestures require a Force Touch trackpad.

VoiceOver gestures require a Multi-Touch trackpad, Force Touch trackpad, or Magic Trackpad.

Photo Booth

Requires a FaceTime or iSight camera (built-in or external) or USB video class (UVC) camera.

FaceTime

Audio calls require a microphone (built-in or external) and broadband internet connection.

Video calls require a built-in FaceTime camera, an iSight camera (built-in or external), or a USB video class (UVC) camera; and broadband internet connection.

Apple TV

High dynamic range (HDR) video playback is supported by the following Mac models:

  • MacBook Pro (2018 or later)
  • iMac Pro (2017 or later)
  • Mac Pro (2019) with Pro Display XDR

Dolby Atmos soundtrack playback is supported by the following Mac models:

  • MacBook Air (2018 or later)
  • MacBook Pro (2018 or later)

Sidecar

Supported by the following Mac models:

  • MacBook (2016 or later)
  • MacBook Air (2018 or later)
  • MacBook Pro (2016 or later)
  • Mac mini (2018 or later)
  • iMac (late 2015 or later)
  • iMac Pro (2017 or later)
  • Mac Pro (2019)

Supported by all iPad models with Apple Pencil support:

  • 12.9-inch iPad Pro
  • 11-inch iPad Pro
  • 10.5-inch iPad Pro
  • 9.7-inch iPad Pro
  • iPad (6th generation or later)
  • iPad mini (5th generation)
  • iPad Air (3rd and 4th generation)

Continuity Camera

Requires an iPhone or iPad that supports iOS 12 or later.

100% Control Mac Os Download

Continuity Sketch and Continuity Markup

Requires an iPhone with iOS 13 or later or an iPad with iPadOS 13 or later.

Handoff

Requires an iPhone or iPad with a Lightning connector or with USB-C and iOS 8 or later.

Instant Hotspot

Requires an iPhone or iPad with cellular connectivity, a Lightning connector or USB-C, and iOS 8.1 or later. Requires Personal Hotspot service through your carrier.

Universal Clipboard

Requires an iPhone or iPad with a Lightning connector or with USB-C and iOS 10 or later.

Auto Unlock

Requires an Apple Watch with watchOS 3 or later or an iPhone 5 or later.

Approve with Apple Watch

Requires an Apple Watch with watchOS 6 or later or an iPhone 6s or later with iOS 13 or later.

Phone Calling

Requires an iPhone with iOS 8 or later and an activated carrier plan.

SMS

Requires an iPhone with iOS 8.1 or later and an activated carrier plan.

Home

Requires an iPhone with iOS 12 or later and a configured Home app.

AirDrop

AirDrop to iOS and iPadOS devices requires an iPhone or iPad with a Lightning connector or with USB-C and iOS 7 or later.

AirPlay

Mac

AirPlay Mirroring requires an Apple TV (2nd generation or later).

AirPlay for web video requires an Apple TV (2nd generation or later).

Peer-to-peer AirPlay requires a Mac (2012 or later) and an Apple TV (3rd generation rev A, model A1469 or later) with Apple TV software 7.0 or later.

Time Machine

Requires an external storage device (sold separately).

Boot Camp

Allows Boot Camp installations of Windows 10 on supported Mac models.

Exchange Support

Requires Microsoft Office 365, Exchange 2016, Exchange 2013, or Exchange Server 2010. Installing the latest Service Packs is recommended.

Windows Migration

Supports OS X 10.7 or later and Windows 7 or later.

100% Control Mac Os X

App Store

Available only to persons age 13 or older in the U.S. and many other countries and regions.

Photos

The improved Retouch tool is supported on the following Mac models:

  • MacBook Pro (15-inch and 16-inch models) introduced in 2016 or later
  • iMac (Retina 5K models) introduced in 2014 or later
  • iMac (Retina 4K models) introduced in 2017 or later
  • iMac Pro (2017 or later)
  • Mac Pro introduced in 2013 or later
  • Apple Books
  • Apple News
  • App Store
  • Automator
  • Calculator
  • Calendar
  • Chess
  • Contacts
  • Dictionary
  • DVD Player
  • FaceTime
  • Find My
  • Font Book
  • Home
  • Image Capture
  • Launchpad
  • Mail
  • Maps
  • Messages
  • Mission Control
  • Music
  • Notes
  • Photo Booth
  • Photos
  • Podcasts
  • Preview
  • QuickTime Player
  • Reminders
  • Safari
  • Siri
  • Stickies
  • Stocks
  • System Preferences
  • TextEdit
  • Time Machine
  • TV
  • Voice Memos
  • Activity Monitor
  • AirPort Utility
  • Audio MIDI Setup
  • Bluetooth File Exchange
  • Boot Camp Assistant
  • ColorSync Utility
  • Console
  • Digital Color Meter
  • Disk Utility
  • Grapher
  • Keychain Access
  • Migration Assistant
  • Screenshot
  • Screen Time
  • Script Editor
  • Sidecar
  • System Information
  • Terminal
  • VoiceOver Utility
100% control mac os x
  • Arabic
  • Catalan
  • Croatian
  • Simplified Chinese
  • Traditional Chinese
  • Traditional Chinese (Hong Kong)
  • Czech
  • Danish
  • Dutch
  • English (Australia)
  • English (UK)
  • English (U.S.)
  • Finnish
  • French
  • French (Canada)
  • German
  • Greek
  • Hebrew
  • Hindi
  • Hungarian
  • Indonesian
  • Italian
  • Japanese
  • Korean
  • Malay
  • Norwegian
  • Polish
  • Brazilian Portuguese
  • Portuguese
  • Romanian
  • Russian
  • Slovak
  • Spanish
  • Spanish (Latin America)
  • Swedish
  • Thai
  • Turkish
  • Ukrainian
  • Vietnamese
First off, Hi! You guys were recommended as a place where I can get helped out of this crazy predicament I'm in.
My System: Rev A G5 20' iMac 1.8GHz, 2GB RAM from OWC (Apple's 256K stick in now though). OSX 3.9. No Bluetooth, sharing, FAX, printer connected or enabled.
My problem: CPU began racing a constant 99-100% after installing a 3rd party iTunes visualizer. Uninstalling it and iTunes made no difference. Have run Disk Warrior, TechTool Deluxe, repaired permissions, zapped the PRAM, run Applejack, all without luck. Activity Monitor shows 100% CPUsage in lower left with no launched apps but the vertical column doesn't come close to that, only about 15% CPUsage.
Fans racing; CPU temperature a steady 165-170ºF. Lots of beachballs.
Apple's Hardware Test gave this result:
Quick test Error Code: 2MLB/10/4: $0005. 22f2
Exended test Error Code: 2MEM/1/4: DIMM0/J4000
Bad memory stick(s)? Had two 1G OWC sticks inside at the time.
Have tested each 1GB stick separately in both of the iMac slots as well as the original 256K from Apple. The problem persists in all cases.
Created a test account. Tried different energy settings. No change.
Here is a piece of System log:
Display starts at offset 15438297 within file of length 15569369.
Use File->Reload (Cmd-R) to display more.
cupsd -f': exited as a result of signal 10 [pid 27511]
Jan 1 09:46:14 localhost crashdump: Unable to determine CPSProcessSerNum pid: 27511 name: cupsd
Jan 1 09:46:14 localhost crashdump: Started writing crash report to: /Library/Logs/CrashReporter/cupsd.crash.log
Jan 1 09:46:14 localhost crashdump: Finished writing crash report to: /Library/Logs/CrashReporter/cupsd.crash.log
Jan 1 09:46:15 localhost mach_init[2]: Server 7253 in bootstrap d03 uid 0: '/usr/sbin/cupsd -f': exited as a result of signal 10 [pid 27526]
Jan 1 09:46:15 localhost crashdump: Unable to determine CPSProcessSerNum pid: 27526 name: cupsd
Jan 1 09:46:15 localhost crashdump: Started writing crash report to: /Library/Logs/CrashReporter/cupsd.crash.log
Jan 1 09:46:15 localhost crashdump: Finished writing crash report to: /Library/Logs/CrashReporter/cupsd.crash.log
Jan 1 09:46:16 localhost mach_init[2]: Server b2d7 in bootstrap d03 uid 0: '/usr/sbin/cupsd -f': exited as a result of signal 10 [pid 27541]
Jan 1 09:46:16 localhost crashdump: Unable to determine CPSProcessSerNum pid: 27541 name: cupsd
Jan 1 09:46:16 localhost crashdump: Started writing crash report to: /Library/Logs/CrashReporter/cupsd.crash.log
Jan 1 09:46:16 localhost crashdump: Finished writing crash report to: /Library/Logs/CrashReporter/cupsd.crash.log
Jan 1 09:46:17 localhost mach_init[2]: Server ac1b in bootstrap d03 uid 0: '/usr/sbin/cupsd -f': exited as a result of signal 10 [pid 27556]
Jan 1 09:46:17 localhost crashdump: Unable to determine CPSProcessSerNum pid: 27556 name: cupsd
Jan 1 09:46:17 localhost crashdump: Started writing crash report to: /Library/Logs/CrashReporter/cupsd.crash.log
Jan 1 09:46:17 localhost crashdump: Finished writing crash report to: /Library/Logs/CrashReporter/cupsd.crash.log
Jan 1 09:46:18 localhost mach_init[2]: Server 0 in bootstrap d03 uid 0: '/usr/sbin/cupsd -f': exited as a result of signal 10 [pid 27571]
Jan 1 09:46:19 localhost crashdump: Unable to determine CPSProcessSerNum pid: 27571 name: cupsd
Jan 1 09:46:19 localhost crashdump: Started writing crash report to: /Library/Logs/CrashReporter/cupsd.crash.log
Jan 1 09:46:19 localhost crashdump: Finished writing crash report to: /Library/Logs/CrashReporter/cupsd.crash.log
Jan 1 09:46:19 localhost mach_init[2]: Server 72e7 in bootstrap d03 uid 0: '/usr/sbin/cupsd -f': exited as a result of signal 10 [pid 27586]
Jan 1 09:46:19 localhost crashdump: Unable to determine CPSProcessSerNum pid: 27586 name: cupsd
Jan 1 09:46:19 localhost crashdump: Started writing crash report to: /Library/Logs/CrashReporter/cupsd.crash.log
Jan 1 09:46:19 localhost crashdump: Finished writing crash report to: /Library/Logs/CrashReporter/cupsd.crash.log
Jan 1 09:46:20 localhost mach_init[2]: Server acab in bootstrap d03 uid 0: '/usr/sbin/cupsd -f': exited as a result of signal 10 [pid 27601]
Jan 1 09:46:20 localhost crashdump: Unable to determine CPSProcessSerNum pid: 27601 name: cupsd
Jan 1 09:46:20 localhost crashdump: Started writing crash report to: /Library/Logs/CrashReporter/cupsd.crash.log
Jan 1 09:46:20 localhost crashdump: Finished writing crash report to: /Library/Logs/CrashReporter/cupsd.crash.log
Jan 1 09:46:21 localhost mach_init[2]: Server b21b in bootstrap d03 uid 0: '/usr/sbin/cupsd -f': exited as a result of signal 10 [pid 27616]
Jan 1 09:46:21 localhost crashdump: Unable to determine CPSProcessSerNum pid: 27616 name: cupsd
Jan 1 09:46:21 localhost crashdump: Started writing crash report to: /Library/Logs/CrashReporter/cupsd.crash.log
Here is the initial repair permissions result. Notice the iTunes comment on top (iTunes has been trashed since):
Repairing permissions on disk /
: object: ./Applications/iTunes.app/Contents/MacOS/iTunes malformed object (inconsistant sizeofcmds field in mach header)
Started verify/repair permissions on disk disk0s3 Macintosh HD
Determining correct file permissions.
We are using special permissions for the file or directory ./Library/ColorSync/Profiles/Displays. New permissions are 16893
We are using special permissions for the file or directory ./Library/ColorSync/Profiles. New permissions are 16893
We are using special permissions for the file or directory ./System/Library/Filesystems/cd9660.fs/cd9660.util. New permissions are 33261
We are using a special uid for the file or directory ./private/var/at/jobs. New uid is 1
We are using a special uid for the file or directory ./private/var/at/spool. New uid is 1
Permissions differ on ./private/var/log/wtmp, should be -rw-r--r-- , they are -rw-r-----
Owner and group corrected on ./private/var/log/wtmp
Permissions corrected on ./private/var/log/wtmp
The privileges have been verified or repaired on the selected volume
Verify/repair finished permissions on disk disk0s3 Macintosh HD
Lastly here is what terminal looks like. I'm a Unix dummy and screwed something up:
Last login: Tue Jan 3 12:46:50 on ttyp1
Welcome to Darwin!
Bob-Matthews-Computer:~ bobmatthews$ Last login: Tue Jan 3 12:46:09 on ttyp1
Welcome to Darwin!
Bob-Matthews-Computer:~ bobmatthews$ sudo vi /etc/hostconfig
Password:
E325: ATTENTION
Found a swap file by the name '/etc/.hostconfig.swp'
owned by: root dated: Mon Jan 2 09:31:23 2006
file name: /private/etc/hostconfig
modified: YES
bobmatth ttyp1 Tue Jan 3 12:49 still logged in
bobmatth ttyp1 Tue Jan 3 12:49 - 12:49 (00:00)
bobmatth ttyp1 Tue Jan 3 12:46 - 12:49 (00:02)
bobmatth ttyp1 Tue Jan 3 12:46 - 12:46 (00:00)
bobmatth ttyp1 Tue Jan 3 12:46 - 12:46 (00:00)
bobmatth ttyp1 Tue Jan 3 12:46 - 12:46 (00:00)
bobmatth ttyp1 Mon Jan 2 14:22 - shutdown (00:39)
bobmatth ttyp1 Mon Jan 2 14:22 - 14:22 (00:00)
bobmatth ttyp1 Mon Jan 2 14:20 - 14:22 (00:01)
bobmatth ttyp1 Mon Jan 2 14:20 - 14:20 (00:00)
bobmatth ttyp1 Mon Jan 2 14:19 - 14:20 (00:01)
bobmatth ttyp1 Mon Jan 2 14:19 - 14:19 (00:00)
bobmatth ttyp1 Mon Jan 2 11:18 - shutdown (00:08)
bobmatth ttyp1 Mon Jan 2 11:18 - 11:18 (00:00)
bobmatth ttyp1 Mon Jan 2 09:49 - 11:18 (01:28)
bobmatth ttyp1 user name: root host name: Bob-Matthews-C Mon Jan 2 09:49 - 09:49 (00:00)
bobmatth ttyp1 Mon Jan 2 09:47 - 09:49 (00:02)
bobmatth ttyp1 Mon Jan 2 09:47 - 09:47 (00:00)
bobmatth ttyp1 Mon Jan 2 09:39 - shutdown (00:04)
bobmatth ttyp1 Mon Jan 2 09:39 - 09:39 (00:00)
omputer.local
process ID: 11427
While openbobmatth ttyp1 Mon Jan 2 09:38 - 09:39 (00:01)
bobmatth ttyp1 Mon Jan 2 09:38 - 09:38 (00:00)
bobmatth ttyp1 Mon Jan 2 09:37 - 09:38 (00:00)
bobmatth ttyp1 Mon Jan 2 09:37 - 09:37 (00:00)
bobmatth ttyp1 Mon Jan 2 09:31 - shutdown (00:01)
bobmatth ttyp1 Mon Jan 2 09:31 - 09:31 (00:00)
bobmatth ttyp1 Mon Jan 2 09:28 - 09:31 (00:02)
bobmatth ttyp1 Mon Jan 2 09:28 - 09:28 (00:00)
ing file '/etc/hostconfig'
dated: Sunbobmatth ttyp1 Mon Jan 2 09:28 - 09:28 (00:00)
bobmatth ttyp1 Mon Jan 2 09:28 - 09:28 (00:00)
bobmatth ttyp1 Sun Jan 1 22:13 - shutdown (05:50)
bobmatth ttyp1 Sun Jan 1 22:13 - 22:13 (00:00)
bobmatth ttyp1 Sun Jan 1 22:10 - 22:13 (00:02)
bobmatth ttyp1 Sun Jan 1 22:10 - 22:10 (00:00)
bobmatth ttyp1 Sun Jan 1 22:10 - 22:10 (00:00)
bobmatth ttyp1 Sun Jan 1 22:10 - 22:10 (00:00)
bobmatth ttyp1 Sun Jan 1 22:09 - 22:10 (00:00)
Feb 13 19:46:58 2005
(1) Another program may be bobmatth ttyp1 Sun Jan 1 22:09 - 22:09 (00:00)
bobmatth ttyp1 Sun Jan 1 22:09 - 22:09 (00:00)
bobmatth ttyp1 Sun Jan 1 22:09 - 22:09 (00:00)
bobmatth ttyp1 Sun Jan 1 22:08 - 22:09 (00:00)
bobmatth ttyp1 Sun Jan 1 22:08 - 22:08 (00:00)
bobmatth ttyp1 Sun Jan 1 22:07 - 22:08 (00:01)
bobmatth ttyp1 Sun Jan 1 22:07 - 22:07 (00:00)
bobmatth ttyp1 Sun Jan 1 22:06 - 22:07 (00:00)
editing the same file.
If this is the case, bebobmatth ttyp1 Sun Jan 1 22:06 - 22:06 (00:00)
bobmatth ttyp1 Sun Jan 1 21:53 - 22:06 (00:13)
bobmatth ttyp1 Sun Jan 1 21:53 - 21:53 (00:00)
bobmatth ttyp1 Sun Jan 1 21:49 - 21:53 (00:03)
careful not to end up with two
different instbobmatth ttyp1 Sun Jan 1 21:49 - 21:49 (00:00)
bobmatth ttyp1 Sun Jan 1 21:45 - 21:49 (00:03)
bobmatth ttyp1 Sun Jan 1 21:45 - 21:45 (00:00)
bobmatth ttyp1 Sun Jan 1 21:45 - 21:45 (00:00)
bobmatth ttyp1 Sun Jan 1 21:45 - 21:45 (00:00)
bobmatth ttyp1 Sun Jan 1 21:40 - 21:45 (00:04)
bobmatth ttyp1 Sun Jan 1 21:40 - 21:40 (00:00)
bobmatth ttyp1 Sun Jan 1 21:39 - 21:40 (00:01)
bobmatth ttyp1 Sun Jan 1 21:39 - 21:39 (00:00)
ances of the same file when making changes.
Qubobmatth ttyp1 Sat Dec 31 18:14 - shutdown (00:21)
bobmatth ttyp1 Sat Dec 31 18:14 - 18:14 (00:00)
bobmatth ttyp1 Sat Dec 31 18:11 - 18:14 (00:02)
bobmatth ttyp1 Sat Dec 31 18:11 - 18:11 (00:00)
wtmp begins Thu Dec 29 15:48
it, or continue with caution.
(2) An edit session for this file crashed.
If this is the case, uBob-Matthews-Computer:~ bobmatthews$ Welcome to Darwin!
Bob-Matthews-Computer:~ bobmatthews$ sudo vi /etc/hostconfig
Password:
E325: ATTENTION
Found a swap file by the name '/etc/.hostconfig.swp'
owned by: root dated: Mon Jan 2 09:31:23 2006
file name: /private/etc/hostconfig
modified: YES
user name: root host name: Bob-Matthews-Computer.local
process ID: 11427
While opening file '/etc/hostconfig'
dated: Sun Feb 13 19:46:58 2005
(1) Another program may be editing the same file.
If this is the case, be careful not to end up with two
different instances of the same file when making changes.
Quit, or continue with caution.
(2) An edit session for this file crashed.
If this is the case, use ':recover' or 'vim -r /etc/hostconfig'
to recover the changes (see ':help recovery').
If -bash: Welcome: command not found
Bob-Matthews-Computer:~ bobmatthews$ Bob-Matthews-Computer:~ bobmatthews$ sudo vi /etc/hostconfig
-bash: Bob-Matthews-Computer:~: command not found
Bob-Matthews-Computer:~ bobmatthews$ Password:
-bash: Password:: command not found
Bob-Matthews-Computer:~ bobmatthews$
Bob-Matthews-Computer:~ bobmatthews$
Bob-Matthews-Computer:~ bobmatthews$
Bob-Matthews-Computer:~ bobmatthews$
Bob-Matthews-Computer:~ bobmatthews$
Bob-Matthews-Computer:~ bobmatthews$
Bob-Matthews-Computer:~ bobmatthews$
Bob-Matthews-Computer:~ bobmatthews$
Bob-Matthews-Computer:~ bobmatthews$
Bob-Matthews-Computer:~ bobmatthews$
Bob-Matthews-Computer:~ bobmatthews$
Bob-Matthews-Computer:~ bobmatthews$
Bob-Matthews-Computer:~ bobmatthews$
Bob-Matthews-Computer:~ bobmatthews$
Bob-Matthews-Computer:~ bobmatthews$
Bob-Matthews-Computer:~ bobmatthews$
Bob-Matthews-Computer:~ bobmatthews$
Bob-Matthews-Computer:~ bobmatthews$
Bob-Matthews-Computer:~ bobmatthews$
Bob-Matthews-Computer:~ bobmatthews$
Bob-Matthews-Computer:~ bobmatthews$
Bob-Matthews-Computer:~ bobmatthews$ E325: ATTENTION
-bash: E325:: command not found
Bob-Matthews-Computer:~ bobmatthews$ Found a swap file by the name '/etc/.hostconfig.swp'
-bash: Found: command not found
Bob-Matthews-Computer:~ bobmatthews$ owned by: root dated: Mon Jan 2 09:31:23 2006
-bash: owned: command not found
Bob-Matthews-Computer:~ bobmatthews$ file name: /private/etc/hostconfigname:: Can't stat `name:' (No such file or directory)
/private/etc/hostconfig: ASCII English text
Bob-Matthews-Computer:~ bobmatthews$ modified: YES
-bash: modified:: command not found
Bob-Matthews-Computer:~ bobmatthews$ user name: root host name: Bob-Matthews-Computer.local
-bash: user: command not found
Bob-Matthews-Computer:~ bobmatthews$ process ID: 11427
-bash: process: command not found
Bob-Matthews-Computer:~ bobmatthews$ While opening file '/etc/hostconfig'
-bash: While: command not found
Bob-Matthews-Computer:~ bobmatthews$ dated: Sun Feb 13 19:46:58 2005
-bash: dated:: command not found
Bob-Matthews-Computer:~ bobmatthews$
Bob-Matthews-Computer:~ bobmatthews$ (1) Another program may be editing the same file.
-bash: syntax error near unexpected token `Another'
Bob-Matthews-Computer:~ bobmatthews$ If this is the case, be careful not to end up with two
-bash: If: command not found
Bob-Matthews-Computer:~ bobmatthews$ different instances of the same file when making changes.
-bash: different: command not found
Bob-Matthews-Computer:~ bobmatthews$ Quit, or continue with caution.
-bash: Quit,: command not found
Bob-Matthews-Computer:~ bobmatthews$
Bob-Matthews-Computer:~ bobmatthews$ (2) An edit session for this file crashed.
-bash: syntax error near unexpected token `An'
Bob-Matthews-Computer:~ bobmatthews$ If this is the case, use ':recover' or 'vim -r /etc/hostconfig'
-bash: If: command not found
Bob-Matthews-Computer:~ bobmatthews$ to recover the changes (see ':help recovery').
-bash: syntax error near unexpected token `('
Bob-Matthews-Computer:~ bobmatthews$ If you did this already, delete the swap file '/etc/.hostconfig.swp'
-bash: If: command not found
Bob-Matthews-Computer:~ bobmatthews$ to avoid this message.
-bash: to: command not found
Bob-Matthews-Computer:~ bobmatthews$
Bob-Matthews-Computer:~ bobmatthews$ Swap file '/etc/.hostconfig.swp' already exists!
-bash: Swap: command not found
Bob-Matthews-Computer:~ bobmatthews$ [O]pen Read-Only, (E)dit anyway, (R)ecover, (Q)uit, (D)elete it:
Please help me recover my beloved Mac!