Just reading through this thread I can see opportunities for things to go wrong, perhaps people can't really see what problems you are having because they don't have the luxury of your grand design on readily available demand (your mind; the blue print)
I think once you start screwing around with the makeup of installations and the structures of directories and alike you're generally on your own, since you shouldn't be doing things like this unless you KNOW what you are doing, I used to do all sorts of whacky stuff myself but I never posted anywhere for assistance since I always knew what I was doing... I know that probably doesn't help but it's important to have a real good idea before doing anything "adventureous" otherwise you'll fall prey to frustration and might even end up typing responses in capital letters, good grief
Why not start again and carefully evaluate everything that you do and try and see why things aren't working the way they are meant too. Afterall as far as I can tell you're just asking the crowd if they can see something you can't, but since you are correcting them for there own apparent blindness then perhaps you are the only one who can help you
I would if it would make a difference (I did the blank slate install twice already with the same two problems... customizations happened ***after*** the blank-slate installation to the hand-installation partition only... once python and TimberWolf had already both failed to work.
I7m not asking for what they can see that I can't I'm reporting the fact that python was broken *at*time*of*original*installation* and remained that way...
TimberWolf seems to be the only other program affected adversely and I don't know as to "why" that remains broken when everything is there.
For some reason *something* is missing and has anyone else run into those two programs not working for them? or has it only been me reporting those two as failing to run when everything else does? (ignoring my customized install entirely as it is an irrelevance for this discussion, it only came up since I mentioned it as part of my original posting however *all* the customization happened after python had already had the blank-slate installation completed.
I installed AmigaOS 4.x to the "Reservation" partition... booted from the Reservation partition and then proceeded to watch the python scripting and anything python related utterly and totally fail to run.
so where people seem to get tripped up is that I have mentioned customizing things... however *when* I customized my system was already AFTER the point where python had already failed.
TimberWolf was tested with and without the customizations and they are irrelevant (same results both times)
the one and only change I have set for both the "basic only" install on the Reservation and the "Customized hand-install" on the "Belxjander" partitions that they have in common is the Grim Reaper having a single location (Work:Development/CrashLogs/" being set for where to save crash logging...
regardless of "fresh from CD" booted and ready or "custom hand-installed" the results were basically the same...
Python and TimberWolf are the only two programs that I can report problems with.
Otherwise I have had *nothing* of note to report at all and everything else works fine (upto and including the older program errors that happen as they are expected somewhat due to the age of the code and being 68K material on a PPC system)