Putting Tire Sealant in Presta Valve Tubes

Share

I got a new bike earlier this summer (a Kona Dew Deluxe) and it’s a sort of cross between a mountain bike and a road bike. It uses the narrow 700 cm road tires and so I’m learning to deal with Presta valves whenever I need to inflate the tires. That requires putting an adapter on the valve stem since my air compressor is set up for much more common Schrader valves.
kona-dew-deluxe
One of the annoyances of bicycling on the Front Range of Colorado is the abundance of thorns called ‘goat heads‘. They will easily puncture bicycle tires. I learned this many years ago when I purchased my first bike in Colorado only to get two flats tires on the same day I took it for its first spin. When I returned to the bike shop, they asked if I had put TR tubes in it yet. TR tubes? “What are those and why didn’t you let me know about this when I bought the bike?” I was new to Colorado and never heard of TR tubes. “TR” stands for thorn resistant and their outside wall is about 4 times thicker than that of standard tubes and so the goat heads generally cannot penetrate in far into the tube wall enough to puncture it. After installing these tubes, I didn’t have any more problems with flat tires from the goat heads on my mountain bike.


However, with my new bike, despite putting TR tubes in it before leaving the bike shop, I’ve had several flats from goat heads. I guess it’s because the rubber on both the tire and the tube is thinner to begin with than standard 26″ mountain bike tires. So I needed another plan. I see a lot of Slime tube sealant for sale these days in bike shops, and I was wondering if there would be a way to get it into tubes that had these newfangled Presta valves since the cores didn’t appear to be removable. I looked on the Internet and found several websites that talked about a method of using cutters to clip off the last few threads on the part that holds on the nut you need to loosen to put air in Presta valves. This causes the threaded part to fall into the tube which allows enough room to put the Slime in the tire. Then you have to push the threaded part back up into the stem and secure it with the nut, which now has no locking thread to keep you from unscrewing it all the way. I was hoping that I would not have to do that. I found that I was in luck because my tubes had Presta valves that allowed me to remove their cores. If you look at the part of the valve that has the threads to hold the valve cap on and it has flats on it, then that means the core can be unscrewed.

presta-valve-1

This Presta valve above has flats on the threaded part that holds on the cap which means the core can be unscrewed from the valve stem.

presta-valve-2

presta-valve-3

In my case, I already had some Slime but my local bike shop guy, Mark at International Bike in Greeley, is a strong proponent of True Goo. He believes that this product is easier than Slime to put in the tire due to its lower viscosity and that it seals better too.

If you search on the Internet, you’ll see a lot of people telling you these tube sealants don’t work. I think the reason for this is that it’s still possible to get a flat even with tube sealant, especially if the hole is so big that the sealant comes out so fast it can’t solidify. Also, people are much more likely to post a rant about a product that let them down rather than to take the time to post a positive review. In addition, when tire sealant works, you don’t really have hard evidence to let you know that you would have gotten a flat if you didn’t have the sealant in the tube. So it’s hard to measure tube sealant’s effectiveness.

In my case, I had the perfect experiment. My rear tire’s tube was losing nearly all its air every 2 days. It meant that each time I wanted to go for a ride, I needed to put air in the tire. I had debated on whether to patch or replace the tube, but then I realized that it would be a great experiment to see for myself whether tire sealant actually works, especially on slow leaks, which are the kind you generally get from the tiny holes that goat heads put in the tubes.

In order to put the sealant in the tire, my bicycle guy gave me some good advice. The rubber transfer tube that comes with these sealants is sized to be a press-fit on Shrader valves, which is much too large in diameter to seal on Presta valve stems. However, if you gradually cut the top of the cone-shaped nozzle until it is a press-fit for a .22 caliber cartridge, it will also be a press fit on a Presta valve which is about .235″ in diameter. You can also use the .22 bullet as a cap because the red cap that is included with it will no longer fit after you cut that much of the tip off the nozzle. You can use a spent .22 caliber casing or something else that is similar in diameter if you’re worried about using live ammunition to seal the bottle. Here’s a picture of what it looks like:

True Goo tire sealant

True Goo tire sealant

