Re: Fw: Postscript preview
LB wrote: Which would not explain why futzing with the environment variables cured (or at least moved) the bug. Then again, perhaps I'm asking too much of the bug as far as consistency goes. This brings me back to my thesis that somewhere there is a buffer overflow. How/why it would involve both the file paths/names and environment variables beats me, but I'll take another shot on the developer list and see what shakes. This problem with preview is still not 100% gone. I have to change the PATH to point to a different copy of GS (Matlab copy or official copy) depending on which Lyx document I open. At this time, only the document that first exhibit this problem needs PATH to point to Matlab copy of GS for preview to work. All other documents I have opened so far work fine with the official version but show preview problem with Matlab copy of GS. Confused, Leo Why don't you make the Matlab copy of GS the same as the system? I open two instances of Windows Explorer to do this kind of work. In one Window, navigate to Matlab and note the name of the Gs directory. Right-click on the gs directory and delete it. It will be safe in the Recycle bin as long as you don't empty the recycle bin. In the other window navigate to the system gs directory. Right-click on it and choose copy. Then paste it into the Matlab directory where the old matlab gs used to reside. Rename it to the same name as the old matlab gs. I suggest this because I don't know the matlab menu or command line just to change it to point to the system-wide gs. If for some reason Matlab doesn't make eps images, change it back. Rename the newly made gs directory which has been renamed to match the original matlab gs to something else. Then right-click and delete it. Otherwise you will have two gs directories in the Recycle bin and not know which one to Restore if they both have the same name. This is the way to do it if you don't know some technical syntax or deep matlab menu option. Remember not to use illegal characters when you create filenames for the .eps images. Do ordinary. Another thing to look at is to invoke GSview, under Start- All programs. After it loads, at the top under Options, choose Advanced Configure. I was once shocked to discover that my gs.dll and gs include path pointed to gs 7.07 which was long gone; you want your current which in your case is 8.14 I think. Anyway, I think those entries are generated from reading the registry. And sometimes GS doesn't uninstall properly and leaves old traces in the registry which are erroneously detected used. The idea here is that if 8.14 is making the eps then when LyX uses 8.14 it should be able to decipher them. This should work unless some command line switches/snytax invoking ghostscript has been changed from what worked with the old version but could be different in the newer gs version. That doesn't happen all that often so your chances should be good. This will avoid you having to edit the Path prefix in lyx back and forth, in order to change versions to accomodate the creating gs version. Good luck, Stephen
Re: Fw: Postscript preview
TechTonics wrote: LB wrote: This problem with preview is still not 100% gone. I have to change the PATH to point to a different copy of GS (Matlab copy or official copy) depending on which Lyx document I open. At this time, only the document that first exhibit this problem needs PATH to point to Matlab copy of GS for preview to work. All other documents I have opened so far work fine with the official version but show preview problem with Matlab copy of GS. Confused, Leo Why don't you make the Matlab copy of GS the same as the system? Don't forget to generate a new version of the problematic image(s) from Matlab again using the system gs 8.14. This idea isn't intended to fix the problem with the original mutant image created by the matlab gs, but to correct the current bad file(s) by making a new one and to fix future problems. Right-clicking in the taskbar(bottom)cascade = = Regards, Stephen
Re: Fw: Postscript preview
Why don't you make the Matlab copy of GS the same as the system? I tried that unsuccessfully already. Matlab generates the ps file even when I remove its GS directory completely. When I substitute Matlab GS with official GS, the figures still misbehave after I regenerate them from scratch with the official GS located in Matlab directory. Another thing to look at is to invoke GSview, under Start- All programs. After it loads, at the top under Options, choose Advanced Configure. I was once shocked to discover that my gs.dll and gs include path pointed to gs 7.07 which was long gone; you want your current which in your case is 8.14 I think. Anyway, I think those entries are generated from reading the registry. And sometimes GS doesn't uninstall properly and leaves old traces in the registry which are erroneously detected used. It points to 8.14 as needed. I give up. Preview works most of the time, I can survive this one document without having the preview. Leo
Re: Fw: Postscript preview
LB wrote: Which would not explain why futzing with the environment variables cured (or at least moved) the bug. Then again, perhaps I'm asking too much of the bug as far as consistency goes. This brings me back to my thesis that somewhere there is a buffer overflow. How/why it would involve both the file paths/names and environment variables beats me, but I'll take another shot on the developer list and see what shakes. This problem with preview is still not 100% gone. I have to change the PATH to point to a different copy of GS (Matlab copy or official copy) depending on which Lyx document I open. At this time, only the document that first exhibit this problem needs PATH to point to Matlab copy of GS for preview to work. All other documents I have opened so far work fine with the official version but show preview problem with Matlab copy of GS. Confused, Leo Why don't you make the Matlab copy of GS the same as the system? I open two instances of Windows Explorer to do this kind of work. In one Window, navigate to Matlab and note the name of the Gs directory. Right-click on the gs directory and delete it. It will be safe in the Recycle bin as long as you don't empty the recycle bin. In the other window navigate to the system gs directory. Right-click on it and choose copy. Then paste it into the Matlab directory where the old matlab gs used to reside. Rename it to the same name as the old matlab gs. I suggest this because I don't know the matlab menu or command line just to change it to point to the system-wide gs. If for some reason Matlab doesn't make eps images, change it back. Rename the newly made gs directory which has been renamed to match the original matlab gs to something else. Then right-click and delete it. Otherwise you will have two gs directories in the Recycle bin and not know which one to Restore if they both have the same name. This is the way to do it if you don't know some technical syntax or deep matlab menu option. Remember not to use illegal characters when you create filenames for the .eps images. Do ordinary. Another thing to look at is to invoke GSview, under Start- All programs. After it loads, at the top under Options, choose Advanced Configure. I was once shocked to discover that my gs.dll and gs include path pointed to gs 7.07 which was long gone; you want your current which in your case is 8.14 I think. Anyway, I think those entries are generated from reading the registry. And sometimes GS doesn't uninstall properly and leaves old traces in the registry which are erroneously detected used. The idea here is that if 8.14 is making the eps then when LyX uses 8.14 it should be able to decipher them. This should work unless some command line switches/snytax invoking ghostscript has been changed from what worked with the old version but could be different in the newer gs version. That doesn't happen all that often so your chances should be good. This will avoid you having to edit the Path prefix in lyx back and forth, in order to change versions to accomodate the creating gs version. Good luck, Stephen
Re: Fw: Postscript preview
TechTonics wrote: LB wrote: This problem with preview is still not 100% gone. I have to change the PATH to point to a different copy of GS (Matlab copy or official copy) depending on which Lyx document I open. At this time, only the document that first exhibit this problem needs PATH to point to Matlab copy of GS for preview to work. All other documents I have opened so far work fine with the official version but show preview problem with Matlab copy of GS. Confused, Leo Why don't you make the Matlab copy of GS the same as the system? Don't forget to generate a new version of the problematic image(s) from Matlab again using the system gs 8.14. This idea isn't intended to fix the problem with the original mutant image created by the matlab gs, but to correct the current bad file(s) by making a new one and to fix future problems. Right-clicking in the taskbar(bottom)cascade = = Regards, Stephen
Re: Fw: Postscript preview
Why don't you make the Matlab copy of GS the same as the system? I tried that unsuccessfully already. Matlab generates the ps file even when I remove its GS directory completely. When I substitute Matlab GS with official GS, the figures still misbehave after I regenerate them from scratch with the official GS located in Matlab directory. Another thing to look at is to invoke GSview, under Start- All programs. After it loads, at the top under Options, choose Advanced Configure. I was once shocked to discover that my gs.dll and gs include path pointed to gs 7.07 which was long gone; you want your current which in your case is 8.14 I think. Anyway, I think those entries are generated from reading the registry. And sometimes GS doesn't uninstall properly and leaves old traces in the registry which are erroneously detected used. It points to 8.14 as needed. I give up. Preview works most of the time, I can survive this one document without having the preview. Leo
Re: Fw: Postscript preview
LB wrote: Which would not explain why futzing with the environment variables cured (or at least moved) the bug. Then again, perhaps I'm asking too much of the bug as far as consistency goes. This brings me back to my thesis that somewhere there is a buffer overflow. How/why it would involve both the file paths/names and environment variables beats me, but I'll take another shot on the developer list and see what shakes. This problem with preview is still not 100% gone. I have to change the PATH to point to a different copy of GS (Matlab copy or "official" copy) depending on which Lyx document I open. At this time, only the document that first exhibit this problem needs PATH to point to Matlab copy of GS for preview to work. All other documents I have opened so far work fine with the "official" version but show preview problem with Matlab copy of GS. Confused, Leo Why don't you make the Matlab copy of GS the same as the system? I open two instances of Windows Explorer to do this kind of work. In one Window, navigate to Matlab and note the name of the Gs directory. Right-click on the gs directory and delete it. It will be safe in the Recycle bin as long as you don't "empty the recycle bin". In the other window navigate to the system gs directory. Right-click on it and choose copy. Then paste it into the Matlab directory where the old matlab gs used to reside. Rename it to the same name as the old matlab gs. I suggest this because I don't know the matlab menu or command line just to change it to point to the system-wide gs. If for some reason Matlab doesn't make eps images, change it back. Rename the newly made gs directory which has been renamed to match the original matlab gs to something else. Then right-click and delete it. Otherwise you will have two gs directories in the Recycle bin and not know which one to "Restore" if they both have the same name. This is the way to do it if you don't know some technical syntax or deep matlab menu option. Remember not to use illegal characters when you create filenames for the .eps images. Do ordinary. Another thing to look at is to invoke GSview, under Start-> All programs. After it loads, at the top under Options, choose Advanced Configure. I was once shocked to discover that my gs.dll and gs include path pointed to gs 7.07 which was long gone; you want your current which in your case is 8.14 I think. Anyway, I think those entries are generated from reading the registry. And sometimes GS doesn't uninstall properly and leaves old traces in the registry which are erroneously detected & used. The idea here is that if 8.14 is making the eps then when LyX uses 8.14 it should be able to decipher them. This should work unless some command line switches/snytax invoking ghostscript has been changed from what worked with the old version but could be different in the newer gs version. That doesn't happen all that often so your chances should be good. This will avoid you having to edit the Path prefix in lyx back and forth, in order to change versions to accomodate the creating gs version. Good luck, Stephen
Re: Fw: Postscript preview
TechTonics wrote: LB wrote: This problem with preview is still not 100% gone. I have to change the PATH to point to a different copy of GS (Matlab copy or "official" copy) depending on which Lyx document I open. At this time, only the document that first exhibit this problem needs PATH to point to Matlab copy of GS for preview to work. All other documents I have opened so far work fine with the "official" version but show preview problem with Matlab copy of GS. Confused, Leo Why don't you make the Matlab copy of GS the same as the system? Don't forget to generate a new version of the problematic image(s) from Matlab again using the system gs 8.14. This idea isn't intended to fix the problem with the original mutant image created by the matlab gs, but to correct the current bad file(s) by making a new one and to fix future problems. Right-clicking in the taskbar(bottom)cascade = = Regards, Stephen
Re: Fw: Postscript preview
Why don't you make the Matlab copy of GS the same as the system? I tried that unsuccessfully already. Matlab generates the ps file even when I remove its GS directory completely. When I substitute Matlab GS with "official" GS, the figures still misbehave after I regenerate them from scratch with the "official" GS located in Matlab directory. Another thing to look at is to invoke GSview, under Start-> All programs. After it loads, at the top under Options, choose Advanced Configure. I was once shocked to discover that my gs.dll and gs include path pointed to gs 7.07 which was long gone; you want your current which in your case is 8.14 I think. Anyway, I think those entries are generated from reading the registry. And sometimes GS doesn't uninstall properly and leaves old traces in the registry which are erroneously detected & used. It points to 8.14 as needed. I give up. Preview works most of the time, I can survive this one document without having the preview. Leo
Re: Fw: Postscript preview
Which would not explain why futzing with the environment variables cured (or at least moved) the bug. Then again, perhaps I'm asking too much of the bug as far as consistency goes. This brings me back to my thesis that somewhere there is a buffer overflow. How/why it would involve both the file paths/names and environment variables beats me, but I'll take another shot on the developer list and see what shakes. This problem with preview is still not 100% gone. I have to change the PATH to point to a different copy of GS (Matlab copy or official copy) depending on which Lyx document I open. At this time, only the document that first exhibit this problem needs PATH to point to Matlab copy of GS for preview to work. All other documents I have opened so far work fine with the official version but show preview problem with Matlab copy of GS. Confused, Leo
Re: Fw: Postscript preview
Which would not explain why futzing with the environment variables cured (or at least moved) the bug. Then again, perhaps I'm asking too much of the bug as far as consistency goes. This brings me back to my thesis that somewhere there is a buffer overflow. How/why it would involve both the file paths/names and environment variables beats me, but I'll take another shot on the developer list and see what shakes. This problem with preview is still not 100% gone. I have to change the PATH to point to a different copy of GS (Matlab copy or official copy) depending on which Lyx document I open. At this time, only the document that first exhibit this problem needs PATH to point to Matlab copy of GS for preview to work. All other documents I have opened so far work fine with the official version but show preview problem with Matlab copy of GS. Confused, Leo
Re: Fw: Postscript preview
Which would not explain why futzing with the environment variables cured (or at least moved) the bug. Then again, perhaps I'm asking too much of the bug as far as consistency goes. This brings me back to my thesis that somewhere there is a buffer overflow. How/why it would involve both the file paths/names and environment variables beats me, but I'll take another shot on the developer list and see what shakes. This problem with preview is still not 100% gone. I have to change the PATH to point to a different copy of GS (Matlab copy or "official" copy) depending on which Lyx document I open. At this time, only the document that first exhibit this problem needs PATH to point to Matlab copy of GS for preview to work. All other documents I have opened so far work fine with the "official" version but show preview problem with Matlab copy of GS. Confused, Leo
Re: Fw: Postscript preview
I think this supports the possibility of a Ghostscript conflict and that Matlab comes with its own version of Gs. I actually have three versions of gs.exe. Cygwin has two. One in cygwin\bin directory and one in cygwin\usr\X11R6\bin directory. Matlab has its own version as well. My install of gs (8.14) has two files in bin directory: gswin32.exe and gswin32c.exe Please suggest what I can do to investigate this further. Leo
Re: Fw: Postscript preview
LB wrote: I think this supports the possibility of a Ghostscript conflict and that Matlab comes with its own version of Gs. I actually have three versions of gs.exe. Cygwin has two. One in cygwin\bin directory and one in cygwin\usr\X11R6\bin directory. Matlab has its own version as well. My install of gs (8.14) has two files in bin directory: gswin32.exe and gswin32c.exe Please suggest what I can do to investigate this further. Leo Having already generated the image files in MATLAB, try temporarily hiding all the Cygwin and Matlab copies of the GS executable (say by adding a $ to the start of their names, which is easy to undo afterward). Then run LyX and see if the images load properly. I'm not positive that ImageMagick runs the GS executable (as opposed to accessing a GS library directly), but I think it does. /Paul
Re: Fw: Postscript preview
LB wrote: I think this supports the possibility of a Ghostscript conflict and that Matlab comes with its own version of Gs. I actually have three versions of gs.exe. Cygwin has two. One in cygwin\bin directory and one in cygwin\usr\X11R6\bin directory. Matlab has its own version as well. My install of gs (8.14) has two files in bin directory: gswin32.exe and gswin32c.exe Please suggest what I can do to investigate this further. Leo Oops, forgot something. If I understood Stephen's concerns correctly, a second experiment might be in order -- having renamed the unofficial GS executables, try reproducing the images from Matlab using the official version of GS. (I'm not a Matlab user, so I don't know exactly what this would entail, but you might have to modify some setting in Matlab that holds the path to GS, or you might need the official GS bin directory on the command path, or worst case you might need to copy the official GS files, both executable and library, into the Matlab directory where the Matlab-installed GS currently lives.) /Paul
Re: Fw: Postscript preview
LB wrote: I think this supports the possibility of a Ghostscript conflict and that Matlab comes with its own version of Gs. I actually have three versions of gs.exe. Cygwin has two. One in cygwin\bin directory and one in cygwin\usr\X11R6\bin directory. Matlab has its own version as well. My install of gs (8.14) has two files in bin directory: gswin32.exe and gswin32c.exe Please suggest what I can do to investigate this further. Leo So far you reported that lyx.exe will always display the images but that lyx.bat will display some and not others and this is for Lyx1.4.2; that the test.ps you sent us now displays but you have another(s) which don't. LyX1.4.1 will display all images with either lyx.exe or lyx.bat. How about with Cygwin LyX? Check to see if changing the lyx1.4.2 bat with this line SET LC_ALL=en_EN to the lyx1.4.1 bat with this line SET LANG=en_EN and then test on the transgressing eps file. That is a quick first step. When I rename files which I'm going to rename later, I do it with 2 Windows Search: find file g*.exe in C:\cygwin, and then g*.exe in C:\GS?\ It makes it easy to keep visual track of the files you've changed for when you want to rename them back. Right-click on the filename with the mouse and rename by *prepending* a $ to the file. You know CygLyX1.4.2 is available. :-) Regards, Stephen
Re: Fw: Postscript preview
Paul A. Rubin wrote: LB wrote: I think this supports the possibility of a Ghostscript conflict and that Matlab comes with its own version of Gs. I actually have three versions of gs.exe. Cygwin has two. One in cygwin\bin directory and one in cygwin\usr\X11R6\bin directory. Matlab has its own version as well. My install of gs (8.14) has two files in bin directory: gswin32.exe and gswin32c.exe Please suggest what I can do to investigate this further. Leo Oops, forgot something. If I understood Stephen's concerns correctly, a second experiment might be in order -- having renamed the unofficial GS executables, try reproducing the images from Matlab using the official version of GS. (I'm not a Matlab user, so I don't know exactly what this would entail, but you might have to modify some setting in Matlab that holds the path to GS, or you might need the official GS bin directory on the command path, or worst case you might need to copy the official GS files, both executable and library, into the Matlab directory where the Matlab-installed GS currently lives.) /Paul Your starting idea seems the easiest place to start. LyX was configured with the system GS. It is now going to use the matlab gs. Does the matlab gs need to be put in the beginning of Path_prefix? Reconfigure/Restart? [SET LC_ALL=en_EN] I think that stands for Locale. I suggested changing that entry in the 1.4.2 lyx.bat to SET LANG=en_EN because I think Leo said both Lyx.exe and lyx.bat work for all images in 1.4.1 This idea and your first approach seem to be less complex, faster, and just as likely to be revealing? We are expecting the matlab gs to work in all cases?! Maybe change the batfile and test on an ornery critter. If it fails, change it back. Then rename the other gs versions and test with matlab gs exclusively. If that fails we know it is likely just the batfile. Change the batfile content again to set lang=en_EN and test with exclusive matlab gs. Since cygwin gs is not used and this method rules out a version conflict this had just better work! To test system gs *and* with system gs substituted for matlab gs also eliminates version GS conflict but the testing procedure may be convoluted and I don't know if there is a Grothendieck dimensional+. +meaning I will have run out of ideas and will recluse, Stephen c Best regards,
Re: Fw: Postscript preview
LB wrote: Having already generated the image files in MATLAB, try temporarily hiding all the Cygwin and Matlab copies of the GS executable (say by adding a $ to the start of their names, which is easy to undo afterward). Then run LyX and see if the images load properly. No they don't. Leo No they don't... and you tried with both lyx.exe and lyx.bat? IOW, has forcing LyX to use the system-wide GS created a change in behavior; like lyx.exe no longer works the same. I think lyx.exe now failing would mean that it had been using the matlab gs and can no longer do so. Matlab gs creates the file so one would expect it to load the file when LyX uses it. LyX.bat would be using the system gs and working in cases where the matlab gs file creation held no incompatibilities. Which is why I ask if you tested both lyx.exe and lyx.bat. If nothing has changed then we have gained no information. You could have changed system gs to a $ and tested LyX using matlab gs to render the image (after renaming). Or if lyx.exe fails, then this step should enable lyx.bat and the fix would be to put the matlab gs at beginning of LyX Path_prefix. Maybe changing LC to Lang is equivalent. Too many maybes bring Bats to the Belfry, Stephen
Re: Fw: Postscript preview
Your starting idea seems the easiest place to start. LyX was configured with the system GS. It is now going to use the matlab gs. Does the matlab gs need to be put in the beginning of Path_prefix? Reconfigure/Restart? [SET LC_ALL=en_EN] I think that stands for Locale. I suggested changing that entry in the 1.4.2 lyx.bat to SET LANG=en_EN because I think Leo said both Lyx.exe and lyx.bat work for all images in 1.4.1 I set PATH in lyx to point to Matlab gs. I renamed gs.exe files in Cygwin and gswin32 files in gs8.14 directories, so that the only gs I have is in Matlab directory. After reconfigure and restart, I get the same preview problem (also when lyx.bat has LANG=en_EN). I have tried this with lyx.bat and lyx.exe. The only difference between lyx.bat and lyx.exe is that the preview problem jumps to different figures (all generated in Matlab). This idea and your first approach seem to be less complex, faster, and just as likely to be revealing? We are expecting the matlab gs to work in all cases?! I'm not sure whether Matlab uses gs.exe to generate the ps files because after renaming gs.exe in the Matlab directory, Matlab still managed to genereate the ps file. BTW in Matlab I use commands: print -depsc2 -r300 -f6 C:\figname.ps print -depsc -r300 -f6 C:\figname.ps to generate ps files. I also changed the .ps to .eps. Another way of generating figures in Matlab is by using File menu. All of these methods seem to make no difference as far as preview of the figures is concerned. I have renamed all gs*.exe programs I could find on my computer (including the once in the hidden directories) with old_gs*.exe. Lyx still previews most figures (.ps and .bmp) ok with the exception of the once that give me grief. Can the system track changes to the files names??? I did not think so. But if it does not, how can Lyx preview figures? I'm tired of this random problem. I think I have to live with it until something else I install in the future that will make things either better or worse... Leo
Re: Fw: Postscript preview
I have changed the names (decreased by one character) of the figures that were given me problems and they are now previewing fine!!! Thanks Leo
Re: Fw: Postscript preview
I have changed the names (decreased by one character) of the figures that were given me problems and they are now previewing fine!!! Clarification: it works when Lyx path points to Matlab gs. When I change path to the official gs the preview stops working. I have installed matlab after my original version of gs was installed. However, I think I have updated gs at the time I installed 1.4.2. It looks like with the old versions of lyx, Matlab's gs was always used as it was installed later, while with 1.4.2 the new version of gs is the default and that version is not compatible with the matlab for some reason. Leo
Re: Fw: Postscript preview
LB wrote: I have changed the names (decreased by one character) of the figures that were given me problems and they are now previewing fine!!! Thanks Leo Great! One of the great Presidents said persistence is a far better quality than talent or genius. Still seems like a surprising way to fix it unless the 1 character decrease was removing a forbidden character used in the filenames. - Stephen Nothing in the world can take the place of persistence. Talent will not; nothing is more common than unsuccessful people with talent. Genius will not; unrewarded genius is almost a proverb. Education will not; the world is full of educated derelicts. Persistence and determination alone are omnipotent. The slogan press on has solved and always will solve the problems of the human race. Calvin Coolidge
Re: Fw: Postscript preview
TechTonics wrote: LB wrote: I have changed the names (decreased by one character) of the figures that were given me problems and they are now previewing fine!!! Great! One of the great Presidents said persistence is a far better quality than talent or genius. Still seems like a surprising way to fix it unless the 1 character decrease was removing a forbidden character used in the filenames. Which would not explain why futzing with the environment variables cured (or at least moved) the bug. Then again, perhaps I'm asking too much of the bug as far as consistency goes. This brings me back to my thesis that somewhere there is a buffer overflow. How/why it would involve both the file paths/names and environment variables beats me, but I'll take another shot on the developer list and see what shakes. /Paul
Re: Fw: Postscript preview
I think this supports the possibility of a Ghostscript conflict and that Matlab comes with its own version of Gs. I actually have three versions of gs.exe. Cygwin has two. One in cygwin\bin directory and one in cygwin\usr\X11R6\bin directory. Matlab has its own version as well. My install of gs (8.14) has two files in bin directory: gswin32.exe and gswin32c.exe Please suggest what I can do to investigate this further. Leo
Re: Fw: Postscript preview
LB wrote: I think this supports the possibility of a Ghostscript conflict and that Matlab comes with its own version of Gs. I actually have three versions of gs.exe. Cygwin has two. One in cygwin\bin directory and one in cygwin\usr\X11R6\bin directory. Matlab has its own version as well. My install of gs (8.14) has two files in bin directory: gswin32.exe and gswin32c.exe Please suggest what I can do to investigate this further. Leo Having already generated the image files in MATLAB, try temporarily hiding all the Cygwin and Matlab copies of the GS executable (say by adding a $ to the start of their names, which is easy to undo afterward). Then run LyX and see if the images load properly. I'm not positive that ImageMagick runs the GS executable (as opposed to accessing a GS library directly), but I think it does. /Paul
Re: Fw: Postscript preview
LB wrote: I think this supports the possibility of a Ghostscript conflict and that Matlab comes with its own version of Gs. I actually have three versions of gs.exe. Cygwin has two. One in cygwin\bin directory and one in cygwin\usr\X11R6\bin directory. Matlab has its own version as well. My install of gs (8.14) has two files in bin directory: gswin32.exe and gswin32c.exe Please suggest what I can do to investigate this further. Leo Oops, forgot something. If I understood Stephen's concerns correctly, a second experiment might be in order -- having renamed the unofficial GS executables, try reproducing the images from Matlab using the official version of GS. (I'm not a Matlab user, so I don't know exactly what this would entail, but you might have to modify some setting in Matlab that holds the path to GS, or you might need the official GS bin directory on the command path, or worst case you might need to copy the official GS files, both executable and library, into the Matlab directory where the Matlab-installed GS currently lives.) /Paul
Re: Fw: Postscript preview
LB wrote: I think this supports the possibility of a Ghostscript conflict and that Matlab comes with its own version of Gs. I actually have three versions of gs.exe. Cygwin has two. One in cygwin\bin directory and one in cygwin\usr\X11R6\bin directory. Matlab has its own version as well. My install of gs (8.14) has two files in bin directory: gswin32.exe and gswin32c.exe Please suggest what I can do to investigate this further. Leo So far you reported that lyx.exe will always display the images but that lyx.bat will display some and not others and this is for Lyx1.4.2; that the test.ps you sent us now displays but you have another(s) which don't. LyX1.4.1 will display all images with either lyx.exe or lyx.bat. How about with Cygwin LyX? Check to see if changing the lyx1.4.2 bat with this line SET LC_ALL=en_EN to the lyx1.4.1 bat with this line SET LANG=en_EN and then test on the transgressing eps file. That is a quick first step. When I rename files which I'm going to rename later, I do it with 2 Windows Search: find file g*.exe in C:\cygwin, and then g*.exe in C:\GS?\ It makes it easy to keep visual track of the files you've changed for when you want to rename them back. Right-click on the filename with the mouse and rename by *prepending* a $ to the file. You know CygLyX1.4.2 is available. :-) Regards, Stephen
Re: Fw: Postscript preview
Paul A. Rubin wrote: LB wrote: I think this supports the possibility of a Ghostscript conflict and that Matlab comes with its own version of Gs. I actually have three versions of gs.exe. Cygwin has two. One in cygwin\bin directory and one in cygwin\usr\X11R6\bin directory. Matlab has its own version as well. My install of gs (8.14) has two files in bin directory: gswin32.exe and gswin32c.exe Please suggest what I can do to investigate this further. Leo Oops, forgot something. If I understood Stephen's concerns correctly, a second experiment might be in order -- having renamed the unofficial GS executables, try reproducing the images from Matlab using the official version of GS. (I'm not a Matlab user, so I don't know exactly what this would entail, but you might have to modify some setting in Matlab that holds the path to GS, or you might need the official GS bin directory on the command path, or worst case you might need to copy the official GS files, both executable and library, into the Matlab directory where the Matlab-installed GS currently lives.) /Paul Your starting idea seems the easiest place to start. LyX was configured with the system GS. It is now going to use the matlab gs. Does the matlab gs need to be put in the beginning of Path_prefix? Reconfigure/Restart? [SET LC_ALL=en_EN] I think that stands for Locale. I suggested changing that entry in the 1.4.2 lyx.bat to SET LANG=en_EN because I think Leo said both Lyx.exe and lyx.bat work for all images in 1.4.1 This idea and your first approach seem to be less complex, faster, and just as likely to be revealing? We are expecting the matlab gs to work in all cases?! Maybe change the batfile and test on an ornery critter. If it fails, change it back. Then rename the other gs versions and test with matlab gs exclusively. If that fails we know it is likely just the batfile. Change the batfile content again to set lang=en_EN and test with exclusive matlab gs. Since cygwin gs is not used and this method rules out a version conflict this had just better work! To test system gs *and* with system gs substituted for matlab gs also eliminates version GS conflict but the testing procedure may be convoluted and I don't know if there is a Grothendieck dimensional+. +meaning I will have run out of ideas and will recluse, Stephen c Best regards,
Re: Fw: Postscript preview
LB wrote: Having already generated the image files in MATLAB, try temporarily hiding all the Cygwin and Matlab copies of the GS executable (say by adding a $ to the start of their names, which is easy to undo afterward). Then run LyX and see if the images load properly. No they don't. Leo No they don't... and you tried with both lyx.exe and lyx.bat? IOW, has forcing LyX to use the system-wide GS created a change in behavior; like lyx.exe no longer works the same. I think lyx.exe now failing would mean that it had been using the matlab gs and can no longer do so. Matlab gs creates the file so one would expect it to load the file when LyX uses it. LyX.bat would be using the system gs and working in cases where the matlab gs file creation held no incompatibilities. Which is why I ask if you tested both lyx.exe and lyx.bat. If nothing has changed then we have gained no information. You could have changed system gs to a $ and tested LyX using matlab gs to render the image (after renaming). Or if lyx.exe fails, then this step should enable lyx.bat and the fix would be to put the matlab gs at beginning of LyX Path_prefix. Maybe changing LC to Lang is equivalent. Too many maybes bring Bats to the Belfry, Stephen
Re: Fw: Postscript preview
Your starting idea seems the easiest place to start. LyX was configured with the system GS. It is now going to use the matlab gs. Does the matlab gs need to be put in the beginning of Path_prefix? Reconfigure/Restart? [SET LC_ALL=en_EN] I think that stands for Locale. I suggested changing that entry in the 1.4.2 lyx.bat to SET LANG=en_EN because I think Leo said both Lyx.exe and lyx.bat work for all images in 1.4.1 I set PATH in lyx to point to Matlab gs. I renamed gs.exe files in Cygwin and gswin32 files in gs8.14 directories, so that the only gs I have is in Matlab directory. After reconfigure and restart, I get the same preview problem (also when lyx.bat has LANG=en_EN). I have tried this with lyx.bat and lyx.exe. The only difference between lyx.bat and lyx.exe is that the preview problem jumps to different figures (all generated in Matlab). This idea and your first approach seem to be less complex, faster, and just as likely to be revealing? We are expecting the matlab gs to work in all cases?! I'm not sure whether Matlab uses gs.exe to generate the ps files because after renaming gs.exe in the Matlab directory, Matlab still managed to genereate the ps file. BTW in Matlab I use commands: print -depsc2 -r300 -f6 C:\figname.ps print -depsc -r300 -f6 C:\figname.ps to generate ps files. I also changed the .ps to .eps. Another way of generating figures in Matlab is by using File menu. All of these methods seem to make no difference as far as preview of the figures is concerned. I have renamed all gs*.exe programs I could find on my computer (including the once in the hidden directories) with old_gs*.exe. Lyx still previews most figures (.ps and .bmp) ok with the exception of the once that give me grief. Can the system track changes to the files names??? I did not think so. But if it does not, how can Lyx preview figures? I'm tired of this random problem. I think I have to live with it until something else I install in the future that will make things either better or worse... Leo
Re: Fw: Postscript preview
I have changed the names (decreased by one character) of the figures that were given me problems and they are now previewing fine!!! Thanks Leo
Re: Fw: Postscript preview
I have changed the names (decreased by one character) of the figures that were given me problems and they are now previewing fine!!! Clarification: it works when Lyx path points to Matlab gs. When I change path to the official gs the preview stops working. I have installed matlab after my original version of gs was installed. However, I think I have updated gs at the time I installed 1.4.2. It looks like with the old versions of lyx, Matlab's gs was always used as it was installed later, while with 1.4.2 the new version of gs is the default and that version is not compatible with the matlab for some reason. Leo
Re: Fw: Postscript preview
LB wrote: I have changed the names (decreased by one character) of the figures that were given me problems and they are now previewing fine!!! Thanks Leo Great! One of the great Presidents said persistence is a far better quality than talent or genius. Still seems like a surprising way to fix it unless the 1 character decrease was removing a forbidden character used in the filenames. - Stephen Nothing in the world can take the place of persistence. Talent will not; nothing is more common than unsuccessful people with talent. Genius will not; unrewarded genius is almost a proverb. Education will not; the world is full of educated derelicts. Persistence and determination alone are omnipotent. The slogan press on has solved and always will solve the problems of the human race. Calvin Coolidge
Re: Fw: Postscript preview
TechTonics wrote: LB wrote: I have changed the names (decreased by one character) of the figures that were given me problems and they are now previewing fine!!! Great! One of the great Presidents said persistence is a far better quality than talent or genius. Still seems like a surprising way to fix it unless the 1 character decrease was removing a forbidden character used in the filenames. Which would not explain why futzing with the environment variables cured (or at least moved) the bug. Then again, perhaps I'm asking too much of the bug as far as consistency goes. This brings me back to my thesis that somewhere there is a buffer overflow. How/why it would involve both the file paths/names and environment variables beats me, but I'll take another shot on the developer list and see what shakes. /Paul
Re: Fw: Postscript preview
I think this supports the possibility of a Ghostscript conflict and that Matlab comes with its own version of Gs. I actually have three versions of gs.exe. Cygwin has two. One in cygwin\bin directory and one in cygwin\usr\X11R6\bin directory. Matlab has its own version as well. My install of gs (8.14) has two files in bin directory: gswin32.exe and gswin32c.exe Please suggest what I can do to investigate this further. Leo
Re: Fw: Postscript preview
LB wrote: I think this supports the possibility of a Ghostscript conflict and that Matlab comes with its own version of Gs. I actually have three versions of gs.exe. Cygwin has two. One in cygwin\bin directory and one in cygwin\usr\X11R6\bin directory. Matlab has its own version as well. My install of gs (8.14) has two files in bin directory: gswin32.exe and gswin32c.exe Please suggest what I can do to investigate this further. Leo Having already generated the image files in MATLAB, try temporarily hiding all the Cygwin and Matlab copies of the GS executable (say by adding a $ to the start of their names, which is easy to undo afterward). Then run LyX and see if the images load properly. I'm not positive that ImageMagick runs the GS executable (as opposed to accessing a GS library directly), but I think it does. /Paul
Re: Fw: Postscript preview
LB wrote: I think this supports the possibility of a Ghostscript conflict and that Matlab comes with its own version of Gs. I actually have three versions of gs.exe. Cygwin has two. One in cygwin\bin directory and one in cygwin\usr\X11R6\bin directory. Matlab has its own version as well. My install of gs (8.14) has two files in bin directory: gswin32.exe and gswin32c.exe Please suggest what I can do to investigate this further. Leo Oops, forgot something. If I understood Stephen's concerns correctly, a second experiment might be in order -- having renamed the "unofficial" GS executables, try reproducing the images from Matlab using the "official" version of GS. (I'm not a Matlab user, so I don't know exactly what this would entail, but you might have to modify some setting in Matlab that holds the path to GS, or you might need the official GS bin directory on the command path, or worst case you might need to copy the official GS files, both executable and library, into the Matlab directory where the Matlab-installed GS currently lives.) /Paul
Re: Fw: Postscript preview
LB wrote: I think this supports the possibility of a Ghostscript conflict and that Matlab comes with its own version of Gs. I actually have three versions of gs.exe. Cygwin has two. One in cygwin\bin directory and one in cygwin\usr\X11R6\bin directory. Matlab has its own version as well. My install of gs (8.14) has two files in bin directory: gswin32.exe and gswin32c.exe Please suggest what I can do to investigate this further. Leo So far you reported that lyx.exe will always display the images but that lyx.bat will display some and not others and this is for Lyx1.4.2; that the test.ps you sent us now displays but you have another(s) which don't. LyX1.4.1 will display all images with either lyx.exe or lyx.bat. How about with Cygwin LyX? Check to see if changing the lyx1.4.2 bat with this line SET LC_ALL=en_EN to the lyx1.4.1 bat with this line SET LANG=en_EN and then test on the transgressing eps file. That is a quick first step. When I rename files which I'm going to rename later, I do it with 2 Windows Search: find file g*.exe in C:\cygwin, and then g*.exe in C:\GS?\ It makes it easy to keep visual track of the files you've changed for when you want to rename them back. Right-click on the filename with the mouse and rename by *prepending* a $ to the file. You know CygLyX1.4.2 is available. :-) Regards, Stephen
Re: Fw: Postscript preview
Paul A. Rubin wrote: LB wrote: I think this supports the possibility of a Ghostscript conflict and that Matlab comes with its own version of Gs. I actually have three versions of gs.exe. Cygwin has two. One in cygwin\bin directory and one in cygwin\usr\X11R6\bin directory. Matlab has its own version as well. My install of gs (8.14) has two files in bin directory: gswin32.exe and gswin32c.exe Please suggest what I can do to investigate this further. Leo Oops, forgot something. If I understood Stephen's concerns correctly, a second experiment might be in order -- having renamed the "unofficial" GS executables, try reproducing the images from Matlab using the "official" version of GS. (I'm not a Matlab user, so I don't know exactly what this would entail, but you might have to modify some setting in Matlab that holds the path to GS, or you might need the official GS bin directory on the command path, or worst case you might need to copy the official GS files, both executable and library, into the Matlab directory where the Matlab-installed GS currently lives.) /Paul Your starting idea seems the easiest place to start. LyX was configured with the system GS. It is now going to use the matlab gs. Does the matlab gs need to be put in the beginning of Path_prefix? Reconfigure/Restart? [SET LC_ALL=en_EN] I think that stands for Locale. I suggested changing that entry in the 1.4.2 lyx.bat to SET LANG=en_EN because I think Leo said both Lyx.exe and lyx.bat work for all images in 1.4.1 This idea and your first approach seem to be less complex, faster, and just as likely to be revealing? We are expecting the matlab gs to work in all cases?! Maybe change the batfile and test on an ornery critter. If it fails, change it back. Then rename the other gs versions and test with matlab gs exclusively. If that fails we know it is likely just the batfile. Change the batfile content again to set lang=en_EN and test with exclusive matlab gs. Since cygwin gs is not used and this method rules out a version conflict this had just better work! To test system gs *and* with system gs substituted for matlab gs also eliminates version GS conflict but the testing procedure may be convoluted and I don't know if there is a Grothendieck dimensional+. +meaning I will have run out of ideas and will recluse, Stephen c Best regards,
Re: Fw: Postscript preview
LB wrote: Having already generated the image files in MATLAB, try temporarily hiding all the Cygwin and Matlab copies of the GS executable (say by adding a $ to the start of their names, which is easy to undo afterward). Then run LyX and see if the images load properly. No they don't. Leo No they don't... and you tried with both lyx.exe and lyx.bat? IOW, has forcing LyX to use the system-wide GS created a change in behavior; like lyx.exe no longer works the same. I think lyx.exe now failing would mean that it had been using the matlab gs and can no longer do so. Matlab gs creates the file so one would expect it to load the file when LyX uses it. LyX.bat would be using the system gs and working in cases where the matlab gs file creation held no incompatibilities. Which is why I ask if you tested both lyx.exe and lyx.bat. If nothing has changed then we have gained no information. You could have changed system gs to a $ and tested LyX using matlab gs to render the image (after renaming). Or if lyx.exe fails, then this step should enable lyx.bat and the fix would be to put the matlab gs at beginning of LyX Path_prefix. Maybe changing LC to Lang is equivalent. Too many maybes bring Bats to the Belfry, Stephen
Re: Fw: Postscript preview
Your starting idea seems the easiest place to start. LyX was configured with the system GS. It is now going to use the matlab gs. Does the matlab gs need to be put in the beginning of Path_prefix? Reconfigure/Restart? [SET LC_ALL=en_EN] I think that stands for Locale. I suggested changing that entry in the 1.4.2 lyx.bat to SET LANG=en_EN because I think Leo said both Lyx.exe and lyx.bat work for all images in 1.4.1 I set PATH in lyx to point to Matlab gs. I renamed gs.exe files in Cygwin and gswin32 files in gs8.14 directories, so that the only gs I have is in Matlab directory. After reconfigure and restart, I get the same preview problem (also when lyx.bat has LANG=en_EN). I have tried this with lyx.bat and lyx.exe. The only difference between lyx.bat and lyx.exe is that the preview problem jumps to different figures (all generated in Matlab). This idea and your first approach seem to be less complex, faster, and just as likely to be revealing? We are expecting the matlab gs to work in all cases?! I'm not sure whether Matlab uses gs.exe to generate the ps files because after renaming gs.exe in the Matlab directory, Matlab still managed to genereate the ps file. BTW in Matlab I use commands: print -depsc2 -r300 -f6 C:\figname.ps print -depsc -r300 -f6 C:\figname.ps to generate ps files. I also changed the .ps to .eps. Another way of generating figures in Matlab is by using File menu. All of these methods seem to make no difference as far as preview of the figures is concerned. I have renamed all gs*.exe programs I could find on my computer (including the once in the hidden directories) with old_gs*.exe. Lyx still previews most figures (.ps and .bmp) ok with the exception of the once that give me grief. Can the system track changes to the files names??? I did not think so. But if it does not, how can Lyx preview figures? I'm tired of this random problem. I think I have to live with it until something else I install in the future that will make things either better or worse... Leo
Re: Fw: Postscript preview
I have changed the names (decreased by one character) of the figures that were given me problems and they are now previewing fine!!! Thanks Leo
Re: Fw: Postscript preview
I have changed the names (decreased by one character) of the figures that were given me problems and they are now previewing fine!!! Clarification: it works when Lyx path points to Matlab gs. When I change path to the "official" gs the preview stops working. I have installed matlab after my original version of gs was installed. However, I think I have updated gs at the time I installed 1.4.2. It looks like with the old versions of lyx, Matlab's gs was always used as it was installed later, while with 1.4.2 the new version of gs is the default and that version is not compatible with the matlab for some reason. Leo
Re: Fw: Postscript preview
LB wrote: I have changed the names (decreased by one character) of the figures that were given me problems and they are now previewing fine!!! Thanks Leo Great! One of the great Presidents said persistence is a far better quality than talent or genius. Still seems like a surprising way to fix it unless the 1 character decrease was removing a forbidden character used in the filenames. - Stephen "Nothing in the world can take the place of persistence. Talent will not; nothing is more common than unsuccessful people with talent. Genius will not; unrewarded genius is almost a proverb. Education will not; the world is full of educated derelicts. Persistence and determination alone are omnipotent. The slogan "press on" has solved and always will solve the problems of the human race." Calvin Coolidge
Re: Fw: Postscript preview
TechTonics wrote: LB wrote: I have changed the names (decreased by one character) of the figures that were given me problems and they are now previewing fine!!! Great! One of the great Presidents said persistence is a far better quality than talent or genius. Still seems like a surprising way to fix it unless the 1 character decrease was removing a forbidden character used in the filenames. Which would not explain why futzing with the environment variables cured (or at least moved) the bug. Then again, perhaps I'm asking too much of the bug as far as consistency goes. This brings me back to my thesis that somewhere there is a buffer overflow. How/why it would involve both the file paths/names and environment variables beats me, but I'll take another shot on the developer list and see what shakes. /Paul
Re: Fw: Postscript preview
Paul A. Rubin wrote: LB wrote: Ok, it tried this. I commented out SET LC_ALL=en_EN. This resulted in a different image having the preview problem. I placed SET XX=Y in lyx.bat and the preview problem moved back to the original image. The same happens when I comment out the other line in the lyx.bat. I also added extra lines in lyx.bat such as SET XX=Y this however did not make any difference as far as image preview is concerned. This is again confusing, though perhaps no more confusing than the fact that deleting unneeded environment variables (other than LC_ALL and the aiksaurus one) did not help. Another puzzling thing is that the preview problem jumps between two specific figures eventhough I have many figures in the document and many of them are generated with Matlab. The preview problem however never affects figures generated with other programs. Is there anything that the names/paths of the two affected figures have in common which is not shared by the other files. For instance, are they the longest paths, do they lie deeper in the directory tree than other figures, ... ? Stephen's idea of a second Ghostscript installation strikes me as possible but unlikely (and unlikely to be the culprit), since there would need to be something causing ImageMagick to alternate between the two GS installations on a figure-by-figure basis within the document (meaning that something in the figure names/paths would have to be triggering the switching). Also, Mathematica exports EPS without using GS and without installing its own GS, so I suspect the same might be true of MATLAB. Still, the whole bug is unlikely, so we shouldn't presume anything. It would be nice if we could intercept the call from IM to GS and see what's being passed, but so far I have not figured out how. /Paul - http://www.mathworks.com/support/solutions/data/1-ZBALJ.html?solution=1-ZBALJ The MATLAB Component Runtime (MCR) 7.0 and 7.1 do not contain a copy of the GhostScript program included with MATLAB. Therefore, applications deployed on a target machine rely on a locally- installed version of GhostScript, if one exists, for exporting some graphics. Since the version of GhostScript installed on the target machine may be different than the one included with MATLAB, the command line parameters potentially may be different as well. This difference causes an error in some instances. I think this supports the possibility of a Ghostscript conflict and that Matlab comes with its own version of Gs. With an earlier distro of LyX I also had XemTeX installed which comes with its own Gs. It had a different version of Gs and the .dlls conflicted with LyX which was solved by moving Xemtex to the end of Windows Path. I'm pretty sure that lyx.exe checks the LyX directory for various executables because Enrico's batfiles seem to use this principle. I'm not so sure about lyx.bat because I thought it was possible that those set commands could change which Gs was invoked. I don't know what they do, the consequences of their mechanism. One major difference in the our environments and Leo's is that he has Matlab installed and we don't. I'm pretty sure that Matlab has Gs installed since I've googled and seen it listed as a sub-dir of Matlab's directory structure (though only for Linux). It should take Leo less than thirty seconds to find out with Win Explorer. I 've a hunch that his Matlab Gs version is earlier than his system Gs, supposing that there are two instances. My troubleshooting idea was to eliminate both ways a Gs version conflict could happen and to use lyx.exe first before lyx.bat to see if the .eps file itself (command line parameters used) perhaps had a version glitch and I thought it would take about 5 minutes (without Matlab running) to see if this affected the problem. I think the Matlab doc I just reported upon supports this possibility. We also have a more recent version of system Ghostscript. My Sherlock Holmes sig, (inmates on death row tell jokes by #) Stephen
Re: Fw: Postscript preview
Stephen Harris wrote: The MATLAB Component Runtime (MCR) 7.0 and 7.1 do not contain a copy of the GhostScript program included with MATLAB. Therefore, applications deployed on a target machine rely on a locally- installed version of GhostScript, if one exists, for exporting some graphics. Since the version of GhostScript installed on the target machine may be different than the one included with MATLAB, the command line parameters potentially may be different as well. This difference causes an error in some instances. I think this supports the possibility of a Ghostscript conflict and that Matlab comes with its own version of Gs. It does indeed. So I agree that hypothetically Leo's MATLAB installation could be generating PS files (using it's own copy of GS) that would be indigestible to LyX-ImageMagick-GS (using a different copy of GS in the last step). That still raises the question of why those images would be successfully displayed in LyX (same LyX-ImageMagick-GS sequence) if an environment variable is deleted ... unless deletion of the environment variable affected which copy of GS was used (both on the command path?) ... in which case the bug would disappear, not switch to a different image. All that said, this bug is clearly not playing fair, so it would be a good idea for Leo to check into this just to rule it out. /Paul
Re: Fw: Postscript preview
Paul A. Rubin wrote: Stephen Harris wrote: The MATLAB Component Runtime (MCR) 7.0 and 7.1 do not contain a copy of the GhostScript program included with MATLAB. Therefore, applications deployed on a target machine rely on a locally- installed version of GhostScript, if one exists, for exporting some graphics. Since the version of GhostScript installed on the target machine may be different than the one included with MATLAB, the command line parameters potentially may be different as well. This difference causes an error in some instances. I think this supports the possibility of a Ghostscript conflict and that Matlab comes with its own version of Gs. It does indeed. So I agree that hypothetically Leo's MATLAB installation could be generating PS files (using it's own copy of GS) that would be indigestible to LyX-ImageMagick-GS (using a different copy of GS in the last step). That still raises the question of why those images would be successfully displayed in LyX (same LyX-ImageMagick-GS sequence) if an environment variable is deleted ... unless deletion of the environment variable affected which copy of GS was used (both on the command path?) ... in which case the bug would disappear, not switch to a different image. All that said, this bug is clearly not playing fair, so it would be a good idea for Leo to check into this just to rule it out. /Paul Yes there has to be another dimension to this. Recall he reinstalled LyX to C:\Lyx\lyx14 and the original problem files, I think it was test.ps, displayed Ok, but then another figure reared its ugly wolverine head. I would think that means that only some files are produced with the problem--either the same gs executable produces files which vary in compatibility or maybe system gs is producing the eps and it sometimes can't be read by an older matlab gs executable. Well, that is getting pretty thin. Maybe he could use the 1.4.1 lyx.bat and put Python at the beginning of the Path_prefix and try it and if it doesn't work, then try ghostscript at the beginning of Path_prefix also, but I think it is already. It would seem that the set variables in lyx1.4.2 batfile would have to part of it, but I don't know what they mean and they don't show up LC_ALL I will google one more time matlab and aikasaurus but I think that is just for Aspell. I'm not feeling well and can't concentrate. I've been up for two days fighting with a virus and am tired and have lost one partition on my hard drive. I guess its a trojan. Nope, I got a hit on allosaurus and matlab, but no aikasaurus. It's a Linux critter anyway. Regards, Stephen
Re: Fw: Postscript preview
Paul A. Rubin wrote: LB wrote: Ok, it tried this. I commented out SET LC_ALL=en_EN. This resulted in a different image having the preview problem. I placed SET XX=Y in lyx.bat and the preview problem moved back to the original image. The same happens when I comment out the other line in the lyx.bat. I also added extra lines in lyx.bat such as SET XX=Y this however did not make any difference as far as image preview is concerned. This is again confusing, though perhaps no more confusing than the fact that deleting unneeded environment variables (other than LC_ALL and the aiksaurus one) did not help. Another puzzling thing is that the preview problem jumps between two specific figures eventhough I have many figures in the document and many of them are generated with Matlab. The preview problem however never affects figures generated with other programs. Is there anything that the names/paths of the two affected figures have in common which is not shared by the other files. For instance, are they the longest paths, do they lie deeper in the directory tree than other figures, ... ? Stephen's idea of a second Ghostscript installation strikes me as possible but unlikely (and unlikely to be the culprit), since there would need to be something causing ImageMagick to alternate between the two GS installations on a figure-by-figure basis within the document (meaning that something in the figure names/paths would have to be triggering the switching). Also, Mathematica exports EPS without using GS and without installing its own GS, so I suspect the same might be true of MATLAB. Still, the whole bug is unlikely, so we shouldn't presume anything. It would be nice if we could intercept the call from IM to GS and see what's being passed, but so far I have not figured out how. /Paul - http://www.mathworks.com/support/solutions/data/1-ZBALJ.html?solution=1-ZBALJ The MATLAB Component Runtime (MCR) 7.0 and 7.1 do not contain a copy of the GhostScript program included with MATLAB. Therefore, applications deployed on a target machine rely on a locally- installed version of GhostScript, if one exists, for exporting some graphics. Since the version of GhostScript installed on the target machine may be different than the one included with MATLAB, the command line parameters potentially may be different as well. This difference causes an error in some instances. I think this supports the possibility of a Ghostscript conflict and that Matlab comes with its own version of Gs. With an earlier distro of LyX I also had XemTeX installed which comes with its own Gs. It had a different version of Gs and the .dlls conflicted with LyX which was solved by moving Xemtex to the end of Windows Path. I'm pretty sure that lyx.exe checks the LyX directory for various executables because Enrico's batfiles seem to use this principle. I'm not so sure about lyx.bat because I thought it was possible that those set commands could change which Gs was invoked. I don't know what they do, the consequences of their mechanism. One major difference in the our environments and Leo's is that he has Matlab installed and we don't. I'm pretty sure that Matlab has Gs installed since I've googled and seen it listed as a sub-dir of Matlab's directory structure (though only for Linux). It should take Leo less than thirty seconds to find out with Win Explorer. I 've a hunch that his Matlab Gs version is earlier than his system Gs, supposing that there are two instances. My troubleshooting idea was to eliminate both ways a Gs version conflict could happen and to use lyx.exe first before lyx.bat to see if the .eps file itself (command line parameters used) perhaps had a version glitch and I thought it would take about 5 minutes (without Matlab running) to see if this affected the problem. I think the Matlab doc I just reported upon supports this possibility. We also have a more recent version of system Ghostscript. My Sherlock Holmes sig, (inmates on death row tell jokes by #) Stephen
Re: Fw: Postscript preview
Stephen Harris wrote: The MATLAB Component Runtime (MCR) 7.0 and 7.1 do not contain a copy of the GhostScript program included with MATLAB. Therefore, applications deployed on a target machine rely on a locally- installed version of GhostScript, if one exists, for exporting some graphics. Since the version of GhostScript installed on the target machine may be different than the one included with MATLAB, the command line parameters potentially may be different as well. This difference causes an error in some instances. I think this supports the possibility of a Ghostscript conflict and that Matlab comes with its own version of Gs. It does indeed. So I agree that hypothetically Leo's MATLAB installation could be generating PS files (using it's own copy of GS) that would be indigestible to LyX-ImageMagick-GS (using a different copy of GS in the last step). That still raises the question of why those images would be successfully displayed in LyX (same LyX-ImageMagick-GS sequence) if an environment variable is deleted ... unless deletion of the environment variable affected which copy of GS was used (both on the command path?) ... in which case the bug would disappear, not switch to a different image. All that said, this bug is clearly not playing fair, so it would be a good idea for Leo to check into this just to rule it out. /Paul
Re: Fw: Postscript preview
Paul A. Rubin wrote: Stephen Harris wrote: The MATLAB Component Runtime (MCR) 7.0 and 7.1 do not contain a copy of the GhostScript program included with MATLAB. Therefore, applications deployed on a target machine rely on a locally- installed version of GhostScript, if one exists, for exporting some graphics. Since the version of GhostScript installed on the target machine may be different than the one included with MATLAB, the command line parameters potentially may be different as well. This difference causes an error in some instances. I think this supports the possibility of a Ghostscript conflict and that Matlab comes with its own version of Gs. It does indeed. So I agree that hypothetically Leo's MATLAB installation could be generating PS files (using it's own copy of GS) that would be indigestible to LyX-ImageMagick-GS (using a different copy of GS in the last step). That still raises the question of why those images would be successfully displayed in LyX (same LyX-ImageMagick-GS sequence) if an environment variable is deleted ... unless deletion of the environment variable affected which copy of GS was used (both on the command path?) ... in which case the bug would disappear, not switch to a different image. All that said, this bug is clearly not playing fair, so it would be a good idea for Leo to check into this just to rule it out. /Paul Yes there has to be another dimension to this. Recall he reinstalled LyX to C:\Lyx\lyx14 and the original problem files, I think it was test.ps, displayed Ok, but then another figure reared its ugly wolverine head. I would think that means that only some files are produced with the problem--either the same gs executable produces files which vary in compatibility or maybe system gs is producing the eps and it sometimes can't be read by an older matlab gs executable. Well, that is getting pretty thin. Maybe he could use the 1.4.1 lyx.bat and put Python at the beginning of the Path_prefix and try it and if it doesn't work, then try ghostscript at the beginning of Path_prefix also, but I think it is already. It would seem that the set variables in lyx1.4.2 batfile would have to part of it, but I don't know what they mean and they don't show up LC_ALL I will google one more time matlab and aikasaurus but I think that is just for Aspell. I'm not feeling well and can't concentrate. I've been up for two days fighting with a virus and am tired and have lost one partition on my hard drive. I guess its a trojan. Nope, I got a hit on allosaurus and matlab, but no aikasaurus. It's a Linux critter anyway. Regards, Stephen
Re: Fw: Postscript preview
Paul A. Rubin wrote: LB wrote: Ok, it tried this. I commented out SET LC_ALL=en_EN. This resulted in a different image having the preview problem. I placed SET XX=Y in lyx.bat and the preview problem moved back to the original image. The same happens when I comment out the other line in the lyx.bat. I also added extra lines in lyx.bat such as SET XX=Y this however did not make any difference as far as image preview is concerned. This is again confusing, though perhaps no more confusing than the fact that deleting unneeded environment variables (other than LC_ALL and the aiksaurus one) did not help. Another puzzling thing is that the preview problem jumps between two specific figures eventhough I have many figures in the document and many of them are generated with Matlab. The preview problem however never affects figures generated with other programs. Is there anything that the names/paths of the two affected figures have in common which is not shared by the other files. For instance, are they the longest paths, do they lie deeper in the directory tree than other figures, ... ? Stephen's idea of a second Ghostscript installation strikes me as possible but unlikely (and unlikely to be the culprit), since there would need to be something causing ImageMagick to alternate between the two GS installations on a figure-by-figure basis within the document (meaning that something in the figure names/paths would have to be triggering the switching). Also, Mathematica exports EPS without using GS and without installing its own GS, so I suspect the same might be true of MATLAB. Still, the whole bug is unlikely, so we shouldn't presume anything. It would be nice if we could intercept the call from IM to GS and see what's being passed, but so far I have not figured out how. /Paul - http://www.mathworks.com/support/solutions/data/1-ZBALJ.html?solution=1-ZBALJ "The MATLAB Component Runtime (MCR) 7.0 and 7.1 do not contain a copy of the GhostScript program included with MATLAB. Therefore, applications deployed on a target machine rely on a locally- installed version of GhostScript, if one exists, for exporting some graphics. Since the version of GhostScript installed on the target machine may be different than the one included with MATLAB, the command line parameters potentially may be different as well. This difference causes an error in some instances." I think this supports the possibility of a Ghostscript conflict and that Matlab comes with its own version of Gs. With an earlier distro of LyX I also had XemTeX installed which comes with its own Gs. It had a different version of Gs and the .dlls conflicted with LyX which was solved by moving Xemtex to the end of Windows Path. I'm pretty sure that lyx.exe checks the LyX directory for various executables because Enrico's batfiles seem to use this principle. I'm not so sure about lyx.bat because I thought it was possible that those set commands could change which Gs was invoked. I don't know what they do, the consequences of their mechanism. One major difference in the our environments and Leo's is that he has Matlab installed and we don't. I'm pretty sure that Matlab has Gs installed since I've googled and seen it listed as a sub-dir of Matlab's directory structure (though only for Linux). It should take Leo less than thirty seconds to find out with Win Explorer. I 've a hunch that his Matlab Gs version is earlier than his system Gs, supposing that there are two instances. My troubleshooting idea was to eliminate both ways a Gs version conflict could happen and to use lyx.exe first before lyx.bat to see if the .eps file itself (command line parameters used) perhaps had a version glitch and I thought it would take about 5 minutes (without Matlab running) to see if this affected the problem. I think the Matlab doc I just reported upon supports this possibility. We also have a more recent version of system Ghostscript. My Sherlock Holmes sig, (inmates on death row tell jokes by #) Stephen
Re: Fw: Postscript preview
Stephen Harris wrote: "The MATLAB Component Runtime (MCR) 7.0 and 7.1 do not contain a copy of the GhostScript program included with MATLAB. Therefore, applications deployed on a target machine rely on a locally- installed version of GhostScript, if one exists, for exporting some graphics. Since the version of GhostScript installed on the target machine may be different than the one included with MATLAB, the command line parameters potentially may be different as well. This difference causes an error in some instances." I think this supports the possibility of a Ghostscript conflict and that Matlab comes with its own version of Gs. It does indeed. So I agree that hypothetically Leo's MATLAB installation could be generating PS files (using it's own copy of GS) that would be indigestible to LyX->ImageMagick->GS (using a different copy of GS in the last step). That still raises the question of why those images would be successfully displayed in LyX (same LyX->ImageMagick->GS sequence) if an environment variable is deleted ... unless deletion of the environment variable affected which copy of GS was used (both on the command path?) ... in which case the bug would disappear, not switch to a different image. All that said, this bug is clearly not playing fair, so it would be a good idea for Leo to check into this just to rule it out. /Paul
Re: Fw: Postscript preview
Paul A. Rubin wrote: Stephen Harris wrote: "The MATLAB Component Runtime (MCR) 7.0 and 7.1 do not contain a copy of the GhostScript program included with MATLAB. Therefore, applications deployed on a target machine rely on a locally- installed version of GhostScript, if one exists, for exporting some graphics. Since the version of GhostScript installed on the target machine may be different than the one included with MATLAB, the command line parameters potentially may be different as well. This difference causes an error in some instances." I think this supports the possibility of a Ghostscript conflict and that Matlab comes with its own version of Gs. It does indeed. So I agree that hypothetically Leo's MATLAB installation could be generating PS files (using it's own copy of GS) that would be indigestible to LyX->ImageMagick->GS (using a different copy of GS in the last step). That still raises the question of why those images would be successfully displayed in LyX (same LyX->ImageMagick->GS sequence) if an environment variable is deleted ... unless deletion of the environment variable affected which copy of GS was used (both on the command path?) ... in which case the bug would disappear, not switch to a different image. All that said, this bug is clearly not playing fair, so it would be a good idea for Leo to check into this just to rule it out. /Paul Yes there has to be another dimension to this. Recall he reinstalled LyX to C:\Lyx\lyx14 and the original problem files, I think it was test.ps, displayed Ok, but then another figure reared its ugly wolverine head. I would think that means that only some files are produced with the problem--either the same gs executable produces files which vary in compatibility or maybe system gs is producing the eps and it sometimes can't be read by an older matlab gs executable. Well, that is getting pretty thin. Maybe he could use the 1.4.1 lyx.bat and put Python at the beginning of the Path_prefix and try it and if it doesn't work, then try ghostscript at the beginning of Path_prefix also, but I think it is already. It would seem that the set variables in lyx1.4.2 batfile would have to part of it, but I don't know what they mean and they don't show up LC_ALL I will google one more time matlab and aikasaurus but I think that is just for Aspell. I'm not feeling well and can't concentrate. I've been up for two days fighting with a virus and am tired and have lost one partition on my hard drive. I guess its a trojan. Nope, I got a hit on allosaurus and matlab, but no aikasaurus. It's a Linux critter anyway. Regards, Stephen
Re: Fw: Postscript preview
LB wrote: Ok, it tried this. I commented out SET LC_ALL=en_EN. This resulted in a different image having the preview problem. I placed SET XX=Y in lyx.bat and the preview problem moved back to the original image. The same happens when I comment out the other line in the lyx.bat. I also added extra lines in lyx.bat such as SET XX=Y this however did not make any difference as far as image preview is concerned. This is again confusing, though perhaps no more confusing than the fact that deleting unneeded environment variables (other than LC_ALL and the aiksaurus one) did not help. Another puzzling thing is that the preview problem jumps between two specific figures eventhough I have many figures in the document and many of them are generated with Matlab. The preview problem however never affects figures generated with other programs. Is there anything that the names/paths of the two affected figures have in common which is not shared by the other files. For instance, are they the longest paths, do they lie deeper in the directory tree than other figures, ... ? Stephen's idea of a second Ghostscript installation strikes me as possible but unlikely (and unlikely to be the culprit), since there would need to be something causing ImageMagick to alternate between the two GS installations on a figure-by-figure basis within the document (meaning that something in the figure names/paths would have to be triggering the switching). Also, Mathematica exports EPS without using GS and without installing its own GS, so I suspect the same might be true of MATLAB. Still, the whole bug is unlikely, so we shouldn't presume anything. It would be nice if we could intercept the call from IM to GS and see what's being passed, but so far I have not figured out how. /Paul
Re: Fw: Postscript preview
LB wrote: Ok, it tried this. I commented out SET LC_ALL=en_EN. This resulted in a different image having the preview problem. I placed SET XX=Y in lyx.bat and the preview problem moved back to the original image. The same happens when I comment out the other line in the lyx.bat. I also added extra lines in lyx.bat such as SET XX=Y this however did not make any difference as far as image preview is concerned. This is again confusing, though perhaps no more confusing than the fact that deleting unneeded environment variables (other than LC_ALL and the aiksaurus one) did not help. Another puzzling thing is that the preview problem jumps between two specific figures eventhough I have many figures in the document and many of them are generated with Matlab. The preview problem however never affects figures generated with other programs. Is there anything that the names/paths of the two affected figures have in common which is not shared by the other files. For instance, are they the longest paths, do they lie deeper in the directory tree than other figures, ... ? Stephen's idea of a second Ghostscript installation strikes me as possible but unlikely (and unlikely to be the culprit), since there would need to be something causing ImageMagick to alternate between the two GS installations on a figure-by-figure basis within the document (meaning that something in the figure names/paths would have to be triggering the switching). Also, Mathematica exports EPS without using GS and without installing its own GS, so I suspect the same might be true of MATLAB. Still, the whole bug is unlikely, so we shouldn't presume anything. It would be nice if we could intercept the call from IM to GS and see what's being passed, but so far I have not figured out how. /Paul
Re: Fw: Postscript preview
LB wrote: Ok, it tried this. I commented out SET LC_ALL=en_EN. This resulted in a different image having the preview problem. I placed SET XX=Y in lyx.bat and the preview problem moved back to the original image. The same happens when I comment out the other line in the lyx.bat. I also added extra lines in lyx.bat such as SET XX=Y this however did not make any difference as far as image preview is concerned. This is again confusing, though perhaps no more confusing than the fact that deleting unneeded environment variables (other than LC_ALL and the aiksaurus one) did not help. Another puzzling thing is that the preview problem jumps between two specific figures eventhough I have many figures in the document and many of them are generated with Matlab. The preview problem however never affects figures generated with other programs. Is there anything that the names/paths of the two affected figures have in common which is not shared by the other files. For instance, are they the longest paths, do they lie deeper in the directory tree than other figures, ... ? Stephen's idea of a second Ghostscript installation strikes me as possible but unlikely (and unlikely to be the culprit), since there would need to be something causing ImageMagick to alternate between the two GS installations on a figure-by-figure basis within the document (meaning that something in the figure names/paths would have to be triggering the switching). Also, Mathematica exports EPS without using GS and without installing its own GS, so I suspect the same might be true of MATLAB. Still, the whole bug is unlikely, so we shouldn't presume anything. It would be nice if we could intercept the call from IM to GS and see what's being passed, but so far I have not figured out how. /Paul
Re: Fw: Postscript preview
One more little experiment, if you don't mind, just to confirm symptoms: if you comment out one of the SET commands in lyx.bat, but replace it with a line of equal length (SET XXX=Y... with enough Xs and Ys to match the line you commented out), does the bug move to a different image (or disappear)? Ok, it tried this. I commented out SET LC_ALL=en_EN. This resulted in a different image having the preview problem. I placed SET XX=Y in lyx.bat and the preview problem moved back to the original image. The same happens when I comment out the other line in the lyx.bat. I also added extra lines in lyx.bat such as SET XX=Y this however did not make any difference as far as image preview is concerned. Another puzzling thing is that the preview problem jumps between two specific figures eventhough I have many figures in the document and many of them are generated with Matlab. The preview problem however never affects figures generated with other programs. Thanks Leo
Re: Fw: Postscript preview
LB wrote: One more little experiment, if you don't mind, just to confirm symptoms: if you comment out one of the SET commands in lyx.bat, but replace it with a line of equal length (SET XXX=Y... with enough Xs and Ys to match the line you commented out), does the bug move to a different image (or disappear)? Ok, it tried this. I commented out SET LC_ALL=en_EN. This resulted in a different image having the preview problem. I placed SET XX=Y in lyx.bat and the preview problem moved back to the original image. The same happens when I comment out the other line in the lyx.bat. I also added extra lines in lyx.bat such as SET XX=Y this however did not make any difference as far as image preview is concerned. Another puzzling thing is that the preview problem jumps between two specific figures eventhough I have many figures in the document and many of them are generated with Matlab. The preview problem however never affects figures generated with other programs. Thanks Leo Do you have two installations of ghostscript on your machine? One in a sub-directory for Matlab and another one in a sub-dir of LyX or maybe a system-wide Ghostscript? If so, that means if you rename the ghostscript executables, maybe they are gs.exe and gswin32.exe, to gs.bak and gswin32.bak, under the Matlab install of Ghostscript, then lyx.exe and lyx.bat should work the same. Try it first with lyx.exe which you know works and if it still works then the correct gs executable has been renamed. Then lyx.bat will have to use the same gs executable since the one under Matlab has been renamed and won't answer the call. It dawned on me that Matlab might have its own gs to make eps' Stephen -- An ambient confluence of mapped coherence ~ Stephen
Re: Fw: Postscript preview
One more little experiment, if you don't mind, just to confirm symptoms: if you comment out one of the SET commands in lyx.bat, but replace it with a line of equal length (SET XXX=Y... with enough Xs and Ys to match the line you commented out), does the bug move to a different image (or disappear)? Ok, it tried this. I commented out SET LC_ALL=en_EN. This resulted in a different image having the preview problem. I placed SET XX=Y in lyx.bat and the preview problem moved back to the original image. The same happens when I comment out the other line in the lyx.bat. I also added extra lines in lyx.bat such as SET XX=Y this however did not make any difference as far as image preview is concerned. Another puzzling thing is that the preview problem jumps between two specific figures eventhough I have many figures in the document and many of them are generated with Matlab. The preview problem however never affects figures generated with other programs. Thanks Leo
Re: Fw: Postscript preview
LB wrote: One more little experiment, if you don't mind, just to confirm symptoms: if you comment out one of the SET commands in lyx.bat, but replace it with a line of equal length (SET XXX=Y... with enough Xs and Ys to match the line you commented out), does the bug move to a different image (or disappear)? Ok, it tried this. I commented out SET LC_ALL=en_EN. This resulted in a different image having the preview problem. I placed SET XX=Y in lyx.bat and the preview problem moved back to the original image. The same happens when I comment out the other line in the lyx.bat. I also added extra lines in lyx.bat such as SET XX=Y this however did not make any difference as far as image preview is concerned. Another puzzling thing is that the preview problem jumps between two specific figures eventhough I have many figures in the document and many of them are generated with Matlab. The preview problem however never affects figures generated with other programs. Thanks Leo Do you have two installations of ghostscript on your machine? One in a sub-directory for Matlab and another one in a sub-dir of LyX or maybe a system-wide Ghostscript? If so, that means if you rename the ghostscript executables, maybe they are gs.exe and gswin32.exe, to gs.bak and gswin32.bak, under the Matlab install of Ghostscript, then lyx.exe and lyx.bat should work the same. Try it first with lyx.exe which you know works and if it still works then the correct gs executable has been renamed. Then lyx.bat will have to use the same gs executable since the one under Matlab has been renamed and won't answer the call. It dawned on me that Matlab might have its own gs to make eps' Stephen -- An ambient confluence of mapped coherence ~ Stephen
Re: Fw: Postscript preview
One more little experiment, if you don't mind, just to confirm symptoms: if you comment out one of the SET commands in lyx.bat, but replace it with a line of equal length (SET XXX=Y... with enough Xs and Ys to match the line you commented out), does the bug move to a different image (or disappear)? Ok, it tried this. I commented out SET LC_ALL=en_EN. This resulted in a different image having the preview problem. I placed SET XX=Y in lyx.bat and the preview problem moved back to the original image. The same happens when I comment out the other line in the lyx.bat. I also added extra lines in lyx.bat such as SET XX=Y this however did not make any difference as far as image preview is concerned. Another puzzling thing is that the preview problem jumps between two specific figures eventhough I have many figures in the document and many of them are generated with Matlab. The preview problem however never affects figures generated with other programs. Thanks Leo
Re: Fw: Postscript preview
LB wrote: One more little experiment, if you don't mind, just to confirm symptoms: if you comment out one of the SET commands in lyx.bat, but replace it with a line of equal length (SET XXX=Y... with enough Xs and Ys to match the line you commented out), does the bug move to a different image (or disappear)? Ok, it tried this. I commented out SET LC_ALL=en_EN. This resulted in a different image having the preview problem. I placed SET XX=Y in lyx.bat and the preview problem moved back to the original image. The same happens when I comment out the other line in the lyx.bat. I also added extra lines in lyx.bat such as SET XX=Y this however did not make any difference as far as image preview is concerned. Another puzzling thing is that the preview problem jumps between two specific figures eventhough I have many figures in the document and many of them are generated with Matlab. The preview problem however never affects figures generated with other programs. Thanks Leo Do you have two installations of ghostscript on your machine? One in a sub-directory for Matlab and another one in a sub-dir of LyX or maybe a system-wide Ghostscript? If so, that means if you rename the ghostscript executables, maybe they are gs.exe and gswin32.exe, to gs.bak and gswin32.bak, under the Matlab install of Ghostscript, then lyx.exe and lyx.bat should work the same. Try it first with lyx.exe which you know works and if it still works then the correct gs executable has been renamed. Then lyx.bat will have to use the same gs executable since the one under Matlab has been renamed and won't answer the call. It dawned on me that Matlab might have its own gs to make eps' Stephen -- An ambient confluence of mapped coherence ~ Stephen
Re: Fw: Postscript preview
Does it display the same old symptoms; it works with lyx.exe or if you delete one of the set commands in lyx.bat? Lyx (or GS) gets stuck at different figures depending on what I comment out in lyx.bat. If the figure doesn't work with lyx.exe then it is the file. Try it with both (the old one which now works and the broken new one) in the same directory. A rather inexplicable matter. The old versions display all figures fine. I have been suspecting the figure files themselves for a while but I don't really understand what the problem could possibly be. Leo
Re: Fw: Postscript preview
LB wrote: Lyx (or GS) gets stuck at different figures depending on what I comment out in lyx.bat. I want to make sure I'm understanding this correctly: in a single document with multiple images, GS will get stuck on image with the original lyx.bat file, then process that image correctly but get stuck on a later one if you comment something out of lyx.bat? (And how far it gets depends on what you comment out?) If so, that really points to a memory buffer issue someplace (but who knows where). /Paul
Re: Fw: Postscript preview
I want to make sure I'm understanding this correctly: in a single document with multiple images, GS will get stuck on image with the original lyx.bat file, then process that image correctly but get stuck on a later one if you comment something out of lyx.bat? (And how far it gets depends on what you comment out?) This is what I'm seeing. Why does 1.4.1 work all the time? What changed? Leo
Re: Fw: Postscript preview
LB wrote: I want to make sure I'm understanding this correctly: in a single document with multiple images, GS will get stuck on image with the original lyx.bat file, then process that image correctly but get stuck on a later one if you comment something out of lyx.bat? (And how far it gets depends on what you comment out?) This is what I'm seeing. Why does 1.4.1 work all the time? What changed? Good question. Another good question is: why only on your machine. There must be something specific to your setup interacting with something specific to version 1.4.2. One more little experiment, if you don't mind, just to confirm symptoms: if you comment out one of the SET commands in lyx.bat, but replace it with a line of equal length (SET XXX=Y... with enough Xs and Ys to match the line you commented out), does the bug move to a different image (or disappear)? This reminds me of a bug I ran into in a computer science class back when mainframes ruled. It made no sense, and was hard to pin down. So I turned in a heap of line printer output showing what was going on, and my instructor looked at it and closed the matter by blithely stating This can't happen. (Turned out the computer was subtracting incorrectly in an emulation mode.) So if all else fails, just tell yourself that This can't happen and therefore the display is actually correct, sensory evidence to the contrary notwithstanding. /Paul
Re: Fw: Postscript preview
Does it display the same old symptoms; it works with lyx.exe or if you delete one of the set commands in lyx.bat? Lyx (or GS) gets stuck at different figures depending on what I comment out in lyx.bat. If the figure doesn't work with lyx.exe then it is the file. Try it with both (the old one which now works and the broken new one) in the same directory. A rather inexplicable matter. The old versions display all figures fine. I have been suspecting the figure files themselves for a while but I don't really understand what the problem could possibly be. Leo
Re: Fw: Postscript preview
LB wrote: Lyx (or GS) gets stuck at different figures depending on what I comment out in lyx.bat. I want to make sure I'm understanding this correctly: in a single document with multiple images, GS will get stuck on image with the original lyx.bat file, then process that image correctly but get stuck on a later one if you comment something out of lyx.bat? (And how far it gets depends on what you comment out?) If so, that really points to a memory buffer issue someplace (but who knows where). /Paul
Re: Fw: Postscript preview
I want to make sure I'm understanding this correctly: in a single document with multiple images, GS will get stuck on image with the original lyx.bat file, then process that image correctly but get stuck on a later one if you comment something out of lyx.bat? (And how far it gets depends on what you comment out?) This is what I'm seeing. Why does 1.4.1 work all the time? What changed? Leo
Re: Fw: Postscript preview
LB wrote: I want to make sure I'm understanding this correctly: in a single document with multiple images, GS will get stuck on image with the original lyx.bat file, then process that image correctly but get stuck on a later one if you comment something out of lyx.bat? (And how far it gets depends on what you comment out?) This is what I'm seeing. Why does 1.4.1 work all the time? What changed? Good question. Another good question is: why only on your machine. There must be something specific to your setup interacting with something specific to version 1.4.2. One more little experiment, if you don't mind, just to confirm symptoms: if you comment out one of the SET commands in lyx.bat, but replace it with a line of equal length (SET XXX=Y... with enough Xs and Ys to match the line you commented out), does the bug move to a different image (or disappear)? This reminds me of a bug I ran into in a computer science class back when mainframes ruled. It made no sense, and was hard to pin down. So I turned in a heap of line printer output showing what was going on, and my instructor looked at it and closed the matter by blithely stating This can't happen. (Turned out the computer was subtracting incorrectly in an emulation mode.) So if all else fails, just tell yourself that This can't happen and therefore the display is actually correct, sensory evidence to the contrary notwithstanding. /Paul
Re: Fw: Postscript preview
Does it display the same old symptoms; it works with lyx.exe or if you delete one of the "set" commands in lyx.bat? Lyx (or GS) gets "stuck" at different figures depending on what I comment out in lyx.bat. If the figure doesn't work with lyx.exe then it is the file. Try it with both (the old one which now works and the broken new one) in the same directory. A rather inexplicable matter. The old versions display all figures fine. I have been suspecting the figure files themselves for a while but I don't really understand what the problem could possibly be. Leo
Re: Fw: Postscript preview
LB wrote: Lyx (or GS) gets "stuck" at different figures depending on what I comment out in lyx.bat. I want to make sure I'm understanding this correctly: in a single document with multiple images, GS will get stuck on image with the original lyx.bat file, then process that image correctly but get stuck on a later one if you comment something out of lyx.bat? (And how far it gets depends on what you comment out?) If so, that really points to a memory buffer issue someplace (but who knows where). /Paul
Re: Fw: Postscript preview
I want to make sure I'm understanding this correctly: in a single document with multiple images, GS will get stuck on image with the original lyx.bat file, then process that image correctly but get stuck on a later one if you comment something out of lyx.bat? (And how far it gets depends on what you comment out?) This is what I'm seeing. Why does 1.4.1 work all the time? What changed? Leo
Re: Fw: Postscript preview
LB wrote: I want to make sure I'm understanding this correctly: in a single document with multiple images, GS will get stuck on image with the original lyx.bat file, then process that image correctly but get stuck on a later one if you comment something out of lyx.bat? (And how far it gets depends on what you comment out?) This is what I'm seeing. Why does 1.4.1 work all the time? What changed? Good question. Another good question is: why only on your machine. There must be something specific to your setup interacting with something specific to version 1.4.2. One more little experiment, if you don't mind, just to confirm symptoms: if you comment out one of the SET commands in lyx.bat, but replace it with a line of equal length (SET XXX=Y... with enough Xs and Ys to match the line you commented out), does the bug move to a different image (or disappear)? This reminds me of a bug I ran into in a computer science class back when mainframes ruled. It made no sense, and was hard to pin down. So I turned in a heap of line printer output showing what was going on, and my instructor looked at it and closed the matter by blithely stating "This can't happen." (Turned out the computer was subtracting incorrectly in an emulation mode.) So if all else fails, just tell yourself that "This can't happen" and therefore the display is actually correct, sensory evidence to the contrary notwithstanding. /Paul
Re: Fw: Postscript preview
LB wrote: I uninstalled Lyx and reinstalled it into c:\lyx\lyx14. This solved my figure problem!!! Thank you. I can now use 1.4.2 Looks like I spoke too soon. Now a different figure does not want to be displayed. Leo Does it display the same old symptoms; it works with lyx.exe or if you delete one of the set commands in lyx.bat? If the figure doesn't work with lyx.exe then it is the file. Try it with both (the old one which now works and the broken new one) in the same directory. A rather inexplicable matter. Perplexed, Stephen
Re: Fw: Postscript preview
LB wrote: I uninstalled Lyx and reinstalled it into c:\lyx\lyx14. This solved my figure problem!!! Thank you. I can now use 1.4.2 Looks like I spoke too soon. Now a different figure does not want to be displayed. Leo Does it display the same old symptoms; it works with lyx.exe or if you delete one of the set commands in lyx.bat? If the figure doesn't work with lyx.exe then it is the file. Try it with both (the old one which now works and the broken new one) in the same directory. A rather inexplicable matter. Perplexed, Stephen
Re: Fw: Postscript preview
LB wrote: I uninstalled Lyx and reinstalled it into c:\lyx\lyx14. This solved my figure problem!!! Thank you. I can now use 1.4.2 Looks like I spoke too soon. Now a different figure does not want to be displayed. Leo Does it display the same old symptoms; it works with lyx.exe or if you delete one of the "set" commands in lyx.bat? If the figure doesn't work with lyx.exe then it is the file. Try it with both (the old one which now works and the broken new one) in the same directory. A rather inexplicable matter. Perplexed, Stephen
Re: Fw: Postscript preview
Hi Stephen I uninstalled Lyx and reinstalled it into c:\lyx\lyx14. This solved my figure problem!!! Thank you. I can now use 1.4.2 Leo LB wrote: The paths are not supposed to be the same. LyX 1.4.1 did not install a python directory under LyX. Also the batfiles are not the same. This usually happens when the preferences files under c:\documents and settings\yourusername~~~\~ are not deleted during the uninstall. Then the next version picks up the old preferences and sometimes doesn't work right. Maybe you have more than just two copies of LyX installed, 1.4.1 and 1.4.2. You can do a Windows Search for the filename lyx.exe and see if if reports more than two instances on your C drive. Also do a search for preferences. Ok. I did not uninstall old versions of Lyx because I'm always worried about upgrading to a new version when an old one is working fine and not being able to open older documents with the new versions. So I have in the Lyx directory four subdirectories Lyx1.3.3, Lyx1.3.5, Lyx1.4.1 and Lyx1.4.2 that contain the four different installs. I only have one preferences file in .lyx directory though. Leo C:\Documents and Settings\Stephen\Application Data\LyX I have a preference file (your^username) and lyxrc.defaults in this directory. WinXP hides some directories; so your ~\Application Data directory contains no LyX* sub-directory? I have CygwinLyX1.4.1 and native Windows Lyx1.4.2 both installed without conflict. In the past I've had trouble with Cygwin's version of Ghostscript conflicting with the Windows version of Ghostscript. And when I tried to install TexLive2005 which is very much like Miktex, I had to fix a conflict with environmental variables, Texmfdir, I think. Your files test OK on my system. I think you should try uninstalling LyX1.4.2 (there is a Cygwin1.4.2 available) and installing it to the default C:\LyX\lyx14 directory, it is designed not to conflict with concurrent versions. Windows doesn't like a dot, . , prefix to directories and you can't make them in Windows Explorer, just Dos. If you do, remember to put the system Python installation at the front of Path_prefix, the local lyx one is tired. You've noticed the batfiles are different, 141 to 142... I don't understand what the 142 batfile does well enough to suggest using the 141 batfile instead of the 142 bat. SET LC_ALL=en_EN versus SET LANG=en_EN which used to work. Stephen
Re: Fw: Postscript preview
I uninstalled Lyx and reinstalled it into c:\lyx\lyx14. This solved my figure problem!!! Thank you. I can now use 1.4.2 Looks like I spoke too soon. Now a different figure does not want to be displayed. Leo
Re: Fw: Postscript preview
LB wrote: I uninstalled Lyx and reinstalled it into c:\lyx\lyx14. This solved my figure problem!!! Thank you. I can now use 1.4.2 Looks like I spoke too soon. Now a different figure does not want to be displayed. Leo But the original one does display, even when loaded from its original (deep) directory? Have you considered offering a small sacrifice (perhaps a wolverine) to the gods of computing? /Paul
Re: Fw: Postscript preview
On 8/1/06, LB [EMAIL PROTECTED] wrote: I uninstalled Lyx and reinstalled it into c:\lyx\lyx14. This solved my figure problem!!! Thank you. I can now use 1.4.2 Looks like I spoke too soon. Now a different figure does not want to be displayed. I do not know what have gone wrong, just want to say that lyx 1.4.3 will use a python script to do the conversion and your problem may or may not go away. Right now, your best bet may be 1.4.1, if it works well for you. Cheers, Bo
Re: Fw: Postscript preview
Hi Stephen I uninstalled Lyx and reinstalled it into c:\lyx\lyx14. This solved my figure problem!!! Thank you. I can now use 1.4.2 Leo LB wrote: The paths are not supposed to be the same. LyX 1.4.1 did not install a python directory under LyX. Also the batfiles are not the same. This usually happens when the preferences files under c:\documents and settings\yourusername~~~\~ are not deleted during the uninstall. Then the next version picks up the old preferences and sometimes doesn't work right. Maybe you have more than just two copies of LyX installed, 1.4.1 and 1.4.2. You can do a Windows Search for the filename lyx.exe and see if if reports more than two instances on your C drive. Also do a search for preferences. Ok. I did not uninstall old versions of Lyx because I'm always worried about upgrading to a new version when an old one is working fine and not being able to open older documents with the new versions. So I have in the Lyx directory four subdirectories Lyx1.3.3, Lyx1.3.5, Lyx1.4.1 and Lyx1.4.2 that contain the four different installs. I only have one preferences file in .lyx directory though. Leo C:\Documents and Settings\Stephen\Application Data\LyX I have a preference file (your^username) and lyxrc.defaults in this directory. WinXP hides some directories; so your ~\Application Data directory contains no LyX* sub-directory? I have CygwinLyX1.4.1 and native Windows Lyx1.4.2 both installed without conflict. In the past I've had trouble with Cygwin's version of Ghostscript conflicting with the Windows version of Ghostscript. And when I tried to install TexLive2005 which is very much like Miktex, I had to fix a conflict with environmental variables, Texmfdir, I think. Your files test OK on my system. I think you should try uninstalling LyX1.4.2 (there is a Cygwin1.4.2 available) and installing it to the default C:\LyX\lyx14 directory, it is designed not to conflict with concurrent versions. Windows doesn't like a dot, . , prefix to directories and you can't make them in Windows Explorer, just Dos. If you do, remember to put the system Python installation at the front of Path_prefix, the local lyx one is tired. You've noticed the batfiles are different, 141 to 142... I don't understand what the 142 batfile does well enough to suggest using the 141 batfile instead of the 142 bat. SET LC_ALL=en_EN versus SET LANG=en_EN which used to work. Stephen
Re: Fw: Postscript preview
I uninstalled Lyx and reinstalled it into c:\lyx\lyx14. This solved my figure problem!!! Thank you. I can now use 1.4.2 Looks like I spoke too soon. Now a different figure does not want to be displayed. Leo
Re: Fw: Postscript preview
LB wrote: I uninstalled Lyx and reinstalled it into c:\lyx\lyx14. This solved my figure problem!!! Thank you. I can now use 1.4.2 Looks like I spoke too soon. Now a different figure does not want to be displayed. Leo But the original one does display, even when loaded from its original (deep) directory? Have you considered offering a small sacrifice (perhaps a wolverine) to the gods of computing? /Paul
Re: Fw: Postscript preview
On 8/1/06, LB [EMAIL PROTECTED] wrote: I uninstalled Lyx and reinstalled it into c:\lyx\lyx14. This solved my figure problem!!! Thank you. I can now use 1.4.2 Looks like I spoke too soon. Now a different figure does not want to be displayed. I do not know what have gone wrong, just want to say that lyx 1.4.3 will use a python script to do the conversion and your problem may or may not go away. Right now, your best bet may be 1.4.1, if it works well for you. Cheers, Bo
Re: Fw: Postscript preview
Hi Stephen I uninstalled Lyx and reinstalled it into c:\lyx\lyx14. This solved my figure problem!!! Thank you. I can now use 1.4.2 Leo LB wrote: The paths are not supposed to be the same. LyX 1.4.1 did not install a python directory under LyX. Also the batfiles are not the same. This usually happens when the preferences files under c:\documents and settings\yourusername~~~\~ are not deleted during the uninstall. Then the next version picks up the old preferences and sometimes doesn't work right. Maybe you have more than just two copies of LyX installed, 1.4.1 and 1.4.2. You can do a Windows Search for the filename lyx.exe and see if if reports more than two instances on your C drive. Also do a search for "preferences". Ok. I did not uninstall old versions of Lyx because I'm always worried about upgrading to a new version when an old one is working fine and not being able to open older documents with the new versions. So I have in the Lyx directory four subdirectories Lyx1.3.3, Lyx1.3.5, Lyx1.4.1 and Lyx1.4.2 that contain the four different installs. I only have one "preferences" file in .lyx directory though. Leo C:\Documents and Settings\Stephen\Application Data\LyX I have a preference file (your^username) and lyxrc.defaults in this directory. WinXP hides some directories; so your ~\Application Data directory contains no LyX* sub-directory? I have CygwinLyX1.4.1 and native Windows Lyx1.4.2 both installed without conflict. In the past I've had trouble with Cygwin's version of Ghostscript conflicting with the Windows version of Ghostscript. And when I tried to install TexLive2005 which is very much like Miktex, I had to fix a conflict with environmental variables, Texmfdir, I think. Your files test OK on my system. I think you should try uninstalling LyX1.4.2 (there is a Cygwin1.4.2 available) and installing it to the default C:\LyX\lyx14 directory, it is designed not to conflict with concurrent versions. Windows doesn't like a dot, . , prefix to directories and you can't make them in Windows Explorer, just Dos. If you do, remember to put the system Python installation at the front of Path_prefix, the local lyx one is tired. You've noticed the batfiles are different, 141 to 142... I don't understand what the 142 batfile does well enough to suggest using the 141 batfile instead of the 142 bat. SET LC_ALL=en_EN versus SET LANG=en_EN which used to work. Stephen
Re: Fw: Postscript preview
I uninstalled Lyx and reinstalled it into c:\lyx\lyx14. This solved my figure problem!!! Thank you. I can now use 1.4.2 Looks like I spoke too soon. Now a different figure does not want to be displayed. Leo
Re: Fw: Postscript preview
LB wrote: I uninstalled Lyx and reinstalled it into c:\lyx\lyx14. This solved my figure problem!!! Thank you. I can now use 1.4.2 Looks like I spoke too soon. Now a different figure does not want to be displayed. Leo But the original one does display, even when loaded from its original (deep) directory? Have you considered offering a small sacrifice (perhaps a wolverine) to the gods of computing? /Paul
Re: Fw: Postscript preview
On 8/1/06, LB <[EMAIL PROTECTED]> wrote: > I uninstalled Lyx and reinstalled it into c:\lyx\lyx14. This solved my > figure problem!!! > > Thank you. I can now use 1.4.2 Looks like I spoke too soon. Now a different figure does not want to be displayed. I do not know what have gone wrong, just want to say that lyx 1.4.3 will use a python script to do the conversion and your problem may or may not go away. Right now, your best bet may be 1.4.1, if it works well for you. Cheers, Bo
Re: Fw: Postscript preview
LB wrote: Hi one more idea: if this is really a PATH problem and things worked normally under lyx 1.4.1, then I would do the following simple steps (unless you already tried this and I didn't see it in the earlier messages): (a) Revert to LyX 1.4.1 and open the Preferences dialog to find out EXACTLY what your PATH setting is in that program. The path in 1.4.1: C:\LyX\Python24;C:\LyX\msys\1.0\bin;C:\LyX\texmf\miktex\bin;c:\lyx\gs\gs8.14\bin;C:\LyX\ImageMagick (b) Copy that string. (c) Re-install LyX 1.4.2 and open the Prefs dialog there to see its PATH settings. I would strongly suspect that this is somehow different from 1.4.1. Reinstalled Lyx 1.4.2 Its PATH is: C:\LyX\Python24;C:\LyX\msys\1.0\bin;C:\LyX\texmf\miktex\bin;c:\lyx\gs\gs8.14\bin;C:\LyX\ImageMagick (d) Enter the previously copied PATH from 1.4.1 into the PATH box in 1.4.2. The paths are exactly the same; (e) Restart LyX 1.4.2 (just to be safe), and see if the preview works now.This also did not work.Thank youLeo The paths are not supposed to be the same. LyX 1.4.1 did not install a python directory under LyX. Also the batfiles are not the same. This usually happens when the preferences files under c:\documents and settings\yourusername~~~\~ are not deleted during the uninstall. Then the next version picks up the old preferences and sometimes doesn't work right. Maybe you have more than just two copies of LyX installed, 1.4.1 and 1.4.2. You can do a Windows Search for the filename lyx.exe and see if if reports more than two instances on your C drive. Also do a search for preferences. Regards, Stephen
Re: Fw: Postscript preview
The paths are not supposed to be the same. LyX 1.4.1 did not install a python directory under LyX. Also the batfiles are not the same. This usually happens when the preferences files under c:\documents and settings\yourusername~~~\~ are not deleted during the uninstall. Then the next version picks up the old preferences and sometimes doesn't work right. Maybe you have more than just two copies of LyX installed, 1.4.1 and 1.4.2. You can do a Windows Search for the filename lyx.exe and see if if reports more than two instances on your C drive. Also do a search for preferences. Ok. I did not uninstall old versions of Lyx because I'm always worried about upgrading to a new version when an old one is working fine and not being able to open older documents with the new versions. So I have in the Lyx directory four subdirectories Lyx1.3.3, Lyx1.3.5, Lyx1.4.1 and Lyx1.4.2 that contain the four different installs. I only have one preferences file in .lyx directory though. Leo
Re: Fw: Postscript preview
LB wrote: The paths are not supposed to be the same. LyX 1.4.1 did not install a python directory under LyX. Also the batfiles are not the same. This usually happens when the preferences files under c:\documents and settings\yourusername~~~\~ are not deleted during the uninstall. Then the next version picks up the old preferences and sometimes doesn't work right. Maybe you have more than just two copies of LyX installed, 1.4.1 and 1.4.2. You can do a Windows Search for the filename lyx.exe and see if if reports more than two instances on your C drive. Also do a search for preferences. Ok. I did not uninstall old versions of Lyx because I'm always worried about upgrading to a new version when an old one is working fine and not being able to open older documents with the new versions. So I have in the Lyx directory four subdirectories Lyx1.3.3, Lyx1.3.5, Lyx1.4.1 and Lyx1.4.2 that contain the four different installs. I only have one preferences file in .lyx directory though. Leo C:\Documents and Settings\Stephen\Application Data\LyX I have a preference file (your^username) and lyxrc.defaults in this directory. WinXP hides some directories; so your ~\Application Data directory contains no LyX* sub-directory? I have CygwinLyX1.4.1 and native Windows Lyx1.4.2 both installed without conflict. In the past I've had trouble with Cygwin's version of Ghostscript conflicting with the Windows version of Ghostscript. And when I tried to install TexLive2005 which is very much like Miktex, I had to fix a conflict with environmental variables, Texmfdir, I think. Your files test OK on my system. I think you should try uninstalling LyX1.4.2 (there is a Cygwin1.4.2 available) and installing it to the default C:\LyX\lyx14 directory, it is designed not to conflict with concurrent versions. Windows doesn't like a dot, . , prefix to directories and you can't make them in Windows Explorer, just Dos. If you do, remember to put the system Python installation at the front of Path_prefix, the local lyx one is tired. You've noticed the batfiles are different, 141 to 142... I don't understand what the 142 batfile does well enough to suggest using the 141 batfile instead of the 142 bat. SET LC_ALL=en_EN versus SET LANG=en_EN which used to work. Stephen
Re: Fw: Postscript preview
LB wrote: Hi one more idea: if this is really a PATH problem and things worked normally under lyx 1.4.1, then I would do the following simple steps (unless you already tried this and I didn't see it in the earlier messages): (a) Revert to LyX 1.4.1 and open the Preferences dialog to find out EXACTLY what your PATH setting is in that program. The path in 1.4.1: C:\LyX\Python24;C:\LyX\msys\1.0\bin;C:\LyX\texmf\miktex\bin;c:\lyx\gs\gs8.14\bin;C:\LyX\ImageMagick (b) Copy that string. (c) Re-install LyX 1.4.2 and open the Prefs dialog there to see its PATH settings. I would strongly suspect that this is somehow different from 1.4.1. Reinstalled Lyx 1.4.2 Its PATH is: C:\LyX\Python24;C:\LyX\msys\1.0\bin;C:\LyX\texmf\miktex\bin;c:\lyx\gs\gs8.14\bin;C:\LyX\ImageMagick (d) Enter the previously copied PATH from 1.4.1 into the PATH box in 1.4.2. The paths are exactly the same; (e) Restart LyX 1.4.2 (just to be safe), and see if the preview works now.This also did not work.Thank youLeo The paths are not supposed to be the same. LyX 1.4.1 did not install a python directory under LyX. Also the batfiles are not the same. This usually happens when the preferences files under c:\documents and settings\yourusername~~~\~ are not deleted during the uninstall. Then the next version picks up the old preferences and sometimes doesn't work right. Maybe you have more than just two copies of LyX installed, 1.4.1 and 1.4.2. You can do a Windows Search for the filename lyx.exe and see if if reports more than two instances on your C drive. Also do a search for preferences. Regards, Stephen
Re: Fw: Postscript preview
The paths are not supposed to be the same. LyX 1.4.1 did not install a python directory under LyX. Also the batfiles are not the same. This usually happens when the preferences files under c:\documents and settings\yourusername~~~\~ are not deleted during the uninstall. Then the next version picks up the old preferences and sometimes doesn't work right. Maybe you have more than just two copies of LyX installed, 1.4.1 and 1.4.2. You can do a Windows Search for the filename lyx.exe and see if if reports more than two instances on your C drive. Also do a search for preferences. Ok. I did not uninstall old versions of Lyx because I'm always worried about upgrading to a new version when an old one is working fine and not being able to open older documents with the new versions. So I have in the Lyx directory four subdirectories Lyx1.3.3, Lyx1.3.5, Lyx1.4.1 and Lyx1.4.2 that contain the four different installs. I only have one preferences file in .lyx directory though. Leo
Re: Fw: Postscript preview
LB wrote: The paths are not supposed to be the same. LyX 1.4.1 did not install a python directory under LyX. Also the batfiles are not the same. This usually happens when the preferences files under c:\documents and settings\yourusername~~~\~ are not deleted during the uninstall. Then the next version picks up the old preferences and sometimes doesn't work right. Maybe you have more than just two copies of LyX installed, 1.4.1 and 1.4.2. You can do a Windows Search for the filename lyx.exe and see if if reports more than two instances on your C drive. Also do a search for preferences. Ok. I did not uninstall old versions of Lyx because I'm always worried about upgrading to a new version when an old one is working fine and not being able to open older documents with the new versions. So I have in the Lyx directory four subdirectories Lyx1.3.3, Lyx1.3.5, Lyx1.4.1 and Lyx1.4.2 that contain the four different installs. I only have one preferences file in .lyx directory though. Leo C:\Documents and Settings\Stephen\Application Data\LyX I have a preference file (your^username) and lyxrc.defaults in this directory. WinXP hides some directories; so your ~\Application Data directory contains no LyX* sub-directory? I have CygwinLyX1.4.1 and native Windows Lyx1.4.2 both installed without conflict. In the past I've had trouble with Cygwin's version of Ghostscript conflicting with the Windows version of Ghostscript. And when I tried to install TexLive2005 which is very much like Miktex, I had to fix a conflict with environmental variables, Texmfdir, I think. Your files test OK on my system. I think you should try uninstalling LyX1.4.2 (there is a Cygwin1.4.2 available) and installing it to the default C:\LyX\lyx14 directory, it is designed not to conflict with concurrent versions. Windows doesn't like a dot, . , prefix to directories and you can't make them in Windows Explorer, just Dos. If you do, remember to put the system Python installation at the front of Path_prefix, the local lyx one is tired. You've noticed the batfiles are different, 141 to 142... I don't understand what the 142 batfile does well enough to suggest using the 141 batfile instead of the 142 bat. SET LC_ALL=en_EN versus SET LANG=en_EN which used to work. Stephen
Re: Fw: Postscript preview
LB wrote: Hi one more idea: if this is really a PATH problem and things worked normally under lyx 1.4.1, then I would do the following simple steps (unless you already tried this and I didn't see it in the earlier messages): (a) Revert to LyX 1.4.1 and open the Preferences dialog to find out EXACTLY what your PATH setting is in that program. The path in 1.4.1: C:\LyX\Python24;C:\LyX\msys\1.0\bin;C:\LyX\texmf\miktex\bin;c:\lyx\gs\gs8.14\bin;C:\LyX\ImageMagick (b) Copy that string. (c) Re-install LyX 1.4.2 and open the Prefs dialog there to see its PATH settings. I would strongly suspect that this is somehow different from 1.4.1. Reinstalled Lyx 1.4.2 Its PATH is: C:\LyX\Python24;C:\LyX\msys\1.0\bin;C:\LyX\texmf\miktex\bin;c:\lyx\gs\gs8.14\bin;C:\LyX\ImageMagick>>> (d)>> Enter the previously copied PATH from 1.4.1 into the PATH box in 1.4.2.> The paths are exactly the same;>>> (e)>> Restart LyX 1.4.2 (just to be safe), and see if the preview works now.>This also did not work.Thank youLeo The paths are not supposed to be the same. LyX 1.4.1 did not install a python directory under LyX. Also the batfiles are not the same. This usually happens when the preferences files under c:\documents and settings\yourusername~~~\~ are not deleted during the uninstall. Then the next version picks up the old preferences and sometimes doesn't work right. Maybe you have more than just two copies of LyX installed, 1.4.1 and 1.4.2. You can do a Windows Search for the filename lyx.exe and see if if reports more than two instances on your C drive. Also do a search for "preferences". Regards, Stephen
Re: Fw: Postscript preview
The paths are not supposed to be the same. LyX 1.4.1 did not install a python directory under LyX. Also the batfiles are not the same. This usually happens when the preferences files under c:\documents and settings\yourusername~~~\~ are not deleted during the uninstall. Then the next version picks up the old preferences and sometimes doesn't work right. Maybe you have more than just two copies of LyX installed, 1.4.1 and 1.4.2. You can do a Windows Search for the filename lyx.exe and see if if reports more than two instances on your C drive. Also do a search for "preferences". Ok. I did not uninstall old versions of Lyx because I'm always worried about upgrading to a new version when an old one is working fine and not being able to open older documents with the new versions. So I have in the Lyx directory four subdirectories Lyx1.3.3, Lyx1.3.5, Lyx1.4.1 and Lyx1.4.2 that contain the four different installs. I only have one "preferences" file in .lyx directory though. Leo
Re: Fw: Postscript preview
LB wrote: The paths are not supposed to be the same. LyX 1.4.1 did not install a python directory under LyX. Also the batfiles are not the same. This usually happens when the preferences files under c:\documents and settings\yourusername~~~\~ are not deleted during the uninstall. Then the next version picks up the old preferences and sometimes doesn't work right. Maybe you have more than just two copies of LyX installed, 1.4.1 and 1.4.2. You can do a Windows Search for the filename lyx.exe and see if if reports more than two instances on your C drive. Also do a search for "preferences". Ok. I did not uninstall old versions of Lyx because I'm always worried about upgrading to a new version when an old one is working fine and not being able to open older documents with the new versions. So I have in the Lyx directory four subdirectories Lyx1.3.3, Lyx1.3.5, Lyx1.4.1 and Lyx1.4.2 that contain the four different installs. I only have one "preferences" file in .lyx directory though. Leo C:\Documents and Settings\Stephen\Application Data\LyX I have a preference file (your^username) and lyxrc.defaults in this directory. WinXP hides some directories; so your ~\Application Data directory contains no LyX* sub-directory? I have CygwinLyX1.4.1 and native Windows Lyx1.4.2 both installed without conflict. In the past I've had trouble with Cygwin's version of Ghostscript conflicting with the Windows version of Ghostscript. And when I tried to install TexLive2005 which is very much like Miktex, I had to fix a conflict with environmental variables, Texmfdir, I think. Your files test OK on my system. I think you should try uninstalling LyX1.4.2 (there is a Cygwin1.4.2 available) and installing it to the default C:\LyX\lyx14 directory, it is designed not to conflict with concurrent versions. Windows doesn't like a dot, . , prefix to directories and you can't make them in Windows Explorer, just Dos. If you do, remember to put the system Python installation at the front of Path_prefix, the local lyx one is tired. You've noticed the batfiles are different, 141 to 142... I don't understand what the 142 batfile does well enough to suggest using the 141 batfile instead of the 142 bat. SET LC_ALL=en_EN versus SET LANG=en_EN which used to work. Stephen
