Disk Warrior Report

Kappy was helping me with my MBP problem with my MacIntosh HD. He recommended, as did others to get the Disk Warrior which I did. I ran it a couple of times last night after I talked with Apple Care support on line-he couldn't figure out what was wrong. I am asking for someone to review this, in particular the File errors down below and give me an interpretation.
I appreciate your help.
Time: 12/7/08 2:17:32 PM DiskWarrior Version: 4.1
DiskWarrior has successfully built a new optimized directory for the disk named "MacIntosh HD." The new directory is ready to replace the original directory.
Notes: All file and folder data was easily located.
Comparison of the original and replacement directories indicates that there will be changes to the number, the contents and/or the attributes of the files and folders. It is recommended that you preview the replacement directory and examine the items listed below. All files and folders were compared and a total of 13,919,576 comparison tests were performed.
Errors, if any, in the directory structure such as tree depth, header node, map nodes, node size, node counts, node links, indexes and more have been repaired.
File: "日本語.html"
Repaired Text Encoding Location: "MacIntosh HD/Applications/Adobe Bridge/Legal.localized/"
Explanations: Text Encoding: File and folder names are stored in Unicode characters. The text encoding value indicates the method used to convert the file name to Unicode. Repairs prevent the name from being displayed incorrectly.
Disk Information:
Files: 510,953
Folders: 135,461
Free Space: 79.31 GB
Format: Mac OS Extended (Journaled)
Block Size: 4 K
Disk Sectors: 311,909,984
Media: FUJITSU MHW2160BHPL
Time: 12/7/08 8:29:49 PM DiskWarrior Version: 4.1 DiskWarrior scanned the disk named "MacIntosh HD" checking all files and folders for damage and potential compatibility problems.
Disk: "MacIntosh HD" Location: "Desktop"
The Property List data was checked in 10,101 files.
The Resource Data was checked in 6,340 files.
The maximum Folder Depth on this disk is 21. This does not exceed the maximum recommended depth.
File: ".cdc.mk4e.plist" Detected that Property List data is damaged and cannot be repaired.
XML parser error: Unexpected character at line 1
Old-style plist parser error: Unexpected character '0x4' at line 1 Location: "MacIntosh HD/Users/goldenmr2w/Library/Preferences/"
File: "com.apple.scheduler7098.plist" Detected that Property List data is damaged and cannot be repaired. Conversion of data failed. The file is not UTF-8, or in the encoding specified in XML header if XML. Location: "MacIntosh HD/Users/goldenmr2w/Library/Preferences/"
File: "com.apple.iphotomosaic.plist" Detected that Property List data is damaged and cannot be repaired. Conversion of data failed. The file is not UTF-8, or in the encoding specified in XML header if XML. Location: "MacIntosh HD/Users/goldenmr2w/Library/Preferences/"
Explanations Folder Depth: This number indicates how many folders are nested inside each other. If a disk contains only three folders and Folder A is inside Folder B and Folder B is inside Folder C, then this disk has a maximum folder depth of three. Folders nested too deeply can cause software compatibility problems.
Property List: This is a standard file format for storing data and is often used to store preferences. The names of these files normally end with a .plist file extension. Corrupt property list files can cause system instability.
Resource Data: This is an older file format for storing data and was often used to store preferences. The names of these files normally end with a .rsrc file extension. Corrupt resource data files can cause system instability.
Thank You Again,
golden2 Denver

Mr. Kappy-I did not see your name on board, and thank you so much.
I just ran a repair disk permissions and got:
Warning: SUID file "System/Library/CoreServices/Finder.app/Contents/Resources/OwnerGroupTool" has been modified and will not be repaired.
which is a whole lot better than all the stuff I was getting yesterday before Disk Warrior.
So maybe that is why the Apple Care person could not find anything wrong.
Okay, I really promise this time not to touch anything I am not supposed to.
May I ask one thing-do you recommend downloading Disk Warrior and have it run routine maintenance as well? And it is okay if I can figure that our for myself, too.
I appreciate your very understandable explanations and recommendations.
golden2 Denver

