I’m not sure why, but out-of-the-box, WordPress’s excellent TwentyTwelve theme prevents you from putting anything in the (empty!) top-right area of the page. It’s a great place for a “contact” link or similar (and check out the Suffusion theme to see how many widget areas a good WP theme ought to have…).
Continue reading
Everyone has had that dreaded experience: you open up the task manager on your computer… and there’s a program name you don’t recognize. It gets worse when you google the name and can’t find a concrete answer on what it is and why it’s there. It gets even worse when you remove it from Autoruns and it comes back. It gets terrible when you realize it has keylogger functionality. The icing on the cake, however, is when the mystery program is also eating up all your RAM.
…
The application does not store or transmit or even display the information polled. It does nothing. I spent the better part of two hours scouring the obscure corners of the binary, thinking surely I must be missing some cleverly hidden method that actually uses this data. I couldn’t find one.
…
that still leaves the question of why it’s doing this at all. The clues are there, vestigial remnants of removed code, exciting to any Executable Archaeologist: The generically named “Form1” of the application contains several widgets which are never actually displayed: a start button, a stop button, a place for displaying mouse coordinates, and a text box for displaying some other unspecified data. I believe this was originally a debugging utility used by “Spacer” engineers to calibrate the accelerometer so that it would not go off when one simply tapped on the touchscreen (triggering a mouse event or keyboard event). They didn’t bother to rigorously prevent memory leaks because it was never intended to run for more than a few minutes at a time. Somehow, through some miscommunication, a copy of this program with the logic for rendering the visuals stripped ended up on the list of utilities that needed to be kept in the final version of “Spacer’s” Windows 8 image for this model of tablet.
Apple has finally released drivers for Windows 8 (NB: because Apple takes standard PC hardware and then customizes it, Apple customers are reliant on Apple for “custom” drivers; the manufacturer drivers don’t work)
Also: the built-in copy of BootCamp has been updated, if you upgrade OS X to version 10.8.3 or later.
To recap:
Even being generous, that’s an 11 month delay between “the world discovering that Apple hardware needed a new set of drivers, or Windows 8 wouldn’t run” and “Apple delivering the drivers”. Many Apple machines were fine, but a large proportion were effectively blocked from running Windows 8 at all. It’s good to see this finally released, but … that’s a pretty poor service from a company the size of Apple.
Worst was the iMacs, where even machines less than 18 months old were (allegedly, according to the Apple.com forums) unusable on Windows 8. You could install it (with some hacks), but then the graphics card was disabled. This means: most major software won’t run (because the graphics card is used so heavily on modern computers you got corruption of on-screen info, or just massive drops in performance, so that apps were unusable), and definitely: no games.
…which, after all, is one of the main reasons for Mac users to dual-install Windows.
Interestingly, it seems this was caused by Apple’s modifications of the ATI graphics card, so that the ATI drivers were convinced there was an external monitor (which Apple didn’t provide a socket for, so there was nothing you could do – even if you owned a second monitor).
Interesting because: in the PC world, ATi used to be famous for writing low-quality, poorly-tested graphics drivers. ATi owners were accustomed to poring over every new minor version update “just in case” it fixed the glaring bugs in the previous one – and spent a lot of time de-installing and re-installing the older versions (when the newest version frequently introduced major new bugs).
So … although it’s ostensibly Apple to blame here in being so late to fix it, my suspicion is that it was some shoddy code in ATi’s driver that (accidentally) only affected Apple-modified cards.
3rd Party Device drivers: every OS-developer’s nightmare!
Apple’s core networking for OS X (Lion, Mountain Lion, etc) is famously poor. One of the (many) unfixed bugs is this:
“I go to a webpage (e.g. google.com) and my browser displays a message saying ‘Server not Found’. If I keep hitting Refresh, it never works. If I wait a few minutes and try again, it works”
This is entirely Apple’s fault. They aggressively (and incorrectly) cache “failed” lookups. And … because it’s Apple … you can’t turn it off. It’s been broken for at least 5 years now, which suggests they have no intention of fixing it.
But: you can “flush” it. Since it’s a cache (which are designed to auto-flush anyway), there’s no harm in doing this.
After the first time, you can repeat the command frequently without typing your password. Simply hit the “up” arrow (to re-type previous command) and Return to run it.
Here’s the magic URL, that you can’t access directly from the site:
http://www.virgin-atlantic.com/en/gb/bookflightsandmore/bookflights/callme.jsp
In 5+ years of flying with Virgin, their online booking system has always, every single time, failed – and redirected me to a page where I get that link to get THEM to phone ME.
(which is useful, since the evil mobile network operators don’t like Virgin’s 08-something numbers, and turn them into premium-rate bills)
It’s a pain going to the site, going through the pointless online booking, knowing that you’ll end up on the “our booking system sucks, click here” page.
So I’m blogging this so I never need to do it again!
Unity’s QA dept needs a smack up-side the head. If you get this bug, you’re a bit screwed – the only “fix” is to go into system settings and wipe Unity’s crud.
Error message:
type == kMetaAssetType && pathName.find (“library/metadata”) != 0
Thanks, Unity, that’s very human-readable and helpful. Not.
(appears to be an Assert written by a junior programmer – or a debug-only Assert that got left in the shipping version(!))\
Problem:
Solution (OS X):
For bonus points, the Unity 4 “upgrade” isn’t an upgrade: it’s a replacement. I expected it to download “the bits that have changed”. Nuh-uh. One gigabyte download! (try getting that in a hurry, when your project has suddenly imploded in front of you, because of the non-existent backwards-compatibility :( ).
I’ve seen similar behaviour before when writing very simple OS X apps. There’s some massive bugs in Apple’s code that have been around for 5+ years (and Apple shows no intention of fixing), which cause “startup actions” to happen in a semi-random order, depending on the NAME and NUMBER of recently-opened projects.
It takes very little testing to discover this. If it’s the problem with the Unity software, then Unity needs to seriously improve their testing on OS X – they should have discovered this easily.
But also … why on earth are they using the NSDocument loading system? Apple never finished writing the docs for it, they seem to have never finished implementing it (major bits of the API seem to be missing) – in general, OS X authors don’t seem to use it any more. Probably because it doesn’t work?
Prologue: Apple et al recommend you “install new OS’s from USB, not DVD – USB is faster”, but I’ve never bothered before. However, there appears to be a major defect in most Apple iMacs, where the DVD drives fail after only a dozen or so uses (google it and there’s depressingly-long forum threads of people reporting the same problem). When this hit my iMac, I was forced to explore the USB alternatives…
With the arrival of Windows 8, much of what we see on the web about “installing windows” or “booting windows” is wrong — including Apple’s own Bootcamp (currently: almost a year out of date, badly broken, and Apple hasn’t announced a fix. Sigh).
Allegedly (confirmed by direct experience, but I’m no expert on this) – Windows 7 (and previous versions) used “MBR” booting. Intel Macs use the more modern “GPT” booting – and Windows 8 has finally dropped backwards compatibility, and uses GPT too.
So, as of 2013: there is nothing “special” needed to make a Mac boot in Windows 8
In fact, if you try to, Windows 8 install WILL FAIL because it doesn’t support the old MBR booting any more (it even produces a clear, helpful error message explaining why)…
For power-users who know what they’re doing, this stack-exchange answer gives good step-by-step instructions (with explanations!) on how to “un-break” a broken boot setup on Mac. Worth bookmarking (I used it to fix one of my machines).
NB: all the tools they use in that answer are pre-installed with the Mac and have “man” docs – type “man (command name)” in Terminal to read them.
NB: you can run these tools straight away, but they will probably refuse to “save changes” because you’re using the disk they’re trying to change (mentioned in the link above). You’ll need to boot into a special “repair mode” – see below:
NB: if you mis-type the instructions on that page, you probably will wipe your hard disk. Don’t try this while tired/drunk/etc – or at least take a full backup of your computer first!
The web is plagued with technically unskilled “journalists” who write articles about “make a USB boot disk for OS X”, and all they do is copy/paste Apple’s own instructions on how to INSTALL OS X (and then they claim credit for it).
The OS X installer requires a 4GB – or, if you’re unlucky, an 8GB – USB key. That’s 8x what you actually need.
It is faster, easier, and safer to use Apple’s own “Make an OS X Bootable USB key” app, which works on any USB drive that’s 1 GB or larger.
You can even create the USB key without downloading the special app – although it requires more fiddling (I recommend: download the app. It’s small and trivial to use).
NB: if you own a mac, make one of these now. Do something useful with those crappy 1GB USB keys you have gathering dust on the shelf!
Because those USB boot disks are so massively valuable, Apple now includes a hidden one on your hard disk too, so that you can boot into that and “fix” your main OS X even if you don’t have a USB drive.
Here’s more info on the “Recovery Partition” as its called.
HOWEVER: since that’s installed on the same disk you’re partitioning, … most / all of the disk-repair / disk-alteration utilities are still disabled. That’s why you want/need a USB emergency disk!
Even devices that work during the Apple boot-menu are DISABLED BY APPLE in their “emergency repair / boot” setup.
But without a mouse, you cannot get to the OS X menubar.
And Apple designed their “emergency” system so that most of the features can ONLY be reached viw the menubar (hmm. They really didn’t think that one through…)
So, memorize this keyboard shortcut: ctrl-f2 (or, on a wireless keyboard or laptop: fn-ctrl-f2).
That hilights the “apple symbol” menu, and you can then use cursor keys to reach the other menus.
Someone at Apple went out of their way to make life miserable for Apple customers. If you own (or can borrow) a MacBook Air, Apple’s Bootcamp enables an extra “magic feature”: it will create the Windows 8 install USB key for you. (NB: requires a 4GB or greater USB key).
…but if you try this on any other physical Mac, Apple blocks that feature. The key you create will work on EVERY Mac – there’s nothing magical about it.
NB: if you have a Windows 8 DVD but don’t own an Air, and you know someone who does, it’s probably worth borrowing theirs now, to make one of those keys, in case you need it later!
NB: alternatively, if you have access to a machine that already has Windows installed, you can use Microsoft’s “create a Windows8 boot disk / installer” app (says win7, but works for win8 too). Unless you have a recent version of Windows, though, you’ll need to download hundreds of megabytes of .NET updates before this will run – which makes this a slow and irritating option.
OfficeTime is one of the more popular/higher rated time-tracking apps for iOS / OS X. On the whole, it’s fine.
But exporting the data – which is half of the app’s purpose – is extremely difficult. There’s no docs I could find either in the app or on the website. You have to google, get lucky, and find some old blog posts by the author with hints. And even then you still have to jump through a 9-step process.
Every time I need to do this, its sufficiently un-obvious that I forget how and have to figure it out again. So, here’s a step by step:
…after that, it’s plain sailing. The UX of the desktop app is poor, but it’s trivial from here to get to Excel, and clean up the data.
At first, I thought you should use the “Reports” menu.
Don’t do that – the export GUI is terrible, it saves files in the wrong format, and … the output format is harder for Excel to use. There’s an easier, better way…
Instead:
This gives you the exact times, down to the nearest minute. Most people don’t bill their client that way – although it’s good to show the actual numbers, you usually want to do a precise (accurate) total, and then round to the nearest 15 minutes for each billable period.
Here’s the Excel / OOO formula for that:
Create a SUM cell for all your times (use the appropraite column, not C6:C10):
=SUM(C6:C10)Create a ROUNDING cell for final number (C12 is wherever you put your SUM cell above):
=CEILING(C12; 1/24/60 * 15 )
NB: the “15″ in that last formula is the “number of minutes to round to” … replace it with “30″ for half-hours, “60″ for hours … etc.
Are you having this problem?
“I tell Firefox to ask before quitting, but it always quits without asking”
Especially on Macs, where cmd-w (close tab) and cmd-q (close window) are immediately next to each other…
It looks as though Firefox won’t fix this. It’s been 3 years, and it’s been reported to them plenty.
In the meantime… I found one solution that *does* work:
Plugin: “Always Ask” (tested on OS X Mountain Lion, with Firefox 16 – works fine)
I find it interesting. The developers decide to remove features – but seem to have misunderstood how/why those were important to the userbase.
Fortunately, the Firefox team are extremely open with their process. Anyone can see the reasoning and the debate that goes into each change – and can comment on it themselves with their own feedback.
So, reading the bug reports on Firefox.com, you can build up a picture. My impression – based on reading a bunch of these reports over the past few years – is that it went something like this:
That’s pretty sound reasoning. Although (and I’m not sure why?) … it seems they forgot to remove the GUI that lets users *insist* on the original behaviour, and to remove the three about:config flags that let advanced users fine-control it. Those are all still there, but they don’t work (any more).
But … by browsing the open bug reports, we find a bunch more reasons why Firefox had the original feature (just a sampling from what I read) :
…which explains why people get so angry and frustrated at the removal of this feature from the browser.
In short:
I suspect that the most common of these reasons is the Mac-specific one. So it’s very likely that a bunch of Firefox developers – who don’t use Macs – wouldn’t have been ABLE to see the problem for themselves. That underlines the importance of consulting your user-base…
After trying 4 or 5 things from this several-years-old page on Firefox’s support forums, I finally hit upon one that worked:
“For the heck of it tonight I clicked on Gmail in my calendar and it finally went to my gmail inbox.”
In my case, I just went to Google Groups, and clicked the Gmail link from the top navbar. Lo and behold – it works!
(this is after a week of having no way to access Gmail from my main web browser)
Looking at the problems other people have had, my guess is that Google’s code for running Gmail has some illegal (i.e. breaks-the-standard) bits in there that try to get around the browser standards by doing silly things with caching. Some of those are … fragile, perhaps … and tend to break easily. Over time, Google has added more and more unnecessary “features” to that code (e.g. I often have to wait for “connecting to google chat”, even though I have google chat permanently disabled and will never EVER use it) … there’s a *lot* of code in there these days; lots that could go wrong!
Normally, a Refresh of a page would fix this – that’s how the WWW was designed in the first place, as a core feature – but Google’s (my guess) playing so fast-and-loose that they’re *also* (deliberately? or accidentally?) bypassing the refresh. I can imagine several well-meaning reasons they might do that, but in the end I’d rather they stuck to the standards, instead of creating these “breaks permanently” problems for people.
And, of course, there’s no Google support for this problem. Once it strikes you, GOOD LUCK! (you’ll need it)
At 27″, it’s too big to “simply” take in to the Apple store. In desperation, I followed this support article from Apple that’s for older iMacs and officially no longer supported.
Which is a pity, because in typical Apple fashion, they’ve deprecated an article that’s still accurate and useful. Following the steps in that article (copy/pasted below in case Apple ever deletes the webpage – something they’ve a habit of doing, sadly), my fans roared to life and the iMac REVIVED!
Resetting the SMU can resolve some computer issues such as not starting up, not displaying video, sleep issues, fan noise issues, and so on. If your computer still exhibits these types of issues even after you’ve restarted the computer, try resetting the SMU. To reset the SMU on one of these iMacs:
Turn off the computer by choosing Shut Down from the Apple menu, or by holding the power button until the computer turns off.
[NOTE -- in my case, OS X had crashed completely, so there was no "turning off" to do - I had to yank the power cable out, and after that, it wouldn't switch on]
Unplug all cables from the computer, including the power cord.
Wait 10 seconds.
Plug in the power cord while simultaneously pressing and holding the power button on the back of the computer.
Let go of the power button.
Press the power button once more to start up your iMac.
I then had to repeat the process – but with a *fifteen second* wait, as per the support page that seems to supercede the article above – to get the fans to shut up.
Beware – latest version of Google Docs has the Gmail bug whereby emails (documents) randomly disappear and become completely inaccessible (this happens a few times a year with Gmail’s IMAP client). With Gmail, you can use the web interface to get around it and see the actual email – but with Google Docs, I don’t know of an alternative route. What you get is that Google appears to have deleted your data, with no comeback.
I just saw it now with Google Docs where a doc created yesterday allegedly didn’t exist any more – it had been removed from history, from recent documents, and … most distressing of all … it resulted in zero hits if you searched for it.
There’s none – it’s just Google’s software being stunningly bad (again).
You have to wait. And pray. And wait some more. And click random things. And pray some more.
For me, clicking around on the different tabs on the left hand side (Home, All Items, Owned by Me) after a minute or so it randomly reappeared.
I’m coming back to this topic more and more, because these abuses of web and HTML services are getting more and more damaging to the users.
If the “old” version of Google Docs doesn’t have this bug, it doesn’t matter – Google has already confiscated it from us. Unlike the core concept of desktop, laptop, and home computers … Google repeatedly takes the software that you possessed, and destroys it, for no reason other than to make things a little easier for engineers who don’t like to support the bad code they shipped.
That’s what this is about: people who use Cloud/SaaS to avoid taking responsibility for the apps they created.
I’m periodically re-trying GitHub’s GUI client, just in case it becomes stable enough for anyone to use on a real project.
Today, with the latest version: every time I start the app, it immediately hard-crashes. The app is literally unusable – it won’t run at all.
At least with the previous versions it would actually start up, so … this is a pretty big step backwards. If it had decent error reporting, like most apps do, I might be able to work out what’s wrong, but of course that’s one of the original problems with GitHub’s app – it disables all error reporting.
(as an aside: it’s interesting that Apple’s Mac App Store has made it so rare to see an app crash that … I can’t even be bothered to try and fix this app or complain about it. For an app to crash on startup is so VERY far behind the current “normal” for apps that … it’s just not worth the effort. I think the Mac App Store is one of the worst things to happen to computing in the last 20 years [if the US govt allows Apple and Microsoft to continue in this way, computers will become a thing of the past], but I have to admit it is achieving some great things)
Firefox … ah, how we love watching you make terrible usability decisions, and then force them upon your users!
FF now has this ridiculous page – WHICH YOU CANNOT DISABLE in Firefox settings:
Since it’s not supported as an user-configurable option, you have to open the magic low-level settings page. Type this into your web browser, as if you were visiting a new website:
about:config
You’ll get a list of settings, and a search bar. In the search bar, type:
newtabpage
You’ll get something like this:
…double-click the “browser.newtabpage.enabled” line until it says “false” in the final column. This will probably make it go bold:
…et voila! You’re back to a normal web-browser. Like you’ve been used to, all these years…
For those that are interested, here’s why I’m scathing about this page:
Most of all … because it actually breaks Firefox’s core feature (searching using Google).
That’s just downright stupid. How come no-one noticed this? Why on earth did they ship something that breaks the core web-browser functionality? I have no idea. Google’s Chrome team must be delighted when stuff like this happens – it just drives more and more people to stop using Firefox.
When you “upgrade” to Lion, be aware that Apple will silently wipe your “auto install / update” settings, and start aggressively downloading every update it can find for every Apple app you use.
In my case, this was gigabytes of data – I really don’t care (and don’t want) “upgrades” to PhotoBooth and other trash that Apple pre-installs. But, because Apple wants to force these on you, they’d already wasted large amounts of bandwidth (on my laptop – on a desktop broadband connection, I wouldn’t care), and reduced my internet browsing for a few days before I found this out.
So … when you upgrade … remember to open “Software Updater”, and change the setting (that Apple has overwritten), back to “don’t check automatically”. Sadly, there’s no setting for “don’t download stuff unless I tell you to” – but at least turning off the auto-check avoids this.
UPDATE: this technique didn’t work. I’m still trying to find something that does. One friend suggested hard-coding the address of all Adobe websites into your “hosts” file, and blocking them. This would prevent you from visiting Adobe’s sites – but would prevent the evil Adobe Updater trojan from downloading – but it will still keep TRYING to run. I want to kill the damn thing completely.
Adobe just doesn’t seem to get the message: the latest version of Adobe Acrobat Reader puts a NEW virus(*) on your desktop, and all the old methods for removing it … don’t work. I previously used this tip from 2010 to remove the virus, while still using the Adobe software installed on my machine, but it no longer works.
With OS X Lion, I’m now trying again with a new approach (through trial and error this seems it might work – but I’ll update this in a few months if the virus still hasn’t come back)
(*) Adobe’s “Updater” has so far:
This app cannot be disabled, the web is full of people complaining and begging Adobe to get rid of it, it’s installed secretly (the user is not informed it exists, let alone asked if they want it), and it has NOTHING TO DO WITH the actual app I installed.
What do you reckon? To me, that sounds closer to a virus than anything else. I don’t for a moment believe that Adobe is unaware of the amount of hatred it instils in their customers…
… It removes one of the most valuable features of OS X for laptop owners:
OS x lion WILL NOT recharge a plugged-in iPhone when the lid is closed (after 10 seconds of pretending to charge – just long enough to fool you – Apple cuts the power)
At conferences, on sales trips, on plane trips … I have relied on this feature many many times to recharge a phone off the laptop battery.
Now?
Denied.
No user setting for it (that I can find so far) just … Removed :(
Here’s ANOTHER overheating bug in Apple’s OS X.
This time, it’s the BlueTooth simulator built-in to the iOS Simulator (used every day by iPhone and iPad developers). The iOS5 version of the simulator has this crazy BT demon (process “BTServer”) that will sometimes – for no apparent reason – take up 100% CPU usage and melt your machine.
Solution:
UPDATE: So … it seems Suffusion has (buried deep inside the config) a way of displaying category pages with a higher-level workaround to the WP “missing feature”. Although so far I can’t find a way to set the settings on individual pages (which is what you generally need). So, I’ll leave this post up – it’s a good starting point for customizing Suffusion’s page-of-pages (which is also, it seems, how you would customize its Category pages.
Just to be clear, this is not a bug in Suffision, although it’s an oversight and I hope it’ll be included in a future version. The core problem is in WordPress: people have been requesting/expecting this feature for the past 5+ years, it’s pretty basic, but for now the WP folks haven’t added it.
This is VERY frequently requested by WP users: you want to have a Page on your site which lists the posts that are in a single Category.
WP has a very low-level way of doing this – which is very error-prone, hard to maintain (it’s hard-coded to database ID’s!), and requires you to break every single theme you own. Every time the theme is updated, you have to manually re-implement the fix!
Fortunately, there’s a minimal workaround (which is documented in the WP docs now (scroll to bottom)) which still (!) requires some theme editing.
Fortunately, Suffusion already has most of this workaround implemented, so we can make the fix without screwing around with the theme so much. The source code in Suffusion is almost identical to the sample provided by WP – but unfortunately it’s missing a key part. In Suffusion, you CAN list posts on a Page, but you CANNOT filter those posts by category.
So, edit the file “posts.php”, titled (in Suffusion): “Page of Posts”.
Where it has these lines:
$args = array(
'orderby' => 'date',
'order' => 'DESC',
'paged' => $paged,
);
…instead copy/paste the following:
$category_exclusive = get_post_meta($posts[0]->ID, 'category', true );
if( $category_exclusive )
{
$cat = get_cat_ID($category_exclusive);
$args = array(
'category__in' => array( $cat ),
'orderby' => 'date',
'order' => 'DESC',
'paged' => $paged,
);
}
else
{
$args = array(
'orderby' => 'date',
'order' => 'DESC',
'paged' => $paged,
);
}
As per WP’s official suggestion … if you want a page to filter by category:
One major thing here: We are being SAFE and non-destructive to the Suffusion theme.
Critically important is that we ONLY do a “filter by category” if the Page itself requests it. WP’s sample code does NOT have this protection (which is why the code above is slightly different).
This means that the rest of Suffusion (which doesn’t know about our new feature) is unaffected, and works as normal
One of the features of Gmail that I’ve long relied upon is the:
“Default: Reply to all, instead of Reply”
In 95% of cases, this is correct – it’s only rarely that you want to actively remove everyone else from the conversation.
…but this stopped working shortly after Google+ came out. Coincidence? I’m not sure.
Certainly, it’s caused MASSES of problems – people being dropped from email conversations, with associated obvious problems e.g. not hearing that a meeting’s been re-arranged.
I’ve bug-reported it to Google, but going on previous experience, there will be just silence.
