Worked on the Univac 9700 which first came out with magnetic wire memory that replaced cores in earlier systems. Fixing memory errors was done by desoldering the affected wire, sliding it along and resoldering it. The wire memory was much faster than the core memory and was about the same speed as the early chip memory.

This evening I was asked to look at firefox for a relative as she was getting this Bing thing that wouldn't go away. I was puzzled and thought there must be a virus that caused it. However, tomorrow is the day when Pipex disappears as her ISP.

Thanks, I altered the type of network card in the VM and login was successful.

I tried logging in using 1 google and one googlemail ID and passwords, nothing doing - using VirtualBox.

It was someone from Airbus who said the ultimate aim was to crew an aeroplane with a dog and a pilot. The pilot's job would be to feed the dog and the dog would be there to bite the pilot if he touched any of the controls. I think Boeing got it right.

When you buy memory from an outlet, see how ESD damage is thought not possible if they grab the memory by the ends with thumb and forefinger. I have had to tell shops that they would be sacked on the spot if they were working on building or handling memory at the manufacturer. They proudly tell you they've never damaged memory, just because purchasers have not hot footed it back to the shop minutes later to say it's broken. The damage they've caused may not result in failure for months, but it will. With a large antistatic mat and a monitored wrist strap I have found memory is the most frequent failing component.

Neither this or moonshine work, sites still still invite downloading Silverlight in order to play content. I have .NET sources that won't build under mono 2.2, so it's usefulness seems limited to code specially written for it.