Some Sage Advice

We just got this from Quark.

We’re delighted to let you know about the availability of the free QuarkXPress 9.2.1 update for Mac OS X users. This is an essential update if you are using QuarkXPress 9 with Mac OS X Lion.

You can download the update immediately from the Quark Web site or with Quark Update (In your System Preferences).

Please note that this update is for Mac OS X users only. There is no equivalent Windows update. This update has been released specifically to address the disappearing icon issue that was introduced with the 10.7.3 update of Mac OS X Lion. QuarkXPress 9 is the only version of QuarkXPress that has been certified to run on Mac OS X Lion.

This is what worked for me, step by step, to remove the MacDefender using Sophos Anti-Virus for Mac Home (which is free):

The 3 threats found after my first full scan on my Macbook were
Users/myname/library/cache/java……
which needed to be cleaned up manually.

1. In the Quarantine Manager, click on the blue link file name of the threat to get it’s details.
2. You need to note the path & file name.
3. In my example I will use users/myname/library/cache/java……
4. You will need to make a custom scan.
5. In the window that’s titled Scan Local Drives, click on the arrow next to Custom Scans
6. Click on the + sign.  You will see a message untitled – No items in scan, this scan has never been run.
7. Double click on it and another window will open asking for a Scan Name (can fill in later).  At the bottom of this window, click the + sign – this will open a finder window called Open.
8. Double click on the file called Users (another window opens)
9. Double click on the home file with your name on it (another window opens)
10. Double click on the Library folder (another window opens)
11. Single click on the Caches folder and then click on the Open button bottom right
12. You should now see the folder Caches with a tick next to it in the window described in step 3.
13. Type in whatever name you want to call the custom scan.  I called mine Caches.
14. Under the title you’ve just typed are 3 buttons. Click on the Options button.
15. Click on the drop down menu where it says log only and choose Delete threat.  So it now says When a threat is found: Delete threat.
16. Click on the Done button.
17. In the customs scan window from step 1. you should see a new custom scan called Caches (or whatever you named it).  Click on the Play button next to the pencil button.
18. A drop down dialogue box asks you to Scan with privileges, Cancel or Scan All.
19. Click on the Scan All button & type in your administrator password & click OK.
20. The scan is performed.  If you Open Quarantine Manager, the threats should be gone.

System requirements for Adobe Creative Suite 5.5

Windows

• * Intel® Pentium® 4 or AMD Athlon® 64 processor (Intel Core™ i3, i5, or i7 or or AMD Phenom® II recommended); Intel Core 2 Duo or AMD Phenom II required for Adobe® Premiere® Pro; processor with 64-bit support required for Adobe Premiere Pro and After Effects®
  * Microsoft® Windows® XP with Service Pack 3; Windows Vista® Home Premium, Business, Ultimate, or Enterprise with Service Pack 2; or Windows 7; 64-bit edition of Windows Vista or Windows 7 required for Adobe Premiere Pro, After Effects, and the Subscription Edition of Master Collection
  * 2GB of RAM (4GB or more recommended)
  * 24.3GB of available hard-disk space for installation; additional free space required during installation (cannot install on removable flash storage devices)
  * 1280×900 display (1280×1024 recommended) with qualified hardware-accelerated OpenGL graphics card, 16-bit color, and 256MB of VRAM
  * Adobe-certified GPU card for GPU-accelerated performance in Adobe Premiere Pro; visit www.adobe.com/go/premiere_systemreqs for the latest list of supported cards
  * Some GPU-accelerated features in Adobe Photoshop® require graphics support for Shader Model 3.0 and OpenGL 2.0
  * Some features in Adobe Bridge rely on a DirectX 9–capable graphics card with at least 64MB of VRAM
  * 7200 RPM hard drive for editing compressed video formats; RAID 0 for uncompressed
  * Adobe-certified card for capture and export to tape for SD/HD workflows
  * OHCI-compatible IEEE 1394 port for DV and HDV capture, export to tape, and transmit to DV device
  * Sound card compatible with ASIO protocol or Microsoft Windows Driver Model
  * DVD-ROM drive compatible with dual-layer DVDs (DVD+-R burner for burning DVDs; Blu-ray burner for creating Blu-ray Disc media)
  * Java™ Runtime Environment 1.6 (included)
  * Eclipse™ 3.6.1 required for plug-in installation
  * QuickTime 9 software required for QuickTime and multimedia features
  * Adobe Flash® Player 10 software required to export SWF files and to play back DVD projects exported as SWF files
  * Broadband Internet connection required for online services and to validate Subscription Edition (if applicable) on an ongoing basis

