Re: PMPFax help needed

[crownmi@zot.io.org (Myles Fudge)]

To Andy Smith, Dave Miller, David Empson (so far)...

Re this (currently 3 message) thread on PMPFax:

In article <4t5tpn$smb@monet.ICSI.Net>, A Smith <ostman@roo.netrax.net> wrote:
>I can rececive a fax quite easily. When I go to send one, though, I get 
>an error message that states that it could not proceed due to either:
>1) PMPencode not exsisting
>or
>2) Not enough memory
>Well, PMPencode is in the correct folder, and I did try reinstalling. 
>Even after my system files, DA's, and stuff, I still have close to 3,000K 
>of memory available.

I have purchased both Faxination and PMPFax.  My preference is PMPFax -- 
it worked (and works) for me, no problems.  Period.  I have used it from 
both the NDA and the desktop application.  I prefer the latter.  PMPFax 
drives a LineLink 144e very nicely, and my 28.8 'Fast Mac V.34' well, too.

I have not had the 'PMPencode not existing' error yet.  I have had the 
'Not enough memory' error, which is why I have gone back to the desktop 
application.  After 1-2mb of goodies loading up during the boot process, 
there is often little room left for error-free faxing.  It seems that I 
have found the desktop application to be more stable over the NDA too.
In terms of errors, I have seen many, many of them in the course of 
sending and recieving the hundreds of outgoing and incoming faxes.  I 
have also located a couple bugs in the software that don't lead to 
serious errors.  I have found that the more minimal a system you setup in 
terms of inits, DAs, etc, the less a chance of errors from PMPFax.  Try 
shift-booting using the desktop applications, or creating a 
separate PMPFax enviroment with InitMaster.  When I get hit by the 
occasional nasty error, I shoot out the version I am currently 
using and re-install the program after which time it works again.

>Also, the phone number for PMP (510-837-9098) is disconnected. Anyone 
>have a current number?
> ostman@sun-link
>is really Andy Smith

I don't have a current number.  I would suggest trying email.  However, 
my several emails to Paul were never answered, hence the phone call...)
I last spoke to Paul a few months ago, before I presented PMPFax to my 
local Apple usergroup (LOGIC).  He indicated that there was one bug fix 
released that related to (I believe) class 2 faxing.  Because I wanted to 
have the most recent version of the software, he said he would send the 
new disk to me.  I didn't ever receive it.  (Paul, are you out there?)
He was beginning contract computer work for a company that would prevent him 
from even continuing to deal with his own software, so he said that he 
was handing PMPFax support over to someone else (unnamed).  I still don't 
know who that person is/was.  I got a strong feeling that he was no 
longer interested in working on the program, so I asked for the source 
code even to make my own personal bug fixes and enhancements (I think 
it's a great program!)  and, hell, even to study.  It wasn't offered.

My estimation is that PMPFax has reached the end of it's development.  It 
wasn't profitable enough to continue.  It was fun, and he learned a lot.
However it didn't generate enough revenue to live on.


-> dempson@actrix.gen.nz (David Empson) wrote:

>Doesn't look good.  Has anyone heard anything from PMP
>since this program was released?

>You too, huh?  My problem is different: I simply cannot
>send a fax with my modem (ZyXEL U-1496E), because PMPFax
>doesn't seem to be using the same definition of "class 2"
>as the modem (not surprising), and "class 2.0" simply
>doesn't work.

I recall Paul specifically mentioning ZyXEL modems in our conversation.  
Seek him out, or someone who has received that upgrade.

>I can't use "class 1", because the modem
>doesn't tell the computer that it supports this unless a
>certain S-register bit is set, and PMPFax is resetting the
>modem before asking.

The program allows you to send a custom AT string, however I cannot 
recall in sequence at which point - before or after it's resetting the 
modem

>The program worked OK (with class 1 only, despite the modem
>supporting class 2) with a Rockwell-based modem I brought
>home from work.

I have used the program to fax with a new 28.8 class 2 modem out to a 
class 1 fax machine and a new class 2 fax machine.  No problems.  In 
fact, quite impressive results.  I now have one very decent printer for 
outputting 320x200x16 b&w scans from my digitizer card (insted of the 
ImageWriter II).  Of course it makes for useful b&w scanning - I can now 
drag & drop my scanned signature on faxed AWGS documents.

>I E-Mailed PMP about this, but never got a reply.

Yes, I had the save negative experience with his email.  Message after 
message, he did not get back to me.  I guess I was lucky to phone soon 
enough that I beat the disconnect.

>My current opinion of PMPFax is: nice concept, shame it
>doesn't work. Faxination may be braindead, but it works.

Unfortunately it doesn't work in your case (and so, perhaps many others 
too).  I have strongly recommended it to several people, with the fair 
warning that your really must have a fast accelerator to survive the 
lengthy encoding/decoding process (especially if you are faxing landscape 
AWGS documents).  One very nice note: I recently discovered that ShowMe 
does a remarkable job of making the decoded fax instantly (!) available 
for viewing (by viewing it in the original ~2000x2000 size) whereas the 
program scales the document down to more reasonbly suit the 320x200 
screen.  It would have been much more useful to include a 640x200 mode 
fast viewer.

>Insufficient hard drive space?  A setup step missed?  INIT
>conflict? Directory structure of hard drive damaged?
>Check that your outgoing fax folder is set correctly.
>I've never tried receiving, but sending worked OK (with the
>right modem).

Conveniently locate your FaxIn and FaxOut folders (or whatever you want 
to customize them to) on a partition with several megs of space free.  
Don't be suprised to receive 1-2 meg faxes when ^all^ is said and done 
(receiving, decoding, logging, etc) although less than 1mb is the norm.
Really watch the goodies that gobble up your RAM during and after the 
boot process (Inits, etc).
 
-- 
Myles Fudge  (crownmi@io.org)
http://www.io.org/~crownmi/pleasure.html