Hee hee hee:

Its not every day I get to correct the RenegadeMime.
The number of four letter combinations is 456,976, of which at least 101 are actually words in English.
This is 226.48 pages at the rate of 25 lines per page at 80 characters a column.
But!
I can print at the rate of 300 dpi**, and leaving a comfortable margin gives me a working area of 8x11 inches per sheet of paper. A old style font can be printed in a 8x8 pixel block.
Adding a space character between words (five characters per word) gives me 24750 minuscule* words per page. That's the entire Tetragrammaton Set printed on 18.5 pages.

Or is it? Its the English Tetragrammaton Set. The Hebrew Tetragrammaton Set would have been different - its unlikely that all the same consonants were used. The bigger question is what the Tetragrammaton Prime Set is - and that means finding out how many sounds are used - and usable- in human speech.

*Capital letters would be 0.026 inches high!
**I may misunderstand this rating: is it dots per linear inch, or dots per square inch?







'New from the Colonel! Chicken and tits!'

Today I got into an argument at work with a co-worker (to use the noun loosely) over ancient Hebrew diacritical marks, and how they applied to the Tetragrammaton*.
An argument which I think I won, for it ended with him screaming uncontrollably "Chicken and Tits!" over and over again.

This made me laugh for the better part of a day.
I cannot understand why he chose this phrase, but I am guessing that perhaps he read an article on the subject that used the example of 'Chicken' and 'Tits' as words that would encode the same without diacritical marks?
Its really the only answer I can think of.

*This chap believed that all four letter words** were names of God. I suspect he never read the 'Nine Billion Names of God' story by Arthur C. Clarke.

** I wanted to print out the list and bring it to work until RenegadeMime pointed out the list would contain 67215243521100939264000000 'words'. Factorials defy intuition.
"The Dead have no motivation"
Kai's sulky refrain from season two of Lexx ran endlessly through my head for the last two weeks as I battled a virus. Two virii, actually, and the second infection was my own fault.
The first one hit my while I cruised a wine-making forum: a TDS variant made itself at home and proved unwilling to vacate. I was running Avira Antivir at the time, an anti virus that up until that moment, I had been perfectly satisfied with.
No problem : everything was backed up, and I needed to reinstall the system anyways. It was a five year old XP Home, SP1 system that I was too damn lazy to setup fresh.
Re-installation was a snap.
Two hours later I was installing the last of my regularly used programs, when I had a lapse into idiocy and stuck an infected thumb drive into the nearest USB port.
Seeing as I was still shaking out bugs, I hadn't turned off the Autorun utility.
I watched in horror as a flutter of shortcuts appeared. Virus 2 installed itself:
W32.Ramnit.
Avira did nothing.
Now I could tell something was going on as my Google results were being redirected, so the fact that Avira said that everything was okay did nothing to help.
Some poking around with msconfig and similar tools led me to a respawning executable:
c:\program files\microsoft\watermark.exe
"Watson, the game's afoot!"
Several tedious hours later, I also uncovered
c:windows\system32\ssmypics.scr
c:\documents and settings\Robert\Local Settings\Temp\tmp\crypt_killexe.exe C:\windows\explorersrv.exe
The screen-saver was a cute touch: when I listed a directory with a screen-saver in it, WinXP runs the screen-saver in order t display the screen-saver's output as the associated icon.
So I had to use a terminal to delete it, and anyways, it kept getting respawned.
Time for more scanners:
Ad-Aware SE could not find it.
Emsisoft HiJackFree couldn't find it.
Clam AV could find it, but became infected itself, and could not remove it.
Moon AV could not find it
Norman Malware Cleaner could not find it.
IS360 ignored it completely.
AdvancedSpywareRemover ignored it.

By this point, infected files exceeded 22,000
Finally:
1, I manually killed every process that seemed infected;
2, I ran OTL with a configuration file for W32.Alureon ( I have no idea if this proved useful);
3, I ran ATF-Cleaner, and wiped everything I could;
4. I ran ESET online virus-scanner with phasers set to PARANOID.
This led me to:
C:\Documents and Settings\All Users\Documents\Server\hlp.dat
Of course, when I unlocked and deleted that, I got the Blue Screen.
No problemo - ran the WinXP Repair facility, and when everything came back up smiling,
installed the AVAST 30 day demo.
AVAST had no problem finding lurking copies of the virus and wiping them clean.
Half an hour more tracking down and killing infected files, and everything seems to be running smoothly.

If you Google a virus name and add terms like 'fix' or 'repair' or (even the pitiful) 'help', you'll get an endless round of forums bloated with HijackThis ( ! (Is the exclamation point mandatory?)) logs and endless lists of 'scan this, try that ' style instructions.
This post is not intended to add to that hideous panoply, but to serve as a bookmark to myself, a reminder of what I did to Fix It.

And of course, to boast: Me, myself and I - 1, w32.Ramnit - 0 .
Had a small amount of welding today, and as nothing went right , I can report two failures.
First: when out of welding rods for a simple stick welder, bare iron wire does NOT make a adequate substitute. Easy to melt the wire, easy to render the wire RED HOT so that it melts off the holder and falls onto, say , my pants.
Neither does nails.
Second: sprinkling on sand or potassium chloride does NOT make a useful substitute for flux.
That being said, the potash will vaporize, and its a little easier to strike a arc. But not easy enough to get the job done.

Turns out my welding rods were stored twenty-six kilometers away from where I thought they were.

Proper Previous Planning Prevents Pretty Poor Performance.