Man, I hate Garmin right now.

I’ve been a huge Garmin fan, right from my first aviation GPS (a Garmin GPSMap 195), through other aviation GPSs, a nuvi in the car, a StreetMap app on my phone, right through to the Forerunner 301 that I liked so much I bought another one when it started acting strangely because they’d been discontinued and I knew I had to act fast before they disappeared. But when I went to Tarifa, I discovered that having an open USB port and salt water don’t go together well. When that Forerunner 301 died, I bought a Forerunner 310XT, which is the nearest equivalent.

The big plus for the 310XT are that it had a completely sealed case, and the big minus is that it follows the trend to more “watch-like” form factor so it doesn’t work as well mounted on the front of the kayak. The lack of a USB port means that to sync it to your computer you need to put a little wireless device in one of the USB ports on your computer. It also uses a more modern heart rate strap that uses the semi-standard ANT+ instead of the completely proprietary protocol they used in the strap for the 301. And thus my hate starts.

So far, I’ve discovered the following things that make me hate this horrible thing.

It takes forever to start showing my heart rate. With the 301, I could take the strap, lick the contacts, put it on, and then turn on the GPS, and it will sync and start showing your resting heart rate within a few minutes. With the 310XT, you can repeat those steps, and you can wait literally half an hour, and it won’t show your heart rate. Start exercising, though, and almost exactly 5 minutes later it will start showing your heart rate.

Syncing with my computer is a pain in the ass. I don’t know if this is because I’m using a Mac, every single time I want to sync with my computer, I have to:

  1. Restart Garmin ANT Agent
  2. Choose “Pair New Device” on Garmin ANT Agent
  3. Turn pairing back on on the 310XT because it will have turned itself off
  4. Wait several minutes for the wireless things to sync up

If I do any of these steps wrong, it will get into a state where Garmin ANT Agent is still searching for a new device and the 310XT is in “Data Transferring” mode, in which case you have to shut down both the device and the program and try again. Also, sometimes you’ll need to accept the pairing request on the device. Also, I can’t sync with both Garmin Connect (their web based tracking system) and Garmin Training Assistant (the desktop tracking system). Compare and contrast with the 301, where all I had to do was plug in the USB cable and then I could sync with both the web app and the desktop app in about 30 seconds flat.

Their tech support SUUUUUUCKS. Ok, so a while ago Garmin Connect said I should download a new program to replace Garmin ANT Agent called Garmin Express. So I did – but because I’m not an idiot, I didn’t remove Garmin ANT Agent. And good thing, because you go through Garmin Express and it pairs with your device (which is every bit as painful as with Garmin ANT Agent), starts downloading your data, and says “While we’re downloading, connect to Garmin Connect” and wants your userid and password. But then it gives an error:
Screen Shot 2014-03-04 at 11.20.00 Note that it says it’s “temporary”, but it’s been happening for a week. That’s not “temporary” in my book.

I wrote to Garmin’s tech support about this “temporary” problem, and the response I got back tells me how to pair my device (note that the message happens after you’ve paired), and tells me to click on an icon and choose something from an menu, but neither the icon nor the menu exist on this software. Which makes me wonder if the person answering my question read the part where I said I was on a Macintosh or the part where I gave the full text of the response I got, or the part where I said I got that *after* it paired and started downloading. So Garmin’s tech support isn’t exactly a reason to keep using Garmin.

So at this point, I’m looking to find either a device or an add on for my iPhone that does the following:

  1. Displays heart rate, speed, time, distance
  2. Has some training assistance like being able to set up interval workouts, but Garmin’s virtual training partner thing was kind of cool too.
  3. Mounts on the front of my kayak or the footstrap area of my surf ski
  4. Doesn’t die in salt water
  5. Syncs with some sort of training tracker, mapper, etc.
  6. Has a heart rate strap that doesn’t wait until you’re 5 minutes into your workout to start showing your heart rate.

Drive replacements…

So after my last post, I discovered that one of the two new 3Tb Western Digital drives is throwing SMART errors, as is one of the older 2Tb Seagate drives. Well, the new one is brand new, just a few weeks old, and the older 2Tb one is just under a year old, so it’s still under warranty, so time to test the two RMA processes side by side.

