Update on Progress with SFS Team-Knit Socks

SFS_TK_Heels1I knitted the heel and had about half of the gussets done on these socks when I decided that I did NOT like the way the picked up stitches for the gussets looked. They weren’t tight enough and appeared to have small holes along the picked up edge. Frustrating, VERY frustrating – especially since these socks must be knit to very high standards. I don’t know if the problem is the way I picked up the stitches – or if I pulled the yarn too tight. I have found that the Regia Stretch yarn used for these socks can be overstretched – it is a very stretchy yarn.

I put the socks in “time out” over the Christmas holidays – just too stressful to deal with them given all the other demands of the season. Last week, I pulled them out, put in lifelines at the instep and the end of the heel turn and then frogged them back to the point where I need to pick up the gusset stitches. 🙁

I plan to tackle the picking up of the gusset stitches this week, paying special attention to how the stitches form as they are picked up…and trying to avoid overstretching the yarn…I will let you know how it goes.

Related Post

Returning to Blog and FO: Clapotis ShawlReturning to Blog and FO: Clapotis Shawl

I have been away from blogging for about five months. There were a number of reasons for this. First, I just got busy with other things and didn’t seem to be able to find time to sit down and write any posts. And then, my knitting projects just didn’t seem to be getting finished — even though I was knitting. And then, my husband started on our remodeling project — which was/is my office. The remodeling will be worth it when it is done — but when it will be done doesn’t seem to be anytime soon. I now have my computer set up in the spare bedroom and I have retrieved a few skeins of yarn and patterns from the boxes I packed up several weeks ago — so I can knit. But heaven help me if I need to find any of my knitting books or any of my yarn stash! It’s all in boxes and plastic containers, stacked three deep and nearly to the ceiling in the garage. (So any future knitting projects are an excuse to go yarn shopping…) I’ll update you on the remodeling progress — here’s to hoping it’s done by the time I need to decorate for the Christmas holiday.

I do have a finished object! I have finished my Clapotis shawl.

Clapotis Shawl Clapotis shawl - full length

I haven’t blocked it yet. Blocking will have to wait until I have free floor space again (remodeling). Here are the details:

Pattern: Clapotis – free on Knitty.com
Yarn: Jaggerspun Zephyr (50% wool, 50% silk) Colorway: Teal Needles: U.S. 4 (3.5 mm)
Since this is a laceweight yarn, I knit 18 repeats of the straight rows to get the length I wanted.
Unblocked the shawl measures 17 inches wide by 62 inches long. It will be wider and longer after blocking.

It’s a lovely, soft shawl and I am very happy with the way it turned out. I liked the finished shawl so much, I cast-on another using Knit Picks Gloss from my stash. More about this WIP another time.

Lack of New PostsLack of New Posts

I apologize to those who read my little blog — I have not posted for some time due to computer issues.

About a month ago, my DH and I both got new HP Desktops with Windows 7 as the operating system. After making all the necessary file transfers, I got up and running and thought things were just dandy. The new desktop was much faster and I loved my much larger monitor (great for these old eyes!). Then, about two weeks ago, funky random things started happening as I was using my new PC. Things like the screen just freezing up — which caused me to go to Task Manager and force the “not responding” program to close. Over the next several days, this went to happening at weird random and unpredictable intervals to happening almost every time I went on to the Internet. And then, it also started happening when I was in other programs — including the game Solitare and even Word. And — it was getting so that Task Manager couldn’t shut down the “not responding” program — now, when it happened the entire PC locked up — and I do mean LOCKED UP! The only way out was to hold down the Power Button until the machine shut down….yep, a hard shut down.

So, last weekend I started researching this little problem. I had to use my iPad — ’cause my HP certainly wasn’t going to let me do any surfing on it. And I discovered that this is a KNOWN problem with Windows 7. I found lots of threads about this little issue — one of which had been going on in a forum for over two years. From this research, I gleaned a few helpful suggestions that I thought I might try. Now this surfing took me most of Saturday afternoon over the Memorial Day holiday. So Sunday, I decided to check out HP Technical Support and see if there was anything new or helpful about this problem. And you know what? HP had a technical article on this problem — along with a whole series of steps to follow to determine how best to fix this little issue.

Now — before anybody goes there — the first thing I did when this little problem popped up was to run my virus scanning software — I did a full scan of my hard drive. As we all know, a virus is the most likely cause of problems with your computer. My computer scan came up clean. No viruses.

So, what was the cause? It was most likely either a program I had recently installed or an update to Windows that had been automatically installed. The solution? Well, HP has a utility called “System Restore” that allows you to go back and “restore” your system to a point before that update — i.e. a time before the problem started happening. Full instructions for how to do this were given in the article. BUT — before I went forward with this, I decided to back up my files — and this took me most of Sunday afternoon. Then Monday I was able to go ahead and do the System Restore. I discovered that there had been an update to Windows just before I started experiencing my issue. So I took my system back to the point just before that update. Viola! No more freezing or locking up! Whew! problem solved.

Not sure what conclusion to draw from all of this. Clearly it is a known issue that can randomly occur with Windows 7 — but it doesn’t appear to be something that Microsoft has addressed at this point — even though it apparently has been happening to Windows 7 users since 2009. I find it interesting that HP has a solution for the problem in the form of a utility that allows you to restore the system back to a point before the problem started to happen.

Anyway — that’s my tale of woe. Now that I have a working PC, I can get to work and actually write a new post about my new vintage crochet pattern. Stop back in a couple of days — I should have the pattern ready and available.

WIP: Progress report on the ClapotisWIP: Progress report on the Clapotis

The clapotis scarf is knitting up nicely. I am now about 3/4 done with the straight row section. So far I have dropped 9 stitches and now have 9 ladders of varying length running diagonally to the edges.

Clapotis - Straight Row Section

The straight row section is supposed to be complete after 12 repeats of the 12 row pattern. However, the instructions also say that if you want to make your scarf longer, you simply knit more repeats of the straight row section. So, I when I finish three more repeats, I will need to decide if the scarf will be long enough, or if I need to add some more length. The 12 row pattern for the straight rows is really fairly easy to knit and it doesn’t take too long to complete one repeat. I am thinking that I’d like this scarf to be a little longer than the 55 inches stated in the pattern, but will see.

The scarf is really soft and has a nice drape. So far, I’m happy with how it’s knitting up.