Catherine, you are a very nice person to be able to respond to Catfish without losing your temper. He is not a nice person. He is rude and always looking for a fight. I have never seen him post on any thread without being insulting to someone. He cannot understand that because of that behavior, no one listens to him except other rude jerks. The only thing to be done is to complain to GW monitors and get him warned and then kicked out when he continues his diatribes. You can get a heat gun at Harbor Freight fairly cheap if you won't be using it a lot. They go on sale frequently. They cut out when they get too hot so don't be surprised that they need a rest in the middle of your repair. The more expensive ones do it as well. I have one of the Harbor Freight ones and a more expensive one and when one dies I just turn on the other. You may have a problem getting the crack cleaned out enough for any product to work. Let us know how your attempts work. Does the crack go all the way around the bottom? I have the same type of tank you do and I left the water in it all winter but it did not crack although I expected it to. I am wondering if it did not because I left the quilt batting on top. When I did pull the plug there was only a small amount of water left in it. Curious. Sandy

Hi, Zep, I had not run the whocrashed program bc. sysnative has it's own two programs it recommends. I used those - the diagnostic one contained 18 files filled with information I would not have been able to decipher - including 2 containing the dump file info that were roughly 3 and 11 MB (roughly). But your post reminded me to download whocrashed for the future. I went ahead and ran it for curiousity's sake. The results are below. It does seem they are suggesting a bad drive - and in at least one place they point to Avast. The larger diagnostic files generated for sysnative showed all the crashes were tied to an Avast driver. I uninstalled and it's been running fine. I might want to reinstall Avast since I run it on all our home desktops and laptops. I'm familiar with it and it hasn't posed a problem elsewhere. The folks at sysnative suggest waiting a little longer and using microsoft security essentials for now. Whocrashed: On Sun 8/4/2013 10:18:38 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\080413-21091-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80002CD2D6C) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Sun 8/4/2013 10:18:38 PM GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: aswsp.sys (aswSP+0x4133E) Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80002CD2D6C) Error: IRQL_NOT_LESS_OR_EQUAL Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: aswsp.sys . Google query: aswsp.sys IRQL_NOT_LESS_OR_EQUAL On Sun 8/4/2013 9:33:50 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\080413-21340-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80002C9CD6C) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Sun 8/4/2013 8:58:12 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\080413-21418-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80002CDCD6C) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Sun 8/4/2013 6:30:46 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\080413-22152-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80002CE6D6C) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. ----------------------------- This report is in somewhat more plain English - but seems to contain less specific diagnostics than the tests for sysnative. thanks. Lynn. -------------------------------------------------------------------------------- Conclusion -------------------------------------------------------------------------------- 5 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers: aswsp.sys If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems. Read the topic general suggestions for troubleshooting system crashes for more information. Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

Hello, You will probably need to set up the account on the new computer if you have not tried it, open thunderbird now click the tools tab, here are settings for rr: Incoming (POP3) Mail Server: pop-server.sc.rr.com Outgoing (SMTP) Mail Server: smtp-server.sc.rr.com News (NNTP) Server: news-server.sc.rr.com Server settings for former Adelphia Customers: Incoming (POP3) Mail Server: pop-server.roadrunner.com Outgoing (SMTP) Mail Server: smtp-server.roadrunner.com If dh was assigned an e-mail address with rr, he can use that for thunderbird, for more information Google "Set up Thunderbird e-mail" If you want to change e-mail address may have to contact rr.

I have had Frozen Shoulders, first in 2004 after I cleaned the soffit around my house by hand. I endured the pain for months before going to the doctor, who sent me for PT. He also offered me Cortisone injection, which I declined as I read that it actually damages the tissue in of itself. Three months of PT and the pain was worse, all the way down the right side of my back and as far over as the spine. It hurt to take deep breaths, and I couldn't even lift a frying pan cause the muscle in my forearm would lock up. Couldn't wash, blow dry my hair. I finally went to another doctor and he told me the only way I could get relief was from having a manipulation, where he would put me to sleep and wrench my shoulder, tearing the adhesions. He said the reason the PT made it worse was that it involved the Trigger points and as I lost range of motion, I depended on different muscles to do the work. He said it can only get better on its own IF if is caught in time and adhesions are not bad. I had the manipulation done and a week of PT to keep me moving it and excerises at home. I got full range of motion back after a month or so. Two years later- the other one froze. This time I went immediately and had the manipulation. Pain free immediately. I'd go and not put it off. If he offers a manipulation, do it. I had a hysterectomy in 1986 at the age of 36 but was on HRT until 2002 - had the first FS in 2004. I agree its probably horomone related partially. I have no diabetes or thyroid problems. About the excerises - check out Aaron Mattes - Active Isolated Stretches - best ones for FS. The PT ones have you hold the stretch way too long and you get the rebound effect of the muscle tightening back up. AIS excerises isolate the individual parts of the muscle and you do fewer of them, hold them shorter time frame and do them slowly. Whenever I overstress in gardening or lifting, cleaning and I feel the muscles tightening, I get those out and do them. Find some Biofreeze to use at night. Rub it on Your shoulder and down your back and arm. Its a gel - kinda like Bengay but much much better. It helped me so that I could sleep. Most PT places have it and some massage places. Wet a hand towel and wring it out. Put it in the microwave for about 2-3 minutes. Take it out and wrap it in another bath towel. Lay it across your shoulder, then move it to any area that hurts. I did this before I would excerise then after the excerises, you ice them down. But just for relief, I'd do the hot towel whenever I hurt. Good luck, FS is much more common than people think. Aleve helped too - more than others for me.