If your Presta valve has a removable core, you can even put the sealant in when the tire is on the bike. Just rotate the valve to the top, insert the nozzle on the valve stem, and rotate it back around to the bottom. Squeeze in about 3 ounces of fluid, rotate back to the top, remove the bottle. Then replace the valve core and fill it with air.

I found that my tire that leaked down every 2 days consistently has now held its pressure for several weeks, which leads me to believe that this stuff actually works as advertised.

The Sun Also Sets

Share

Sun Microsystems has always intrigued me. For a number of years, it seemed as if the company could do no wrong. During the early 1990’s, Sun occupied the top position in high performance computer workstations, a category of computing that has since virtually disappeared thanks to advances in PC hardware. Despite desperate attempts to unseat it from its leadership position by worthy competitors like HP, DEC, and IBM, Sun was able to prevail.

If you had purchased Sun stock in May of 1994, you’d have seen it skyrocket to nearly 100 times its value by August of 2000, just 6 years later. Had you kept it at the historical high price of $253/share, you’d have seen your investment lose more than 98% of its value when it came back down to just $3.17 a share by October 2008.

SUNW/JAVA stock price meteoric rise and fall

SUNW/JAVA stock price meteoric 100x rise and fall


Sun has always been a leader and innovator. As the workstation market was overtaken by PCs running Windows, Sun became an exceptionally strong competitor in the server market. In 1999, Sun was riding high and looked to be unstoppable. The company was getting lots of positive press about its new language called Java which sought to be the long awaited ‘write once, run anywhere’ computer language. Presumably, it would be the last computer language that a developer would ever need to learn.

Java had an incredible amount of hype surrounding it. Something that would relegate the Microsoft Windows operating system into a well-deserved irrelevance had finally arrived. No longer would all the popular desktop programs be forced to use Microsoft’s proprietary OS. Instead, applications could be written in Java and run equally well on a Mac, a PC, or any number of Unix-derived operating systems. It was a simple matter of providing a run time environment for each computing platform. That run time environment became known as the Java Virtual Machine (JVM). If you have an orange coffee cup in your systray that always seems to be begging for an update, then that is an indication that you have a Java Virtual Machine on your PC.

The JVM looking for an update

The JVM looking for an update

For a while, many websites required the JVM to work properly, but lately I’ve noticed it has become much less necessary. And very few commercial desktop programs require a JVM. Whenever I install a new Windows OS, I can sometimes go for months before realizing I haven’t downloaded Sun’s JVM.

The Java programming language should not to be confused with JavaScript which is a completely different language used primarily in web browsers which was developed independently of the Java programming language. JavaScript was developed by Netscape and was originally called LiveScript. When the folks at Netscape saw the positive response Java was enjoying back in 1996, they made a cross-marketing agreement with Sun to rename LiveScript to JavaScript to tap into Java’s significant cachet. Netscape agreed to promote the Java language in exchange.

Despite all the hopes and dreams of Sun and enthusiastic Java developers, this ‘write once, run anywhere’ promise never achieved its potential. Today it looks even less likely that Java will unseat Windows from its hegemony on the PC. Apple has only recently managed to make some progress on the Windows desktop monopoly by finally breaking through single digit market share of installed base. Apple is now at 10% market share vs. Windows at 88.7% share according to a ComputerWorld report. But when it comes to desktop apps, Apple still relies on Microsoft to deliver the goods in the form of Office applications even for its Mac OS. I guess we’ll see if Google will have better luck than Apple in unseating Microsoft on the desktop with Google’s upcoming desktop OS and cloud computing approach to applications.

After Sun developed Java, it appeared to change directions. Sun seemed to be intoxicated with Java’s assured future success. This infatuation with a language that had failed to achieve its mission in any significant way 12 years after being introduced reached its zenith when Sun changed its stock symbol from SUNW to JAVA in 2007. I think it was Sun’s way of turning its back on its hardware roots in exchange for the promised fortunes of free software. For Sun’s market cap, the downhill slide continued despite the new stock symbol.

I had worked with Sun back in the late 1990’s and found that if you emailed Sun a Microsoft Word document it would be rejected along with a request that you to re-submit it in HTML format. I thought this was rather odd, since Microsoft’s Word was emerging as a defacto standard and surely someone at Sun should have been able to convert it to HTML. But then I found out that Sun employees didn’t have Windows computers and weren’t allowed to buy them. This was around the time that laptops running Windows were becoming indispensable business tools. Sun had acquired an insane hatred for all that emanated from Microsoft to the point where the use of its products was prohibited. In essence, Sun’s management had constructed a reality distortion field for itself and the rest of the company.

