Thursday 31 December 2015

Debunking the cult of Apple

Of course, I don't believe in any kind of personality cult. This article debunks the cult of Steve Jobs to quite an extent by suggesting he was just another capitalist like Gates. I don't know anyone who idolises Gates that much. Apple have made some great hardware, but the prices they charge help to create the kind of elitism they aspire to, by pushing the purchase out of reach for a lot of people. That is one reason why the Ipad is so popular, because the cost has come down to something an average person can afford, but then it throws into hard focus why people are expected to pay so much more for a Macbook, Imac or Mac Pro.

Alex Gibney also made a documentary called "The Man in the Machine". The second article linked to refers to that documentary, and also a book which has questioned whether Apple will turn out to be too dependent on its visionary leader and floundering since he has gone. I think that is a very real likelihood because it has happened in so many other corporates; look at Microsoft's history under Steve Ballmer and all of their many new product fiascos. Apple went through that too, starting with Jobs' original tenure in charge of the Mac product development and launch, which soon demanded change he was unwilling to provide as early sales figures flopped, and which led to his ouster and departure. Apple did a lot of things right after he left, but it also made a lot of mistakes which led to his return 12 years later, and Jobs must have learned from the experience to have built the company up to where it was when he died. So there is plenty of scope for Apple to have a few challenges in the years ahead, and the size that the company is now makes it more likely to happen; a few bad product launches will hardly make a blip in a big company, but the US DOJ and EU will look at them a lot harder with antitrust considerations, and they are likely already in the legislators' sights.

The Mac4Newbies article is disappointing in that it dismisses the Apple scandals, the real ones like Jobs hounding Gizmodo over the lost iPhone prototype, suicide rates at Foxconn, the stock backdating scandal or the tax havens in Ireland. Over a four year period, from 1997 to 2001, after Jobs had returned as CEO, a number of backdated stock options were issued to Jobs and other senior Apple figures. The issue was that the options were not reported properly in Apple's books and led to charges of fraudulent behaviour against a couple of senior managers at the company. Both settled out of court and were subjected to various penalties by regulatory agencies. The tax rip-off is a much bigger issue not just for Apple but other companies worldwide which have engaged in similar practices to avoid paying tax in the countries in which they sell their products. In a nutshell this is how it works:
  • Manufacturer in the USA through its Chinese subsidiary makes a product in China for say $100
  • International Distribution in Ireland buys the product from Manufacturer's Chinese subsidiary for the $100 plus shipping costs.
  • International Distribution sells the product to New Zealand Retail subsidiary for $500.
  • New Zealand Retail ships the product to New Zealand and sells it for $600 to the customer.
We can see that a large amount of the profit was made in Ireland, not in the country where the sale was made. If a company in New Zealand is getting stuff manufactured, then the markup is generally going to occur in New Zealand and will be subject to our local laws and tax rates.  But if a company has enough volume of sales to open an office in Ireland then they can take advantage of the very low tax rates in that country in order to pay almost no tax. In fact there has more recently been allegations brought against Apple that Ireland improperly have levied almost no tax against them. The result has been that countries around the world are now looking at the amount of tax that is being avoided from these practices and it may well come to pass that Apple and other big corporates will find it much harder to engage in these practices in the future.

The doco is interesting because it managed to dig out a few people like one of the early Mac hardware developers, Bob Belleville, who haven't been in high profile roles since their time at Apple. Belleville got shown the door at the same time as Jobs, but unlike his erstwhile leader, little seems to be known of his work since then. Andy Hertfeld's Folklore website and the resulting book paint a great insight into some of the early developmental work at Apple, particularly around the time that the Mac was first developed in the mid 1980s.

Checking a mobile phone's IMEI status

All mobile phones have an IMEI number (International Mobile Equipment Identity). This number is part of an international system to uniquely identify each mobile phone. With the IMEI number phones can be identified and traced if they are stolen, or they can also be locked to a particular mobile operator's network. The IMEI number can be obtained from the phone in order to check its number.

The website IMEI.info claims to be able to check the status of the IMEI number of each phone and to advise whether a particular phone is simlocked. If you don't have another network sim card it may be the best way to check the simlock status for a phone.

I tried this with one of my old phones that I don't use any more. It is only 8 months old but I got a new phone two months ago and soon I will be buying my second Android, so I won't need that 8 month old as a backup. Along the way I discovered Vodafone now sells all of their phones locked out of the box. But if you can wait 9 months after you bought the phone, they don't charge you anything to unlock it.


Saturday 26 December 2015

Resolving long path errors deleting files in Windows

One of the most detested situations in just about any version of Windows is to receive the message that the path to a file or folder is too long. There are a number of variations of this message but one that is commonly seen when trying to delete files is "The source filenames are larger than is supported by the filesystem" which is an absolute load of BS and a total pack of lies. This is because the filesystem allowed these files to be created in the first place.

What is happening is that the filesystem since the advent of the Win32 API on Windows NT (the predecessor of Windows 10 going back to the very first version ever produced, NT 3.1 of 1993) has, in fact, supported paths up to 32768 characters in length, but because Windows Explorer was designed for a previous version of Windows (16-bit i.e. Windows 95 and its predecessors) that only supported 259 character paths (drive letter, colon and backslash plus 256 characters), it still enforces that limit. This creates a huge problem when trying to delete old files or paths (for example cleaning up the contents of a backup disk and removing old backups to make way for new ones).

The fact MS has never bothered to fix Explorer which means a huge inconvenience for many users means everyone has to find a way of bypassing Explorer to fix these problems. There are a number of different solutions which I have seen at different times.
  • A special script calling Robocopy to reach the bottom of a directory path and move each directory up one level at a time until it can be deleted. I used this one but can't recall where I got it from.
  • A useful looking program called Long Path Fixer appears to be able to address this problem. I have not tried testing this software.
  • The simplest option which I am now using is the file manager from 7-Zip. Since this excellent piece of software is already on all my computers, this has been the easiest to test and implement and has proved to do exactly what is needed provided it is used in the right way.
