If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

You should still be able to get tyFTPd working with MovieLoader with the changes I suggested earlier. You might need to delete the chache directories and allow them to be rebuilt, but it did work for me.

THANKS!

That worked fine.

I made the changes in message #53, but not the "." for ":" substitution for Long Date in the following message, and for the first time, tyftpd worked with MovieLoader Tivo-to-Tivo, which was what I really needed (always HAS worked from hard drive to Tivo). This was HR10-250 to HR10-250.

You should still be able to get tyFTPd working with MovieLoader with the changes I suggested earlier. You might need to delete the chache directories and allow them to be rebuilt, but it did work for me.

Woohoo!! Changes worked. This is awesome. Best thing is, it doesn't slow down my TiVo like mfs_ftp. :-) One thing though, do you know why the recordings all show up with a duration of 0:00 (Partial)??

One thing though, do you know why the recordings all show up with a duration of 0:00 (Partial)??

I just noticed that when I initiate the transfer, the duration is listed correctly, but after it completes, it is set to 0:00. I was looking at tyftpd.tcl, but really don't see why this would be happening. I see where it sets it, but not why it is resetting it to back to 0:00 after the transfer completes. Any ideas?

Why on earth would you want to stop such a kewl program No, seriously, I usually just disconnect the clients and issue a kill <pid> to get rid of the server and haven't had any reboot issues. How are you stopping it when you get a reboot and what platform. I only have THD's to test with.

Woohoo!! Changes worked. This is awesome. Best thing is, it doesn't slow down my TiVo like mfs_ftp. :-) One thing though, do you know why the recordings all show up with a duration of 0:00 (Partial)??
!

I've noticed that too. They also loose the station affiliation to which station they were recording from. It just says "tyFTPd" where it would normally have the station callsign.

They say beer will make me dumb. It are go good with pizza!-----------
3XR10, prommed, 3xdvr40,4xdvr39, all networked, ranging from 40GB to 750GB

I've noticed that too. They also loose the station affiliation to which station they were recording from. It just says "tyFTPd" where it would normally have the station callsign.

Well, I think the Station stuff was never implemented. Looking at line 1198 I see this in tyftpd.tcl:

Code:

# TODO - We could add a function to locate the real first station based on the CallSign
# Create the dummy Station object
set station [db $ServerData(db) create Station]
dbobj $station set CallSign "tyftpd"
dbobj $station set Name "tyftpd"

So on mine, and I am sure yours, the station always remains tyftpd. The CallSign data is in the XML so I don't understand the comment. jkozee must have had something else in mind.

Why on earth would you want to stop such a kewl program No, seriously, I usually just disconnect the clients and issue a kill <pid> to get rid of the server and haven't had any reboot issues. How are you stopping it when you get a reboot and what platform. I only have THD's to test with.

I have been starting the program via telnet, when I close out the telnet window the TiVo reboots. Using directv hr10-250 6.4a SW, I will try to kill <pid> then close telnet window and see what happens.

How aer you calling the command when you run it from a window. IIRC, if you are running ANY tcl script in the foreground of a telnet window, and you close the windows without killing the process (ctrl-c), then the unit will reboot. This may have nothing to do with tyFTPd.

Smee is correct, the station isn't implemented. This is the same behavior as mfs_ftp IIRC. In order to do stations properly, one would have to search the unit and try to locate the station by callsign and then use that object exists, or else create a dummy one. I don't even think that tivo's own TivoDesktop bother with stations, but it would be trivial to add if one was so inclined.

How aer you calling the command when you run it from a window. IIRC, if you are running ANY tcl script in the foreground of a telnet window, and you close the windows without killing the process (ctrl-c), then the unit will reboot. This may have nothing to do with tyFTPd.

you are correct sir!! I was running ./tyftpd.tcl -l -d & command prompt and when I closed the window it rebooted. I confirmed killing <pid> before closing window keeps the TiVo running, also confirmed ./tyftpd.tcl -l command and then (ctrl-c) to kill process also keeps the TiVo alive. Thanks jkozee

Do you know why the recordings all show up with a duration of 0:00 (Partial) after the transfer completes even though the transfer starts off with the correct duration after the transfer first starts?? I really can't figure out why it is happening. At least it is happening to me on my DTIVOs running 6.4a.

No. I haven't had a chance to look at that. I don't think I touch anything but state in CleanupRecording. You can try setting the properties (startime stoptime duration etc) again there and see if that fixes it.

Are you working on the MovieLoader patch for the FSID's in the filename? I haven't seen a request in that thread, so I thought you might be having a go at it yourself. I don't use MovieLoader and don't really do JAVA, but I did dowload it to see what issues it has with tyFTPd. Looks like you could add another regex pattern for the FSID case and get rid of those "Unparseable date" errors fairly easy.

I will upate tyFTPd to allow for daemonizing and will add a flag to only show the tmf directory which should improve the MovieLoader compatibility. I'll include the patch to ignore PASV ip address checks also and I just finished a porting mfs_ftp_helper to the mips.32/mips.64 unified code.