Similar Messages

  • Suggestion: Use Disk Warrior/ Disk Utility before, after 10.5.6 update

    FWIW: For years I have used a combination of Disk Warrior and then Disk Utility before and after updates, major installs, etc. Normally I boot right into Disk Warrior and let it do it's routine and after that check the disk and repair permissions using Disk Utility. Result: Many years of OS X iterations with no problems yet. Knock on wood.
    10.5.6: Same routine, no problems.
    Observations:
    Disk Warrior reported a higher number of Directory graph items out of order after being run prior to installation than most updates of this size in my opinion.
    Disk Utility: The disk checked fine and no permissions were repaired. Except that old Group 26.....
    Net: 10.5.6 seems the fastest of the Leopards so far. Safari is by far the best yet. It also seems there are a ton of 3rd party apps being updated so be sure to follow due diligence and turn off the Haxies before you begin.
    I am beginning to get excited about Snow Leopard, as Leopard's progress is really starting to show.

    I thought I was obsessive compulsive for running Repair Disk, Repair Permissions and Disk Warrior (and sometimes TechTool Pro) before installing any OS updates. It’s good to know someone else does that.
    I too have never had a problem with any updates. When I installed the first version of Leopard 10.5, it balked on my G5 1.6 GHz computer because it had non-Apple RAM in it that neither Disk Utilities nor Disk Warrior would catch (or even TechTool because it looked like good RAM, but the initially finicky 10.5 installer did not like it). The only way I figured it out was to run System Profiler from the install disk, so I added that to my list of “before installing” tasks.
    It seems many people having problems with updates don’t know to at least run Disk Utilities before an update.
    It’s good you are trying to get the word out.

  • Mac Book Crashing Can anyone please help with this error message,  I've run Disk warrior and everthing is coming up fine, so may be a hardware issue, thank you Interval Since Last Panic Report:  22119 sec Panics Since Last Report:          14 Anonymous UU

    I've run Disk warrior, it says all the files and harddrive are fine.
    thanks for your help.  This crashing was happening before I upgraded to Lion
    Interval Since Last Panic Report:  22119 sec
    Panics Since Last Report:          14
    Anonymous UUID:                    1DA2B715-D1E5-4BF1-A47F-D31CBD8C1E78
    Wed Mar  7 13:21:17 2012
    panic(cpu 2 caller 0xffffff7f8098c907): NVRM[0/1:0:0]: Read Error 0x00000100: CFG 0x0a2910de 0x00100000 0x00000000, BAR0 0xd2000000 0xffffff80a0354000 0x0a5480a2, D0, P2/4
    Backtrace (CPU 2), Frame : Return Address
    0xffffff80a398b800 : 0xffffff8000220702
    0xffffff80a398b880 : 0xffffff7f8098c907
    0xffffff80a398b910 : 0xffffff7f80a7ca64
    0xffffff80a398b960 : 0xffffff7f80a7cb24
    0xffffff80a398b9c0 : 0xffffff7f80d29749
    0xffffff80a398bb00 : 0xffffff7f80a9bbad
    0xffffff80a398bb30 : 0xffffff7f80996282
    0xffffff80a398bbe0 : 0xffffff7f80991b84
    0xffffff80a398bdd0 : 0xffffff7f80993639
    0xffffff80a398beb0 : 0xffffff7f8092e484
    0xffffff80a398bf00 : 0xffffff7f820a47d6
    0xffffff80a398bf50 : 0xffffff7f820a4f2a
    0xffffff80a398bf70 : 0xffffff800023db2c
    0xffffff80a398bfb0 : 0xffffff8000820057
          Kernel Extensions in backtrace:
             com.apple.NVDAResman(7.1.8)[94BA87BA-B128-3310-9860-98EC67AB7FAF]@0xffffff7f809 2c000->0xffffff7f80c05fff
                dependency: com.apple.iokit.IOPCIFamily(2.6.8)[F63D4ABE-42DA-33EF-BADD-3415B0CB0179]@0xffff ff7f808b7000
                dependency: com.apple.iokit.IONDRVSupport(2.3.2)[4B3F84DC-18B3-3897-BC56-4E3940878047]@0xff ffff7f8091a000
                dependency: com.apple.iokit.IOGraphicsFamily(2.3.2)[FE536983-1897-3D6B-965E-24B5A67080DA]@0 xffffff7f808e2000
             com.apple.nvidia.nv50hal(7.1.8)[7596DB8C-AE9D-3C87-B11A-0ED8F940CAF8]@0xffffff7 f80c06000->0xffffff7f80f27fff
                dependency: com.apple.NVDAResman(7.1.8)[94BA87BA-B128-3310-9860-98EC67AB7FAF]@0xffffff7f809 2c000
             com.apple.driver.AGPM(100.12.42)[380DAA3B-4F08-3152-A3A0-E3F8B6E4B92B]@0xffffff 7f820a3000->0xffffff7f820adfff
                dependency: com.apple.iokit.IOGraphicsFamily(2.3.2)[FE536983-1897-3D6B-965E-24B5A67080DA]@0 xffffff7f808e2000
                dependency: com.apple.iokit.IONDRVSupport(2.3.2)[4B3F84DC-18B3-3897-BC56-4E3940878047]@0xff ffff7f8091a000
                dependency: com.apple.iokit.IOPCIFamily(2.6.8)[F63D4ABE-42DA-33EF-BADD-3415B0CB0179]@0xffff ff7f808b7000
    BSD process name corresponding to current thread: kernel_task
    Mac OS version:
    11D50
    Kernel version:
    Darwin Kernel Version 11.3.0: Thu Jan 12 18:47:41 PST 2012; root:xnu-1699.24.23~1/RELEASE_X86_64
    Kernel UUID: 7B6546C7-70E8-3ED8-A6C3-C927E4D3D0D6
    System model name: MacBookPro6,2 (Mac-F22586C8)
    System uptime in nanoseconds: 5224512131000
    last loaded kext at 1624245923653: com.apple.driver.AppleFireWireStorage    3.0.1 (addr 0xffffff7f808b3000, size 16384)
    last unloaded kext at 1739101632802: com.apple.driver.StorageLynx    3.0.1 (addr 0xffffff7f80809000, size 8192)
    loaded kexts:
    com.regularrateandrhythm.driver.RowmoteIREmu    1.0
    com.bresink.driver.BRESINKx86Monitoring    8.0
    com.AmbrosiaSW.AudioSupport    3.2
    com.apple.driver.Oxford_Semi    3.0.1
    com.apple.driver.AppleUSBDisplays    317
    com.apple.driver.AppleHWSensor    1.9.4d0
    com.apple.filesystems.autofs    3.0
    com.apple.driver.AudioAUUC    1.59
    com.apple.driver.AGPM    100.12.42
    com.apple.driver.AppleMikeyHIDDriver    122
    com.apple.driver.AppleHDA    2.1.7f9
    com.apple.driver.AppleUpstreamUserClient    3.5.9
    com.apple.driver.AppleMCCSControl    1.0.26
    com.apple.driver.AppleMikeyDriver    2.1.7f9
    com.apple.driver.AppleIntelHDGraphics    7.1.8
    com.apple.driver.AppleIntelHDGraphicsFB    7.1.8
    com.apple.driver.SMCMotionSensor    3.0.1d2
    com.apple.iokit.IOUserEthernet    1.0.0d1
    com.apple.Dont_Steal_Mac_OS_X    7.0.0
    com.apple.driver.AudioIPCDriver    1.2.2
    com.apple.driver.AppleSMCLMU    2.0.1d2
    com.apple.GeForce    7.1.8
    com.apple.driver.ACPI_SMC_PlatformPlugin    4.7.5d4
    com.apple.driver.AppleMuxControl    3.0.16
    com.apple.driver.AppleLPC    1.5.3
    com.apple.driver.AppleUSBTCButtons    225.2
    com.apple.driver.AppleIRController    312
    com.apple.driver.AppleUSBTCKeyboard    225.2
    com.apple.driver.AppleUSBCardReader    3.0.1
    com.apple.iokit.SCSITaskUserClient    3.0.3
    com.apple.AppleFSCompression.AppleFSCompressionTypeDataless    1.0.0d1
    com.apple.AppleFSCompression.AppleFSCompressionTypeZlib    1.0.0d1
    com.apple.BootCache    33
    com.apple.iokit.IOAHCIBlockStorage    2.0.1
    com.apple.driver.AppleUSBHub    4.5.0
    com.apple.driver.AppleSmartBatteryManager    161.0.0
    com.apple.driver.AppleFWOHCI    4.8.9
    com.apple.driver.AirPort.Brcm4331    513.20.19
    com.apple.iokit.AppleBCM5701Ethernet    3.0.8b2
    com.apple.driver.AppleEFINVRAM    1.5.0
    com.apple.driver.AppleAHCIPort    2.2.0
    com.apple.driver.AppleUSBEHCI    4.5.8
    com.apple.driver.AppleACPIButtons    1.4
    com.apple.driver.AppleRTC    1.4
    com.apple.driver.AppleHPET    1.6
    com.apple.driver.AppleSMBIOS    1.7
    com.apple.driver.AppleACPIEC    1.4
    com.apple.driver.AppleAPIC    1.5
    com.apple.driver.AppleIntelCPUPowerManagementClient    167.3.0
    com.apple.nke.applicationfirewall    3.2.30
    com.apple.security.quarantine    1.1
    com.apple.driver.AppleIntelCPUPowerManagement    167.3.0
    com.apple.iokit.IOFireWireSerialBusProtocolTransport    2.1.0
    com.apple.iokit.IOFireWireSBP2    4.2.0
    com.apple.driver.AppleUSBHIDKeyboard    152.3
    com.apple.driver.AppleHIDKeyboard    152.3
    com.apple.driver.AppleUSBAudio    2.8.2f5
    com.apple.kext.triggers    1.0
    com.apple.driver.DspFuncLib    2.1.7f9
    com.apple.driver.AppleSMBusController    1.0.10d0
    com.apple.iokit.IOSurface    80.0
    com.apple.iokit.IOBluetoothSerialManager    4.0.3f12
    com.apple.iokit.IOSerialFamily    10.0.5
    com.apple.iokit.IOFireWireIP    2.2.4
    com.apple.iokit.IOAudioFamily    1.8.6fc6
    com.apple.kext.OSvKernDSPLib    1.3
    com.apple.driver.AppleHDAController    2.1.7f9
    com.apple.iokit.IOHDAFamily    2.1.7f9
    com.apple.driver.ApplePolicyControl    3.0.16
    com.apple.driver.AppleSMC    3.1.1d8
    com.apple.driver.IOPlatformPluginFamily    4.7.5d4
    com.apple.driver.AppleSMBusPCI    1.0.10d0
    com.apple.driver.AppleGraphicsControl    3.0.16
    com.apple.driver.AppleBacklightExpert    1.0.3
    com.apple.nvidia.nv50hal    7.1.8
    com.apple.NVDAResman    7.1.8
    com.apple.iokit.IONDRVSupport    2.3.2
    com.apple.iokit.IOGraphicsFamily    2.3.2
    com.apple.driver.BroadcomUSBBluetoothHCIController    4.0.3f12
    com.apple.driver.AppleUSBBluetoothHCIController    4.0.3f12
    com.apple.iokit.IOBluetoothFamily    4.0.3f12
    com.apple.driver.AppleUSBMultitouch    227.1
    com.apple.iokit.IOUSBHIDDriver    4.4.5
    com.apple.iokit.IOSCSIBlockCommandsDevice    3.0.3
    com.apple.iokit.IOUSBMassStorageClass    3.0.1
    com.apple.driver.AppleUSBMergeNub    4.5.3
    com.apple.driver.AppleUSBComposite    4.5.8
    com.apple.iokit.IOSCSIMultimediaCommandsDevice    3.0.3
    com.apple.iokit.IOBDStorageFamily    1.6
    com.apple.iokit.IODVDStorageFamily    1.7
    com.apple.iokit.IOCDStorageFamily    1.7
    com.apple.driver.XsanFilter    403
    com.apple.iokit.IOAHCISerialATAPI    2.0.1
    com.apple.iokit.IOSCSIArchitectureModelFamily    3.0.3
    com.apple.iokit.IOUSBUserClient    4.5.8
    com.apple.iokit.IOFireWireFamily    4.4.5
    com.apple.iokit.IO80211Family    412.2
    com.apple.iokit.IOEthernetAVBController    1.0.0d5
    com.apple.iokit.IONetworkingFamily    2.0
    com.apple.iokit.IOAHCIFamily    2.0.7
    com.apple.iokit.IOUSBFamily    4.5.8
    com.apple.driver.AppleEFIRuntime    1.5.0
    com.apple.iokit.IOHIDFamily    1.7.1
    com.apple.iokit.IOSMBusFamily    1.1
    com.apple.security.sandbox    177.3
    com.apple.kext.AppleMatch    1.0.0d1
    com.apple.security.TMSafetyNet    7
    com.apple.driver.DiskImages    331.3
    com.apple.iokit.IOStorageFamily    1.7
    com.apple.driver.AppleKeyStore    28.18
    com.apple.driver.AppleACPIPlatform    1.4
    com.apple.iokit.IOPCIFamily    2.6.8
    com.apple.iokit.IOACPIFamily    1.4

    Please describe:
    Computer model & hardware characteristics (especially RAM).
    How much free space left on HDD.
    Any add-ons you may have added to the system (antivirus, screen eye candy, etc.)
    What applications were running when the crash occurred.
    What were you doing when the crash occurred.

  • PhotoShop CC 2014 - Blowing Directories on Hard Drives - Should Ship with a free Version of Disk Warrior ;-)

    Since installing PS CC 2014 I have had serious problems.
    Problems one could expect from a 'new' software.
    However, having my drives' directories damaged due to Scratch Disks is something I have never seen before.
    I had PS use an SSD as Scratch Disk. As this became full, I assigned another scratch disk (This time a RAID0).
    As it ran full (200GB of PS Scratch) All the other files on that drive vanished. And photoshop was no longer able to even save the current document
    (event though the destination had enough space avail.) See screenshot:(Watch the finder status in the back, the doc to be saved was 200MB and my disk had 3.38 GB avail.
    But PS would not let me save due to scratch disks full)
    Anyway, back to the serious problem. The RAID0 scratch disk, after I quit PS, was not longer mountable.
    Trying to repair it with DU reported:
    And trying with terminal This:
    ** /dev/rdisk13
       Executing fsck_hfs (version hfs-226.1.1).
    ** Checking Journaled HFS Plus volume.
    ** Checking extents overflow file.
    ** Checking catalog file.
    ** Rebuilding catalog B-tree.
    CreateNewBTree returned -34
       Disk full error
    So I went ahead and did some research and found Disk Warrior.
    It was able to rebuild my catalog and I am up an running again.
    But having to spend $99 on a PS bug is not so nice. I have been able to recreate this problem 3 times the past hours.
    The problem occurs only when PS is using the RAID as Scratch disk. If I try to fill the drive by writing to it via terminal or Finder,
    i just get a Disk is Full. PS on the other hand will blow the catalog and make the  disk unmountable...
    Any Ideas ?

    Thanks for your reply, Chris Cox. I've checked the Windows System Event Log and here are the details:
    Details (Tab) of same error (Photoshop)
    I noticed since Jan 5, 2015, Photoshop has crashed a lot. I run Adobe Illustrator with it but it doesn't give the same errors. Other applications run fine too, so I'm not sure if it as you mentioned that it is the "system" that is crashing so often.
    (You seem to have suggested a video card upgrade. I will work on that next. Thanks)
    I hope you or anyone who can, help me with this problem with Photoshop and the issue with my account in Creative Cloud.
    Looking forward to your help. Thank you.

  • Disk Warrior 3.0.3 on OSX 10.6.8?

    I'm having major problems with my iMac (2.4 Ghz Intel Core 2 Duo/2 GB 66 MHz DDR2 SDRAM/running OSX version 10.6.8). Very, very slow to login, hangs up during normal use, slows to a crawl, etc. I did some searching on this forum and have tried some suggestions offerred to people with similar problems, such as running Disk Utility. When I ran it off the hard drive it went through the process with no real error messages (found a few "damaged files" and put them in folder named the same). Then I tried running it off my Snow Leopard install disk and got the message:
    Disk Utility stopped repairing "Macintosh HD" Disk Utility can't repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files.
    Next on my list, before going so far as reformatting/restoring (I use Time Machine to back up my system onto a 500 GB external hard drive) I want to run Disk Warrior. Here at the office we have a very old version (3.0.3). Will it work with Snow Leopard? I popped the disk into a Mac running Lion and it had the slash through the icon, indicating that it isn't compatible. However, I popped it into my work iMac, which is running the same OS as my problem iMac at home, and it looks as though it may work.
    Obviously the most recent version would be ideal but will this one at least run for me? If it will I think I'll give it a shot. If it doesn't work I'll look into getting an upgrade. Anyone know?
    One other thing...never could locate the S.M.A.R.T. info in my Disk Utility. Saw that mentioned several times in posts but it doesn't appear on my version. I did download an app called SMARTReporter and ran that. All indications were that my hard drive is OK.

    I'm unclear what you did after re-reading your original post. Did you do this:
    Repair the Hard Drive and Permissions
    Boot from your Snow Leopard Installer disc. 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 your hard drive entry (mfgr.'s ID and drive size) from the the left side list.  In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive.  If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer.
    If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.

  • Disk Utility sees problem invisible to Disk Warrior?

    Hi all,
    In brief: Disk Utility seems to think I've got a big problem, Disk Warrior seems to be unable to fix it.
    More detail: I ran verify disk from Disk Utility and was told I needed to repair my startup volume. So I ran Disk Utility's repair disk function from the install CD and it was unable to repair the disk. It was also unable to repair permissions.
    So I reached for trusty Disk Warrior and ran that. It rebuilt the directory, reporting various changes, eventually ending with zero errors. That should have fixed it, right?
    But then I re-ran Disk Utilty and was told, again, that the disk needed to be repaired.
    Here's what happened when I ran DU's repair function from the install CD:
    - I selected only the volume containing Mac OS X for repair and Disk Utility reported there's an "invalid leaf record count (it should be 3 instead of 525) and also that '1 HFS volume repaired' but '1 HFS volume could not be repaired'. (I'd selected only my startup volume).
    - The verify disk function reports the same
    - The repair disk permissions function cannot complete its task. Its error message reads: "Disk Utility internal error: disk utility has lost its connection with the disk management tool and cannot continue. Please quit and relaunch disk utility."
    So, I ran Disk Warrior AGAIN (2nd time) and sure enough, it reports that it successfully rebuilt the directory but that the rebuilt version has no changes from the original version (meaning it's ok, right?).
    Needless to say, if my startup disk DOES need repair, I want to do something about it. But does it need repair? And if Disk Warrior can't fix it, what can? Could it be that Disk Utility is seeing a problem that's invisible to Disk Warrior?
    By the way, I ran DW's manual diagnostic and it said the drive itself was operating normally.
    Very grateful if any of you can give me some insight into this.
    Jason
    Dual G5 2.5Ghz 2GB RAM, Powerbook G4 1.33Ghz, iPod 60GB   Mac OS X (10.4.8)   500GB internal HDD

    Hi Allan,
    Sure thing. Here's the business.
    Disk Warrior (v3.0.3)
    DW reports that it's successfully rebuilt a new directory each time I run it. I've run it three times now. The first time, there were differences between the original directory and the rebuilt version and it displayed a message coloured red describing this. On the subsequent two occasions, it has displayed a message coloured green and said there are "no changes to the number or contents of the files and folders" in the rebuilt directory.
    DW's manual diagnostic reports that the drive itself is "operating normally."
    DU
    Running DU internally (from the volume that also contains 10.4.9), it can only 'verify', of course. The volume's name is 'G5 hard drive'. The full message is:
    Verifying volume “G5 hard drive”
    Checking HFS Plus volume.
    Checking Extents Overflow file.
    Checking Catalog file.
    Checking multi-linked files.
    Checking Catalog hierarchy.
    Checking Extended Attributes file.
    Incorrect number of Extended Attributes
    Checking volume bitmap.
    Checking volume information.
    d.",1)
    G5 hard drive
    Error: The underlying task reported failure on exit
    1 HFS volume checked
    Volume needs repair
    Running DU (repair disk) from the install CD (for Powermac G5, OS X 10.3.5) produces the following report:
    Repairing disk for "G5 hard drive"
    Checking HFS plus volume
    Checking extents overflow file
    Checking catalog file
    Checking multi-linked files
    Checking catalog hierachy
    Checking extent attributes file
    Invalid leaf record count
    (It should be 3 instead of 422)
    Repairing volume
    The volume G5 hard drive was repaired successfully
    Repair attempted on 2 volumes
    1 HFS volume repaired
    1 HFS volume could not be repaired
    So let's say that DW is doing it all right, and the copy of DU on the install CD (10.3.5) is producing an inaccurate result because it doesn't match up with Tiger, I can understand that. But why would the same problem come up with DU run internally from (in the course of the last 24 hours) both 10.4.8 and 10.4.9 (because the problem survived my upgrade)?
    On the other hand, Allan, possibly DW isn't the right tool for the job. In that case, do you know what is?
    Thanks,
    Jason
    Dual G5 2.5Ghz 2GB RAM, Powerbook G4 1.33Ghz, iPod 60GB   Mac OS X (10.4.9)   500GB internal HDD

  • TM and  Disk Warrior

    The past few months I have had a problem with Time Machine getting corrupted often, but not always, when I do a restart. T M resides on a partition on an external disk. After a restart it either doesn't show up or is not mounted as shown in Disk Utility. The repair permissions and repair disk options are grayed out. Sometimes I can do a Verify Disk, but it always fails. The other partition on the disk is usually fine. Often if I run a repair permissions on the main Leopard partition on the iMac's internal drive, somewhere during the process a message appears that the T M partition is not repairable but is being made available with a read only functionality.
    Disk Warrior sees the partition and will begin the repair process. After a short time a message appears in the DW window stating "speed reduced by lack of memory" The process hangs on step 5, locating directory data. I found one time that if I just let it go in background for up to 2 days, the process will finally complete, and continue on to repair the disk. T M then works fine until the next time I have to restart the iMac again. The latest repair report from DW is as follows.
    • Errors, if any, in the directory structure such as tree depth, header node, map nodes, node size, node counts, node
    links, indexes and more have been repaired.
    • 2 iNode(s) had a link count that was repaired.
    • 6 link files no longer point(s) to an original file and therefore cannot be repaired.
    • 9 files had an incorrect key that was repaired.
    • 1 folder had a directory entry with an incorrect flag that was repaired.
    • 10 folders had an incorrect item count that was repaired.
    • 29 folders had a directory entry with an incorrect custom icon flag that was repaired.
    • Incorrect values in the Volume Information were repaired.
    • Critical values in the Volume Information were incorrect and were repaired.
    • There is no blessed System Folder, you will be asked to choose a System Folder after replacing the directory.
    • 6 files could not be found.
    • 9 folders could not be found.
    • 11 folders will have more items.
    • 1 folder will have fewer items.
    • 10 files will now become accessible.
    • 4 folders will now become accessible.
    • 2 files had a Name that changed.
    Disk Information:
    Files: 2,963,472
    Folders: 427,119
    Free Space: 773.69 MB
    Format: Mac OS Extended
    Block Size: 4 K
    Does anyone know what the problem might be causing T M to get corrupted, or at least how to get DW to perform the repair in a normal timeframe of just a few minutes?
    Thanks

    R C-R wrote:
    By this, do you mean that the partition's name is the one that appears after "Name: " in the Time Machine system preference & the partition contains a root level folder named "Backups.backupdb"? Is this partition used for anything else besides TM backups?
    Yes, separate partition with no other data on it.
    Disk Utility's permissions verify & repair options should only be available for mounted volumes (partitions) that are viable boot volumes; IOW, that can be used as a startup disk. TM backups are not startup volumes (because among other reasons they have no root level system folders), so both of these options should always be grayed out for TM backup volumes unless there is also a separate installation of OS X on them. If you have ever seen them not grayed out, this would be abnormal.
    BTW, I've been under the impression even partitions that are not bootable can be repaired. I have other partitions on other disks that have no system software that disk utility will go thru the repair process. Agreed that repair permissions is not available though.
    Often if I run a repair permissions on the main Leopard partition on the iMac's internal drive, somewhere during the process a message appears that the T M partition is not repairable but is being made available with a read only functionality.
    This doesn't make any sense to me. As explained above, permissions can't be repaired or verified on a normal TM volume. If you are repairing permissions on the normal startup volume on the internal drive of the iMac (or on any other startup disk), what is on the TM volume should be immaterial.
    Doesn't make any sense to me either. It doesn't happen all the time, but it does happen. Maybe something else is going on in the background while the permissions repair is going on that causes this result.
    A few other queries:
    How/when do you power down the external drive? If you shut down the Mac, do you wait for that to complete before powering down the external?
    Restart only when necessary, such as when new or update to software requires restart. Shut down only if I am having some other problem that I think might be helped by doing so. At shutdown, externals power down automatically.
    Is Disk Warrior an up-to-date, Leopard compatible version?
    Yes - 4.1.1
    Have you (perhaps inadvertently) manually changed anything in the folders of Backups.backupdb or created aliases that might reference any of its files or folders? Any chance that something destined for the other partition on the external drive accidentally was dropped into the TM partition instead?
    Not to my knowledge.
    Message was edited by: glassetcher

  • Disk Warrior and 'The Folder with the ? Mark'

    Good morning. My MacBook recently crashed and I am left with the dreaded and endlessly blinking 'Question Mark Folder'. I have tried to restart using the System Disk and running Disk Utility but the Hard Drive is nowhere to be found.
    I have read in the Discussions that running DiskWarrior may help. I have the program on my PowerBook G4 as well as on an external hard drive, but I do not have a DiskWarrior disc. Is there a way to run the program from these to repair the drive on my MacBook or retrieve my data? If not, is there a way to make a DiskWarrior disc from my .dmg file?
    Thanks for your help.
    John

    Disk Warrior comes on a bootable disc unless you downloaded it or lost yours. You cannot easily make a bootable CD or DVD, but your could put it on a bootable external hard drive that has a bootable copy of OS X (current version) and your copy of DW must be at least 4.0 for Tiger or 4.1 for Leopard.
    However, it's most unlikely that DW will help you because the question mark means that important system files are lost or corrupted. The solution is to reinstall OS X. It's possible you can do the following:
    How to Perform an Archive and Install
    An Archive and Install will NOT erase your hard drive, but you must have sufficient free space for a second OS X installation which could be from 3-9 GBs depending upon the version of OS X and selected installation options. The free space requirement is over and above normal free space requirements which should be at least 6-10 GBs. Read all the linked references carefully before proceeding.
    1. Be sure to use Disk Utility first to repair the disk before performing the Archive and Install.
    Repairing the Hard Drive and Permissions
    Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger.) After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported, then quit DU and return to the installer.
    2. Do not proceed with an Archive and Install if DU reports errors it cannot fix. In that case use Disk Warrior and/or TechTool Pro to repair the hard drive. If neither can repair the drive, then you will have to erase the drive and reinstall from scratch.
    3. Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When you reach the screen to select a destination drive click once on the destination drive then click on the Option button. Select the Archive and Install option. You have an option to preserve users and network preferences. Only select this option if you are sure you have no corrupted files in your user accounts. Otherwise leave this option unchecked. Click on the OK button and continue with the OS X Installation.
    4. Upon completion of the Archive and Install you will have a Previous System Folder in the root directory. You should retain the PSF until you are sure you do not need to manually transfer any items from the PSF to your newly installed system.
    5. After moving any items you want to keep from the PSF you should delete it. You can back it up if you prefer, but you must delete it from the hard drive.
    6. You can now download a Combo Updater directly from Apple's download site to update your new system to the desired version as well as install any security or other updates. You can also do this using Software Update.

  • Disk Warrior?

    I was having a problem opening certain programs (Office programs, iTunes) after updating Quicktime. Someone suggested that I repair my disk in disk utilities. I ran the repair and got this error:
    Invalid key length
    The volume Macintosh HD needs to be repaired.
    Error: The underlying task reported failure on exit
    1 HFS volume checked
    Volume needs repair
    First of all, what does all this mean? Someone on the boards recommended I purchase Disk Warrior to fix the problem. What are the chances this will actually fix it?
    The closest Apple Store is pretty far so I don't want to take it in if I don't have to. I also don't want to invest too much money because I plan on buying a new one in the next six months to a year.

    smitchell:
    what does all this mean?
    Disk Utility reports "Underlying task reported failure" when repairing a volume is a directory/filesystem corruption which cannot be repaired by Disk Utility. The article suggested the use of a third party disk utility. Tech Tool Pro and Disk Warrior are the best utilities for the job.
    Someone on the boards recommended I purchase Disk Warrior to fix the problem.
    As noted above, this is the utility most recommended in the forums as it is a very effective tool, as is the other utility I linked above.
    What are the chances this will actually fix it?
    There is an excellent chance that DW will repair the corrupted directory. Were your only error the invalid key length I would be more sanguine of success. However, with the -9972 error, I cannot guarantee it.
    In some cases the directory issue may be hardware based. It may result from a failing or failed HDD. If that is true in your case, DW will not do the job for you. However, since we don't know whether your issue is hardware or software based, it is not easy to tell.
    In most cases you would just go ahead and run one of these utilities anyway. If you had one of these in your toolbox, I would suggest that you begin there. However, these utilities cost around $100.
    Here is an option I would personally consider. If you have the latest PowerBook G4 12" it is now 3 years old. The average life of a HDD today is 3 to 5 years. In other words, your HDD is on the brink. For $100 you can buy a pretty nice HDD and with minimal skills, install it yourself. Of course, it will be helpful if you have a good reliable backup. If you don't you will then need to recover your data from the old HDD.
    Here is a link that suggests a variety of approaches to your issue: Kappy on Error -9972.
    I realize I have not given you very specific directions. However, I thought I would lay out some options for you to consider. Please do post back with your questions and/or comments.
    cornelius

  • Disk Warrior help

    hi, here's my situation.
    2.5 dual with 3.5 gigs of RAM. Running Tiger. hard drive i believe is a Hitachi (whatever is the default drive) and is 160 gigs.
    I was editing in DVPSP 3 and it kept quiting on me. so i restarted. when i did the OS did not come up instead i got the folder with the flashing question mark. not good. it happened to me last year and i knew that i was in trouble.
    I rebooted with the install cd. i then went to disk utility and tried to repair the disk. i got an error saying, "Invalid B-tree node size." from what i researched this means the drive is corrupted but not a hard drive failure, correct? i also looked for the start up disk but the drive was not detected there as well. all i saw was the install cd.
    I also have another internal hard drive installed. a 250 gig drive that i use for all my video work. it just so happened that the drive i was working on last night was my main drive (the 160 gig drive) as the 250 gig drive was full. this drive seems to be ok.
    I bought disk warrior last night which i installed on an Imac I have. I hooked this up to the 2.5 dual via a firewire cable. from the Imac i started Disk Warrior and i could see both my drives on the 2.5 dual. i selected my damaged drive and selected "Rebuild."
    I realized it was going to take a few hours so i went to sleep. this morning it was done and i read the report, saying it had built a temporary drive. like the dummy that i am (and being half asleep didn't help) i accidently cancelled everything. i didn't click on "Replace." ah!!!
    so i re-did everything while i went to work this morning. so when i get home later today, after i click on "Replace." everything will be good? i realize some stuff might be lost but i want to at least be able to boot into my system. i have a lot of photos that i want to save and also the latest project i was working on.
    is it true you can also "Preview" the new drive and be able to back up files right then before it replaces your old drive.
    any advice will be greatly appreaciated! thanks.
    - robert

    Hi, Roberto and ds_store—
    I'm writing to share a few thoughts, fwiw, in addition to ds_store's helpful reply. Though I consider myself a relative newbie to such maladies (particularly in OS X), I've unfortunately also experienced disk corruption within the last 10 days. . .
    (1) Re: "this means the drive is corrupted but not a hard drive failure, correct?" — probably. But this is something you can easily check. I'd suggest two things:
    ](a) Booting from your Install Disc, open Disk Utility and select your HD. Note the "S.M.A.R.T. status." Hopefully, it says "verified."
    ](b) While holding down the option key, boot from your Install Disc again. This will provide you with 2 or 3 choices of "boot volumes" for startup. Select Apple Hardware Test (AHT). Run in Extended Test mode. Among other components, this will provide results evaluating your logic board, mass storage (HD), and memory (RAM).
    If Disk Utility reports S.M.A.R.T. status "verified" and AHT indicates that mass storage has "passed," these provide a strong indication that your HD probably has not suffered any significant hardware failure. (Note that this is not definitive without further diagnostics that an Apple-Authorized Service Provider can conduct.)
    (2) Another benefit of running AHT is that it may provide an indication of other factor(s) that caused your Power Mac to suffer from such significant disk directory corruption. Imho, this is a question well worth your attention. (In my case, it was bad RAM. Not only didn't DiskWarrior work initially because of this — but the directory would have probably become corrupted again because of the RAM problem, even if I had been able to replace the directory with one "rebuilt" by DW.) Assuming DW does work for you (which seems likely, based on what you've described), you may benefit from running Disk Utility and DIsk Warrior again in the near future as a means to evaluate whether there is an ongoing source of corruption. Keep in mind that DW focuses on disk directory maintenance and repair — other HD maintenance/repair functions require TechTool Pro or other utilities.
    (3) Re: "a lot of photos that i want to save and also the latest project i was working on" — if DW is successful, your data may be fine. But if it proves necessary (and directory corruption isn't too bad or is improved by DW), you may be able to recover your unsaved data using FireWire Target disk mode, with your PowerMac as target and iMac as host.
    (4) Re: "is it true you can also "Preview" the new drive and be able to back up files right then before it replaces your old drive?" — I haven't tried this personally with DiskWarrior, but it should be feasible, according to the details described in the "What to Look for During Preview" section (pp. 30-33) of the DiskWarrior Manual that you can read from its CD.
    I hope some of this is useful to you. Good luck!
    Dean

  • Disk Warrior Shows Corrupted plists

    Greetings and Happy New Year!
    I've just finished running Disk Warrior on my boot drive (Lion 10.7.2) and it returned a list of corrupted plist files that can't be repaired. Before I try and run them down and move them to the trash, I want to double check that the list doesn't include items that might cause trouble should I decide to remove them. The following is a cut and paste from the DW report:
    File: ".com.cocoastuff.apple.plist"!
    Detected that Property List data is damaged and cannot be repaired.!
    Conversion of string failed. The string is empty.!
    Location: "SSD-LION/Library/Preferences (Corrupt)/"!
    File: "com.apple.systemdfine2.plist"!
    Detected that Property List data is damaged and cannot be repaired.!
    Unexpected character j at line 2!
    Location: "SSD-LION/Library/Preferences (Corrupt)/"!
    File: "com.apple.systemuinbws.plist"!
    Detected that Property List data is damaged and cannot be repaired.!
    Unexpected character } at line 1!
    Location: "SSD-LION/Library/Preferences (Corrupt)/"!
    File: "com.apple.systemuinccp.plist"!
    Detected that Property List data is damaged and cannot be repaired.!
    Unexpected character V at line 1!
    Location: "SSD-LION/Library/Preferences (Corrupt)/"!
    File: ".com.cocoastuff.apple.plist"!
    Detected that Property List data is damaged and cannot be repaired.!
    Conversion of string failed. The string is empty.!
    Location: "SSD-LION/Library/Preferences/"!
    File: "com.apple.iphotomosaic.plist"!
    Detected that Property List data is damaged and cannot be repaired.!
    Conversion of string failed. The string is empty.!
    Location: "SSD-LION/Users/Tim/Library/Preferences/"!
    File: "com.apple.appstore.plist"!
    Detected that Property List data is damaged and cannot be repaired.!
    Conversion of string failed. The string is empty.!
    Location: "SSD-LION/Users/Tim/Library/Cookies/"!
    File: ".com.cocoastuff.apple.plist"!
    Detected that Property List data is damaged and cannot be repaired.!
    Conversion of string failed. The string is empty.!
    Location: "SSD-LION/Users/Tim/Library/Preferences/"!
    I'd appreciate any suggestions or ideas regarding the items on the list. Specifically, is it safe to remove the corrupted files?
    Thanks!
    T-Ray

    Yes, downloaded DW this morning.
    I've had some inconsistent problems that include self-restarts.
    I had also noticed a sound coming from one of the drives (not the boot drive) that sounded like the drive was acting strangely. I dismounted the drive. To my untrained ear, it sounded as if the drive was swinging the read head arm every 10 seconds or so, even when the drive was not in use. All attempts to diagnose or repair the drive showed it acting normally but I know that it shouldn't be making a mechanical noise like that while at rest.
    The plists showing on the error list from DW include things that seem system related, i.e., .com.cocoastuff.apple.plist, com.apple.systemdfine2.plist, com.apple.systemuinbws.plist, etc. Since they aren't seemingly associated with an application, I can't really say if they're a problem or a false positive from DW.
    My natural inclination is to remove them, but their association with system-related items makes me hesitate.
    Thanks for your response!

  • Disk Warrior hangs in 10.4.7

    I originally posted this in the Tiger section in April, when I was using 10.4.6 - no replies then so I'm hoping someone's found a solution since. I just updated to 10.4.7 but the problem remains unchanged. It only seems to be an issue on the Powerbook; Powermac desktops running Tiger have no problems running the complete Disk Warrior routine.
    Original post:
    I've read just about every post relating to Diskwarrior here, but this seems to be a new wrinkle. Recently I took my G4 Powerbook (15" aluminum 1.25 GHz) from 10.3.9 in steps up to 10.4.6. No problems, did all the recommended things (repair permissions before and after each update, etc.). The volume is journaled. No issues with Firewire external drives. Apps seem to run OK.
    Today I bought DW 3.0.3 rev 39 thinking that now with Tiger I'd need that revision. (I had been using rev 38 with 10.3.9, no problems.) It boots from the CD fine, but when I run it it hangs up during the final "looking for differences in files/folders" stage. It may get only to 2-300 tests, it may get to 90,000 tests, but then it just hangs. The blue progress bar continues to "ripple" but no further progress happens. If I hit "skip" it'll go to the report, telling me (in red) that some repairs have been made, and that "nnn files will now be accessible."
    I hit "cancel", then quit DW to reboot the Powerbook. I can boot from the OS X install DVD and run Disk Utility to verify the hard drive as OK, and to repair permissions (one more time). According to DU, everything's fine - and the 'book does appear to run normally. It's just that DW always hangs at that last stage.
    Someone suggested that even if I skip the remainder of the DW process I can go ahead and replace the rebuilt directory. I've done that a couple of times but it leaves me with a very hinkety feeling.
    Thanks in advance for any help!

    If you have DW v3.0.3 Revision 38 (and not DW 3.0.2 in any revision because 3.0.2 was for OS X 10.3.x), you can use that on your machine. You can use v3.0.3 on any version of OS X from 10.2.1 to 10.4.x.
    Alsoft updates DiskWarrior for the sake of new hardware that is released with updated Boot ROMs. The new revisions are created so that they will be able to boot the new machines. The software itself is the same.
    For example, I use the original 3.0.3 version of DW on my G5 iMac, but since the DW disc won't boot the iMac, I use a version that's installed on a boot volume I keep on an external for the purpose of maintenance.
    Good luck!

  • Disk Warrior directory optimization on a system ssd?

    Disk Warrior 5 reports poor directory optimization on my 3rd party system drive SSD - a Samsung 840 EVO 512GB drive.   Knowing the issues with TRIM etc on Yosemite, is there any reason to not do this?

    Yeah, I had already reached out to them, but I wanted to cast a wider net for opinions or reports.   In the end, Alsoft responded with an AOK, and it went fine.   Performance a little improved, for sure.

  • 'Invalid node structure', 'Invalid B-tree node size', Disk Warrior useless

    Hi everyone, I am getting sick of this, it's the second time it's happened to me in a relatively short space of time, the first time with an Iomega external 500GB drive, this time with a 1.5TB Western Digital.
    I gave the Western Digital drive two partitions, (as I did for the previous Iomega drive), one for doing backups of my MacBooks internal drive, the other for random media, mostly VIDEO_TS folders.
    After going away for a couple of weeks, I returned home, plugged in the Western Digital drive via USB, the Internal backup partition showed in Finder, the other did not. Obviously I ran Disk Utility which was only able to show an error report with the usual 'Invalid node structure etc' message.
    I tried running Disk Warrior 4.2 (supposedly the version which works with Snow Leopard) from the DVD, (holding down the C key after restart), and..... nothing, just the grey screen and spinning wheel showing, so I gave up on that and installed DW to the Utilities folder. Now it starts up, the corrupt drive showed up, I hit the Rebuild button in DW, things seemed to be happening, but then the Beach Ball appeared and there was a (very) long hang before I decided to Force Quit.
    I am assuming that if DW can not fix the drive, it is done for, and may as well be used as a door stop.
    I am prepared to buy yet another drive, but can someone please give me an idea about why this has happened to me twice now, and what I can do to prevent it from happening again?

    Just erase the partition. Nothing yet suggests the drive is bad. When you got the drive did you prep it correctly? Usually bare drives are pre-formatted for Windows. You might consider doing this:
    Extended Hard Drive Preparation
    1. Open Disk Utility in your Utilities folder.
    2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Click on the Partition tab in the DU main window.
    3. Under the Volume Scheme heading set the number of partitions from the drop down menu to two and size them as you prefer. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, set the partition scheme to GUID then click on the OK button. Click on the Partition button and wait until the process has completed.
    4. Select the volume you just created (this is the sub-entry under the drive entry) from the left side list. Click on the Erase tab in the DU main window.
    5. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, check the button for Zero Data and click on OK to return to the Erase window.
    6. Click on the Erase button. The format process can take up to several hours depending upon the drive size.
    Repeat Steps 4-6 for the other partition. Alternatively, you can start with a single volume. After the zero data erase you can then re-partition the drive.

  • FYI: New version of Disk Warrior seems to hang when run with Snow Leopard

    FYI: It seems that the new version of Disk Warrior hangs when run in Snow Leopard

    I have been using DW 4.2 on 10.5.8 and the speed-up was the first thing I noted, too, so it isn't just SL.
    Now if it would only 'come up for air' and respond to input to move window (so I can put it where I can see it if needed) I'd like that.
    There is a 23 page review of Snow Leopard on Ars. On page 22:
    People sometimes ask what, exactly, is wrong with HFS+.
    Aside from its obvious lack of the features just listed, HFS+ is limited in many ways by its dated design, which is based on HFS, *a twenty-five year-old file system.*
    To give just one example, the centrally located Catalog File, which must be updated for each change to the file system's structure, is a frequent and inevitable source of contention. Modern file systems usually spread their metadata around, both for robustness (multiple copies are often kept in separate locations on the disk) and to allow for better concurrency.
    Practically speaking, think about those times when you run Disk Utility on an HFS+ volume and it finds (and hopefully repairs) a bunch of errors. *That's bad, okay?* +*That's something that should not happen*+ with a modern, thoroughly checksummed, always-consistent-on-disk file system unless there are hardware problems (and a ZFS storage pool can actually deal with that as well). And yet it happens all the time with HFS+ disks in Mac OS X when various bits of metadata to get corrupted or become out of date.
    Apple gets by year after year, tacking new features onto HFS+ with duct tape and a prayer, but at a certain point there simply has to be a successor—whether it's ZFS, a home-grown Apple file system, or something else entirely. My fingers are crossed for Mac OS X 10.7.
    If Disk Utility was reliable in mapping out weak sectors (it is not) and report/log errors. But it doesn't and I trust my data to other file systems when possible. We've come to expect and depend on 3rd party utilities and that Apple First Aid doesn't fix every possible error.
    Scanning one drive for errors can take a long time. Maybe it needs to be done, maybe in the background. With 2TB drives it gets worse. Spending hours to scan for errors??? I've set TechTool Pro to concurrently scan anywhere from one to a dozen volumes at once.
    An ounce of prevention, as they say, is worth a pound of cure.

