• Tech

    Uninstall “Advanced Mac Cleaner”

    1. Stop Advanced Mac Cleaner from the Activity Monitor
    2. Delete Advanced Mac Cleaner from the Applications folder
    3. Delete Advanced Mac Cleaner from the User’s Login Items
    4. Delete the helper application from ~/Library/Application Support
      • amc
      • awc
      • Advanced Mac Cleaner
      • Mac Adware Cleaner (You will be asked to authenticate).
    5. Delete the Library files
      • Advanced Mac Cleaner
      • Mac Adware Cleaner
      • hlpramc
      • hlprawc
      • hlpramcn
      • hlpradc
      • pcvark
    6. Delete the Launch Agent files
      • adwarecleaner
      • hlpramc
      • hlprawc
    7. Then, return to the Library folder again (back arrow), and open the folder named Preferences. Locate all files containing the names Mac Adware Cleaner, adware, adwarecleaner or pcvark, and drag them to the Trash.
    8. Return to the Library folder again (back arrow), and open the folder named Logs. Locate all files containing the names Mac Adware Cleaner, hlpramc, hlprawc, and drag them to the Trash.
    9. Return to the Library folder again, and open the folder Saved Application State. Locate all folders containing the names pcvark or Mac Adware Cleaner, and drag them to the Trash.
    10. Open System Preferences > Users & Groups > select your User Account > Login Items. Select the item named Mac Adware Cleaner, and click the [-] (minus) button to delete the now nonexistent program from your Login Items.

    Or, you could try out AppCleaner from FreeMacSoft.

  • DirecTV

    [iOS] Cannot login to DirecTV as TV Provider

    If you’re a DirecTV subscriber and trying to watch TV shows on iOS/iPad OS/TV OS, you may have encountered an error when trying to log into DirecTV. Individual channel apps may ask you if you want to Link your TV Provider to the app and if you select “Yes”, you will be presented with a login screen for DirecTV.

    Unfortunately, the API version of the login screen has some kind of error (probably an encryption mismatch) and will give you an error saying

    That User ID doesn't seem to work here. Please sign in with a different ID. Care Code 205.4

    You should FIRST check that you have the correct user ID and password by logging into your account page at DirecTV.com. If that works, then the problem is with the interface between your iOS device’s API and DirecTV’s auth server. You can circumvent the API by logging in via web…

    You have to select a TV Provider that is not DirecTV and NOT log in. I chose AT&T U-verse then backed out of the setting screen. This will leave your TV Provider setting blank. Then when an individual channel app asks for your TV Provider info, you can select DirecTV and you will be presented with a clunky web-base login page instead of the sleek API screen.


  • Office 365

    How to change the UI language for Office 365 for Mac OS X when it’s stuck

    THE PROBLEM: I finally took the plunge and subscribed to Office 365. Once installed, I noticed all the User Interface (UI) was in Japanese. There was no setting in each Office applications’ Preferences and also made sure that US English was chosen in OS X’s System Preferences > Language & Region > General. I had used the Japanese setting before, so I made sure to delete that from the list and restart the computer. I even deleted my Japanese input method from the Keyboard Preference pane. To no avail, Word, Excel, and Powerpoint UIs were stuck in Japanese.

    THE CAUSE: If you’re a long time Mac user like me, you have probably migrated an old OS X account from computer to computer – preserving the users’ preferences through many versions of Microsoft Office. And if you’ve worked for a foreign company, you probably have installed a non-native language version of Office once before but uninstalled it since then. Your computer might have been setup by the company IT in a foreign language, then your account was created in English. In scenarios like this, “smart” installers like the one for Office 365 for Mac might picked up the scent of the foreign language files and presented you Word, Excel, and PowerPoint in that foreign language.

    THE SOLUTION: You can fix this by forcing the individual application to re-remember (or forget) it’s UI language.

    1. Open System Preferences > Language & Region > Apps pane
    2. If Word/Excel/Powerpoint is not listed, click the “+” button to add it.
    3. From the dropdown list, choose the language it’s currently showing (in my case, Japanese). Keep System Preferences open.
    4. Open the application, then Quit it.
    5. With the application closed, now choose the language you want (in my case, US English)
    6. When you open the application again, it should be in the language you want it to be in.
    7. One step further: If you’ve chosen the same language as the System’s default language, you may delete the entry from the list using the “-” button.

    This is a much safer solution than to delete the lproj folders from the Contents of the application or executing Terminal commands against the plist files.

  • Fujitsu Scansnap S1500M

    Fujitsu ScanSnap S1500M/S1300 vs OS X Catalina

    With the upgrade to OS X Catalina’s 64-bit environment, ScanSnap Manager, the heart and soul of the system is no longer usable. The new 64-bit ScanSnap Home software is not compatible with the older scanners.

    Your choice is to:

    • Junk the old scanner and get a new one (expensive)
    • Use 3rd party 64-bit scanning software like VueScan or ExactScan (clunky)
    • Keep the older 32-bit compatible OS X running until the day you buy a new scanner (dangerous)

    Although choice 3 sounds like a bad idea for security, there is a way to get around this:

    • Load OS X Mojave in a virtual machine (Parallels/Fusion)
    • Designate an old Mac as a scanning station

    If you’re a hoarder holding on to an old ScanSnap, you probably have a end-of-life Mac being used as a dumb station for listening to LIVE Lo-Fi Beats on YouTube. You can designate this machine as a scanning station. You might even have an older printer that still works that you’re not willing to throw away. This Mac will also be your print station! Just remember, this Mac will soon be a security issue, so make sure you don’t leave anything on it.

    Of course, if this doesn’t inspire joy, Marie Kondo it and just get a new scanner.

  • Tech

    bash script to fix e-mail message dates on OS X Server with dovecot

    Recently I moved a Cyrus mailstore on a dying XServe to a Dovecot mailstore on a new Mac mini.

    I f**ked up and copied files without the -p option to preserve the file dates.

    cp -p     #Doh!

    Mail clients like OS X’s Mail.app do not read the mail header for the actual message’s received-date and uses the file modification date. Now I have hundreds of thousands of mail messages from 2004 that say they are from Dec 31, 2019 (Yes, I was working New Year’s Eve).

    So I had to find a way to read the dates from the messages and set the modification dates on each message file. As a lazy hacker, I looked for somebody that already had the same problem. I found Steve Major’s example. It was easy to follow and helped me see the limitations of BSD on OS X. There were other example scripts for Linux but those wouldn’t have worked for OS X. Mainly, the -d option for the date command had a totally different implementation.

    date -d #OS X is not Linux

    Like I said, I’ve been running a server since 2004, so I was unsure if all the mail headers would include a “Date” field compliant with RFC2822. They didn’t.

    I had to take the largest common denominator of date formats and try to get them to conform to RFC2822. So, I first wrote a quick script that parsed the files and wrote all the Date fields to file for examination. I quickly saw that 99% of the messages could be forced to conform to the format that I needed with minimal intervention.

    So I took Steve’s code and modified it to my collection of messages. And in the meantime, figuring out that OS X BSD can reformat dates if it was sanitized to a known format.

    date -j -f "%d %b %Y %T %z" "$datestring" "+%Y%m%d%H%M.%S

    This is where I found out I didn’t have to manually convert the Month names (%B) to Month numbers (%b), but I had to sanitize the Timezone (%Z) to a UTC offset (%z)… and that the legacy timezone format we’re all familiar with like “CST” was no longer kosher with UNIX. In addition to that, I would have to force the OS X shell to read ALL locales if I wanted to convert legacy timezones automatically to UTC offsets. But because I pre-examined those Date fields, I noticed that only users in the US had their UTC offset missing and only had legacy TZ. All other countries are SO used to handling UTC offsets, it was a given.

    So after two weeks of programming in-between grocery shopping and flipping houses, I have finally created: