or Connect
New Posts  All Forums:Forum Nav:

WiRNS 1.2.x - Page 12  

post #331 of 559
Jim:

Can you try something, please? Leave it running as a service and change your auto update times 2 or 3 times today and see how it responds.

I am running as an app and I plan on forcing 2 or 3 auto updates, also.


Ryan:

Based on what I have seen, I think that this build is a grand slam. Everything has been loaded and working for me in perfect sync. Here is where I stand:

I have 6 of my RTV's running on 1 instance of WiRNS. I am using 4 providers (Dish Network, DirectTV, Expressvu and Vidéotron Digital Cable). I guess my concern over character sets was unfounded. The database seems stable and interacts with all of the configuration screen components without issue. There doesn't seem to be a problem with duplicate channels (for me) now.

As I mentioned before, during initial (cleaned and deleted) installation, there is an issue with the "insertion point" being off by one space in each field of the pop-up window. This seems to be the only functional problem on this build. Way to go!!

Regards,

Wayne
post #332 of 559
Thanks Wayne.. Though I've checked several times the router settings and even rebooted the router twice since I changed ports, I'll COLD BOOT it today when I go home i.e remove the power cord and put it back again. That way nothing can remain in the router's RAM too. Hope that should do away with the problem. Rest all's working fine.

Last night I put the Perl script to force a netconnect on the replay TV for updating the channel guide from my WiRNS server that is always in a standby mode but wakes up to execute this script at 2:00 a.m in the morning.

The only thing that I'm still interested in knowing is that this Perl script when sending a netconnect to my replay makes it download the guide that my WiRNS server has. But I will have to manually update this guide every say 14 days i.e the time limit set in the WiRNS program. So how can we set our WiRNS server to auto update the guide 3 times in a day. I know that the latest 1.2.8.xxxx build runs as a service but how can you tell it as to when to stop and when to run. Secondly, when this service it running, how can you tell it to force a MANUAL GUIDE UPDATE ?

You said it right.. This build does a good job. I do get excpetion while building the ToDo list but I guess that's something to do on my end. Great job done by Ryan on all this stuff and not need to mention all the efforts that you, l8er, kjac have put in. Keep up the good work.

sudhs
post #333 of 559
Quote:
Originally posted by sudhs
So how can we set our WiRNS server to auto update the guide 3 times in a day. I know that the latest 1.2.8.xxxx build runs as a service but how can you tell it as to when to stop and when to run. Secondly, when this service it running, how can you tell it to force a MANUAL GUIDE UPDATE ?
sudhs
sudhs:

Please don't update 3 times per day. Once per day is (for most users around here) just fine.

The DataDirect service is a privilege extended to us by kjac and the kind folks at the zap2it labs. They are already having issues with server use. We don't want to ruin a good thing.

As you know, the latest builds are configurable for DD download time. Ryan has asked them to let us know what times are considered off peak. When he gets his answer, I hope that we all try to use the service during those times.

Regards,

Wayne
post #334 of 559
Running as a app, I have had 3 auto updates (re-configuring the time after each) without a flaw. 14 days, PPV, ToDo, ReplayGuide all behaving well.

I am going to switch over to run as a service and see what happens.

Regards,

Wayne
post #335 of 559
Wayne
Thanks for a prompt reply .. Don't worry.. I didn't mean to do it 3 times a day.. That would just be too insane.. hehehe.. Once DD lets us know a good "off-peak time" then we can set our processes to pull the guide at that time.

Hey, when you say that you run WiRNS as APP then does that mean you run it from a command line i.e ODS mode rather than running it as a service. If so then does it automatically update the guide etc.. If so, can you please send me the command line params that I should use to do this "auto update" using APP mode and put this also as a scheduled service to run it once a day to update my guide.

The steps that I currently follow in this whole process are

1. I manually force a MANUAL GUIDE DOWNLOAD on WiRNS to get the guide info from DD ----> This is the manual procedure that I want to automate.

