Albert,

I just got WAA myself and I'm having the same problem.  Alaska Support says 
the GIF is a generated file:

     a 'disclaimer' (Powered by Alaska Software WAA)

and the problem is that the package that spawns the file is not putting it 
with the HTML where the the web server can find it.  Problem is, I still 
don't know what to change in my configuration to tell the package to put the 
file where it needs to be.

Here is my most recent question to Alaska Tech Support, and the reply, and 
my follow-up question.  Read from the bottom to the top to get the thread in 
chronological order:

Hi Till:
Thank you for your explanation.  I think Im still missing something.  I 
thought the gateway provided the link between IIS and the Package, and that 
the Package would put the files where the gateway needed them for IIS.  It 
will come clear for me sooner or later, but if you could be patient and help 
me once more, Id appreciate it.  Let me provide additional information:

Here is my StartWAA.Bat, located in c:\alaska\waa1w32\server.  The only 
changes I made were to turn _LOG=ON and to change the port from 1024 to 
1020.  That was suggested by someone on the newsgroup, and seemed to solve a 
problem I had getting the WAA server to load in the first place.

REM File: STARTWAA.BAT

REM

REM Purpose: Setting environment variables for

REM          WAA1SRV.EXE

REM



SET WAA_WORKERTHREADS=5

SET WAA_HOST=localhost

SET WAA_PORT=1020

SET WAA_TRACE=OFF

SET WAA_DEVMODE=OFF

SET WAA_INTERNAL_LOG=ON

start %1 waa1srv.exe

Here is the waa1srv.cfg that was generated by the install program, located 
in the ..\server directory as well.  I did not change it at all:

#

# this is the package configuration file

# enter name and location package-DLLs

# file name must not include the extension

#

addpkg = ..\source\samples\waa\alaska1\alaska1

addpkg = ..\source\samples\waa\misc\myfirst

addpkg = ..\source\samples\waa\misc\htmldemo

addpkg = ..\source\samples\waa\misc\email

addpkg = ..\source\samples\waa\klondike\menu

addpkg = ..\source\samples\waa\klondike\klondike

addpkg = ..\source\samples\waa\frameset\frameset

My gateway is c:\inetpub\wwwroot\cgi-bin\waa1gate.isa

As a test, I changed the version number in myfirst.prg.  When I reloaded the 
WAA server and clicked on the Package info, it showed the new version 
number, so I know the WAA server is loading the correct packages.  If I 
comment out the call to oHTML:header() and oHTML:footer() in myfirst.prg and 
rebuild it the application works properly, so I know that IIS is running, 
the WAA server is running, the package is loaded, and the gateway is telling 
the IIS and WAA servers where each other is located.  The WAA server has the 
application (package) loaded.

Does this help you help me figure out why IIS doesnt find the file on disk? 
Can you suggest where I should put the packages and change the waa1srv.cfg 
to get the application to work properly?

Thanks in advance for your assistance.

 Steve 

-----Original Message-----
From: Alaska Technical Support [mailto:support@alaska-software.com]
Sent: Thursday, August 25, 2005 9:59 AM
To: steve@bestaero.com
Subject: Re: WAA--trying to get the demo to work...

Hi, Steve!

> When I try to run the demo applications that came with WAA I get the

> following error referring to a missing file.  I do not have a file named

> waapwr.gif anywhere on my computer.  Did I need to download some 
> additional

> files to get the demo to work?

They symptoms you describe indicate a problem in the configuration

of your web server. WAAPWR.GIF is a file that is included in the WAA's

binaries. In other words, the .GIF file is generated on-the-fly and made

available to web applications. Once you've got everything up-and-running,

you will find that file somewhere on your harddisk.

> And why would it be looking for it in ..\wwwroot anyway?  Shouldn't it

> be located in the ..\wwwroot\alaska1 folder with the application?

Actually, no. The .GIF file is normally put in WAA-generated web pages

as a 'disclaimer' (Powered by Alaska Software WAA). Because the image

is used within pages displayed by the client browser, it must be readily

accessible by the web server. Hence, the document root folder.

I'd suggest you re-check the configuration of your web server.

Generally speaking, all static content included in a web applictation must

be placed in folders that can be accessed by the web server.

