I have since tried several of the alternate ARM programs out there: MediaNet, JReceiver, rioplay, and there may have been one or two others. But I could never get any of them to work. I got close recently with JReceiver, but instructions that date back to 2003 do not account for today’s versions of the various components.

I decided to take another look at why some tracks don’t show up in the database. Forum postings indicate it should have no problem with ID3v2.x. All of my tracks have v2.3 and no v1.x tags. And most tracks are indexed fine. So I started reading about the history of ID3, the details of the different versions, and notable incompatibilities such as Windows Media Player 12 still won’t read v2.4 tags.

The text encoding available in ID3v2 made me think because I know of some programs can’t read a Unicode text file; it must stored in ANSI. So referred to my tag editing program, Tag & Rename, and there is a setting for enabling the writing of v2 tags in Unicode. But if a tag is in Unicode format, T&R doesn’t indicate this; only when a tag is rewritten will it use the appropriate format based on the setting.

I used a different tagging application, Kid3, to show which tags are in what format (down to individual tags in a track). I tested with a track and encoded all relevant fields (artist, title, album) in Unicode. When I indexed it in ARM, it didn’t show up. I used Kid3 to change the tags to ISO-8859-1, indexed again, and voila! I did further testing and determine that if you format, say, title in Unicode but the artist in ISO-8859-1, the artist will show up in the database, but not the song underneath the artist. So ARM still reads all the tags in a track; it is just those that are encoded in Unicode are not added to the database (the individual tags).

Since I am not trying to use international characters sets there is nothing really to be gained by storing in Unicode. I have asked the developer of T&R to add the ability to see what format a given tag is in (similar to Kid3), but in the meantime I have been rewriting my tags without the Unicode setting enabled as I check for album art in my tags.

One of the difficult parts to remove, if you haven’t done it before, is the clutch drum.  To do so, you need to remove spark plug and insert a screw driver into the combustion chamber to keep the piston from moving.  Then use a Torx 15 driver and insert it into the whole in the front of the drum.  Turn the driver counter-clockwise while holding the engine/chassis still to remove the screw holding the drum in place.

After you remove the springs holding the clutch together, loosen the clutch with a wrench and remove it.  Then you can remove the gray plastic cover that houses the starter string, pulley, and spring.  When you remove the pulley retaining parts, you can lift out the pulley.  You need to be careful when doing so because the spring will uncoil all over the place if you don’t reign it in while lifting the pulley out.

I slowly let the spring uncoil so I can work with the pulley.  Now you can replace the broken string.  The frustrating part for me at this point was keeping the spring in place while trying to attache the pulley.  After several failed attempts, I figured out a better way.  I was trying to mount the pulley with the string wound around it, which means that the spring has to be uncoiled a bit.  But this leads to the spring not wanting to remain flat when the pulley is being mounted on the shaft.  The better thing to do is to unwind the the starter string so it is fully extended.  You can then wind the spring as tight as it will go around the pulley (less one or two revolutions).

Even though the spring has more potential energy at this point, there is enough friction between each revolution of the spring that it makes it less prone to want to jump off the pulley.  I found it much easier to mount the pulley when the spring is wound tighter around it.

I hope this trick will help you if you need to replace the starter string on your Ryobi trimmer.

• dBlog – This offered some features I have been looking for, but the default locale is Italian.  There is a translation for English which changes titles and headers, but things like the calendar remain in Italian.  There isn’t a lot of documentation in English, so I was left to doing a lot of manual code search-and-replace.
• DotNetNuke - This is one of the primo open-source CMS solutions available.  It is an immensely powerful application that uses modules to offer the features you want: blog, document library, file library, ecommerce, forums, feeback, etc.  The application is geared for more commercial or multi-user sites, not a one-off blog, so the portal is a bit too much for what I am looking for.
• Nukedit - A solution ready to go pretty much right out of the box.  But it lacks some of the features that even simpleblog offers.
• WordPress - Probably the most popular blog software out there.  But it uses PHP and mySQL, whereas I prefer ASP and Access since I know how to write in VBScript.  I installed PHP and mySQL and tried to get WordPress working, but ultimately could not.

I have been using simpleblog 2.3 for awhile, and 2.2 before that.  Version 3 is available and after looking at it before all the others, I decided to look at it again.  It has the advantage that I am already familiar with the code that Johann has used for 2.x.  While it still lacks the features I have been looking for, I grew tired of trying all the other solutions.  So I have upgraded sidefumbling to simpleblog 3.0.

Pros:

• Very simple installation using ASP with VBScript and an MSAccess database.
• Built-in RSS feed.
• Version 3 adds a sidebar for recent posts.
• Version 3 uses FCKeditor for creating posts, which is a customizable WYSIWYG editor.
• Easy to integrate it into your site by editing ASP files and including your own scripts.
• Use of CSS for easy manipulation of global settings for font, layout, etc.

Cons:

• No use of categories or the ability to group/search for posts based on keywords.
• No search engine.
• No notification of pending comments.
• No use of CAPTCHA for comment spam-prevention.
• Difficult to use code blocks for using literal code in posts, though I have figured out in FCKeditor how to do this.
• Admin interface is limited to accessing previous posts by using calendar to access posts written on specific date, i.e., you cannot just browse a list of your posts for the one you one; you have to use the calendar to find the day you want and then bring up any posts for that single day only.
• Cross-browser support is limited, mostly by layout issues.
• No built-in way for posting from a mobile device, which is nice when traveling or making posts while at a conference, etc.
• Not regularly updated.

Despite the cons, I offer my thanks to Johann for creating a free solution that has obviously worked for me.