2. The perl script that I was talking about sends a net connect to the replaytv and then the ReplayTV downloads the guide info from WiRNS by "Hijacking the headend request, as we build the channel list locally here" ---> This is an automated procedure using Perl script.

So I believe that running WiRNS as an APP for step 1 can automate that step too and once the update is done then somehow to kill WiRNS APP so that WiRNS can run again for Step 2 thru the Perl script.

Please do let me know about running WiRNS as an APP and the command line that I need to enter to do this so that it can automatically go and download the guide by itself rather than me forcing a Manual Guide Update.

Thanks again for your help..

sudhs
post #336 of 559
Quote:
Originally posted by lonetreejim
Oh oh.

WiRNS v1.2.8 build 29238 (running as a service) did not auto update last night. Last night was the second night of running this version. The first night updated at 2:20a just fine.

I'll try running as an application for a couple days to see if it auto updates in that mode.

Anybody else seeing this?

ltj
Jim:

Your first auto update should have been at the top of an hour (eg. exactly 2:00am and not 2:20am). If it was not.... did you set your update time in config/DataDirect?

At present, I don't believe, that Ryan defaulted auto update to a particular time. Therefore, if you don't actually choose a time, there will be a problem updating. Once you select a time to update, it will appear in brackets.

Hopefully, that's all there is to your problem.

Regards,

Wayne
post #337 of 559
sudhs:

