search for: win2000mag

> Might not be it...but the '30 second lockup' triggered a memory... > > Could this be the 'looking for scheduled tasks' problem? > Here's a blurb from the > windows-net-mag site > (http://www.win2000mag.net/Articles/Index.cfm?ArticleID=24546) . Like Windows 2000, XP suffers from a little-documented browse delay. When you browse to a Windows 9x computer name (\\computername), your XP computer checks for Scheduled Tasks on computers to which it's connecting. This search can cause as much as a 3...