Mac OS

* Multicore Intel® processor with 64-bit support
* Mac OS X v10.5.8 or v10.6; Mac OS X v10.6 required for Adobe Flash Builder™ 4.5 Premium Edition and Flash Builder integration with Flash Catalyst® and Flash Professional; Mac OS X v10.6.3 required for GPU-accelerated performance in Adobe Premiere Pro
* 2GB of RAM (4GB or more recommended)
* 26.3GB of available hard-disk space for installation; additional free space required during installation (cannot install on a volume that uses a case-sensitive file system or on removable flash storage devices)
* 1280×900 display (1280×1024 recommended) with qualified hardware-accelerated OpenGL graphics card, 16-bit color, and 256MB of VRAM
* Adobe-certified GPU card for GPU-accelerated performance in Adobe Premiere Pro
* Some GPU-accelerated features in Adobe Photoshop require graphics support for Shader Model 3.0 and OpenGL 2.0
* 7200 RPM hard drive for editing compressed video formats; RAID 0 for uncompressed
* Core Audio–compatible sound card
* DVD-ROM drive compatible with dual-layer DVDs (SuperDrive for burning DVDs; external Blu-ray burner for creating Blu-ray Disc media)
* Java Runtime Environment 1.6
* Eclipse 3.6.1 Cocoa version required for plug-in installation
* QuickTime 9 software required for QuickTime and multimedia features
* Adobe Flash Player 10 software required to export SWF files and to play back DVD projects exported as SWF files
* Broadband Internet connection required for online services and to validate Subscription Edition (if applicable) on an ongoing basis

*Visit the NVIDIA website for system requirements and compatibility. The list of graphics cards that are compatible with Adobe Premiere Pro CS5 is updated on a regular basis.

*Adobe online services, including Adobe CS Live Services, are available only to users 13 and older and require agreement to additional terms and Adobe’s online privacy policy. Online services are not available in all countries or languages, may require user registration and may be subject to change or discontinuation without notice. Additional fees or subscription charges may apply.

I have a Mac OS X 10.6 Snow Leopard server that I manage. We have it connected via iSCSI to a SNAPServer SAN disk array (RAID-6). The beauty of RAID 6 and the GUID format of the drives is that we can resize a volume on the fly…sort of. On the Mac, you can resize partitions but because of the way partitions are handled, you may get an error from Disk Utility. The below procedure works without destroying data. That being said, please read the IMPORTANT NOTE below:

IMPORTANT NOTE: The following procedures are ONLY for people with RAID cards who have upsized their raid array. If you have a MacBook or MacBook Pro, this is not for you! If you want to move from a smaller single drive to a larger single drive, try CarbonCopyCloner or SuperDuper .Once my raid array had finished upsizing from 5.5GB to 9.1GB, I had to resize the partition in order to actually use the space. OS X’s Disk Utility gives the cryptic error

(Partition failed with the error: MediaKit reports partition (map) too small. )  Not particularly helpful, is it. All my googling has never found an answer, so I thought I’d post my solution here. Before you start, BACKUP YOUR DATA. While I have not lost data using this procedure, if you make a typo, the results could be catastrophic!

1. Open up a terminal
2. type df and press enter
3. Note the mount point for the drive you’re trying to expand. Mine was “/dev/disk4s1″. We’re only interested in the disk, not the slice, so I’m going to use “/dev/disk4″.
4. In Disk Utility, unmount the current partition on the disk.
5. run “sudo gpt show /dev/disk4″. If this fails, you probably didn’t unmount the partition first.
6. The line with the largest size is the partition we care about. Write down the start and size numbers. Check them again to be sure you wrote them down correctly!
7. In Disk Utility, unmount the partition again.
8. run “sudo gpt destroy /dev/disk4″
9. run “sudo gpt create -f /dev/disk4″
10. run “sudo gpt add -b 409640 -s 11719262168 /dev/disk4″. Notice those numbers came from the start and length of the partition we want to save.
11. Reboot. (On a Snow Leopard server I did not need to reboot!)
12. Now use Disk Utility to resize the partition. If you didn’t reboot, Disk Utility will probably give an error, but it might still work. Reboot now anyways.

Basically what’s going on here is that the GPT table is built only big enough for the drive it’s on. That’s a logical assumption – hard drives don’t magically get larger – unless they’re RAID arrays. We’re just removing the GPT partition information, and replacing it. Should things go crazy, as long as you’ve got the start and size information for the partition you care about, you should be good.  No guarantees obviously, but I’ve done this three times and no data loss yet.