IMG Home PageIMG ProductsProduct DownloadsOrdering InformationTechnical Support and Frequently Asked QuestionsDeveloper's Corner and UtilitiesAbout IMG
CustomersIMG ResellersMedia InformationIMG Events / Trade ShowsUseful LinksIMG Contact InformationIMG Information / Policies
Translate

IMG KnowledgeBase & Frequently Asked Questions

IMG Logo



Search FAQ's

Keyword Keyword Search Help
Category Type Product Version

PC1505120404
(Windows XP) Enabling Remote Desktop reports problem with IMGGINA2.DLL

Use updated version of DLL (originally for Windows Server 2003)
Original ID: PC205339
Category: CommonType: Problem/Resolution Product: Logon ModuleVersion: 1.77



PC1505120405
(Windows 2000/XP) User Shell differences, script problems, issues with IMGLOGON.DLL, need access to other logon capabilities

Download Patch for My-T-Pen, My-T-Soft, or My-T-Touch
Original ID: PC205340
Category: CommonType: Problem/Resolution Product: Logon ModuleVersion: 1.75



PC1505120406
(Windows 2000/XP) Home Drive entered in User Properties not available after logon

  • This is caused by updates in Windows 2000 that are not backwards compatible to NT. Suggested workaround is to use NET USE command in logon script (e.g. if Home drive is H:, use NET USE H: \\WIN2KDOMAIN\USERS\[Current User])
  • Alternative: Use the Patch176.

  • Original ID: PC205341
    Category: CommonType: Problem/Resolution Product: Logon ModuleVersion: 1.75



    PC1505120407
    Need 1.75 version release capabilities (Windows 2000/XP Logon Scripts do not execute) for pre 1.75 versions

    Replace IMGLOGON.DLL with 1.75 version. This is a security issue with Windows 2000 servers for the Win32 API call NetUserGetInfo. Prior to 1.75, this is called in the security context of the local machine, rather than the authenticated user. Most likely seen on native Windows 2000 servers as domain controllers with user logging onto the domain (rather than local machine).
    Original ID: PC205342
    Category: CommonType: Problem/Resolution Product: Logon ModuleVersion: 1.70



    PC1505120408
    Touch Logon Button appears prior to touchscreen driver being loaded (e.g. ELO), confusing or annoying users

    We have added a modifiable delay prior to showing the first dialog display - Replace the IMGLOGON.DLL & IMGLOGON.EXE files with the downloads below.
    Original ID: PC205343
    Category: CommonType: Problem/Resolution Product: Logon ModuleVersion: 1.70



    PC1505120409
  • (Windows 2000/XP) Non-Administrative User at Logon reverts to Demo Logon and disables IMG Logon Module.
  • (Windows 2000/XP) Timeout at username / password screen does not re-display "Touch Logon to begin".

  • The best solution is to replace the IMGLOGON.DLL & IMGLOGON.EXE files with the downloads below. If this is not desirable, see advanced notes below.
  • To resolve license problem without replacing files, user rights in registry must be addressed. (User needs "Set Value" permission in HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\Current Version & sub-keys)
    Original ID: PC205344
  • Category: CommonType: Problem/Resolution Product: Logon ModuleVersion: 1.70



    QG1506120499
    How "Secure" are the My-T-Soft Logon Utilities?

    The supported logon option for Windows 2000/XP is tagged as "My-T-Soft 2 Keyboard (Windows 2000 and later)" in the "My-T-Soft Logon Utilities" provided by the software. This feature uses an integration to the MSGINA.DLL (or possibly other third party GINAs, if so configured) where the software only monitors specified events (as supported by the Microsoft API for working within the GINA (Graphical Identification aNd Authentication)), so the keyboard can be shown during the logon screens, in the context of the secure WinLogon desktop. In short, this means that there is no security actions taken at all by our software - all that happens is the virtual keyboard is brought up within the GINA/WinLogon desktop, and can be used by the user to generate keystrokes for entering name/domain/password - ALL authentication takes place as it normally would by the underlying Microsoft software. The My-T-Soft software just provides a mechanism to enter text into the required fields in the secure WinLogon desktop.

    The Secure Attention Sequence (SAS) is generated via the Microsoft provided API programming interface, so a physical keyboard Control-Alt-Delete keystroke is not required. However, the software does require a physical touchscreen press / mouse click event (assuming there are no other virtual event software capabilities present).

    The security of this approach hasn't really been much of concern to those familiar with the technical aspects of what is going on at this level. Microsoft specifically publicly provides the GINA/WinLogon API for smart cards, biometric, and other identification schemes, but ALL authentication is done by the Microsoft software. In no way, shape, or form does this level have access to, or perform any authentication - My-T-Soft's particular implementation just provides a mechanism to enter the name/domain/password to the underlying security levels. So if you accept Microsoft's security, all that happens with the My-T-Soft software is it provides another way to enter the text (name/password) that is used to submit to the authentication system. Here is their documentation regarding this: MSDN - WinLogon and Gina

    If there are further questions, or need for clarification, please contact IMG Technical Support.

    Category: GeneralType: Question/Answer Product: Logon Module

    Notes:



    IMG Home PageIMG ProductsProduct DownloadsOrdering InformationTechnical Support and Frequently Asked QuestionsDeveloper's Corner and UtilitiesAbout IMG
    CustomersIMG ResellersMedia InformationIMG Events / Trade ShowsUseful LinksIMG Contact InformationIMG Information / Policies