When installing 2.3b2 I was allowed to choose a non-system 
disk. It did create an Applications folder and installed into it. 
Parts of the framework were installed correctly (based 
onmod dates) but it did not work properly.

After installing on the system disk the IDE worked fine but 
the package manager did not except from within the IDE. I 
suspect double clicking on the Package Manager was trying 
to use an older version of python, possibly Apple's.

Logged In: YES 
user_id=45365

For some reason setting rootDiskOnly causes strange error 
messages to appear in the installer, and you have to switch disks 
back and forth to make installation possible. And people with only 
one disk don't even have this option.

The problem is probably that the packages created by our 
buildpkg.py module aren't fully adhering to the (unwritten) 
standard. For now the workaround is to allow non-system-disk 
installs, but warn people in the welcome message that this doesn't 
work. For the future we should either fix buildpkg or replace it 
with a module that uses OSA to talk to the Apple Package Maker 
tool.

Logged In: YES 
user_id=580910

The Python2.5 installer won't allow installation to non-system disks and that 
seems to work fine. The same is true of the universal installer for 2.4.3.

Installing on other disks won't work because the framework and the python and 
pythonw executables contain hardcoded paths.