Another dumbass I have to deal with. Ini files
are client specific so I have no idea how to
edit his, you moron. This being the case it
would be stupid of me to attempt to give the
Rube this kind of advice.
His client should and probably does have a
way, independent of the .ini file to hand
configure a path preload which then writes
it to the .ini file, at least temporarily.
Not being familiar with his lame client,
this also I do not know. But, I can and
did advise the moron to use his client's
header editor to set up a path preload.
It's up to him to learn how to make sure
his client's .ini file retains it and/or
does not overwrite it.
His claiming the path preloading doesn't
work and implying it's got something to
do with
alt.net servers is stupid because
I showed him via MID how easily it can
be done and how very long path preloads
work just fine.
No please to be buggering off, ass face!