site  contact  subhomenews

Googled has tightened restrictions for login

October 21, 2020 — BarryK

I discovered this a couple of days ago, went to login to my Gmail account, and got a message that my browser does not have javascript enabled or is an incompatible browser.

This is on my laptop, which has SeaMonkey 2.53.3. I just checked, The latest EasyOS has SM 2.53.4, and can login to Gmail OK.

What I did with SM 2.53.3, is go to "about:config" then search for "useragent", then there is this parameter:


Which is set to "false". Right-click on it and choose "toggle", so it then becomes "true". Then login to Google works.

I think that it is really dumb that some companies will bar a browser based on the user agent string, given how easy it is to change it.

You can check your browser user agent string here:

Running 2.53.4 right now, and without the above parameter toggled to "true", this is what I get:

Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0 SeaMonkey/2.53.4

If I were to toggle that parameter to true, the user agent is the same except doesn't have the "SeaMonkey/2.53.4" on the end.

I am wondering whether I should set that parameter as "true" by default? It is simply an entry in /root/.mozilla/*/prefs.js:

user_pref("general.useragent.compatMode.strict-firefox", true);

If anyone reports this login problem with latest SM, then will do.

EDIT 2020-10-22:
How about that, yesterday was able to login to Google with my 2.53.4 SM, this morning can't. Setting "strict-firefox"  user agent has fixed it, so that will be the default for next release of EasyOS.

Tags: tech

How to boot Win10 from a USB stick

June 08, 2020 — BarryK

Over the years, I have not had good experiences with Windows 10. There were a couple of posts to the "ethos" tag in this blog:

A few days ago, I accidentally wiped the Windows 10 installation on my Lenovo desktop PC, purchased early 2020. Here are some posts:

I was developing EasyDD, and accidentally wrote a EasyOS image file to the NVME drive, destroying the Win10 installation, as reported here:

The NVME drive had four partitions. partition-1 was the fat32 esp boot partition, partition-2 was only 16MB don't know what for, partition-3 is the actual installation (ntfs C: drive), and partition-4 was a ntfs 1GB "recovery drive".

Writing the 1.3GB image file to the NVME drive destroyed the GPT (GUID Partition Table) and the first three partitions. However, partition-4 was still intact, and I thought that I could use it to reinstall Win10.

There is a secondary, backup, GPT at the end of the drive, so running "gdisk nvme0n1" I was able to use the secondary GPT and restore the first GPT.

But no way could I figure out how to use partition-4 to recover Windows!!!

I downloaded Win10 ISO from an official Microsoft website ...and then the fun and games started.

The ISO is about 5GB, too big for a 4.7GB DVD. After some searching, the only solution is to use a double-layer DVD. There was lots of advice, including on official MS sites, to write the ISO to a USB-stick.

Boot the ISO from a USB-stick, reasonable yes? No!!! I tried and tried, googled, heaps of other frustrated people reported the same problem, it won't boot. After some hours, I discovered that MS has used the udf filesystem for the ISO, which the UEFI-firmware on my desktop PC doesn't recognise. And, it seems, same situation for everyone else.

Why use udf, why not iso9660? There is a file, "install.wim", that is 4.2GB, however, iso9660 only supports files up to 4GB. hence, one or two years ago, MS changed to udf. Note, fat32 also has the 4GB file-size limitation.

Can't boot from a USB-stick, that is bad news. What to do?

Well, we can make a Win10 bootable USB-stick, with some ingenuity. What I did was use a EasyOS USB-stick, and gutted it.

EasyOS on a USB flash drive has two partitions, a 640MB fat32 esp boot partition, with reFind boot manager, and a second ext4 partition that fills the drive.

I reformatted the second partition as ntfs, and copied the contents of the ISO file to it. Like this, where sdb2 is the mounted USB-stick second partition:

# mkdir mntpt
# mount -t ntfs /dev/sdb2 /mnt/sdb2 (or in Easy just click on the partition)
# mount -t udf Win10_2004_EnglishInternational_x64.iso mntpt
# cp -a mntpt/* /mnt/sdb2/
# sync
# umount mntpt
# umount /mnt/sdb2 (or in Easy just click the close-box)

In the first partition, I deleted everything except the "EFI" folder, and in /mnt/sdb1/EFI/BOOT/drivers, deleted 'ext4_x64.efi' and copied /usr/share/refind/drivers_x64/ntfs_x64.efi to /mnt/sdb1/EFI/BOOT/drivers (you will need reFind package installed).

/mnt/sdb1/EFI/BOOT only needs 'BOOTX64.EFI' and 'refind.conf', and I edited the latter to only have this:

timeout 10
textonly on
textmode 0
scanfor manual
menuentry "Windows 10 USB" {
volume usbwin10ntfs
loader \efi\boot\bootx64.efi

Where "usbwin10ntfs" is the label that I assigned to the second partition:

# blkid /dev/sdb2
/dev/sdb2: LABEL="usbwin10ntfs" UUID="47360BD96837F0BC" TYPE="ntfs"

...I used Gparted to set that label, but whatever it was before would be OK, no need to change it.

Rebooted the PC, holding down the <F12> key to get the UEFI boot menu, and there was the USB-stick, and was able to boot Win10. However, no way could I find out how to use that partition-4 to perform a recovery, had to do a fresh install to partition-3. The install wrote appropriate stuff into the partition-1 fat32 boot partition also.

I was able to jump through these hoops in Linux, but Windows users, well, maybe their only solution is to use a double-layer DVD, and reinstall Win10.   

Tags: tech

Documentation for Lenovo Ideacentre 510S 07ICB

March 22, 2020 — BarryK

GCMartin expressed interest in this PC. He asked for the Blowfish speed test result in HardInfo, and I reported "1.83", which he responded is very good.

For anyone who might be interested, all documentation is online. The PC only comes with a tiny piece of paper with getting started instructions. The PDFs are here: 

Here are earlier reports on this PC: 

Tags: tech

The resurrection of GOOSEE Diagrammer

March 12, 2020 — BarryK

Back in 1999, I wrote a book, titled "Flow design for embedded systems", published in the USA by R&D Books. It describes a diagramming technique that I invented, for designing code, prior to actual coding. There was a floppy disk attached inside the back cover, with a Windows 32-bit application called "GOOFEE Diagrammer".

The book is out of print, however, used copies are available, for example at Amazon:

I received an email from Scott M., asking if I have the companion disk. Scott collects old books, and he has two copies of my book, without the floppy disk. I replied that around 2009, when I lived near the small town of Perenjori in Western Australia, my house was burgled, and my 4TB external backup drive was stolen, which had a lot of that old stuff in it. But, I told him that I would look and see if the companion disk is archived somewhere else, such as in a CD/DVD.

I have an old computer, with Cyrix 5x86 CPU, Zip-drive, and 20GB IDE hard drive, that was my main workhorse in 1999. I got rid of most of my old computers when left Perenjori, however hung onto that one. I did take a few things out of it at some time, so it no longer works. So, need to be able to access that old IDE drive, and I even found an old 100MB Zip disk, that I think has GOOFEE development on it.

So I bought one of these, for AU$28:


...the photo shows it plugged into my Zip drive. Note, it has a IDE power plug as well. On the right is the cable to the mains power adapter, and centre cable is the USB3 cable to the PC.

Unfortunately, my 100MB Zip disk doesn't work, Inserts OK, whirring sounds, but nothing more. The 20GB IDE HD works fine.

Yes, I found the companion disk, but also found the development files for "GOOSEE Diagrammer". GOOFEE is an acronym for "Graphical Object Orientation For Embedded Engineering". It is a GUI tool for designing a program, however, I realised that it also had the potential of also generating the code, as C code -- hence GOOSEE Diagrammer was born. GOOSEE is an ancronym for "Graphical Object Oriented Software Engineering Environment".

GOOFEE Diagrammer got mixed reviews. One guy thought that it was very useful for code design where he worked, and suggested an alternative acronym "Graphical Obfuscation Operation For Eternal Employment"!

Anyway, the C code generation part of it (introduced with GOOSEE Diagammer) never got publicly released. I lost interest, as I had moved onto "EVE"


"EVE" is an acronym for "Embedded Vector Editor", a general-purpose vector drawing application. See here (source code also available):

GOOSEE Diagrammer

This extension to GOOFEE Diagrammer, with generation of C code, never got released. I think that it reached version 1.4beta1, however, I can only find version 1.3 on my old 20GB IDE hard drive. I even installed 'testdisk' via the PPM, a file recovery tool, to no avail.

'goosee.exe' is a Win32 application, and still works in Windows 10.


What I found has now been uploaded. Here is an introduction:

Example from above link:


User manual:

Tarballs are available:

...the last one is the source code. GOOFEE and GOOSEE Diagrammer are written in assembly language, and require MASM, Microsoft's assembler, to compile. Which is free:

Useful links here:

Is GOOSEE Diagrammer actually useful as a code design and generation tool? Or just a novelty plaything? Perhaps it depends whether your brain is "graphics oriented" or "text oriented". I do recall for me at the time, I had decided that I preferred just to code directly, no need for an intermediate design phase -- but it might be different if more than one person is working on a project.  

Tags: tech

Librem 5 hardware evaluation

November 02, 2019 — BarryK

I have posted about the Librem 5 phone, the last post is here:

I have wondered about whether it is viable from the viewpoint of power consumption, and yesterday came across an evaluation of the Librem 5 hardware design, by an engineer with expertise in the hardware of this field: also raises other concerns.

Will Purism get the phone to a point where it is basically usable? Not have to be recharged twice per day, and able to connect while on the move?

There is mention of the reality not living up to the hype, and this interview with a former employee of Purism is revealing:

Small businesses, of a certain kind, depend on hype for their survival. Hype, spin, whatever word you want to use, to catch people. Quite possibly the ensnared people will be satisfied with the result.

Purism may survive and may actually deliver products that satisfy customers -- well, their laptops seem to be already achieving the latter goal. On the journey between dream and delivery, they need cash, the money must roll in, hence hype, or selling the dream, is essential.

I am reminded of an Australian TV series, "Very small business", about a business named "Worldwide Business Group", that was perpetually on the verge of financial collapse. The guy running this business published obscure magazines that nobody read, and at the start of the series he wanted to hire a journalist -- he found a guy who was a professional journalist but had had a mental breakdown, and was wanting to get back into journalism -- he was taken on on-probation, or whatever word you would use when you work for no pay.

Here is a trailer for the series, very low resolution (144p):

...I think that you need to join i-Tunes to view the full episodes. There was a later series "Back in very small business", that I have not seen.

Tags: tech

Librem 5 and Pinephone assembly

October 15, 2019 — BarryK

The first prototypes of these phones are built and shipped to some developers.

The Librem 5 is planned to be manufactured in batches that will be progressively refined. The first one is named "Aspen", to be followed by "Birch". Here is a video showing Aspen being disassembled and reassembled:

Interesting, it has no heatsink. A heatpipe is planned for Birch. The speaker, Tod Weaver, states that he has to charge the battery twice per day, but is hoping it will eventually get down to once per day. That would be very light usage without heatsink. I wonder how many hours of actual usage in the day?

Whatever, that is so far off we expect with modern phones. My Huawei rarely gets below 90% in a day, in which I might, say, go on a train ride to the city and be browsing all the way there and back. If drive somewhere and use the GPS, it does consume a bit more.

The SoC is, I think 28nm technology, and I think I read that late in 2020 they plan to progress to a 14nm NXP SoC. The two m.2 sockets with external modem and ...what's in the other socket, can't remember ...anyway, that configuration is going to be current-hungry.


The Pinephone is an alternative. They both have modem separate from the SoC, in the case of the Pinephone it is soldered in, so the phone is much slimmer. Here is a video showing assembly of the first prototype:

Interesting, it looks like the back of the LCD is being used as the SoC heatsink. I haven't found any information on battery life, but doubt that it will be good news ...but premature to give any opinion.


One good thing about the Pinephone, it has a modem with frequencies suitable for Australia.

Tags: tech

Librem5 phone first batch

September 27, 2019 — BarryK

The first batch of Librem5 phones has been manufactured. This is their first iteration, somewhat larger than the planned final version to allow for some experimentation, for example with the antenna.

I have posted a few times about this phone, for example:

Purism announcement:


And here is an FAQ about the first batch:

I had gone off this phone, in favour of the Pinephone, as the Librem5 did not have a modem with frequencies suitable for Australia. However, they have just announced that they will be supporting the BM818 modem -- this has a "T1" variant that supports the B28 band that we require for Telstra. However, it is not yet known whether the phone will support the T1 variant. I suppose one problem will be the antenna design, to handle all the different frequencies. 

EDIT 2019-10-04:
Here is a video, showing using phone, first batch:  

Tags: tech