RDSS MAJOR problems (resolved pending update)

[Ted Craven]

Folks, as of sometime this morning Monday February 19, 2018 - Several RDSS 2.1 users are reporting significant problems with all kinds of normal operations of RDSS.

The symptoms are simply - the 'non responding' message in the program header and the little 'wheel' spinning indicating that something is happening. This happens so frequently - for example in moving between Tabs, or selecting pacelines, even doing Downloads in the Data Centre - that RDSS V2.1.045 (and I suspect many other RDSS Versions) effectively grinds to a halt.

This appears to be related to specific Windows 10 versions, specifically so far - Windows 10 Version 1709, Build # 16299.xxx where xxx is a further 3 digit sub-build number which varies. I don't know if the problem is the 1709 update version, or the 16299 Build version, or what :confused:

While I drop everything to investigate this - could I please ask everyone who sees this and is having this problem to please post here (or send me by email) your current Windows 10 Version info. Here's how to find that.

Use the Search bar to type the program winver. This displays the Windows Version which looks like this (on my computer). We're interested in the red highlighted version info:

45514

My Windows version info is an earlier version than the one which several folks have reported using while experiencing the RDSS problem.

I am trying to find out which Windows Versions are responsible for the problem, and THEN try to find out how to solve the problem after doing some research.

I would be VERY interested in knowing if anyone using the older RDSS 2.0 also has the problem on Windows 10 Version 1709.

In the meanwhile, I can suggest that people try to roll back their Windows 10 Updates to a previous version to see if that solves the problem, and if so - WHICH version is still stable for RDSS. If you get a satisfactory solution, please report here (or by email to me) what eventually worked for you, with as much detail as possible - thank you!

Sorry about this latest problem. I am now working with a few people to do some testing with this system roll back attempt to (temporarily) correct things.

Please stay tuned.

Ted

[cratman]

Hi Ted,

1709

Also older version also had problem

[Lt1]

Ted I have windows 8.1 and have the problem
Tim

[rmath]

I am using Windows 7 Pro.

Dick

[JLG]

1709 (OS Build 16299.248) is mine, and I have the problem.

[JLG]

Checked Windows update, and its been over a week since I had an update, and RDSS worked fine just yesterday.

[Ted Craven]

I am using Windows 7 Pro.

Dick

And ... how's working for you?

Ted

[carl153]

version 1709 (os Build 16299.248) I have the problem

[Lt1]

Ted my last update was 2-14. There was 1 today at 1144am but well after problem surfaced.
Tim

[Ted Craven]

FWIW, I loaded up another computer (an old MS Surface 1) which had been updated to the current Windows 10 1709 16299.125. On that computer I can duplicate the reported problems in BOTH RDSS 2.1.045 and the older RDSS 2.06.

However as stated initially, on my other Win 10 Ver 1703 Surface 3 computer I continue to have NO problems.

I people are reporting that they have this problem on Windows versions earlier than Windows 10 (Win 8.1, Win 7) that's a whole new wrinkle. Can I get a re-confirmation please that the 'not responding' message, interminable 'wheel' icon appears when trying to do mostly ANYTHING in Rdss 2.1 occurs when using Win 8.1 and Win 7 or any Windows earlier than Win 10 Version 1709. If that's the case, then something OTHER than the Windows version is the culprit.

Anyone running RDSS on a Mac - could you please report your experience using any RDSS version - but please state specifically which WIndows version you are running on the Mac.

Thanks ...

Ted

[rmath]

All I get is a blank screen.
Tried to contact Trackmaster but no one is available today.
Had this problem off and on for several days now.

Might not be just a Windows 10 problem.
Dich

[Ted Craven]

All I get is a blank screen.
Tried to contact Trackmaster but no one is available today.
Had this problem off and on for several days now.

Might not be just a Windows 10 problem.
Dich

It may not be just a Windows 10 problem, but it's NOT a TrackMaster problem (because I can download file, and if you wait long enough, you can still download files from TrackMaster).

Everyone - please don't call TrackMaster about this: it's not their fault. I have called them to tell them the same thing and refer folks to this discussion.

Ted

[Bill V.]

Hi Ted
I just got home. I worked 3 races before I saw your message here.

So far I see no problems.


45516

[dlivery]

version 1703 (OS build 15063.909)
(Not Responding)

[carl153]

