Menu
▾
▴
jabref-users
|
From: pandion <pa...@fr...> - 2007-11-15 21:27:39
|
Hi everyone, I know perfectly well, that you actually don't need the win32 installer to run JabRef. However, it's a nice feature particularly for people who are no IT buffs and who might want to uninstall the thing later on. Deleting a 'jar' is totally foreign to them. I'm writing to the list because the win32 installer of JabRef unpacks an executable which is only executable with an admin password under Windows Vista. The UAC is unhappy about the JabRef.exe. Does anyone know a fix or workaround? Or will there be another executable which doesn't cause the trouble in a few day? Help would be appreciated a lot. Thanks a lot. Cheers, Thomas |
|
From: Christopher O. <oe...@oe...> - 2007-11-16 15:00:51
|
Hi Thomas, this is definitely a bug if you are right. The install definitely needs admin rights, but running the JabRef.exe should not. Can you confirm again by running the exe from the folder you installed it into? Just to check that it is not an artifact of running JabRef from the installer (which launches it using Admin rights). Cheers, Christopher P.S.: I cc'ed Uwe, as he is our NSIS-master. On Thu, 15 Nov 2007 16:12:57 +0100, pandion <pa...@fr...> wrote: > Hi everyone, > > I know perfectly well, that you actually don't need the win32 installer > to run JabRef. However, it's a nice feature particularly for people who > are no IT buffs and who might want to uninstall the thing later on. > Deleting a 'jar' is totally foreign to them. > > I'm writing to the list because the win32 installer of JabRef unpacks an > executable which is only executable with an admin password under Windows > Vista. The UAC is unhappy about the JabRef.exe. > > Does anyone know a fix or workaround? Or will there be another > executable which doesn't cause the trouble in a few day? > > Help would be appreciated a lot. > Thanks a lot. > > > Cheers, Thomas > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Jabref-users mailing list > Jab...@li... > https://lists.sourceforge.net/lists/listinfo/jabref-users |
|
From: pandion <pa...@fr...> - 2007-11-17 15:54:28
|
Dear Christopher Thank you for your reply. Yes, I can confirm the behaviour I described before. Even though I had started the Jabref.exe directly before, I did it again to be absolutely sure. The symbol of the executable is even endowed with one of these "nice" little Windows shields indicating executables which need administrative privileges and provoke UAC confirmation dialogues. I also attach a small screenshot of the Installer-Symbol and of the Jabref Folder on the C: drive so that you can see that I am aware of the difference between the two. I can confirm the behaviour on Windows Vista Ultimate (German) and Windows Vista Business (German). All available patches are applied to both installations. One machine is a standard HP office system, the other is a machine assembled by a small local hardware assembler. Starting the jar directly causes no trouble, whatsoever. It's only the executable which needs administrative privileges. The UAC dialogue states the usual things (in German on my machine, what I post here are ad-hoc translations): * An unidentified program wants to access your computer. * Unidentified manufacturer. * Cancel - Allow I hope that this information is helpful to you. :-) Thanks and kind regards, Thomas Christopher Oezbek schrieb: > Hi Thomas, > this is definitely a bug if you are right. > > The install definitely needs admin rights, but running the JabRef.exe > should not. > > Can you confirm again by running the exe from the folder you installed > it into? Just to check that it is not an artifact of running JabRef from > the installer (which launches it using Admin rights). > > Cheers, > Christopher > > P.S.: I cc'ed Uwe, as he is our NSIS-master. > > On Thu, 15 Nov 2007 16:12:57 +0100, pandion <pa...@fr...> wrote: > >> Hi everyone, >> >> I know perfectly well, that you actually don't need the win32 installer >> to run JabRef. However, it's a nice feature particularly for people who >> are no IT buffs and who might want to uninstall the thing later on. >> Deleting a 'jar' is totally foreign to them. >> >> I'm writing to the list because the win32 installer of JabRef unpacks an >> executable which is only executable with an admin password under Windows >> Vista. The UAC is unhappy about the JabRef.exe. >> >> Does anyone know a fix or workaround? Or will there be another >> executable which doesn't cause the trouble in a few day? >> >> Help would be appreciated a lot. >> Thanks a lot. >> >> >> Cheers, Thomas >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2005. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> _______________________________________________ >> Jabref-users mailing list >> Jab...@li... >> https://lists.sourceforge.net/lists/listinfo/jabref-users |
|
From: Christopher O. <oe...@oe...> - 2007-11-18 17:42:58
|
Hi Thomas, I have looked into the issue and its mostly Vista's vault (for thinking that also all programs generated by NSIS need admin rights). I have applied the suggested modification of setting the required admin level for Vistas UAC by RequestExecutionLevel user Could you give the version at http://www.inf.fu-berlin.de/~oezbek/jabref/JabRefSetup.exe a spin and see if it works? Cheers, Christopher On Sat, 17 Nov 2007 16:54:21 +0100, pandion <pa...@fr...> wrote: > Dear Christopher > > Thank you for your reply. > > Yes, I can confirm the behaviour I described before. > Even though I had started the Jabref.exe directly before, I did it again > to be absolutely sure. The symbol of the executable is even endowed with > one of these "nice" little Windows shields indicating executables which > need administrative privileges and provoke UAC confirmation dialogues. > > I also attach a small screenshot of the Installer-Symbol and of the > Jabref Folder on the C: drive so that you can see that I am aware of the > difference between the two. > > I can confirm the behaviour on Windows Vista Ultimate (German) and > Windows Vista Business (German). All available patches are applied to > both installations. One machine is a standard HP office system, the > other is a machine assembled by a small local hardware assembler. > > Starting the jar directly causes no trouble, whatsoever. It's only the > executable which needs administrative privileges. > > The UAC dialogue states the usual things (in German on my machine, what > I post here are ad-hoc translations): > * An unidentified program wants to access your computer. > * Unidentified manufacturer. > * Cancel - Allow > > I hope that this information is helpful to you. :-) > > > Thanks and kind regards, > Thomas > > > > Christopher Oezbek schrieb: >> Hi Thomas, >> this is definitely a bug if you are right. >> The install definitely needs admin rights, but running the JabRef.exe >> should not. >> Can you confirm again by running the exe from the folder you installed >> it into? Just to check that it is not an artifact of running JabRef >> from the installer (which launches it using Admin rights). >> Cheers, >> Christopher >> P.S.: I cc'ed Uwe, as he is our NSIS-master. >> On Thu, 15 Nov 2007 16:12:57 +0100, pandion <pa...@fr...> >> wrote: >> >>> Hi everyone, >>> >>> I know perfectly well, that you actually don't need the win32 installer >>> to run JabRef. However, it's a nice feature particularly for people who >>> are no IT buffs and who might want to uninstall the thing later on. >>> Deleting a 'jar' is totally foreign to them. >>> >>> I'm writing to the list because the win32 installer of JabRef unpacks >>> an >>> executable which is only executable with an admin password under >>> Windows >>> Vista. The UAC is unhappy about the JabRef.exe. >>> >>> Does anyone know a fix or workaround? Or will there be another >>> executable which doesn't cause the trouble in a few day? >>> >>> Help would be appreciated a lot. >>> Thanks a lot. >>> >>> >>> Cheers, Thomas >>> >>> ------------------------------------------------------------------------- >>> This SF.net email is sponsored by: Microsoft >>> Defy all challenges. Microsoft(R) Visual Studio 2005. >>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >>> _______________________________________________ >>> Jabref-users mailing list >>> Jab...@li... >>> https://lists.sourceforge.net/lists/listinfo/jabref-users |
|
From: <uwe...@we...> - 2007-11-20 16:55:23
|
Christopher Oezbek schrieb: > The install definitely needs admin rights, Admin rights are no longer required with the new installer version I sent some monts ago to Christopher. Christopher, is this version considered to be used or not? I'm asking because I got no feedback until now. >> I'm writing to the list because the win32 installer of JabRef unpacks an >> executable which is only executable with an admin password under Windows >> Vista. The UAC is unhappy about the JabRef.exe. I don't have Vista but I had a similar problem with another installer for LyX. The solution was to compile the .exe a different way. I can't tell more than this was a compiler settings problem, when I remember correctly. The installer doesn't touch the JabRef.exe anyway. regards Uwe |
|
From: <uwe...@we...> - 2007-11-20 16:57:35
|
Christopher Oezbek schrieb: > I have looked into the issue and its mostly Vista's vault (for > thinking that also all programs generated by NSIS need admin rights). I > have applied the suggested modification of setting the required admin > level for Vistas UAC by > > RequestExecutionLevel user Is this a Java or an NSIS setting? regards Uwe |
|
From: Christopher O. <oe...@oe...> - 2007-11-20 23:00:22
|
> Is this a Java or an NSIS setting? This is an NSIS thing. Cheers, Christopher |
|
From: Christopher O. <oe...@oe...> - 2007-11-20 23:11:28
|
On Tue, 20 Nov 2007 17:54:20 +0100, Uwe Stöhr <uwe...@we...> wrote: > Admin rights are no longer required with the new installer version I > sent some monts ago to Christopher. Christopher, is this version > considered to be used or not? I'm asking because I got no feedback until > now. We are using your installer from January, which needs admin rights. I am sorry, if you send another one, I must have missed it. Can you resend it? Thanks, Christopher |
|
From: <uwe...@we...> - 2007-11-21 02:25:51
|
Christopher Oezbek schrieb: > We are using your installer from January, which needs admin rights. Here is the latest installer for JabRef 2.3 to test: http://fkurth.de/uwest/JabRef/JabRefSetup.exe Please try out if it works correctly on Vista. Changelog: - JabRef can now also installed without admin permissions - prevent that the same JabRef Version can't be installed twice - prevent that JabRef can't be uninstalled as user when it has been installed with admin permissions regards Uwe |
|
From: pandion <pa...@fr...> - 2007-11-21 10:02:13
|
Dear Uwe I am afraid to tell you, that the new installer is worse than the old one. [Problem 1: Installer] No system administrator wants his/her users to install applications without admin privileges. So there was no complaint whatsoever, that the installer needed admin privleges. The installation without admin privileges goes to the .../AppData/Roaming folder of a specific profile. This is bad. I'm sorry, but this is real bad. The installer should run under administrative privleges only and install the application to /Program Files/JabRef. That's what the old installer did and what the new one still does when you start it with admin privileges. Please, think about all those admins out there that have to administer extensive Windows environments! When users are capable of installing applications into their profile folders this causes hours and hours of additional work because this is just not tolerable in large environments! [Problem 2: Executable] The executable itself, which was why this thread was started in the first place, still needs admin privleges to run (meaning: causes an UAC prompt) after you installed JabRef with admin privileges. So I am afraid, from my point of view the original problem isn't solved and a new one was introduced. I did not and will not test the JabRef executable after an installation without admin privileges into an .../AppData/Roaming profile folder. This makes my skin crawl. I am very sorry to give you such an unpleasant reply. However, I do appreciate that you are working on a solution a lot! So, thank you for that. Regards, Thomas Uwe Stöhr schrieb: > > Here is the latest installer for JabRef 2.3 to test: > http://fkurth.de/uwest/JabRef/JabRefSetup.exe > > Please try out if it works correctly on Vista. > > Changelog: > - JabRef can now also installed without admin permissions > - prevent that the same JabRef Version can't be installed twice > - prevent that JabRef can't be uninstalled as user when it has been > installed with admin permissions > > regards Uwe |
|
From: Christopher O. <oe...@oe...> - 2007-11-21 10:22:11
|
Hi Thomas, thanks for giving Uwe's version a spin. Have you also tried the version at http://www.inf.fu-berlin.de/~oezbek/jabref/JabRefSetup.exe ? > [Problem 1: Installer] > No system administrator wants his/her users to install applications > without admin privileges. I don't think this is correct. We as the JabRef developers should strive for the software being as comfortable as possible to use and install. This includes that users can install JabRef if they do not have admin rights (in this case installing is more like copying files to a directory anyway). > Please, think about all those admins out there that have to administer > extensive Windows environments! When users are capable of installing > applications into their profile folders this causes hours and hours of > additional work because this is just not tolerable in large environments! But a "smart" user can always download the jar and copy it to their profile, and work around the installer. > [Problem 2: Executable] > The executable itself, which was why this thread was started in the > first place, still needs admin privleges to run (meaning: causes an UAC > prompt) after you installed JabRef with admin privileges. Can you verify that the above version retains the problem? Thanks for helping out with this, Christopher |
|
From: <uwe...@we...> - 2007-11-21 11:38:11
|
pandion schrieb: > [Problem 1: Installer] > No system administrator wants his/her users to install applications > without admin privileges. So there was no complaint whatsoever, that the > installer needed admin privleges. There were complaints. There is no need to force users not to use JabRef. When you install JabRef as users you can only set user registry variables. And Windows provides this feature exactly for that purpose! > The installation without admin > privileges goes to the .../AppData/Roaming folder of a specific profile. This is correct as this is the default install folder for user installations, this is set as default by Windows. You can choose another directory if you like. > Please, think about all those admins out there that have to administer > extensive Windows environments! When users are capable of installing > applications into their profile folders this causes hours and hours of > additional work because this is just not tolerable in large environments! This is not true. Every users is allowed to write into his user folders, that's what they are for. As I said, users cannot set system wide settings, so all settings they can make only applies to their account, other users on the computer don't see any difference. > [Problem 2: Executable] > The executable itself, which was why this thread was started in the > first place, still needs admin privleges to run (meaning: causes an UAC > prompt) after you installed JabRef with admin privileges. You mean the JabRef.exe? This has not yet been touched because I have not the latest source code. Christopher will send me the sources and I'll correct also for this application the UAC setting.. > I did not and will not test the JabRef executable after an installation > without admin privileges into an .../AppData/Roaming profile folder. > This makes my skin crawl. Then install it as admin. But anyway, before you shout again, please argue what exactly is incorrect with the user installation. I got so many requests for user install for my installer for the program LyX so this is really wanted, and other programs offer this, for example even such a complex program like MiKTeX. regards Uwe |
|
From: pandion <pa...@fr...> - 2007-11-21 15:03:27
|
Dear Uwe Obviously you were offended by my reply. That was by no means my intention and I apologize for this!! I will try again to state, what I wanted to state. Hopefully I am able to make you see what I mean without offending you again! I appreciate all kinds of endeavours in the open source field and have no intention of discouraging or offending you. -- > You mean the JabRef.exe? This has not yet been touched because I have > not the latest source code. Let me quote a sentence of my original posting to the list (Nov 15th): "I'm writing to the list because the win32 installer of JabRef unpacks an executable which is only executable with an admin password under Windows Vista. The UAC is unhappy about the JabRef.exe." So I always wrote about the executable and not about the installer. I hope that we can agree on a misunderstanding in this respect. -- Concerning the installer issue: Let me explain that I am writing from an administrator perspective. There is in very, very many situations an urgent need to force users not to be able to install something on their own. The work of a whole team of administrators can be destroyed or at least tainted if users can install whatever they like into their personal profiles. There are also organisational guidelines that have to be followed, etc. I am sure that many users have a different opinion on this and request a user install option. Their organisation may not pre-install JabRef on their machines or whatever... But trying to convince the organisation to install it in an organised way would be a lot better in my opinion. I have seen so many machines in terrible states because users tinkered with them in every possible way. Your opinion may be different, of course, but mine and the one of most admins I know personally is, that installers should not install to user profiles. I also got an Email from Christopher Oezbek, who reminded me that smart users may download the jar and just use the jar. Obviously he's got a point there! :-) Concerning the default installation path and the registry keys for installations without user admin privileges: Yes, I am absolutely aware that .../AppData/Roaming is the default path for user installations. And yes, there are some installers which offer user installs. MiKTeX is the example you stated, Skype is another one. Yet, installers like these have been causing problems to me and my colleagues in the past and will go on to do so. I think it's very, very good to use the registry keys (or a config file) within the user profile to store the personal settings of a user. So every user can have his/her personal settings - irrespective of where the actual installation goes. Additionally no system-wide files or settings need to be made accessible for everyone. So that's great. Talking from my personal experience I can just state that within a large environment user installs cause problems! By keeping the installer the way it was before you can help organisations. - At the same time you do not prevent home users from using JabRef. A home user has the admin password. So he/she will be able to install JabRef. >> I did not and will not test the JabRef executable after an >> installation without admin privileges into an .../AppData/Roaming >> profile folder. This makes my skin crawl. Perhaps this paragraph was a bit too emotional. :-) You see, Uwe, I think JabRef is great. I would like to be able to recommend and use it in small and large environments. From my point of view, the option "user install" makes it just less attractive for well-managed environments. That's all. Kind regards and best wishes, Thomas |
|
From: <uwe...@we...> - 2007-11-21 17:06:45
|
pandion schrieb: > Obviously you were offended by my reply. That was by no means my > intention and I apologize for this!! I was not offended, sorry when it sounded like this. > Let me quote a sentence of my original posting to the list (Nov 15th): > "I'm writing to the list because the win32 installer of JabRef unpacks > an executable which is only executable with an admin password under > Windows Vista. The UAC is unhappy about the JabRef.exe." I'll fix this as soon when I get the latest source code from Christopher. Looking at your second post, it seems that it isn't enough to set the execution level for Vista. I'll try to provide an alternative jabref.jar launcher executable when I couldn't fix this using NSIS. > So I always wrote about the executable and not about the installer. I see now. But anyway my new installer version is a big improvement in terms of usability and mainatinability of the code. > Concerning the installer issue: > Let me explain that I am writing from an administrator perspective. > There is in very, very many situations an urgent need to force users not > to be able to install something on their own. The work of a whole team > of administrators can be destroyed or at least tainted if users can > install whatever they like into their personal profiles. There are also > organisational guidelines that have to be followed, etc. I have had many many discussions about this issue and no Administrator could tell what exactly could be a problem. The Windows infrastructures allows user installations and describe this in techbase articles. A users cannot destroy the work of anybody. Sorry, but what you say is a polemic. What could be destroyed by assigning of a file extension in HCKU - nothing? The installer does nothing more. This is the same when you do this via the file explorer options. This is always possible for users, so what is the problem, that the installer does this by one click instead of doing this manually by 10 clicks? > But trying to convince the organisation to > install it in an organised way would be a lot better in my opinion. Then talk to people working in a big company - they all confirm that this is impossible, even at universities. But anyway when a user has a porgram locally installed and the company decides to install it system wide, there won't be a problem. The user can then use the system wide version or his local one. > I also got an Email from Christopher Oezbek, who reminded me that smart > users may download the jar and just use the jar. > Obviously he's got a point there! :-) What do you mean? > Concerning the default installation path and the registry keys for > installations without user admin privileges: > Yes, I am absolutely aware that .../AppData/Roaming is the default path > for user installations. And yes, there are some installers which offer > user installs. Why not, they use the Windows infrastructure. There's no reason of not using what is offered. Not doing this is as if your TV has a remote control, but you force your children not to use it to become good childen. > MiKTeX is the example you stated, Skype is another one. > Yet, installers like these have been causing problems to me and my > colleagues in the past and will go on to do so. That is a problem of the installers. E.g. MiKTeX needs the registry extensively and not everything is possible as user in the registry. Due to these kind of restrictions I e.g. decided not to offer to install LyX as user. But the JabRef installer does nothing more then setting a file extension and to add a start menu shortcut. Things you can always do as user. > I think it's very, very good to use the registry keys (or a config file) > within the user profile to store the personal settings of a user. So > every user can have his/her personal settings - irrespective of where > the actual installation goes. Additionally no system-wide files or > settings need to be made accessible for everyone. So that's great. You haven't looked in the installer code, right? If you do, you'll see that no personal settings are made. This can be done by the user later when he wants. regards Uwe |
|
From: pandion <pa...@fr...> - 2007-11-21 15:36:09
|
Dear Christopher Thanks for your reply. I tested the JabRefSetup downloaded from the link you provided. These are my test results: WinXP pro SP 2 -------------- * using Java Runtime Environment 1.6 Update 3 * installation using JabRefSetup under admin account: no problem * double click on JabRef shortcut and on JabRef.exe in admin and in user account: no problem * starting the jar directly in admin and in user account: no problem WinVista Ultimate ----------------- * using Java Runtime Environment 1.6 Update 3 * starting JabRefSetup requires admin privileges: :-) i like it! * installation using JabRefSetup and admin privileges: no problem * starting the jar directly: no problem, no admin privileges necessary * double click on JabRef shortcut and on JabRef.exe: - no admin privileges necessary - the computer starts working for a few seconds, then nothing more happens - after starting JabRef.exe with admin privileges explicitly the same thing happens: nothing much. So almost all problems are solved in your installer. Only one problem remains: The new JabRef.exe doesn't do much under WinVista while it works properly under WinXP. Kind regards, Thomas Christopher Oezbek schrieb: > Hi Thomas, > thanks for giving Uwe's version a spin. Have you also tried the > version at > > http://www.inf.fu-berlin.de/~oezbek/jabref/JabRefSetup.exe > > ? > >> [Problem 1: Installer] >> No system administrator wants his/her users to install applications >> without admin privileges. > > I don't think this is correct. We as the JabRef developers should strive > for the software being as comfortable as possible to use and install. > This includes that users can install JabRef if they do not have admin > rights (in this case installing is more like copying files to a > directory anyway). > >> Please, think about all those admins out there that have to administer >> extensive Windows environments! When users are capable of installing >> applications into their profile folders this causes hours and hours of >> additional work because this is just not tolerable in large environments! > > But a "smart" user can always download the jar and copy it to their > profile, and work around the installer. > >> [Problem 2: Executable] >> The executable itself, which was why this thread was started in the >> first place, still needs admin privleges to run (meaning: causes an >> UAC prompt) after you installed JabRef with admin privileges. > > Can you verify that the above version retains the problem? > > Thanks for helping out with this, > Christopher |
|
From: Christopher O. <oe...@oe...> - 2007-11-21 17:23:19
|
Hi Thomas, > * double click on JabRef shortcut and on JabRef.exe: > - no admin privileges necessary > - the computer starts working for a few seconds, then nothing more > happens > - after starting JabRef.exe with admin privileges explicitly the same > thing happens: nothing much. Can you repeat that test by running it under the command line? Probably this is a problem with JabRef crashing and you not seeing the stack-trace. Thanks, Christopher |
|
From: <uwe...@we...> - 2007-11-21 21:32:52
|
Dear pandion, I uploaded a new version of the installer to http://fkurth.de/uwest/JabRef/ Could you please test this out on Vista? --- Concerning our user install dispute, maybe I was too harsh in my last post, but I had this discussion too often. What I would like to discuss instead of general opinions are directly your concerns, like when user installs, the registy setting blablub is set that interferes with the Windows guideline #xxxxx. But anyway, JabRef's installer does nothing more what users are allowed to do no matter if they use the installer or not, so I promise it is safe to use on any Windows platform. thanks in advance and regards Uwe |
|
From: pandion <pa...@fr...> - 2007-11-23 12:32:21
|
Dear Uwe I tested your installer under Windows Vista. The installer and the uninstallation routine both work fine - irrespective of whether you install it as user or as an admin. (Yes, I tested both for you! :-) ) (The problem with the executable remains: JabRef.exe provokes an UAC message and thus needs admin privileges. But Christopher solved this problem as you'll learn from another e-mail in a few minutes.) Have a nice weekend! Thomas Uwe Stöhr schrieb: > Dear pandion, > > I uploaded a new version of the installer to > http://fkurth.de/uwest/JabRef/ > > Could you please test this out on Vista? > > thanks in advance and regards > Uwe |
|
From: pandion <pa...@fr...> - 2007-11-23 12:33:06
|
Dear Christopher I've just tested your installer and executable again. New download, remove all traces of old installations, clean install after reboot. Actually I wanted to run it from the command line to see what the output to the command line would be, as you requested... but it simply worked! I have no idea what the problem was last time, but now it works. Plain and simple. So... great! :-) Cheers, Thomas Christopher Oezbek schrieb: > Hi Thomas, > >> * double click on JabRef shortcut and on JabRef.exe: >> - no admin privileges necessary >> - the computer starts working for a few seconds, then nothing more >> happens >> - after starting JabRef.exe with admin privileges explicitly the >> same thing happens: nothing much. > > Can you repeat that test by running it under the command line? Probably > this is a problem with JabRef crashing and you not seeing the stack-trace. > > Thanks, > Christopher > |
|
From: <uwe...@we...> - 2007-11-23 14:56:14
|
pandion schrieb: > Actually I wanted to run it from the command line to see what the output > to the command line would be, as you requested... but it simply worked! Good to hear! > I tested your installer under Windows Vista. > > The installer and the uninstallation routine both work fine - irrespective of whether you install > it as user or as an admin. (Yes, I tested both for you! :-) ) Many thanks! So the next installer version could be the one I created including Christopher's JabRef.exe Christopher, could you please send me in private mail what you changed in the JabRef.exe source code that it works now? best regards Uwe |
|
From: Christopher O. <oe...@oe...> - 2007-11-28 09:51:41
|
Hi Uwe, > Christopher, could you please send me in private mail what you changed > in the JabRef.exe source code that it works now? the only change I did was to add the RequestExecutionLevel user SilentInstall silent XPStyle on RequestExecutionLevel user Section "" We now use the latest version of your setup.nsi with the following modification (since we define the VERSION already in the build file): !ifndef VERSION !define VERSION "2.3" !endif Thanks for resolving this, the new installer will be used for JabRef 2.3.1, which will be released shortly. Christopher |
|
From: <uwe...@we...> - 2007-11-28 11:44:56
|
Christopher Oezbek schrieb: >> Christopher, could you please send me in private mail what you changed >> in the JabRef.exe source code that it works now? > > the only change I did was to add the RequestExecutionLevel user > > SilentInstall silent > XPStyle on > RequestExecutionLevel user But I did exactly the same and the user Pandion reported that it doesn't work but your version does. But anyway, now it works and can be published. > Thanks for resolving this, the new installer will be used for JabRef > 2.3.1, which will be released shortly. Good news! thanks and regards Uwe |
|
From: Christopher O. <oe...@oe...> - 2007-11-29 06:58:58
|
> But I did exactly the same and the user Pandion reported that it doesn't > work but your version does. But anyway, now it works and can be > published. I believe that was rather a problem with not uninstalling first/not restart Vista (he reported that initially it did not work, but then later on did). We will see what happens with 2.3.1. Cheers, Christopher |
Thanks for helping keep SourceForge clean.
X