Overview
Artifact ID: | 780ec1c9fe412a94c81f6e2ae86d0d4cb2edb76f |
---|---|
Ticket: | c8c0b78c840e4df9aefd2687bf6cac5abfce08e5
Windows 7: "fossil ui" and "fossil server" fail |
User & Date: | anonymous 2010-10-19 09:11:14 |
Changes
- Appended to comment:
<hr /><i>anonymous claiming to be arichardson added on 2010-10-19 09:11:14:</i><br /> >The original poster uses windir/system32. I think it's not a good idea, to use such an special OS folder for a user installed executable. I can't agree with that. The executable should absolutely not care where it's installed. Why should it stop working in some magic location? If the OS wants to prevent the installation, fine, if group policy wants to prevent it, also fine, but otherwise the executable should work as expected. I have installed many programs in %windir%\system32 in the past and this is the first time there's ever been a problem. >Especially Vista/Win7 haves special mechanismns to protect this folder. The only "special mechanism" is a dialog box saying "you want to do this? really?" and me saying "yes". >In addition to this: windows uses differrent ways to expand paths while searching executables(see above). As far as I can see this is the only valid argument against fixing this, that it would require OS-specific code in a "#ifdef _WIN32" block. I hate that kind of thing normally.