I put in both RMAs on the same day. I had some problems with the Seagate web site, but I didn’t make careful note of the details and I forget exactly what the problem was. In both cases, I opted for the “advanced replacement” service where they send you the replacement drive first, and then you use that box to send back the defective one. I don’t recall either of them offering a more expedited version of the service.

The WDC drive took a few days to arrive. When the WDC one arrived, there was an option on their web site to click a single link and buy a UPS shipping label with the return address and RMA number and stuff all pre-printed. Very nice. When I went to the WDC support site dashboard, it already showed the new drive’s serial number as registered to me, and it had removed the defective one from my list of registered drives. The only problem: the dashboard showed the warranty period on the replacement one as expiring in 5 months. That’s a bit odd. I put in a ticket to ask about it and they said that when the defective one arrives back, they’ll update the warranty period back out to three years. We’ll see.

The Seagate one took over a week to arrive. The replacement has a big “REFURBISHED” label on it. I guess it’s unreasonable to expect a new drive to replace a year old drive, but one can live in hope, right? They sent me an email with instructions for returning it, including helpfully putting the return address and order number on page 4 of a 7 page email and suggesting I print it out and use that as a “mailing label”. That email also told me that I’d opted for “Ground Advanced Replacement” and if I’d opted for “Advanced Replacement” instead I would have gotten 2 day shipping on my replacement and a pre-paid shipping label for the return, all for $9.95. I don’t recall ever being offered this, or if I was, i wasn’t told how it differed from the free service. Still, the order confirmation is probably the wrong time to tell you what you should have ordered instead. Anyway, I guess I’ll be trudging off to the UPS store to get this shipped tomorrow.

Ok, now I’ve told you why Western Digital rules and Seagate drools, I’ll tell you about my replacment experiences.

When the first drive arrived, I shut down my computer, yanked the bad drive, put in the new drive, and rebooted. I got a message asking me if I wanted to start the RAID in degraded mode, and I did. Everything started up perfectly. I did the parted and mdadm magic to make the partitions on the new /dev/sdb and get it into the RAID, and after everything rebuilt it was right as rain. The number of odd DMA errors appearing in /var/log/kern.log went down to zero.

When the second drive arrived, I attempted the exact same thing. I shut down, yanked the bad one, put in the new one, and powered it up, and it refused to boot. Uh oh. Carefully checked the serial number on the drive to make sure it was the defective one. Checked in the BIOS to see if it seeing all the drives. But when I booted, I never saw the message asking me if I wanted to boot with the degraded RAID, it just hung. Put the defective drive on a spare SATA controller and booted, and it booted fine. Hmmmm. Used the appropriate mdadm commands to fail and remove the defective drive, and add the new one to the RAID. Tried grub-install, and it gave a non-fatal error about a device named “null”, but when I attempted to boot without the defective drive, got a grub error about being unable to find bios-i386-pc or something like that. Tried booting from all 4 disks, and got the same error. So I booted with the defective drive still installed, and waited 24+ hours for the RAID to finish rebuilding. Once it finished, I was able to do a grub-install and it didn’t give that strange error, and afterwards I was able to boot with the defective drive safely back in its shipping box. Phew.

More upgrades

So back when I wrote this post, my system had 2 21″ 1080p monitors, and it had a pair of 500Gb drives and another pair of 1Tb drives. But I didn’t stand still.

Over time, I replaced one of those monitors with a 27″ WQHD IPS LED monitor. That’s a lot of letters, but the important thing is it is very big, and it has a lot of pixels, and it’s beautifully sharp. I had hoped when I got it that I’d be able to keep both of the 21″ monitors as well, because the motherboard has built-in HDMI and DisplayPort, but it appears that when you have an external graphics card the built-in graphics shut down. I may be wrong about that, but I never discovered a way to enable it.

A few weeks ago I decided to treat myself and bought a second video card (this time an nVidia GeForce GT 620) to go into the second PCIe slot. That took a bit of fiddling around until I discovered that I needed to enable “xinerama” on the nVidia Settings in order to get all three monitors so I could drag windows from one to the other and cut and paste from one to the other. Without that setting it was acting like I had the two original monitors that acted like they had before, and a third monitor that would have nothing to do with them. Interestingly enough, though, KDE’s keyboard settings will no longer work – I had to go into the xorg.conf file and manually add a setting to swap the control and caps lock key. It also doesn’t have the numlock key on by default any more, although I haven’t manually fixed that. There are some weird little graphic glitches, especially on the login screen.

I also replaced my lovely and clicky Unicomp keyboard, which I spilled Diet Coke on and was experiencing some odd behaviour, with a dasKeyboard Professional Model S. It has MX Blue switches, which means it has almost as good a feel as the Unicomp, but it’s not as noisy.

Over the intervening years, I’ve also upgraded the disks. I haven’t really needed more space (although I’m getting more profligate about keeping stuff I formerly would have deleted), but as disks get old I’ve replaced them with bigger ones. So I went from the 2×500 + 2x1Tb to

  • 2x1Tb + 2x2Tb
  • 2x2Tb + 2x2Tb

There might have been an intermediate step along the way I left out. In each case, I’ve used fdisk to put a single partition on each new disk (because although I could just add the raw device to a RAID, I’ve found that making a partition allows you to use it for booting later, and as disks age out I’ve made the second set of disks into the first one, etc.) Then I’ve made them into a RAID-1 using mdadm --create /dev/mdNNN --level=1 --raid-devices=2 /dev/sdc1 /dev/sdd1, then migrated everything off the old pair to the new pair using pvcreate /dev/mdNNN; vgextend lvm2 /dev/mdNNN; pvmove /dev/mdMMM; vgreduce lvm2 /dev/mdMMM Then I’ve made sure grub knows about the new disks using grub-install /dev/sda, and usually I’m good to go.

A couple of weeks ago, one of my 2Tb drives reported some SMART errors. Nothing bad enough to trigger an email report, but enough to turn an orange warning flag on munin (basically smartctl returns an error code of 192). I took the machine down and ran SEATOOLS and it found a couple of sector errors and offered to repair them. I repaired them, and everything was fine for a week or so and then the same thing happened. At that point I decided to buy new disks. But since 3Tb disks are now as cheap as 2Tb disks back when I bought them, I figure it’s time to upgrade. So I bought the 3Tb drives.

At first when they came, I pulled out one pair of 2Tb drives and checked the model numbers. They agreed with the model numbers that SEATOOLS had reported for the bad drives, so I put the new 3Tb drives in their place, and connected the old ones up to the “other” SATA cables, the ones that don’t correspond to a drive carrier where the disks just sit on the floor with the cables hanging out. I booted everything up, and went through the whole process – the pvmove is the worst part of it, because it takes a few hours. After it was done, I was looking at stuff and realized that the new 3Tb drives had only made a 2Tb RAID! Wish I’d noticed that before I’d done all the time consuming stuff. Turns out fdisk doesn’t support 3Tb drives, and it doesn’t give you any warning before it makes a 2Tb partition on your 3Tb drive. So I did the same commands in reverse to move all the content back off the new drives onto the old one. Then I used GNU parted instead of fdisk to create a gpt partitioned disks with one 3Tb partition each. Went through the hours of migration, and it wouldn’t boot. It would boot with the old disks hanging off the side, but not if I took them out. A bit of reading revealed that there was a problem with grub and gpt disks – you needed to create a first small partition for grub to install its image to, and then the second big partition to make the big RAID on. So off I went, migrating back, repartitioning, migrating forward. All in all, a lot of wasted hours spent on this.

But after all that work, the damn thing still wouldn’t boot. I could plug the old disks back in and boot, but as far as I could tell, the raid that included those two disks wasn’t used for anything – it wasn’t in pvdisplay, and I could mdadm --stop it and the system would keep going. But if I unplugged it, it wouldn’t boot – it would show the Grub prompt screen, tell me that it was unable to read /dev/fd0 (which is odd, because I don’t have a floppy), say it was unable to read lvm/lvm2-boot, and then throw me to the grub-rescue prompt which is utterly useless. But as long as I got those two drives plugged in, it was booting so who was I to complain?

I asked on askubuntu.com, and didn’t get any response. I asked on the ubuntu forums, and got a response from a moderator who said “I don’t know much about RAID and lvm”, but who then proceeded to assert about 7 different things that were completely untrue about RAID and lvm. He also demanded that I run this tool, “boot-repair”, which would magically cure everything. Except for a couple of problems:

  • The documentation for the tool says that you can start it “from the command line”, but what they really mean is that you can start it “from the command line” if you’re running in a graphical environment. It doesn’t work if you’re away from home and sshed in. Minor, but annoying.
  • It wants to destroy your existing mdadm setup and replace it with dmraid. That’s a big nope.
  • It sends a lot of information about your system to a pastebin file, without giving you any option to edit or update some of that before it shares it with the world. Hey, look at that, it dumped out some disk sectors that have an email on it!
  • After gratuitously mucking about with my system, it didn’t actually fix anything.

