Subj : Weird problems with Squish
To : Sean Dennis
From : Peter Knapper
Date : Mon Dec 27 2004 09:18 pm
Hi Sean,
Well I can't really comment too much other than what you probaby already
know...
SD> + 27 Dec 00:20:38 SQSH Begin, Squish/386 v1.11
BTW, WHICH executable are you using SQ386 or Squish/2? BOTH list as /386 in the
log and that can makes things confusing.
SD> + 27 Dec 00:20:38 SQSH Begin, Squish/386 v1.11 (mem=-
This says that Squish is running out of memory... in a big way (a negative
quantity???). Something else on your system is doing this, so its probably not
a Squish issue. One thing with Squish/386, I found that using "Buffers Medium"
resulted in errors, so I have only been using Squish/2 and "Buffers Large"
since very early on in Squish 1.11 days. This was even a Scott Dudley
recommendation, given the known issues with the /386 specific environment...
SD> ! 27 Dec 00:21:05 SQSH Archiver error: Can't run archiver (-1)
Its unable to get the memory it needs to run, so it confirms the above
situation)...
SD> -If I do this using GoldEd+/EMX at the command prompt
SD> (using a batch file), this error occurs.
Are you using the EMX handles bug fix? Namely the line in config.sys -
SET EMXOPT=-h256 -!0x800
EMX is not perfect, it does have issues at times, I have moved away from using
EMX wherever possible because of these memory usage issues I keep seeing.
The worst one was BinkD/2, the EMX version would run for between 22 - 72 hours
before refusing to run BinkD again until a reboot. I now use the non-EMX
version of BinkD/2 and it runs for months at a time...
SD> I am wondering if there's a problem with OS/2 running
SD> out of handles)
Its more like EMX consuming the handles and not releasing them to me.
I hope this helps................pk.
--- Maximus/2 3.01
* Origin: Another Good Point About OS/2 (3:772/1.10)
