summaryrefslogtreecommitdiffstats
path: root/PCbuild/Uninstal.wse
Commit message (Collapse)AuthorAgeFilesLines
* New runtime vrbl DOADMIN. When false, we never try to write under HKLM,Tim Peters2001-08-051-3/+4
| | | | | | | | | | | | and install the Python and MS runtime DLLs into the Python dir instead of a system dir. Initial value is taken from new compiler vrbl _DOADMIN_ (default true), and forced to false if the user doesn't have admin privs. This makes it possible to *test* non-admin installs on machines where the distinction doesn't exist (like my home box), via just changing _DOADMIN_. It may also be useful for users who don't *want* an installer to scribble into their system dir (for example, me(! most days)), but that would require adding more GUI to let them get at it.
* Just changes to comments.Tim Peters2001-08-011-3/+0
|
* I hope this irons out the Add/Remove kinks on Win2K for users w/o AdminTim Peters2001-07-311-4/+13
| | | | privs, but haven't tested that yet. Doesn't hurt on Win98SE, anyway.
* Massive fiddling to get the install to work at all on a Win2K box under aTim Peters2001-07-301-0/+507
plain unprivileged User acct: + Had to duplicate Wise's Uninstal.wse script, in order to change the line at its end that unconditionally tries to write uninstall info under HKLM. This is our new file Uninstal.wse, which must be included by python20.wse instead of using Wise's version. + In every other case we write to HKLM, also write to HKCU instead (we were already doing that in *most* places, but not quite all). + If the user doesn't have admin privs, the DLLs we usually write to the system dir are written to the root of the Python installation instead. That's python22.dll, plus the two MSVC runtime DLLs. + Added a new component "Register file extensions". Registering .py etc is done under HKEY_CLASSES_ROOT, and that also requires admin privs; i.e., AFAICT it's impossible for an unprivileged user to accomplish this. In the component selection dialog, if the user doesn't have admin privs I gray out this new component so the user knows they aren't getting file extensions. After all that, Python installs, the Start Menu entries are OK, it runs its test suite to completion, and the uninstaller works too. Only known problem so far is that the integration with Win2K's Add/Remove subsystem isn't quite right yet in this irritating case.