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.

Title: Windows installer halts
Type: Stage:
Components: Windows Versions:
Status: closed Resolution: wont fix
Dependencies: Superseder:
Assigned To: theller Nosy List: morr, theller
Priority: normal Keywords:

Created on 2003-11-25 11:38 by morr, last changed 2022-04-11 14:56 by admin. This issue is now closed.

File name Uploaded Description Edit
SystemSpecs.txt morr, 2003-11-25 11:38 Selected test system specifications
Messages (7)
msg19124 - (view) Author: Jens Olsson (morr) Date: 2003-11-25 11:38
The Windows installer halts when starting to install files, 
more exactly when installing the file "UNWISE.EXE" and 
the progress bar reads "1%".

Python versions tested:

All tested versions behave the same. Since I don't believe 
it's a common bug I attach selected computer specs for 
the system in question. I find it hard to believe it is the 
python windows installer by itself that contains the bug 
but since I haven't experienced this with any other 
installer I submit the bug anyway. It can't be my system 
by itself either.

- Varying the installation options does not seem to help 
(non exhaustive testing done).
- Running install on on specific processor (Hyper 
Threading is enabled) does not change things

Test system summary (see attachment for full specs):
Gigabyte 8KNXP motherboard, intel Northwood 3.0GHz HT, 
2x512MB Corsair 3500, Radeon 9700 AIW, Seagate 
Barracuda 160GB, Windows XP Pro SP1a.

Reproduction steps:
1. Launch installer
2. Click 'next' when asked for directory
3. Click 'next' when asked about backups
4. Click 'next' when asked for component selection
5. Click 'next' when asked for start menu group selection
6. Click 'next' when prompted with the "ready to install" 
7. Observere bug
msg19125 - (view) Author: Thomas Heller (theller) * (Python committer) Date: 2003-12-03 20:58
Logged In: YES 

I've asked in the WISE support news group for help, I've
also seen similar behaviour in other software built with WISE.
msg19126 - (view) Author: Thomas Heller (theller) * (Python committer) Date: 2003-12-05 19:49
Logged In: YES 

Here is advice I got from a Wise rep:

This sounds like it is hanging at the point that the install
is trying to self register files. You can test this by
running the setup.exe with a /m1.  This will run the install
in manual mode, and prompt when each file is trying to self
register.  This will indicate which file it is trying to
self register, and then the error message.

Can you try this, please, and report the result?
msg19127 - (view) Author: Jens Olsson (morr) Date: 2003-12-10 11:38
Logged In: YES 

I couldn't update comments and didn't have time to figure out 
how I should do it so I hope this attached file will do.

Follow up:

I ran the installer with the suggested /m1 option. The install 
asked for the following directories (in order):


All input boxes had default values which seemed reasonable so 
I left them unchanged.

Then the actual installer window showed (as without /m1). 
After submitting the requested information (as reported in the 
inital bugreport) the installer halted when the small window 
titled "installing" showed, at 1% and the file unwise.exe... just 
as before. No question about registring files (besides the five 
windows promting for manual input of directories as described 

No error messages. Just the same behaviour as before with 
some additional directory prompting dialoges at the beginning.
msg19128 - (view) Author: Jens Olsson (morr) Date: 2004-02-24 09:29
Logged In: YES 

Any news on this one? Latest version behaves the same. Is 
there any alternative Windows install procedure that is 
reasonable easy to perform?
msg19129 - (view) Author: Thomas Heller (theller) * (Python committer) Date: 2004-02-25 19:14
Logged In: YES 

Nope, there isn't really progress.  I spend some time in the
wise support news group, but didn't really get a useful
answer.  I have to limit the time I spend on this.

IMO a better thing would be to bring the innosetup script in
CVS up to date with the current inno version - they are at
4.1.x currently, and add code for the missing features.  I
have the impression that innosetup is powerful enough to
handle all that is needed.

The only downside would that probably Python 2.3.4 will be
the only version using this installer, since 2.4 will be
released as MSI file.
msg19130 - (view) Author: Thomas Heller (theller) * (Python committer) Date: 2004-12-22 15:55
Logged In: YES 

No time to struggle with WISE.
Date User Action Args
2022-04-11 14:56:01adminsetgithub: 39598
2003-11-25 11:38:09morrcreate