My advice would be throw in what you got, sounds like the manure was pretty aged so that is a good thing. If you can get your hands on more stuff, good but don't stress yourself too much over it. Your idea to try testing a few seedlings in it is a good one! There are some plants that take much better to growing in a compost bed than others. Potatoes and pumpkins are a couple that I've heard like growing in bins of leaves and other compost stuff. I've had lots of onions, garlic, carrots, kohlrabi, parsley, turnips, parsnips, spoon mustard, chinese kale, broccoli, and some volunteer melons all growing quite happily in new lasagna beds. What types of plants are you wanting to grow? Plants that I've found difficult to grow in really new lasagna beds include corn and sunflowers(it needs to get it's roots down into hard ground to stay upright well in my experience), peanuts (they need a sandy soil surface or something they can easily peg the flowers down into so the peanuts can form underground). Peas and beans are supposed to be sensitive to young compost but I can't say how much, they have grown well enough for me but I usually try and give them the more finished compost where I grow them. Just remember that building soil is a work in progress. Keep adding organic matter to the bed each season. Try new things. Have fun. Here is a link that might be useful: My Garden

Heres what the Symantic website had to say about this trojan Targeting over 400 banks and having the ability to circumvent two-factor authentication are just two of the features that push Trojan.Silentbanker into the limelight. The scale and sophistication of this emerging banking Trojan is worrying, even for someone who sees banking Trojans on a daily basis. This Trojan downloads a configuration file that contains the domain names of over 400 banks. Not only are the usual large American banks targeted but banks in many other countries are also targeted, including France, Spain, Ireland, the UK, Finland, Turkeythe list goes on. The ability of this Trojan to perform man-in-the-middle attacks on valid transactions is what is most worrying. The Trojan can intercept transactions that require two-factor authentication. It can then silently change the user-entered destination bank account details to the attacker's account details instead. Of course the Trojan ensures that the user does not notice this change by presenting the user with the details they expect to see, while all the time sending the bank the attacker's details instead. Since the user doesnÂt notice anything wrong with the transaction, they will enter the second authentication password, in effect handing over their money to the attackers. The Trojan intercepts all of this traffic before it is encrypted, so even if the transaction takes place over SSL the attack is still valid. Unfortunately, we were unable to reproduce exactly such a transaction in the lab. However, through analysis of the Trojan's code it can be seen that this feature is available to the attackers. The Trojan does not use this attack vector for all banks, however. It only uses this route when an easier route is not available. If a transaction can occur at the targeted bank using just a username and password then the Trojan will take that information, if a certificate is also required the Trojan can steal that too, if cookies are required the Trojan will steal those. In fact, even if the attacker is missing a piece of information to conduct a transaction, extra HTML can be added to the page to ask the user for that extra information. (In the example below the user is asked to enter their encryption key, in addition to the regular information.) Here is the login form viewed on a clean machine: (Insert Picture of a Regular Log In Screen) Below the form presented to an infected user is shown, the input box added by the Trojan has been marked in red: (Insert Picture of an Infected Log In Screen) When instructed, the Trojan can also redirect users to an attacker-controlled server instead of the real bank in order to perform a classic man-in-the-middle attack. Currently there is only one bank targeted in this way; however, recent updates to the Trojan change the user's DNS settings to point to an attacker-controlled server. Using this technique the Trojan can start redirecting any site to an attacker site at any time. This feature could also mean that if the Trojan is removed but the DNS settings are left unchanged then the user may still be at risk. (See below for the attackers' DNS server addresses.) Add to all of the above the ability to steal FTP, POP, Web mail, protected storage, and cached passwords and then we start to see the capabilities of this Trojan. But, it doesnÂt stop there  don't forget the porn! The Trojan also contains over 600 pornographic Web site URLs that can be shown to the infected user so that the attacker can make money from the referrals. Lastly, the Trojan can also download updates, which it regularly does. It can also download other executables and it can use the infected machine as a proxy or as a Web server on any chosen port (in tests the http port used was 18102). The multiple configuration files that the Trojan downloads are updated several times per day and currently the Trojan is capable of injecting HTML into about 200 different URLs. The configuration files are compressed and encrypted; however, after decrypting them we can see how the Trojan works in more detail. The configuration files are structured as .ini files and each section of an .ini file represents a different task. Here is a snippet from the configuration file that was used to inject HTML into the banking form shown in the example above: jhw21] pok=insert qas=someBankSite.com/xpage/loginxxxxxxxxxs.htm njd=name="oppasswd; dfr=14 xzn=/)n xzq=2 rek=(div class="clear sep4")(/div) (label for="clave")Clave de firma: (/label) (input name="ESpass" type="password" size="8" maxlength="8" class="input01 aleft w180"/) req=166 The configuration options in the snippet above are as follows: Token: Purpose: pok Action to take qas URL to take action on njd String to search for xzn End string to search for rek HTML to insert The Trojan searches for the string name="oppasswd; then it finds the end tag /) then it inserts the string into the page: (div class="clear sep4")(/div) (label for="clave")Clave de firma: (/label) (input name="ESpass" type="password" size="8" maxlength="8" class="input01 aleft w180"/) Shown below is the HTML shown to the user on a non-infected computer: (label for="clave")Clave personal: (/label) (input id="clave" name="oppasswd" type="password" size="8" maxlength="8" class="input01 aleft w180"/) (/div) And on an infected computer: (label for="clave")Clave personal: (/label) (input id="clave" name="oppasswd" type="password" size="8" maxlength="8" class="input01 aleft w180"/) (div class="clear sep4")(/div) (label for="clave")Clave de firma: (/label) (input name="ESpass" type="password" size="8" maxlength="8" class="input01 aleft w180"/) (/div) Note: I substituted ) for > in the above examples. The Trojan can take any of the following actions when altering the HTML of a page: insert, delete, replace, and replace all. The Trojan uses the keyword "ESpass" (see the form above) as a keyword when the user sends a page to the bank and the Trojan checks if the page contains that keyword. Using this technique the Trojan can recognize pages it has altered and can extract the relevant data from the page and send it to the attacker as well as to the bank. The configuration files for this Trojan currently contain over 200kb of data; however, new URLs and HTML are being added to the configuration files on a daily basis. The Trojan is easily updated since the full HTML of any banking-related Web site is sent to the attackers. Using these submissions they can target banks for which they do not have bank accounts already. We are currently monitoring all of the updates to this Trojan. The Trojan accesses the following URLs for configuration, updates, and to send stolen data:  iloveie.info  webcounterstat.info  microcbs.com  reservaza.com  screensaversfor-fun.com  mystabcounter.info  85.255.119.218 The Trojan also downloads a copy of Trojan.Flush.J, which changes the users DNS settings to the following attacker settings:  85.255.116.133  85.255.112.87 For protection, please keep your antivirus definitions up to date and block the above addresses at the firewall. Note: Not only did this Trojan grab my attention for obvious reasons, but the Trojan also installed itself as a .midi driver, causing my music to stop! For the record, the Trojan adds itself the following registry key so that it is loaded in all applications that use sound: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32\"midi1 But it also said this: Discovered: December 17, 2007 Updated: January 8, 2008 12:54:17 PM Also Known As: Spy-Agent.cm [McAfee] Type: Trojan Infection Length: 54,189 bytes and 98,304 bytes Systems Affected: Windows 2000, Windows 95, Windows 98, Windows Me, Windows NT, Windows Server 2003, Windows Vista, Windows XP Trojan.Silentbanker is a Trojan horse that records keystrokes, captures screen images, and steals confidential financial information to send to the remote attacker. Protection Initial Rapid Release version December 17, 2007 revision 023 Latest Rapid Release version January 10, 2008 revision 023 Initial Daily Certified version December 17, 2007 revision 032 Latest Daily Certified version January 15, 2008 revision 016 Initial Weekly Certified release date December 19, 2007 Click here for a more detailed description of Rapid Release and Daily Certified virus definitions. Threat Assessment Wild Wild Level: Low Number of Infections: 0 - 49 Number of Sites: 0 - 2 Geographical Distribution: Low Threat Containment: Moderate Removal: Easy Damage Damage Level: Medium Payload: Records keystrokes and captures screen images Releases Confidential Info: Steals confidential financial information Distribution Distribution Level: Low

Here is some information I got from a colleague of mine. As far as using a borrowed disc: "The only problem may be that if the installed system has had a Service Pack added to it, the disk will need to be the same or there'll be no Repair option, just reinstallation. In other words, if the system is at SP3 level, a WIN2000 SP2 disk won't work". There have been 4 service packs, so it's more than possible! Windows key: will you need it? "As far as keys is concerned, it depends. Sometimes yes. sometimes no. I think it depends on which Service Pack has been installed and whether the key data is accessible when doing the repair". See link for additional info. CLICK HERE

Sharon can you use the computer you are reporting here on to download the programs grandms suggests? Save them to a thumb drive or external drive, heck even burn them to a CD. Anything to get you underway. To get the latest AdAware definitions after you have downloaded the program itself click the link below and save this to your thumb drive. Install AdAware then double click on defs.zip on the thumb drive, click to open. It will not be recognised but you are invited to browse to the right program. Browse to C:\Program files\Lavasoft\AdawareSE Personal\ and click on Adaware.exe, click OK and the latest definitions will be installed. Now run AdAware. There will be a similar procedure if you elect to update the other prorams using that method. However you might find after AdAware cleans up you can get online for the updates which will be easier for you. Here is a link that might be useful: AdAware's latest definitions