RE: Logon

[cld@xxxxxxxx (Carl Distefano)]

You don't need "log.log". (Never heard of it, don't
where it comes from -- is it in the default
installation?) If you log on as "jim", all you need is
"jim.log".

It just occurred to me that the idea behind making the
LOGON command RUN the .LOG files like XPL programs must
have been that these .LOG files were supposed to be
vehicles for loading different configurations
for different users. In other words, instead of (or in
addition to) putting the usual LOAD commands in
STARTUP.INT, customized sets of these commands for
different individuals could be collected in .LOG files,
so that when a particular user logs on, his or her
customized settings are loaded. I never heard of the
LOGON command actually being used that way, but it
certainly would be a viable and convenient use for it,
even in a non-network setting. E.g., LOGON HIS and LOGON
HERS commands for households where more than one person
uses Xy. It would also be a way for individual users to
switch between different configurations, e.g. LOGON HTML
and LOGON NORMAL. You get the idea.

As for Rene's suggestion of just ignorning LOGON, it's
never worked for me either. I wonder, therefore, why it
works for him. Rene: when you command VA/NV NL, what
directory is specified? Is there a .LOG file in that
directory?

--
Carl Distefano
cld@xxxxxxxx
http://users.datarealm.com/xywwweb/
> Carl and Rene: Thanks for your comments on my out-of-office logon problem.
> Rene: I tried removing the BX login jimQ2 ;*; line from startup.int, but
> that didn't work. The program continued to freeze. Carl: I think you're
> telling me that I need to have two log files on the same drive. On my
> computer at the office, I have jim.log, which has FF in the file, and
> log.log, which has BC in the file.
>
> I'm still curious if anyone has a clue why this problem cropped up after
> about 10 years of no problems putting XyWrite 4 on other computers.
>
> Jim Eberle
> jeberle@xxxxxxxx
>