Go into your WiRNS configuration/DataDirect settings and set your auto update (preferrably to something like 14:00 (2pm). It will update at exactly 2pm everyday (that WiRNS is running at 2pm).

Yes, app mode is command line. You still have all of the WiRNS functionality. Use startwirns.bat to launch app mode.

Regards,

Wayne
post #338 of 559
Wayne,

I do indeed have the time set up. I picked 2:20a at install time and on the first night it updated by itself just fine (see log). It was the second night that it didn't even try. When I forced a manual update it updated fine.

This is not the first build this has happened on. Take a look back and you'll see I posted the same issue on Jan 6 (page 16 of this thread). In the previous time I let it run a 3rd night and it didn't update then either.

So, from my observation I could conclude that, when WiRNS is run as a service, it updates at the precribed time the day it's started and never does it again unless it's forced.

I am just curious if anyone else running as a service has seen similar results.

Jim

---------------------------------------------------------------------------------------------

[2005-01-08 21:27:39] WiRNS v1.2.8 build 29238 - (c) 2004 kjac
[2005-01-08 21:27:39] Updated by rbolen70
[2005-01-08 21:27:39] Thanks: ijprest, waynethedvrguy, Remmer99, gduprey, LeeThompson, j.m., archdog99, FlipFlop, The Dreamer and all the other Replay Hackers out there.
[2005-01-08 21:27:39] Initializing.
[2005-01-08 21:27:39] Loading configuration
[2005-01-08 21:27:39] Starting WiRNS
[2005-01-08 21:27:39] Detected configuration settings. Starting Replay Emulation server on: 192.168.2.97
[2005-01-08 21:27:39] Loading server plugins.
[2005-01-08 21:27:39] Configured to update guide at: 02:20
[2005-01-08 21:27:39] Loading ReplayZone genre data.
[2005-01-08 21:27:48] Plugin: ChannelGuideProvider.dll (1.1.1833.29238) loaded.
[2005-01-08 21:27:48] Refreshing RecordingGuide for: RTV(192.168.2.90)
[2005-01-08 21:27:50] Parsed 51/51 entries.
[2005-01-08 21:27:50] Plugin: GuideServer.dll (1.3.1833.29239) loaded.
[2005-01-08 21:27:50] Plugin: HeadendProvider.dll (1.1.1833.29239) loaded.
[2005-01-08 21:27:50] [PLUGIN] IVSProvider loading permanent entries from F:\\WiRNS\\IVSProvider.conf
[2005-01-08 21:27:50] [PLUGIN] IVSProvider added 2 entries from F:\\WiRNS\\IVSProvider.conf.
[2005-01-08 21:27:50] [PLUGIN] IVSProvider loading cached entries from F:\\WiRNS\\IVSProvider.cache
[2005-01-08 21:27:50] [PLUGIN] IVSProvider added 0 entries from F:\\WiRNS\\IVSProvider.cache.
[2005-01-08 21:27:50] Plugin: IVSProvider.dll (1.1.1833.29239) loaded.
[2005-01-08 21:27:50] Plugin: NoPhoneNumbers.dll (1.0.1833.29239) loaded.
[2005-01-08 21:27:50] Plugin: NoSoftwareUpdate.dll (1.0.1833.29239) loaded.
[2005-01-08 21:27:50] Plugin: PutSyslogProvider.dll (1.1.1833.29239) loaded.
[2005-01-08 21:27:50] Plugin: ServerManagment.dll (1.1.1833.29239) loaded.
[2005-01-08 21:27:50] Plugin: XactProvider.dll (1.1.1833.29239) loaded.
[2005-01-08 21:27:50] Plugin: ZipcodeProvider.dll (1.1.1833.29239) loaded.
[2005-01-08 21:27:50] Replay Network Server Emulation started.
[2005-01-08 21:27:50] Starting configuration server on 127.0.0.1:8923
[2005-01-08 21:27:50] Loading server plugins.
[2005-01-08 21:27:50] Plugin: ServerManagment.dll (1.1.1833.29239) loaded.
[2005-01-08 21:27:50] Replay Network Server Emulation started.
[2005-01-08 21:27:50] Starting NTP Proxy
[2005-01-08 21:27:50] Starting DNS Proxy
[2005-01-08 21:27:50] [DNS] Started DNS Proxy Server
[2005-01-08 21:27:50] **************************************
[2005-01-08 21:27:50] Time Synchronizer (C)2001 Valer BOCAN <vbocan@dataman.ro>
[2005-01-08 21:27:50] Simple Network Time Protocol (see RFC 2030)
[2005-01-08 21:27:50] Modified for WiRNS by rbolen70
[2005-01-08 21:27:50] Connecting to: ntp-production.replaytv.net
[2005-01-08 21:27:50] Local time: 1/8/2005 9:27:50 PM
[2005-01-08 21:27:50] Precision: 8.83423532389192E+74 ms
[2005-01-08 21:27:50] Poll Interval: 1 s
[2005-01-08 21:27:50] Reference ID: time-A.timefreq.bldrdoc.gov (132.163.4.101)
[2005-01-08 21:27:50] Root Dispersion: 25.4974365234375 ms
[2005-01-08 21:27:50] Round Trip Delay: 110 ms
[2005-01-08 21:27:50] Local Clock Offset: -143 ms)
[2005-01-08 21:27:50] **************************************
[2005-01-08 21:27:50] Ready to intercept/proxy ReplayTV requests
.
.
.
[2005-01-09 02:20:00] Attempting to commence update at 2:20
[2005-01-09 02:20:00] Purging old guide information
[2005-01-09 02:20:06] Update Time: 2005-01-09 02:20:00
[2005-01-09 02:20:06] Updating guide information in the database.
[2005-01-09 02:20:06] Processing guide information for: Sun Jan 09
[2005-01-09 02:20:19] Updating lineupmap for: Cogeco Cable Inc. - Digital
[2005-01-09 02:20:20] Updating lineupmap for: Rogers Cable Inc. - Digital
[2005-01-09 02:20:20] Updating lineupmap for: Rogers Cable Inc.
[2005-01-09 02:20:26] Processing guide information for: Mon Jan 10
[2005-01-09 02:20:46] Processing guide information for: Tue Jan 11
[2005-01-09 02:21:03] Processing guide information for: Wed Jan 12
[2005-01-09 02:21:25] Processing guide information for: Thu Jan 13
[2005-01-09 02:21:46] Processing guide information for: Fri Jan 14
[2005-01-09 02:22:06] Processing guide information for: Sat Jan 15
[2005-01-09 02:22:27] Processing guide information for: Sun Jan 16
[2005-01-09 02:22:46] Processing guide information for: Mon Jan 17
[2005-01-09 02:23:04] Processing guide information for: Tue Jan 18
[2005-01-09 02:23:23] Processing guide information for: Wed Jan 19
[2005-01-09 02:23:42] Processing guide information for: Thu Jan 20
[2005-01-09 02:24:01] Processing guide information for: Fri Jan 21
[2005-01-09 02:24:12] Processing guide information for: Sat Jan 22
[2005-01-09 02:24:16] Parsing PPV Configurations.
[2005-01-09 02:24:17] Processing ToDo Information.
[2005-01-09 02:24:17] Refreshing RecordingGuide for: RTV(192.168.2.90)
[2005-01-09 02:24:18] Parsed 51/51 entries.
[2005-01-09 02:24:18] Building ToDo List for: RTV
[2005-01-09 02:24:18] Updating Database with ReplayGuide for: RTV
[2005-01-09 02:24:18] Uploading ReplayGuide data to Poopli...
[2005-01-09 02:24:23] Done.
[2005-01-09 02:24:24] Refreshing plugin channel guide.
[2005-01-09 02:24:24] Loading ReplayZone genre data.
[2005-01-09 02:24:32] Refreshed plugin channel guide.
[2005-01-09 02:24:32] Vacuuming database
[2005-01-09 02:24:45] **************************************
[2005-01-09 02:24:45] Time Synchronizer (C)2001 Valer BOCAN <vbocan@dataman.ro>
[2005-01-09 02:24:45] Simple Network Time Protocol (see RFC 2030)
[2005-01-09 02:24:45] Modified for WiRNS by rbolen70
[2005-01-09 02:24:45] Connecting to: ntp-production.replaytv.net
[2005-01-09 02:24:44] Local time: 1/9/2005 2:24:44 AM
[2005-01-09 02:24:44] Precision: 8.83423532389192E+74 ms
[2005-01-09 02:24:44] Poll Interval: 1 s
[2005-01-09 02:24:44] Reference ID: time-b.nist.gov (129.6.15.29)
[2005-01-09 02:24:44] Root Dispersion: 141.006469726563 ms
[2005-01-09 02:24:44] Round Trip Delay: 109 ms
[2005-01-09 02:24:44] Local Clock Offset: -509 ms)
[2005-01-09 02:24:44] **************************************
[2005-01-09 02:24:44] Collecting free memory
[2005-01-09 02:24:45] Ready to intercept/proxy ReplayTV requests
.
.
.
[2005-01-10 01:27:49] Updating ReplayGuide information
[2005-01-10 01:27:49] Processing ToDo Information.
[2005-01-10 01:27:49] Refreshing RecordingGuide for: RTV(192.168.2.90)
[2005-01-10 01:27:50] Parsed 51/51 entries.
[2005-01-10 01:27:51] Building ToDo List for: RTV
[2005-01-10 01:27:51] Updating Database with ReplayGuide for: RTV
[2005-01-10 01:27:51] Uploading ReplayGuide data to Poopli...
[2005-01-10 01:27:56] Done.
???????????????????????????????????????????????????????????? ???????
[2005-01-10 05:27:49] Updating ReplayGuide information
[2005-01-10 05:27:49] Processing ToDo Information.
[2005-01-10 05:27:49] Refreshing RecordingGuide for: RTV(192.168.2.90)
[2005-01-10 05:27:51] Parsed 51/51 entries.
[2005-01-10 05:27:51] Building ToDo List for: RTV
[2005-01-10 05:27:51] Updating Database with ReplayGuide for: RTV
[2005-01-10 05:27:51] Uploading ReplayGuide data to Poopli...
[2005-01-10 05:27:56] Done.


