Subj : Grunged message cap pointer help?
To : Paul Quinn
From : Mike Luther
Date : Tue Jul 24 2001 08:49 am
Thanks Paul ..
ML> of magnitude in the next message number upward!
PQ> [ ...trim... ]
ML> What did I do?
PQ> Have you started using a different editor? Like, I
PQ> had to change MsgEd's setting for the 'LastRead'
PQ> pointer file's _name_ default, in order to get it
PQ> working properly.
No different editor at all. I'm using the same one. No, there were no changes
made in it. I have two different Max systems on the same box in OS/2, but
their message base and the entire operation there are completely separated,
while running in native OS/2 in two different sessions on the same box.
The IE operation is a totally separate affair, using a completely different
partition arrangement operating in a DOS-VDM session on that same box with
totally different hardware.
Up until this thing started, nothing line this ever happened.
I really do not know the editor in use for that IM application. It came with
the HUB when I took it over by default and ported it to my OS/2 system. It ran
just fine for a year when WHAM!
PQ> Do have another program, or user, using the same
PQ> netmail area? Any recent changes or additions to your
PQ> system?
No other program uses the same netmail area. The other systems use totally
separate paritions even!
The BATCH file that runs this deal has not changed either!
This started when I added the LINUX echos. Two of them are reflectors from the
Internet side of life. Non-the-less, they are still SQUISH format message
bases. They use EXACTLY the same message base definitions in FASTECHO as does
everything else. Same editor, same everything. You can go through the FESETUP
game and can't tell any of this appart from any other echo of about 200 that
are carried on the HUB.
I've looked at the SQUISH.CFG file for clues toward where you are pointing me.
I can't find any.
I wish you would expand on something you said above! MSGED is what came to me
with the HUB. It is in use.
PQ> Like, I had to change MsgEd's setting for the 'LastRead'
PQ> pointer file's _name_ default, in order to get it
PQ> working properly.
I notice that in the MSGED.CFG file there are two references to 'lastread' in
it. The first calls for a lastread lastread, which implies to me that there
should be a file "lastread..something" in the MSGED directory. There is no
file that has been created there by that name.
This HUB system isn'y my original setup. In that SQUISH is used in various
places for different runs at things, there are the following SQUISH.CFG files,
which, I think I'm being told are the things that MSGED uses for its indexing
for caps!
These are in my OS/2 related efforts and I use AREAS.BBS for them:
About the 25th or June or so is sure about where this mess was created! I
notice that the MSGED and MAILER directory are frozen in time at 26-Mar.
MAILER\TMP is a slush directory implanted by the former sysop.
SQUISH.CFG in E:\IM has the new stuff in it as of 29-Jun-2001, as does the one
in E:\MAIL which has the real SQUISH in it! The others do not. Neither does
the file "SQUISH" in E:\MSGED which I assume is the "ASCI" listing of what the
export of FE did there:
SQUISH 24,934 14-02-96 18:10
Years ago before my time!
Thus, from your perspective, is the fact that this thing was laid out with all
this stuff scattered all over heck and back, resposible? Before I just go
copying again, you would advise that I simply conform all this to what is in
the E:\MAIL directory for the MAILER ??
As you can tell, in my setup, by gar if it's going to drive something the silly
file will be in "ONE" place if I have anything to do with it!
Thanks for your time!
--> Sleep well; OS/2's still awake! ;)
Mike @ 1:117/3001
--- Maximus/2 3.01
* Origin: Ziplog Public Port (1:117/3001)
