You’ll notice the line:

new-object System.Security.Cryptography.X509Certificates.X509Store "My","CurrentUser"

The “My” is the StoreName (AddressBook, AuthRoot, CertificateAuthority, Disallowed, My, Root, TrustedPeople, TrustedPublisher). See http://msdn.microsoft.com/en-us/library/system.security.cryptography.x509certificates.storename.aspx for more info.

“CurrentUser” is the StoreLocation with “CurrentUser” or “LocalMachine” the only two options at present. See http://msdn.microsoft.com/en-us/library/system.security.cryptography.x509certificates.storelocation.aspx for more info.

param
(
 [parameter(Mandatory=$true)][string]$certPattern
)
write-host "`nCertificate search pattern = '$certPattern'"
$store = new-object System.Security.Cryptography.X509Certificates.X509Store "My","CurrentUser"
$store.Open("ReadWrite")
$certs = $store.Certificates
foreach ($cert in $certs)
{
    if ($cert -like $certPattern)
    {
        write-host "Deleting: "$cert.Thumbprint $cert.Subject
        $store.Remove($cert)
    }
}
$store.Close()

Short summary: this is a fun, but tough ride!

RAMROD is Redmond Cycling Club’s premier riding event of the season. Far less “popular” (only in attendance) than the Flying Wheels ride in June, but holding far higher cache for riders who have completed it. Despite its fabled toughness, these days, it sells out every year, with a waiting list of disappointed riders. The parks department limits it to just 800 riders.

My friend Steve Hastings and I headed down to Enumclaw Wednesday evening. RAMROD is done on Thursdays. After dinner at Quiznos, we stopped off at QFC to pick up some breakfast supplies. Steve was fine with Balance bars and the like but I like to eat more substantial things. So we got some milk and I got myself some turkey sandwich meat. It’s convenient that the place we stayed at, King’s Value Inn, has a mini-fridge to store food. Oh, and we got some chocolate milk too. Twin Brook Creamery has some really good chocolate milk!

After we arrived at our motel and unpacked, I did some prep work getting things packed for the next morning and then did a little internet surfing before going to bed. I slept a bit fitfully. The bed was harder than I am used to and I think I was a little amped up for the next morning.

We woke up to the phone ringing (our wake-up alarm) at 0330. I took a quick shower to really wake up and ate a quick breakfast (milk, cereal that I brought with and the turkey sandwich meat). Packing got a bit hurried as we moved a bit slower than we should have. Our goal was to arrive at the starting point at 0430, but we didn’t leave until just after 0434. Fortunately, it’s only about 10 minutes to the Enumclaw High School (the start and end point of the ride) so we weren’t that late. However, arriving even 15 minutes later than normal (for Steve) meant that parking was much, much harder. We had to do some searching to find a spot to park!

We got set up and headed for the starting line, making a quick pit-stop. Hint: the lines are for the toilets and not the urinals, so be sure to check. Plus, there’s a 2nd set of bathrooms further down the hallway which had much, much shorter lines.

0511 we were at start line ready to go. Unfortunately, Steve discovered he had 2 left-hand gloves so he went back to car to see if he could find a right-hand glove. He didn’t find a biking glove but did find a weightlifting glove so he was OK.

At 0516 we departed. There wasn’t much need for headlights after about 20 minutes as it started to get light pretty quickly. We paced behind a few different pacelines as we rode. We made good time, though I was trying to not to push too hard. I had a long ride ahead of me.

0632 @ mile 22.5, we did a quick stop at a port-o-potty at a Texaco in Kapowsin. While there we switched to dark lenses. The sun was clearly up and though there were some clouds it was getting bright quickly. We were back on the road at 0644.

We arrived at the Eatonville rest stop, the first official rest stop of the ride at 0721 @ 32.7 miles. There was a good crowd at the stop. Too early to have everybody spread out yet. They had some rather good scones for food, but, oddly, they only had the scones. No jam, butter, peanut butter or anything else besides simple water. I ate 2 scones. Steve didn’t eat a whole one. He wanted some extra stuff on his scone so it wasn’t that appetizing to him.

We were at the rest stop for about 20 minutes, which wasn’t bad, but was a bit longer than I really wanted.