Sun acquired StarOffice in 1999. It later offered the software as a free open source “almost-compatible” alternative to Windows Office applications and called it OpenOffice. I’ve used OpenOffice which is the free version of StarOffice, but have found the applications lacking true compatibility. It feels like a product that was built without any apparent business model in mind, unless you consider a quixotic attempt to marginalize your archenemy’s revenue source to be a business model.

Sun had always been vertically integrated, supplying not only its own operating system, but also its own computing hardware all the way down to its Sparc CPU. Sun made some early tentative steps to get its Solaris OS to run on x86 CPUs, but the early efforts never really gained much traction, likely an indication that they were conflicted about making it work. Instead of figuring it out, Sun abandoned those efforts and continued to promote its Sparc architecture, and continues to offer Sparc-based hardware to this day. I believe it was this decision to try to do battle with not just Microsoft, but also with Intel, that furthered Sun’s problems. Sun entered into an alliance with AMD in 2004, but AMD has problems of its own, namely that it has to compete with Intel too. Finally, in 2007, Sun began working with Intel by adopting Xeon CPUs for its high-end servers. But I think it was too late at that point.

In 2004 Sun arrived at a legal settlement with Microsoft, claiming the company was exercising its monopoly position to ruin Java, earning it $1.95 B for its years of legal wrangling. However, I think the damage done to the relationship between the two companies was beyond repair. By the time of the settlement, Sun was hemorrhaging. Giving an ailing company that much cash is like giving it to a crack addict. They’ll only use it to go on a binge and, based on the sort of acquisitions made after that point in time, that’s exactly what happened.

Sun spent $1 billion to acquire MySQL in 2008, an open source database project that was no doubt starting to give Oracle and its competitors cause for concern because it was encroaching on the highly profitable database business. This acquisition did little to boost Sun’s prospects because MySQL really didn’t seem to fit in anywhere at Sun, and it’s hard to imagine there was any potential for revenue since MySQL was already open source and freely downloadable. Only about 1% of MySQL customers were paying for it. That sort of genie cannot be stuffed back in a bottle. To make matters worse, Sun was determined to move it upstream by improving its performance, furthering its threat to database companies who were still charging for their software.

By early 2009, Sun, having lost nearly 98% of its market value and suffering from years of losses or break-even results, was looking to be put out of its misery by being acquired by a rival. IBM appeared to be the front runner but in a surprise bid, Oracle came in and made an offer that Sun accepted instead. The deal is still pending some regulatory approvals.

What Oracle expects to achieve with Sun is anyone’s guess, but I think Oracle made the deal to get its hands on MySQL and to make sure it never becomes a competitive threat to its primary source of revenue. Despite claims to the contrary, Oracle has no need for Sun’s hardware business because it is no longer sufficiently differentiated from the competition. Sun’s software businesses have never made any money when one considers the cost of developing, supporting, and defending them. It’s just mystifying to me what Oracle’s Larry Ellison thinks he’s getting for $7.5 billion. I suppose if the company can be parted out, Ellison will be able to derail further development of MySQL, keep Sun’s $3 billion in cash, and sell off the rest of the company in an effort to recoup the remaining $4.5 billion. Oracle probably won’t risk entering the hardware business and thus alienating key allies like HP, Dell, and IBM when it comes to offering its database server on their hardware. My guess is that once the deal is approved and things quiet down, a fire sale for what’s left of Sun’s assets will ensue.

Sun was a formidable company in its heyday, and I’m sure there are still a lot of smart people there despite Bill Joy’s proclamation to the contrary, now known as Joy’s Law, that ‘most of the smartest people work for someone else’. That statement comes across with such a demoralizing thud that it’s hard to wrap one’s mind around its true meaning. Scott McNealy, Sun’s former President and CEO, known primarily for his sarcastic sound bites about Sun’s competitors and his periodic resurrections, has somehow been silenced. I don’t think he’ll be making a reappearance because Ellison is not the type of person who likes to be upstaged, as can be seen from the YouTube video below where he amuses the audience with his take on Cloud Computing.

