![]() In this case the INtime kernel continues to operate until it decides to release Windows and allows it to completely shutdown. The INtime product has a feature which can intercept bluescreen events (Windows “STOP” or "Bugcheck" events) so that if an event occurs which causes a bluescreen, the system will freeze. The system freezes or resets when I start the kernel See Deploying Your INtime System and Local Node Configuration. Configuration files may result in errors when the hosts differ in the number of cores or in memory size. This also confuses the INtime Configuration Tool. This may be caused by applying a configuration from one host onto a host with more cores, resulting in incorrect memory descriptions in the registry. This reserves memory at the top of available RAM before Windows is ever booted and prevents Windows from using it. If running on a 32-bit version of Windows and there is 4 GB or less of RAM installed, consider changing the configuration to “Exclude memory from Windows”. If you have configured memory from the Windows non-paged pool and you find a message “memory not available”, Windows was unable to allocate the required memory in a single contiguous allocation. Memory not available (INtime for Windows) If you receive a message about license failure, inspect the cases in the “License Failures” section. Possible failures may include the following: Look for error messages from the INtimeKernelManager service, which should explain why the kernel failed to start. Open the Windows Event Viewer and inspect the INtime log. To access the event log, click on INtime status monitor icon and select Event Viewer from popup menu. I started the INtime kernel but it did not start (INtime for Windows) If you have multiple development kits each with their own key, be sure to use the correct key with each development kit. A fingerprint with RAID enabled will create a license that will be invalidated after a disk reformat. Make sure that RAID is disabled in the BIOS before reformatting the disk drive to avoid invalidating the license for future drive reformatting. Some default BIOS settings enable RAID even with only one disk. However, if the storage medium is a RAID volume then there is no unique disk ID so the license reverts to using the Windows volume ID. After INtime 5 the disk hardware ID is used instead so this is no longer an issue. If you replace or reformat the disk drive then your license will be invalidated. Prior to INtime 5, a node-locked license is keyed in part from the volume ID of the system volume of the Windows installation. Reformatting the hard drive will invalidate the license Incorrect license installedīe careful that when installing a license generated from a fingerprint that the license is being installed on the correct host. ![]() Restoring the clock value will allow the system to continue to function. If your clock battery failed or the system clock was changed back by more than one day after you install the software, the license management software considers this action as an attempt to defeat the licensing, so will fail. ![]() See the documention on License Manager for more information. ![]() This topic lists problems you may encounter while running INtime software, and explains how to avoid or resolve those problems. The system freezes when I start my application.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |