#CRYSTL.ZIP
8 messages in this thread
Angelo, I can see from Jeff's logs that he downloaded the file, but I can't
find it on our system anywhere. Would you please up load it again?
Bob,
>> Would you please up load it again?<<
Sure
Ang
Bob,
Product Support propigated new forum software to all of CIS last night, and
sometimes when they do that, we lose files in preview.
BTW. They still haven't fixed the recurring bug in message scrolls to MAIL, so
I guess I outta scrub the boards for awhile.
Joe,
>> Product Support propigated new forum software to all of CIS last night,
Is this new CIS software? Have they fixed the SCA QUI NEW bug that causes the
wrong starting nember to be assigned as the first new message in a thread? (The
bug that KLUDGE deals with?) CIS stated they hoped it would be fixed in the
Latin 1 release of the software, but it wasn't. This bug still causes missing
messages when retrieving marked headers, and CIS sysops conveniently ignore
replying to my queries. Most people probably aren't aware of this bug; they
just wonder why they see replies to messages they never saw in the first place.
I can easily duplicate this problem, (it's only with ASCII protocol, not HMI),
but no one from CIS wants to hear about it or listen to me. You previously
mentioned to me that you were aware of this bug; is anything ever going to be
done about it?
John
>> This bug still causes missing messages when retrieving marked headers…
(it's only with ASCII protocol, not HMI)…
I've run into this using Wincim, but doesn't Wincim use HMI? I inquired
about this before in the Wincim support forum but only got the runaround, the
standard reply was "Try rebuilding the cabinet indexes, this will solve it.".
Not.
David
John,
That IS supposed to be one of the fixes in this release of the software.<g>.
Joe,
>> That IS supposed to be one of the fixes in this release of the software.<g>.
I'll let you know if it's still here in a week or two; I really dislike having
to use CIS' proprietary software to avoid this bug.
John
Oh, uh, that's right, Thanks, Joe, I'm sure it wasn't because WE lost it, it
musta been CompuServe's fault!
Didja hear that, Angelo? It wasn't my fault.