This is a mechanism that has nothing to do with the WAA. Supposed

you created a web page using NOTEPAD and put an image on it,

your web server won't find it unless it's addressable through document

root. If you've got an index page, for example, put in document root

(or vice versa) etc. That's simplifying things a bit but may be used as a

rule of thumb.

Hope this helps,

  Till Warweg

  Alaska Technical Support



--------------------------------------------------------------------

Technical Support:      support@alaska-software.com

News Server:              news.alaska-software.com

Homepage:                 http://www.alaska-software.com

WebKnowledgeBase: http://www.alaska-software.com/kbase.shtm

European Office: Fax: +49 (0) 61 96 - 77 99 99 23

US Office: Fax: +1 (646) 218 1281

--------------------------------------------------------------------



----- Original Message ----- 

From: "Steve Woolstenhulme" <steve@bestaero.com>

To: <support@alaska-software.com>

Sent: Wednesday, August 24, 2005 2:53 PM

Subject: WAA--trying to get the demo to work...

> When I try to run the demo applications that came with WAA I get the

> following error referring to a missing file.  I do not have a file named

> waapwr.gif anywhere on my computer.  Did I need to download some 
> additional

> files to get the demo to work?

>

> And why would it be looking for it in ..\wwwroot anyway?  Shouldn't it be

> located in the ..\wwwroot\alaska1 folder with the application?

>

> . Steve Woolstenhulme .

>

> Content-type: text/html

> Server Error

> Cannot open file C:\inetpub\wwwroot\waapwr.gif : (0)No error

Steve Woolstenhulme wrote:

> Albert,
> 
> I just got WAA myself and I'm having the same problem.  Alaska Support says 
> the GIF is a generated file:
> 
>      a 'disclaimer' (Powered by Alaska Software WAA)

Just use your own HTML3 class and replace (overload) the :footer() method,
this way you get over all these problems (and get rid of the "powered by"
logo):

CLASS MyHtml3 FROM HTML3

   EXPORTED:
   METHOD Footer

ENDCLASS


/*
   Footer() replacement
*/
Method ShopHtml:Footer( cFooter )
   If cFooter # NIL
      ::Put( cFooter )
   EndIF

   ::Put( "</body></html>" )
RETURN NIL

You have to do the following two steps to use the changed class.

- Add the WAA_HTML3CLASS parameter when calling the package:

http://localhost/cgi-bin/waa1gate.exe?WAA_HTML3CLASS=MyHtml3&....

- Link WAA1USER.LIB to the package DLL.

HTH
Thomas Braun

Steve,
You may not use html3:footer method. Create your own myFooter function and 
call it in the source
FUNC myFooter(oHtml)
RETURN oHtml:Put("</body></html>")

i..e. this function is to close all required open html tags. Generate a 
form, open it source in the Internet Explorer and check tags. If you want a 
kind of perfect html code, you may use htmltidy to spell check it. At least 
I alway check when I create a new function.

Vladimir

"Thomas Braun" <nospam@software-braun.de> wrote in message 
news:1um9kz9cuau6r.1kk5v50k9tr90.dlg@40tude.net...
> Steve Woolstenhulme wrote:
>
>> Albert,
>>
>> I just got WAA myself and I'm having the same problem.  Alaska Support 
>> says
>> the GIF is a generated file:
>>
>>      a 'disclaimer' (Powered by Alaska Software WAA)
>
> Just use your own HTML3 class and replace (overload) the :footer() method,
> this way you get over all these problems (and get rid of the "powered by"
> logo):
>
> CLASS MyHtml3 FROM HTML3
>
>   EXPORTED:
>   METHOD Footer
>
> ENDCLASS
>
>
> /*
>   Footer() replacement
> */
> Method ShopHtml:Footer( cFooter )
>   If cFooter # NIL
>      ::Put( cFooter )
>   EndIF
>
>   ::Put( "</body></html>" )
> RETURN NIL
>
> You have to do the following two steps to use the changed class.
>
> - Add the WAA_HTML3CLASS parameter when calling the package:
>
> http://localhost/cgi-bin/waa1gate.exe?WAA_HTML3CLASS=MyHtml3&....
>
> - Link WAA1USER.LIB to the package DLL.
>
> HTH
> Thomas Braun