Hi Rob Thanks a lot .
You & the "remote partner " seems to be the two extremes . A really impressive mail with lot of positive attitude . Can you tell something more about LWP use for my solution i.e. how to transer a doc/html file automatically on daily basis from my windows machine to a unix machine . Rob I am easliy able to make the page as html that is not the issue - probably i need some html converter to keep up the formatting else I don't think even perl's rename command could be helpfull in keeping up the formatting . I couldn't very well understand the answer to 3rd one . Do you mean that WMI & pstools both r not perlish way ? ( not clear ) . I think WMI should be a pure perlish way ( we naturally need to use files supplied with OS & WMI is also the one) . There I still many parts of your mail which I am going through like Net::FTP also to check out an automated ftp ,will ask you or list with next set of problems :)) . Thanks & Regards Pradeep "Rob Dixon" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Pradeep Goel wrote: > > Hi All ,pls answer if u know anything out of 3 different questions. > > Hello Pradeep. Welcome to perl.beginners. A lot of us here know a lot > about Perl, and between us we can help you with almost any Perl problem > that a Perl beginner might come across. > > > 1) > > Can somebody give some pointers where to look for or any particularly > > good one ( free of course ) automated ftp tool which can be used for > > transfering a txt/doc file from my win XP system to a unix server ?. > > In Perl you would want to use Net::FTP, or take a look at LWP, which > will let you handle several common Internet protocols. But I know of no > ready-written Perl application ( free, of course ) that will do the job. > One approach might be the Perl 'system' function, which will allow > you to write something like > > system 'ftp' > > but that requires that all of the necessary information can be included > in the command line. You might check the XP help files to see if this is > possible. A full solution would need to send commands to the ftp utility > and receive results back from it. This would need the IPC::Open2 > module, which is essentially an enhancement of standard pipe > operation that allows bidirectional communication. If you add a > layer on top of this which reads and writes STDIN and STDOUT, > then you could pass commands from the keyboard to the utility and > display the corresponding output, just as if you were controlling it > directly. > > > 2) > > Also if somebody what I can do to make a page html instead of txt or > > doc - keeping up the format ( need not be exact format but it should > > not just be a messed up one). > > when i rename from .doc to .html or use copy command ( i.e. on > > windows machine) the format goes off completely - & what left is > > contiguous words that's all ?. > > It sounds here as if you want to convert a MS Word file to HTML? > Your idea of renaming files is a good one, but even this can get a > little complicated at times, with file protection and ownership > to take account of, as well as unprintable characters embedded > in filenames. Perl could help you here. It has a function 'rename' > which will change the name of a file for you. The syntax is > > rename OLDNAME,NEWNAME > > but beware, as if you already have a file called NEWNAME, it will > be overwritten. You could check out the help files on your copy of > Word, but I'm afraid that, to my knowledge, there are no Perl > modules which will parse a Windows Help file. You may however > be interested in the Pod2WinHlp module, which will translate > Perl's 'Plain Old Documentation' to a Windows Help. Should you > need to write your own Perl translation module then we will > help you all we can. > > > 3) > > last question could there be any problem ( like ease of modification > > or flexibility related ) if i am using pstools to get remote > > information from win systems instead of WMI scripts. > > The scripts thus reduced to a total of hardly 4-5 lines instead of > > longer 2-3 page scripts in WMI. Is there any adv of using WMI in > > place of pstools ?. > > There's the rub, you see: there could be any number of problems I'm > afraid. It really depends on what information you're getting, the > method you have used to connect to the remote system, any security > systems that protect the remote data, and how you want to process > the information once it is retrieved. No interface exists to my > knowledge which provides a straightforward Perl interface to > either Windows Management Instrumentation or pstools, but it can > certainly help with the processing of the data once it has arrived. > Being a 'Practical Extraction and Reporting Language' it is ideally > suited to this sort of application, and I would direct you to the > 'perlform' part of the documentation, which will help you neatly > arrange reports on the accumulated data. If you have access to the > administrator of the remote system, I also suggest that you evangelise > the Perl approach. If you can get someone else to format the > data as you would wish before you even retrieve it, then it > can only be an advantage to you. Once your remote partner > has seen the possibilities that Perl offers I'm sure he would be > only too willing to cooperate. > > Please come back to us if you have any further questions about the > Perl approach to problem solving. We will be only too willing to assist. > > > Rob :-> > > > > > -- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