?????? WiRNS should have tried to update at 2:20a.
post #339 of 559
Thread Starter 
DUH! Forgot to have the timer re-initialize after the update.

This fixes the Manual Guide Update Timer...

 

wirns.1.2.8.guidetimer.zip 89.8115234375k . file
post #340 of 559
Quote:
Originally posted by rbolen70
This fixes the Manual Guide Update Timer...
Thank you sir!

BTW, the NAT functions have worked perfectly since your advice to open the NTP port. I can't tell you how handy it is not to have to worry about my daughter's guide updates (not to mention trying to keep her current on the WiRNS versions).

FWIW, the remote RTV does not need to be named in the WiRNS setup for it to be able to get guide updates. I removed my daughter's RTV from the listing on my instance and she can still upload the guide no problem. The only things she can't do are use the To-Do List, Channel Guide and Guide Server functions of WiRNS.

ltj
post #341 of 559
Wayne and Ryan,

All's working for me except for one piece and i.e IVS. I've chosen port 5000 and my ISN is 00004-54832-61736. I had changed it to port 29100 and then to port 27000 but they weren't reachable. So I changed it back to 5000. Now I can reach to it again thru. Lunatic Haven. No probs. It pings just fine. So that means all's working good. Correct ? Now the problem that I'm having is that even though I've accepted the show, it has been showing me 0% for the last 2 days. One more thing.. I checked up and verified that my D-Link DI-713P DOES NOT SUPPORT loopback but since I don't have any other ReplayTV so I don't have to bother about it as long as I can reach thru Lunatic Haven. Correct ? Can this be occuring because I converted a 5504 to 5040 ? Please help.

