🚀 go-pugleaf

A couple of months ago, I posted a message regarding a problem I was
experiencing with the public domain WINDOWS package and asking if anyone had had
similar problems with it.  A while after that I posted regarding a problem
with memory allocation via malloc() after having run WordStar 2000.  It
started to make sense that WINDOWS would call malloc() to save the contents
of the screen prior to opening the window so that it could restore the
screen when the window was closed.  I contacted Lattice tech support who
basically told me they were aware of no problems with malloc() and it must 
be my code.

(As a quick aside, after my WordStar posting I was contacted by a person with 
MicroPro [authors of WS2000], who was quite courteous and interested in 
helping me.  I by no means intended my posting to be a statement about WS2000 
and apologize if I came across that way)

After yet another problem with malloc() I contacted Lattice Technical
Support today, and was informed that they are now aware of a problem with
malloc().  According to the tech person I spoke with, malloc() will return 
a valid pointer the first time it is called, but it is possible, on subsequent 
calls, for malloc() to return a valid pointer to an invalid memory block.  
A fix is in the works, but he could not say when it would be available.

I feel like my sanity has been restored.  I only wish it were so easy for my
company's reputation to be totally restored;  this problem caused quite a
bad image for us with a large California client.  I hope no one else out
there goes through what I went through.  (I'm doing my best not to get
bitchy here).

Does anyone out there have any idea of how difficult it is to port a fairly
sizable system (including assembler interfaces) from Lattice C to MicroSoft C?

Statically yours (for now anyway),


parris							...{ihnp4|akgua}!gatech!itcatl!parris

"What to do today, what to do today..."