From Eatonville, the road was gradually uphill, with occasional downhills thrown in. We were getting closer to Mt. Rainier park. The sun was up and the skies were clear and sunny but not too hot. It was a scenic ride. I was feeling good, even though we were mostly chugging up a gradual slope, but Steve was suffering. He still hadn’t recovered completely from his gall bladder surgery (and subsequent lack of training), so the mild grind uphill was getting to him and, in retrospect, I think his lack of eating hurt him too. Even if I’m not hungry, I force myself to eat and drink on a regular schedule. That helps me a great deal as it tends to prevent bonking (fairly easily solved by slamming a few gels) and dehydration (much more serious as it is hard to catch up once dehydrated).

We hit the Ashford Valley Grocery Store at 0902 @ mile 52.40, to avoid the official rest stop a few miles further up the road. Steve thinks it saves us time, but honestly, I think it’s a wash by the time you add in the lack of parallelism – we need to leave one person behind to watch the bikes when we buy supplies and go to the bathroom vs. both of us going for food and port-o-potties simultaneously at the official rest stops (better lines of sight to the bikes if nothing else).

We departed at 0930, so a 28 minute stop. Again, not ideal but this early in the ride, I didn’t stiffen up that quick. On STP, we had a couple of 40 minute breaks that just killed me from getting too cooled off. 29 minutes later (0959 @ mile 58.81), we rolled through the Mt. Rainier Park entrance! At that point, according to Steve (I didn’t check my watch) we had some 2400 feet of climbing already done! From there, the climbing began in earnest. For the next 65 minutes we climbed and climbed. At mile 65.15, we took a quick, 10 minute break at Longmire Inn. We’d covered 6.3 miles in 65 minutes, so you can see our average speed was around 6 miles an hour. Partly this was due to Steve not being 100%. I could have ridden a little faster but maybe a mile per hour faster max.

After Longmire Inn, we spent the next 75 minutes climbing up to Inspiration Point (just past the Paradise entrance). There’s a point where you’re riding and off to your right you see faster cyclists riding along the road several hundred feet above you. It’s slightly discouraging. I heard a few people groan when they realized how much more climbing there was. However, what the 1st timers don’t realize is that the next rest stop is right there too, so in the end, it wasn’t so bad.

We hit the Inspiration Point rest stop at 1203 @ mile 74.75). I felt good and was glad to have completed the climb of the first pass! We were there for about 20 minutes resting and admiring the sights before having the fun downhill section to the 2nd food stop: Box Canyon (1239 @ mile 82.43). It took 17 minutes to go 7.68 miles (avg. speed 27.1 miles per hour!). On the way down you have to be careful not to admire the scenery too much because it’s quite spectacular. I never notice on the way up – I’m too busy pedaling!

The food selection at Box Canyon was much better than the Eatonville stop. Fruit, potatoes, bagels with peanut butter, some rather dry cookies, and chocolate croissants (Steve’s particular favorite). While there, I noticed one young woman had a RAGNAR relay temporary tattoo on her arm. I asked if she’d done the relay (which was Friday – Saturday – just 5 days prior!) and she said yes, having run the equivalent of a marathon! Very impressive!

It seemed like we were there for a while, but looking at my log, we were at the rest stop for only 21 minutes! We left at 1300.

From Box Canyon, you climb for 3 miles to the top of Backbone Ridge. Even though it’s fairly steep, Backbone is sort of a bump in the road in comparison to what we’d just climbed. It took about 30 minutes to get to the top (I don’t have precise numbers for when we hit the peak). Then you have another fun downhill section. Again, you are greeted with some spectacular scenery though you can’t enjoy it too much as you have to watch the road!

1339 @ mile 93.07, we were at the bottom. We stopped at the Grove of the Patriarchs for a quick (11 minute) bathroom break. It’s less than a 1/2 mile to where you hit Hwy 123, which leads you to Cayuse pass.

Things start out nice enough. There’s lots of shady trees and the slope is very modest. And then, imperceptibly, the slope gets steeper and the trees start to get less shady. After a couple of miles you are on the real climb to Cayuse. This is the challenging pass! You’re 95, 96 miles into your ride, you have some 6000 feet of climbing on your legs, and you’re starting to hit the heat of the day and you have no shade. We were super-lucky this year. The heat was extremely modest. A few years ago, temps were pushing >90 degrees, which must have been withering on this climb!

