I have a 20 yr old craftsman 14" chainsaw in excellent condition. The problem I have is that it runs for about a second or 2 then stops. I brought it to sears to be repaired. After charging me an arm and a leg and supposedly working on the fuel line the saw still wont run. Anyone know how I can fix it?

-- hector g (hector@wabcmail.com), April 28, 2002

Answers

Take it back to Sears and raise h-ll. Their repair warranty is supposed to extend for a month or so. I just finished going thru that with a old Craftsman mower. Older Sears chainsaws were sometimes made by Echo/Poulan. See if you have a good small engine guy in your neighborhood.

-- Willis (wpoze@yahoo.com), April 28, 2002.

I asked my hubby this question, and he said to make sure you have no dirt in the fuel tank.

-- Laurean (cranston_06010@yahoo.com), April 28, 2002.

The problem is the crankseals, age is a dead giveaway. On a two stroke engine when the piston goes down it pressurizes the fuel/oil mixture, as the piston moves below the schavenger ports (those holes in the cylinder walls), if the seals are dried, cracked, or inadequate the fuel pressure exits the sides of the crankshaft, see the gunk accumulating at the ends of the crank, replace the crankseals by spliting the cases and taking the crank to a shop which has press ability. Acommon problem of the 1970's motorcycles. Nothing else will work until you reestablish crankcase fuel pressure

-- mitch hearn (moopups@citlink.net), April 28, 2002.

Sorry hector g, I just can't help myself.

A 20 yr old Craftsman chainsaw in EXCELLENT condition that stops after just a second or two.

My personal feelings of Sears.

It would be my thought to take it right back to the repair section of the store with receipt in hand, to show that it had been worked on and should be in good working order now.

-- Notforprint (Not@thekeyboard.com), April 29, 2002.

Long distance repairs are tough, but I would have to agree with crank seals being bad. You might be lucky and just have carb problems.

-- Emil in TN (eprisco@usit.net), April 29, 2002.