I downloaded SA yesterday. It works fine if I don't log on to the internet.

Carl

[rmath]

I tried not logging onto the internet but still only get a blank screen with a not responding message.
Rmath

[Ted Craven]

I downloaded SA yesterday. It works fine if I don't log on to the internet.

Carl

Carl - VERY INTERESTING! I confirm that if I unplug my RDSS non-functioning computer (my old Surface1) from the internet, things run smoothly again (so far, after 5 minutes of testing).

Could I get others to test this behaviour as well. Unplug or disconnect your computer form the internet. Please test you have successfully disconnected from the internet by opening your browser and trying to connect to a site: e.g. paceandcap.com or Google or whatever. (Please try that a few times to make sure you are not just fetching a page from your browser cache).

Then restart RDSS and see if the sluggish, non-responsive behaviour persists. I'll appreciate folks reports.

FWIW - RDSS does NOT check the internet every few seconds !! and you should be able to use it just fine without an internet connection.

But this might point me to look at new (though delayed) Windows Firewall settings, or something related ...

Ted

[Lt1]

Ted I'm confirming problem on windows 8.1.
Tim

[carl153]

I just downloaded 02/20 PRX and it's working fine.

Carl

[dlivery]

WiFi internet disconnected
Seems to of corrected the non responding issue

Lawrence

[JLG]

disconnected my WIFI on win 10 laptop using using RDSS, and that corrected the issue with the (not responding) problem.

[Ted Craven]

Debugging Update news (just posting all this as I discover it ...):

On one of my Win 10 computers which showed the problem -

I unplug the internet cable (literally a cable which connects the computer to my router) and I can move quickly and freely in RDSS, as normal. I confirm my browser has no connection to the internet.

I then plug the cable back in - now browser connects to internet again AND RDSS resumes its sluggish behaviour! No Internet connection - RDSS = fine. With Internet connection - RDSS slow and non-responsive. Even in the same session of RDSS, and with both new and old versions.

I would appreciate it if others experiencing today's problem would confirm that a disconnection from the internet (and test the disconnection please) - solves this problem. It would point in a particular direction.

Investigating further.

Ted

[Ted Craven]

disconnected my WIFI on win 10 laptop using using RDSS, and that corrected the issue with the (not responding) problem.

WiFi internet disconnected
Seems to of corrected the non responding issue

Lawrence

Thanks guys!

This suggests a TEMPORARY workaround:

- download from Trackmaster by waiting however long it takes to download files (i.e. you need the internet). In the Data Centre, check Download but uncheck Convert (you can do convert later when not connected to internet) Get your download cards.

- Then disconnect from the internet, uncheck Download and check Convert.

- While disconnected from the internet - do your handicapping.

Of course, this would be the method if you have not yet downloaded data for today. If you HAVE downloaded cards, simply disconnect from the internet and do your work.

IF you have multiple computers - you could disconnect ONE of them from the internet to do your work with RDSS and keep the other connected to watch races or place wagers with your ADW.

Just some quickie operational ideas while we work on the source of this problem ...

Ted

[Blueken555]

Hi Ted,

Windows 10 ver 1709 build 16299.248. Been an interesting day

Best
Ken

[Ted Craven]

Hi Ted,

Windows 10 ver 1709 build 16299.248. Been an interesting day

Best
Ken

You're telling me!! :eek: Ken, please let us know if the 'disconnect from the internet' trick temporarily works around this problem for you. A lot of fine races running today ... I know RDSS has a bead on many of them.

Ted

[Ted Craven]

Now focusing on checking the differences in Windows Firewall permission settings among my RDSS-working and RDSS-non-working computers.

Perhaps something there got changed this morning (by Gawd knows what 'universal' Microsoft update method ... :confused::confused:)

Ted

[Ted Craven]

Hi Ted
I just got home. I worked 3 races before I saw your message here.

So far I see no problems.


Thanks Bill! You're lucky! If need be, maybe later we can connect and squeeze out the differences in your Windows Firewall (or other :confused:) settings. You are obviously using the same Win 10 version as others who have this problem. Good luck today!

Ted

[The Pook]

Windows XP Pro 2002 on a Mac.

-Internet connected-Feb 19 is a blank. Nothing comes up after downloading and converting. Previous days and Feb 20 work fine. Both old and new versions of RDSS.