But the worst thing about the Cayuse Pass climb is its unrelenting nature. On most climbs, the slope increases, it decreases, it often even has (short) flat spots in it where you get a few moments to recover. Not on this climb! You set a grade and that’s it. For 9 miles! I chugged along at 6.1 miles an hour. Steve slowly fell behind so I tried not to go faster, though honestly, even had I been motivated, I could have only managed maybe 0.2 – 0.3 miles per hour faster. I found that going slower than 6 was actually harder for me than going 6 so I hoped Steve wouldn’t try to kill himself keeping up with me! Turns out he didn’t. In fact, he was starting to feel better – he was drinking more and his side-stitch from his gall bladder surgery 7 weeks prior was no longer bothering him.

I arrived at the Deer Creek water stop at 1440 @ mile 100.28. Boy was I glad for the rest break! Plus I was getting a bit low on water. There was no food. Just water. In my notes at this stop I wrote, “Cayuse is a bitch. Unrelenting hill. And long!”

I overheard the volunteers talking to one of the riders. The first rider arrived at Deer Creek around 1130! 3 hours ahead of Steve and I!

From Deer Creek, you still have 4 miles to the top. That doesn’t sound like much until you do the math and realize that 4 miles at 6 miles an hour is 40 minutes! Ugh! We departed the rest stop at 1453 (13 minute stop) and started our grind uphill. The rest break gives you a temporary burst of energy but then you quickly run out of steam. I really watched my odometer on this, counting down the distance and hoping that it really was 4 miles and not like 4.5 miles! I started to fade a bit and my 6.1 dropped down to 5.8 miles per hour.

I reached the top of Cayuse Pass at 1534 @ mile 104.34. So it was actually 4.06 miles, darn close to 4 miles! I was very happy to reach the top! They have a nice water stop at the top. My legs were a bit rubbery and I was feeling a little shaky. I ate some food and drank water waiting for Steve to arrive. Given how hard it was for me, I was a little worried about him. He showed up just a few minutes later and though tired said things went well and he felt OK.

Ride tip: Don’t spend too long at the Cayuse Pass stop. There’s food only 15 – 20 minutes away! Drink some water, eat a gel, enjoy the scenery and head out! You can rest on the way down! We burned up 20 minutes at the stop, only to stop again for another 27 minutes just 15 minutes later!

We departed at 1555 (21 minutes) and had a fast, fun coast down to the last official food stop. They warned of rough roads and to not go too fast, but actually there was only about ½ mile of bad road and they actually took the time to mark the big road hazards so you could see them! The rest was as good as any other downhill section I’d ridden.

I arrived at the Crystal Mountain lunch break [Deli Food Stop] at 1611 @ 112.61 (avg. 31.0 mph!) On the way down, my stomach started growling! I was hungry!! At the rest stop, I totally pigged out. I had a sandwich, a large bunch of grapes, a cookie, some other fruit, and multiple piles of potato chips. It was probably the potato chips that did me in. When we left, my stomach didn’t feel too good! Not like I was going to throw up or anything but just way too full! I wrote in my log, “I am going to be waddling the rest of the way!”

We left at 1648 (27 minutes – a bit too long for my taste) and enjoyed more downhill. As we got lower, the fabled headwinds began to make themselves felt. Steve says they were better this year than in past years. I’ll have to take his word for it! I pulled Steve for a while and then Steve took over and pulled for a while. My stomach didn’t feel very good so I couldn’t work as hard as I would have liked to. It was pretty amazing drafting though. Thanks to the headwinds and the moderate downhill slope, Steve was pedaling away and I was literally coasting, hitting my brakes to slow down! Never had that happen before!

Around mile 126 is the last stop: Greenwater. [Updated - The Deli Stop is the last official stop. Greenwater is a non-official, though popular, stop. Thanks Steve!] Though I “kinda sorta” needed to use the bathroom, I was feeling good overall (all that food was beginning to hit my bloodstream and I no longer felt bloated to boot!), we were making such good time, I had plenty of food and water left and Steve felt good too so we passed the Greenwater stop like our hair was on fire. Even with the headwinds, we’d been averaging 18 or 19 miles an hour and often were hitting 20+ on the steeper sections. It is almost literally all downhill from Cayuse to Enumclaw! Which is handy considering the headwinds! We had a guy drafting behind us for about 30 minutes but he dropped at the Deli Food Stop. Then we had something very fortuitous happen to us as we passed the stop. Just ahead was a small 4-person paceline. We caught up with them in short order, and settled in behind them. They were going a little slower than what we had been going, but it gave both of us a chance to rest. In the end, we were behind them for nearly an hour!

