RaceVIEW Pinewood Derby Manager Update History

RaceVIEW Update History

This page contains a brief description of the updates which have been issued since RaceVIEW was commercially released. They are listed in reverse chronological order, starting with the most recent update. The information for the most recent update is also available on the Updates Page .

Each updater contains all of the prior updates since the last major release. Therefore, you do NOT need to download and install all of the updates. Rather, simply download and install the latest update.

I intend to inform RaceVIEW users of significant changes, at least in terms of functionality, made to the product through this page and various updater README files.

Minor maintenance upgrades are distributed via the Updates Page at no cost.

Update History
Update v1.6.5 12/1/07	This update will update any version of RaceVIEW to the latest version. You do NOT need to apply any of the previous updaters. The purpose of this update was to add support for the timers from Affordable Pinewood.
Update v1.6.4 3/18/06	This update will update any version of RaceVIEW to the latest version. You do NOT need to apply any of the previous updaters. The purpose of this update was to fix a problem with the DT8000 interface.
Update v1.6.3 1/18/05	This update is mainly focused on usability issues and addresses a number of our more common support questions. Specifically, I added on-screen instructions to the program registration screen. Another significant change was the addition of an "Abort Derby..." button on screens that are normally viewed during Derby execution. A number of users over the years have requested this functionality. Added a new check for interrupted Derbies. Now, when RaceVIEW checks for interrupted status, it not only checks for presence of the log file but also checks to see if one or more interrupted Derbies actually exist. Previously, you may have interrupted a Derby, then deleted its results and RaceVIEW would still think an interruption had occurred.
Update v1.6.2 12/21/04	This update adds a new "RaceVIEW User Manual.doc" which supersedes and replaces "RaceVIEW Instructions.doc". The original User Mnaual was woefully inadequate and far behind the software. I think you will find the new manual useful and very thorough. It also removes the telephone number for RaceVIEW (which was incorrect) from the splash screen and the About screen. Please refer to www.raceview.com for the latest contact information. The Test a Timer screen was rearranged to make the operations clearer. Also, on-screen, step-by-step instructions were added. This should eliminate all confusion about how to use this panel. Updates any version of RaceVIEW from 1.4.6 to 1.6.1 to the new version 1.6.2. You do NOT need to apply any of the previous updaters.
Update v1.6.1 3/15/03	This update fixes a bug which prevented RaceVIEW from using COM3 and COM4. Unlike previous updates, this one will only update v1.6.0.
Update v1.6.0 3/11/2001	This update fixes a bug which prevented RaceVIEW from recognizing the DT8000 timer in the new Timer Test panel. All DT8000 users should install this upgrade. Also, fixed a bug in the recall of Derby division information in the new Registration panel.
Update v1.5.9 3/10/2001	I received some great feedback from users immediately after releasing Version 1.5.7. I missed a number of things, which Update 1.5.8 and 1.5.9 fix. A number of changes were made in the Derby Definition Panel. The most significant change was: If editing an existing Derby, the pertinent settings, such as Division Names and Finalists/Div stored in the *.div (Derby Setup) is now read back so that your settings are not reset to the defaults. Registration Entry Changes: 1) Appearance of the Registration panel was fixed, including removal of the scroll bars and disabling user closing of the window. 2) Added on-line help to all the panel controls and indicators. 3) The information from an existing registration file is read, if you are editing an existing derby. The only exception is the "Racing?" column, which is always set to "Y" for all racers (this can be changed for each racer within RaceVIEW on race day as each division is run). The grayed out buttons on the RaceVIEW Main Panel caused some confusion. These buttons are for features that are not currently available. The on-line help for these buttons was updated to indicate this. See the Update159-README file for additional details of the changes made in this release.
Update v1.5.8 3/9/2001	This update fixes a bug which caused loss of cars numbers when editing a previously created Derby using the new Derby Registration panel from v1.5.7.
Update v1.5.7 3/3/2001	This update adds the ability to create Derby registration and division setup internal to RaceVIEW and automated timer model detection and timer testing. The Main Panel was modified to give access to these new features. The main panel buttons were reorganized to provide visual cueing as to the order of the processes in setting up and running a Derby. Also, added the ability to delete Derby results files. With these additions, the end user will not have to use any external programs, including Windows Explorer, to setup or to remove derby data files! Also, the built-in timer test panel should remove the only other significant problem that users have had in getting ready for a Derby; that is checking out the timer-RaceVIEW interface.
Update v1.5.6 2/1/2001	This update fixes the printing of long lane assignment lists. Previously, RaceVIEW only printed up to 16 races. Now, for long lists, it prints all lane assignments, 32 per page on as many pages as necessary. Added optional print of Leader Board (only top 24). Please note that we DO NOT recommend using divisions with such large lane assignment tables. You should seriously consider dividing into smaller divisions for a fairer race. This update was written in Oct, 2000, but not released until 2/1/2001.
Update v1.5.5 8/8/1999	This update adds support for the DT8000 finish line from Newbold Products.
Update v1.5.4 2/6/1999	This update fixes a bug reported by Win98 users regarding registration number not displaying oin Race Display. Some indicators had a Macintosh font (Helvetica) specified. This was fixed by changing all instances of "Helvetica" to "Arial". Helvetica is not available on PC. Caused missing Car number digits ("1's) under Win98 if Smooth Fonts was turned ON.
Update v1.5.3 1/23/1999	This update fixes a bug reported by users who number cars with less than 3 digits. RaceVIEW has allowed this for some time, but few users have taken advantage of this feature. There was a bug in the code which only affected the Finalists which RaceVIEW adds to the registration file.
Update v1.5.2 1/10/1999	This update fixes the "Error 37" bug introduced in Version 1.5.1 and adds abort during a race for Fast Track timers.
Update v1.5.1 12/12/98	Another fix for the "Judge" interface. I'm not going to claim it to be the last this time! A couple of users had found an error condition caused when the starting gate was left open. RaceVIEW now warns you of this condition, without aborting the Derby. If you are using the "Judge", please provide feedback (good or bad)!
Update v1.5.0 3/19/98	Fixed "Judge" interface, added Abort at Race level (no more CTL-ALT-DEL !!), and more.
Update v1.4.9 1/20/97	Updates any version of RaceVIEW from 1.4.6 through 1.4.8 to Version 1.4.9 Made scrollbar on Display Round Assignment table (for more than 15 races) accessible. Print Round Assigment no longer displays its panel. Also fixed cosmetics on this screen; namely centering of titles. Made Up Arrow on scrollbar on Registration Entry table accessible.
Update v1.4.8 1/19/97	Updates Ver 1.4.6 or 1.4.7 to Ver 1.4.8 Well, I thought I had this one fixed with the 1.4.7 fix, but Mark Risner found another problem with the Judge interface. I hope this is the last one!
Update from 1.4.6 to v1.4.7 (Obsolete)	This update is essential for all installations using RaceVIEW with the "Judge" from New Directions. This patch fixes a bug which results in erroneous readings from the Judge. My thanks to Sam Joseph of Cub Scout Pack 475 in Oldsmar FL who not only reported, but patiently helped me to debug, this problem. Thanks for your help, Sam!
Update from 1.4.x to v1.4.4	I wasn't keeping track of change history in a reportable form during this time.