| View previous topic :: View next topic |
| Author |
Message |
hudsonsmom Almost hooked
Joined: 23 Jul 2011 Posts: 5
|
Posted: Sun Jul 24, 2011 7:08 pm Post subject: |
|
|
Close, but still having problems...
- Installed FreeSCO and WiRNS 3.0.4
- Setup Schedules Direct account
- Was able to view the Channel Guide info in WiRNS
The showstopper is having problems dialing into the FreeSCO. For some reason, the modem is only activating every 15 minutes (or so) - and only for about 30 seconds. By the time I force the Replay to redial, it's too late - and the modem hangs up.
I reviewed the /pkg/sbin/mgetty file, and the key variables are set as follows:
PHONESIM=n
DELAY1=2
DELAY2=30
From what I understand, this means it should be redialing every 30 seconds or so - plenty of time for Replay to sync up. But...
Help!
| jonwz wrote: | That's very good gobbidy-gook. From my recollection, that what the initial PPP packet looks like on a terminal screen.
|
|
|
| Back to top |
|
 |
jonwz Replay user

Joined: 05 Nov 2007 Posts: 63
|
Posted: Mon Jul 25, 2011 3:54 am Post subject: |
|
|
I haven't played with the mgetty settings as I normally have access to a telco line simulator.
But there's an easy way to force the FREESCO modem to answer, and give control back to FREESCO:
http://www.avsforum.com/avs-vb/showthread.php?p=20582320#post20582320
| hudsonsmom wrote: |
From what I understand, this means it should be redialing every 30 seconds or so - plenty of time for Replay to sync up. But...
Help!
|
_________________ Own three upgraded 3xxx's - |
|
| Back to top |
|
 |
hudsonsmom Almost hooked
Joined: 23 Jul 2011 Posts: 5
|
Posted: Mon Jul 25, 2011 12:32 pm Post subject: |
|
|
Thank you!
Forcing the FreeSCO connection works perfectly. Just wait for the replay to start "Dialing", and type:
[Linux] minicom /dev/cua0 38400
ATA <to start up modem>
Hopefully, the guide is downloaded correctly - so far, so good. I'm currently at "Getting program listings for channels (60%)" for 31 channels - so far it's taken 29 minutes.
Let me know if you're interested in the final download stats.
Thanks, again.
Pennee
|
|
| Back to top |
|
 |
sillyname99 Replay fan

Joined: 30 Sep 2006 Posts: 51
|
Posted: Mon Jul 25, 2011 5:54 pm Post subject: |
|
|
Congratulations Penee.
I found a driver for the pcmcia network card, so now I'm trying to figure out how to install it onto the floppy.
I don't know if I'm going to be able to pull this off. We may just have to abandon the showstoppers and only use the 5040. At least I have that working. |
|
| Back to top |
|
 |
Susan G Replay user

Joined: 07 Dec 2005 Posts: 74
|
Posted: Mon Jul 25, 2011 6:14 pm Post subject: |
|
|
| hudsonsmom wrote: | Thank you!
Forcing the FreeSCO connection works perfectly. Just wait for the replay to start "Dialing", and type:
[Linux] minicom /dev/cua0 38400
ATA <to start up modem>
Hopefully, the guide is downloaded correctly - so far, so good. I'm currently at "Getting program listings for channels (60%)" for 31 channels - so far it's taken 29 minutes.
Let me know if you're interested in the final download stats.
Thanks, again.
Pennee
|
Yes, congratulations! I'm definitely interested in the final download stats, since I've been trying to get a similar setup working for days. My connections always fail at the very end.
Are you running FREESCO in VMWare player, or natively?
Thanks-
-Susan |
|
| Back to top |
|
 |
hdonzis Moderator

Joined: 05 Jan 2005 Posts: 7826 Location: San Antonio, TX
|
Posted: Mon Jul 25, 2011 9:35 pm Post subject: |
|
|
| sillyname99 wrote: | | I found a driver for the pcmcia network card, so now I'm trying to figure out how to install it onto the floppy. |
I don't know what version of FREESCO you are using, but I docuemented my experience with getting a PCI Ethernet driver working here...
Henry _________________ Here's my Poop |
|
| Back to top |
|
 |
sillyname99 Replay fan