Turns out, we were thinking the same thing:  though we could have ridden faster than they were riding, with just 2 of us, it was unlikely we could have maintained the pace we’d been riding for the 80-90 minutes that it would have taken to finish the ride. So we just waited and rested. We both were prepared to pull, but some pacelines are suspicious of straphangers like us, so they cycled amongst the 3 male riders. The lone woman was apparently not feeling that strong because at one point, she was 2nd rider and actually dropped back to be the constant 4th rider. The slight increase in wind from being in 2nd place was wearing her out.

When we hit SE Mud Mountain Road (about 7 miles from the finish line) the paceline suddenly broke up. Since I was feeling pretty fresh (thanks to the long pull we’d gotten from the defunct paceline), and even moreso, motivated by really needing to go to the bathroom, I turned on the afterburners. We cranked along at a good clip. Mud Mountain road contains the last downhill section which I used as best I could (it’s a little rough with some sharp turns). After than you’re talking flat ground the rest of the way!

On the flats, I looked at my watch. We might be able to finish before 1840, which is the best arrival time Steve & Denise ever did! So now I was doubly motivated! I pulled hard! About ½ mile out, Steve suggested that we slow down and take it easy to “cool down” for the finish line. I was having none of that! So he followed me in as fast as I could pedal.

We arrived at 1841. I had 148.69 miles on my odometer. Steve’s best time ever! This was my first one so if I’d finished it would have been my best time ever!

I was glad to be done, but even with that last ½ hour sprint in me, I didn’t feel too bad (especially after visiting the bathroom!) We enjoyed being lazy and I got an ice cream sandwich and bought a ride picture of myself (with Steve chugging along in the background!). Eventually, we packed up our bikes, and headed to Quiznos for dinner and then I got to relax while Steve drove us back to his place! Thanks Steve!

It’s funny. Right after finishing, I was thinking, “Wow, I don’t know if I’d want to do this every year, that was a tough ride!” But now that I’ve had 3 or 4 days to forget how tired I was, I would totally do it next year!

private void MyFunction (string blah, params string[] lotsOfPossibleBlah) ...

I had a powershell script that I wanted to extend with similar behavior. I wanted a couple of required parameters and then allow user to call with a unlimited list of optional parameters.

However, once you specify a parameter attribute, Powershell complains if you try to add extra parameters. So, for example, this works:

param ($a, $b)

write-host a= $a b= $b xtras= $args

.\foo.ps1 1 2 3 4 
a= 1 b= 2 xtras= 3 4

This does NOT work:

param
(
    [parameter(Mandatory=$true)][string]$a,
    [parameter(Mandatory=$true)][string]$b
)

write-host a= $a b= $b xtras= $args

.\foo.ps1 1 2 3 4
D:\foo.ps1 : A positional parameter cannot be found that accepts argument '3'.
At line:1 char:10
+ .\foo.ps1 <<<<  1 2 3 4 
    + CategoryInfo          : InvalidArgument: (:) [foo.ps1], ParameterBindingException
    + FullyQualifiedErrorId : PositionalParameterNotFound,foo.ps1

