MFSStream vs TyTool

[boboli]

I also have the problem with MFSStream producing 0K downloads thru DelousedTW. However, I haven't really been too concerned about is, as TyTool5 does work.
But I am curious. Which process produces a better quality download? Is it worth the effort to fix MFSStreams or is TyTool5 fine for the purpose?
B
T-60 2.5.2 2 120 G HDs

[mrblack51]

0k files are often the result of not having a noscramble patch applied, either directly to the kernel or through the kernel module.

tytool seemed to extract stuff great. mfs_stream seemed to pull off files that were 16 bytes off (as in 16 bytes of garbage or something) according to tydemux.

[boboli]

Originally posted by mrblack51
0k files are often the result of not having a noscramble patch applied, either directly to the kernel or through the kernel module.

tytool seemed to extract stuff great. mfs_stream seemed to pull off files that were 16 bytes off (as in 16 bytes of garbage or something) according to tydemux.

Well, I do know that noscramble is active. I also have tried to put mfsstream files in the /tivoweb-tcl dir instead of the modules dir. And I have edited the mfsstream.cfg file to reflect the proper path. And I have also created a /var/hack/tivoweb-tcl dir. Plus I have sacrificed a live goat in the light of the first full harvest moon that fell on the third Weds of the month while howling loudly and profusely..
None of the above have fixed the mfsstream problem. Though the last one did get my neighbor pissed at me. :D
B

[mrblack51]

the mfsstream files belong in the modules dir. mfs_stream belongs anywhere, but the .cfg needs to be modified to reflect that. also, you need to have the tyhttpd server running.

[boboli]

Originally posted by mrblack51
the mfsstream files belong in the modules dir. mfs_stream belongs anywhere, but the .cfg needs to be modified to reflect that. also, you need to have the tyhttpd server running.

Mfsstream files in modules dir. Check
Mfsstream.cfg reflects proper path. Check
The tyhttpd server is running. Check
/var/hack/tivoweb-tcl dir created. Check.

Don't understand why it still doesn't work.
B

[mrblack51]

i am assuming you are running tivoweb-tcl out of /var/hack/tivoweb-tcl?

i would go through the instructions again, carefully. also, try extracting some stuff manually by running mfs_stream from the command prompt. did you make sure to chmod a+x mfs_stream?

[boboli]

Originally posted by mrblack51
i am assuming you are running tivoweb-tcl out of /var/hack/tivoweb-tcl?

i would go through the instructions again, carefully. also, try extracting some stuff manually by running mfs_stream from the command prompt. did you make sure to chmod a+x mfs_stream?

No, the deloused TW was installed by SZ's 2.5.2 upgrade and it resides in /tivoweb-tcl.
I'll check the permissions as you suggest and see what I can see.
B

[boboli]

Originally posted by boboli
No, the deloused TW was installed by SZ's 2.5.2 upgrade and it resides in /tivoweb-tcl.
I'll check the permissions as you suggest and see what I can see.
B

mfsstream.itcl was set to read only. I did the chmod a+x and rebooted the unit.
Still 0K transfers. This is really a mystery. And I hate mysteries.
B

[mrblack51]

check to make sure that mfs_stream is executable. mfsstream.itcl is different from mfs_stream. one is the program that extracts stuff, the other is a script which provides the tivoweb interface. put mfs_stream in /bin, and then modify the mfsstream.cfg to point to /bin for the path.

[boboli]

Originally posted by mrblack51
check to make sure that mfs_stream is executable. mfsstream.itcl is different from mfs_stream. one is the program that extracts stuff, the other is a script which provides the tivoweb interface. put mfs_stream in /bin, and then modify the mfsstream.cfg to point to /bin for the path.

Well, color me six different kinds of embarrassed. :rolleyes:
When I did a 'find' I did ' find / -iname mfss*' which, of course, did not locate the mfs_stream executable. I placed that file in the path designated by the .cfg file and, imagine this? It worked!
While I will probably still use TyTool for the extraction process, it's nice to have the mystery solved.
Thank you MrBlack. Much appreciated.
B