Oh, and when you write to the authors of the tool, as the tool itself recommends you do if it didn’t fix your problem, you get an email that basically demands you donate some money to them before they’ll look at your pastebin file.

I tried asking on G+ as well, but the only advice I got there was a suggestion that I give up trying to boot from the gpt drive and install an SSD to boot from.

Anyway, in order to diagnose some more, I tried booting from the Kubuntu 13.10 install disk, and trying the “Try” option to get a liveCD environment working. With the “old” disks not installed, I was able to assemble two RAID-1s, one 3Tb and one 2Tb. So far so good. But then I noticed something that made my heart sink – pvdisplay was showing the 3Tb drives, but it was listing the other pv as “missing”. I suddenly realized why I wasn’t able to boot after taking out what I thought was the older failing pair of disks – because I’d taken out the newer, non-failing pair. Because mdadm and lvm successfully insulate you from worrying about getting disks in the right place and the right order, I had assumed that because the pair I was migrating away from was showing up as /dev/sde1 and /dev/sdf1, that they were the ones that I had outside the disk caddies sitting on the ground. But in actual fact, the ones sitting on the ground were actually /dev/sdb1 and /dev/sdd1. I was fooled because device letters don’t map 1:1 with specific SATA cables on the motherboard, if you put in extra drives they might end up between the ones you had before. With a growing mixture of trepidation and excitement, I checked checked the part numbers as well as the model numbers on the 4 2Tb disks, and confirmed my mistake. I put the newer 2Tb drives back in the caddies, and removed the older 2Tb drives, and everything booted correctly. And God alone knows how many steps back things would have worked if I’d bothered to check these part numbers earlier. I probably wouldn’t have had to inadvertently post the contents of an old email on pastebin, that’s for sure.

As of right now, /dev/sda and /dev/sdb are 3Tb drives, and /dev/sdc and /dev/sdd are 2Tb drives, and now that I have an extra Tb to play with, I have to figure out how to allot it. I currently have no way of knowing whether the system is booting from /dev/sda or from /dev/sdc, and I’m also not 100% sure that the 2Tb pair that I removed are the ones that had the problems in the first place. I think I’ve got a few extended SEATOOLS sessions ahead of me.

Going out with a bang

The evening before our last day, Boyan had said he thought there wasn’t going to be much wind tomorrow, so we could work on our forward stroke. Frank’s back had been hurting in the double, so when we went into Tarifa for dinner he’d stopped at the ferry terminal and booked an excursion to Tangier for the day.

I dropped him off after an early breakfast and I was sitting in my usual place overlooking the ocean and using the hotel’s pathetic wifi when Kassie sent me a message saying that they were going to do a downwinder. I was confused – I didn’t know if she meant the group was doing one in the afternoon, or she had hooked up with the two english guys to do a downwinder in the morning, but then ten minutes later she looked up from her computer to realize that she’d been sitting right behind me all the time, and she came over to clarify. It turns out that she had come to the hotel in the morning because the group was just about to leave for an unprecedented morning downwinder and nobody had noticed that I was back from dropping off Frank already.

I got ready as quick as I could, and we all hopped into the van for the trip to Punta Paloma. It was Karen’s turn to paddle with us, and so we had the three Germans, one Swede, one Australia, one Canadian/American, and Boyan the Bulgarian. I have lost track of which person was in which boat at this time, but I do know that Kassie and I were in red stripe V8s.

We went out beyond the point and turned downwind. There was a strong set of waves coming from about our 7 or 8 o’clock and running offshore, and a weaker set coming from about our 4 or 5 o’clock. The current/tide was against us, which is the main difference about going in the morning instead of the afternoon, and that steepened and shortened both sets of waves. The set coming from the shore direction got weaker as we went on, and the set going towards the shore got stronger – because of this, and because we were going so far down the beach, we ended up being fairly far out to sea, far enough it have about a kilometer of time over a shoal or reef that made everything more choppy and confused.

