> From: Eli Zaretskii [mailto:e...@gnu.org] > Sent: 28 August 2013 16:12 > > > I've just made my third attempt, and was about 6 minutes between > > starting the .exe and seeing a blank window. It's now been another > > five or so, and it's still blank. (By "blank" I mean it has the normal > > Windows furniture, the emacs File/Edit/Options/etc menus, and then a > > large white space. The usual bar towards the bottom indicating the > > current buffer, line number, etc isn't present.) > > If you type "net stop netlogon" from a cmd window, does the problem go away?
Yes, it does! Hurrah! After a bit of experimentation, the problem seems to be my work VPN (OpenVPN). If that's running, emacs behaves strangely. If it isn't, no problems at all. So when I reported that emacs started cleanly after a reboot this morning, it was nothing to do with the reboot - it was my being on a train with no network. Does emacs normally do any sort of network access on startup? I'm not aware of having done any customisation which would require a net connection. I have used emacs to edit files on other drives which may not be present, but I can't find any "previous buffer" lists or similar which might mean it's still trying to visit them. There's also the question of why the VPN is causing issues, but I think that's my sysadmin's problem :) Many thanks, Elizabeth