Scripts and Vim definitely didn't change - the only thing updated was some
Windows software.

Interestingly, it seems to have returned to full speed now, after rebooting
a couple more times.  I had rebooted the system once or twice while
installing the updates, and saw the behaviour after the reboots.  So I
rebooted again to check if one more reboot would fix the issue (as far as
Win7 has come, it still needs a swift kick in the reset button sometimes),
with no luck.  ... But as of today it seems OK again.

Very odd.

Perhaps Windows was doing some heavy-duty indexing in the background ...
that took 5 days ... to resolve... ?

I dunno.  Very very odd.

I'll look into ProcMon - maybe it would have revealed what Win7 was up to
and I could have saved us all some time and random flailing about.  :P

Thanks everyone!  For now, I think we can call this resolved (?) by the
dark power that is the Repeated Windows Reboot...  :/

-Greg


On Mon, Dec 5, 2011 at 11:31 PM, George V. Reilly <[email protected]> wrote:

> On Mon, Dec 5, 2011 at 10:23 PM, Christian Brabandt <[email protected]>
> wrote:
> >
> > On Tue, December 6, 2011 5:31 am, Ben Fritz wrote:
> > > I'd start by narrowing it down to plugins vs. your .vimrc. Try all of:
> > >
> > > gvim -i NONE (to check for the .viminfo/_viminfo file containing
> > > something ridiculous)
> > >
> > > gvim -N -u NORC -i NONE (to check for .vimrc/_vimrc causing it)
> > >
> > > gvim -N --noplugin -i NONE (to check for plugins causing it)
> > >
> > > gvim -N -u NONE -i NONE (to check all your config at once)
> >
> > Also there is a faq on it:
> > http://vimhelp.appspot.com/vim_faq.txt.html#faq-36.12
>
> If your scripts and vimrc haven't changed but your Windows has,
> ProcMon [1] may help pinpoint what's going on.
>
> [1] http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx
> --
> /George V. Reilly  [email protected]  Twitter: @georgevreilly
> http://www.georgevreilly.com/blog  http://blogs.cozi.com/tech
>
> --
> You received this message from the "vim_use" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>

-- 
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

Reply via email to