Issue497854
This issue tracker has been migrated to GitHub,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
Created on 2001-12-30 14:31 by loewis, last changed 2022-04-10 16:04 by admin. This issue is now closed.
Messages (8) | |||
---|---|---|---|
msg8555 - (view) | Author: Martin v. Löwis (loewis) * | Date: 2001-12-30 14:31 | |
Using the Windows installer of Python 2.2 on Windows XP Professional, as a user "root" who is member of the Administrator's group, performing an admin installation, the Python 2.2 program group does not show up in the start menu of other users. The cause for this problem is that the installer puts the shortcuts into \Documents and Settings\root\Start Menu, not into \Documents and Settings\All Users\Start Menu. Notice that it is difficult to login as Administrator on XP, since the Administrator account is not displayed on the welcome screen (only if the old-style login screen is selected). Even if installing Python as Administrator, the shortcuts still end up in \Documents and Settings\Administrator\Start Menu. |
|||
msg8556 - (view) | Author: R. Lindsay Todd (rltodd) | Date: 2002-02-22 17:19 | |
Logged In: YES user_id=283405 This is also a problem under Windows 2000 Professional, where I am actually logged in as "Administrator" and have made sure it is a full administrative install I'm doing. Registry settings are properly made for everyone; it is just the short cuts that don't appear. I've been working around this by manually moving the program group folder to "All Users" and changing the ACLs. This should be done before installing win32all, which will create the program group under "All Users". |
|||
msg8557 - (view) | Author: R. Lindsay Todd (rltodd) | Date: 2002-03-22 18:29 | |
Logged In: YES user_id=283405 The Python 2.2.1c1 installer for Windows still has this shortcoming: Even when doing an administrative install, shortcuts for Python are created in "Administrator"s profile, not "All Users". However, various extensions, like wxpython, win32all, etc. seem to get this right. |
|||
msg8558 - (view) | Author: Tim Peters (tim.peters) * | Date: 2002-03-22 19:02 | |
Logged In: YES user_id=31435 Yes, the installer hasn't changed, and won't for 2.2.1 unless somebody other than me can make time to do it. That seems unlikely to the point of fantasy, alas. |
|||
msg8559 - (view) | Author: Guido van Rossum (gvanrossum) * | Date: 2002-03-22 20:55 | |
Logged In: YES user_id=6380 Then at least let's remember to fix this in 2.3. |
|||
msg8560 - (view) | Author: Tim Peters (tim.peters) * | Date: 2002-04-04 19:26 | |
Logged In: YES user_id=31435 Changed to Windows/2.2.1 candidate, assigned to me, and boosted priority. |
|||
msg8561 - (view) | Author: Tim Peters (tim.peters) * | Date: 2002-04-04 19:58 | |
Logged In: YES user_id=31435 The install script had gotten lost in the maze of Wise system vrbls, so the same (or similar) problem was evident on Win2K. The release22-maint branch contains a putative fix now, which works OK on Win2K, but I don't have access to an XP box and don't know whether "the rules" changed there. |
|||
msg8562 - (view) | Author: Tim Peters (tim.peters) * | Date: 2002-04-04 20:02 | |
Logged In: YES user_id=31435 Checked in on the trunk too. Did all I can do here, so closing it. |
History | |||
---|---|---|---|
Date | User | Action | Args |
2022-04-10 16:04:50 | admin | set | github: 35849 |
2001-12-30 14:31:42 | loewis | create |