CJfilms
08-07-2006, 03:17 PM
Wow, it's been a while huh?
The press release, Saturday night...
http://www.mountainspeedway.com/press/2006_results/8-5.htm
the press release, Sunday...
http://www.mountainspeedway.com/press/2006_results/8-6.htm
Photos...for both days of course!...
http://www.mountainspeedwayphotography.com/
Points...
http://www.mountainspeedway.com/press/2006_stats/8-5.htm
The give-a-ways from Saturday night...
http://www.mountainspeedway.com/press/2006_news/8-5gaw.htm
Mountain Madness...
http://www.mountainspeedway.com/press/mountain_madness/8-5.htm
The updated schedule...
http://www.mountainspeedway.com/events/
Be sure to check out the link on the press release pages to mylaps.com!!!
Also, I would like to note that I am working on registering the transponders with mylaps to make the lap times accessible online...I grabbed number 82, I think that Dean Gulick was the only one to have used it yet. I am having a problem though...if you are logged in, you can look at all the lap times. However, a common viewer not logged in can still NOT see the individual lap times, even for a registered unit... I will see what I can come up with to resolve this. Technically this would not be a problem if all the transponders were only used by the same people each week...which they do. The problem comes in with special events...NEETS races...and people who register at the beginning of the year and only race a few races. These chosen few would not be able to have access to the times unless they had a username and password to myaps.
I will work on this a little more, but I may have a solution already...
IF, IF!!!, I register all of the units, and GIVE the password to the crew who uses the transponder week to week, then you would be able to access the times.
If you haven't figured it out already... "Hey Joe, why not put a common password to every unit, like **mountain**"? Answer, I would like to, it would make things a heck of a lot easier! The problem is when someone doesn't like the points leader of a division, they may be tempted to upload a 'driver photo' of a horse's @$$ for that driver...or change info about the driver then change the password on the account. In the case of any of that happening, I would be left with no choice but to undo everything I have done and unregister all the transponders and close out all of the accounts.
That is something I don't want to have to do... This is how ONE person can ruin it for ALL. This is why I am trying to come up with an alternative.
The press release, Saturday night...
http://www.mountainspeedway.com/press/2006_results/8-5.htm
the press release, Sunday...
http://www.mountainspeedway.com/press/2006_results/8-6.htm
Photos...for both days of course!...
http://www.mountainspeedwayphotography.com/
Points...
http://www.mountainspeedway.com/press/2006_stats/8-5.htm
The give-a-ways from Saturday night...
http://www.mountainspeedway.com/press/2006_news/8-5gaw.htm
Mountain Madness...
http://www.mountainspeedway.com/press/mountain_madness/8-5.htm
The updated schedule...
http://www.mountainspeedway.com/events/
Be sure to check out the link on the press release pages to mylaps.com!!!
Also, I would like to note that I am working on registering the transponders with mylaps to make the lap times accessible online...I grabbed number 82, I think that Dean Gulick was the only one to have used it yet. I am having a problem though...if you are logged in, you can look at all the lap times. However, a common viewer not logged in can still NOT see the individual lap times, even for a registered unit... I will see what I can come up with to resolve this. Technically this would not be a problem if all the transponders were only used by the same people each week...which they do. The problem comes in with special events...NEETS races...and people who register at the beginning of the year and only race a few races. These chosen few would not be able to have access to the times unless they had a username and password to myaps.
I will work on this a little more, but I may have a solution already...
IF, IF!!!, I register all of the units, and GIVE the password to the crew who uses the transponder week to week, then you would be able to access the times.
If you haven't figured it out already... "Hey Joe, why not put a common password to every unit, like **mountain**"? Answer, I would like to, it would make things a heck of a lot easier! The problem is when someone doesn't like the points leader of a division, they may be tempted to upload a 'driver photo' of a horse's @$$ for that driver...or change info about the driver then change the password on the account. In the case of any of that happening, I would be left with no choice but to undo everything I have done and unregister all the transponders and close out all of the accounts.
That is something I don't want to have to do... This is how ONE person can ruin it for ALL. This is why I am trying to come up with an alternative.