Joined: 30 Sep 2006 Posts: 51
|
Posted: Tue Jul 26, 2011 12:10 am Post subject: |
|
|
I was using 0.4.3, so the first thing I will do is get 0.3.2. However, I'm not clear on how to get the driver to the right place on the floppy. It comes with a file called SETUP and a file called 8139.vol. The SETUP file is:
echo "Install RTL 8139X/8100 Family Fast Ethernet Adapter Driver (MDI)"
echo 'Please input source path ? ( ex: a:/sco/5.x) \c'
read d_path
echo "Please wait to transfer files ................"
if [ ! -x /tmp ]
then
mkdir /tmp
fi
doscp $d_path/8139.vol /tmp/VOL.000.000
echo "Transfer End ............"
echo "Please use 'custom' to install the driver."
echo "And follow the following options::"
echo " Software/Install New/From 'your computer'/MediaImages"
echo "Then enter the directory::/tmp"
I put the files in the router directory. When I tried to run SETUP, it ran the freesco setup instead, possibly because I didn't use capital letters. I'll try the capital letters after work tonight. I'm also not sure how I will get to the "custom" thing if I get that far. If anyone has thoughts, I'd appreciate any direction.
Thank you all for your patience. |
|
| Back to top |
|
 |
hdonzis Moderator

Joined: 05 Jan 2005 Posts: 7826 Location: San Antonio, TX
|
Posted: Tue Jul 26, 2011 11:24 am Post subject: |
|
|
| sillyname99 wrote: | | However, I'm not clear on how to get the driver to the right place on the floppy. |
It's been too long ago that I don't remember. However, I'm sure I found instructions on it out there...
Henry _________________ Here's my Poop |
|
| Back to top |
|
 |
sillyname99 Replay fan

Joined: 30 Sep 2006 Posts: 51
|
Posted: Tue Jul 26, 2011 4:26 pm Post subject: |
|
|
I downloaded 0.3.2 and the pcmcia driver, but either I don't have the settings right or I didn't do the right thing with the driver. I continue to google, looking for instructions or tips.
Susan, did you have a good reference for settings?
Thanks |
|
| Back to top |
|
 |
Susan G Replay user

Joined: 07 Dec 2005 Posts: 74
|
Posted: Tue Jul 26, 2011 10:22 pm Post subject: |
|
|
| sillyname99 wrote: | I downloaded 0.3.2 and the pcmcia driver, but either I don't have the settings right or I didn't do the right thing with the driver. I continue to google, looking for instructions or tips.
Susan, did you have a good reference for settings?
Thanks |
You mean for the FREESCO settings? I just followed the Wiki instructions, but I didn't have any problems with my network card. Are you trying to add drivers to the FREESCO floppy? I never tried to do that. I got as far as making a bootable FREESCO USB stick and confirmed that it won't see my internal modem.
Sorry I can't help.
-Susan |
|
| Back to top |
|
 |
hdonzis Moderator

Joined: 05 Jan 2005 Posts: 7826 Location: San Antonio, TX
|
Posted: Wed Jul 27, 2011 2:53 pm Post subject: |
|
|
If you're looking for instructions on setting up FREESCO version 0.3.2, then you should be looking here, with the step-by-step instructions being here...
Henry _________________ Here's my Poop |
|
| Back to top |
|
 |
rmeden Replay junkie

Joined: 22 Jun 2007 Posts: 146
|
Posted: Wed Jul 27, 2011 9:39 pm Post subject: |
|
|
Here's a new piece of info for folks doing FreeSCO modem setups in a VM.
When setting up FreeSCO for LaHo, the PC didn't have a serial port. I used a USB->Serial adapter. There were *lots* of retransmissions and while it worked, it worked slowly and sometimes there were interrupt problems (seen if I typed commands directly to the modem in minicom)
The solution was drop drop the USB-Serial adapter and put in a PCI one. Ever since connections (mine and others) have been very clean.
Robert |
|
| Back to top |
|
 |
RichG Almost hooked
Joined: 28 Jul 2011 Posts: 6
|
Posted: Thu Jul 28, 2011 11:14 am Post subject: |
|
|
| sillyname99 wrote: | I downloaded 0.3.2 and the pcmcia driver, but either I don't have the settings right or I didn't do the right thing with the driver. I continue to google, looking for instructions or tips.
Susan, did you have a good reference for settings?
Thanks |
Don't know where you got the driver. If you go to freesco.sourceforge.net and download the Freesco 0.3.2/modules 032 zip file, you'll find modules.html inside. This web page has the driver names for various network adapters and instructions for installing a driver. To save you some time, the driver must be placed in \ROUTER\DRV on the freesco floppy. |
|
| Back to top |
|
 |
