I have recently been seeing random messages complaining that PythonUser
isn't present on my machine. Some time ago I investigated Python but
gave up and removed all references (apparently not). The most recent of
these messages came when I tried to save my choices for the new
MiniTime app.
"MiniTime Filing system or path PythonUser: not present (code 1410)"
Clearly this all stems from operator error here and I'd be very
grateful if someone could suggest where the problem might be other than between my ears.
In article <5b662288f5brian.jordan9@btinternet.com>,
Brian Jordan <brian.jordan9@btinternet.com> wrote:
I have recently been seeing random messages complaining that PythonUser
isn't present on my machine. Some time ago I investigated Python but
gave up and removed all references (apparently not). The most recent of
these messages came when I tried to save my choices for the new
MiniTime app.
"MiniTime Filing system or path PythonUser: not present (code 1410)"
Clearly this all stems from operator error here and I'd be very
grateful if someone could suggest where the problem might be other than
between my ears.
The plot thickens...
A short while ago I typed *shoe rather than *show into the command line
with this result
*shoe
Filing system or path PythonUser: not present
In message <5b6715b218brian.jordan9@btinternet.com>
Brian Jordan <brian.jordan9@btinternet.com> wrote:
In article <5b662288f5brian.jordan9@btinternet.com>,
Brian Jordan <brian.jordan9@btinternet.com> wrote:
I have recently been seeing random messages complaining that
PythonUser isn't present on my machine. Some time ago I
investigated Python but gave up and removed all references
(apparently not). The most recent of these messages came when I
tried to save my choices for the new MiniTime app.
"MiniTime Filing system or path PythonUser: not present (code
1410)"
Clearly this all stems from operator error here and I'd be very
grateful if someone could suggest where the problem might be
other than between my ears.
The plot thickens...
A short while ago I typed *shoe rather than *show into the
command line with this result
*shoe
Filing system or path PythonUser: not present
If you are not using Python and don't want it.
do a *show python*
This will show all the paths to where the various bits of Python are > located. My !Pythonuser is located at:
HardDisc4.$.!BOOT.Choices.Boot.PreDesk.!PythonUser
In article <5b662288f5brian.jordan9@btinternet.com>,
Brian Jordan <brian.jordan9@btinternet.com> wrote:
Some time ago I investigated Python but gave up and removed all
references (apparently not). The most recent of these messages came when
I tried to save my choices for the new MiniTime app.
"MiniTime Filing system or path PythonUser: not present (code 1410)"
A short while ago I typed *shoe rather than *show into the command line
with this result
*shoe Filing system or path PythonUser: not present
On 26 May, Brian Jordan wrote in message
<5b6715b218brian.jordan9@btinternet.com>:
In article <5b662288f5brian.jordan9@btinternet.com>,
Brian Jordan <brian.jordan9@btinternet.com> wrote:
Some time ago I investigated Python but gave up and removed all references (apparently not). The most recent of these messages
came when I tried to save my choices for the new MiniTime app.
"MiniTime Filing system or path PythonUser: not present (code
1410)"
A short while ago I typed *shoe rather than *show into the
command line with this result
*shoe Filing system or path PythonUser: not present
The most likely explanation is that something which you installed
for Python and then didn't uninstall is adding to Run$Path using
the unset PythonUser$Path variable (ie. the variable behind
PythonUser: as a filename prefix). Using
*Show Run$Path
should reveal this. If that doesn't reveal anything, then the
problem as reported with MiniTime would make me investigate
*Show Choices$Path
*Show Choices$Write
as well.
Once you know what is being added to which variable, you can then
start to search for where it is being added.
In article <5b662288f5brian.jordan9@btinternet.com>,
Brian Jordan <brian.jordan9@btinternet.com> wrote:
The plot thickens...
A short while ago I typed *shoe rather than *show into the command line
with this result
*shoe
Filing system or path PythonUser: not present
Is MiniTime trying to use a * command that is absent from my machine?
And what has PythonUser got to do with it anyway?
In message <5b6715b218brian.jordan9@btinternet.com> Brian Jordan
<brian.jordan9@btinternet.com> wrote:
In article <5b662288f5brian.jordan9@btinternet.com>, Brian Jordan
<brian.jordan9@btinternet.com> wrote:
I have recently been seeing random messages complaining that
PythonUser isn't present on my machine. Some time ago I investigated
Python but gave up and removed all references (apparently not). The
most recent of these messages came when I tried to save my choices
for the new MiniTime app.
"MiniTime Filing system or path PythonUser: not present (code 1410)"
Clearly this all stems from operator error here and I'd be very
grateful if someone could suggest where the problem might be other
than between my ears.
The plot thickens...
A short while ago I typed *shoe rather than *show into the command
line with this result
*shoe Filing system or path PythonUser: not present
If you are not using Python and don't want it.
do a *show python*
This will show all the paths to where the various bits of Python are
located. My !Pythonuser is located at:
HardDisc4.$.!BOOT.Choices.Boot.PreDesk.!PythonUser
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 63 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 492958:53:09 |
| Calls: | 840 |
| Files: | 1,300 |
| D/L today: |
2 files (14,540K bytes) |
| Messages: | 262,046 |