It would be too much of a hassle to change that because it's my default document directory, and there are some dependency problems as well which I don't think it's a good idea to alter it.
When I installed MikTeX 2.9 I didn't remove MikTeX 2.8. The compiler works fine if I re-configure LyX to use the MikTeX 2.8 installation. Compiling speed was very slow though (this happened after I installed some packages for 2.8 which seemed to be causing such slowness although I couldn't figure out why - this is the reason why I installed MikTeX 2.9). Another point is that my office computer also uses LyX on a MikTeX 2.9 installation (also runs on Windows XP). The directory also contains spaces, but I can compile normally on that machine. Now I don't know which part is actually the culprit, because it seems that the compiler is designed to deal with spaces but somehow that does not work on my computer. --- 2011年12月5日 星期一,Richard Heck <rgh...@comcast.net> 寫道﹕ 寄件人: Richard Heck <rgh...@comcast.net> 主題: Re: Compile error: "The directory path to the document cannot contain spaces" 收件人: "David" <dav_0...@yahoo.com> 副本(CC): lyx-users@lists.lyx.org 日期: 2011年12月5日,星期一,上午1:53 On 12/04/2011 07:55 AM, David wrote: Dear all, I have been using MikTeX 2.8 and has recently upgraded to MikTeX 2.9. To ensure my LyX (2.0) runs smoothly I uninstalled that and reinstalled the latest version (2.0.2), pointing it to my latest MikTex installation. However, when I use it to compile my document (Ctrl+R) a message box appears immediately saying that "The directory path to the document cannot contain spaces", an error that I have never encountered before. Yes I know my directory contains spaces but it worked fine before I did all these changes. Moving my file somewhere else works, but certainly it will be too troublesome to do that every time. Furthermore my directory is something like "D:\My Documents\blahblahblah" and I clearly cannot change "My Documents" to something else. Actually, you can change it. I don't have Windows machines in my house any more, but I used to do it routinely on my wife's machine. Is there an alternative method that can bypass this problem? It would seem that the configuration script has for some reason decided MikTeX won't allow spaces. You might try reconfiguring, but then again, if the configure script failed this test, then there may be an issue. Windows people may be able to give more advice. Richard