More things to report on W32.SillyFDC.
Yesterday, Feb 2 at 6:58:33 p.m. , I turned on the computer, but didn’t log-on until 5-minutes later.
After log-on, I went to clicked onto [ Computer ] and noticed 3 Drives :
1. Hard Disk Drive (1)-- S3A6xxxD004 (C:) -- Local Disk
2. Device with Removable Storage (1) -- DVD RW Drive -- CD Drive
3. Network Location (1) -- desktop.ini -- Configuration Setting
But both the Telephone Line and the High-speed LAN Cable are unplugged, so how did I get a Network Location ?
( desktop.ini is apparently only 6 bytes , as opposed to the usual 174 bytes )
Today, Feb 3, I looked again at the Norton Security History Log for this log-on on Feb 2, and it reads as follows :
Item 1 : 6:58:33 p.m. -- Firewall rules were automatically updated for Local Security Authority Access.
Item 2 : 6:58:42 p.m. -- Firewall rules were automatically updated for Services and Controller App.
Item 3 : 6:58:42 p.m. -- Firewall rules were automatically updated for Services and Controller App.
Item 4 : 6:58:48 p.m. -- Firewall Configuration updated: 105 rules .
Item 5 : 6:58:48 p.m. -- Firewall Configuration updated: 105 rules .
Item 6 : 7:05:11 p.m. -- User logged in
This Log is different from the one I looked at on Feb 2, within the first 15 minutes after logging-in that day.
This item is now missing from the log :
Item ? : 6:58:45 p.m. -- connected to a protected network ( 127.0.0.0 / 255.0.0.0 )
Something funny is going-on.
xxxxxxxx
I also noticed that when I turned on the computer, quite often the DVD Drive goes into a high-speed spin.
There is no bootable DVD here, only a closed Music DVD I made way-back in early 2008.
But before Dec/2008 when W32.SillyFDC first surfaced, my Toshiba Computer never goes into a high-speed spin on booting.
xxxxxxxx
There are actually 2 Users on the Toshiba Computer, namely :
1. MYSELF - Administrator - password protected.
2. ASP.NET Machine Account - Standard Account - password protected.
I don’t know whether the second account created for Visual Studio / Internet would be a problem here.
Keeping watch until re-boot to Out-Of-Box condition.