FCB::Open: Operating system error 32(The process cannot access the file because it is being used by another process.) occurred w

Hello all,
I am running into an interesting scenario on my desktop.  I'm running developer edition on Windows XP Professional (9.00.3042.00 SP2 Developer Edition).  OS is autopatched via corporate policy and I saw some patches go in last week.  This machine is also a hand-me-down so I don't have a clean install of the databases on the machine but I am local admin.

So, starting last week after a forced remote reboot (also a policy) I noticed a few of the databases didn't start back up.  I chalked it up to the hard shutdown and went along my merry way.  Friday however I know I shut my machine down nicely and this morning when I booted up, I was in the same state I was last Wenesday.  7 of the 18 databases on my machine came up with

FCB:pen: Operating system error 32(The process cannot access the file because it is being used by another process.) occurred while creating or opening file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\Test.mdf'. Diagnose and correct the operating system error, and retry the operation.
and it also logs  
FCB:pen failed: Could not open file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\Test.mdf for file number 1. OS error: 32(The process cannot access the file because it is being used by another process.).

I've caught references to the auto close feature being a possible culprit, no dice as the databases in question are set to False.  Recovery mode varies on the databases from Simple to Full.  If I cycle the SQL Server service, whatever transient issue it was having with those files is gone.  
As much as I'd love to disable the virus scanner, network security would not be amused.  The data and log files appear to have the same permissions as unaffected database files.  Nothing's set to read only or archive as I've caught on other forums as possible gremlins.  I have sufficient disk space and the databases are set for unrestricted growth.

Any thoughts on what I could look at?  If it was everything coming up in RECOVERY_PENDING it's make more sense to me than a hit or miss type of thing I'm experiencing now.