View Full Version : Manual Update - REALLY Manual!
Hello,
My old Windows 98 computer developed a major functionality problem last year, prompting me to purchase a new Vista PC and to cancel my Internet dial-up service on the old machine.
Now I'm in the process of trying to get the old computer back off the sickbed, and I would like to load Spybot onto it. I had uninstalled Spybot last December, since it would no longer finish a scan, but after finally succeeding in doing some maintenance on the hard disk now the computer seems to be doing better -- so I'd like to try running Spybot on it again.
I should add that I have always suspected that the original trouble might have been due to some kind of malware: that's why I think there is still a purpose in installing Spybot on a machine that's no longer connected to the Internet. If I can find the malware and remove it, in theory I can put the computer back on the Web. I'd like to have that option again.
The trouble is, the old computer doesn't have an Ethernet port for my new High-Speed Internet service, so the only way that I know of to download and install Spybot on it is to download the program to the new computer and onto a CD-ROM disk, then put that disk in the old computer and run the installation wizard from there.
I've gotten as far as that, but now it turns out that Spybot won't scan. I keep getting an error message saying that, "You need to install the detection updates first by using the integrated update or the manual updates." Of course I can't do either of those, because the computer isn't hooked up to the Internet anymore.
So as I see it there are two theoretical possibilities: 1) I could download the updates from outside of Spybot onto the CD-ROM, and then manually copy them onto the appropriate Spybot folder; or 2) I could download the updates from outside of Spybot onto the CD-ROM, and then customize the "SDUpdate" program to look for the updates file locally instead of on the Internet.
What I wish to know, then, is: Will the first of these methods work? And, is there any way for me to do the second one, and if so, then how?
Thanks very much.
--JorgeA
spybotsandra
2009-12-09, 14:18
Hello,
Please download the installation and the update file on another computer,
copy these to a CD or USB stick and then install and run it on the infected computer:
Installation file (http://www.spybotupdates.com/files/spybotsd162.exe)
Update file (run it after the installation) (http://www.spybotupdates.com/updates/files/spybotsd_includes.exe)
Best regards
Sandra
Team Spybot
Hi Sandra,
I tried your suggestion. Here is the sequence of things I tried:
A)
After downloading Spybot to the CD-ROM on the new computer, loading the CD-ROM on the old computer, and installing the program, I downloaded the updates file to the CD-ROM on the new computer, and then dragged it from there to the Updates folder on the old computer.
The first thing I noticed in Windows Explorer is that what showed up in the computer folder listing was not the actual spybotsd_includes.exe file, but what it called a "shortcut" to the file. When I clicked on that "shortcut," the computer first slowed down to a crawl and then froze. Not even Crtl-Alt-Del helped, and I had to turn the computer off.
B)
After rebooting, I tried running the updates file straight from the CD-ROM via Windows Explorer. I got an "NSIS Error" saying that:
"The installer you are trying to use is corrupted or incomplete. This could be the result of a damaged disk, a failed download or a virus.
"You may want to contact the author of this installer to obtain a new copy.
"It may be possible to skip this check using the /NCRC command line switch (NOT RECOMMENDED)." Given that warning, I did not try to use any such command. (Nor would I know how to use it.)
C)
Next, I dragged the spybotsd_includes.exe file to the Includes folder (instead of to the Updates folder), and clicked on it. I got the same "NSIS Error" message as above.
D)
Finally, I tried loading Spybot and then telling it to search for updates. Of course it tried to go online, which that computer can't do, so when I clicked on "Cancel" for the dialer to start, I got an error message saying, "Error retrieving update info file!" :mad: Isn't there any way to tell it to look for the update file locally?
So, what EXACTLY do I need to do in order to install the updates file (not the Spybot program, that's already newly installed) on the old computer?
I am not a computing expert, and these procedures are not intuitive for me. I would appreciate detailed, step-by-step, start-to-finish instructions for installing the updates manually.
Thanks in advance for your time.
--JorgeA
You don't need to install Spybot on the suspect computer. And you do not need to download SpyBot to the CD-ROM.
On a stable computer that is running Spybot normally, update the detections. Next, drag and drop the ENTIRE SpyBot folder to CD-ROM.
Next, put the CD-ROM in the suspect computer. Make sure you have explorer on that computer set to Show Hidden Files.
Next, browse the SpyBot folder on the CD-ROM and find the file spybotSD.exe (spybotSD.exe is a hidden file so, if you don't see it, double chedk that you have Show Hidden Files enabled).
Double-click spybotSD.exe on the CD-ROM to run SpyBot. You can now run SpyBot directly from the CD-ROM and scan the suspect computer.
Thank you, Bill -- I'll try that.
I had the impression that Spybot had to be installed on the computer that was being scanned.
I'm still curious if it's possible (and how) to download updates and integrate them into Spybot "by hand" outside the program's automated process. But your idea might be the solution I needed! Will be trying it right away.
--JorgeA
Thank you, Bill -- I'll try that.
I had the impression that Spybot had to be installed on the computer that was being scanned.
Spybot can run out of the directory it was installed in because all files required are in the installation directory. At least, I was able to do that with v1.5.
But I'm sorry, I forgot an important step: BEFORE copying the Spybot directory over to the CD-ROM, open Spybot on the computer where it was installed and do the following:
- DISABLE "Lock Hosts File"
- DISABLE Resident and Teatimer
This will prevent these settings from interfering with running a non-native install. Copy the Spybot directory over to the CD-ROM. You can change any of those settings back after you copied them over.
I'm still curious if it's possible (and how) to download updates and integrate them into Spybot "by hand" outside the program's automated process. But your idea might be the solution I needed! Will be trying it right away.
--JorgeA
Don't know, never needed to. But I hope this helps - let me know how it works out!
Hi Bill,
I'm glad you sent that follow-up, because in the meantime I tried the instructions as given originally and all I got when trying to load Spybot was an "illegal operation" message after the hard disk churned for about half an hour.
Before posting this message, I tried the newest instructions -- and I'm sorry to report that the procedure didn't work. I got the same "illegal operation" error message. I did disable SD Resident and TeaTimer, as well as the Lock Hosts File, on the good computer. Since I already had a copy of Spybot installed on the suspect computer, I disabled them on that one too, for good measure, and then tried to run Spybot from the CD-ROM. No dice.
FWIW, the version of Spybot I'm using (or trying to use) on the suspect computer is the current one, 1.6.2.46.
The only tweak to this procedure that I can think of is that maybe I need to restart the computer(s) right after disabling those features? I re-enabled them on my good computer as soon as I copied the Spybot directory to the CD-ROM, as I'd rather not leave it unprotected if possible. Let me know if you think that this (rebooting after disabling and before copying) would help, or if you think of anything else to try.
Thanks for the ideas!
--JorgeA
Just an update on this issue:
Because I kept getting error messages suggesting that the download file might be corrupted, I decided to erase the first updates file from the CD-ROM and download a new one.
I think I forgot to disable TeaTimer and the Lock Hosts File this time, but I kept them disabled on the suspect computer. I moved the CD-ROM to the suspect computer and clicked on the updates file. This time it loaded and ran great -- asked me where to put the unzipped files, and I put them on the hard drive -- and am presently running the up-to-date Spybot on the suspect computer.
The only thing is that, whereas the installed Spybot loads right away, the non-installed Spybot takes 20-30 minutes to load (I got tired of waiting, so went off to do something else). Also, FWIW the Spybot on my new computer looks for a total of 779087 items, whereas the one on the suspect computer is looking for 776390 files, even though they're from the same update (aren't they?).
Will report back on developments if Spybot successfully finishes, or crashes again on the old computer.
Thanks again for your help. I've learned a lot about computing, and about Spybot, in the last day or two.
--JorgeA
Glad to read that you're making progress!
BTW, I've learned that when diagnosing/fixing a problem computer, to do it right it's best to not be in a rush...!
Let me know how it works out! :santa:
Hi Bill,
O.K., I got the updates file to extract itself on my suspect computer, and the new Spybot that's installed there accepted it, and I was able to run a scan --ALMOST to the very end.
When it got to file 776390/776390, Spybot said to "Please wait scanning download directories." That's where it eventually stopped, with the dreaded error message "This program has performed an illegal operation and will be shut down. If the problem persists, contact the program vendor."
Still, I count this as major progress because (a) I hadn't been able to get even this far lately, what with Spybot's updates not even loading, and (b) this is exactly as far as I was able to get a year ago. So at least we've removed a layer of new issues and are back to the original problem, whatever that is.
You bet that doing this stuff requires a lot of patience!!
Any ideas as to how to get past this particular hurdle?
--JorgeA
Well, from what you wrote before, 776390 is the number of items it Spybot looking for, so I'm thinking that maybe the scan completed but ended poorly?
Oh, if the suspect computer is a Windows 98 computer, and if the HD has not been maintained, then there is a very good chance that the hard drive is horribly fragmented. It's been my experience that extreme fragmentation on Windows 98 FAT32 hard drives (especially older hard drives) can and will cause program crashes and general instability. And slow your computer to the point of where it's as slow as a herd of turtles stampeding through molasses!
If I were you, I'd check the Windows 98 hard drives for errors, with either CheckDisk or Norton Disk Doctor, and then defragment that bad boy. I had an old Windows 98 desktop that was so fragmented that every time it accessed the hard drive, it made a sound like a bicycle chain! Spybot took forever to run on that thing. I resurrected it by running Norton Disk Doctor from the CD (which found and fixed lots of hidden problems like various file errors and cross-linked files), then defragmented the HD (which took over 10 hours!).
You also might try installing Speedfan (http://www.almico.com/speedfan.php) and use it to check the S.M.A.R.T. status on the hard drive, in case the HD is so old and tired it's causing data problems. But I'm betting that bad fragmentation is part of your problems.
-Bill.
Oh, something else - to speed up the Spybot scan, defragmentation, system speed, etc. the VERY FIRST STEP on all computers (ESPECIALLY Windows 98 computers) is to completely delete all temp files. If you hold down the Shift key while you press DELete, the files will be permanently and completely deleted without going to the trash bin.
In this order:
Delete the cache on all browsers ("temporary files")
Delete all cookies
Search the entire hard drive for *.tmp. Do Control-A to select all and then Shift-Delete all these files
On Win98, you might find the search will show hundreds or thousands of these .tmp files located in C:\WINDOWS
Shift-Delete all non-text files in the C:\WINDOWS\TEMP directory
Only keep .log and .txt files because they can be useful in diagnosing problems
Empty the recycle bin
Here's to a successful resurrection...! :wav:
-Bill.
Well, from what you wrote before, 776390 is the number of items it Spybot looking for, so I'm thinking that maybe the scan completed but ended poorly?
Oh, if the suspect computer is a Windows 98 computer, and if the HD has not been maintained, then there is a very good chance that the hard drive is horribly fragmented. It's been my experience that extreme fragmentation on Windows 98 FAT32 hard drives (especially older hard drives) can and will cause program crashes and general instability. And slow your computer to the point of where it's as slow as a herd of turtles stampeding through molasses!
If I were you, I'd check the Windows 98 hard drives for errors, with either CheckDisk or Norton Disk Doctor, and then defragment that bad boy. I had an old Windows 98 desktop that was so fragmented that every time it accessed the hard drive, it made a sound like a bicycle chain! Spybot took forever to run on that thing. I resurrected it by running Norton Disk Doctor from the CD (which found and fixed lots of hidden problems like various file errors and cross-linked files), then defragmented the HD (which took over 10 hours!).
You also might try installing Speedfan (http://www.almico.com/speedfan.php) and use it to check the S.M.A.R.T. status on the hard drive, in case the HD is so old and tired it's causing data problems. But I'm betting that bad fragmentation is part of your problems.
-Bill.
Hi Bill,
Funny you should mention a fragmented hard drive. Just last week I managed to get Norton Disk Doctor to complete the diagnostic/defrag process on my Win98 PC for the first time in over a year! Every time I tried it, it would keep restarting due to repeated "disk writes," and eventually it would just give up with a message about too many disk writes, or simply freeze the computer completely.
Last week I finally figured out how to close down enough processes (without disabling the system) that NDD was able to finish without complaint. According to Norton SystemWorks, now my hard drive (supposedly) is in tip-top shape. Although... I ran NDD from the hard disk itself rather than from the CD as you did, I don't know if that makes a difference.
In any case I'm not sure that I can trust NDD's verdict, as Spybot is once again having trouble even loading (taking forever to open, and ending with an "illegal operation" error), so I will look into getting Speedfan onto the sick computer and see what's up.
Thanks again!
--JorgeA
P.S. I should say that Spybot seems to be the ONLY program that's having trouble opening and running. Word and the Norton products seem to be working as well as ever.
Hi Bill,
Funny you should mention a fragmented hard drive. Just last week I managed to get Norton Disk Doctor to complete the diagnostic/defrag process on my Win98 PC
Norton Disk Doctor does not defrag the hard drive - it only diagnoses and fixes file system errors. You need a separate application to defrag the hard drive. Norton has Speedisk to defrag the hard drive, but I've never used it and earlier versions were dangerously buggy.
Norton Disk Doctor does not defrag the hard drive - it only diagnoses and fixes file system errors. You need a separate application to defrag the hard drive. Norton has Speedisk to defrag the hard drive, but I've never used it and earlier versions were dangerously buggy.
Hi Bill,
Whoops! I meant Norton SystemWorks. Sorry about that. It was the "Speed Disk" option under Norton Utilities within SystemWorks. On the screen it looks just like Windows's Scandisk program. It was Speed Disk that kept restarting due to disk writes. In any case, the SystemWorks "One Button Checkup" says that the disk is now defragged (before, it was down to 76%) and didn't find any errors.
I did use NDD at one point last week, and everything seemed to be hunky-dory with the hard disk as far as it was concerned. Come to think of it, it too kept restarting until I shut down enough processes for it to stop complaining. But I did get to run both NDD and Speed Disk (defrag) till they finished successfully.
Hope this helps to provide useful info.
--JorgeA
Just wanted to add that for good measure I did also run the Windows Disk Defragmenter last week.
Hopefully this and my previous post will provide enough information to continue....
--JorgeA
Hi Bill,
Whoops! I meant Norton SystemWorks. Sorry about that. It was the "Speed Disk" option under Norton Utilities within SystemWorks. On the screen it looks just like Windows's Scandisk program...
!!!!!!!!!!!!!!!!!!!!!
They are two completely different programs that perform two completely different tasks, and on screen are only vaguely like each other.
Jorge, I can't help you if you don't even know what program you're using.
!!!!!!!!!!!!!!!!!!!!!
They are two completely different programs that perform two completely different tasks, and on screen are only vaguely like each other.
Jorge, I can't help you if you don't even know what program you're using.
Bill, c'mon -- I have not used these programs in more than a year as my old computer sat in the corner, basically ignored. And even back then I was strictly what we might call a "black box" user: My interest in learning the inner workings of computers and software, which was immense back when PCs first came out but had waned ever since the introduction of Windows, has only returned in the last couple of months. So my computer tech knowledge is more relevant to current systems than it is to anything that appeared after MS-DOS 3.3 and before Vista.
In addition to which, I have now done SO MANY things with and to that computer in recent days (including multiple installations and uninstallations of Spybot) that it has all become a blur, and it should not be surprising that I may have mistyped a name.
As I reported in the brief follow-up to my previous post to you, I did run the actual Windows defragmenter last week. I just ran it again tonight, after performing the maintenance work you suggested. Spybot is STILL taking an inordinate amount of time loading. (Been waiting for it now for 25 minutes.)
I did stipulate near the beginning of this thread that I am not a computer connoisseur. So please bear with me as I belatedly acquaint myself with my ten-year-old system. This is a learning opportunity for me, and I greatly appreciate your generous help.
--JorgeA