Specifically you start up the 7-Zip File Manager, then use that to browse to the folder you want to delete, select the folder and then using the keyboard press the Del key to recycle, or Shift+Del to delete outright. Note that pressing the Delete button or right clicking and choosing Delete actually work differently and are not as reliable as they will still produce the detestable error message. You have to use the keyboard commands to guarantee hassle-free results.

So after all of the huge hassles and inconvenience that MS has inflicted over the years due to a huge amount of uselessness from its programmers then being able to solve this problem is a great step forward.

Monday 21 December 2015

How to stop the popup notifications in Windows 10

If you have computers that are used continuously or exclusively for presentation then you may want to look at ways of stopping popup or toast notifications in Windows 10. After all one of the most annoying notifications is the one for new updates which is modal and therefore unable to be ignored, then it opens another window which can be very annoying.

(Presentation computers should also have the Updates settings changed so the updates don't just automatically install when MS feels like it and disrupt your use of the computer)

Using the Local Group Policy Editor you can accomplish the removal of notifications by permanently enabling Quiet Hours mode and preventing it from being turned off. This is only a per user setting rather than for the whole computer so you'll want to ensure you have a limited number of users on such a computer and you will need to make the changes for each one individually. You must be using an edition of Windows that allows local group policy editing, such as Pro, Enterprise or Education.


Here you can see where to find the settings in the local group policy and what they can be set to. The minimum I recommend are:
  • Set the time quiet hours begins - I enabled this and set it to 0 minutes after midnight
  • Set the time quiet hours ends - I enabled this and set it to 1439 minutes (23 hours 59 minutes) after midnight.
  • Turn off quiet hours - set to disabled. Doing this turns on quiet hours and it cannot be turned off with the icon in the system notification area. (The icon gives you the on/off settings in its context menu but clicking on them does nothing; the system will remain quiet)
Any settings you change will take effect more or less immediately.


Tuesday 8 December 2015

Using Windows 7 Photo Viewer in Windows 10

There is a great reason for this :) I like the Windows Photo Viewer which offers one-handed zooming with the mouse wheel and you just use the arrow keys on the keyboard to move to the next image. On the new Windows 10 photo viewer you have to press Ctrl to zoom with the mouse wheel and have to zoom right back before you can click the arrows at each side to go to the next or previous image.
To get the Windows 7 photo viewer back in Windows 10 is described in this article here
To summarise all you need to do is
  • Add these entries to the registry - copy them into a text file then rename it to a .reg file. Then double click the file to import it to the registry.
  • Right click on a photo and choose the app to open it as "Windows Photo Viewer".
This is quite a safe procedure because the registry entries contained below refer to the existing photoviewer.dll which is part of Windows and already installed in your system. It is not adding anything new to your system.

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\Applications\photoviewer.dll]

[HKEY_CLASSES_ROOT\Applications\photoviewer.dll\shell]

[HKEY_CLASSES_ROOT\Applications\photoviewer.dll\shell\open]
"MuiVerb"="@photoviewer.dll,-3043"

[HKEY_CLASSES_ROOT\Applications\photoviewer.dll\shell\open\command]
@=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\
00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,72,00,75,00,\
6e,00,64,00,6c,00,6c,00,33,00,32,00,2e,00,65,00,78,00,65,00,20,00,22,00,25,\
00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,69,00,6c,00,65,00,73,00,\
25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,20,00,50,00,68,00,6f,\
00,74,00,6f,00,20,00,56,00,69,00,65,00,77,00,65,00,72,00,5c,00,50,00,68,00,\
6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,65,00,72,00,2e,00,64,00,6c,00,6c,\
00,22,00,2c,00,20,00,49,00,6d,00,61,00,67,00,65,00,56,00,69,00,65,00,77,00,\
5f,00,46,00,75,00,6c,00,6c,00,73,00,63,00,72,00,65,00,65,00,6e,00,20,00,25,\
00,31,00,00,00

[HKEY_CLASSES_ROOT\Applications\photoviewer.dll\shell\open\DropTarget]
"Clsid"="{FFE2A43C-56B9-4bf5-9A79-CC6D4285608A}"

[HKEY_CLASSES_ROOT\Applications\photoviewer.dll\shell\print]

[HKEY_CLASSES_ROOT\Applications\photoviewer.dll\shell\print\command]
@=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\
00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,72,00,75,00,\
6e,00,64,00,6c,00,6c,00,33,00,32,00,2e,00,65,00,78,00,65,00,20,00,22,00,25,\
00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,69,00,6c,00,65,00,73,00,\
25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,20,00,50,00,68,00,6f,\
00,74,00,6f,00,20,00,56,00,69,00,65,00,77,00,65,00,72,00,5c,00,50,00,68,00,\
6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,65,00,72,00,2e,00,64,00,6c,00,6c,\
00,22,00,2c,00,20,00,49,00,6d,00,61,00,67,00,65,00,56,00,69,00,65,00,77,00,\
5f,00,46,00,75,00,6c,00,6c,00,73,00,63,00,72,00,65,00,65,00,6e,00,20,00,25,\
00,31,00,00,00

[HKEY_CLASSES_ROOT\Applications\photoviewer.dll\shell\print\DropTarget]
"Clsid"="{60fd46de-f830-4894-a628-6fa81bc0190d}"

Please note this has been updated to fix the problem with the above registry entries. There turned out to be a problem with copying them from the reg file to paste into this post, which has something to do with the way the registry file is formatted.