-Internet NOT connected all dates work, but slowly. Both old and new versions of RDSS.

Pook

[Ted Craven]

Windows XP Pro 2002 on a Mac.

-Internet connected-Feb 19 is a blank. Nothing comes up after downloading and converting. Previous days and Feb 20 work fine. Both old and new versions of RDSS.

-Internet NOT connected all dates work, but slowly. Both old and new versions of RDSS.

Pook

Thanks Pook. So - with internet disconnected, RDSS works but more slowly than usual, in your observation. Correct?

FWIW - several more private reports that with internet disconnected (using Win 10 on PC) RDSS runs apparently as fast as before this problem.

Narrowing the focus. (Need more coffee ... ;) )

Ted

[The Pook]

Yes. By slow, I mean slow. Sometimes selecting another pace line will take over 30 seconds.

Pook

[gentz]

windows 10......... 1709......build 16299.248
unresponsive

[rmath]

When I disconnected from the internet everything worked fine.
As soon as I reconnected the problem came back.
rmath

[Lt1]

I turned computer off and restarted. Opened RDSS without going on to internet but problem still persist. Running windows 8.1 on HP Pavilon 15.
Tim

[zimal2]

Using Win 7. Same problem....ok if turn off internet.
Zim

[Ted Craven]

I turned computer off and restarted. Opened RDSS without going on to internet but problem still persist. Running windows 8.1 on HP Pavilon 15.
Tim

Tim, how do you know you are not connected to the internet? Did you turn some network connection setting off? Did you test you were not connected to the internet by opening your browser and trying to connect to different websites?

My suspicion is that even if you did not use your browser to go to a website, you are still connected to the internet - and thus have the same problems we're discussing.

Ted

[Ted Craven]

Using Win 7. Same problem....ok if turn off internet.
Zim

Thanks Zim.

Ted

[fastcharlie55]

Folks, as of sometime this morning Monday February 19, 2018 - Several RDSS 2.1 users are reporting significant problems with all kinds of normal operations of RDSS.

The symptoms are simply - the 'non responding' message in the program header and the little 'wheel' spinning indicating that something is happening. This happens so frequently - for example in moving between Tabs, or selecting pacelines, even doing Downloads in the Data Centre - that RDSS V2.1.045 (and I suspect many other RDSS Versions) effectively grinds to a halt.

This appears to be related to specific Windows 10 versions, specifically so far - Windows 10 Version 1709, Build # 16299.xxx where xxx is a further 3 digit sub-build number which varies. I don't know if the problem is the 1709 update version, or the 16299 Build version, or what :confused:

While I drop everything to investigate this - could I please ask everyone who sees this and is having this problem to please post here (or send me by email) your current Windows 10 Version info. Here's how to find that.

Use the Search bar to type the program winver. This displays the Windows Version which looks like this (on my computer). We're interested in the red highlighted version info:

45514

My Windows version info is an earlier version than the one which several folks have reported using while experiencing the RDSS problem.

I am trying to find out which Windows Versions are responsible for the problem, and THEN try to find out how to solve the problem after doing some research.

I would be VERY interested in knowing if anyone using the older RDSS 2.0 also has the problem on Windows 10 Version 1709.

In the meanwhile, I can suggest that people try to roll back their Windows 10 Updates to a previous version to see if that solves the problem, and if so - WHICH version is still stable for RDSS. If you get a satisfactory solution, please report here (or by email to me) what eventually worked for you, with as much detail as possible - thank you!

Sorry about this latest problem. I am now working with a few people to do some testing with this system roll back attempt to (temporarily) correct things.

Please stay tuned.

Ted
Did not download todays card from gulfstream,but have the card for the 21st and it is running fine. v1709 build16299.248

[Ted Craven]

Thanks Charlie. So - it has nothing to do with Windows Version. Everything to do with some setting (newly changed today) other than Windows version.

I'm checking:

- Windows Defender (firewall) - turning it OFF (not recommended): no effect.

- no other security anti-virus or malware software installed.

- explicitly adding RDSS2.EXE to Apps permitted through the Windows Firewall - no effect (and previously not required).

Only thing that works so far is:

-disconnect the computer from the Internet.

That said, I still have 2 computers which work fine. Not sure what's different about them ...

I am about to compose a message to Microsoft Tech support Forum, describing the behaviour and what's been tried so far: https://answers.microsoft.com/en-us/

