I haven't been back to this forum for a while; It's good to see some activity on my old complaint threads! I suspect that almost everyone's mileage will differ. Each state will likely have somwhat different interpretations of the fed regs, and will certainly have their own rules. In areas with already strong MG programs, I'm certain that things will continue for at least a while. In my area that isn't the case. To be fair, the U of Mn continues to support research and outreach, and each county does have an extension office here. But more and more counties are like mine, with a part-time assisant (secretary) whose time is shared with another office or two. Our extension office fields calls for 4-H, some county health programs, pregnancy & early childhood development and some drug abuse prevention services programs as well as the ag and hort stuff. There is now an extension agent's name on the building directory, but I happen to know that she lives and works 90 miles away in another county. There is no computer or phone on her desk, so I assume she attends occasional meetings here, but largely telecommutes from her office in that other county. While the farm economy is small in our area, I did notice a yellow pages ad in the new phone book for a "farm consultant", so apparently the slow loss of free help from the government creates an opportunity for entrepeneurship!

do you happen to still have the paper work that came with it like the directions and the instructions manual that will have all your default info in it and how to reset it. If not look on the bottom for the model and google that you should be able to go to the manufacturer site and find the manuals. Did you set up your router originally with it connected to a desktop computer, in other words which pc did you install the software on? The router is setup on the family PC not my Laptop. Unplugging the router (and modem if one) itself from power and powering down all the computers, then power up the modem if you have cable first then after a while power up the router and once it is fully up then power up the various computers, often makes a big difference. I think we have a modem and a router for Xbox and laptops. are you just using the Vista built in firewall? Yes.I'm using the windows firewall. what are you using is it cable or dsl or what for internet? My son says it's cable/DSL internet. have you done all your windows updates? Yes.Except for three optional ones. I'm confused about resetting the router. That would be on the main computer. Will this help my laptop internet connection?

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.

>On the other hand it's cheesey nit picking at words and terms that are commonly used interchangeably. OK, but what you said about thermostats not activating aux heat on their own was just plain incorrect. The backup heat can be activated manually with the emergency heat - OR the thermostat can activate it if it deems it necessary. The definition of "necessary" depends on the thermostat you buy. For cheapo ones, all it takes is a couple degrees between the set and actual temperatures. Higher end ones use more advanced algorithms to save more energy. >If you believe all the research resulting in setback t-stats reccomended for energy savings is incorrect that's your right I never said setbacks were always bad, I think they are beneficial for most of this country that has straight gas/electric heat with a single stage AC outside, especially given all the poorly insulated houses and oversized systems out there. But on HEAT PUMPS, yes I think setbacks do more harm then good. The fact is that heat pump capacity drops along with temperature, and there is nothing a fancy thermostat can do about that. Maybe you live in a climate that rarely gets under the 30s, in that case I can understand where you're coming from. But where I am, there is a good part of the year where temperatures are warm enough that heat pumps are still useful, but cold enough that they need the help of aux heat for recovery. The choices are, A) Setback and use a cheap stat that kills my electric bill by using aux heat to recover B) Setback and use a fancy stat that holds back on the aux heat, but consequently takes AGES to try and recover, and eventually has to call on the aux heat for help anyway C) Don't setback Which would you pick?