Re: GSview/Ghostscript problems
Jörg Zastrau wrote: Let me clarify this: Normally the AFPL Ghostscript Installer/Deinstaller works as expected. Yes this is works for me too, also when I used the one year old GPL GS 8.15 and AFPL GS 8.14 installers. However I was able to reproduce a situation where the registry entrys where not removed by GS 8.51. This involved installing a previous version of GS (8.0.0) as a normal user (partly failed) and then installing and deinstalling GS 8.51 with root privileges and a few cups of coffee. OK I know now why: The uninstaller of GS deletes only the first entry of the registry. That means it uses the EnumRegKey command tocheck for the version number. In your case it finds 8.0.0 so this one is deleted and the entry of 8.51 is still in the registry. I notice that under Windows the presence/absense of a gs installation is mostly correct under the systems software management system system settings - software. My guess is that the proper way of detecting installed software involves some other database or other entries in the registry other than HKEY_LOCAL_MACHINE/SOFTWARE/AFPL Ghostscript. I'll try if I can locate an installed GS via the registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ only if this was successful I'll read the path from HKLM/SOFTWARE/AFPL Ghostscript. This should fix these problems. thanks and regards Uwe
Re: GSview/Ghostscript problems
But anyway another user reported me that old GS (de)installers don't delete the registry keys correctly so that my installer find wrong versions. I'll check this and if this is the case I'll change the code so Let me clarify this: Normally the AFPL Ghostscript Installer/Deinstaller works as expected. However I was able to reproduce a situation where the registry entrys where not removed by GS 8.51. This involved installing a previous version of GS (8.0.0) as a normal user (partly failed) and then installing and deinstalling GS 8.51 with root privileges and a few cups of coffee. This was done on a 2nd Win2000 Box. The conclusion is that checking the registry for keys is not a safe bet wether the software is installed or not as long as there is the possibility of stale registry entries no matter how they get there. I notice that under Windows the presence/absense of a gs installation is mostly correct under the systems software management system system settings - software. My guess is that the proper way of detecting installed software involves some other database or other entries in the registry other than HKEY_LOCAL_MACHINE/SOFTWARE/AFPL Ghostscript. Sigh, I've never thaught that the installer stuff will be so complicated and takes so much time. jupp... It caught me too when I did this. Something that should be a few lines ended up beeing two pages of code just to set some environment variables. Jörg -- Jörg Zastrau Universität Kaiserslautern Lehrstuhl für Hochspannungstechnik und EMV Gebäude 11 / Raum 334 Postfach 3049 67653 Kaiserslautern Tel: +49-631-205-2826 E-Mail: [EMAIL PROTECTED]
Re: GSview/Ghostscript problems
Jörg Zastrau wrote: Let me clarify this: Normally the AFPL Ghostscript Installer/Deinstaller works as expected. Yes this is works for me too, also when I used the one year old GPL GS 8.15 and AFPL GS 8.14 installers. However I was able to reproduce a situation where the registry entrys where not removed by GS 8.51. This involved installing a previous version of GS (8.0.0) as a normal user (partly failed) and then installing and deinstalling GS 8.51 with root privileges and a few cups of coffee. OK I know now why: The uninstaller of GS deletes only the first entry of the registry. That means it uses the EnumRegKey command tocheck for the version number. In your case it finds 8.0.0 so this one is deleted and the entry of 8.51 is still in the registry. I notice that under Windows the presence/absense of a gs installation is mostly correct under the systems software management system system settings - software. My guess is that the proper way of detecting installed software involves some other database or other entries in the registry other than HKEY_LOCAL_MACHINE/SOFTWARE/AFPL Ghostscript. I'll try if I can locate an installed GS via the registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ only if this was successful I'll read the path from HKLM/SOFTWARE/AFPL Ghostscript. This should fix these problems. thanks and regards Uwe
Re: GSview/Ghostscript problems
But anyway another user reported me that old GS (de)installers don't delete the registry keys correctly so that my installer find wrong versions. I'll check this and if this is the case I'll change the code so Let me clarify this: Normally the AFPL Ghostscript Installer/Deinstaller works as expected. However I was able to reproduce a situation where the registry entrys where not removed by GS 8.51. This involved installing a previous version of GS (8.0.0) as a normal user (partly failed) and then installing and deinstalling GS 8.51 with root privileges and a few cups of coffee. This was done on a 2nd Win2000 Box. The conclusion is that checking the registry for keys is not a safe bet wether the software is installed or not as long as there is the possibility of stale registry entries no matter how they get there. I notice that under Windows the presence/absense of a gs installation is mostly correct under the systems software management system system settings - software. My guess is that the proper way of detecting installed software involves some other database or other entries in the registry other than HKEY_LOCAL_MACHINE/SOFTWARE/AFPL Ghostscript. Sigh, I've never thaught that the installer stuff will be so complicated and takes so much time. jupp... It caught me too when I did this. Something that should be a few lines ended up beeing two pages of code just to set some environment variables. Jörg -- Jörg Zastrau Universität Kaiserslautern Lehrstuhl für Hochspannungstechnik und EMV Gebäude 11 / Raum 334 Postfach 3049 67653 Kaiserslautern Tel: +49-631-205-2826 E-Mail: [EMAIL PROTECTED]
Re: GSview/Ghostscript problems
Jörg Zastrau wrote: Let me clarify this: Normally the AFPL Ghostscript Installer/Deinstaller works as expected. Yes this is works for me too, also when I used the one year old GPL GS 8.15 and AFPL GS 8.14 installers. However I was able to reproduce a situation where the registry entrys where not removed by GS 8.51. This involved installing a previous version of GS (8.0.0) as a normal user (partly failed) and then installing and deinstalling GS 8.51 with root privileges and a few cups of coffee. OK I know now why: The uninstaller of GS deletes only the first entry of the registry. That means it uses the EnumRegKey command tocheck for the version number. In your case it finds "8.0.0" so this one is deleted and the entry of "8.51" is still in the registry. I notice that under Windows the presence/absense of a gs installation is mostly correct under the systems software management system "system settings -> software". My guess is that the proper way of detecting installed software involves some other database or other entries in the registry other than "HKEY_LOCAL_MACHINE/SOFTWARE/AFPL Ghostscript". I'll try if I can locate an installed GS via the registry key "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\" only if this was successful I'll read the path from "HKLM/SOFTWARE/AFPL Ghostscript". This should fix these problems. thanks and regards Uwe
Re: GSview/Ghostscript problems
>> But anyway another user reported me that old GS (de)installers don't >> delete the registry keys correctly so that my installer find wrong >> versions. I'll check this and if this is the case I'll change the code >> so Let me clarify this: Normally the AFPL Ghostscript Installer/Deinstaller works as expected. However I was able to reproduce a situation where the registry entrys where not removed by GS 8.51. This involved installing a previous version of GS (8.0.0) as a normal user (partly failed) and then installing and deinstalling GS 8.51 with root privileges and a few cups of coffee. This was done on a 2nd Win2000 Box. The conclusion is that checking the registry for keys is not a safe bet wether the software is installed or not as long as there is the possibility of stale registry entries no matter how they get there. I notice that under Windows the presence/absense of a gs installation is mostly correct under the systems software management system "system settings -> software". My guess is that the proper way of detecting installed software involves some other database or other entries in the registry other than "HKEY_LOCAL_MACHINE/SOFTWARE/AFPL Ghostscript". >> Sigh, I've never thaught that the installer stuff will be so complicated >> and takes so much time. jupp... It caught me too when I did this. Something that should be a few lines ended up beeing two pages of code just to set some environment variables. Jörg -- Jörg Zastrau Universität Kaiserslautern Lehrstuhl für Hochspannungstechnik und EMV Gebäude 11 / Raum 334 Postfach 3049 67653 Kaiserslautern Tel: +49-631-205-2826 E-Mail: [EMAIL PROTECTED]
Re: GSview/Ghostscript problems
- Original Message - From: Uwe Stöhr [EMAIL PROTECTED] To: Stephen Harris [EMAIL PROTECTED] Cc: lyx-users@lists.lyx.org; [EMAIL PROTECTED] Sent: Wednesday, November 16, 2005 4:49 PM Subject: GSview/Ghostscript problems Stephen Harris wrote: I downloaded your Lyx1.3.6_1 version 2 installer yesterday, Nov. 15, the full version. But I only uninstall my old Lyx1.3.6. Still the install went well. And it loaded Gsview to c:\program files, which was not where I have one. It showed up in the Edit/Preferences/Path prefix. Strangely, the Path prefix also showed gs8.13 which I've deleted in favor of gs8.51and which is also in my Windows path. So I'm not sure where it came from, The installer checks in the registry for ther version numbers of Ghostscript, if one is found its path is added to the path_prefix. 8.13 comes before 8.51 in the registry and you therefore had troubles. Have you deinstalled version 8.13 before you installed 8.51? Having two version installed mostly error prone. But anyway another user reported me that old GS (de)installers don't delete the registry keys correctly so that my installer find wrong versions. I'll check this and if this is the case I'll change the code so that only the greatest version number is taken for the path_prefix. Sigh, I've never thaught that the installer stuff will be so complicated and takes so much time. It must bring you a rare joy unexperienced my most mortals. :=) regards Uwe Yes, I did a find for (gs8.13) in the registry and there it was. So I deleted the gs8.13 value. I did a fresh uninstall/reinstall of just LyX. I copied just find.exe from C:\msys\1.0\bin to C:\Lyx\bin. Tex Information was correct. Everything seems to work perfectly. The spellchecker also worked, although it was not shown in the Path Prefix; I have it installed in C:\Aspell which is in my Windows path. I didn't dl a non-English dictionary. To test it thoroughly I suppose I should uninstall everything but Aspell. Version 2 has small problems easy to fix manually. It looks ideal for newcomer installations, someone complained about having to visit the websites for installs, though I should test it. Let's hope the LyX improvements are easy to incorporate. Good job, thank you, Stephen
Re: GSview/Ghostscript problems
- Original Message - From: Uwe Stöhr [EMAIL PROTECTED] To: Stephen Harris [EMAIL PROTECTED] Cc: lyx-users@lists.lyx.org; [EMAIL PROTECTED] Sent: Wednesday, November 16, 2005 4:49 PM Subject: GSview/Ghostscript problems Stephen Harris wrote: I downloaded your Lyx1.3.6_1 version 2 installer yesterday, Nov. 15, the full version. But I only uninstall my old Lyx1.3.6. Still the install went well. And it loaded Gsview to c:\program files, which was not where I have one. It showed up in the Edit/Preferences/Path prefix. Strangely, the Path prefix also showed gs8.13 which I've deleted in favor of gs8.51and which is also in my Windows path. So I'm not sure where it came from, The installer checks in the registry for ther version numbers of Ghostscript, if one is found its path is added to the path_prefix. 8.13 comes before 8.51 in the registry and you therefore had troubles. Have you deinstalled version 8.13 before you installed 8.51? Having two version installed mostly error prone. But anyway another user reported me that old GS (de)installers don't delete the registry keys correctly so that my installer find wrong versions. I'll check this and if this is the case I'll change the code so that only the greatest version number is taken for the path_prefix. Sigh, I've never thaught that the installer stuff will be so complicated and takes so much time. It must bring you a rare joy unexperienced my most mortals. :=) regards Uwe Yes, I did a find for (gs8.13) in the registry and there it was. So I deleted the gs8.13 value. I did a fresh uninstall/reinstall of just LyX. I copied just find.exe from C:\msys\1.0\bin to C:\Lyx\bin. Tex Information was correct. Everything seems to work perfectly. The spellchecker also worked, although it was not shown in the Path Prefix; I have it installed in C:\Aspell which is in my Windows path. I didn't dl a non-English dictionary. To test it thoroughly I suppose I should uninstall everything but Aspell. Version 2 has small problems easy to fix manually. It looks ideal for newcomer installations, someone complained about having to visit the websites for installs, though I should test it. Let's hope the LyX improvements are easy to incorporate. Good job, thank you, Stephen
Re: GSview/Ghostscript problems
- Original Message - From: "Uwe Stöhr" <[EMAIL PROTECTED]> To: "Stephen Harris" <[EMAIL PROTECTED]> Cc:; <[EMAIL PROTECTED]> Sent: Wednesday, November 16, 2005 4:49 PM Subject: GSview/Ghostscript problems Stephen Harris wrote: I downloaded your Lyx1.3.6_1 version 2 installer yesterday, Nov. 15, the full version. But I only uninstall my old Lyx1.3.6. Still the install went well. And it loaded Gsview to c:\program files, which was not where I have one. It showed up in the Edit/Preferences/Path prefix. Strangely, the Path prefix also showed gs8.13 which I've deleted in favor of gs8.51and which is also in my Windows path. So I'm not sure where it came from, The installer checks in the registry for ther version numbers of Ghostscript, if one is found its path is added to the path_prefix. 8.13 comes before 8.51 in the registry and you therefore had troubles. Have you deinstalled version 8.13 before you installed 8.51? Having two version installed mostly error prone. But anyway another user reported me that old GS (de)installers don't delete the registry keys correctly so that my installer find wrong versions. I'll check this and if this is the case I'll change the code so that only the greatest version number is taken for the path_prefix. Sigh, I've never thaught that the installer stuff will be so complicated and takes so much time. It must bring you a rare joy unexperienced my most mortals. :=) regards Uwe Yes, I did a find for (gs8.13) in the registry and there it was. So I deleted the gs8.13 value. I did a fresh uninstall/reinstall of just LyX. I copied just find.exe from C:\msys\1.0\bin to C:\Lyx\bin. Tex Information was correct. Everything seems to work perfectly. The spellchecker also worked, although it was not shown in the Path Prefix; I have it installed in C:\Aspell which is in my Windows path. I didn't dl a non-English dictionary. To test it thoroughly I suppose I should uninstall everything but Aspell. Version 2 has small problems easy to fix manually. It looks ideal for newcomer installations, someone complained about having to visit the websites for installs, though I should test it. Let's hope the LyX improvements are easy to incorporate. Good job, thank you, Stephen