Ted

[dlivery]

Ditto - disconnect the computer from the Internet.
No outside interference

[ignacio todoberto bernal]

hi chief! here is mywinver 1709 osbuilt16229.15

[ginag2]

I'm having problems described - just starting today.

I have Win7 home pro 64bit / winver 6.1 build 7601

- Gary

[Ted Craven]

hi chief! here is mywinver 1709 osbuilt16229.15

And ... do you have any problems?

Ted

[Ted Craven]

I'm having problems described - just starting today.

I have Win7 home pro 64bit / winver 6.1 build 7601

- Gary

Thanks Gary.

Ted

[Ted Craven]

Did not download todays card from gulfstream,but have the card for the 21st and it is running fine. v1709 build16299.248

Charlie, taking a closer look at this - I hear you saying that tomorrow's (or future) cards show NO problems. Can you confirm that Yesterday (or previous) also show no problems?

If YES to both above questions, could I ask you to download a card for today to check that only CURRENT DAY cards cause a problem? You can ask Trackmaster for a refund (info@trackmaster.com) and I've already given them a heads-up to all this.

If there is some kind of problem with current day cards, it would be a good test to try it out with NO current day cards downloaded. Though - others who DO have current day (Monday Feb 19) cards downloaded could also try this same test.

Maybe RDSS is accessing some 'ancient' URL for current day cards which stopped existing as of mid-morning this morning :confused: If that's the case, at the moment I have no memory of that, but I am scouring the software source code ...

Thanks!

Ted

[ginag2]

I can confirm that my system also works at speed when offline. While connected, it will finally complete an action after 20 or 30 seconds - each new action - same delay. If I try to connect through to TwinSpires, it completely freezes the program and necessitates a re-boot.

- Gary

[Bill Lyster]

Ted:

Windows 10 , 1709, OS build 16299.248

Very slow access to tracks, PPs, individual lines. 30-40 seconds per activity.

The good news is that I got closed out of a couple of losing races:)

[fastcharlie55]

Have you tried to reboot and load another file other than 02/19

[tizlinda]

Confirming same issue on windows 7 and 10. Works fine offline. Older cards do NOT work online, only offline.

[fastcharlie55]

I'm running the same version as you and did a reboot and loaded a different date other than 02/19 and it works fine. I downloaded 02/19 and the problem showed up so I did a reboot and came back up and all my files are fine except 02/19

[SCSAYS]

Ted, I also have the same problem .Currently running RDSS on windows XP Home Edition Version 2002 service Pack 3.

[Ted Craven]

Folks, thanks to several of you who reported aspects of how this problem presented to you and several ideas to follow up on - here is the answer to the problem and both the Short Term temporary solution and the Final full solution.

The Problem - is caused because ever since RDSS 2.06 (May 2014) and all the way up to the current RDSS 2.1.045 - even if you did not choose to connect to SuperTote to get tote info, for CURRENT DAY (today) cards, RDSS was reaching out anyway to a Brisnet.com address to see if tote info was available for a given track. It should NOT have done this (and I blame the programmer :eek::o) if you didn't login to Supertote first. It appears that this morning Feb 19, 2018, that old Brisnet Supertote address was finally decomissioned, since they have moved to a NEW version of tote and race day info. Before today, when RDSS hit that old address, it failed gracefully. Today, it failed HARD, and the RDSS internet access component simply ended up waiting 45 - 60 seconds to learn that there was no such address anymore. And then tried again, and again ... That's why it was taking forever to do anything.

