Technical Information

DD Reports & Windows10

/in , , , , /by

Windows 10 does some strange things with printers and Digital Dining.  And you may encounter this issue if using a Windows10 machine as your Back Office.  Symptoms of this issue could be any of the following but typically this simple fix will address any of them.

  • Reports display incorrectly (column titles and data appears unformatted)
  • Reports display blank results when information is known to exists to report on
  • Reports appear to not run at all.  (ie. No report window pops up after a report is run)

To fix this issue, try navigating to control panel, devices and printers and ensure that you have a default printer selected.  To do this, right click on the printer and select “Set as Default”.  A check mark will appear over the printer typically letting you know that this particular printer is now your default.

Reopen BackOffice and run your report and see if the issue is resolved.

If the issue is not resolved.  Go back to control panel, devices and printers and select a different printer as the default. (You can always select any printer to print to once you are ready to print a report.)

Try to run your report again and see if that fixes the issue.

If that does not, your system may need to have a REPAIR_ALL run, which typically takes roughly 20mins.  Please call if you feel you need to have a REPAIR_ALL run on your system as certain aspects have to changed prior to running this tool.

Our support number is 843-900-4433

 

Properly Uninstalling Digital Dining from WinXP

/in , , , , /by

Digital Dining leaves behind some trace files when is uninstalled from a WinXP system.  So after an uninstall is performed you need to backtrack and perform a few extra steps to completely remove DD.  You want to do this when performing reinstalls to address issues or things of that nature.

Before Uninstalling DD, backup your configuration files in the Digital Dining directory.

You will want to copy the following files to a temporary location as you will drop them back once a reinstall is complete.

DDDATA.ini, DDPRINT.ini, POS.ini

Next open control panel, add remove programs and select to remove Digital Dining.

When the uninstall is complete DO NOT REBOOT yet.  Select No when prompted to reboot.

Browse out to File Explorer, and navigate to Program Files or Program Files (x86) and right click on the Digital Dining directory itself and select Delete.

Next still from File Explorer, navigate to the Windows directory.  Navigate to the Assembly directorty.  High all files that start with DD.  Delete these files.

Next Reboot and then perform a fresh install from the BackOffice\Data\CDROM directory. (ie. Setup.exe) — Always install as administrator.  Do this by right clicking the setup.exe file and select “Run As Administrator”

When the install completes, DO NOT REBOOT.  Grab your configuration files you copied out of the directory earlier and paste them in the Digital Dining Application directory.

Now you can reboot and the system should come right up and hopefully any issues being had are now resolved.

Troubleshooting Caller ID Issues with DD

/in , , , , /by

Digital Dining Caller ID is relatively simple process to setup and manage.   You just have to plug in a CallerID box such as WhoozCalling and then setup the Caller ID server to reflect the COM port and communication settings.

This is done by launching the Caller ID Server from the Digital Dining Application directory and then select Setup from the top menu.

Enter in the details for the COM port and how many lines the system will be using and what type of CallerID Unit is being used.

Numbers should start relaying through the CallerID Server and users can select to enter order for the caller directly from the POS.

Computer Not Found Error

/in , , , , /by

When attempting to connect to your data folder from a client terminal, sometimes even though you can see the backoffice machine and select the data path for DD, it will come back in a yellow status saying “Computer Not Found”.

This issue seems to be Permissions/DNS related although typically changing these settings will not correct this error for some reason.  Here is a work around that does fix the issue:

  1. Make sure the back office machine is using a STATIC IP Address.  Not DHCP.
  2. Open Windows File Explorer, Browse to Windows directory.
  3. Browse to System32\drivers\etc
  4. Locate the files labeled “HOSTS”
  5. Right click on the file and select edit.
  6. At the bottom of the file on a new line enter the IP Address of the backoffice server.  Hit the tab key, then enter the network name of the backoffice machine.  (ie. xxBO).
  7. Save and close the file.
  8. Your digital dining data path box should now appear green and you should be able to connect to data.

How to fix QSR

/in , , , /by

QSR sometimes will display a memory allocation message and offer the ability to choose to move Storage Memory to Program Memory.  Unfortunately without a bump bar attached you have no way to select this option.  So here is the breakdown of how to address this issue:

