Re: DOS/NT install Was: Recommendations for learning Perl

[Frank Miedreich <miedreich@acm.org>]

******    message to minivend-users from Frank Miedreich <miedreich@acm.org>     ******

You are formatting your email with HTML. Please turn this off.
You are asking a question about installation on NT. This is not immediately
obvious from the subject of your message.

>
>
>Perhaps I am the sole dissenting opinion, but I've been trying to get this
>minivend package to work on my NT system for the last year to no avail. 
>It has been possibly the most wasteful and burdonesome trial I've ever
>experienced, and I am a programmer with experience in NT/Unix
>administration, Dos/Unix shell scripting, and lead a local Perl User group
>in MD. 
>
>

You have been trying to install minivend for one year without success? The
persistence of DOS users never fails to amaze me.

>
>
>It has a lot of potential, I just can't seem to get by the catalog setup
>part.  I've set up a special IP address under IIS4.0, and even started
>taking apart the actual Perl Code to see what may be stalling this
>process.  The worst part is that even after "Reading the Fricking Manual"
>for Minivend, I still feel as if this is basically an undocumented
>program.  At least from the NT point of view. 
>
>

I seem to remember that some cgi problems with IIS came from the necessity
to have nph in cgi output. At least CGI.pm requires (required?) the nph
option to work with IIS. There is info in the WHATSNEW file in your
distribution:

    * To improve page response time, you can specify a SEND=1
      attribute to any new-syntax MiniVend tag -- it sends the
      output that has accumulated to that point. If you have named
      your link program to begin with nph- (i.e. nph-simple instead
      of simple) the program will start sending output immediately.
      This can greatly improve apparent response time on large search
      or loop lists.

      The nph-executable can also be optionally used with an
      alias:

      Catalog simple /catalogs/simple /cgi-bin/simple /cgi-bin/nph-simple

      If you reduce your vlink buffer size to 512 bytes, this will
      improve likelihood of immediate response at some cost in CPU
      utilization. (This change requires editing vlink.c and compiling --
      don't worry about it if you don't know how to do that.)

Maybe this helps, good luck.

Frank

--
Frank Miedreich
Max-Planck-Institut fuer psychologische Forschung


-
To unsubscribe from the list, DO NOT REPLY to this message.  Instead, send
email with 'UNSUBSCRIBE minivend-users' in the body to Majordomo@minivend.com.
Archive of past messages: http://www.minivend.com/minivend/minivend-list