Despite the multitudes of really smart people at Sun, its decline, fall, and consumption shows that no amount of technical brilliance can overcome bad decisions on the part of management.

Business Relationships vs. Hostage Situations

Share

I’ve been working with computers for a very long time, dating back to the time when you needed to use punched cards to program them. After graduating with several engineering degrees from Penn State, I went on to design computer peripherals for a major computer firm for many years. Because of my computer experience, my friends, most of whom are not computer experts, often use me as their first line of defense when they have a computer problem. And these days, “business is a boomin’.”

Part of the reason people have trouble with their PCs is because of the aggressive nature of companies trying to shove services down the throat of anyone who gets on the Internet. Not content to festoon what might otherwise be useful information with blinking banner ads, the new target of choice is the browser’s toolbar.

Last night I was helping my auto mechanic friend with his computer because it had lost his user profile, and Windows would let him log in but wouldn’t remember any of his desktop icons or save any of his browser’s bookmarks. He needs his computer to do his job as a mechanic since GM has moved all of its documentation on-line and without a computer, you just can’t function as an auto mechanic anymore. I know that sounds unbelievable but it’s true.

While I was adding a new user and copying his data over from his prior user’s settings, which seems to be the only way to fix a broken user profile on Windows, I noticed that his browser real estate had shrunk considerably since I first helped him to set up the computer. Why? It was because numerous toolbars had somehow managed to install themselves without my friend’s help. I suppose he may have helped a little but I can assure you it wasn’t intentional. I know this because his smile brightened more each time I managed to make one of them disappear. So in addition to fixing the main problem, namely the lost Windows profile, I also spent a lot of time cleaning up the computer.

Not only did I remove the offending toolbars, but I also removed all the miscellaneous links HP had included in his browser before he even set up the computer. He was too afraid to delete these items for fear he might break something. I call this stuff ‘crapware’, because it usually induces a customer to try crippled versions of programs or services which seek to get him to sign up for a perpetual subscription to an unnecessary service. And I should mention that the computer crawled along at a snail’s pace because of its heavy-handed virus protection software which his employer requires him to use, at his expense, of course.

I might have forgotten about this travesty and you’d not be reading it here, but then I got spammed by Sun today. I’ve been constructing an article in my head about Sun Microsystems which I will publish soon about how this once proud and capable company is now engaging in a desperate attempt to monetize the un-monetizable, namely Java, by using Java’s persistent need for updates as a trojan horse. I made sure to visit Sun’s CEO blog, written by the pony-tailed Jonathan Schwartz himself, just to make sure that was their plan. Sure enough, it was.

In my haste to quiet that little Java coffee cup by saying ‘yes’ to the update, it installed Carbonite’s crapware on my PC. Now, I’m no fan of on-line backup services and had previously written a critical review of what I think of them. Part of my view is colored by an image that I will now convey to you. Hang on, because I think you’ll like it. In any event, I can guarantee you won’t forget it.

A few years ago I witnessed a sales pitch for a service to provide on-line backup. I won’t mention the perpetrator, and you’ll never guess who it was because this idea was pitched by at least a million companies over the past few years and it’s one of those bad ideas that simply will not die. But during the presentation, the presenter took several opportunities to indoctrinate us, much like he was reciting a mantra, with this phrase:

“When you hold the customer’s data, you hold the customer.”

Along with this mantra, delivered with pregnant pauses both before and after, he used a hand gesture. Imagine holding an invisible tennis ball out in front of you at approximately waist level, palm pointed upward. The image is that of grasping and squeezing a person’s unmentionables. Wow! I think I knew where he was going with this. It wasn’t a business relationship he was proposing, it was a hostage situation.

Thanks, but no thanks. I’d prefer not to get involved in that kind of thing.

Yet it is precisely this kind of desperate business model that gets investors all worked up these days. No longer can you propose to provide a useful and valuable service for which people are willing to pay. Instead you must trick them into accepting something (often something offered for ‘free’) and then force them to become some sort of stooge, paying you perpetually for your right to continually abuse them.

I can only hope that this nonsense fades into oblivion, because I don’t want to live in a world where every business relationship requires duplicity and, eventually, larceny.

