forum.vdsworld.com

[tim6389]

i have just learned the dos can not stdout out right

what i mean is if i try this

tail -f cardout.dat <----- this works outputs it to the screen BUT

if i do this

tail -f cardout.dat | perl4 parse.pl /4 /olog.txf <---this won't work cuase dos can't pipe it out right ( when using the -f command whick i need)


any vds code that i can uses so i can fix this problem


thanks

[Mac]

For DOS output to a file, use:

> (overwrites/creates the destination file)

>> (appends to the destination file)

Example:
dir/s > test.dat

dir/s >> test.dat

Cheers, Mac

[tim6389]

but i need the tail -f so that it will watch the file as it grows, and it will feed the data TO the perl script if i just have it save to a file then the perl script will stop runing when it get to the end of the file this is what tail -f does it let's the data to be feed to the perl script " like a live feed"

hard to explain BUT does don't have a stdout like linux does.

[Mac]

I'm not familiar with the program and don't understand exactly
what you want to do. However, if the DOS command:

tail -f cardout.dat

prints the correct results to screen, the following will print the
same results to output.txt (or any file name you choose):

tail -f cardout.dat > output.txt

If you need to continously add info to the file, you can use a
loop with ">>" like this:

tail -f cardout.dat >> output.txt

NOTE: In DOS, if you use a filename or command with spaces,
it may need to be enclosed in quotes.

If this still is not what you need, maybe you can try to explain
step by step (in more detail) what your program does, and what
you're trying to do. We'll need to know that before we can
come up with a solution in either DOS or VDS...

Cheers, Mac

[tim6389]

ok i know you are talking to say BUT the file option won't work also ( i tried it) what i need is a vds program that will do this:


take the output from tail -f and feed that output to the perl script,


the reason the >> won't work cause dos pipe command is lacking the Ability to DO a live feed and feed it to the perl script. the program that i run gathers data then i used the perl script to convert that data to english, well english for me that is. this must be done DURing live feed other wise the data would be repeated...that is why i uses tail -f it watchs the file as it grows, thus making it not repeat the info

hard to explain...


i hope i explain it better

[Tommy]

How about launching the Perl script directly and modifying the Perl script to directly read
the data from an output file created by "tail" and to directly write the final output file?

[tim6389]

that might work, but i have alot of option that are in the perl script which can make it hard to run the Perl script directly. some of the option are:


#Useage:
#
# <logfile> \0 only new cmd82's and C9's data display
# <logfile> \1 all cmd82's and C9's data display
# <logfile> \2 all cmd82's and C9's packet and data display
# <logfile> \3 all parsed packets display
# <logfile> \4 all cmd82's and c9's in all INS40
# <logfile> \5 all cmd82's and c9's fully disassembled


also reading the ouput directly can cause problems like :

one when the program is waiting to get data before it can write in this case the perl script would stop.. beacuse it would think its at the end of the file this is why tail -f comes to play

[iMPA]

what about a DOS batch file, first run the tail program and then the perl script...

[tim6389]

iMPA

i try that BUT this:

[SnarlingSheep]

I don't really know what "tail" does..or anything about perl for that matter but, you might try something along the lines of repeatedly running tail -f cardout.dat with the perl script open.

[tim6389]

SnarlingSheep



what tail -f does is this :

"monitors a file as it grows. Every two seconds, tail wakes up and displays any new data at the end of the file. This flag is ignored if reading from the standard input and standard input is a pipe."


so what i need is a way to have vds take the tail -f cardout.txt - this is display in a dos window and feed this info into perl.. now i see that in your script you have this:

[tim6389]

anyone have any other ideas

[iMPA]

Maybe using the vdsconsole.dll?
It provides Visual DialogScript the ability to provide communication between a console application and their script.

good luck !!

[tim6389]

is that dll freeware?

[Skit3000]

If you want to know if a dll is freeware or not, search for it on vdsworld... If there isn't a Price: label it's free...