If you don't have any unaffected configurations left in the registry, and the sfc /scannow and recovery console options are unavailable to you, I think all that is left is to wipe the disk and reinstall. This will of course eliminate all data, so you need to find a way to back up the stuff you want to keep. By all means try the sfc and recovery options before you kill the disk. You have nothing to lose by trying.
You can also wait a bit and see if Rick or Denny find this thread; they are more experience than I and might know a better way.
Message Edited by JackShack on 02-14-2006 01:24 PM
Tried to restore as far back as we could, looks like the trojan was embedded awhile ago. Can't restore further back. So sounds like best bet is to recover? How much data and files will be lost or am I completely dumpint the hard drive and starting from scratch? Sounds like a total pain. Also, will this affect the registry? If the trojan or worm, I thik he picked up at least 1 of each, has hit the registry, will this cure that also? Or ia a 44 magnum the only way out?
There is a chance that the missing file had something to do with the trojan, so the first thing I would try is to use system restore to go back to a point about two weeks before the trojan became noticable. If this doesn't work, you have other choices provided your Win XP installation disk is at the same service pack level as the version of Win XP on the hard drive. If it is, you can try to use system file checker or the recovery console to repair your installation. If the Win XP installation disk is older than the hard drive version, you will need to do a clean installation.
System File Checker is a command that instructs Windows to check its key files for errors and replace those that are damaged. You open the Run box, type cmd, and in the dialog box that opens you type sfc /scannow. You may need a Win XP installation disk if the routine finds a file that it cannot replace from the cache in the system. This is why I said that the version on your hard drive must match that of the Win XP installation disk that you have. Computers that shipped more than two years ago generally have a Win Xp (initial release) or a Win XP sp1. If you have updated the version on your hard drive to Win XP sp2, neither of these disks will work with an attempt to repair the os. You can also try the recovery console, again provided that the Win XP installation disk matches the version on the hard drive. You may also try a repair/install, which requires you to boot from your Win XP installation disk and choose "repair" instead of new installation. Any of these options require the version of Win XP to be the same on the hard drive and the installation disk.
The missing file (its name is actually rtl70.bpl, not rt170.bpl) is a file associated with Borland's Delphi. If you are using Delphi, see the "accepted answer" in
this thread. If you are not using Delphi, a clean install is probably indicated, as System File Checker (sfc) will do nothing for the problem since the missing file is not a Windows system file and Recovery Console will not be useful either for the same rerason.
You may be able to go to Start|Run, enter
msconfig and click OK and on the Startup tab uncheck an item referring to the missing file, but in view of the problems you are having it seems unlikely that this would enable you to access the network or the Internet.
AOL says my continued lost conns is due to MS=- see error below. WHERE can I find this to repair? MS says contact Dell.. dell says it have to pay even though I still have my warranty!
Pam
*** GPF Data ***
Error C0000005 occurred in module patrav21.dll at address 0A4F4FEF
jackshack
6.4K Posts
0
February 14th, 2006 17:00
If you don't have any unaffected configurations left in the registry, and the sfc /scannow and recovery console options are unavailable to you, I think all that is left is to wipe the disk and reinstall. This will of course eliminate all data, so you need to find a way to back up the stuff you want to keep. By all means try the sfc and recovery options before you kill the disk. You have nothing to lose by trying.
You can also wait a bit and see if Rick or Denny find this thread; they are more experience than I and might know a better way.
Message Edited by JackShack on 02-14-2006 01:24 PM
DEEJ13
3 Posts
0
February 14th, 2006 17:00
jackshack
6.4K Posts
0
February 14th, 2006 17:00
There is a chance that the missing file had something to do with the trojan, so the first thing I would try is to use system restore to go back to a point about two weeks before the trojan became noticable. If this doesn't work, you have other choices provided your Win XP installation disk is at the same service pack level as the version of Win XP on the hard drive. If it is, you can try to use system file checker or the recovery console to repair your installation. If the Win XP installation disk is older than the hard drive version, you will need to do a clean installation.
DEEJ13
3 Posts
0
February 14th, 2006 17:00
jackshack
6.4K Posts
0
February 14th, 2006 17:00
System File Checker is a command that instructs Windows to check its key files for errors and replace those that are damaged. You open the Run box, type cmd, and in the dialog box that opens you type sfc /scannow. You may need a Win XP installation disk if the routine finds a file that it cannot replace from the cache in the system. This is why I said that the version on your hard drive must match that of the Win XP installation disk that you have. Computers that shipped more than two years ago generally have a Win Xp (initial release) or a Win XP sp1. If you have updated the version on your hard drive to Win XP sp2, neither of these disks will work with an attempt to repair the os. You can also try the recovery console, again provided that the Win XP installation disk matches the version on the hard drive. You may also try a repair/install, which requires you to boot from your Win XP installation disk and choose "repair" instead of new installation. Any of these options require the version of Win XP to be the same on the hard drive and the installation disk.
Denny Denham
2 Intern
•
18.8K Posts
0
February 14th, 2006 19:00
The missing file (its name is actually rtl70.bpl, not rt170.bpl) is a file associated with Borland's Delphi. If you are using Delphi, see the "accepted answer" in this thread. If you are not using Delphi, a clean install is probably indicated, as System File Checker (sfc) will do nothing for the problem since the missing file is not a Windows system file and Recovery Console will not be useful either for the same rerason.
You may be able to go to Start|Run, enter msconfig and click OK and on the Startup tab uncheck an item referring to the missing file, but in view of the problems you are having it seems unlikely that this would enable you to access the network or the Internet.
datalova
1 Message
0
February 15th, 2006 00:00