Download Tenasys Driver
- Download Tenasys Driver Download
- Download Tenasys Driverpack
- Download Tenasys Driver Printer
- Download Tenasys Drivers
Public Safety Scheduling, Timekeeping & Overtime Management
InTime is a provider of workforce management software that is purpose-built for public safety and trusted by 500+ public safety agencies. With over 25 years in the public safety sector, InTime has the proven expertise in understanding the complex scheduling needs of law enforcement, fire, corrections, and dispatch agencies. Purpose, TenAsys includes software drivers with the latest INtime software that enable on-chip tasks to communicate using global objects or high-performance Ethernet-compatible protocols. The resulting system is highly scalable, as platforms with different numbers of cores can be used, and also in capability, as the support for Windows.
Secure Your Copy of the Public Safety Overtime Management Research Report
Participate in the survey for the chance to win a $100 Visa® Gift Card
InTime is a provider of workforce management software that is purpose-built for public safety and trusted by 500+ public safety agencies. With over 25 years in the public safety sector, InTime has the proven expertise in understanding the complex scheduling needs of law enforcement, fire, corrections, and dispatch agencies.
InTime is comprised a breath of capabilities and modules, the core of which is Staff Scheduling, TimeKeeping, and Overtime Management. With InTime, agencies can increase productivity, reduce costs, ensure compliance, and minimize risk.
See what our Public Safety customers are saying about InTime
IMPROVE PRODUCTIVITY
Ensure data-driven decision making and scheduling by enabling fully integrated, automated management of essential workforce planning tasks.
We used to call officers on the phone when we would have overtime to get filled and it was a laborious process. Now we can post it, they get a phone notification, they’ll sign up for the shift, and we’re done in 5 minutes.
REDUCE COSTS
Reduce overtime costs through tracking and assignment tools and improve cost recovery by streamlining reimbursements for specific emergencies (FEMA, COVID-19).
Before, we had 3 or 4 different sheets that we had to update to keep everything accurate. Now, everything is in one place and it’s easy to transfer officers from one shift to another. It’s beyond belief how much time and money is saved.
ENSURE COMPLIANCE
Manage staffing and maintain compliance with union and agency-specific policies through rules-based scheduling and alerts.
InTime made us more efficient to track who was supposed to be in those assignments. More importantly, we were able to print out the documentation who the officers were, and the exact hours worked.
MINIMIZE RISKS
Minimize agency liability and unnecessary risks to staff and the general public through improved visibility of inappropriate scheduling.
It felt like errors happened all the time, at least once a week- it’s just human error. Now, I don’t ever see the errors, I love that it catches if there is less than 8 hours between schedules or double bookings.
SCHEDULING
Build, maintain, & control the scheduling of your workforce, no matter how large your organization or how complex your operation.
TIMEKEEPING
InTime’s scheduling system contains all your employee overtime, timebanks, leaves and complex pay rules. All that data automatically populates your timesheets; meaning the only thing you have to manage is approvals.
OVERTIME
Streamline your overtime management process and use InTime’s advanced reporting to help reduce unnecessary overtime.
PUBLIC SAFETY
We know that law enforcement, corrections, dispatch, fire and EMS have some of the toughest scheduling requirements. That is why InTime can be configured to handle your specific rules, while still being easy to use on a daily basis.
CITIES & COUNTIES
All your departments and agencies managed autonomously in one centralized secure system. The results are improved operational oversight, cross-department scheduling and more effective reporting.
PRIVATE SECURITY
With a user-friendly location-based scheduling interface, InTime simplifies contract commitments and controls costs to give you improved productivity, reduced overhead, and higher margins.
ORANGE COUNTY LAW & JUSTICE
How does Orange County manage 10,000 employees and 145,000 subpoenas/year?
WINNEBAGO COUNTY SHERIFF
How did Winnebago County Sheriff reduce officer burnout?
CAL FIRE
How did CALFIRE reduce the time they spend managing overtime by 98%?
CALGARY POLICE SERVICE
How CPS consolidated 4,000+ spreadsheets with InTime
Home → Current INtime Product Information → INtime Product Release Information → INtime 5 Update 5.1 Release Notes
This file contains the latest product information and installation notes. You can view it after installation at INtimehelpreadme.rtf. This package contains a number of updates compared to the original 5.0 release. See the specific notes for this update below for details.
Update 5.1 for the INtime 5 SDK contains new feature support and bug-fixes.
Contents
- Getting Started
- Product Features
- Installation
- New in INtime 5 SDK version 5.1.13140.0
- Changes in INtime 5 SDK (version 5.1)
- New in INtime 5 (version 5.0)
- Other changes in this release
- More information and technical support
See the following documents:
- Quick Start Guide: Introduces the product and leads the reader through installation and some example applications. Provided as a PDF format file with the product.
- INtime Help: Full reference to the INtime SDK and product, available in three formats:
- A standalone help file
- An integrated help collection for Visual Studio
- A web-based collection at TenAsys' website
This Software Development Kit (SDK) consists of tools, utilities and resources to be installed on a Windows system and integrated with the Visual Studio product in order to generate applications for the INtime family of products, which consist of the following:
- INtime for Windows
- INtime Distributed RTOS
It can install an INtime for Windows runtime and provides tools to install an INtime Distributed RTOS runtime on a separate PC host.
INtime 5 SDK installation
Your product has been shipped with license management technology. The details of this are described in a separate document included in the product package. Be sure to read the document before attempting to install the product.
If you have been provided with the installation materials from a download, launch the installation from the intimexxx_installer.exe executable. This will insure that the installation will proceed with the correct permissions and will check for prerequisites.
You can install INtime 5 SDK on the following versions of Windows (both 32- and 64-bit versions supported):
- Windows 8
- Windows 7
- Windows Server 2008 R2
- Windows Vista, Service Pack 1 or later
- Windows Server 2008
- Windows XP, Service Pack 3 or later
- Windows 2003 Server, R2 service pack 2 or later
Note: TenAsys recommends installing the most recent service pack available at the time of this release. Note that Windows service packs issued after this release may require an update from TenAsys.
Refer to the Quick Start Guide for specific installation instructions.
INtime Distributed RTOS runtime installation
The target system must be a PC platform capable of booting from CDROM, or from USB media, with IDE or SATA interface and a drive attached to that controller. The runtime kit is initially booted from the product CDROM or from a USB flash drive, and installed on a hard drive connected to one of the platform's IDE or SATA ports.
A keyboard is required for installation; both PS/2 and USB types are supported.
A supported network card is required for connection to the Windows development system. Supported cards are listed at this location:
Refer to the Quick Start Guide for specific installation instructions.
Support for Windows 8
This release of the INtime SDK may be installed on Windows 8 (32- or 64-bit versions). The Windows 8 platform requires INtime to be installed in Dedicated mode only, even on the 32-bit platform because of internal resource conflicts.
Support for Visual Studio 2012
This release of the INtime 5 SDK contains support for Visual Studio 2012. This includes all the INtime Wizards, add-ins, project support, debugging and help features of previous Visual Studio versions.
A major difference of the VS2012 implementation is that the INtime Project object (INTP package) has been removed. This means that INtime projects no longer include the INtime project icon but instead the INtime project properties are carried by means of a Visual Studio 'Platform' definition. Another small change is that the license is checked only by the debugger component now, whereas in previous versions it was checked by the INTP object. The practical effect of this is that no special action is required to edit and compile an INtime project now, only the debugger action requires an SDK license to be present.
Support for new Intel processors and chipsets
Support has been added to the kernel for the new 'Haswell' family of processors from Intel, known as 'Core i-series 4th Generation' processors. This support identifies the CPU and attempts to configure it for best real-time performance.
General network support has also been added for the new Intel i217 Ethernet controllers found in the 8-Series/C-220 chipsets supporting the new processors.
Serial drivers new hardware support
Support for the Oxford Semiconductor PCI Express interface components has been added to the comrocket driver.
Extended support in LNC (Local Node Configuration) library
The LNC library has been reorganized and additional functionality provided. The original calls will be kept for compatibility purposes. The new calls include support for Advanced Settings, Autoload, and Network configuration.
See http://support.tenasys.com/INtimeHelp_5/#abt_lnc.html for full details of the library.
The following problems have been resolved in this update compared to the original INtime 5 SDK release:
INtime Distributed RTOS runtime activation methods updated
There are additional and improved methods for activating INtime Distributed RTOS systems. Please refer to the RTOS-activation.pdf file in the INtimehelp directory for further details.
C library
Microsoft-style names for POSIX functions such as open, read, write, close have been added to the C library to further simplify the porting of code from Windows. The following functions have been added:
In direct.h: _getcwd _mkdir _rmdir _chdir
In io.h: _open _close _read _write _access _chmod _chsize _creat _dup _dup2 _eof _filelength _lseek _ltell _mktemp _setmode _tell _mask _unlink
In math.h: _copysign _copysignf _hypot _hypotf _j0 _j1 _jn _matherr _y0 _y1 _yn _logbf _nextafterf _finitef _isnanf
INtime Configuration now exports network settings
The INtime Configuration tool now exports network settings along with the other configuration settings when exporting nodes. As part of the associated import operation, the directories %INTIMECFG%nodeetc will be first deleted before the import starts.
Bluescreen when using MSI interrupts in shared mode in Windows 7
A rare Windows STOP(0xC8) could occur when using a device using MSI for interrupt delivery, when in shared mode on Windows 7 (32-bits) only. The STOP event was due to a Windows interrupt handler being executed in an invalid context; changing how the EOI was delivered from the INtime interrupt handler fixes the problem.
Memory leak in iwin32 CreateThread (RtCreateThread)
Drivers technotrend sound cards & media devices. A memory leak occurred when an iwin32 thread is created then deleted. A single segment was leaked on each cycle. This has been fixed in this update.
JitterCS sample project fails to compile
A required resource file is not installed with the JitterCS sample project for Visual Studio 2008. This file has been re-added in this update.
DSM: RegisterRtDependency updated for backwards compatibility
The RegisterRtDependency API has been superseded since INtime 4.0 by RegisterRtDependencyEx because the DSM database is now distributed between the participating nodes in an INtime system. In the last release, this change caused a different behavior in INtime 5.0 compared to previous versions of INtime which may have caused some applications using DSM calls to fail. The old behavior has now been preserved in the original calls and the new functionality added to the Ex versions of the calls.
INtime Distributed RTOS filesystem improvements
The FAT filesystem on INtime Distributed RTOS has been updated for performance and reliability. Substantially faster write times are possible compared to the original release.
INtime Distributed RTOS: not possible to rename the root node
Renaming the root node renders the system unbootable. This has been fixed in this update.
Memory leak in Node Detection service
Download Tenasys Driver Download
A memory leak occurred in the Node Detection service when multiple connect and disconnect cycles to a remote system took place. This has been resolved in this update.
INtime networking (network7)
The network interface driver for Broadcom interfaces could experience a fault during reallocating internal memory buffers. This has been fixed in this update.
Fixed a failure in netlib:getaddrinfo() that was induced by the stack not being loaded. If istack.rta is now loaded then this function now just returns TRUE.
HPE drivers
The hpeOpen() call with PROBE_ONLY now supports checking for interrupt support. If using PROBE_ONLY, interrupts may be verified by setting the interrupt parameter to ALL_INTERRUPTS. If the verification fails, the return value for hpeOpen may be the error return value from SetRtInterruptHandlerEx().
RT Class Library (rtclass)
The debug versions of this library now output debug messages to stderr, instead of stdout.
Global Objects network process (gobs_net.rta)
A memory leak in this process has been resolved. After a while this leak could cause calls to CopyRtData/ ntxCopyRtData to fail due to the lack of buffers. This would cause Visual Studio debug sessions and Intex sessions to fail.
Web Administration (websadm)
INtime Distributed RTOS: on selecting the Reboot button, display the main screen before performing the reboot so avoid multiple accidental reboots.
On activating a node via the web browser, close the browser window and perform an automatic reboot.
Note: When using the Firefox internet browser to configure an INtime RTOS system, the browser window will not automatically close after a reboot of the RTOS system; do not try to correct this by setting the Dom.allow_scripts_to_close_windows to true in about:config, as that will cause the reboot not to be performed.
WinNtxProxy
The WinNtxProxy component was updated to allow it to be correctly installed as a service on Windows 7.
USB3
The USB stack has been updated to allow for three transfer structures per endpoint, thus allowing overlapped asynchronous I/O operations.
Syslogd (Distributed RTOS syslog service)
A change was made to allow the service to forward syslog message over the network, even though it is started before the network service.
RT Application Loader (ldrta.exe)
A change introduced into INtime 5.0 to work around mapping limitations in Windows was found to cause corruption to some sections on loading in some circumstances. This could cause faults during the loading of a module (.RTA or .RSL). This has been resolved in this update.
The following features are new in INtime 5
INtime Distributed RTOS
This release of the INtime SDK introduces INtime Distributed RTOS, a product which takes the multi-core features developed in INtime 4.0 and targets a standalone PC platform, without Windows.
The same real-time performance and features found in the INtime for Windows product are now available on a standalone system. Platform requirements for the INtime Distributed RTOS target include a x86-compatible processor, at least 128 MB of RAM, ATA or SATA interface with disk device, a support network card, and a keyboard for installation. Debugging of your application takes place directly on the target platform using NTX technology to connect to the SDK host. The same binary RTA files may be run on INtime for Windows or INtime Distributed RTOS targets.
Global Objects networking (GOBSnet)
An extension of the Global Objects technology allows the access to objects on a different host to occur over the network between multiple INtime hosts, as well as between the nodes on those hosts. A single process resides on one node and forwards requests to the other nodes on the host, requiring only a single network connection no matter how many nodes are present on the host. Improvements in the node to node interface on the same host have been made, resulting in higher performance between nodes. The same technology has been used in a new implementation of the NTX interface for Windows applications, allowing them to interface to INtime applications anywhere.
Message Queue objects
A new system object is introduced in this release. The Message Queue is an object for transferring binary strings from one process to another, and in some ways resembles a flexible data mailbox. The maximum size of a message is configurable per queue object, and there is a sideband mechanism for passing the occasional message which is larger than that limit. Optimization has been carried out to maximize performance when transferring messages between nodes on the same host by exploiting shared memory techniques. Finally, the queue object is created of a fixed size so that system memory is not consumed by an unserviced queue.
The NTX interface has been extended to allow Windows applications to use these objects too.
Support for USB 3.0
This release introduces a completely new USB stack which includes support for USB 3.0 and the XHCI controllers found on newer PC platforms. In addition the application interface has been improved for better performance and functionality.
The original implementation of the USB stack (USBSS) has also been included in order to support legacy applications generated on older versions of the product, but it is recommended that new development takes place using the new software.
There are also new versions of the USB serial drivers and USB tools.
New INtime for Windows configuration library (LNC)
This release includes a new library of configuration primitives intended to allow the user to provide customized configuration utilities. The Local Node Configuration (LNC) library allows many of the configuration operations performed by the INtime Configuration utility to be performed from a user-generated application. The INtime Configuration utility has been migrated in order to use the library.
New default memory size of INtime for Windows nodes
The default node memory size for INtime For Windows nodes on creation is now 32 MB. With more services available by configuration the default memory size has been increased to accommodate them.
Download Tenasys Driverpack
New options for istack.rta
Two new command-line options have been added to istack.rta (the INtime network stack) to assist in driver configuration:
-L List the Ethernet devices which are accessible from the current node and recognized by the network stack and its drivers. Lists the device IDS, name and interface name by which it may be accessed from the stack.
Download Tenasys Driver Printer
-LL List all of the Ethernet devices currently supported by the stack and its drivers. Shows the device ID and a short description of each device.
New default memory configuration for istack.rta
The default memory configuration has been changed from a fixed, 4 MB heap to a standard C-library heap. The value vm.kmem_size in loader.cfg was changed from 0x0400000 to 0x0. This means that istack.rta with a single interface will consume much less memory by default.
Download Tenasys Drivers
For more information about TenAsys and the INtime products go to the website at http://www.tenasys.com/intime.
For online documentation, go to http://support.tenasys.com/intimehelp_5.
For technical support, go to http://www.tenasys.com/support.