DOCSLIB.ORG

Mystery Behind Windows Registry

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Mystery Behind Windows Registry Mystery Behind Windows Registry Index of Windows Registry Guide 1. What is Registry - an introduction 2. The Structure of Registry · HKEY_LOCAL_MACHINE (all of the settings for the system) · HKEY_CURRENT_CONFIG (a subset of HKEY_LM that details the current configuration) · HKEY_USERS (settings for the users of the machine) · HKEY_CURRENT_USER (subset of HKEY_USERS that details out the profile of the current user) · HKEY_CLASSES_ROOT (a subset of HKEY_LM & all of the software "classes" and extensions) · HKEY_DYNAMIC_DATA (dynamic information about PC that is built at startup) 3. Registry Corruption - Problem & Solutions · Registry Problems - Corruption of Registry · Protecting the Registry - Backup Solutions · Recovering from Registry Failure 4. Registry Tips and Secrets (Only in html version at http://srana.virtualave.net/winreg.htm ) 5. Some essential software for rescue 6. Inf files 7. Remote Registry Editing What is Registry and It's Role What is the Registry? The Registry has been made out to be a phenomenal mystery probably due to the CLSID keys alone and as such has inspired a number of books, faqs websites etc. It is very unfortunate that Microsoft has chosen to deal with the Registry and Registry editing as a "black art," leaving many people in the dark as to the real uses of all the settings in the systems. Microsoft's refusal to adequately, and publicly, supply information about the correct settings is extremely frustrating and added further mystery to registry. Certainly, more damage has and will be done because of lack of knowledge than because of too much information. The Windows Registry is a set of data files used to help Windows control hardware, software, the user's environment, and the "look and feel" of the Windows interface. The Registry is contained in two files in the Windows directory (in NT they are called "hives"): system.dat and user.dat, with backup copies system.da0 and user.da0. The Registry database is accessed with regedit.exe which is in the Windows directory. Formerly, in older version of windows (before windows 95) these functions were performed by WIN.INI, SYSTEM.INI, and other .INI files that are associated with applications. The evolution of application and operating system control has three distinct levels: · In Legacy Windows systems, SYSTEM.INI and WIN.INI held all the control functions for the operating systems and applications. Essentially, SYSTEM.INI controlled the hardware while WIN.INI controlled the desktop and applications. All changes to drivers, fonts, settings, and preferences would be stored in the .INI files. Any new application that was installed added pointers to the .INI files. Those pointers would then be referenced in the application's code. · Additional .INI files that controlled the applications were added by programmers who needed more control than was available because of the limited size of the WIN.INI and SYSTEM.INI files. For example, Microsoft included with Excel a file called EXCEL.INI, which held the options, settings, defaults, and other information critical to making Excel work correctly. The only pointer that was then required in WIN.INI was to the EXCEL.INI path and filename. · The Registry was initially developed as a reference file for data-file associations to applications. It was expanded to include all functions for 32-bit operating systems and applications. Originally, SYSTEM.INI and WIN.INI controlled all Windows and application features and access. It worked well when average users used only a few applications. As the number and complexity of applications grew, so did the number of entries to the .INI files. The downside of this approach, in a growing environment, is that everyone would make changes to the .INI files when applications were added to the system. However, no one ever removed references from their .INI files when they removed applications, so SYSTEM.INI and WIN.INI continued to get larger and larger. Each incremental size increase meant slower performance. Even upgrading applications presented its challenges. The upgrade would add entries but never take the old ones away, presumably to ensure compatibility if another program was to access the settings. Because the maximum size of an .INI file is 64KB, an obvious problem arose. To counter the problem, vendors started supplying .INI files of their own, with just pointers to the specific .INI files in WIN.INI and SYSTEM.INI. The downside of this approach was the proliferation of .INI files throughout the system and the hierarchical nature of access. If WIN.INI made a particular setting, and an application's .INI file overrode that setting, who was responsible and where should--or could--a system-wide setting that had priority be made? The Registry is a set of files that control all aspects of the operating system and how it works with outside events. Those "events" range from accessing a hardware device directly to how the interface will react to a specific user to how an application will be run and much more. It was designed to work exclusively with 32-bit applications, and file size is limited to a about 40MB. The Registry is complex by its very nature, and on purpose. What the Registry Does The Registry is the data file for all 32-bit hardware/driver combinations and 32-bit applications in both Windows NT and Windows 95. Sixteen-bit drivers do not work in NT, so all devices are controlled through the Registry, even those normally controlled by the BIOS. In Windows 95, 16-bit drivers will continue to work as real-mode devices, and they use SYSTEM.INI for control. Sixteen-bit applications will work in either NT or 95, and the applications still refer to WIN.INI and SYSTEM.INI files for information and control. Without the Registry, the operating system would not have the necessary information to run, to control attached devices, to launch and control applications, and to respond correctly to user input. Data File for OS to Hardware/Drivers The Registry is a database of all the settings and locations of 32-bit drivers in the system. When the OS needs to access hardware devices, it uses drivers, even if the device is a BIOS-supported device. Non-BIOS-supported devices that are installed must also have a driver. The drivers are independent of the OS, but the OS needs to know where to find them, the filename, the version, and other settings and information. Without Registry entries for each of the devices, they would not be usable. Data File for OS to Applications When a user attempts to launch an application, the Registry supplies application information to the OS so the application can be found, the correct data file locations are set, and other settings are available. The Registry holds information about default data and auxiliary file locations, menus, button bars, window status, and other options. It also holds installation information such as the date of installation, the user who installed the software, the version number and date, and sometimes the serial number. Depending on the actual software installed, it may contain other application-specific information. Two Types of Control Although, in general, the Registry controls all 32-bit applications and drivers, the type of control it exercises is based on users and computers, not on applications or drivers. Every Registry entry controls a user function or a computer function. User functions would include the desktop appearance and home directory, for example. Computer functions are related to installed hardware and software, items that are common to all users. Some application functions affect users, and others affect the computer and are not specifically set for an individual. Similarly, drivers may be user-specific, but, most of the time, they are for general use by the computer. All of the settings discussed in the rest of the book are separated by user and computer. Some examples of user-type functions controlled by the Registry are · Control Panel functions · Desktop appearance and icons · Network preferences · Explorer functionality and features Some of those functions are the same regardless of user; others are user-specific. Computer-related control items are based on the computer name, without respect to the logged-in user. An example of this type of control would be installing an application. The availability and access to the application is constant, regardless of the user; however, icons to launch the application are dependent on the user logging in to the network. Network protocol availability and priority is based on the computer, but current connections are based on user information. Here are some examples of computer-based control items in the Registry: · Access control · Login validation · File and print sharing · Network card settings and protocols · System performance and virtual memory settings Without the Registry, Windows 95 and Windows NT would not be possible. They are too complex to be controlled by the older .INI files, and their expansion capabilities allow almost unlimited installation and use of applications. The Registry is, however, much more complex than the .INI files, and understanding how it works, what it does, and how to work with it is critical for effective system administration. The Registry controls all 32-bit applications and their functions on the system, plus the interaction between multiple applications, such as copying and pasting. It also controls all the hardware and drivers. Though most of the settings are made during installation and through the Control Panel, understanding the Registry is fundamental to reliable and capable management of Windows NT and Windows 95 systems. The Structure of the Registry The Registry is a complex database of information that was built in a hierarchical fashion by the writers and programmers of Windows. Much like a community that is made of estates that are made of buildings that are made of walls that are made of bricks, the Registry has many components.
Load more

Recommended publications
  • Server Operating System
    Server Operating System ® White Paper Guide to Microsoft® Windows NT® 4.0 Profiles and Policies © 1997 Microsoft Corporation. All rights reserved. The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication. This White Paper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT. Microsoft, the BackOffice logo, MS-DOS, Windows, and Windows NT are registered trademarks of Microsoft Corporation. Other product or company names mentioned herein may be the trademarks of their respective owners. Microsoft Corporation • One Microsoft Way • Redmond, WA 98052-6399 • USA 0997 Abstract This guide provides information and procedures for implementing Microsoft® Windows NT® 4.0 Profiles and Policies on client workstations and servers. A Microsoft Windows NT 4.0 User Profile describes the Windows NT configuration for a specific user, including the user’s environment and preference settings. A System Policy is a set of registry settings that together define the computer resources available to a group of users or an individual. With the addition of System Policies and the new User Profile structure to Windows NT 4.0, network administrators have a greater ability to control the user environment than they have ever had before. This document provides the details that administrators need to know to implement a rollout of User Profiles and System Policies under Windows NT 4.0.
    [Show full text]
  • Command Line Interface User's Guide
    Dell™ OpenManage™ Server Administrator Version 5.2 Command Line Interface User's Guide www.dell.com | support.dell.com Notes and Notices NOTE: A NOTE indicates important information that helps you make better use of your computer. NOTICE: A NOTICE indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. ____________________ Information in this document is subject to change without notice. © 2006 Dell Inc. All rights reserved. Reproduction in any manner whatsoever without the written permission of Dell Inc. is strictly forbidden. Trademarks used in this text: Dell, the DELL logo, PowerEdge, and OpenManage are trademarks of Dell Inc.; Microsoft, Windows, Windows Server, MS-DOS, and Windows NT are registered trademarks of Microsoft Corporation; SUSE is a registered trademark of Novell, Inc. in the United States and other countries; Red Hat and Red Hat Enterprise Linux are registered trademarks of Red Hat, Inc.; Intel, Pentium, and Itanium are registered trademarks and Intel386 is a trademark of Intel Corporation; AMD, AMD Opteron, AMD-V, and AMD PowerNow! are trademarks of Advanced Micro Devices, Inc.; VESA is a registered trademark of Video Electronic Standards Association; UNIX is a registered trademark of The Open Group in the United States and other countries; OS/2 is a registered trademark of International Business Machines Corporation. Other trademarks and trade names may be used in this document to refer to either the entities claiming the marks and names or their products. Dell Inc. disclaims any proprietary interest in trademarks and trade names other than its own. December 2006 Contents 1 Introduction .
    [Show full text]
  • The Last Great Commodore 64 Commercial Software Sale
    theMONITOR CommodoreUsersGroupofSaskatchewan 361729thAvenue Regina,SK S4S2P8 Tel:(306)584-1736 BBS:(306)586-6608 President eachother.Membershipdues($15)arepro-rated, TristanMiller 584-1736 basedonaJanuarytoDecemberyear.Anaddi- VicePresident tional$5willbechargedformemberswishing ByronPurse 586-1601 theirnewsletterstobemailedtothem. Secretary/Treasurer KenDanylzczuk 545-0644 Anyone interested in computing is welcome to Editor attendanymeeting.Membersareencouragedto TristanMiller 584-1736 submitpublicdomainandsharewaresoftware AssistantEditors forinclusionintheCUGSDiskLibrary.These ByronPurse 586-1601 programsaremadeavailabletomembersat$3.00 R LyndonSoerensen 565-2167 each(discountedpriceswhenbuyingbulk).Since KeithKasha 522-5317 someprogramsonthedisksarefrommagazines, 64Librarian individualmembersareresponsiblefordeleting StanMustatia 789-8167 anyprogramthattheyarenotentitledtobylaw 128Librarian (youmustbetheownerofthemagazineinwhich O KeithKasha 522-5317 theoriginalprogramwasprinted).Tothebestof MemberatLarge ourknowledge,allsuchprogramsareidentifiedin HerbThompson 543-3460 theirlistings. T TheMonitorispublishedmonthlybytheCom- Otherbenefitsofclubmembershipincludeaccess modore User's Group of Saskatchewan toourdiskcopyingservice,tomakebackupsof I (CUGS).MeetingsareheldonthefirstWednes- copy-protectedsoftware,anymemberswhoowna dayofeverymonthinMillerHighSchool'scafete- modemandwishtocallourbulletinboardwill ria annex, unless otherwise noted. The next receiveincreasedaccesstothemessageandfile meetingwillbeheldonDecember1,1993from areas.Theboardoperatesat300to2400baud,24
    [Show full text]
  • Hack Attacks Revealed
    Hack Attacks Revealed A Complete Reference with Custom Security Hacking Toolkit John Chirillo This netLibrary eBook does not include the ancillary media that was packaged with the original printed version of the book. Publisher: Robert Ipsen Editor: Carol A. Long Assistant Editor: Adaobi Obi Managing Editor: Micheline Frederick New Media Editor: Brian Snapp Text Design & Composition: Thomark Design Designations used by companies to distinguish their products are often claimed as trademarks. In all instances where John Wiley & Sons, Inc., is aware of a claim, the product names appear in initial capital or ALL CAPITAL LETTERS. Readers, however, should contact the appropriate companies for more complete information regarding trademarks and registration. Copyright © 2001 by John Chirillo. All rights reserved. Published by John Wiley & Sons, Inc. No part of this publication may be reproduced, stored in a retrieval system or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, scanning or otherwise, except as permitted under Sections 107 or 108 of the 1976 United States Copyright Act, without either the prior written permission of the Publisher, or authorization through payment of the appropriate per- copy fee to the Copyright Clearance Center, 222 Rosewood Drive, Danvers, MA 01923, (978) 750- 8400, fax (978) 750-4744. Requests to the Publisher for permission should be addressed to the Permissions Department, John Wiley & Sons, Inc., 605 Third Avenue, New York, NY 10158-0012, (212) 850-6011, fax (212) 850-6008, E-Mail: PERMREQ @ WILEY.COM. This publication is designed to provide accurate and authoritative information in regard to the subject matter covered. It is sold with the understanding that the publisher is not engaged in professional services.
    [Show full text]
  • Dell Server Administrator Version 7.4.1 Release Notes
    Server Administrator 7.4.1 Release Notes Release Type and Definition Server Administrator This document contains updated information for the "Server Administrator User's Guide" and any other technical documentation included with Server Administrator. NOTE: System Management software, including the Server Administrator (Server Administrator), is available only on the "Systems Management Tools and Documentation" DVD. The Server Administrator (Server Administrator) documentation includes the "User's Guide", "Messages Reference Guide", "CIM Reference Guide", "Command Line Interface (CLI) Guide", "SNMP Reference Guide", and "Compatibility Guide". You can access the documentation from the Systems Management Tools and Documentation DVD or from "dell.com/support/manuals". Version 7.4.1 Release Date December 2014 Previous Version 7.4.0 Importance RECOMMENDED: It is recommended to apply this update during your next scheduled update cycle. The update contains feature enhancements or changes that will help keep your system software current and compatible with other system modules (firmware, BIOS, drivers and software). Platform(s) Affected For a complete list of supported Dell PowerEdge systems and supported Operating systems, see the Dell Systems Software Support Matrix available in the required version of OpenManage Software at dell.com/openmanagemanuals. What is Supported Hardware Requirements • Minimum of 2 GB RAM • Minimum of 512 MB free hard drive space • Administrator rights • Monitor with a minimum screen resolution of 800 x 600. The recommended screen resolution is at least 1024 x 768 Software Requirements • Supported operating system and web browser. • TCP/IP connection on the managed system and the remote system to facilitate remote system management. • Supported systems management protocol standard.
    [Show full text]
  • Verde Staff User's Guide
    Staff User’s Guide Version 2.0 (SFX 4.x) CONFIDENTIAL INFORMATION The information herein is the property of Ex Libris Ltd. or its affiliates and any misuse or abuse will result in economic loss. DO NOT COPY UNLESS YOU HAVE BEEN GIVEN SPECIFIC WRITTEN AUTHORIZATION FROM EX LIBRIS LTD. This document is provided for limited and restricted purposes in accordance with a binding contract with Ex Libris Ltd. or an affiliate. The information herein includes trade secrets and is confidential. DISCLAIMER The information in this document will be subject to periodic change and updating. Please confirm that you have the most current documentation. There are no warranties of any kind, express or implied, provided in this documentation, other than those expressly agreed upon in the applicable Ex Libris contract. This information is provided AS IS. Unless otherwise agreed, Ex Libris shall not be liable for any damages for use of this document, including, without limitation, consequential, punitive, indirect or direct damages. Any references in this document to third‐party material (including third‐party Web sites) are provided for convenience only and do not in any manner serve as an endorsement of that third‐ party material or those Web sites. The third‐party materials are not part of the materials for this Ex Libris product and Ex Libris has no liability for such materials. TRADEMARKS ʺEx Libris,ʺ the Ex Libris bridge , Primo, Aleph, Alephino, Voyager, SFX, MetaLib, Verde, DigiTool, Preservation, URM, Voyager, ENCompass, Endeavor eZConnect, WebVoyage, Citation Server, LinkFinder and LinkFinder Plus, and other marks are trademarks or registered trademarks of Ex Libris Ltd.
    [Show full text]
  • QWK Mail Reader
    BBS Archives - Off-Line Mail Readers http://archives.thebbs.org/ra110c.htm Off-Line Mail Readers 1ST-200.ZIP 1620K 07-20-1995 1stReader 2.00 QWK offline mail reader from Sparkware. This archive contains the rest of the basic 2.00 release. It includes manuals, address book, RIP and database support. 1ST-200C.ZIP 485K 07-20-1995 1stReader 2.00 QWK offline mail reader from Sparkware. This archive contains the spelling checker, 1STEDIT text editor and FLI support modules. (File 3 of 6 in 2.00 release) 1ST-200D.ZIP 934K 07-20-1995 1stReader 2.00 QWK offline mail reader from Sparkware. This archive contains the multimedia sound files used by the full 1stReader 2.00 release. You do not need them if you do not have a sound card. (File 4 of 6 in 2.00 release) 1ST-200E.ZIP 238K 07-20-1995 1stReader 2.00 QWK offline mail reader from Sparkware. This archive contains support for third party programmers who are interested in writing utilities for the 2.00 release. Includes full documentation on the 1stReader API interface. (File 5 of 6 in 2.00 release) 1ST-200F.ZIP 368K 07-20-1995 1stReader 2.00 QWK offline mail reader from Sparkware. This archive contains the 80386 (and higher) compiled version of the 1ST.EXE program. Do NOT use if you own a 80286 or 8088 system. (File 6 of 6 in 2.00 release) 1ST-BBS.ZIP 108K 07-20-1995 1stReader 2.00 sysop's kit. This archive tells you, the sysop, how to setup your own {QWKID}.BBS file so 1stReader can be "preconfigured" and ready to work seamlessly with your bulletin board system.
    [Show full text]
  • Alt.Am Yellow Netpages™ USENET Newsgroups
    Yellow NetPages™ USENET Newsgroups a.bsu – alt.am 81 a.bsu.programming ak.admin alt.1d alt.activism.children Alaskan network news administration. One-dimensional imaging, & the think- Open discussion of political issues a.bsu.religion ing behind it. about children. ak.bushnet.thing a.bsu.talk Alaskan Public Access Networking. alt.2600 alt.activism.d aaa.inu-chan The magazine or the game system. A place to discuss issues in ak.config Inu-chan by Kenso KATO (Moderated) You decide. alt.activism. Alaskan regional heirarchy configura- ab.arnet tion. alt.2600.codez alt.activism.death-penalty No description. For people opposed to capital punish- ab.general ak.test ment. Items of general interest in Alberta, Messages with the beta-nature. alt.2600.crackz Canada. Broken software protection. alt.adjective.noun.verb.verb.verb akr.freenet The penultimate alt group. ab.jobs Discussion about the Akron Regional alt.2600.hackerz Jobs in Alberta, Canada. Free-Net. Just what is so cool about not be able alt.adoption to spell? For those involved with or contemplat- ab.politics akr.internet ing adoption. Discussion of politics in Alberta, Internet access in the Akron, Ohio, alt.2600.hope.announce Canada. area. Hackers on Planet Earth announce- alt.adoption.agency ments. Licensed non-profit adoption agency abg.acf-jugend alabama.announce information. abg.acf-termine Announcements of interest to everyone alt.2600.hope.d in Alabama. (Moderated) Hackers on Planet Earth discussion. alt.aeffle.und.pferdle abg.acf-vor German TV cartoon characters das alabama.config alt.2600.hope.tech Aeffle und das Pferdle.
    [Show full text]
  • CIS Microsoft Windows 10 Enterprise (Release 1607) Benchmark
    CIS Microsoft Windows 10 Enterprise (Release 1607) Benchmark v1.2.0 - 06-28-2017 This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International Public License. The link to the license terms can be found at https://creativecommons.org/licenses/by-nc-sa/4.0/legalcode To further clarify the Creative Commons license related to CIS Benchmark content, you are authorized to copy and redistribute the content for use by you, within your organization and outside your organization for non-commercial purposes only, provided that (i) appropriate credit is given to CIS, (ii) a link to the license is provided. Additionally, if you remix, transform or build upon the CIS Benchmark(s), you may only distribute the modified materials if they are subject to the same license terms as the original Benchmark license and your derivative will no longer be a CIS Benchmark. Commercial use of CIS Benchmarks is subject to the prior approval of the Center for Internet Security. 1 | P a g e Table of Contents Overview ............................................................................................................................................................... 32 Intended Audience ........................................................................................................................................ 32 Consensus Guidance ..................................................................................................................................... 32 Typographical Conventions .....................................................................................................................
    [Show full text]
  • Administrator Guide
    FRONTDOOR Administrator Guide FRONTDOOR Administrator Guide Copyright © 1998, 1999, 2001 Definite Solutions HB; All rights reserved. All Definite Solutions products and trademarks are trademarks or registered trademarks of Definite Solutions HB; with the exception of FrontDoor which is a registered trademark of Joaquim Homrighausen. Other brands and product names are trademarks or registered trademarks of their respective holders. This publication is protected by international copyright laws and treaty provisions. It may only be distributed and used in accordance with those laws and treaty provisions. DEF-E-FDADMIN-Z-1/2001-EP Produced in Sweden. To the memory of Catharina Frödin and Alva Gårdlund. And to Alexander, Janet, Christian, Katja, and Igor. Party on Fred, we miss you. Special thanks to Bruce Bodger for his help with the production of the entire FrontDoor package. Special thanks to Colin Turner for his help with the production of this document. Special thanks to Jim Louvau for his help with the initial development of the communications module for the OS/2 version of FrontDoor. FrontDoor Administrator Guide TABLE OF CONTENTS TABLE OF CONTENTS ............................................................................................................................................................ 4 1. INTRODUCTION ................................................................................................................................................................... 8 ABOUT THIS DOCUMENT ............................................................................................................................................................
    [Show full text]
  • CIS Microsoft Windows 10 Enterprise (Release 1703) Benchmark V1.3.0 - 10-30-2017
    CIS Microsoft Windows 10 Enterprise (Release 1703) Benchmark v1.3.0 - 10-30-2017 This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International Public License. The link to the license terms can be found at https://creativecommons.org/licenses/by-nc-sa/4.0/legalcode To further clarify the Creative Commons license related to CIS Benchmark content, you are authorized to copy and redistribute the content for use by you, within your organization and outside your organization for non-commercial purposes only, provided that (i) appropriate credit is given to CIS, (ii) a link to the license is provided. Additionally, if you remix, transform or build upon the CIS Benchmark(s), you may only distribute the modified materials if they are subject to the same license terms as the original Benchmark license and your derivative will no longer be a CIS Benchmark. Commercial use of CIS Benchmarks is subject to the prior approval of the Center for Internet Security. 1 | P a g e Table of Contents Overview ............................................................................................................................................................... 32 Intended Audience ........................................................................................................................................ 32 Consensus Guidance ..................................................................................................................................... 32 Typographical Conventions .....................................................................................................................
    [Show full text]
  • Wibukey Developer Guide
    WibuKey Developer Guide for Windows, Mac OS, Linux/UNIX on IBM compatible PCs and Macintosh Version 6.11, Edition February 2013 WibuKey Developer Guide © Copyright 2003-2013 by WIBU-SYSTEMS AG, Rueppurrer Strasse 52-54, 76137 Karlsruhe, Germany Printed in Germany All rights reserved. No part of this documentation, the accompanying software, or other components of the described product may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, for any purpose other than the personal use of the purchaser without the express written permission of Wibu-Systems. While the data contained in this document has been written with all due care, Wibu-Systems does not warrant or assume responsibility that the data is free from errors or omissions. Wibu-Systems expressly reserves the right to change programs or this documentation without prior notice. Trademarks WIBU®, CodeMeter®, SmartShelter® are registered trademarks of Wibu- Systems. All other brand names and product names used in this documentation are trade names, service marks, trademarks, or registered trademarks of their respective owners. Wibu-Systems is member of: PCMCIA since 1993 USB Implementers Forum since 1997 SD Card Association since 2007 SIIA Software & Information Industry Association since 1998 Bitkom, Bundesverband Informationswirtschaft, Telekommunikation und Neue Medien (German Association of Information Technology, Telecommunications, and New Media) since 2003 VDMA, Verband Deutscher Maschinen- und Anlagenbau
    [Show full text]