TIP: Click on subject to list as thread! ANSI
echo: muffin
to: All
from: Mvan Le
date: 2007-04-09 15:09:28
subject: Maximus Squish bug

Maximus Squish bug
------------------

I'm running Maximus 3.01 (DOS) and Squish386 under NT 4.0.

Has anybody noticed that Squish won't scan out messages changed with the
Msg_Change command unless the Msg_Area command is executed first ?

For example, if you try modifying an existing message: 

  The MESSAGE Section
  There are 1 messages in this area.  The highest is #1
  NO NEW messages have been posted.

  (1 / 1)  Msg.area fdo.OZ_HUMOUR ... Tell a joke
           Press  for the NEXT message.

  MESSAGE Menu (8422 mins left):
  \List all areas     Area change         [Previous area      ]Next area
  Previous message    Next message        Enter message       Reply to a message
  Browse messages     Your mail           Change current msg  =ReadNonStop
  ...
  ...
  ...
  Select: c

  This message has already been packed as netmail, scanned to another
  system as an echomail message, or read by the addressee.

  Press ENTER to continue

  Edit message anyway (y,N)? y

  ...
  ...
  ...

  Saving your message (#1).


  (1 / 1)  Msg.area fdo.OZ_HUMOUR ... Tell a joke
           Press  for the NEXT message.

It will scan properly ("...\Sq386.exe OUT SQUASH link") the first time: 

  + 10 Apr 08:35:28 SQSH Begin, Squish v1.11 (mem=375K - main=0708:0a87)
  # 10 Apr 08:35:28 SQSH Scanning messages
  : 10 Apr 08:35:28 SQSH    OZ_HUMOUR      (Toss=0000  Sent=0001)
  ...
  ...
  ...
    10 Apr 08:35:28 SQSH ZIPing mail for 3:712/0 (313 bytes)
  # 10 Apr 08:35:28 SQSH Linking messages
  + 10 Apr 08:35:28 SQSH End.  Toss=0 (0/s), sent=1 (1/s), mem=368K

But if you then try to change it a second time it won't scan: 

  + 10 Apr 08:35:38 SQSH Begin, Squish v1.11 (mem=375K - main=0708:0a87)
  # 10 Apr 08:35:38 SQSH Scanning messages
  ...
  ...
  ...
  + 10 Apr 08:35:38 SQSH End.  Toss=0 (0/s), sent=0 (0/s), mem=207K

Until you change it a 3rd time:

  + 10 Apr 08:36:21 SQSH Begin, Squish v1.11 (mem=375K - main=0708:0a87)
  # 10 Apr 08:36:21 SQSH Scanning messages
  : 10 Apr 08:36:21 SQSH    OZ_HUMOUR      (Toss=0000  Sent=0001)
  ...
  ...
  ...
    10 Apr 08:36:21 SQSH ZIPing mail for 3:712/0 (313 bytes)
  # 10 Apr 08:36:21 SQSH Linking messages
  + 10 Apr 08:36:21 SQSH End.  Toss=0 (0/s), sent=1 (1/s), mem=368K

I get the feeling the current Squish message area (or .sqb, .sqd, .sqi and
.sql files) is being locked and a "scan me" bit isn't being set
on the latest modified message.

It will never scan the last message changed even if you log off.

To get it to scan you must either

  1. run Msg_Area BEFORE changing any message in the current area or, 

  2. switch to the current area from a different area first

Either way Msg_Area must be invoked.

Btw you only need to invoke Msg_Area command - selecting a different area
is inconsequential to these tests.

Maybe there're no problems under MSDOS or OS/2 ... .

--- Maximus/2 3.01
* Origin: Top Hat 2 BBS (1:343/41)
SEEN-BY: 3/0 633/267 640/954 712/0 313 550 620 848
@PATH: 343/41 138/146 392 123/500 261/38 712/848 633/267

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.