Step 1) Stand in front of the QSR box.

Step 2) Push the Power Button Off

Step 3) Push the Power Button On.

All Fixed.

 

Adding Reports to Dropbox Tasks

/in , , /by

You can have Digital Dining automatically send your reports to DropBox for you by performing the following.

Open up ddsetup.exe.  Log In.  Click on Misc. Task Maintenance.  Report Task Maintenance. Name this report if this is a new report and you are not modifying an existing task.

Select Report Type desired, Select specific report.  Destination -> Disk File.  Output Format-> PDF.

Path -> Browse out to the location of your DropBox folder location.  Give the report a name and be sure to have it add date format to the end of the report so it doesn’t overwrite preexisting reports.

Click on Access.  Click Add Task.  Click on Schedule.  Choose “Daily” and a time for this task to run (ie. 3am)

Save and Exit.  You can now add or edit your next task and assign a different report to be pushed to DropBox.  Do this for each report you are wishing to have in your DropBox.

Adding Enter Server Drops

/in , /by

In order to allow Server Drops for staff.  Open up ddsetup.exe from the back office machine.  Log in.  Click on Windows, Register Report Maintenance, Register Report Window.  Ensure that you see “Enter Server Drops” listed available.

If not “Find” it in the list to add to the window.  (You might have to remove another option that isnt being used in order to add it.)

Once that is complete, when a server wants to make a drop, the person receiving the drop needs to enter it by logging into the POS and clicking Register Options, Enter Server Drops.

Select the server they are accepting the drop from and enter the amount of the drop.

Done.

 

Setting Up Multi-Store Frequent Diner

/in , /by

SETTING UP THE HQ MACHINE
(The machine that will house all the data for the Frequent Diner data.  This SHOULD ALWAYS BE the back office where Digital Dining is installed.)

