Thanks Khen1950fx,

I actually got it to work using the code below. I changed auto:0 to auto:1 and that did it.

require "subparseform.lib";
&Parse_Form;

print "Set-cookie: cart_id=1234; user_id=123;\n";   
print "Content-type: text/html\n\n";

use strict;
use CGI;

use Device::ParallelPort; 
# use Device::ParallelPort::drv::linux
# Set up your parallel port object and tell it what driver to use.
my $parport = Device::ParallelPort->new('auto:1');

# $parport->set_bit(0,1);
# $parport->set_bit(1, 1);
$parport->set_bit(2, 1);
$parport->set_bit(3, 1);
$parport->set_bit(4, 1);
$parport->set_bit(5, 1);
$parport->set_bit(6, 1);
$parport->set_bit(7, 1);

[download]

If I don't comment out the CGI lines I get an Internal Server Error, that's why I have them. Is there a serious problem with doing it this way?

In reply to Re^2: Accessing parallel ports by tumoheat
in thread Accessing parallel ports by tumoheat

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.