Play To Win
There are 4 tournaments now open for play totaling 150,062,400 community points amounting to USD $15,006.24 for prizes in our shop.
Recent Winner
Navigation
Poll
Fun Horse Names for Our Thoroughbred Born on January 1st - He's Going to the Kentucky Derby. What name should this horse have?
Born First Run First - Perfect name for a horse we expect to win a lot of stake races
6%
Happy New Year Baby - With all the money this horse will earn, it's going to be a great racing year!
3%
Follow Your Elders - Born before the other horses, this is a perfect name for a leader on his way to the Triple Crown.
8%
Can Run From Day One - Born early and ready to race. Bring on the bed of roses!
19%
January's First - This guy will be first on that First Saturday in May when he crosses the finish line for the Kentucky Derby.
64%
Total votes: 36
- Login or download our free game to post comments
- Older polls
HRFAN.exe error
Posted on: Wed, 10/01/2008 - 10:50am
HRFAN.exe error
There is a problem that I can reproduce pretty regularly on my machine. It involves setting up a race and changing the track condition. Often when I try HRFAN.EXE errors out. I can sometimes change track condition two or three times successfully and race, but when it does eventually error out it then errors out numerous times in succession.
Is this a known issue, planned to be fixed, or is it unique to me?
Tournament Schedule
Featured VIP Member
Newest Forum Topics
Most Active Topics
Horse Racing Totals
Last 20 Days
Total Horse Races: 2,463,995
Total Jockey Races: 657,188
Total Bettor Races: 339,206
Recently Active Members
There are currently 27 users and 38 guests online.
Comments
I don't believe I've ever seen this on my computer.
I get this message 25% of the time, very frustrating.
If one of the support team wants to remote in to my computer and see, I am cool with that. Or, I can send you the text of the error report it generates.
Hopefully the new version of the game will fix this error. Errors that are not consistent have been low priority. I'm not trying to make excuses, but the team is so focused on the new build. If we cannot get this fixed through the new build, once things settle down, we'll focus on it. One thing that comes to mind is that sometimes the program doesn't process as fast as the computer, thus bringing back the result that you're getting. Since it's a bug that's not consistent, it definitely has something to do with processing. Again, we will get to it if the new build doesn't fix it. We feel your pain!
It's nothing to just OK the error, then start the program again. It is more of an annoyance than anything. But there are workarounds. I was just thinking if it's a widespread thing, I could give you some data on it.
I'm not really complaining here. If the new upgrade is as cool as it sounds, I will complain even less =)
I have also gotten this message before, not as much as some other people though, but it gets kind of annoying.