The Short-term Solution. (Please see this post below (http://paceandcap.com/forums/showpost.php?p=114294&postcount=59) for a possibly improved workaround).

1. Set your computer date to a Future date where you have no cards downloaded but where you can still download the actual cards you want. For example, to download tomorrow Tuesday Feb 20, set your computer Date to Feb 21. Restart RDSS and download the cards for Yesterday (because when RDSS thinks Today is Feb 21, cards for Feb 20 will be Yesterday).

2. Handicap the races with the computer date still set to a future date where you have no cards (important, because if you work on a card which RDSS thinks is TODAY - even if that TODAY is in the actual Future - it will try unsuccessfully forever to get tote data for it). OR --

3. Once you have the cards Downloaded (and Converted), you can disconnect from the Internet and set the date back to today's correct date. If you are disconnected from the Internet , you can use RDSS normally to handicap Today's races.

4. If you have 2 computers, you can have one disconnected from the Internet to do your current day RDSS handicapping, and the other to watch odds and place wagers with your ADW.

5. If you have 1 computer, disconnect from the Internet and do your current day RDSS handicapping, then close RDSS, reconnect to the Internet and place your wagers with your ADW.

I know - that's a terrible workaround :mad:, but it seems to BE a workaround until ...

The Final Solution. I was getting close to releasing an update to RDSS 2.1 within a few days anyway which has solved the above described problem (that's why I was not experiencing the problem on 2 of my 4 computers - they had a newer testing version :o).

Within the next 48 hours maximum, I will polish that RDSS 2.1 update sufficiently that I can release it in general - and also release the entire RDSS 2.1 to the general user base (the remaining ~30% or so who are not already using RDSS 2.1). That's because the old RDSS 2.06 is now 'toast' because it can't (won't) be updated to fix today's bug.

I will report here and by general email to all current RDSS users when the next release of V2.1 is available, which fixes today's bug AND reinstates tote access. That update should be BEFORE Thursday Feb 22.

I am sorry that this has happened today - my apologies to everyone affected. I really think folks will like the tote module renovation - and those of you who have NOT tried RDSS 2.1 - you'll like that too, better than the previous version.

Thanks,

Ted

[SCSAYS]

Ted, NO apologies needed.Your dedication and continuance to the Sartin Methodology is a gift to all members. We owe you a debt of gratitude.

[ignacio todoberto bernal]

And ... do you have any problems?

Ted yes same

[ginag2]

Thanks for burning the midnight oil Ted - very much appreciated. - Gary

[ram]

Hi Ted, am having the same problem reported here, ie: "program not responding" message, interminable loading time from one race to the other, or from one screen to the other, freezing up, and having to use ctrl alt del to get out of the program. Am using win 8.1. I initially thought it was a problem with the computer, and uninstalled RDSS a couple of times, 2nd. time shut off the firewall, ran as administrator etc., did some program to try to restore to an earlier date, (just succeeded in wiping out a few other programs including printer driver} no luck. Will try to reinstall RDSS, and use it off the internet and see what happens. Let you know, Rich

[ram]

hi ted, had downloaded a card for today at TuP, tried working it while on the internet, same problems pretty much, as yesterday. Exited RDSS, shut off internet connection, went back into RDSS, worked TuP, and the program seems to run fine. Hope this helps. Rich

[Ted Craven]

hi ted, had downloaded a card for today at TuP, tried working it while on the internet, same problems pretty much, as yesterday. Exited RDSS, shut off internet connection, went back into RDSS, worked TuP, and the program seems to run fine. Hope this helps. Rich

Rich, glad that worked for you! Thanks for reporting in.

Ted

[Bill Lyster]

Changing the date worked for me. It took a while to change the date, but now my computer is two days ahead.

After changing the date I was able to work yesterday's cards while on the internet last night and again this morning.

When I opened RDSS all I did was go back to 2/20 races and the assembly and handicapping went off witout a hitch.

[Ted Craven]

Folks, despite what I wrote above regarding a short-term workaround solution (change dates, disconnect from internet) - it seems there may be a simpler way for the time being:

When connected to the Internet, load RDSS and immediately go to the Data Centre and download/convert the tracks you're interested in: today, tomorrow, yesterday, whatever. Do NOT open any card for Today before you at least Download what you need.

Then disconnect from the Internet.

Then proceed to do whatever handicapping you need to in RDSS.

The important nuance for this 'improved' (?) workaround is to NOT open a card BEFORE you Download data from TrackMaster. Once you open a card, you will (may) experience the lengthy slow-downs and non-responsiveness which has been described.

So Download first, disconnect from the Internet, then proceed to handicap races. I have tested this using RDSS V2.1.045 (the latest available in the Testing Forum).

That said - for whatever reason this morning - I am NOT experiencing any slow downs using RDSS 2.1.045 when connected to the Internet (i.e. the opposite of what has been the entire fiasco yesterday :eek:). Your mileage may vary. If you DO experience repeated slow-downs today using RDSS, follow the guidelines in this post.

More to come ...!

Ted

[Ted Craven]

Ongoing saga ...

The problem seems to have gone away today. It seems you can use RDSS as normal!

It appears that Brisnet (TwinSpires) made a change since yesterday such that the out-dated Supertote weblink RDSS was mistakenly hitting - and failing poorly such that it tied up processing forever - now fails more gracefully today and DOES NOT tie up RDSS forever.

Please everyone test this by simply ignoring all workaround advice given above and using RDSS as normal. Stay connected to the internet as you normally would while using RDSS.

That said - I will still proceed with an update in the next few days, as this could change again with no notice.

Feedback is appreciated!

Ted

[ginag2]

Ted - Just ran a race on Prx card - all worked as normal - including PL and prices capture via Twinspires.

Thanks - gary

[SCSAYS]

Ted no issues today. RDSS is working flawlessly. Ran race cards from MVR PRX SUN for FEB 20 .

[Lt1]

Hi Ted just downloaded Parx 2-20 card. Everything working well so far.Thanks for all your hard work.
Tim

[Ted Craven]

Thanks guys! Still moving forward testing that update.

Ted

[agomez]

Hi Ted: I faced that problem yesterday and I thought it was lack of memory in the program, so I created a new data file, downloaded a new file and it ran well. Anyway all day was very troublesome. My windows version is 1709.

Best regards
Antonio

[DaveEdwards]

Hi Ted,

1709 here.

I'm a bit late into this as I've been a little busy the last few days. Downloaded a few cards yesterday and all seemed fine.

[Blueken555]

Hi Ted,

Everything back to normal

Best
Ken

[Bill Lyster]

All is well here RDSS wise, but in the last couple of days I see this about once a card?? Any idea what the big red X is all about? Is it the magic gold entry to Willy Wonkas?

45539

It also occurred at TAM and TUP, one race only, but different races each track.

[Ted Craven]

All is well here RDSS wise, but in the last couple of days I see this about once a card?? Any idea what the big red X is all about? Is it the magic gold entry to Willy Wonkas? ;)

It also occurred at TAM and TUP, one race only, but different races each track.

Pay no attention to the red X (and it is gone after V2.1.045). An experiment, abandoned, not intended for a public version :o

Cheers,

Ted

[rmath]

I ran several cards yesterday and had no problems (yet).
Bil I get that red x on several cards each day.
It is almost always on just one race per card.
Have no idea what it means.

rmath

[The Pook]

Ted,

Today, Feb 21, all horses are listed as Profit Line rank 1. Yesterday was fine.

Pook

[rmath]

Pook, Same thing here.
I sent a picture of this to Ted.

rmath

[Ted Craven]

Re Profitline - indeed! I can duplicate that.

Another case of (in this case) TwinSpires changing web link of how RDSS fetches ProfitLine info. Thus, ProfitLine is down until I can fix that. :(

If I can fix it for an update tomorrow, I will. If it will take longer than that to fix and test - it will have to wait until a subsequent update (a few more weeks). If that's the case, no ProfitLine until then ...

And until then, I recommend just avoiding fetching ProfitLine and having every horse with a rank 1.

To clear any bad ProfitLine data from today -- go to your File System, RDSS2.1\Data\ProfitLine\2018\ folder - look for today's date folder and delete it.

I'll see what's what with fixing that ProfitLine retrieval, if it's quick.

Ted

[Ted Craven]

On further investigation - looks like ProfitLine is working normally now.

Please try this:

- login to TwinSpires and fetch ProfitLine for a card (on the card summary screen)

- re-assemble a race (if you have previously assembled it and gotten bad ProfitLine numbers). If it's a fresh race, just Assemble it.

- see how the ProfitLine numbers look.

I just tried several cards from today and got normal ProfitLine readouts:

45540

I also checked the web links RDSS uses to fetch ProfitLine data and those links are still valid and also work when I cut and paste them into a browser.

So -- the only thing I can conclude at the moment is that there was a temporary glitch at TwinSpires this morning, which is now fixed and back to normal. In fact, there's nothing for me to do, nothing to change.

Please let me know if you all agree.

Ted

[Lt1]

Ted my profit line is now correct. FYI this is 3rd day I encountered this problem. The other 2 days PL went back to normal in about 1/2 hr of my signing in and out.
Tim

[Ted Craven]

Ted my profit line is now correct. FYI this is 3rd day I encountered this problem. The other 2 days PL went back to normal in about 1/2 hr of my signing in and out.
Tim

Noted! Not sure why. But soon - not the next update in a day or so, but the one after that in March, we'll get ProfitLine a different way and it should all be easier.

In the meanwhile, we may find ourselves watching ProfitLine for 'normalcy' (if you use ProfitLine at all), and if abnormal, refetch it, reassemble races.

Thanks for checking Tim!

Ted

[ram]

Ted, I'd like to agree with the others who have already posted that no apologies are necessary. THANK YOU for all you do for us! tich

[rmath]

Everything is back to normal.

Rmath

[OldPR65]

Running RDSS V2.1.033 (8/26/16) along with Windows 1709.16299.248 and have no issues.

[Ted Craven]

Running RDSS V2.1.033 (8/26/16) along with Windows 1709.16299.248 and have no issues.

Thanks OldPR! Still working on the RDSS 2.1 update - testing a few things in the next couple of days. Will report back soon re the update!

Glad things are working well in the meantime.

Ted

[poweshow]

Is there a chance we get the release before the weekend? I would absolute hate for these problems to pop up again during the weekend when I'm seriously playing and wagering hundreds of dollars. At the least perhaps we could get the release and keep the old version around so we can jump to the other if either goes down.

[Ted Craven]

Is there a chance we get the release before the weekend? I would absolute hate for these problems to pop up again during the weekend when I'm seriously playing and wagering hundreds of dollars. At the least perhaps we could get the release and keep the old version around so we can jump to the other if either goes down.

There are a couple of issues in testing which are important enough that I resolve them before releasing an update broadly (scratch reporting, sorting). I hope I can release something for this weekend, but there's a chance I might miss that.

If I had to bet, I'd bet that the single issue which interrupted RDSS last Monday will not recur immediately (outdated Brisnet URL hit failed badly rather than gracefully). That event was much more uncommon than common. For example, just try typing in your browser: www.rdss2.com/thisisabadURL (http://www.rdss2.com/thisisabadURL) (or www.google.com/thislinkdoesnotexist (http://www.google.com/thislinkdoesnotexist)) - you will at least get an immediate failure notice, which RDSS would be able to handle no problem. The Monday problem was because the failure notice took a long time to come back, which is not normal, which was fixed by Brisnet on Tuesday. (And RDSS should not be hitting that old Brisnet Supertote link, which is among the changes to the forthcoming update).

Anyway - I hope that gives a bit of confidence that perhaps we have a few more days to get a new update which will not have unacceptable bugs. I absolutely agree though with you that it would be a shame to lose ANY more time being able to use RDSS profitably, which is why I am releasing an update rather earlier than I otherwise had planned to.

Ted

[Dorianmode]

Maybe it's all resolved now ... but I have :
1709 (OS Build 16299.248),
and have had no problems this week, and it's working now.
I know it was fine on Thursday 2/22 for me also.

I have no problems ... :rolleyes:

[Ted Craven]

Maybe it's all resolved now ... but I have :
1709 (OS Build 16299.248),
and have had no problems this week, and it's working now.
I know it was fine on Thursday 2/22 for me also.

I have no problems ... :rolleyes:

Thanks Doc! Yes, looks like back in order now, but still working feverishly to get an update. Looks like next week, by now ...

Ted

[poweshow]

Please tell me with March here and big-time prep races beginning we're going to have our tote back. We desperately need this live tote back, absolutely desperately.

[Jeebs]

Please tell me with March here and big-time prep races beginning we're going to have our tote back. We desperately need this live tote back, absolutely desperately.

Poweshow,

Ted would be doing a great disservice to the group by releasing an RDSS version that was littered with bugs, generated incomplete or incorrect information, or locked up/froze up. All of which could have adverse effect on your bankroll. Even though the current release can't support tote, and going back and forth between RDSS and an ADW is inconvenient, I think you would agree that it's better than nothing and at least the data is accurate and stable.

Ted is going about this the right way. It is probably a blessing that the bug from a few weeks ago didn't persist, as it may have rushed a not quite ready for prime time release to us just to avoid that bug. Since it was a one time fluke, it bought time enough to bring this closer to perfection.

Thank you Ted for all you do!

[Ted Craven]

Please tell me with March here and big-time prep races beginning we're going to have our tote back. We desperately need this live tote back, absolutely desperately.

Poweshow - I hear and accept the urgency of your plea! Yes, absolutely the tote will return very shortly. This weekend is a big one for testing the remaining few items of what will be a 2-part update. First, next week, the previously existing tote functionality returns, along with a number of other enhancements to V2.1. Next, in March, the remainder of the tote and new race-day info from the new tote system (all Scratches/Changes, mutuels, ProfitLine, auto-export to modeling), along with long overdue secure access to TrackMaster downloads (HTTPS).

Got to get it right (enough) at each software release stage that any bugs I missed don't stop folks dead in their tracks :eek:.

A tip of the hat to my (anonymous) long suffering early testers ... :D

Ted

[rdiam]

I completely agree with Jeebs. Ted's efforts should not be underestimated. Patience is a virtue.

[poweshow]

I hate how patient and correct you guys are all the time... it's disgusting. Perhaps one of you fine gentlemen can teach me some patience someday, especially on the track.

Thanks y'all

[The Pook]

Ted

Profitline is not downloading again. I am not prompted to log in to Twinspires as usual. Yet the red dots show up saying Profitline is downloaded. I am not using the latest update. I am using the one from last November. Has the connection expired and is now working in the new format you keep promising?

Pook

[Ted Craven]

Pook, it looks and acts normal today for me.

45854

If you see the 'red dots' on a Card Summary screen it means a ProfitLine file of data was downloaded for this track today. Look for it in the Folder (for example): C:\Rdss2.1\Data\ProfitLine\2018\20180314\ TAM today would be file: 20180314-TAM.htm

If that file is there (because the 'red dots' are there) - it means somehow you downloaded ProfitLine for that track today. So far, nothing happens without the user manually requesting PL figs and logging in to TwinSpires, and certainly not in the old versions.

Any other ideas?

Ted

[The Pook]

Those files are in the folder but contain 0kb. Like I said normally when I hit the Profitline button in the summary screen I am prompted to login to Twin spires. When I do that I go back to the summary screen and hit the button again. There is a small wait while the red dots appear. Then when I assemble a race the PL horses are shown along with all scratches.

Today when I hit the Profit Line button there is no login screen and the red dots indicating PL etc. immediately light up. But the are no PL listings and no scratches.

That is why I was wondering whether this new connection method that you have been writing about has kicked in leaving the old one useless.

Pook

[Ted Craven]

The 'new connection method' relates only to TrackMaster, not to TwinSpires.

Can you login to TS via the button on the RDSS Desktop? Are the UID and PWD for TwinSpires stored and presented in RDSS on the 'Please Login' RDSS page still correct? Can you login to TS outside of RDSS in your browser with the same UID/PWD?

It seems somehow you are not able to login to TS. RDSS is incorrectly thinking you have, and downloads en empty file.

Ted

[The Pook]

Says it can’t find the server. I download from Trackmaster okay. Outside of the RDSS browser I get in to TS fine. But from within RDSS no dice.

Pook

[fastcharlie55]

Online now working fine

[Ted Craven]

Says it can’t find the server. I download from Trackmaster okay. Outside of the RDSS browser I get in to TS fine. But from within RDSS no dice.

Pook

Remind me - you're using Windows XP within Mac OS? Any chance that Windows version got updated in the last while since things were working OK for you? I can think of one setting (in the Windows Registry) which RDSS watches out for to permit its internet access from being blocked by some websites requiring secure access - TwinSpires has been among those.

We'd have to troll among settings in your Registry since RDSS seems unable to do that job itself - to see what a particular setting is and then reset it. If you want to, let's do that by email then a phone call, just let me know.

But those and other old oddities are why I am upgrading the internet access components in the next update - which should do away with issues like that (if indeed what I have described is what is causing the problem). For TrackMaster access, but also for all other authenticated and non-authenticated web sites access (perhaps including TwinSpires).

Let me know.

Ted

[The Pook]

Ted

I don’t know of any updates or changes since yesterday when everything was fine. Parallels sometimes updates on its own but has been no notification recently. Weird. PM me with things I can look for in the registry.

Pook

[dogkatcher]

Try loading from the Entries screen. Longshots sometimes win.

[Ted Craven]

This issue is resolved by the update: RDSS 2.1.048 and subsequent. Please report any RDSS 2.1 Bugs to the Bugs List, here: http://paceandcap.com/forums/showthread.php?t=10575

Closing this thread.

Ted