I bought the 10X12 HFGH and it is up. I dug a hole and placed the base frame in it and filled it with what we call red breeze. I did have a bit of a problem with the instructions. I went to HF web site and downloaded a new set of instructions. That helped, but even with these new instructions, it left a lot to the imagination. They were different than the ones that came with the GH. I do want to make some modifications to our GH also to make it stronger. I am new to this site and would like to know how to find pictures on here, especially of the pool cover for insulation. I am thinking of putting up bubble wrap on the inside to help with insulation. I found these items on EBAY. Greenhouse Insulation Fittings - Super Alliplugs x 50 Has any one tried these? Here is the link to his EBAY store. Looks like lots of parts we could use on our HFGH. http://stores.ebay.com/Greenhouse-Warehouse He is located in UK, but the parts look exactly like what came with the HFGH, if you need extra parts. Tom S Colorado Here is a link that might be useful: GreenHouse parts in the UK for HFGH

***"Can I take the solenoid out of this compartment and try and jump it safely?"*** I don't advise trying that as the solenoid mounting bracket probably serves to ground the solenoid to the chassis and without a ground the solenoid will not work. If you have some booster start jumper cables you can safely set the battery out of the tractor and connect the red jumper cable to the tractor positive cable and then to the battery positive post. You might want to wrap up where the jumper cable connects to the tractor battery cable with some type of insulating media (plastic trash bag maybe) to keep from accidental shorting on the chassis ground. Next.......connect the black jumper cable to the battery and lastly....connect the last black jumper cable end to the negative battery cable end or to a clean bare metal chassis bolt or other ground. Now you can jumper the solenoid by touching a small jumper from the battery cable side of the solenoid to the small wire post on the solenoid. A safer way to test the solenoid is to use a volt meter or 12 volt test light on the small post/wire of the solenoid while someone holds the brake pedal down and turns the key to start position. If the small post/wire shows voltage at that time there is a good chance the solenoid could be bad. If the small post/wire does not show voltage at that time then the brake safety switch or the key switch are suspect. IF....the small post/wire shows voltage and the solenoid has clicked (operated)..........but the starter does nothing.......then you can jumper directly to the starter cable (the OTHER big solenoid post) with the red jumper cable instead of the battery cable side of solenoid. Just do the same procedure as first except connect the red cable to the starter side of solenoid or to the starter post itself. Touch the last black jumper end to a chassis ground to test starter. Caution.....it might spark some when you make that last contact. If the starter operates then the starter is OK.

Well, we finally pruned back our lilac!! DH used a pole chainsaw we got this year - it was really helpful - on the big older branches mostly on the inside of the clump. Then I made a tool (husbands suggestion) by taping a hook onto the end of a piece of bamboo, and used that to hook the top branches and pull them down so I could trim them - this saved me from having to get up on a ladder. Worked well!! So here are the before and after pics. It's a little hard to tell how much we trimmed because of the trees in our neighbors yard behind it. But a lot did come off! Hoping it likes it next spring and we get some new fresh growth and blooms :) This was taken 6/1/14: This was taken 9/10/15 And here is my fancy tool for pulling the top branches down: I hated having more of the neighbors green shed exposed. I keep trying to get something to grow up along that area so it will hide it (the green plant you see there is some type of weed plant that I find in other places in the yard. I let it go this year, that's why it's so tall), but haven't had any luck. Think I need to amend the soil area (we have sand on top of the old grass there, but I have dug up a couple of spots for plants and added some soil) or maybe I should put planter boxes at the top of the fence instead. Did you trim yours, popmama and maidinmontana? I love that picture of yours, maidinmontana - very pretty! Yours is really tall as well. Marj

Hi Zep, Here's the information from the Whocrashed report. System Information (local) -------------------------------------------------------------------------------- computer name: LYNNDELL windows version: Windows XP Service Pack 3, 5.1, build: 2600 windows dir: C:\WINDOWS Hardware: Inspiron 530, Dell Inc., 0FM586 CPU: GenuineIntel Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz Intel586, level: 6 4 logical processors, active mask: 15 RAM: 2950799360 total VM: 2147352576, free: 2022486016 -------------------------------------------------------------------------------- Crash Dump Analysis -------------------------------------------------------------------------------- Crash dump directory: C:\WINDOWS\Minidump Crash dumps are enabled on your computer. On Tue 6/10/2014 9:46:41 PM GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\Mini061014-01.dmp This was probably caused by the following module: win32k.sys (win32k+0x5FC9E) Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFBF85FC9E, 0xFFFFFFFFADB9BAE4, 0x0) Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M file path: C:\WINDOWS\system32\win32k.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: Multi-User Win32 Driver Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch. 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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. -------------------------------------------------------------------------------- Conclusion -------------------------------------------------------------------------------- One crash dump has been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you. 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. ------------------------------------------------------------ I'll try reinstalling Firefox, but I'm doubtful because during the course of today - after my initial Firefox difficulties, I did update from Firefox 29 to Firefox 29.0.1. So I can re-install 29.0.1, but installing it this afternoon did not fix the problem. I'll check back later. And now I'll reinstall. Thank you. Lynn.