\n should work fine for new line and having the sambar perl should not make a difference. The hash line on your script needs to point to perl so if perl is C:\perl\perl\perl.exe the hash line would be #!C:/perl/bin/perl.exe or #!C:/perl/bin/perlis.dll
I'm not at all sure why you would install sambar here C:\temp\Sambar60-1\ More traditionally it would be C:\sambar\ or at least it makes it easier in the long haul to set paths. Php is just as much fun to work with. Have you tested your script in a dos box? cd\path to script\ script name > errors.txt Peter -----Original Message----- From: [EMAIL PROTECTED] (cherie) To: "sambar List Member" <[EMAIL PROTECTED]> Date: 23 Jun 2004 06:00:19 +0200 Subject: [sambar] Perl is finally working (somewhat)! > Peter: I apologize for attributing a different suggestion to > you,[quote:9644608264="Peter"]I did not tell you to lose the -wT I > gave you detailed instructions on how to setup perl on sambar. If you > followed those instructions you would be using the activestate build. > Once its running delete the perl in sambar. > > The hash line should look like this #!D:/perl/bin/perl.exe or > #!D:/perl/bin/perlis.dll dending what perl you are using and what > drive it > is located on. > > ________________________________________________________________ > I have not been able to get perl scripts to operate properly. My > config.ini is in C:\temp\Sambar60-1\config\ : > > line # 176 says: > Perl Executable = > > lines 183-187 are for the Extensions: > #ISAPI Extensions = *.dll > ISAPI Extensions = > CGI Extensions = > #CGI Extensions = *.pl *.cgi > WinCGI Extensions = > > > I installed Activestate perl into C:\Perl\ > There is a perl .exe in C:\Perl\bin\ and there is a perl5.8.3.exe > there too. > > I restarted Sambar, and I used in IE their script called environ.pl > which ran fine from http://localhost/cgi-bin/environ.pl to deliver > the environment variables, but \n does not work nor does \t. Their > original script conained the line /usr/bin/perl so I changed it per > your suggestion to C:\Perl\bin\perl.exe but the newline doesn't > work. I also tried C\Perl\bin\perl5.8.3.exe with the same result. I > am stumped. I have not deleted perl from Sambar, and maybe it is > somehow finding it despite my first line. If I eliminate the > 'shbang' line altogether I get the same thing as I do when it's > there! There must be a book I can read to get the reasons for things > like why it's necessary to modify the config.ini file, and why the > pl files MUST be in the cgi-bin directory (ie you can't move the > script to http:/127.0.0.1/environ.pl and get it to run). All the > Perl books I have talk about hashes etc. and they are understandable > but no help with this setup problem. Maybe PHP would be easier? > Thank you everyone. > > Cherie > > > > -----Original Message----- > From: [EMAIL PROTECTED] (cherie) > To: "sambar List Member" <[EMAIL PROTECTED]> > Date: 19 Jun 2004 16:25:42 +0200 > Subject: [sambar] Perl is finally working (somewhat)! > > > Thanks for the help, everyone. > > Leif Gregory's advice was true that the notepad was a source of > > problems; even though I enclosed the filename in quotes and made > sure > > the extension was l.pl, I was getting an 'internal error'. > Switching > > to PSPad eliminated that source of error. Also, Peter's suggestion > > to lose the -wT switches on line #1 worked to finally give a > working > > script! I read in a book that these switches helped debug but not > in > > this case. I wish I knew what was the location of the perl > > interpreter I am using. This is a Windows computer so there's no > > /usr/bin/ directory. The \n and \t control characters do not work, > > but I sent a copy of the script to my friend who has a UNIX > computer > > and they do work on her computer. Here's my script right now: > > > > #!/usr/bin/perl/perl.exe > > print "<P> -wT doesn't work > > P> neither does backslash n for newline or backslash t for > > tab!"; > > print "<P>why doesn't newline or tab work?\tI wonder why.\n > > It's a huge mystery"; > > print "<p>Hello,World!\n Hello,World!<br>Hello,World!"; > > > > It doesn't even care if the first line is there or not, it's > probably > > finding an interpreter to use in the windows path. > > It would be great if I knew what those codes were in the log file > when > > the scripts crash. That information is not available to newbies, > > right? > > Thanks to everyone for the advice. > > Cherie > > > > ------------------------------------------------------- > > To unsubscribe please go to http://www.sambar.ch/list/ > > > > > > > ------------------------------------------------------- > To unsubscribe please go to > http://www.sambar.ch/list/[/quote:9644608264] > > ------------------------------------------------------- > To unsubscribe please go to http://www.sambar.ch/list/ > > ------------------------------------------------------- To unsubscribe please go to http://www.sambar.ch/list/
