Upgrading O/S's and applications sounds fine, however much software was never _designed_ to be secure, also design compromises are often required and code often contains unintentional bugs (even patches can add bugs), therefore you should assume that all software is potentially insecure and plan accordingly e.g. limit the use of known insecure products (IE, OE etc) and evolve a layered security policy to manage the evolving system enviroment. Oh another consideration is an old PC may run Win98 and a personal firewall fine, but when running XP it runs low on RAM and crashes the firewall, anti-virus etc, also XP has many more vunerable services running by default and can handle much higher network traffic, oops!
Too many people (especially residential broadband users) seem to ignore the benefits of NAT firewall routers and personal firewalls * (as another layer) to protect computers running any O/S. I see and hear frequent stories about broadband connections being compromised because the ISP negilgently sold broadband connections with a basic broadband modem, this is nuts given the threats and the low price of routers now e.g. in the UK a good basic ADSL NAT firewall router with 4-way ethernet 10/100 switch costs 67UKP retail, that's cheaper than some ADSL modems (and any new O/S) even if you have to buy a 9UKP NIC! OK the ISP may see a little extra cost, but it's better than the high traffic/cost of zombie PCs!
* You should not rely on only software firewalls because these only work when installed/running (after OS is installed/patched/booted), and can occasionally crash and can leave your computer vunerable.
Selective IP/port/feature blocking can be futile since you don't know where the next vunerability will appear, the best basic policy is to block everything _both_ ways then carefully unblock/enable only the features you need now (for each security layer), not forgetting to limit access rights at user level as approriate. Secure use is also a factor e.g. only send confidential information offsite via a secure connection or in an encrypted archive, and use secure practices and software when accessing email/websites.
I'm reading the "Secure Coding" (O'Reilly) by some CERT/CC staff, to get better ideas, I recommend you do too, these is much in there which appears obvious but is not common sense in various security contexts.