The two uber athletic Germans ranged far ahead, while Karen and the younger of the three Germans held down the middle, and Kassie and I brought up the rear. Boyan ranged up and down the line trying to herd the cats and keep us together. For the middle couple of kilometers I was finding myself having to actually wait for Kassie, which made me think I was actually improving some, but those thoughts were dashed by the afternoon’s paddle where once again I spent most of the time bringing up the rear. No idea what the difference was – it might have been her, it might have been me, it might have been the conditions, it might have been the time of day. Maybe I should just stop trying to measure myself against everybody else and measure myself against myself. And on that yardstick, I think I have much to be happy about. I think I was doing better at catching waves in the big stuff, better at linking, and better at not getting a cockpit full of water than even I was a few days ago. Stuff that would have terrified me a year ago was downright fun, and stuff that was hard work on Monday was almost easy by Saturday.

I shouldn’t get cocky, though. I’m fully aware that even Lake Ontario can produce conditions that make these ones seem tame, and I’ve got much to learn and practice.

One technique that got a real workout in the morning was trying to pick the right wave when you’ve got two sets setting up interference patterns. Sometimes instead of waves, you’ve got pyramid shaped lumps forming and dissolving, and trying to find a lump that is going to push you in the right general direction, or push you in the wrong direction but give you the speed you need to catch one going in the right direction can be a frustrating and rewarding experience. At one point during the morning paddle I found myself stalled on top of he fourth wave in a row with the cockpit filling with water and I said “stop chasing the big ones, find some small waves and just enjoy the small push they give you for as long as it lasts”. That worked, and gave me both the rest and the speed I needed and I soon found myself on big waves again. Boyan would gather us together for short pep talks, which also helped you get out of the intense concentration on just the next wave, give you a chance to enjoy the view for a few seconds, and then refocus on the task at hand. Even when he broke you out of a nice streak of linked waves, it was a good idea.

Just before heading into shore, Boyan made us do a set of remounts. I haven’t done remounts in meter high waves in a while, and it’s a good skill to practice in a nice safe environment with the waves pushing you towards shore and a big group of people around. I kind of blew the first one, but the subsequent ones went well and I made sure to practice on my less good side. I gave a small tweak to my shoulder, but not so bad that I couldn’t paddle.

The afternoon’s downwinder was very similar. The tide and current were running with us, and the wind was a bit stronger, so the surf was a bit better, but the part on the reef was even rougher and more challenging. Again, the emphasis was on turning towards the next wave, especially when you were on one that was petering out and you could see one forming at an angle. We zigged and zagged, but generally progressed towards our destination, although at the end we found ourselves abeam the take out and several hundred meters off shore, necessitating a bit of paddling in beam seas. I’d anticipated this a bit and come more directly inland while the rest of the group did a wide arc – except the two irrepressible Germans who’d actually paddled past the take out and then back into the waves and current just for the extra exercise.

After two 12.5 km downwinders in one day, my shoulder was a bit sore, my left calf muscle was a bit cramped, my psoas muscles in my groin were stiff getting out of the boat, and my left knee was hinting at that stabby pain I sometimes get, and of course my hand was still a bit mangled. I was, for the only time, kind of glad that I was done paddling for a while. I was actually so tired that I didn’t even go to the hotel porch to use the wifi – I just laid down and tried to read until it was time to pick up Frank. And after dinner, only the briefest of checks of my email and Facebook, a quick dump of all available clothing into my fortunately oversized suitcase, and off to bed.

Of course in the morning all the pain is forgotten and I wish I was paddling again, but today is a full day of travel and no time to even look longingly at the boats on the trailer. Oh well, maybe I’ll be back some day.

Long Lake Long Boat Regatta

[dciframe]http://connect.garmin.com:80/activity/embed/379176254,465,548,0,auto,border:1px solid blue;align:left;[/dciframe]
Today was the race I thought about all the time I was rehabilitating my shoulder and losing weight. This was the real test if I was back or not. Ten miles, in the Adirondacks, with all the uncertainty of weather that might entail.

Yesterday, the forecast for today kind of sucked. Winds of up to 20 miles per hour, 80% probability of precipitation, and thunderstorm in the early afternoon. But this morning the forecast was quite improved – the rain was supposed to hold off until afternoon, and the wind was supposed to be lower. Well, one out of two aren’t bad – as start time approached it was clear that the skies were going to stay clear, but the wind was moderately strong whipping straight down the lake, with stronger gusts and building.