Argh. Very annoying. Nothing in the docs, ebooks, etc. that I’ve read mention this gotcha. Their examples just work because they don’t add any attributes to their parameter list. After an hour of poking around and prodding, I finally found a list of Powershell attributes you could add to a parameter (http://msdn.microsoft.com/en-us/library/ms714348(VS.85).aspx) which saved the day. It is the attribute ValueFromRemainingArguments. This tells the parameter to grab all the remaining arguments into an array, so you get behavior just like the $args param. In fact, you can name this paramer $args, though in the example below, I named it $xtras just so there would be no confusion about the actual origin of the values.

So now this works, and is exactly the behavior I wanted. 2 required parameters and an optional number of extra parameters.

param 
(
    [parameter(Mandatory=$true)][string]$a, 
    [parameter(Mandatory=$true)][string]$b,
    [parameter(ValueFromRemainingArguments=$true)]$xtras
)

write-host a= $a b= $b xtras= $xtras

.\foo.ps1 1 2 3 4 
a= 1 b= 2 xtras= 3 4

For 3 years, Sam has been alone with just a robot, GERTY, for company. Sam is getting a bit restless to get back to his wife and child after the end of his 3 year contract. Unfortunately, while checking up on one of the robotic mining units, he has an accident. To say more would ruin the story, though I have to say I knew the basic plot outline before seeing it and I still greatly enjoyed it.

This movie is good in part because it so unusual. There are no aliens and for the most part, no super-futuristic technology (with 1 exception). This is a movie where technology serves the characters and not the other way around. And I thought it was well-written. The plot is quite intriguing and makes you think. You don’t get spoon-fed with this one. There are no “reveals” to explain what is happening. What Sam sees is what you see. Actually there are maybe 2 scenes where this isn’t true but it’s at the end of the movie where it doesn’t matter. You can already figure out what is going to happen.

I also really liked the musical score of this movie.

This is what science fiction was really meant to be. An exploration/reflection of the human condition.

8/10

I imagine this movie was hard to pitch. “It’s a movie about trains (yawn). Only this one doesn’t have anybody on it! (OK… so what?) Only *this* train has a load full of dangerous chemicals! (Hmm… getting warmer…) And all attempts to stop it fail! (I guess that’s the ‘Unstoppable’ part…) except for Denzel Washington (Ah! Now we’re talking!) and his young sidekick played by Chris Pine (who?) – you know, the guy who was Captain Kirk on the new Star Trek movie (hmm… not sure if trains and spaceships have the same demographic… Nice, but still sounds boring…) We’ll we’re gonna do lots of shots of trains rumbling over the camera, and we’ll have close calls with head-ons with… other trains! And of course, we’ll have the train smashing things- but nothing big enough or heavy enough for it to derail! (Ooh! Smashing things. That’s sounding much better! … What about car chases? Everybody likes a good car chase!) Oh… well um… we’ve got that too! We have a guy who is chasing the train in big pickup truck! With a police escort! (So he’s gonna jump on the train and stop it?) Err… not exactly. He’s a welder. (A welder?) Yeah, but he works in the train maintenance department, so he… well he wants to stop the train really bad! (Why? Is a relative on board?) No. (Are his kids trapped on a bus sitting on the train tracks?) No. He just likes a challenge. (Oh…) Did I mention it’s got Denzel Washington? (Oh yeah? Sold!)

I’m sure it went exactly like that.

It may sound like I didn’t like the movie, but I did enjoy it. It was fun, if inconsequential. They did a good job with making things feel tense and making 70 miles per hour seem like it was fast. Do you need to see it in the theater? Probably not. One thing I was slightly disappointed by was that they didn’t play up the massively deep and powerful sounding diesel engines these trains have. Probably because most sound systems can’t do the sound justice.

It’s one of those movies that is quite enjoyable, eminently watchable but parts of it don’t really hold up under deep scrutiny. It’s a bit formulaic and clichéd on hindsight, but hides its pedestrian nature well. I’d definitely say it is worth renting. Even if you dont’ like trains I think you’ll be entertained.

6/10

myapp -setdbvalue "User %USERNAME% is on %COMPUTERNAME%."

So the string I want stored in the database is “User %USERNAME% is on %COMPUTERNAME%.”.

However, if you call the above, you would end up with a string like: “User KEVENKER is on KILOTWO.” Definitely NOT the intended value.

After about an hour of searching, I never found the definitive answer! However, I learned enough from reading http://stackoverflow.com posts and http://ss64.com/nt/ that I managed to come up with this solution:

myapp -setdbvalue "User "%"USERNAME% is on "%"COMPUTERNAME%."

So what happens here is that the cmd processer sees the following strings:

"User " + "%" + "USERNAME% is on " + "%" + "COMPUTERNAME%."

and simply concatenates these all together into one string when passing this argument to my program.

So there you have it. I hope this helps some hapless person. Hopefully the title will be good enough for searching. I’m sure this has been solved before but finding the solution is the hard part.

I wanted to generate a timestamp for naming files of the form yyyymmddhhmmss. The problem is that batch scripts don’t really support string formatting. You can get %date%, e.g. Thu 11/04/2010, and you can get %time%, e.g.  7:55:31.23. So you have to tease out the pieces manually, by using batch script’s “substring” abilities.

The only real “gotcha” is that the time doesn’t print a zero at the front of single digit times. So if you do something like:

you can end up with a string that looks like: “20101104 75531″, with that space in it, which is rather annoying. Not to mention that it breaks scripts unless you put quotes around everything.

Basically, you need to check to see if the first character in the time portion is a space and if it is, insert a 0 at the front and grab everything after the space. So the snippet I developed is:

PS – Sorry about the jacked up formatting. It seems WordPress is going through one of its periodic episodes where the editor decides to to whatever it feels like. The HTML mode no longer appears to actually let you edit HTML either, making things extra fun!!

Note that workingDirectory MUST be set to something valid if you run as a different user. Set to null if you want to run in current directory.

The reason for the lock() in GetOutput is that I want to create a function that outputs to one StringBuilder, not two. If you will always have two StringBuilders, then you can get rid of the lock.

I’m super-new to threads, so be kind for any obvious mistakes!

        public void RunShellCommand(

            string username

            , string domain

            , SecureString password

            , string workingDirectory

            , string command

            , out string stdOut

            , out string stdErr

            , out int exitCode

            , int timeoutSeconds)

        {

            string cmd = “/c” + command;

            string fileName = System.Environment.ExpandEnvironmentVariables(“%comspec%”);

            RunProcess(

                username

                , domain

                , password

                , workingDirectory

                , fileName

                , cmd

                , out stdOut

                , out stdErr

                , out exitCode

                , timeoutSeconds);

        }

        public void RunProcess(

            string username

            , string domain

            , SecureString password

            , string workingDirectory

            , string fileName

            , string arguments

            , out string stdOut

            , out string stdErr

            , out int exitCode

            , int timeoutSeconds)

        {

            Process p = new Process();

            p.StartInfo.FileName = fileName;

            p.StartInfo.Arguments = arguments;

            p.StartInfo.UseShellExecute = false;

            p.StartInfo.RedirectStandardOutput = true;

            p.StartInfo.RedirectStandardError = true;

            p.StartInfo.CreateNoWindow = true;

            p.StartInfo.WorkingDirectory = workingDirectory;

            if (!string.IsNullOrEmpty(username))

            {

                p.StartInfo.UserName = username;

                p.StartInfo.Domain = domain;

                p.StartInfo.Password = password;

            }

            StringBuilder sbOut = new StringBuilder();

            StringBuilder sbErr = new StringBuilder();

            List<object> lOut = new List<object>();

            List<object> lErr = new List<object>();

            p.Start();

            lOut.Add(p.StandardOutput);

            lOut.Add(sbOut);

            lErr.Add(p.StandardError);

            lErr.Add(sbErr);

            System.Threading.Thread outThread = new System.Threading.Thread(GetOutput);

            System.Threading.Thread errThread = new System.Threading.Thread(GetOutput);

            outThread.IsBackground = true;

            errThread.IsBackground = true;

            outThread.Start(lOut);

            errThread.Start(lErr);

            if (!p.WaitForExit(timeoutSeconds * 1000))

            {

                throw new ApplicationException(

                    string.Format(

                    “Executing {0} {1} timed out!”

                    , p.StartInfo.FileName

                    , p.StartInfo.Arguments));

            }

            // 

            // Wait for readers grab all data before closing streams.

            // Closing the stream before it has finished may cause data-loss and may 

            // cause an ObjectDisposedException on the thread but this is trapped. 

            //

            errThread.Join(timeoutSeconds * 1000);

            outThread.Join(timeoutSeconds * 1000);

            p.StandardError.Close();

            p.StandardOutput.Close();

            stdOut = sbOut.ToString();

            stdErr = sbErr.ToString();

            exitCode = p.ExitCode;

        }

        private void GetOutput(object parameters)

        {

            List<object> paramList = (List<object>)parameters;

            StreamReader sr = (StreamReader)paramList[0];

            StringBuilder sb = (StringBuilder)paramList[1];

            try

            {

                while (!sr.EndOfStream)

                {

                    string l = sr.ReadLine();

                    lock (sb)

                    {

                        sb.AppendLine(l);

                    }

                    Console.WriteLine(l);

                }

            }

            // ObjectDisposedException happens if we timeout and close the

            // stream before sr.EndOfStream is reached

            catch (ObjectDisposedException) { }        

        }

This article talks about they common myths surrounding learning new material.

• Vary the setting. Learn the same material in two different places.
• Vary your learning activities. When learning a language, for example, move between vocabulary, reading and speaking. A little bit of each seems to work better than all of one thing.
• Space out your study of a particular item. Study something one day, then a few days later, then maybe a week later. (there’s actually a guy who sells a computer program (SuperMemo) for this (http://www.wired.com/medtech/health/magazine/16-05/ff_wozniak)).
• Testing, even self-testing helps to remember material.

http://www.zerohedge.com/sites/default/files/Mackinac%20Great%20Depression.pdf

It’s a long read, but definitely worth your time.