Lunatic Haven Results

Asked ReplayTV server about unit at ISN 00004-54832-61736.
Found on Replay server.


The IP for your ReplayTV is XX.XX.XX.XX
The Port for your ReplayTV is 5000
Successfully contacted ReplayTV unit.
The ReplayTV says:

ISN: 00004-54832-61736
Nickname: Vyomdi
post #342 of 559
sudhs:

Looks like you are almost there. I just tried to add you to my contact list (to test your connection). I couldn't contact your unit.

As I understand it, just because you get a ping from Lawrence's test page, it doesn't mean that you are 100% good to go.

I don't know anything about the DLink configuration. Hopefully, j.m. or another network guru is around today and can tell you what you need to do. However, a couple of things to ensure:

1- You have nothing else using the port.
2- You entered the ip of the RTV unit properly in the router config/port forwarding information.
3- all of the check boxes that should be checked are checked.
4- patience will be rewarded.

Regards,

Wayne
post #343 of 559
Thanks for the prompt reply and consideration. I changed my port from 5000 to 29000 again to test. Then I asked a friend of mine to reach me at http://68.40.162.42:29000/ivs-IVSGetUnitInfo which he could do successfully. Can you also please try to go to this site and check for the results. I'm sure you'll get thru since he successfully did. Then I went to the Lunatic Haven and test it from there. it failed the test from Lunatic Haven. So there's something fishy about this whole setup where it succeeds from one place but fails at the other. Also, the lunatic haven port number failure message is still showing me the old port number i.e 5000.

Asked ReplayTV server about unit at ISN 00004-54832-61736.
Found on Replay server.


The IP for your ReplayTV is XX.XX.XX.XX
The Port for your ReplayTV is 5000
Unable to contact ReplayTV unit.
500 Can't connect to 68.40.162.42:5000 (connect: timeout)
Check your port forwarding settings
-------------------------------------------------

Thanks for all the help extended. Will try out some more perm. and combs.. As you said.. Patience Pays.

Regards
sudhs
post #344 of 559
sudhs:

I was able to ping you with a browser but could not get you with my RTV.

Did you try rebooting your WiRNS computer after the port forwarding/router changes? That might be worth a try.

BTW... you were already in my address book. I must have sent you something in the past, no?