At the start, I lined up next to Roger Gocking with the idea of maybe trying to hold his wake – he’s always been faster than me, but I thought maybe with my improvements, I could hold him. But almost as soon as the start gun went off, Roger was fouled by some idiot in a guide boat. The guide boat guy put his oar right over Roger’s boat, and both of them had to stop dead. Honestly, guys, you know those things are slower than kayaks, and you’re not facing forwards, so you’ve got no right to be trying to mix it up with the kayaks on the front line. Line up behind us and wait your freaking turn. Roger is a better man than I am and didn’t yell at the guy, just proceeded to quietly untangle, but I needed a new strategy.

I latched onto Mike Littlejohn’s stern wake. He was going gang-busters. Jim M was ahead of us, as expected, and Todd F was coming up past us, but otherwise it was just us up front. Now in the past I’ve beaten Mike a few times, and he’s beaten me a few times. I don’t know what the difference is, except I know that he’s got two boats that he made himself and I can’t tell the difference between them, and one is unlimited class and one is touring class – and today he was in his unlimited class boat. But he’s also a big guy and his technique sucks, so I had an idea that maybe I could ride his wake on the way down, and then gap him at the turn, and extend my lead on the way back. Certainly that’s pretty much how it worked in 2010 – I increased my lead on everybody except Dave Wiltie into the wind on the way back, but I’d been on Wiltie’s stern wake then, and at this point there was nobody I could see likely to come through and drag me away from Mike.

My heart rate was really high – in the mid 160s. I didn’t think I could sustain that. By the 4 km mark, I was feeling it, and I wasn’t seeing any sign of weakness from Mike. The idea that he would fade and I’d be able to take the lead was kind of seaming like a pipe dream. And worse, the wind was coming hard from the right side, and my boat wanted to weathervane into the wind. I was wasting effort applying hard left rudder just to stay pointing straight ahead. I had a momentary bobble, and caught a glimpse over my shoulder and realized that Roger was caught up to us and riding my wake. That spurred me on a bit, and I tried to pass Mike. I was a little upwind, partly by choice, partly because my boat was weathervaning into the wind. Roger stayed on my wake, but I never managed to get more than half a boat length ahead of Mike. Even getting a better angle on the waves towards the turn bouy didn’t help.

But as I was cutting towards the turn bouy, I got a massive stroke of good luck – the war canoe “Dog Breath” came roaring by. At first, they clashed paddles with me and I said “Thanks, I really needed that” and one of them said sorry. But then I managed to get on their side wake. It was great – I had to sweep on the side towards them because I was getting sucked into them, but the speed was incredible. I put some serious distance into Roger and Mike. I yelled to the guys on Dog Breath “All is forgiven”. But we were close to the turn bouy and when they turned I couldn’t stay with them – I might have been able to if I was inside the turn, but I was on the outside. After the turn I tried to get onto one of their stern wakes, but it just wasn’t happening. And the wind was horrible – it was coming from the front, then from the side, then from the front. A couple of kilometers after the turn, there was an island and I was trying to get into the wind shadow of it as had Jim and Todd and the war canoe, but the weathervaning of my boat was making it really hard.

I eventually did it get into the wind shadow, but by the time I did, Mike and Roger were back on my tail, and soon afterwards Mike came up even with me, with Roger still on his tail. I still had the feeling I might be able to get past them in the end. The wind was now in our face, and it was strong. Some of the gusts were as strong as any I’ve ever encountered in the boat, and I had to switch to a low paddling style. But it was hard hard hard. Now it was all three of us side by side. I tried Mike’s side wake, I tried Roger’s side wake, I tried to get into the V between then, but nothing helped. Neither of them were showing any signs of fading, but I was. I was side by side with them with a kilometer to go, but in that last kilometer I fell off behind. By the end, Roger had a boat length on Mike, and Mike had a boat length on me.

Roger, Mike and I at the finish.
Roger, Mike and I at the finish.

It wasn’t as good as I’d hoped, but it was probably the best result I’ve had. I’ve never finished anywhere near Roger before, and he’s doesn’t look like he’s slowed down any. But I was disappointed not to beat Mike. He’s beaten me in the past, but I’ve also beaten him. I was hoping I’d get him this time. Oh well, maybe next year. I just wish I could find a solution to the weathervaning on this boat. It’s a good boat otherwise.