Reply to Re: Hard drive question
If you don't have an account, just leave the password field blank.
Interesting.
Google says that "t-logger" is a device made by Dallas Semicondictor.
"Elite t logger" resolves to a corporate keylogger application that runs on XP and 2000. AFAIK, neither of these NT platforms supports Drivespace.
Unless this machine came from a "Corporate Redeployment" initiative, I doubt it would be the latter application.
Did you boot to safe mode when you did your clean out?
I am guessing your father is running Win9x.
You could download a dos boot from bootdisk.com, and use a dos based scanner. This would not check your registry for certain, but it would eliminate Windows from interacting with your scan.
All of the mainboards I use have the Trend-Micro, chipaway chip on them. This checks the boot sector at the start of the boot up POST test. I am unfamiliar with the current McAfee software, does it have a boot scan?
Is drivespace the only tool or program that seems to behave improperly?
Weird story. I worked at a Financial Institution for a while. We had an old 340 thinkpad that thought it had and 800 mb Hard-drive. They picked up some virus that messed up the MBR, and made it look like it had 2 400 mb drives. Another reboot and it had 4 200 mb.
I couldn't even clear it with dos 5 fdisk. SO, I used an OS/2 boot disk set (3 disks) and rand their fdisk, format and installed OS/2. This cleared it enough to use the dos boot, and finally installed the corporate image from CD. Good job I did not do a network install.
On first bootup I then found the Monkey A virus had hidden somewhere, and I was finally able to clear the machine.
mm
Google says that "t-logger" is a device made by Dallas Semicondictor.
"Elite t logger" resolves to a corporate keylogger application that runs on XP and 2000. AFAIK, neither of these NT platforms supports Drivespace.
Unless this machine came from a "Corporate Redeployment" initiative, I doubt it would be the latter application.
Did you boot to safe mode when you did your clean out?
I am guessing your father is running Win9x.
You could download a dos boot from bootdisk.com, and use a dos based scanner. This would not check your registry for certain, but it would eliminate Windows from interacting with your scan.
All of the mainboards I use have the Trend-Micro, chipaway chip on them. This checks the boot sector at the start of the boot up POST test. I am unfamiliar with the current McAfee software, does it have a boot scan?
Is drivespace the only tool or program that seems to behave improperly?
Weird story. I worked at a Financial Institution for a while. We had an old 340 thinkpad that thought it had and 800 mb Hard-drive. They picked up some virus that messed up the MBR, and made it look like it had 2 400 mb drives. Another reboot and it had 4 200 mb.
I couldn't even clear it with dos 5 fdisk. SO, I used an OS/2 boot disk set (3 disks) and rand their fdisk, format and installed OS/2. This cleared it enough to use the dos boot, and finally installed the corporate image from CD. Good job I did not do a network install.
On first bootup I then found the Monkey A virus had hidden somewhere, and I was finally able to clear the machine.
mm
