When I try to update to Service Pack 3, It starts to extract to a weird (creates a new folder...different name each time) name folder. once the files finish extracting, I get a notice saying update.exe - Entry Point Not Found. In the box it says "The procedre entry point" (then a bunch of garbage...two or three lines filled)...then "could not be located in the dynamic link library KERNAL32.DLL. Once I hit okay the created folder disappears. Also I have been getting a lot of reboots (Blue screen) lately. I suspected a virus (worm or Trojan) but ran McCafe virus scanner, ad-aware, and Spy-bot....did find some problems (no viruses but a worm was fixed) and I troubleshoot some problems but now im starting to get frustrated...Please Help! Thanks

Possibly: Run W2K setup and allow it to repair current installation (especially system files - but perhaps all it can/will). Download the SP again; is the version you have the full 128Meg file - and did it come from a known/clean source (e.g. MS notwithstanding problems in the past with one or two items from M$-land)? Re' BSOD: any signs of overheating; also is RAM as good as it might be (matched spec. chips)?

to Run W2K setup (do you mean from CD?) SP3 I received from MS Overheating maybe a problem will have to look. Not sure if RAM is mismatched (but were purchased separately Thanks

Yes; run setup\repair via CD boot or the 4 W2K floppies. A few W2K repair guides (if needed?) http://www.windowsreinstall.com/install/win2k/repairw2k/page1.htm http://is-it-true.org/nt/nt2000/atips/atips71.shtml http://support.microsoft.com/default.aspx?scid=kb;en-us;238359 http://support.microsoft.com/default.aspx?scid=kb;en-us;268106 (leads ultimately to downloadable how to from the W2K RK freebie chapter.) BSOD arrivals could mean a re-install to fix; although sometimes a Repair may fix it; similarly an Upgrade of current installation may do it (Upgrade is effectively an overwrite of current installation); but you will have to re-apply SP... Possibly you downloaded something 'nasty'; possibly an app/util isn't all it might be? Overheating may cause BSOD, though not all that common in this regard? Hardware changes can sometimes cause them - again not very common; they usually just cause system to hang? Usually software is the cause; either a crash or three has finally done in the installation; or you have 'imported' something unpleasant? Personally I prefer Norton to Macafee for a-v; found Macafee not very user-friendly, and pain to update definitions. Soem also suggest it misses some items? Norton do provide an on-line a-v scan (from what I read here)? Might be worth a visit to see if it finds anything? Also there are other freebie on-line scanners out there. If the SP3 is a CD copy from M$ perhaps contact them and ask for a replacement. Bad CDs are not very comon thesse days, but they do sometimes happen. Usually/frequently problems with copying/installing files in W2K are caused by defective (not up to W2K standard) RAM. W2K is very picky about RAM quality/specs. If a stick isn't 'kwite' as W2K likes, then... Similarly a failing stick may be cause for BSOD? Folks have often been misguided by error messages (can't copy/open a file etc.) both with NT and W2K that suggest CD problems or other issues, and all the while it's RAM that's the problem.