The next time someone is proposing to give you something that sounds like it’s for free, grab your wallet and anything else you’d like to hang on to and run in the opposite direction, because if you don’t, your valuables will soon be in the possession of someone who may not treat them with the same respect that you have for them.

Backing up a WordPress Blog on GoDaddy

Share

Blogging is a great way to prepare content for the Internet without spending a lot of time worrying about the details of website administration and content formatting. But it’s easier to put content in a blog than it is to get it out of the blog for backup purposes. WordPress has a way to export the postings and comments into an XML file for local storage, but since you have to remember to do it periodically, you’re likely to lose a few postings if something goes awry on the server and you haven’t done a backup for a while. And the XML export doesn’t save the images you may have uploaded to your web host because those are not stored in the same database as the posts and comments.

I started looking around for a WordPress backup solution and was unable to find anything that looked like a good fit. WordPress posts and comments are not located on your GoDaddy web host. They are on a separate host/database that GoDaddy sets up when you install WordPress as an application. I download my website’s changed files to my local PC using a scheduled WS-FTP session. I generally use FileZilla for FTP and would like to use it instead of WS-FTP, but it doesn’t have a way to automate periodic downloads so I’m forced to use WS-FTP for my backups. WS-FTP isn’t free, but until FileZilla supports recurring automated scheduling of uploads/downloads, it’s the only way I know to do this. The FTP backup takes care of downloading my blog images and other website files but not the actual blog postings or comments.

GoDaddy has a web interface to set up cron jobs and I was pretty sure I could back up my blog’s database to the same WordPress directory that stores my blog’s theme and php files using a script to dump the database. A database dump could put a copy of the postings and comments in SQL format in a location where my WS-FTP job could find it and download it on a regular basis.

I figured others would like to know how to do this, so I’ve written up a short ‘how to’ here.

I will assume you have are using GoDaddy’s Linux hosting and have an SSH login and know your way around a Linux system. If not, you’ll need some help from a Linux expert who can understand the instructions below.

First of all, you can use a single command to perform the WordPress database backup manually, to make sure it’s working. Here is an example of mine which I store in a file called “wpbackup” located in the wordpress directory (please note, this command should all be on a single line):

mysqldump --add-drop-table -h mysqlhostname -u mysqlusername -pmysqlpassword mysqldatabasename | gzip -c > $HOME/html/wordpress/yourblogbackup.sql.gz

If you can’t remember the mysql hostname, username, password, and databasename because GoDaddy generates them for you automatically when you install WordPress as an application, you can find them all in the /wordpress/wp-config.php file. Please note that there is no space between the -p and the password. All other spaces are required. The mysqldump command takes all the data from your wordpress blog database and puts it in a SQL format that allows you to re-import it should the need arise. The “| gzip -c” compresses the database since SQL is made of plain text and it compresses pretty well, probably 4:1 or better. If you don’t want to use it, you can leave it out.

You will need to confirm that this is working properly. Just make sure it’s executable and type in “./wpbackup” to run it. Then you can do a “gzip -d” on the yourblogbackup.sql.gz file to turn it back into sql statements so you can browse the contents of the output file. Once you’re sure it’s working, then you are ready to set up the cron job. It is possible set up a cron job manually by editing the crontab file in your home directory, but GoDaddy has a web interface that allows you to set up and manage cron jobs without having to know how to edit the crontab file directly. You can see the result in the crontab file by looking at it in your home directory after you set it up if you’re curious.

Just go to the Hosting Control Center -> Content -> Cron Manager

Set up the job to make the wpbackup script execute on a regular basis. It should be done frequently enough to insure that your FTP download is getting a recent backup of the database.

With the cron job executing on a regular basis, and a scheduled FTP download of your website, the most recent content from your blog will get backed up so that should misfortune strike, you’ll be able to restore it to its original condition. The two commands to do that are:

gzip -d yourblogbackup.sql.gz
mysql -h mysqlhostserver -u mysqlusername -pmysqlpassword mysqldatabasename < yourblogbackup.sql

(please note, the mysql command should be all on one line)

If you found a better or easier way to backup your WordPress blog, please leave a comment with a link to your solution.
WP Starter Guide