Any special install problems with Webinator?

Post Reply
User avatar
Thunderstone
Site Admin
Posts: 2504
Joined: Wed Jun 07, 2000 6:20 pm

Any special install problems with Webinator?

Post by Thunderstone »



I have WebSite, WebBase, and IMS email running on a NT 3.51 Server with
64MB memory. I currently use Excite 1.0 to index pages and would like to
switch over to Webinator.

Is there anything I should watch out for during installation? I don't want
to screw up what has been a reliable system.



User avatar
Thunderstone
Site Admin
Posts: 2504
Joined: Wed Jun 07, 2000 6:20 pm

Any special install problems with Webinator?

Post by Thunderstone »



James Corey said:

Installing Webinator should not affect anything in your current installation.
It simply installs somewhere in your HTML tree, and adds one program in your
cgi-bin directory. The only known issue with your setup it that it appears
WebSite mangles long file names, so you may need to rename webinator.exe.


User avatar
Thunderstone
Site Admin
Posts: 2504
Joined: Wed Jun 07, 2000 6:20 pm

Any special install problems with Webinator?

Post by Thunderstone »



This came over on the WebSite email list (by coincidence), and it seems to
relate to your comment about 8.3 file names on a WebSite server:

---------------quote----------
What sort of script are you trying to run? If it's 16-bit (eg. VB3) then you
are restricted to 8.3 file names.

I once tried something similar with a VB3 CGI and WS 1.1e, but I couldn't use
the default inline mapping of .wcgi as the 16-bit sub-system of NT can't use
long file names (or spaces!). Setting a mapping of .wgi to wwwserver/win-cgi
fixed it, and as soon as I moved to VB4 32-bit I could use the 4 letter
default mapping without any trouble.
------------end quote---------

Is Webinator 16-bit?

At 15:36 06/29/97 -0400, you wrote:


User avatar
Thunderstone
Site Admin
Posts: 2504
Joined: Wed Jun 07, 2000 6:20 pm

Any special install problems with Webinator?

Post by Thunderstone »



Webinator is a 32-bit program. It is also a regular CGI program, not a
WinCGI program. The long filename does work with other web servers such
as Netscape and MS-IIS, so it appears to be WebSite that is doing the
mangling.

James Corey said:


Post Reply