Are you using j.m.'s ivsprovider.conf? If so, are the settings correct in the file? Just fishing for answers.

Stay with it. You will get it.

Regards,

Wayne
post #345 of 559
When you check the replay server: rddns-rns.replaytv.net
(which is what the replay units do)

rddns lookup 00004-54832-61736

you get a repsonse:

<UnitTicket isn="00004-54832-61736" ip="68.40.162.42" port="5000" lastupdateddate="2005-01-07 07:23:10" />

This says that you are using port 5000 and the last update was on Jan 7.
This is why they cannot contact you since you are on a different port.

-Chris
post #346 of 559
Thanks a bunch wayne and gatomon. I think both your comments lead to the conclusion that 'coz of my not shutting down my WiRNS server for the last 3 days (i.e when I've been experimenting with the port no. thing) I'm facing this problem. So first thing I'll do after returning from work will be to shut down the machine, bring it back up again, clear all cookies and temp. internet files. Then i'm gonna fire the Perl script and also make sure that it's gonna update the guide info. + Reply Info + Todo list. Once done, I'll check thru Lunatic Haven and post my coments.

Hey gatomon, where and how did you get the info. (i.e the lastupdatedate etc.) from rddns-rns.replaytv.net ?

Again guys.. thanks a lot for your inputs and help. Since all this has been more-or-less setup for me i.e auto guide update, auto channel update, auto mapping of DISH (110,119 and 61.5) sats. and CA, I'm pretty happy with the moves this forum has made. All the help and inputs from each and every person count a whole lot. The last part that's left is the IVS which I hope will somehow get resolved. Keeping my fingers crossed.

Thanks again..
Regards,
sudhs
post #347 of 559
wayne.. I think you did send me the 60 mins show earlier, but it never completed. So I asked for some more shows from other users and they didn't complete too. Once this port issue is resolved, I'll request another one from you. Also, please tell me what purpose does the IVSProvider.conf serve out here. It's used for Loopback purposes to override RDDNS data. Since I'm using just one ReplayV, do I really need to configure it with the IP|PORT|ISN ? Bby the way, which IP to use.. ReplayTV IP or WiRNS IP ? I think it should be ReplayTV's IP . Correct ? 'coz the port is that of ReplaTV.

Your comments and suggestions are really appreciated.

Regards,
sudhs
post #348 of 559
sudhs:

You really don't need ivsprovider.conf. It is for loopback. I didn't know how you were configured. (the ip is supposed to be for the RTV unit)

Just double/triple check your routers port forwarding configuration. Cross your fingers. At some point, it was working because we got a transfer started.

Wayne
post #349 of 559
Wayne.. still no luck man.. I rebooted the WiRNS server and executed the script to do the netconnect and still the port shows 5000. I even configured the IVSprovider as mentioned. Mine is a very simple confgn. i.e one replaytv and one D-Link 713P router,which does not have loopback. I've checked again 'n again for the port mentioned in the "Virtual Server" setting of my router (which is actually the port fwding section) and I've confirmed the IP address also to be the same as ReplayTV but no luck. I think that as gatomon has mentioned that somehow he still sees my status on rdns server to be having port 5000 and it was last updated on Jul 7th. Now I don't know where did he pick up that data from. I mean how did he get to the rdns sever and ask/query for the data. As per gatomon he says ...
------------------------------------------------------
When you check the replay server: rddns-rns.replaytv.net
(which is what the replay units do)

rddns lookup 00004-54832-61736

you get a repsonse:

<UnitTicket isn="00004-54832-61736" ip="68.40.162.42" port="5000" lastupdateddate="2005-01-07 07:23:10" />
-------------------------------------------------------------------------

don't know how and where does he see this data from. But it seems that it's the rdns servers that need to be updated with the new port number. How??.. that I don't know.. Do you have some insight on this one..


regards,
sudhs
post #350 of 559
Ryan, many thanks!

