while(my $line = <$info>)  {
    foreach ($line) {
        chop;
        @vlinks = split(/:/,$_) ;
        print "<tr><td><a href=\"bookDETAIL.cgi?book=$vlinks[1]\">$vli
+nks[0]</a></td><td>$vlinks[2]</td><td>$vlinks[3]</
+a></td></tr>"
    }    
}
[download]

Some notes on that piece of code:

• chop is not what you want. chop chops off any character found at the end of the string. Use chomp, that only removes trailing newlines. If your input file does not end with a newline, chop damages data. chomp does not.
• foreach ($line) is quite useless, you are not iterating over an array here. But it makes $_ an alias for $line. You use $_ only as explicit argument to split. Better remove foreach and write the split simply as @vlinks = split /:/,$line;.
• You could entirely avoid $line, because while (<$handle>) already implicitly assigns to $_ and checks for end of file. In that case, split can also be reduced to a single argument, as it operates on $_ by default. So:

  while (<$info>) {
      @vlinks=split /:/;
      # ...
  }
  [download]

• You use @vlinks only inside the while loop, so you should limit its scope to that loop: while (<$info>) { my @vlinks=split /:/;
• And, as many other monks told you: Don't try to handle CSV files manually, use Text::CSV and its fast companion, Text::CSV_XS. CSV may look like a cute and harmless file format, but it's like a gremlin waiting for being feed in a shower after midnight. CSV lacks a proper, agreed specification, and so everybody has invented variants for quoting, escaping, empty fields, NULL, binary data, line endings and tons of other nasty details over the last decades. Tux++ has put a lot of effort into the Text::CSV family of modules (including DBD::CSV) to handle all of that ugly stuff for you.

Alexander