Maybe you are looking for

  • Connecting a Mac Pro to an LCD HDTV

    It seems that LCD monitors don't come as big as LCD TV's, and I want to use my Mac Pro to watch movies and gaming. A Samsung 35T (30") costs around 1200$ where a 46" lcd HDTV costs about the same price. There is a card you can buy for the Mac Pro whi

  • Just wanted to say I love OS4, its like having a new phone!

    I usually dont post on forums, but I thought I would comment on OS4 that we all got today. I think its great (could of been much better, but better than nothing), I love the new features and the "look", seems like my battery life is a little better b

  • Another "can't connect" problem... can anyone help?

    My wife and I have been iChating with our daughter, who is in a dorm room, with no problems... until now. We get the "invite declined" screen or "failed to accept." It does not work either with AIM or a .mac account. It works fine within my own home

  • Re-installing InDesign

    I had a copy of InDesign CS6 on my iMac, but my computer crashed and I had to re-install the operating system. Now, when I try to re-install InDesign on the computer, I receive the following message: "Serial Number you provided is valid, but a qualif

  • MacBook Air and older iPods?

    My MacBook Air did not seem to take a liking to my original U2 Special Edition iPod when I grabbed it this morning, stuck a USB connector cable onto it and plugged into the Air, intending to use it as a disk drive and drag some tracks onto it to stic