Working great for me now. PPV for Dishnetwork is there. No weirdness in the guide...all channels show the correct info.

Again, thanks!

Sean
post #351 of 559
sudhs:

Check here and at planetreplay.com for one of the network guys to chime in. j.m. hangs out from time to time at planetreplay. He is a wizard with this kind of stuff.

Are you running behind a firewall? Can that be an issue?

Is there any chance of trying another router? Possibly a Linksys would offer another look at this.

It will work itself out.

Regards,

Wayne
post #352 of 559
Does anybody have a clue of how to remove OR replace the IVS port entry on the rddns-production.replaytv.net ? It seems that currently it is set to 5000 but I need to update it with 29000. How can I do it ? Even though I have changed the port fwd to 29000 but the Lunatic Haven still shows an error message syaing that my port is set to 5000.

So which file needs to be updated ? Is it IVSProvider.hosts file or wirns.hosts file or any other file ? Please help..

sudhs
post #353 of 559
I have a new 5504, i already am using wirns to get cananda and dish listings with remapped channels. I need to activate it with repalytv though. can i do that through wirns or do i need to reset my ip adress so it will go out normally to activate it?, then reset it fo rwirns and d/l the listings again, or will activating it, force me to d/l different listings?
post #354 of 559
OK..wayne.. i got the thing working now.. Port 29000.. yooohoooo.. Now the real test is whether the IVS will work or not. So let's give it a try. I'll request a show from you. Please grant permission to my request. Oh.. bythe way the trick was pretty simple.. Since I knew that I had to somehow reset the rddns entry which cannot be done thru a WiRNS server no matter what you put so why not go directly to it. So I changed the statiC IP to automated on my RTV and then said Connect To Replay TV Service which is forced a NetCOnnect. The request said CHekcing for activation, Chekcing for new channels and I disconnected right there so that it does not change my software back to 5504. Now the connection of my RTV to the rddns server and setting the clock were more than enough to reset the port no of my IVS to 29000. I now pinged it thru the IVS tester and it worked like a charm. Then I changed my RTV IP back to the WiRNS IP and all's working fine now. I mean atleast the ping is working fine now from the IVS tester also.

Thanks for your help and efforts on this..

Regards,
sudhs
post #355 of 559
rddns lookup 00004-54832-61736

<UnitTicket isn="00004-54832-61736" ip="68.40.162.42" port="29000" lastupdateddate="2005-01-12 04:23:24" />

It seems it's been updated with port 29000. BTW, rddns is a part of an older
program (replaypc-0.4.0). It's written in "c" and I had to fix a couple of things
to make it work. I've complied it on Mac OSX and linux, I don't do "windows".

-Chris
post #356 of 559
Quote:
Originally posted by rbolen70
DUH! Forgot to have the timer re-initialize after the update.

This fixes the Manual Guide Update Timer...
Ryan, no joy.

WiRNS v1.2.8 build 24467 didn't auto update last night (night 2).

ltj
post #357 of 559
Jim:

You should go to 29238. It (IMHO) is rock solid.

Regards,

Wayne
post #358 of 559
Wayne.. I accepted the your send but it still shows me 0% of 112x Mb done. For some reason it's not moving on my side. EVen though my router can now be pinged from IVS tester side for port 29000 but it still does not start the reception of the shows. Any light on this. Can this be some internla error of ReplayTV since I've hacked 5504 to work like 5040. Is there anybody on this forum who has converted a 5504 to 5040 and receiving the shows via IVS ?

Thanks again Wayne..

regards,
sudhs
post #359 of 559
sudhs:

I have many sends going from that particular RTV unit. It could be queued. I will send you a short clip from another unit.

Regards,

Wayne
post #360 of 559
sudhs:

I was able to add your unit to my address book in an RTV. Immediately afterwards, I was not able to send the clip. I tried at least 5 times.

Strange. I will try later.

Regards,

Wayne
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: ReplayTV & Showstopper PVRs
This thread is locked