& not so recent
additions & corrections
Windows 10 Pro - folder
"Can't find the specified file" / "The file or folder does not exist".
Having experienced a certain amount of frustration at not having a
working JRE on my old Windows 7 Pro workstation, I gave way to a moment
of insanity and upgraded it to Windows 10. As it said with
the installer download information, 'don't worry, all of your files and
programs will still be there and you can carry on working straight
away'. Um, yes, well, - not quite. The 'upgrade'
wiped out all of my passwords, SSH keys, IP addresses and bookmarks,
forcing me to spend several days reconfiguring software and hardware.
Indeed, this passage was added to the website prior to my seeing if I
have regained the ability to upload it. My bookmarks will never come
back (medical treatment, important suppliers, research articles, etc.)
so I will have to rebuild that information as I go along. Furthermore,
Win 10 adds a fair bit of psychedelic clutter in an attempt to
appeal to 5-year-old cellphone users, and it takes a while to get
rid of this cruft and make it possible to work without
experiencing constant migraine (although, it is not quite as
bad as Gmail, which has decided that its users will be unable to grasp
the filing-cabinet metaphor and so has replaced 'folders' with 'labels').
I have coped with the dumbing down, and
the deliberate frustration of user intentions in the interests of
advertising, but obviously the sheer amount of programming effort
involved in creating a ridiculously unergomomic interface has caused
some eyes to stray from the metaphorical ball. The real killer in Win
10 Pro, which took days to overcome just in itself, is that it is not
possible for users to rename folders. This applies to the Pro version
1709 in this case, but the issue might be more general. The Win 10 Home
edition, versions in the 1800- range, is unaffected.
This might sound like a trivial
problem, but it prevents file-reorganisation and structured archiving,
and in my case it does not exactly fit well with >40 years of
scientific and engineering activity. My son Steve and I tried
everything to fix this bug via file ownerships and privileges, and in
the end by editing the Registry, but all to no avail.
The Registry editing soultions offered
online incidentally, are somewhat fraught. Commenting-out 5
registry keys is said to fix the problem (it didn't work for me), and
because using Regedit is a bit scary, some kind souls have offered
self-executing fixes. I downloaded one, but instead of running it, I
opened it with Notepad and had a look. It would have made
changes to the desktop and hundreds of folders, presumably
turning the computer into an extreme adware platform or worse. I also searched
for reviews of the download site and learned that the author was a
'good guy' who would never do anything bad to your computer. I suspect
that this was what is known as a 'fake review'.
In the end, I decided that the bug
could not be fixed and started to look for a work-around. Once I had
abandoned the lame idea that there might be some possibility of
repair, I was in business within minutes. The solution I discovered is
odd, but ridiculouly trivial. Windows won't give the file owner or user
the right to rename a folder in Explorer, but it allows 3rd
software to rename folders. Hence, having created a backup
folder for my website in File Explorer ('New folder', not renamable) I went to it in
OpenOffice and renamed it to what I wanted it to be called. The same
trick works with Photoshop and Nvu, but not with
Microsoft Notepad (which presumably uses procedures belonging to the
You can't make this stuff up, and it is
hard to imagine how a software build with such a fundamental bug can
end-up being released. The solution is straightforward though: until
Microsoft addresses the problem in an OS update, do your file
management via the 'file' dialog of a non-Microsoft app.
between DWK and John Crabtree, KC0G on the origin of Wheeler's
(includes new references).
More has been added to the article on Converting an existing bike into
. The article first appeared on
The camerasunderwater info collection has been
transferred to this website. See the Photography and Optics
For those who notice such things, it will be apparent that I
have decided at last to bring my HTML writing methods into the 17th
Century. I started writing this website in
around 2000, using a piece of software called 'Adobe
Pagemill produced terrible HTML (what the hell is a
'naturalsizeflag' ?), but it had some very clever features that were
not replicated by later programs. Particularly, it had a link
checker and manager that allowed files to be relocated; i.e., a file
could be moved to a new folder and all the pages linking to it would be
updated accordingly. That allowed the maintenance of a
logical data hierarchy, which is a serious bonus in a site with as many
files as this one.
Pagemill was never updated to keep
abreast of new HTML standards because Adobe first replaced it with a
horror called 'GoLive', which wanted to kidnap the victim's website and
imprison it in
a databse, and then acquired a piece of
software called 'Dreamweaver'. Giving GoLive a miss for
reasons; I tried editing my website
using Dreamweaver, but quickly discovered that the dream was a
nightmare. I had produced many of my page layouts by using
Dreamweaver however insisted that all data in every table
cell needed to be contained within a paragraph, so would insert
<p> at the beginning of each entry and
</p> at the end. This was not required by the
but any attempt to delete these spurious tags would result in
them being reinserted when the file was saved. So,
opening a file in Dreamweaver and then saving it had the effect of
utterly destroying the layout.
At the time of mein Kampf mit
Dreamweaver, there was talk of new browsers that were not going to
support old HTML standards. The idea, in the minds of the
individuals promoting this approach was, presumably, that people would
be able to come back from the dead to re-edit their work. I
started to panic, and tried out various other editors, but there seemed
to be none capable of editing pre-existing pages without wrecking
them. All insisted that the user had to do it their way, and
the orthodoxy seemed to be that no web page actually needed to have any
significant content; so it was obviously necessary to force vast
amounts of blank space.
So eventually, I gave up and carried on
Pagemill, while slowly converting pages into pdfs and dreading the
point at which browsers would cease to
parse my HTML. That problem, of course, never happened;
firstly because all of the people who had died since the beginning of
the Internet proved to be disinclined to
update their markup,
but mainly because the idea of excluding legacy code is idiotic.
To do such a thing would be software project suicide, because
results in a browser that can't browse. Deprecated coding
methods are not
secret, and so it's obvious that a browser
just has to render what it gets. The rather
Archive Wayback Machine
for example, somewhat depends on that facility.
But there comes a point at which even I
have to admit that a piece of software is too old. Indeed,
Pagemill now has to be run under Wine, or in an XP Virtualbox.
So I started looking around and reading software reviews, and
discovered that the horrors of the early 21st
Century have mostly gone away. Checking for broken links, for
example, can be accomplished by means of an online link checking
service (e.g., brokenlinkcheck.com
and, better than Pagemill, these services check both internal and
external links. Furthermore, there are now HTML editors that
don't wantonly destroy pages they didn't create.
One such editor is Nvu
free WYSIWYG for Windows, Mac and Linux. It gets good reviews
(with some reservations - see, eg., sitewizard
but the real $64k question that reviewers fail to address is: "What
happens when you open and save a 20 year old page?"
In the case of Nvu, the software corrects any glaring errors
declares the code, somewhat optimistically, to be HTML 4.01
Transitional (i.e., in this case, very loose).
Also, having performed this automatic
conversion, it does not assume that the page needs to be saved unless
the user also makes a change.
By making a minimal non-rendering
change in (say) the page header, it is possible to save the file and
see what the conversion has done; and the glorious and unprecedented
result is that the page looks exactly the same as it did before (in
Chrome and IE at least). Now, suddenly, I find that it is
possible to update old pages without re-writing them from scratch.
It's a wonder that other development teams had not thought of
this. Moreover, should you go into source mode and delete
changes made by the software, they actually stay deleted
(provided that the code remains internally consistent).
So, with thanks to the Nvu team, the
pages in this site can now be updated as and when they need editing;
and the source will then be seen to declare (in the sense
of 'Lies, Damned lies, and statements of conformity') that it is HTML
Nvu is discontinued as of 2008-09-12. It was replaced by KompoZer
which is essentially the same as Nvu but with some bug fixes.
. Started porting optical &
from the Cameras
Underwater Info website
The English translation of Paul Drude's 1902 paper "On the
construction of Tesla transformers: Period of oscillation and
self-inductance of the coil.
" Can now be downloaded from
arXiv.org and cited accordingly: arXiv:1605.04196
and self capacitance of solenoids
. v 1.00
Coils terminated by a parallel impedance behave differently from coils
operated with one or both ends open circuit (vertical antennas, Tesla
coils, helical resonators). The troubled history of self-resonance and
self-capacitance modelling is due to the unrecognised impossibility of
analysing these two very different situations using the same formulae.
This article demonstrates that standard helical transmission-line
theory does not apply in the uniform current case, and that it also
needs considerable extension if it is to be applied properly to free
coils. A new semi-empirical free-coil model is based on an Ollendorff
helical transmission line terminated by its own axial field and fringe
field capacitances. The author's well known 2008 update of Medhurst's
formula (CL-DAE) remains valid.
self-resonance measurements by Alex Pettit, KK4VB
Added information on the use of a neon bulb array to visualise fields.
Some changes to the discussion in view of work on the main
self-capacitance and self-resonance article.
: Bob Weaver has a new article on
the Geometric Mean Distance
method for calculating inductance, including the first ever estimation
of the error inherent in using it. He also introduces the use of Monte
Carlo methods as solution to the mathematical intractability of many
I have issued a new version of Notation
Symbols and Abbreviations
(1.09). Despite the IOP guidelines, I have not (yet?) made the decision
to put all mathematical variables in italic
but I am in the process of eliminating any difference in meaning
between plain and italic symbols. All articles with version dates after
Feb. 14th 2016 will reflect this change (although few are actually
affected). The main issue was that in some documents I had used an
italic form to represent a quantity per unit length. I had thought of
creating new symbols to get around this early bad decision, but
actually it is easier and less confusing simply to put length into the
equation, e.g., resistance per unit length becomes R/ℓ
: A new version of Solenoid Inductance
is available (v 0.20). There are some
minor additions and a partial re-write of the introduction. Most of the
changes are to the typesetting and layout of equations. The work is
: A new (still unfinished) draft
detectors for RF measurement
is available (v 0.09).
2015, Nov 27th
reworking of the complementary follower detector
Patrick Turner. A full discrete component op-amp circuit with
long-tailed pair for NFB gives -3 dB @ 10 MHz.
: Updated version of Inductor