Viruses
Topic: work
The following e-mail messages were found to have viruses in them:

Sender: mojako143@yahoo.com
IP Address: 210.5.125.179
Subject: Mail Delivery (failure xxx)
MessageID: A42A91DD428
Report: ClamAV: message.scr contains Worm.SomeFool.P
MailScanner: Windows Screensavers are often used to hide viruses (message.scr)
Report: MailScanner: Found dangerous IFrame tag in HTML message

Viruses
Topic: work
The following e-mail messages were found to have viruses in them:

Sender: labaya@tei.ph
IP Address: 202.78.104.83
Subject: Re:
MessageID: E440D1DD428
Report: ClamAV: foto2.cpl contains Worm.Bagle.AG
MailScanner: Control panel items are often used to hide viruses (foto2.cpl)

Sender: james@fillib.org.ph
IP Address: 202.78.104.83
Subject: Re:
MessageID: 635E31DD428
Report: ClamAV: foto2.cpl contains Worm.Bagle.AG
MailScanner: Control panel items are often used to hide viruses (foto2.cpl)

Engg1 PC
Topic: work
2 days after I repaired this PC, it wouldn't connect to the server again. More on that later.

Today, Oct. 28, 2004, Bong Manalang called me, told me this PC wouldn't boot.

True enough, there was a BIOS ROM error. Researched on the net and found out that several factors could cause it, but none of them solved the problem (change RAM, PS, Video card and other peripheral cards).

Finally decided to remove the FLASH ROM from a batchmate PC and installed it to this one.

Problem solved. Spent about 45 minutes, but in between had to replace the hub at TSG with a switch, so all in all I spent about an hour.

Posted by Samboy at 12:01 AM JST

Share This Post

Post Comment | Permalink

TSG Hub
Topic: work
Replaced the hub (3com) with a CNET SOHO switch. The hub's power supply died.

(15 minutes)

Workshop @ Conference Room
Topic: i-Solv Project
Spent the whole day on a user workshop with the Project Team.

I think it's very fruitful. :-)

Viruses
Topic: work
The following e-mail messages were found to have viruses in them:

Sender: noreply@paypal.com
IP Address: 210.5.97.160
Subject: Thank you!
MessageID: 4BF461DD428
Report: ClamAV: list.pif contains Worm.SomeFool.P
MailScanner: Shortcuts to MS-Dos programs are very dangerous in email (list.pif)

Engg1 PC
Topic: work
Spent 45 minutes fixing the PC.

Tested the cable by logging on to the network using the AccThinkPad. Login successful, so I changed the NIC to one of the old CNet Pro200's.

Then I copied the driver files onto the hard disk.

MetThinkPad
Topic: work
I spent about 45 minutes, then 20 more (was caught by the lunch hour):

1. fiddling with the encrypted photos and moving to the shared folder for the committee's use
2. making available Kodak software and another one which I forget
3. Installing Fluke software.

Viruses
Topic: work
The following e-mail messages were found to have viruses in them:

Sender: fyp-nyc-jobs-subscribe@yahoogroups.com
IP Address: 210.5.116.162
Subject: Mail Delivery (failure xxx)
MessageID: 269A41DD428
Report: ClamAV: message.scr contains Worm.SomeFool.P
MailScanner: Windows Screensavers are often used to hide viruses (message.scr)
Report: MailScanner: Found dangerous IFrame tag in HTML message

IP Address: 66.94.237.32
MessageID: 131CE1DD428
Report: ClamAV: Fish.com contains Worm.Bagle.AG
MailScanner: Executable DOS/Windows programs are dangerous in email (Fish.com)

Meeting notes
Topic: i-Solv Project
Notes on the meeting with i-Solv (from 10am to 2:20pm):

Attendance:

Cesar Agito, i-Solv GM
Alex Garcia, i-Solv Project Manager
Maricel Paz, i-Solv SysAd

JVAMJr, SFE Project Manager
DPP, Billing Supervisor
ELP, Encoder
FVV, OM
CFF, CA
Pie, Programmer
Gina, Pie's Asst.
Erap, Meter Reading
Mariliz, Meter Reading

i-Solv asked for the following:
1. Organizational Chart (from MSM)
2. Customer Application Form (ok)
3. Schedule of Rates (DPP, ok)
- other Rates (PPA, etc.)
4. Class Codes (Pie)
5. Chart of Accounts (MCAJr)
6. Structures of Tables (Pie)

My notes:

The Org. Chart is to determine ownerships of databases/tables.

Pie suggested that account numbers be changed into the following format: yymm99999... to reflect the date of application of each customer.

FVV, CFF, DPP & ELP disagreed and wanted to use a geographical approach.

Perhaps we can follow Apaul's old style, but we will include "yyyymm" in the last portion of the account number.

But i-Solv suggested that we assign Account ID's (separate and universally unique) to each applicant (& existing customers, I presume). I agree that this is the best approach.

We also discussed the possible hierarchical recording of customer address records according to Franchise, Feeder, Barangay, Sitio, Subd/Village, Street.

Suggestions/enhancements:

1. Record all adjusted readings for auditing purposes.
2. Criteria for disconnection -- table-based to be flexible

Questions:
1. Worst-case scenario: let's say merong customer na hindi na-reading for 2 years. How to input that?

On Wednesday, 10-27-2004, i-Solv wants our inputs and wishlists so they can documents all requirements and bound the Scope of Work.

Pie is asking for a Billing meeting so we can work out what we need to present on Wednesday. We said, FINE.

Personal notes:
FB - 5 collectors, 2 tellers

Problems:
1. Timely posting of bank payments ([almost] real-time)
2. Who will sign the Acceptance Documents? I guess one officer per module (3 modules) and the Project Manager (and the GM?)
3. How do we distribute partial payments? (Unbundling)
4. How to bill changed meters?