DGS Racing/EPOS Release Notes
Version 3.5.0 Release Date: February 16, 2010
IMPORTANT: Before upgrading a database to racing v3.5.0, the database must be updated to sports v2.3.0.6.
Changes: D583: Games that have a parent game, but are not periods of the parent game, did not appear in the PID. D586: Fixed the right margin on the EPOS Operation Summary report. D660: "Out of present range" error when trying to post an EPOS sports ticket. D661: "List index out of bounds" error when posting a Pick bet with a large number of selections. D665: If a terminal configuration specified TSP800 as the ticket printer, an "Invalid variant type conversion" error would occur when running the EPOS Terminal application. D821: When voiding a round robin ticket, the ticket would appear once on the EPOS Voids report for each parlay in the round robin. D936: When a terminal's configuration specified that the terminal had a customer display, but the terminal actually didn't have the display attached, printing tickets would fail after the serial output buffer became full. D1291: In the Racing Call Center, when placing a double or pick bet, if a runner was scratched in the first race, the checkbox for that runner's position in subsequent races was also disabled. D1292: An error would occur when printing the Track Listing report with the Disabled option selected. D1293: The Rebate report didn't show the bet type for quinella, pick-3 and pick-4 bets. D1294: Exacta, trifecta and superfecta boxes were listed separately from the non-box bets. They are now combined. D1295: On the Race Wager Listing report, the placed date field overlapped the settled date field. D1296: In the Racing Call Center, when a multi-race bet type was selected (double, pick-x), the display of the races and runners had the wrong race number on all races after the first race. D1378: There is now a separate minimum stake for each bet type. Previously, there was a single minimum stake for all bet types. D1379: In the Racing Call Center, unit stake amounts can now contain decimal amounts. D1398: The DGS-Bodog interface now supports multi-currency. F381: Added support for the Samsung tax printer. F434: Group and subtotal the Till Activity Report by currency. F598: Added support for up to 20 runners per race in the EPOS terminal.
Version 3.4.1 Release Date: October 21, 2008
Changes: F392 Mobile terminal support o EPOS Terminal: Added support for the Zebra RW420 wireless mobile printer. Terminals using this model of printer generate tickets using the new template files DefaultRacingTicketCPCL.xml, DefaultSportsTicketCPCL.xml and DefaultVoucherCPCL.xml, which must be located in the same folder as dgsterm.exe. o Terminal Manager: “Zebra RW420” added to the printer model options in the terminal configuration form. Version 3.4.0 Release Date: October 6, 2008
Changes: F402: Change: EPOS Terminal now enforces the same related game rules that are enforced by the call center and web applications. D490: Bug fix: When a location had only ticket sold transactions for an operation date (no tickets cashed, vouchers issued, vouchers cashed, etc), some fields on the EPOS Operation Summary report were blank when they should not have been blank. D491: Bug fix: The bet description was incorrect on Pick-X wagers placed in the racing call center application. The track and race number were missing from the description. D492: Bug fix: When a racing call center wager was rejected because the race was closed, then was subsequently resubmitted after opening the race, the selections were duplicated. D493: Bug fix: The Print Lines report in the Terminal Manager application was not correctly displaying rotation numbers greater than 32767. D499: Bug fix: During the process of paying rebates, an error message would appear once for every deleted player account. D500: Bug fix: The PID was displaying “+000” for the odds on selections that had no odds. D505: Bug fix: An error occurred when attemting to place an EPOS wager on a game with a rotation number greater than 32767.
Version 3.3.1 Release Date: June 13, 2008
Changes: RE-4071: Bug Fix: Enforce aggregate limits for pick bets RE-4073: Big Fix: New Fix for races after midnight, related to RE-3943 RE-4072: New feature: EPOS Terminal can print the ticket to an XML file.
Version 3.3.0 Release Date: February 15, 2008
Changes: Bug fix: “Maximum payout per player per race”, with the option of “max net profit” was not being enforced correctly.
Version 3.2.0 Release Date: February 13, 2008
Changes: RE-3955: Bug Fix: A bug introduced in v3.1 with the new rebate rates was fixed. The process of paying rebates took too long. RE-3948: New feature: Flat tax per transaction. RE-3952: Bug Fix: Fixed a bug that resulted in a “could not find field” error when paying rebates. RE-3951: Bug Fix: Fixed a bug in the Rebate Detail Report that caused the report to fail when it attempted to connect to the database. RE-3917, RE-3953, RE-3944: New Feature: Free plays.
Version 3.1.0 Release Date: January 9, 2008 Changes: RE-3720: Bug Fix: EPOS ticket numbers are generated randomly, but the system was not checking that a newly generated random ticket number was unique. In the rare case that a ticket number was not unique, an error would occur when the ticket was inserted. The system now checks for uniqueness and generates another ticket number if necessary. RE-3902: Bug Fix: On an EPOS ticket printed in raster mode, wager detail descriptions that were too long for a single line were not wrapping to the next line properly. Only the last line was visible. RE-3905: Bug Fixes: When printing the Print Lines report, a tournament type game would cause a division by zero error. Also, point spread line parts that had odds but no point spread were printing with the odds and no point spread, when odds without point spread is an incomplete (unavailable) line and should not appear at all. RE-3909: Bug Fix: The Terminal Client installer was not setting the “Start In” attribute of the short cuts it created. This caused the application to not be able to find certain files when it was launched using the shortcut. RE-3910: Bug Fix: After creating a new till in the Terminal Manager, the new till showed a blank description in the till list. After refreshing, the description would appear as it should. RE-3911, RE-3913: New Terminal Manager Report: Voucher Transaction Report. RE-3912: Bug Fix: The Operation Summary report was showing incorrect amounts for Vouchers Issued and Vouchers Redeemed. RE-3914, RE-3915: New Feature: As a security measure, all reports that include an EPOS ticket serial number or voucher number now only show the first 8 characters of the number. This will make it more difficult for a ticket to be cashed without having the actual ticket in hand. The only place an entire ticket number or voucher number appears is on the ticket or voucher itself. RE-3916: Bug Fix: A bug in the Terminal Manager cause the terminal configuration dialog to assign an incorrect ticket template to a terminal. RE-3919, RE-3920: New Feature: Since report no longer show complete ticket numbers and voucher numbers, all areas where a ticket or voucher number must be entered by the user (other than cashing a ticket) now accept only the first 8 characters. If more than one ticket shares the same first 8 characters, the UI will prompt the user to select the desired ticket. Areas affected: placing a hold on a ticket, printing a Ticket Details report. RE-3922: Bug Fixes: Racing Call Center application: When the user edits an existing Trifecta Box wager, the edited bet was being erroneously converted to an Exacta Box. An err prevented editing of an existing Pick-X bet. When editing an existing Superfecta bet, the last leg was lost. RE-3923: Bug Fix: In the Racing Call Center, bets with very long selections strings (more than 17 or 18 selections) did not appear completely in the readback area. The UI control was not large enough for all selections to be displayed, but they were actually there and the bet was being posted properly. The user just couldn’t do a proper readback. RE-3926: Bug Fix: The system was not properly enforcing the Max Payout Per Player Per Race rules on parlay bets. The bug resulted in bets not being paid because the limit had been exceeded, even when the limit had not actually been exceeded. RE-3927: New Feature: Previously, the system had separate rebate percentages for straight (WPS) and exotic (everything else) bets. Now, there is a separate rebate percentage for each bet type. RE-3930: Bug Fix: Attempting to place a racing parlay bet using the EPOS Terminal Client would cause an “Abstract Error” which would prevent posting of the bet. RE-3940: New Feature: The EPOS Terminal Client now supports printing tickets in raster mode on printers that are not using a Windows driver (direct parallel connection). RE-3943: Bug Fix: There was a problem when a race program when past midnight (system time, not track time). I.e. when some races had post times and offtimes on one day, and some races had post and off time on the next day. The way post times and off times were stored, bets placed on the races after midnight appeared to the system to be past post bets, even when they weren’t. This caused the system not not score them automatically and required the user to manually release the bets for scoring.
Version 3.00.0 Release Date: November 4, 2007 IMPORTANT: After upgrading to version 3.00.0 of the terminal client, the DIP switches on Star ticket printers must be set to 1thru6 ON, 7*8 OFF. Ticket printing will fail if these switches are not set correctly.
Changes: RE-3694: Differences between the way parlay payouts are calculated in the web application and call center and EPOS terminal were resolved. RE-3011: The PID shortcut created by the installer did not work. The target was incorrect. The terminal client now supports the Star TSP700 printer with USB interface. To use a TSP700 USB printer, install the driver contained in the file “rasterdrv_2k-xp_20060601.exe”. Tickets can now be printed using graphics instead of text. For backward compatibility, text tickets are still supported using the existing ticket templates. The terminal client now reads the status of the ticket printer before printing a ticket. This prevents a ticket from being posted if a printer condition exists that will prevent the ticket from being printed (printer offline, out of paper, etc). On Star printers, DIP switch 1 must be set to 1 through 6 ON, 7 and 8 OFF. RE-3886: In the terminal client, a voucher can now be issued by touching Tools -> Issue Voucher. Changes were made to the terminal client UI to make it more touch-friendly. Previously, some dialogs required the use of a keyboard and/or had buttons that were difficult to touch with a finger because of their size. RE-3885: When a voucher was issued but not redeemed, it was not included in the Vouchers Issued amount on the EPOS Operation Summary report. When the voucher was later redeemed, it would then be included in both Vouchers Issued and Vouchers Redeeemed at the same time. RE-3887: When reconciling a till in the Terminal Manager, the application automatically generates a Till Activity report. The application was generating the report for the wrong till. RE-3882: The Print Lines report in the Terminal Manager was showing the point spread in place of the money line. RE-3877: A new Terminal Manager Print Lines default template was added which prints lines using the decimal odds format. RE-3205: When a parlay card wager was placed through a web application, the system was validating the bet amount by using the maximum bet amount as both the maximum and the minimum. This did not effect normal parlays or parlay card in EPOS. It only effected parlay card wagers place online.
Version 2.95.0 Release Date: February 14, 2007
Changes: RE-5, RE-3042: The PID now stores its configuration in an XML file instead of in the registry. After upgrading to 2.95.0, PID users should run the PID Configuration utility before running the PID. The first time the PID Config utility is run after upgrading to 2.95, it will create the XML configuration file. RE-3082: The Terminal Client and Terminal Manager automatic update process has been improved. RE-18 (bug): When a league that is configured to display in the PID is deleted, the PID Config and PID applications fail with errors. RE-3010 (bug): The Card Creator application would allow the user to proceed without selecting which form they are using. RE-3035 (bug): Online parlay cards were using the local min/max wager amount settings instead of the online settings. RE-3033 (bug): When a user attempted to place a parlay card wager for less than the minimum wager amount, an incorrect error message was displayed: “No argument for format ‘%s’”. RE-15 (bug): When creating a sportsbook account from an EPOS player tracking account, some field values were not being set properly. RE-7: When printing a Print Lines report in the Terminal Manager, only active leagues will appear in the list. Previously, all leagues appeared. RE-8: The Print Lines report has been modified to display lines in the format that was used prior to version 2.93. RE-3009: When printing the Print Lines report, the user can choose which template is to be used. RE-3014 (bug): In the Wagers On a Race report, the tote ticket number field was not wide enough for the entire number to appear. RE-3013 (bug): In the Racing Manager, the application would allow a user to open two instances of the racing console for the same date at the same time. This is no longer allowed. RE-3018 (bug): In the Terminal Client, the “Tracks-2” and “Tracks-3” buttons were not enabled when there were more tracks than would fit on one screen. RE-3001: The Terminal Manager will no longer allow the current operation date to be advanced beyond the current date.
Version 2.93.0 Release Date: August 30, 2006
Files changed in this release: DGS_EPOS_2_93_0.sql (Database update script) dgs.dll (DGS COM+ Library) dgsrcp.dll (DGS Racing COM+ Library) dgsrc.exe (DGS Racing Call Center Client) dgsrm.exe (DGS Racing Manager) CardCreator.exe (Parlay Card Creator) dgsets.dll (DGS EPOS Terminal Server) dgspid.exe (DGS Public Information Display) pidconfig.exe (PID Configuration Tool) dgstm.exe (DGS EPOS Terminal Manager) dgsterm.exe (DGS EPOS Terminal Client) PrintLines.rpt (Terminal Manager report file) TillActivity.xsl (Obsolete Terminal Manager report file) RecTillSum.xsl (Obsolete Terminal Manager report file) RaceStats.xsl(Obsolete Terminal Manager report file) GameStats.xsl (Obsolete Terminal Manager report file) EposSales.rpt (Obsolete Terminal Manager report file) TicketPayout.xsl (Obsolete Terminal Manager report file) UnpaidTicketsAll.rpt (Obsolete Terminal Manager report file) UnpaidTickets.xsl (Obsolete Terminal Manager report file) RecTillSum.rpt (New Terminal Manager report file) TillActivity.rpt (New Terminal Manager report file) TillActivityHeader.rpt (New Terminal Manager report file) TillActivityCurrency.rpt (New Terminal Manager report file) RacingStats.rpt (New Terminal Manager report file) GameStats.rpt (New Terminal Manager report file) EposSalesSum.rpt (Terminal Manager report file) EposSoldCashed.rpt (Terminal Manager report file) EposOpSum.rpt (Terminal Manager report file) TicketPayoutSum.rpt (Terminal Manager report file) TicketPayoutDetail.rpt (Terminal Manager report file) EposTicketDetails.xsl (Terminal Manager report file) ExpiredTickets.rpt (Terminal Manager report file)
Changes: RE-257: The timeout for calls to the Bodog host system was lengthened to 2 minutes from 30 seconds (applies to Bodog integration only). RE-234: When using the PDI VMR-138 mark sense scanner with the EPOS Terminal Client, the application was not sending scanner configuration commands to the scanner properly. This resulted in the scanner not working correctly when the scanner’s factory default settings were not the correct settings for the application. RE-90: On taxes of type “Percent of Payout”, the tax is now calculated on Payout – Refund. Previously, it was calculated on the entire payout, even if all or part of the payout was a refund. RE-239: When scoring PICK bets, the system was not properly paying winning tickets when one or more legs of the legs in the result was 99 (all). RE-249: The database was optimized to improve the performance of EPOS reports. RE-237: In the Terminal Manager, unpaid tickets can now be expired. RE-251: In the Card Creator, if the “doc” folder did not exist, an error message would occur when creating the parlay card document. RE-233: When attempting to cash a ticket and the ticket was in a currency that was not available on the terminal at which the ticket was being cashed, the wrong error message would be shown. Now the error message says “Currency XXX is not available at this terminal”. RE-199: When the limit set configuration specifies that a bet should be sent to the tote, and a tote configuration did not exist for the location at which the bet was being sold, an incorrect error message would appear. RE-232: The Terminal Manager now automatically upgrades when it detects that an upgrade is required. RE-77: The EPOS system now has an operation date. The operation date must be closed manually each day. RE-235: The ticket number was not being printed on parlay card tickets. RE-240: The EPOS Voids report was not showing the ticket number. RE-231: On the EPOS Sold/Cashed report, the space provided for the ticket number was too small to show the entire ticket number. Only the first 8 characters were showing. RE-213: The account number was not appearing on the Wagers on a Race report. RE-212: An ODBC error would occur when printing the Wager Listing report. RE-228: When manually editing race results, existing PK4 results would be deleted. RE-229: The Print Lines report in the Terminal Manager has been modified. Games are now selected by league instead of by sport, and the report is now a Crystal report instead of an XML document in a browser.
Version 2.92.0 Release Date: July 19, 2006
Files changed in this release: DGS_EPOS_2_92_0.sql (Database update script) dgs.dll (DGS COM+ Library) dgsrcp.dll (DGS Racing COM+ Library) dgsrc.exe (DGS Racing Call Center Client) RacingAPI.dll (Virtual Racing API) dgsets.dll (DGS EPOS Terminal Server) dgstm.exe (DGS EPOS Terminal Manager) dgsterm.exe (DGS EPOS Terminal Client) EposTicketDetails.xsl (Terminal Manager report file) TillActivity.xsl (Terminal Manager report file)
Changes: RE-214: The Till Activity Report and the EPOS Ticket Details Report in the Terminal Manager were not showing the new EPOS ticket number. RE-153: A racing installation that was integrated with ASI did not have the capability of paying a wager that lost less than the full amount at risk. RE-122: The Racing Call Center Client is not aware of the host system and the UI changes on the fly to show ASI specific information when the host system is ASI. RE-190: Support was added for the new ASI racing profile. RE-216: The risk amount was being displayed incorrectly for a cash customer when integrated with ASI. Version 2.91.1 Release Date: July 14, 2006
Files changed in this release: dgs.dll (DGS COM+ Library) dgsrcp.dll (DGS Racing COM+ Library) dgsterm.exe (EPOS Terminal Client)
Changes: RE-202: Support for the ASI racing profile was removed in this version. It was first added in 2.91.0 and will be back in 2.92.0. RE-200: When adding a team to a parlay wager in the EPOS Terminal Client, an access violation would occur. RE-201: A bug was introduced in v2.91.0 that caused pick bets to be scored incorrectly.
Version 2.91.0 Release Date: July 13, 2006
Files changed in this release: DGS_EPOS_2_91_0.sql (Database Update Script) dgs.dll (DGS COM+ Library) dgsrcp.dll (DGS Racing COM+ Library) dgsrm.exe (DGS Racing Manager) dgsfeedclient.exe (DGS Feed Client) dgsrc.exe (DGS Racing Call Center Client) CardCreator.exe (DGS Parlay Card Creation Utility) dgsets.dll (DGS EPOS Terminal Server) dgsterm.exe (DGS EPOS Terminal Client) dgstm.exe (DGS Terminal Manager)
Changes: RE-197: The Cashed Ticket Template was introduced in version 2.90, but the default template created by the v2.90 database updated was blank. This would cause an error in the terminal client until the operator edited the template. This update will set the default ticket template to a generic template. RE-196: There was a bug in the enforcement of the parlay maximum dogs setting for bets placed at the point of sale. RE-195: A bug prevented a house quinella wager from being manually scored. RE-187: In some cases, the system returned a list of races in the wrong order. RE-88: Horse parlays can now be placed at the point of sale. RE-183: When printing an EPOS Ticket Details report from the Terminal Manager, and the ticket number entered was non-existent, the wrong error message was displayed. RE-177: In the Past Post Tickets window in the Racing Manager, the seconds were not being shown for the off time. RE-162: A bug caused the error message “Current recordset does not support updating” when attempting to place a horse parlay wager using the Racing Call Center client. RE-164: The Racing Call Center client was sending the wrong phone line value to the Recording Manager application when starting a new recording session. RE-158: The amounts that appear on the Cashed Ticket receipt now include taxes.
Version 2.90.0 Release Date: June 5, 2006 Files changed in this release: DGS_EPOS_2_90_0.sql (Database Update Script) dgs.dll (DGS COM+ Library) dgsrcp.dll (DGS Racing COM+ Library) dgsrm.exe (DGS Racing Manager) dgsfeedclient.exe (DGS Feed Client) dgsrc.exe (DGS Racing Call Center Client) dgsets.dll (DGS EPOS Terminal Server) dgsterm.exe (DGS EPOS Terminal Client) dgstm.exe (DGS Terminal Manager)
Changes: RE-75: EPOS ticket numbers are now 12-digital hexadecimal numbers. RE-152: Rebates were not adjusting the player’s daily figure on racing installations that are hosted by ASI. RE-150: When opening the Limits form in the Racing Manager, an error would sometimes occur: “Item cannot be found in the collection corresponding to the requested name or ordinal”. RE-76: When an EPOS ticket is presented for cashing, and the ticket has previously been cashed, in addition to alerting the clerk that the ticket has already been cashed, the system can optionally print a receipt with the details of the cashed ticket (when, where and for how much the ticket was cashed). RE-110: When a racing ticket total stake calculates to zero (for example and exacta on selections 1/1) the error message has been changed to something more meaningful. RE-102: In the racing web application, the drop-down box to select a race for wagering used to contain all the races for the track. Now it contains only open races. RE-103: In the upcoming races list of the racing web application, only races for the current date will now appear. Previously, any race with a Minutes-To-Post value would appear. Under normal circumstances, a race from a past-date can never have a MTP value, but if for some reason it does, it will no longer appear as an upcoming race. RE-98: The Rebates Detail report was not working properly on non-DGS hosted systems. RE-92: The “No Hookups” setting of a game was not being enforced on EPOS wagers. RE-68: When an EPOS terminal’s configuration specified that a piece of hardware was present, but the device was not actually present (such as a mark-sense scanner, cash drawer, etc), an error would occur during application startup. This stopped the initialization process and the application was not completely initialized. RE-93: The EPOS system was allowing a ticket on a game that had already started to be canceled (with a manager’s approval). This is no longer allowed.
Version 2.89.0 Release Date: May 11, 2006
Files changed in this release: DGS_EPOS_2_89_0.sql (Database Update Script) dgs.dll (DGS COM+ Library) dgsrcp.dll (DGS Racing COM+ Library) dgsrm.exe (DGS Racing Manager) dgsfeedclient.exe (DGS Feed Client) dgsrc.exe (DGS Racing Call Center Client) dgsets.dll (DGS EPOS Terminal Server) dgsterm.exe (DGS EPOS Terminal Client)
Changes: First release to integrate racing with ASI. Feature #201: The player’s profile now appears in the racing call center UI. Bug #170: In the EPOS Terminal, when buying ½ point on a total over, ½ point was added to the total instead of subtracted. Feature #218: In the Bodog build, the batch-scoring batches will not exceed 1000 tickets per batch. When more than 1000 tickets are scored, a new batch will be started every 1000 tickets. Bug #202: House quinella bets were not being charted.
Version 2.88.0 Release Date: April 20, 2006
Files changed in this release: DGS_EPOS_2_88_0.sql (Database Update Script) dgs.dll (DGS COM+ Library) dgsrcp.dll (DGS Racing COM+ Library) dgsrm.exe (DGS Racing Manager) dgsfeedclient.exe (DGS Feed Client) dgsrc.exe (DGS Racing Call Center Client) dgsets.dll (DGS EPOS Terminal Server) etsstatus.xsl (DGS ETS status page stylesheet) dgsterm.exe (DGS EPOS Terminal Client) dgstm.exe (DGS EPOS Terminal Manager) EposOpSum.rpt (Terminal Manager Report)
Changes: Bug fix: The EPOS Operation Summary report would time out if the report took longer than 30 seconds to create. Bug #129: When a racing ticket was voided, it no longer appeared in the player’s history when viewed from a sports UI, but was still visible in Racing Manager reports. Now, a voided racing ticket appears in the player’s history and is visible in the sports call center, sports manager and sports web application. Bug #194: Limits and maximum payouts were not being enforced correctly when an account bet was placed in a currency other than the system currency. Feature #205: Previously, the options for closing a race were “Close at Post Time” and “Manual”. Manual was a confusing name, since “Manual” meant that the race would close when it was closed by the DGS Feed. In this release, the name “Manual” has been changed to “Close by DGS Feed” to avoid confusion. Also, the following close method options have been added: “Close at 3MTP”, “Close at 2MTP”, “Close at 1MTP” and “Close at 0MTP”. Feature #206: The system now tracks how a race was closed. It appears in the Racing Manager’s Race Console. The options are: “Closed by Feed”, “Closed by MTP Target” and “Closed by Manager”. Bug #208: In version 2.87, the error “Exchange Rate not initialized” would occur when attempting to place a House Quinella wager with the Racing Call Center Client. Bug #209: Everywhere a race off-time appears, the seconds are now shown. Feature #210: The system determines which wagers are possible past-post by comparing the time the wager was placed to the race off time. Previously, wagers whose placed time was later than the off time were considered possible past-post. Now, the operator can configure a number of seconds before off time that a wager will be considered possible past-post. This value is configured in the Track Configuration of the Racing Manager and is labeled “Past-post seconds before off time”. In other words, if this value is set to 30 seconds, then wagers with a placed time that is later than the off time or that is less than 30 seconds before off time will be treated as possible past-post (the manager still makes the decision whether to score or void the tickets). Bug #212: When running the feed client in capture mode, some files would overwrite other files because the file name was the time the file received. In this release, the feed client uses an incrementing number as the file name so that all file names are unique. Bug #213: In v2.87 an “Invalid variant type conversion” error would occur when attempting to post a round- robin or reverse wager from the EPOS Terminal Client. Version 2.87.3 Release Date: March 29, 2006
Files changed in this release: dgsrcp.dll (DGS Racing COM+ Library)
Changes: Bug fix: Some debug logging was left in the release. It wasn’t thread-safe and caused an error under load. Only the Bodog build was affected.
Version 2.87.2 Release Date: March 28, 2006
Files changed in this release: dgsrcp.dll (DGS Racing COM+ Library)
Changes: Bug fix: When a player attempted to place a Pick-4 bet with fewer than 4 selections, the error message stated that “A Pick4 requires at least three selections”. It now correctly says “four selections”. Bug fix (Bodog Build): An error (Variant array index out of bounds) would occur when attempting to post a ticket.
Version 2.87.1 Release Date: March 28, 2006
Files changed in this release: dgsrcp.dll (DGS Racing COM+ Library)
Changes: Bug fix: An error would occur when calling the racing web service’s ValidateTicketRacing because of some new attributes being required in v2.87.0. The caller does not need to supply those attributes. The application server properly handles their absence now.
Version 2.87.0 Release Date: March 24, 2006
Files changed in this release: DGS_EPOS_2_87_0.sql (Database update script) dgs.dll (DGS COM+ Library) dgsrcp.dll (DGS Racing COM+ Library) dgsfeedclient.exe (DGS Feed Client) dgsrm.exe (DGS Racing Manager) TheoWinAmount.rpt (Racing Manager Report) dgsets.dll (DGS EPOS Terminal Server)
Changes: Bug fix: When the racing IdWagerType for a profile was larger than 32767, an error would occur when trying to log in a player on that profile. The DGS Feed Client can now run in capture and replay modes. New Racing Manager report: Limited Payouts. This report shows how much the book has saved by limiting odds and payouts. It shows the amount that would have been paid out if full track odds had been paid compared to the amount actually paid, subtotaled by track and bet type. Bug #194: Many of the racing reports did not take the exchange rate into account for wagers placed in a currency other than USD. Bug #129: Voided racing tickets now appear in the player’s sports history. Bug: Limits were not being enforced correctly when a wager was placed in a currency other than US Dollars.
Version 2.86.0 Release Date: February 2, 2006
Files changed in this release: DGS_EPOS_2_86_0.sql (Database update script) dgs.dll (DGS COM+ Library) dgsrcp.dll (DGS Racing COM+ Library) default.cpc (COM+ Configuration File)
Changes: Bug fix: A bug in the Hessian implementation caused some Hessian calls to be made without the input parameters. This only affected the BoDog build. Batch scoring/unscoring implemented for the BoDog interface.
Version 2.85.0 Release Date: February 1, 2006
Files changed in this release: DGS_EPOS_2_85_0.sql (Database Update Script) dgs.dll (DGS COM+ Library) dgsrcp.dll (DGS Racing COM+ Library) RacingAPI.dll (Blazing Silks API) default.cpc (COM+ Configuration File) dgsrm.exe (DGS Racing Manager) TrackList.rpt (Racing Manager Report file) dgsets.dll (DGS EPOS Terminal Server) dgsterm.exe (DGS EPOS Terminal Client) dgstm.exe (DGS EPOS Terminal Manager) EposVolTrack.rpt (Terminal Manager Report)
Changes: Bug #146: Till Refill/Drop functionality was added in v2.84.0, but the rights were not added to the system. So, even though it was theoretically possible to refill or drop a till, it wasn’t possible to give a user the right to do it. Feature #148: Tracks now have a short name in addition to the track name and track code. Currently, the short name is used only for the track button captions in the EPOS Terminal Client. In the future, we plan to use the short name in the ticket description where the track code is currently used. Feature #149: Racing bet types are now enabled at the limit set level instead of system-wide. Bug #151: When printing some reports (e.g. Unpaid Tickets Report for all tickets going back to the beginning of time, for example) at the point of sale, the report could time out. Feature #152: New Terminal Manager report: EPOS Volume By Track. First release to include support for integration with BoDog. First release of the Blazing Silks API. Version 2.84.0 Release Date: December 1, 2005
Files changed in this release: DGS_EPOS_2_84_0.sql (Database Update Script) dgs.dll (DGS COM+ Library) dgsrcp.dll (DGS Racing COM+ library) dgsrm.exe (DGS Racing Manager) PastPostTickets.rpt (Racing Manager Report file) dgsrc.exe (DGS Racing Call Center Client) CardCreator.exe (Parlay Card Creator Application) dgsets.dll (DGS EPOS Terminal Server) dgsterm.exe (DGS EPOS Terminal Client) AcpCfg.exe (Configuration utility for ACP-100 Mark Sense Scanner) dgstm.exe (DGS EPOS Terminal Manager) UnpaidTicketsAll.rpt (Terminal Manager Report) DGS Terminal Manager Users Guide.pdf
Changes: Terminal Manager: In the Terminal Configuration dialog, there is a new option for the Mark Sense Scanner setting: ACP-100. Racing Manager: A new form was added to configure which tracks are available for which profile and wagering interface (call center, internet and EPOS). Click File->Profile Tracks Card Creator bug fix: The vertical and horizontal adjustment values were being ignored. It was not possible to fine tune the placement of the mark sense marks in the parlay card document. EPOS Terminal Client: Till refill and drop feature added. House Quinella wagers can now have more than one selection in each leg. New wager type: House Quinella Box. Racing Manager: The player’s account number now appears in the past-post tickets window. New Racing Manager report: Possible Past Post Tickets report. Bug fix: When a race has a missing runner, the runner numbers were incorrect in the EPOS Terminal Client. Bug fix: The Racing Call Center Client was not launching the Recording Manager correctly. Bug fix: An error would occur when editing a quinella bet. Change: In the Terminal Manager, when printing an Unpaid Tickets Report for all unpaid tickets, the tickets are now subtotaled by currency and ordered by ticket number.
Version 2.83.0 Release Date: November 7, 2005
Files changed in this release: DGS_EPOS_2_83_0.sql (Database Update Script) dgs.dll (DGS COM+ Library) dgsplayer.dll (DGS Player COM+ Library) dgsrcp.dll (DGS Racing COM+ Library) dgsets.dll (DGS EPOS Terminal Server) dgsterm.exe (DGS EPOS Terminal Client) dgsrm.exe (DGS Racing Manager) PLTrack.rpt (Racing Manager Report file) TicketList.rpt (Racing Manager Report file) TicketsOnRace.rpt (Racing Manager Report file) ToteDetail.rpt (Racing Manager Report file) TrackList.rpt (Racing Manager Report file) RebatesDetail.rpt (Racing Manager Report file) WCPrograms.dot (Winner’s Circle Program Template) dgsrc.exe (DGS Racing Call Center Client)
Changes: Bug fix: A bug was introduced in 2.82.0 that prevented a player from logging in to any application if the player did not have an agent. Bug fix: A bug was introduced in 2.82.0 that prevented players from logging in simultaneously to the sports call center and the racing call center. New Feature: Winner’s Circle past performance data can be imported from the Racing Manager. New Feature: Winner’s Circle program documents (Word documents) can be created by the Racing Manager. New Racing Manager Report: Rebates Detail Report. Bug fix: The wager settle date wasn’t being set on house quinella wagers. New Feature: Racing wagers can be placed with unit stakes of as little as 10 cents. Bug fix: The Profit/Loss by Track report showed totals for all tracks, even when the report was filtered by track type.
Version 2.82.0 Release Date: September 23, 2005
Files changed in this release: DGS_EPOS_2_82_0.sql (Database Update Script) dgs.dll (DGS COM+ Library) dgsrcp.dll (DGS Racing COM+ Library) dgsplayer.dll (DGS Player COM+ Library) dgsbgame.dll (DGS Game COM+ Library) dgsets.dll (DGS EPOS Terminal Server) dgsterm.exe (DGS EPOS Terminal Client) dgstm.exe (DGS EPOS Terminal Manager)
Changes: Bug fix: A bug in the new login method in v2.81.0 prevented it from working. A new method was added to the CBusPlayerRTx API COM class. The size of the IdWagerType field was changed from Smallint to Integer.
Version 2.81.1 Release Date: September 16, 2005
Files changed in this release: dgs.dll (DGS COM+ library) dgsrcp.dll (DGS Racing COM+ library) dgsplayer.dll (DGS Player COM+ library)
Changes: Bug fix: A bug in the new login method in v2.81.0 prevented it from working.
Version 2.81.0 Release Date: September 15, 2005
There is now a separate installer for the database update scripts (SetupDatabaseScripts_X_X_X.exe). The database update scripts are no longer in setup_dgs_X_X_X.exe. There is now an installer for the EPOS Terminal Client (SetupTerminalClient_X_X_X.exe). It installs dgsterm.exe to the folder C:\Program Files\DGS\Terminal Client. Be sure to remove any instances of dgsterm.exe that are in a different location and remove any incorrect shortcuts.
Files changed in this release: DGS_EPOS_2_81_0.sql (Database update script) dgs.dll (DGS COM+ library) dgsrcp.dll (DGS Racing COM+ library) dgsplayer.dll (DGS Player COM+ library) dgsrm.exe (DGS Racing Manager) dgsets.dll (DGS EPOS Terminal Server) dgstm.exe (DGS EPOS Terminal Manager) UnpaidTickets.rpt (Terminal Manager report) UnpaidTicketsAll.rpt (Terminal Manager report) dgsterm.exe (DGS EPOS Terminal Client)
Obsolete files (no longer used): UnpaidTickets.xsl (Terminal Manager report)
Changes: Bug fix: In v2.80.0, when posting an EPOS racing ticket, the following error would occur: Error loading EntryName from recordset. The Unpaid Tickets report was changed so that when a date range is specified, the report will include tickets that were unpaid at the end of the date range. For example, if the unpaid tickets report is printed for Aug-1 to Aug-7, then the report will include tickets that are unpaid or were paid after Aug-7. Previously, it only included unpaid tickets at the time the report was printed. When a date range is not specified, the report includes all ticket that are unpaid at the time of printing as it always has. Player login and logout methods changed for all applications.
Version 2.80.0 Release Date: September 6, 2005
Files changed in this release: DGS_EPOS_2_80_0.sql (Database update script) dgs.dll (DGS COM+ Library) dgsets.dll (DGS EPOS Terminal Server) dgstm.exe (DGS EPOS Terminal Manager) EposSalesSum.rpt (Terminal Manager report file) EposOpSum.rpt (Terminal Manager report file) EposTaxSum.rpt (Terminal Manager report file)
Obsolete files (no longer used): TaxByLocation.xsl (Terminal Manager report file)
Changes: New Terminal Manager report: EPOS Sales Summary. This report is identical to the EPOS Sales report, except that it only shows the totals per day instead of listing every ticket. New Terminal Manager report: EPOS Operation Summary. New Terminal Manager report: EPOS Tax Summary. This report replaces the Taxes By Location report, which was removed. Version 2.79.1 Release Date: August 24, 2005
IMPORTANT: There is now an installer for the Racing Call Center Client. The installer will install dgsrc.exe into “c:\Program Files\DGS\Racing Client”. Before using the installer on a machine for the first time, manually remove any copies of dgsrc.exe that exist on the machine and any existing shortcuts.
Files changed in this release: dgsrcp.dll (DGS Racing COM+ library) dgs.dll (DGS COM+ Library) dgsrm.exe (DGS Racing Manager) dgsrc.exe (DGS Racing Call Center Client) dgsfeedclient.exe (DGS Feed Client)
Changes: Changes to support host sportsbook systems other than DGS. Bug #140: In the Racing Call Center Client, an error would occur when the user tried to edit an unposted bet.
Version 2.79.0 Release Date: August 23, 2005
IMPORTANT: The installer setup_dgs_X_XX_X.exe no longer contains a “Reports” component. The Racing Manager reports are now installed by the Racing Manager installer, which puts the report files into the same folder as dgsrm.exe. The registry entry that specifies the location of the report files (HKLM\Software\DGS\Racing\ReportFilePath) is no longer used. When upgrading the Racing Manager on a workstation, remove any old Racing Manager report files that might be in a different location on the machine.
Files changed in this release: DGS_EPOS_2_79_0.sql (Database update script) dgsrcp.dll (DGS Racing COM+ library) dgs.dll (DGS COM+ Library) dgsfeedclient.exe (DGS Feed Client) dgsrc.exe (DGS Racing Call Center Client) dgsets.dll (DGS EPOS Terminal Server) dgsterm.exe (DGS EPOS Terminal Client) dgstm.exe (DGS Terminal Manager)
Changes: Feature #136: Racing wagers now get their Place Date/Time value from the database server instead of the COM+ server. Bug #134: In the Terminal Manager, it was not possible to close a report that was a Crystal Report. Now, the user can right-click the report node in the tree view and choose “Delete” from the popup menu to delete, or close, the report. Bug #135: On EPOS racing bets placed in a foreign currency (other than USD), the bet description contained the unit stake in USD instead of the foreign currency. Bug #137: The Terminal Manager installer was not putting Terminal Manager shortcuts on the desktop or in the start menu. Feature #138: After scoring races, the dialog that appears showing how many wagers were scored and how many were not scored now contains much more information. The Racing Call Center Client was modified to remove all direct connections to the database. All database access is made through the hook interface. Version 2.78.2 Release Date: August 17, 2005
Files changed in this release: 02_UpdatePlayerStatistic.sql (database patch) dgsrcp.dll (DGS COM+ Racing Library)
Changes: Bug #133: House Quinellas were not being graded when a runner on the ticket was scratched.
Version 2.78.1 Release Date: August 10, 2005
Files changed in this release: dgsrcp.dll (DGS COM+ Racing Library)
Changes: Bug #130: When the system scored quienllas and quinella boxes it did not set the settle date. This caused the wagers to not appear in the player’s history.
Version 2.78.0 Release Date: August 4, 2005
Files changed in this release: DGS_EPOS_2_78_0.sql (Database update script) dgs.dll (DGS COM+ Library) dgsrcp.dll (DGS COM+ Racing Library) dgsfeedclient.exe (DGS Feed Client) dgsrm.exe (DGS Racing Manager) dgsrc.exe (DGS Racing Call Center Client) PLTrack.rpt (Racing Manager Report) TicketList.rpt (Racing Manager Report) TicketsOnRace.rpt (Racing Manager Report) dgsets.dll (DGS EPOS Terminal Server) dgstm.exe (DGS Terminal Manager) EposTicketDetails.xsl (Terminal Manager Report Stylesheet) dgsterm.exe (DGS EPOS Terminal Client) dgspid.exe (DGS Public Information Display) PIDConfig.cpl (PID Configuration applet)
Changes: The amount paid on a racing bet can include amounts that are due to all or part of the bet winning as well as amounts that are paid because of selections being scratched, or both. Before this version, the system did not distinguish between those two amounts. It simply stored the total amount paid to the player which included both amounts paid for winnings and amounts refunded for scratches. Now, on racing bets scored by the DGS Racing System (i.e. booked bets), the system tracks the amount of a racing bet’s payout that is due to runners being scratched. In the Terminal Manager, the EPOS Ticket Details report shows the amount of the racing wager payout that is due to refunds. In the Terminal Manager, the Racing Statistics report no longer includes scratches and refunds in the “Stake” and “Paid Out” columns. Therefore, the stake and hold percentages are no longer skewed by scratches and refunds which have a hold percentage of 0. Note that on tote bets, the system does not know how much of a payout is due to scratches, therefore scratches ARE included in the stake and payout of for tote bets. In the Racing Manager Profit/Loss by Track report, the “Stake” amount now excludes amounts that were refunded and the “Paid Out” amount excludes refunds. I.e., refunds are excluded from the report completely. In the Racing Manager, the name of the “Ticket Listing” report was changed to “Racing Wager Listing” to avoid confusion with EPOS tickets. In the Racing Manager, the Racing Wager Listing report now shows the amount refunded due to scratches and voids. In the Racing Manager, the “Tickets on a Race” report was renamed to “Wagers on a Race”. In the Racing Manager, the “Wagers on a Race” report now shows the amount refunded due to scratches and voids. The limit sets window in the Racing Manager has been reorganized using a tabset. There is also now a list of all profile/track combinations that the limit set is assigned to. Feature #116: A “Quick Results” button was added to the Race Results window. Clicking this button will open the Quick Result form, which is a form that makes it easier to enter complete results quickly instead of just making minor changes to existing results. Feature #116: In the Racing Manager’s Race Console, there is a “Edit Results” button next to the “Score Tickets” button. Clicking this button will open the Race Results Window (the same window you could previously only open from the Races->Open window). Feature #107: In the Racing Manager, a limit set can now be configured to limit the total payout or the total net profit a player can win on a single race. Feature #108: The system can now pay rebates to players. The rebates are configured, per track, in the limit set (Racing Manager). Bug #113: In the EPOS Terminal Client, when a race had runners “1” and “1A”, the “1” button was disabled when runner “1” was scratched, even though runner “1A” was still running. This bug was in the EPOS terminal only. The web client and the call center were not effected. Bug #114: When manuall entering quinella results, the selections must be entered with the smaller numbered runner first. For example, the quinella result must be entered as “2-8” regardless if the actual finish order was “2-8” or “8-2”. If the user entered the result in the wrong order, all bets would be scored as losers. Now, if a users enters the result in the wrong order, the system will correct it automatically. Feature #71: The following race information is now stored in the system: Distance, Surface, Class and Purse. This information is not available in the feed for every race, but when it is, it will be present. Feature #71: The following entry information is now stored in the system: Trainer Name, Owner Name, Weight, Equipment and Medication. Feature #103 and #104: In the Racing Call Center Client and Racing Web Client, quinella bets can now have more than one runner in each position. In other words, a bet like this can now be placed: QIN 1/3,5.
Version 2.77.0 Release Date: July 28, 2005
Files changed in this release: DGS_EPOS_2_77_0.sql (Database update script) dgs.dll (DGS COM+ Library) dgsrcp.dll (DGS COM+ Racing Library) dgsfeedclient.exe (DGS Feed Client) dgsrm.exe (DGS Racing Manager) PLTrack.rpt (Racing Manager report file) dgsrc.exe (DGS Racing Call Center Client) dgsets.dll (DGS EPOS Terminal Server) dgsterm.exe (DGS EPOS Terminal Client) dgspid.exe (DGS EPOS Public Information Display) PIDConfig.cpl (PID Configuration Applet)
Changes: Feature #101: The PID can now display Winner’s Circle odds and results. Feature #22: In the EPOS Terminal, quinella bets can now have more than one runner in each position. In other words, a bet like this can now be placed: QIN 1/3,5. Feature #22: The EPOS terminal now supports quinella box wagers. Bug #102: The racing call center client was always trying to record instead of respecting the preferences setting. Feature #97: In the Racing Manager, the Profit/Loss by Track report can now be filtered by All Tracks, Live Tracks and Virtual Tracks. Feature #57: The feed server will only allow one login for each username/password. Feature #59: The feed client now shows messages sent by the feed server administrator. Operators should monitor these messages. The feed server administrator will send messages when there is something important that the operator needs to know such as a wrong result or a race going off late.
Version 2.76.0 Release Date: June 28, 2005
Files changed in this release: DGS_EPOS_2_76_0.sql (Database update script) dgs.dll (DGS COM+ Library) dgsrcp.dll (DGS COM+ Racing Library) dgsplayer.dll (DGS COM+ Player Library) dgsbgame.dll (DGS COM+ Game Library) dgscpwiz.exe (COM+ Configuration Wizard) dgsrc.exe (DGS Racing Call Center Client) dgsrm.exe (DGS Racing Manager) dgsfeedclient.exe (DGS Racing Feed Client) dgsets.dll (DGS EPOS Terminal Server) dgsterm.exe (DGS EPOS Terminal Client) dgstm.exe (DGS EPOS Terminal Manager) dgspid.exe (DGS EPOS Public Information Display) PIDConfig.cpl (PID Configuration Applet)
Changes: Feature #74: In the Race Results window of the Racing Manager, a note was added next to the “Off Time” field to remind the user that the off time should be entered using the track’s timezone. Bug #47: The Racing Client would get an error "Login failed for user sportbookdba" if DSSports.dat file was not present, even though the Racing Call Center doesn’t connect directly to the database. This is now fixed and that file is no longer required by the Racing Call Center. Bug #52: Sometimes when the user selected a track from the drop-down list, a different track was displayed. This was caused when a new track was created during the user’s session. This has now been fixed. Bug #55: When the name of a profile was changed, the name remained the same in the Racing Manager. This caused users to think that profiles were missing from the Racing Manager when they just had a different name. Feature #81: The EPOS Terminal Client and the Public Information Display now support decimal odds. The EPOS Terminal uses the odds style configured for the player associated with the EPOS location. The PID uses the odds style specified in the PID Config Conrol Panel Applet. Bug #85: Limits were not being enforced for PICK bets. Feature #92: For EPOS, each currency can individually be configured to round to any amount. For example, USD can be rounded to the cent, while Venezuelan Bolivars can be rounded to the nearest 100 VEB. Bug #90: In the Racing Client, when the user opens a player account and the system confirms the player’s password, if the user clicked “Cancel”, the player would remain logged in. Feature #86: In the track window of the Racing Manager, there are two new track types: Winner’s Circle and Casino. These are for tracks that belong to the virtual racing system. Bug #49: When a racing pool is canceled, there are no results for the pool. Since no bets matched a winning result, all bets were scored as losers. Now, when there are no results for a pool, all bets on that pool are refunded.
Version 2.75.0 Release Date: April 29, 2005
Files changed in this release: DGS_EPOS_2_54_0.sql (Database update script) dgs.dll (DGS COM+ Library) dgsrcp.dll (DGS Racing COM+ Library) dgsrc.exe (DGS Racing Call Center Client) dgsets.dll (DGS EPOS Terminal Server) PIDConfig.cpl (PID Configuration Control Panel Applet)
Changes: The system now supports account parlay card wagers. The Racing Call Center Client was not launching the call recording application. It does now. An option was added to the PID Configuration to allow the user to specify which league should show scores.
Version 2.74.0 Release Date: April 11, 2005
Installation Notes: Terminal Manager: There is a new installer for the Terminal Manager. Before using the new installer, uninstall any previous installation of the Terminal Manager using Add/Remove Programs from the Control Panel.
Files changed in this release: DGS_EPOS_2_74_0.sql (Database update script) dgs.dll (DGS COM+ Library) dgsrcp.dll (DGS Racing COM+ Library) dgsrm.exe (DGS Racing Manager) dgsets.dll (DGS EPOS Terminal Server) dgsterm.exe (DGS EPOS Terminal Client) dgstm.exe (DGS Terminal Manager) TicketPayoutDetail.rpt (Terminal Manager report file) dgstrans.exe (Schedule Translation Tool) dgspid.exe (Public Information Display) PIDConfig.cpl (PID Configuration Applet)
Changes: When printing the Game Statistics Report from the Terminal Manager, an error would occur. Bug fix: The EPOS Sold/Cashed report was including all locations, not just locations managed by the manager printing the report. New Terminal Manager report: Ticket Payout Detail Report. This is very similar to the Ticket Payout Summary report, except that it lists all the tickets instead of just showing totals. House Quinellas are now charted in the Racing Manager. In the Racing Manager, tote bets are now charted in a separate chart. On MLB bets placed in the EPOS Terminal, the listed pitcher value will initially be the default listed pitcher specified in the player account used by the terminal location. On MLB total and run-line bets, the profile setting “Allow action on MLB total and run line” is now enforced. If this box is checked, then the user has the option of selecting the listed pitcher option. If it is not checked, then the user has no option and the bet must list both pitchers. A bug that sometimes caused an error in the EPOS Ticket Details report was fixed. The PID can now show the scores of games. The scores are entered using the Schedule Translation Tool.
Version 2.73.1 Release Date: March 30, 2005
Installation Notes: The installer for the Crystal 8.5 Runtime has been updated. The latest installer is CrystalRuntime_8_5a.exe.
Files changed in this release: dgstm.exe (DGS Terminal Manager)
Changes: Bug fix: When printing the new reports in the Terminal Manager (EPOS Sales, EPOS Sold/Cashed, EPOS/SB Transfers) a “File not found” error would occur on some machines. Bug fix: Some files required by the Crystal Reports runtime were missing from the installer. The Crystal Runtime should be reinstalled using the new installer on machines that use the Crystal Runtime (DGS Terminal Manager, DGS Racing Manager).
Version 2.73.0 Release Date: March 30, 2005
Files changed in this release: DGS_EPOS_2_73_0.sql (Database update script) dgs.dll (DGS COM+ Library) dgsets.dll (DGS EPOS Terminal Server) dgsterm.exe (DGS EPOS Terminal Client) dgstm.exe (DGS Terminal Manager) EposSoldCashed.rpt (Terminal Manager Report file)
Changes: New Terminal Manager report: EPOS Sold/Cashed In the EPOS Terminal, the user can select the listed pitcher on baseball plays.
Version 2.72.0 Release Date: March 23, 2005
Installation Notes Racing Manager: The Racing Manager now has a separate installation utility named SetupRacingManager_X.exe. It is no longer contained in setup_dgs_X.exe. Before installing the Racing Manager using the new setup utiility, uninstall the Racing Manager using Add/Remove Programs in the control panel. To do this, in Add/Remove Programs, select “DGS Race and Sportsbook” and click the “Change/Remove” button. Choose “Modify” and click “Next”. Deselect the Racing Manager and continue.
Files changed in this release: DGS_EPOS_2_72_0.sql (Database update script) dgs.dll (DGS COM+ Library) dgsrcp.dll (DGS Racing COM+ Library) dgsrm.exe (DGS Racing Manager) dgsfeedclient.exe (DGS Feed Client) dgspid.exe (DGS Public Information Display) PIDConfig.cpl (DGS PID Configuration Applet)
Changes: The PID application can optionally display a graphic on each banner. The system now stores a separate DGS tote configuration (broker ID and password) for each EPOS location instead of one global setting. The configurations are stored in the DgsToteConfig table.
Version 2.71.0 Warning: The database must be updated to sports version 2.1.3.0 BEFORE updating the racing schema to 2.71.0.
Release Date: March 18, 2005 Files changed in this release: DGS_EPOS_2_71_0.sql (Database update script) dgs.dll (DGS COM+ Library) dgsrcp.dll (DGS Racing COM+ Library) dgsplayer.dll (DGS Player COM+ Library) dgsbgame.dll (DGS Game COM+ Library) dgscpwiz.exe (DGS COM+ Configuration Wizard) default.cpc (COM+ Configuration file) dgsrc.exe (DGS Racing Call Center Client) dgsets.dll (DGS EPOS Terminal Server) dgstm.exe (DGS EPOS Terminal Manager) EposSbTransfers.rpt (Terminal Manager Report file) EposSales.rpt (Terminal Manager Report file) dgspts.exe (DGS Player Tracking System) dgsterm.exe (DGS EPOS Terminal Client) dgspid.exe (DGS Public Information Display) PIDConfig.cpl (DGS PID Configuration Applet)
Changes: New Terminal Manager Report: EPOS-Sportsbook Account Transfers. Bug fix: A manager was required to have permission to print the Epos Voids Report in order to be able to print the Ticket Payout Report. Bug fix: A bug in the Racing Call Center Client caused the selections in the 5th and 6th legs of a pick 6 bet to possibly be different that the ones actually selected by the user. When DGS tote tickets were resolved, the current date was used for the settle date. This caused a problem when tickets from one day were resolved the following day. Now, the race date will be used regardless of when the ticket is resolved. In the EPOS Terminal Client, if a player card has been scanned and the player tracking account is linked to a sportsbook account, the player can make a deposit into his sportsbook account at the point-of-sale. New Terminal Manager Report: EPOS Sales Report. A Zip Code field was added to the player tracking system personal information. A sportsbook account can be created using the Player Tracking System. The sportsbook account is created using the personal information from the player tracking account. Bug fix: The draw odds were not being displayed in the PID.