Conference hydra::amiga_v1

4650.0. "Power Windows fix for chip memory" by SNOFS1::GERAGHTY (Simon, SPR CS IS) Tue Apr 02 1991 01:57

I've been using Power Windows v2.5b for some time now, and I recall someone
posting a comment last year (can't find it in this conference) saying that
it did not put the images in chip ram as required by intuition.

I figured a way of patching the program to do this, because I got sick of 
having to edit my generated source code so images were put in chip ram.

Using NewZap, find the second occurrence of the word USHORT in the program,
and change it to USCHIP. Then when you #include the generated source in your
program, always insert the following line above the #include statement:

#define USCHIP USHORT chip

It works a treat! Of cource, Lattice say you can use the -acdb option to LC to
allocate all structures to chip ram, but I couldn't get that to work properly.

regards,

Simon.

 _--_|\
/      \      SPR Customer Services Information Systems
\_.--._/  ,
      v  '

re            <<< Note 4650.0 by SNOFS1::GERAGHTY "Simon, SPR CS IS" >>>
>                     -< Power Windows fix for chip memory >-

	I'm having a basic problem with Power Windows 2.5c

	I think I've tried everything and I think I've looked 
everywhere, but it just  ISN'T  producing a header file.  Yes, I've 
clicked on all the boxes to generate code for everything, and I've 
clicked on the  HEADER  gadget to bring up the file requestor asking 
me where I want the header to go - and what I reply gets into the 
header gadget's string.  It just doesn't put a .h file down anywhere.

	Reg

    The file requester for header is an input file !
    Created header is  specified with the other requester ,output.
    This is mentioned in the manual at page 5.
    
    Regards,
    	Roberto.