IntelliCAT Migration to Windows 7 User Support Document March 21, 2014 Manual Part Number: 99875658-1.01 REGISTERED TO ISO 9001:2008 MagTek I 1710 Apollo Court I Seal Beach, CA 90740 I Phone: (562) 546-6400 I Technical Support: (888) 624-8350 www.magtek.
Copyright © 2014 MagTek, Inc. Printed in the United States of America Information in this publication is subject to change without notice and may contain technical inaccuracies or graphical discrepancies. Changes or improvements made to this product will be updated in the next publication release. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of MagTek, Inc.
1. Detailed Steps for migrating to Windows 7, 32/64bit Using MtAdmIn.MDB local and networked including reference to SQL Before you begin the new install, open DATA ENTRY on the old PC, click on HELP ABOUT. If the Version is 1.8.XX or lower, the IntelliCAT setup is referred to as a 1.XX install. New IntelliCAT Software is required. Contact your MagTek Representative at 562-546-6400 to order new Software. If the Version 2.
Step 1 Copy Old INTCAT.INI file COPY the INTCAT.INI located in C:\Windows\ from the Old PC and PASTE it to the desktop on the new PC for review and use with the new installation. Step 2 – Verify IntellICAT version Open the INTCAT.INI file on the desktop of the new PC. Review the old INTCAT.INI file, if the DO NOT MODIFY section is present, the IntelliCAT setup is already using 2.XX IntelliCAT, skip Steps 3 and 4.
Step 7 – Setting Commports On the desktop INTCAT.INI file, Change the ICCommPort (Motorized IntelliCoder) under the [ADMIN] section and change the ICCommPort and IPCommport (IntelliPIN) under the [COMMUNICATION] section to match the PORT settings defined in DEVICE MANAGER, and noted after the driver install was completed. IntelliPIN: Set device to match what is in DEVICE MANAGER under PORTS 64 bit PC only: IntelliStripe 380 - set the device to match what is in DEVICE MANAGER under PORTS.
Step 10 A - SAVE Old XP 1.XX Local Install Files - If Step 3 and 4 were performed, SAVE the files below. This was an old XP 1.XX original install. Save files to a thumb drive or network folder. First SAVE, then EDIT and RENAME where it states Mandatory. If the renaming is not completed as required, the new installation will fail to work as the MtAdmin.MDB file between versions 1.XX is not compatible with the 2.XX MtAdmin.MDB file. This is a critical Step as highlighted below Old Files From 1.
Step 12 - Local UDL Customization/Creation – O.S. Dependent If the [ODBC] section is networked, SKIP THIS STEP. If the [ODBC] section was present in the old INTCAT.INI file, all of the UDL’s were copied in Step 11 and will need to be copied into each new PC as the migration takes place. No changes are required to the UDL’s unless Win 7, 64bit is being implemented. See changes below regarding Win 7, 64bit. 12 A - Migrating XP 1.XX to 2.
12 B - Migrating from XP 1.XX to 2.XX (Win 7, 64bit) Create an IntelliCAT64.UDL, Operator64.UDL (Optional) and a Controller64.UDL (Optional) XP 1.XX to 2.XX (Win 7, 64 bit) - Create a local IntelliCAT64.UDL, a local Operator64.UDL (if present in old PC setup) and a local Controller64.UDL (if using Controller) following the instruction in the document entitled (Creating 64bit UDL for 64bit PC for MtAdmin.MDB) On the Desktop INTCAT.
12 E - Controller UDL's, if in use, may have different names UDL's for WorkQConnect - examples are Controller.UDL, Work.UDL, Production.UDL, etc. and are only required in a Networked Environment. Typical examples of the path structure to the WorkQConnect as located in the [ODBC] section are: Local Controller UDL’s local path structure Action Required (32 bit) WorkQConnect="File Name=C:\Program Files\MagTek\IntelliCAT\Controller.UDL" No change required.
SQL Users Only Action required If a SQL database is being used in an old XP 2.XX and you are migrating to a Win 7 32bit environment, a Controller.UDL is not required but one may be in use. 32bit PC - Controller.UDL, if in use No change is required to the current *.UDL's including the Controller.UDL 64bit PC - Controller64 UDL, create new UDL Complete Step 12B as referenced above (create a new Controller64.
Step 14 - Local/Network Setup If the desktp INTCAT.INI file also includes some Mapped Drives or UNC paths, this means that the old IntelliCAT Setup is a partial local/network setup Review the Networked Location of the IntelliCAT install by following the mapped drive or UNC path. 14 A - Locate the old MTAdmin.MDB that is in use Example of current 1.X setup = \\server1\Magtek\IntelliCAT\MTAdmin.mdb.......... The file will continue to be used during the migration - DO NOT TOUCH this file.
Step 17 - Network UDL customization/creation - 1.XX conversion to 32/64bit 17 A - 32bit - Customize IntelliCAT.UDL and create an Operator.UDL and a Controller.UDL if present for a networked install XP 1.XX to 2.XX (Win 7 32bit) - Follow the instructions in Step 12 A. The [ODBC] section will reference a mapped drive or UNC path structure as in the example below Change the [ODBC] to reflect new UDL's (32bit) PC [ODBC] CardHistConnect="File Name=\\server1\MagTek\IntelliCAT\IntelliCAT.
Win 7 64BIT and SQL Action Required If a Controller.UDL is present and using SQL Make one change. For (Win 7 64bit only), Note: If a SQL database is being used in XP 2.XX and you are migrating to a Win 7 64bit environment, a Controller. UDL is not required but one may be in use. If in use, follow this step. Complete Step 12 B as referenced above (create a new Controller64.
Step 23 - Activation Open Data Entry on the Desktop and email support@magtek.com with the 8 digit challenge number or call 888-624-8350 for the Activation codes. Do not close Data Entry until you receive the activation codes or you will have to reopen Data Entry and provide MagTek with a new 8 digit challenge number. Step 24 - Log off as Administrator. Log off as Administrator and have a regular user log in.