hudsonsmom Almost hooked
Joined: 23 Jul 2011 Posts: 5
|
Posted: Thu Jul 28, 2011 11:33 am Post subject: |
|
|
My setup...
- Showstopper 2000
- Vista Laptop
- External Zoom 56k USB modem
- magicJack
- VMware Player 3.1.4 <installed locally on laptop>
- WiRNS 3.0 Beta (updated to 3.0.4) <installed locally on laptop>
Now that there's time, I will probably order a chat-cord, to see if I can simplify things - and get rid of the external modem and magicJack.
Timing...
- My "test" setup only included 31 channels - it ran in 46 minutes.
- I updated the Schedules Direct list for the essentials (53 channels), and re-ran NetConnect - it ran it 59 minutes.
I'm planning to do a weekly forced connections, and 1-2 hours is workable.
Once again, thanks to everyone for your help I LOVE my Showstopper, and am ecstatic that I don't have to give it up. Thank you!!
Hope this helps.
Pennee
| Susan G wrote: | Yes, congratulations! I'm definitely interested in the final download stats, since I've been trying to get a similar setup working for days. My connections always fail at the very end.
Are you running FREESCO in VMWare player, or natively?
|
|
|
| Back to top |
|
 |
RichG Almost hooked
Joined: 28 Jul 2011 Posts: 6
|
Posted: Thu Jul 28, 2011 2:50 pm Post subject: |
|
|
WORKING SOLUTION for SHOWSTOPPER HS2000
(sorry about the formatting, but I'm new to this)
My setup:
- Desktop ( WiRNS Server) -> Creative Modem Blaster, Realtek PCIe GBE network adapter, XP Pro
- Laptop (Dial-Up Server) -> Thinkpad X61s, Thinkpad Modem (CXT), Intel 82566MM network adapter, XP Pro SP3, VMWare Player (3.1.4), Freesco 0.3.2 (noauth beacuse true dial-up)
- Replays:
2 Replay 5000 (network connected)
1 ShowStopper HS2000
- 2 Telco Phone Lines
The 5000s have worked flawlessly with WiRNS - first with version 2 and now with version 3; the SS was a different story:
Dataflow for SS: SS->Telco(line1)->Telco(Line2)->Laptop Modem->VMWare serial->Freesco cuax->Freesco eth0->VMware->WiRNS Server->VMWare->Freesco eth0->Freesco cuax->VMWare serial->Telco->SS
The WiRNS server modem refuses to interact with the SS, but the SS and Thinkpad play nice together. Loaded the SS dialing prefix with the Line 2 phone number and the SS and WiRNS connected on a regular basis; did not change the modem speed as modems are pretty good at finding a working speed on their own, did change my zip code. Like others, the initial call showed progress to 88% then got the dreaded Network Connect Error. Discarded the changes, once again chaned my zip code and attemped to connect to ReplayTV's service. It also terminated abnormally! This happened consistantly until a 243-Zones (6)Clear Channel Guide was executed. Tried to just get the Channel Guide from WiRNS without changing the zip code. It connected, spent a long time (about 1 hour) downloading, then died with "problem with connection" message (not exact). This time there was an added bonus of the channel guide getting wiped out. Connecting to the replay service gave the same results as before: it failed. As before, clearing the channel guide resolved the problem. A network trace revealed that both the initial setup failure and the get channel guide failure occured when WiRNS sent a large burst of data to the SS. It appears to be a problem in the VMWare-Freesco coupling. Changed the VMWare network interface to "Bridged" instead of "NAT", changed the network setting in Freesco to use DHCP (setup->Advanced settings->(62)Local network->(627)Use DHCP client to y). x out to the screen that lets you save the setting save then reboot.
After this, the network traces showed much better flow control, and the SS completes all interactions with WiRNS. I download 417 channels for 14 days in less than 1 hour.
Threr is a caveat: Freesco may not have the correct driver for your native ethernet controler. The pcnet32.gz driver is for, among others, the vmware NAT interface. In bridge mode you are using your native network adapter. If when you boot Freesco, it will say, in red, that there is no network interface, this tells you that you need a different network driver. the link Freesco.sourceforge.net modules.zip contains alternate drivers and installation instructions.
Good Luck,
-Rich |
|
| Back to top |
|
 |
Susan G Replay user

Joined: 07 Dec 2005 Posts: 74
|
Posted: Tue Aug 02, 2011 3:52 pm Post subject: |
|
|
@RichG:
| Quote: | | Changed the VMWare network interface to "Bridged" instead of "NAT", changed the network setting in Freesco to use DHCP (setup->Advanced settings->(62)Local network->(627)Use DHCP client to y). x out to the screen that lets you save the setting save then reboot. |
I was finally able to get a successful net connect with my Showstopper/FREESCO/VMWare setup when I changed the VMWare ethernet connection to "Bridged", so thank you very much for that tip! There's still something not right with my settings, because "Use DHCP client" enabled actually didn't work -- I had to leave that at "n".
I switched back to DNNA after the change-of-heart announcement, but I do want to get WiRNS working again in preparation for the inevitable. When I tried last night with the exact same settings that worked before I kept getting network connection errors at the end, so I'm back to troubleshooting, but at least I know it's possible to get this working!
Thanks-
-Susan
P.S.: And thanks for posting your info, Pennee!  |
|
| Back to top |
|
 |
RichG Almost hooked
Joined: 28 Jul 2011 Posts: 6
|
Posted: Thu Aug 04, 2011 2:29 pm Post subject: |
|
|
| Quote: | | I was finally able to get a successful net connect with my Showstopper/FREESCO/VMWare setup when I changed the VMWare ethernet connection to "Bridged", so thank you very much for that tip! There's still something not right with my settings, because "Use DHCP client" enabled actually didn't work -- I had to leave that at "n". |
This is not a major issue. The only reason I can think of for this to fail is that your home network doesn't have a DHCP on it. If you do then something strange is going on. The reason for suggesting you use the DHCP client setting is to place Freesco on the same subnet as your WiRNS server. This will eliminate any firewall issues in your configuration. You can accomplish the same thing by manually assigning IP addresses to both your eth0 and modem adapters in Freesco. Most consumer routers assign DHCP addresses in the 50-150 number range. Assigning numbers between 200 and 254 should avoid conflicts. Assign using this formula: (same as WiRNS).(same as WiRNS).(same as WiRNS).(unique above 200).
DO NOT DO THIS IF YOU ARE USING NAT IN VMWARE!
| Quote: | | I switched back to DNNA after the change-of-heart announcement, but I do want to get WiRNS working again in preparation for the inevitable. When I tried last night with the exact same settings that worked before I kept getting network connection errors at the end, so I'm back to troubleshooting, but at least I know it's possible to get this working! |
Using bridged mode helps avoid the problem, but it doesn't solve it: it still takes a few interactions between WiRNS and the SS to settle in to a working data exchange. In my setup, I net connect daily without any failures so far, but I send to the SS 417 channels and guide data for 2 weeks. If you are sending (for example) 50 channels, the guide data may still be bursting to the replay before the 2 endpoints establish a workable exchange. I'd be interested in knowing what would happen if you were to go through the initial setup again. If that works, then this theory has more credibility. |
|
| Back to top |
|
 |
Susan G Replay user

Joined: 07 Dec 2005 Posts: 74
|
Posted: Thu Aug 04, 2011 6:24 pm Post subject: |
|
|
| RichG wrote: | | Quote: | | I was finally able to get a successful net connect with my Showstopper/FREESCO/VMWare setup when I changed the VMWare ethernet connection to "Bridged", so thank you very much for that tip! There's still something not right with my settings, because "Use DHCP client" enabled actually didn't work -- I had to leave that at "n". |
This is not a major issue. The only reason I can think of for this to fail is that your home network doesn't have a DHCP on it. If you do then something strange is going on. The reason for suggesting you use the DHCP client setting is to place Freesco on the same subnet as your WiRNS server. This will eliminate any firewall issues in your configuration. You can accomplish the same thing by manually assigning IP addresses to both your eth0 and modem adapters in Freesco. Most consumer routers assign DHCP addresses in the 50-150 number range. Assigning numbers between 200 and 254 should avoid conflicts. Assign using this formula: (same as WiRNS).(same as WiRNS).(same as WiRNS).(unique above 200).
DO NOT DO THIS IF YOU ARE USING NAT IN VMWARE!
| Quote: | | I switched back to DNNA after the change-of-heart announcement, but I do want to get WiRNS working again in preparation for the inevitable. When I tried last night with the exact same settings that worked before I kept getting network connection errors at the end, so I'm back to troubleshooting, but at least I know it's possible to get this working! |
Using bridged mode helps avoid the problem, but it doesn't solve it: it still takes a few interactions between WiRNS and the SS to settle in to a working data exchange. In my setup, I net connect daily without any failures so far, but I send to the SS 417 channels and guide data for 2 weeks. If you are sending (for example) 50 channels, the guide data may still be bursting to the replay before the 2 endpoints establish a workable exchange. I'd be interested in knowing what would happen if you were to go through the initial setup again. If that works, then this theory has more credibility. |
Thanks for the clear explanation, Rich. I have a 78-channel lineup, and AFAIK my SS has only ever gotten 7-8 days of guide info. I'm going to try your suggestions later tonight & I'll post my results.
-Susan |
|
| Back to top |
|
 |
Susan G Replay user

Joined: 07 Dec 2005 Posts: 74
|
Posted: Fri Aug 05, 2011 12:06 am Post subject: |
|
|
| Quote: | | I'd be interested in knowing what would happen if you were to go through the initial setup again. If that works, then this theory has more credibility. |
Hi Rich-
I changed the IP addresses for eth0 and the modem dial-in as you suggested -- in my case, to 192.168.0.201 and 192.168.0.210. My WiRNS PC is 192.168.0.100. This is with the VMWare Player in Bridged mode.
I changed the ZIP code to a valid one I'd never used before and connected to get phone numbers. That went very smoothly, and I was able to select my WiRNS lineup on the input screen.
I went ahead and did a Net Connect at that point, which I knew was a little foolish, since I hadn't rebooted. I wanted to see what would happen anyway, and sure enough the connection failed at "Transferring additional information...".
I then cleared the Channel Guide twice and tried a Net Connect again. That also failed.
Then I went into Setup. The SS said all or some of my setup info was no longer available, which I knew was a good sign! I entered another new ZIP Code, and this time after it got phone numbers I selected my provider again, selected Connect, and it went through getting Channel Guide data without a hitch.
It took about 20 minutes for 78 channels, which isn't bad at all. I forced a Net Connect again after scheduling a recording, and with one day's updated data it completed in about 7 minutes, which is great.
I'm pretty sure I could have avoided the failed connections by just clearing the Channel Guide twice after "Getting Phone Numbers..." and going back into Setup, but I did want to see both the "wrong" way and the "right" way after all my previous attempts. That might sound crazy, but now it makes sense to me.
BTW (to answer my own question in another thread ), I never had to go the "power down/unplug" reboot route.
I'm thrilled to finally have this working, and without your suggestions re Bridged mode, etc., I might well still be struggling with this!
Thank you so much!
-Susan |
|
| Back to top |
|
 |
amblinn Replay fan

Joined: 05 Jul 2011 Posts: 28 Location: SF Bay Area
|
Posted: Mon Aug 08, 2011 9:59 am Post subject: |
|
|
Back from vacation (and pleasantly surprised by the continuation of the ReplayTV service... not that I'm going back, though ).
Just wanted to add my $0.02 that I also switched over to bridged mode, and my download times have gone from about 20 min per day of guide data to about 2 min per day of guide data. Definitely much nicer. |
|
| Back to top |
|
 |
RichG Almost hooked
Joined: 28 Jul 2011 Posts: 6
|
Posted: Mon Aug 08, 2011 2:29 pm Post subject: |
|
|
| Quote: | Thanks for the clear explanation, Rich. I have a 78-channel lineup, and AFAIK my SS has only ever gotten 7-8 days of guide info. I'm going to try your suggestions later tonight & I'll post my results.
|
Went and reviewed the network traces again and you're right WiRNS: is sending 8 days of channel guide data to the SS. I thought I saw WiRNS advertise 14 days (or whatever number of days is specified in the Configuration-Guide Data setting) but sends the correct amount. This would explain why the % complete goes slowly to 23%, then jumps into updating the Zones info. The WiRNS guys can verify whether or not WiRNS is sending the 8 or 14 number (# days file size for vnd.replay.gz.)
In the words of Adrian Monk, "This is what happened:" WiRNS is sending Channel Guide data to the SSs in 1/2 MB bursts. This is fine for the network units (4000s,5000s), but problematic for the dial-up units. At best, the modems in these units are 300 TIMES SLOWER than a 10 mb/s home network. Freesco can hold 10K (default) of backlogged data before it has to throw away the overflow. Windows has a 75k buffer before it has to throw away the overflow. Obviously these 2 combined can not accommodate 1/2 MB of data. Both of these software packages have features (Window Full) to throttle the data from Wirns and prevent buffer overflow. Vmnet8 - the VMWare NAT pseudo-router is either dropping this message or passing it along too late and data corruption occurs. This data must be retransmitted until it gets through successfully (long download times) or the retry count is exhausted (what Susan and I were experiencing.) The other consequence of converting to bridge mode is the packet size adjustes down from 1K+ to the MTU of the modem. For my modem, 590 bytes with a 533 byte payload. This means that Freesco does not have to waste time repackaging the data.
All that this really means is that this solution is not configuration dependent -> it should improve downloads whether you ar running Freesco on th same machine as WiRNS or on a separate platform. Everyone should follow the old axiom "if it ain't broke, don't fix it," but if the download time are painfully long, you might want to try resetting your ReplayTV modem speed back to Default, and trying this approach.
Rich |
|
| Back to top |
|
 |
hdonzis Moderator

Joined: 05 Jan 2005 Posts: 7826 Location: San Antonio, TX
|
Posted: Mon Aug 08, 2011 2:42 pm Post subject: |
|
|
| RichG wrote: | | Quote: | Thanks for the clear explanation, Rich. I have a 78-channel lineup, and AFAIK my SS has only ever gotten 7-8 days of guide info. I'm going to try your suggestions later tonight & I'll post my results.
|
Went and reviewed the network traces again and you're right WiRNS: is sending 8 days of channel guide data to the SS. I thought I saw WiRNS advertise 14 days (or whatever number of days is specified in the Configuration-Guide Data setting) but sends the correct amount. This would explain why the % complete goes slowly to 23%, then jumps into updating the Zones info. The WiRNS guys can verify whether or not WiRNS is sending the 8 or 14 number (# days file size for vnd.replay.gz.) |
WiRNS doesn't send any number of days of guide data, the RTV requests the days that it wants. 4Ks and 5Ks ask for 12 days of guide data, and pre-4Ks ask for 8 days of guide data (I posted the RTV CG request algorithm here). WiRNS can load up to 14 days of guide data simply as an independent virtual RTV which has its own channel guide to view...
Henry _________________ Here's my Poop |
|
| Back to top |
|
 |
RichG Almost hooked
Joined: 28 Jul 2011 Posts: 6
|
Posted: Mon Aug 08, 2011 3:47 pm Post subject: |
|
|
| hdonzis wrote: | | RichG wrote: | | Quote: | Thanks for the clear explanation, Rich. I have a 78-channel lineup, and AFAIK my SS has only ever gotten 7-8 days of guide info. I'm going to try your suggestions later tonight & I'll post my results.
|
Went and reviewed the network traces again and you're right WiRNS: is sending 8 days of channel guide data to the SS. I thought I saw WiRNS advertise 14 days (or whatever number of days is specified in the Configuration-Guide Data setting) but sends the correct amount. This would explain why the % complete goes slowly to 23%, then jumps into updating the Zones info. The WiRNS guys can verify whether or not WiRNS is sending the 8 or 14 number (# days file size for vnd.replay.gz.) |
WiRNS doesn't send any number of days of guide data, the RTV requests the days that it wants. 4Ks and 5Ks ask for 12 days of guide data, and pre-4Ks ask for 8 days of guide data (I posted the RTV CG request algorithm here). WiRNS can load up to 14 days of guide data simply as an independent virtual RTV which has its own channel guide to view...
Henry |
Thanks Henry! |
|
| Back to top |
|
 |
Space Replay elitist

Joined: 18 Nov 2010 Posts: 479
|
Posted: Tue Aug 09, 2011 12:47 pm Post subject: |
|
|
Actually, I believe the 5Ks download/retain 13 days of data.
Here is the data my guide currently holds:
8/8 4:30pm - 8/21 8pm
So it actually has a little more than 13 days currently (including the prior days data). |
|
| Back to top |
|
 |
hdonzis Moderator

Joined: 05 Jan 2005 Posts: 7826 Location: San Antonio, TX
|
Posted: Tue Aug 09, 2011 12:57 pm Post subject: |
|
|
| Space wrote: | Actually, I believe the 5Ks download/retain 13 days of data.
Here is the data my guide currently holds:
8/8 4:30pm - 8/21 8pm
So it actually has a little more than 13 days currently (including the prior days data). |
It's all a matter of perspective. The pre-4Ks ask up to day 8 and the 4Ks/5Ks ask up to day 12. Today is the 9th, not the 8th, so the 21st is 12 days forward. The fact that it holds one day back may figure into "retains", but the people discussing this are asking about days forward, not days back. And, the 5K downloads 12 days and retains 13 days, it doesn't download/retain 13 days...
Henry _________________ Here's my Poop |
|
| Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|