Step 1: Click on START | RUN or Press the Windows Key + r (if Windows 8 or higher).  Type ~cmd~.  In the black box that opens, type ~ipconfig~.  Press enter.  This will display the current IP configuration for this system.  We are looking for the IP Address and the Gateway Address of the Computer. .  The IP Address & Gateway should be something like (192.168.#.# or ###.###.###.###). Write down both of these addresses and label them accordingly; as we will need when we are configuring Port Forwarding in our router.

Step 2: Open up your web browser and type “Whats My IP” and hit enter.  This will display the HQ’s public IP Address. (This is the address the other stores will use to communicate with HQ.  ie. 69.124.54.127)  Write this address down as you will need it later when setting up the other locations.

Step 3: Install Digital Dining on the Back Office PC and select ~Typical Back Office & Frequent Diner Multi Store HQ~.

If DD is already installed (but Multi Store Frequent Diner is not).  Run ~setup.exe~  from ~C:\Program Files (x86)\Digital Dining\DATA\CDROM~.
Ensure to select ~Multi Store – HQ~ for this location.  (For other locations that will communicate with the HQ server, you make sure to select the option for ~Multi Store Store~ (not HQ)).

Step 4: Once the HQ has been installed we will want to go configure the server.  Open ~DDSETUP.exe~.  Located in ~C:\Program Files (x86)\Digital Dining\Application~.  Login as ~sysop~.

Step 5: Click the menu labeled ~Misc~.  Then select ~Servers~.  Ensure that the path for Frequent Diner(old) is pointed to the correct location where Digital Dining is installed.  (ie. ~C:\Program Files (x86)\Digital Dining\Application OR if pointing to a Shared Resource: \\COMPUTERNAME\Digital Dining\Application).

Step 6: Click on the button labeled ~Advanced~  Scroll to the right with the arrows and note the port assignment for the Frequent Diner Server (ie. 50123).  You will need this port number in order to configure Port-Forwarding on the router at the HQ location.

Step 7: Click on the ~External Servers~ tab, and ensure that you see “HQ Messaging Queue” listed here and that the port number matches.  (ie. 50123).  Note: Location should be blank for the HQ system.  ~Save~ and ~Exit~.

Step 8: Open ~DDSTART.exe~.  Ensure that all of the services needed are checked (DDHLSRV, DDCDSRV1, DDFDSRV, DDMSGSRV, DDMSGQUE & DDPRINT) and then select ~Save~ then ~Exit~.

Step 9: Open up your internet browser and navigate to the “Gateway Address” you recorded from earlier.  (ie. 192.168.x.x)  This should prompt you for a login to the router.  Typically the username is ~admin~ and the password is either ~blank~, ~password~ or ~admin~ if no one has assigned a specific password to the router.  If they have you will need to obtain that password.

Once logged in to the router, Port Forwarding is typically found under the advanced section of LAN settings, or it may just be in its own tab or area called Advanced, depends on what kind of router we are working with as to where you will find the Port Forwarding section.

Step 10: Add in the Port Forwarding information for the HQ Machine.  You will click to Add, then you will Give it a name such as FDSRV, then you if asked for Protocol you will select UDP/TCP or Both if that option is available.  For Port range or Assignment you will enter in the Port # you obtained earlier when setting up the HQ Frequent Diner server.  (ie. 50123).  For Destination you will enter in the IP address of the HQ machine that we obtained earlier from when we ran IPCONFIG.  (ie. 192.168.#.#).  Apply your settings, and reboot the router.  This will take down the internet temporarily until the router comes back up.

Step 11: Reboot the Back Office machine and Let all the Digital Dining Services start back up.  We are done with the HQ configuration for Multi Store Frequent Diner.

SETTING UP THE OTHER STORE MACHINES

Step 3: Install Digital Dining on the Back Office PC and select ~Typical Back Office & Frequent Diner Multi Store Store~.

If DD is already installed (but Multi Store Frequent Diner is not).  Run ~setup.exe~  from ~C:\Program Files (x86)\Digital Dining\DATA\CDROM~.
Ensure to select ~Multi Store – Store~ for this location.

Step 4: Once the Store has been installed we will want to go configure the server.  Open ~DDSETUP.exe~.  Located in ~C:\Program Files (x86)\Digital Dining\Application~.  Login as ~sysop~.

Step 5: Click the menu labeled ~Misc~.  Then select ~Servers~.  Ensure that the path for Frequent Diner(old) is pointed to the correct location where Digital Dining is installed.  (ie. ~C:\Program Files (x86)\Digital Dining\Application OR if pointing to a Shared Resource: \\COMPUTERNAME\Digital Dining\Application).

Step 6: Click on the button labeled ~Advanced~  Scroll to the right with the arrows and note the port assignment for the Frequent Diner Server (ie. 50123).  You will need this port number in order to configure Port-Forwarding on the router at the HQ location.

Step 7: Click on the ~External Servers~ tab, and ensure that you see “HQ Messaging Queue” listed here.  For location type in the IP Address we collected earlier from the HQ machine when we went out to “Whats My IP”.  Ensure that the port number matches what was listed on the Internal Servers tab.  (ie. 50123).  ~Save~ and ~Exit~.

Step 8: Open ~DDSTART.exe~.  Ensure that all of the services needed are checked (DDHLSRV, DDFDSRV, DDMSGSRV, DDMSGQUE & DDPRINT) and then select ~Save~ then ~Exit~.

Step 9: Reboot the Back Office machine and Let all the Digital Dining Services start back up.  We are done with the Store configuration for Multi Store Frequent Diner.

In order to see the status of communication between the Store Locations and the HQ Location, From each machine launch DDMSGQUE.EXE (Note: you may need to launch ~Task Manager~, Highlight ~DDMSGQUE.EXE~ , Select ~End Task~, Confirm ~End Task~,  and then relaunch ~DDMSGQUE.EXE~ it in order to have it accessible for viewing.  You should see a monitor like below and it should show its status as to its ability to sync with HQ.

COLOR CODES:

  • COLOR
  • RED
  • YELLOW
  • GREEN
  • STATUS
  • Currently Disconnected.
  • Attempting to Sync.
  • Connected and Last Sync Date.

 

DIP switch settings for Epson T88IV and TMU220B printers

/in , /by

TM-T88IV – Serial
DSW1: 7 on and all others off
DSW2: all off

TM-T88IV- USB, Ethernet, Parallel
DSW1: all off
DSW2: 8 on and all others off

TMU220B – Serial
DSW1: all off
DSW2: 2 on and all others off

TM-U220B- USB, Ethernet, Parallel
DSW1: all off
DSW2: 2 and 4 on and all others off

What is PCI Compliancy & How can I make sure I am PCI Compliant?

/in /by

What is PCI and why should you care?The Payment Card Industry Security Standards Council (PCI SSC) facilitates the broad adoption of the PCI security standards in an effort to enhance payment account data security. This council was organized and founded by American Express, Discover Financial Services, JCB International, MasterCard Worldwide, and Visa, Inc. Restaurant businesses are responsible for handling sensitive payment card data according to the PCI DSS standards. In the event of a data security breach, you could experience any or all of the following, depending on the circumstances and whether you have taken the necessary steps to comply with PCI:

•Heavy financial damages due to fines that range from $50,000 to $500,000.
•A loss of reputation and, therefore, a decline in the number of guests visiting your restaurant.
•A temporary or permanent loss of your ability to accept credit cards as a form of payment at your restaurant.

Failure to comply with the PCI DSS standards could be very costly, and possibly even result in the loss of your business.How can you protect your business?

•Use a POS system that has been validated against the Payment Application Data Security Standards (PADSS), formerly supervised by Visa and known as Payment Application Best Practices (PABP). The PA DSS assists software vendors in developing payment applications that do not store sensitive cardholder data, thus ensuring their products are validated against the PCI DSS. Menusoft Systems, the developer of Digital Dining, is pleased to say that our current version is already listed as a vendor whose payment application has been validated. This list is available at www.pcisecuritystandards.org/security_standards/pa_dss.shtml and shows past versions of Digital Dining that are compliant as well. Make sure by going to theweb link listed above and verifying that you are on the current version or a certified version.

•The PCI DSS is a multifaceted security standard that includes requirements for security management, policies, procedures, network architecture and other critical protective measures other than software design (the part that Digital Dining gets audited and certified). This comprehensive standard is intended to help restaurants proactively protect customer account data.

The PCI Security Standards Council will enhance the PCI DSS as needed to ensure that the standard includes any new or modified requirements necessary to mitigate emerging payment security risks, while continuing to foster wide-scale adoption. The core of the PCI DSS is a group of principles and accompanying requirements, around which the specific elements of the DSS are organized:
Build and Maintain a Secure Network
Requirement 1: Install and maintain a firewall configuration to protect cardholder data
Requirement 2: Do not use vendor-supplied defaults for system passwords and other security parameters Protect Cardholder Data
Requirement 3: Protect stored cardholder data.
Requirement 4: Encrypt transmission of cardholder data across open, public networks. Maintain a Vulnerability Management Program
Requirement 5:Use and regularly update anti-virus software.
Requirement 6: Develop and maintain secure systems and applications. Implement Strong Access Control Measures
Requirement 7: Restrict access to cardholder data by business need-to-know.
Requirement 8: Assign a unique ID to each person with computer access.
Requirement 9: Restrict physical access to cardholder data. Regularly Monitor and Test Networks Requirement 10: Track and monitor all access to network resources and cardholder data.
Requirement 11: Regularly test security systems and processes.Maintain an Information Security Policy
Requirement 12: Maintain a policy that addresses information security. More information about PCI DSS is available at http://www.pcisecuritystandards.org/.We strongly recommend that you:

•Obtain the PCI DSS Outline located here on our website and use it as a starting point for configuring your restaurant for maximum security.

•We also recommend you take advantage of the ever improving security features by upgrading to the latest version of Digital Dining available.

•Undergo an onsite data security assessment by a Qualified Security Assessor (QSA) or complete a Self Assessment available at: https://www.pcisecuritystandards.org/saq/index.shtml. Questionnaire (SAQ), to identify any vulnerability within your system.

The PCI DSS requires merchants to do this on an annual basis, to assist you with PCI DSS compliance. There are four versions of this questionnaire, each version specific to a particular business scenario. The council provides instructions to guide you through selecting the SAQ that best applies to your organization, and frequently asked questions, to help you better understand the purpose of the council, and the PCI DSS. The SAQ, and all other materials.

•Undergo a network scan through a PCI DSS Approved Scanning Vendor (ASV). This is required on a quarterly basis, to ensure network security. More information is available at www.pcicomplianceguide.org/pcicompliance-vendors.html.