文件列表:

TANNER.L-EDIT (0, 2006-04-07)
TANNER.L-EDIT\TANNER.L-EDIT.PRO.V10.0.WITH.LVS.V10.0-CROSSFiRE (0, 2006-04-07)
TANNER.L-EDIT\TANNER.L-EDIT.PRO.V10.0.WITH.LVS.V10.0-CROSSFiRE\c-le10 (0, 2006-04-07)
TANNER.L-EDIT\TANNER.L-EDIT.PRO.V10.0.WITH.LVS.V10.0-CROSSFiRE\c-le10\COMCTL (0, 2006-04-07)
TANNER.L-EDIT\TANNER.L-EDIT.PRO.V10.0.WITH.LVS.V10.0-CROSSFiRE\c-le10\COMCTL\50COMUPD.EXE (509984, 2005-01-21)
TANNER.L-EDIT\TANNER.L-EDIT.PRO.V10.0.WITH.LVS.V10.0-CROSSFiRE\c-le10\crack (0, 2006-04-07)
TANNER.L-EDIT\TANNER.L-EDIT.PRO.V10.0.WITH.LVS.V10.0-CROSSFiRE\c-le10\crack\install.txt (1333, 2006-03-26)
TANNER.L-EDIT\TANNER.L-EDIT.PRO.V10.0.WITH.LVS.V10.0-CROSSFiRE\c-le10\crack\TannerLicenseInstaller (0, 2006-04-07)
TANNER.L-EDIT\TANNER.L-EDIT.PRO.V10.0.WITH.LVS.V10.0-CROSSFiRE\c-le10\crack\TannerLicenseInstaller\tlicinst.exe (184320, 2005-01-21)
TANNER.L-EDIT\TANNER.L-EDIT.PRO.V10.0.WITH.LVS.V10.0-CROSSFiRE\c-le10\crack\TannerLicenseInstaller\tprotutl.dll (110592, 2005-01-21)
TANNER.L-EDIT\TANNER.L-EDIT.PRO.V10.0.WITH.LVS.V10.0-CROSSFiRE\c-le10\crack\Tanner_Macros_Keygen (0, 2006-08-09)
TANNER.L-EDIT\TANNER.L-EDIT.PRO.V10.0.WITH.LVS.V10.0-CROSSFiRE\c-le10\crack\Tanner_Macros_Keygen\artwork_macros_kg.exe (96256, 2005-01-21)
TANNER.L-EDIT\TANNER.L-EDIT.PRO.V10.0.WITH.LVS.V10.0-CROSSFiRE\c-le10\crack\Tanner_Macros_Keygen\path to dxf plugin acs key file (65, 2006-10-28)
TANNER.L-EDIT\TANNER.L-EDIT.PRO.V10.0.WITH.LVS.V10.0-CROSSFiRE\c-le10\crack\Tanner_Macros_Keygen\path to plot plugin acs key file (65, 2006-10-28)
TANNER.L-EDIT\TANNER.L-EDIT.PRO.V10.0.WITH.LVS.V10.0-CROSSFiRE\c-le10\crack\Tanner_v2003_licgen (0, 2006-08-09)
TANNER.L-EDIT\TANNER.L-EDIT.PRO.V10.0.WITH.LVS.V10.0-CROSSFiRE\c-le10\crack\Tanner_v2003_licgen\license.src (856, 2005-01-21)
TANNER.L-EDIT\TANNER.L-EDIT.PRO.V10.0.WITH.LVS.V10.0-CROSSFiRE\c-le10\crack\Tanner_v2003_licgen\metaloxydefieldeffectransistor.dll (197120, 2005-01-21)
TANNER.L-EDIT\TANNER.L-EDIT.PRO.V10.0.WITH.LVS.V10.0-CROSSFiRE\c-le10\crack\Tanner_v2003_licgen\Tanner1.tlu (91170, 2007-01-14)
TANNER.L-EDIT\TANNER.L-EDIT.PRO.V10.0.WITH.LVS.V10.0-CROSSFiRE\c-le10\crack\Tanner_v2003_licgen\tannerkg.exe (230400, 2005-01-21)
TANNER.L-EDIT\TANNER.L-EDIT.PRO.V10.0.WITH.LVS.V10.0-CROSSFiRE\c-le10\DATA.TAG (104, 2005-01-21)
TANNER.L-EDIT\TANNER.L-EDIT.PRO.V10.0.WITH.LVS.V10.0-CROSSFiRE\c-le10\DATA1.CAB (31366584, 2005-01-21)
TANNER.L-EDIT\TANNER.L-EDIT.PRO.V10.0.WITH.LVS.V10.0-CROSSFiRE\c-le10\DATA1.HDR (83234, 2005-01-21)
TANNER.L-EDIT\TANNER.L-EDIT.PRO.V10.0.WITH.LVS.V10.0-CROSSFiRE\c-le10\LANG.DAT (4679, 2005-01-21)
TANNER.L-EDIT\TANNER.L-EDIT.PRO.V10.0.WITH.LVS.V10.0-CROSSFiRE\c-le10\LAYOUT.BIN (609, 2005-01-21)
TANNER.L-EDIT\TANNER.L-EDIT.PRO.V10.0.WITH.LVS.V10.0-CROSSFiRE\c-le10\LDRIV.530 (0, 2006-04-07)
TANNER.L-EDIT\TANNER.L-EDIT.PRO.V10.0.WITH.LVS.V10.0-CROSSFiRE\c-le10\LDRIV.530\I386 (0, 2006-04-07)
TANNER.L-EDIT\TANNER.L-EDIT.PRO.V10.0.WITH.LVS.V10.0-CROSSFiRE\c-le10\LDRIV.530\I386\RAINPORT.HLP (10279, 2005-01-21)
TANNER.L-EDIT\TANNER.L-EDIT.PRO.V10.0.WITH.LVS.V10.0-CROSSFiRE\c-le10\LDRIV.530\I386\RAINTEMP.SYS (20480, 2005-01-21)
TANNER.L-EDIT\TANNER.L-EDIT.PRO.V10.0.WITH.LVS.V10.0-CROSSFiRE\c-le10\LDRIV.530\I386\RAINVTMP.DLL (11776, 2005-01-21)
TANNER.L-EDIT\TANNER.L-EDIT.PRO.V10.0.WITH.LVS.V10.0-CROSSFiRE\c-le10\LDRIV.530\I386\RNBOVTMP.DLL (16896, 2005-01-21)
TANNER.L-EDIT\TANNER.L-EDIT.PRO.V10.0.WITH.LVS.V10.0-CROSSFiRE\c-le10\LDRIV.530\I386\SENTINEL.HLP (10929, 2005-01-21)
TANNER.L-EDIT\TANNER.L-EDIT.PRO.V10.0.WITH.LVS.V10.0-CROSSFiRE\c-le10\LDRIV.530\I386\SENTTEMP.HLP (10300, 2005-01-21)
TANNER.L-EDIT\TANNER.L-EDIT.PRO.V10.0.WITH.LVS.V10.0-CROSSFiRE\c-le10\LDRIV.530\I386\SENTTEMP.SYS (64512, 2005-01-21)
TANNER.L-EDIT\TANNER.L-EDIT.PRO.V10.0.WITH.LVS.V10.0-CROSSFiRE\c-le10\LDRIV.530\OEMSETUP.INF (705, 2005-01-21)
TANNER.L-EDIT\TANNER.L-EDIT.PRO.V10.0.WITH.LVS.V10.0-CROSSFiRE\c-le10\LDRIV.530\RANI386.DLL (29184, 2005-01-21)
TANNER.L-EDIT\TANNER.L-EDIT.PRO.V10.0.WITH.LVS.V10.0-CROSSFiRE\c-le10\LDRIV.530\SETUPX86.EXE (27136, 2005-01-21)
TANNER.L-EDIT\TANNER.L-EDIT.PRO.V10.0.WITH.LVS.V10.0-CROSSFiRE\c-le10\LDRIV.530\SNTI386.DLL (38400, 2005-01-21)
TANNER.L-EDIT\TANNER.L-EDIT.PRO.V10.0.WITH.LVS.V10.0-CROSSFiRE\c-le10\LDRIV.533 (0, 2006-04-07)
TANNER.L-EDIT\TANNER.L-EDIT.PRO.V10.0.WITH.LVS.V10.0-CROSSFiRE\c-le10\LDRIV.533\SETUP.EXE (18912, 2005-01-21)
... ...

Sentinel System Drivers Version 5.33 README.TXT File Copyright (c) 1991-1997 Rainbow Technologies, Inc. All Rights Reserved. The Sentinel System Drivers provide a communication path between your protected application and the Sentinel key. The driver you install depends on the operating system you are using. This readme file describes the installation procedures for all Sentinel System Drivers. See the appropriate section for the procedure about the driver that you are installing. ----------------------------------- README File Contents ----------------------------------- 1.0 File List 2.0 Changes Since Last General Release 3.0 Windows NT Driver Installation Procedure 3.1 Windows NT Driver Configuration 3.2 Windows NT Driver Un-install 3.3 Recovery Mechanisms on NT-4.0 3.4 Windows NT - DOS Device Driver 4.0 Windows 3.x Driver Installation Procedure 4.1 Windows 3.x Driver Configuration 4.2 Windows 3.x Driver Un-install 5.0 OS/2 Driver Installation Procedure 5.1 OS/2 Driver Configuration 6.0 Windows 95 Driver Installation Procedure 6.1 Windows 95 Driver Configuration 6.2 Windows 95 Driver Un-install 7.0 Autodetecting Setup Program ----------------------------------- 1.0 File List ----------------------------------- README.TXT - This file. SENTINEL.DDP - OS/2 installation script file. SETUP.EXE - A program design to detect the active OS and launch the appropriate Installation program. DOS\SENTDOS.SYS - DOS Device Driver for use with some interfaces under Windows NT. OS2\INSTALL.CMD - OS/2 installation command file. OS2\SENTINEL.SYS - OS/2 Sentinel Driver. WIN_31\INSTALL.EXE - Install program for Windows 3.x Sentinel Driver. WIN_31\SENTINEL.386 - Windows 3.x Sentinel Driver. WIN_NT\SETUPAXP.EXE - Sentinel Driver installation program for Windows NT on ALPHA platforms. WIN_NT\SETUPX86.EXE - Sentinel Driver installation program for Windows NT on INTEL platforms. WIN_NT\SETUPPPC.EXE - Sentinel Driver installation program for Windows NT on Power PC platforms. WIN_NT\SNTI386.DLL - Sentinel Driver setup DLL for Windows NT on Intel platforms. WIN_NT\SNTALPHA.DLL - Sentinel Driver setup DLL for Windows NT on Alpha platforms. WIN_NT\SNTPPC.DLL - Sentinel Driver setup DLL for Windows NT on Power PC platforms. WIN_NT\I386\SENTINEL.HLP - Help file for the WinNT Sentinel Driver setup DLL. WIN_NT\I386\SENTTEMP.SYS - WinNT Sentinel Driver for x86 systems. WIN_NT\I386\RNBOVTMP.DLL - WinNT Sentinel Virtual Device Driver for x86 systems. WIN_NT\ALPHA\SENTINEL.HLP - Help file for the WinNT Sentinel Driver setup DLL. WIN_NT\ALPHA\SENTTEMP.SYS - WinNT Sentinel Driver for Alpha systems. WIN_NT\ALPHA\RNBOVTMP.DLL - WinNT Sentinel Virtual Device Driver for ALPHA systems. WIN_NT\PPC\SENTINEL.HLP - Help file for the WinNT Sentinel Driver setup DLL. WIN_NT\PPC\SENTTEMP.SYS - WinNT Sentinel Driver for Power PC systems. WIN_NT\PPC\RNBOVTMP.DLL - WinNT Sentinel Virtual Device Driver for Power PC systems. WIN_95\SENTINEL.VXD - Windows 95 Sentinel Driver. WIN_95\SENTW95.EXE - Sentinel Driver installation program for Windows 95. WIN_95\SENTW95.DLL - Sentinel Driver installation DLL. WIN_95\SENTW95.HLP - Windows help file used by the DLL. WIN_95\SENTSTRT.EXE - Program used to initialize the VxD. ----------------------------------------------------- 2.0 Changes Since Last General Release (PD-5.30) ----------------------------------------------------- 1. MIPS Windows NT is no longer supported. (PD-5.31) 2. Corrected an NT driver installer problem that caused the installation to fail when the driver files were located in subdirectories named i386, ALPHA, and PPC - and those subdirectories were not positioned at the lowest level of the pathname. (PD-5.31) 3. Modified the NT and Win95 driver installer to return non-zero error code if an error is encountered during the installation. (PD-5.31) 4. Added a command line switch /E (or /e) to NT and Win95 driver installer to prevent any error message from being displayed during the installation. (PD-5.31) 5. Added code to remove the 'Sentinel' entry from NT Service Control Manager when the Sentinel driver is uninstalled. (PD-5.32) 6. Setup.exe is now included to detect the active OS, and to launch the appropriate Sentinel System Installation program. Please see 7.0 Autodetecting Setup Program for more details. (PD-5.33) 7. Corrected an Win95 driver problem that caused the key access to fail when an ECP-capable printer such as HP LaserJect 5L is attached with active print job(s). (PD-5.33) 8. Modified the NT driver to avoid the possibilities of affecting other time-critical processes. (PD-5.33) 9. Localized the Windows 3.1, Windows 95, and Windows NT driver installers to support English, Chinese, French, German, and Spanish. Following table shows the components and the status of localization, "x" means a language is supported. (PD-5.33) ENGLISH CHINESE FRENCH GERMAN SPANISH ================================================================== DOS x OS/2 x Win 3.1 x x x x x Win 95 x x x x x Win NT Intel x x x x x Win NT Alpha x Win NT PowerPC x 10. Modified the NT driver IRP allocation scheme to avoid incompatibilities with Radisys Corporation's INtime software. (PD-5.33) 11. Removed SENTINEL.ZIP, OEMSETUP.INF, and INSTALL.BAT from the release file list. (PD-5.33) ------------------------------------------------ 3.0 Windows NT Driver Installation Procedure ------------------------------------------------ Note: administrative privilege is required to install the NT driver. 1. Make a backup copy of the diskette. 2. Under the Microsoft Windows NT Main group, double click on "Command Prompt". (On NT 4.0 or later, select "Run" from the Taskbar) 3. Change drive to the floppy drive containing the Driver Diskette. \WIN_NT. In case of CD-ROM distribution, change the current directory to \PRODUCT\DRIVERS\\WIN_NT, where is one of the languages supported. (On NT 4.0 or later, click the "Browse..." button and select the directory described above) 4. Run driver setup program -- Type SETUPX86 (for Intel systems), SETUPPPC (for PowerPC systems), or SETUPAXP (for DEC Alpha systems) at the command prompt. There are several command line options: 1. /q Quiet mode. Normal dialogs are not displayed but error messages will be displayed. 2. /e Suppress all messages. (Overwrites the /q switch) Both normal dialogs and error messages not displayed. Look for non-zero return code from the installer so installation error can be detected. 3. /pxxx Path, where xxx is the path of files to be installed. Specify the path of files to be installed. Otherwise, files will be copied from the default directory. 4. /o Overwrite the existing Sentinel Driver. By default, if the existing driver is newer than the one to be installed, the installer will not copy over it. Optionally, we provide an integrated setup program, SETUP.EXE, at the root directory of the driver software that autodetects the operating system and invoke the correct driver setup program for you. Please refer to the "Autodetecting Setup Program" section for more details. 5. A window with the title bar "Sentinel Driver Setup Program" is displayed. 6. Select "Functions" and then "Install Sentinel Driver" from the menu bar. 7. A dialog box with the default path for the NT driver is displayed. Change the drive letter if necessary and click "OK". 8. The Sentinel Driver and associated files are copied to the hard disk. One of the DLLs, SNTI386.DLL, SNTALPHA.DLL, or SNTPPC.DLL and SENTINEL.HLP are copied to \%SYSTEMROOT%\SYSTEM32. SENTTEMP.SYS is copied to the file \%SYSTEMROOT%\SYSTEM32\DRIVERS\SENTINEL.SYS. %SYSTEMROOT% is the directory where Microsoft Windows NT has been installed. 9. If the driver installation is successful, a dialog box with the message "Sentinel Driver Files Copied Successfully" is displayed. 10. When complete, a dialog box with the message "Driver Installed! Restart your system" is displayed. 11. Click "OK" to continue. 12. Restart your computer. Manual Installation of Sentinel System Driver for Windows NT ------------------------------------------------------------ PD-5.33 and later no longer supports manual installation. ------------------------------------------------- 3.1 Windows NT Driver Configuration Procedure ------------------------------------------------- Note: administrative privilege is required to configure the NT driver. If your system setting has been changed and you would like to reconfigure the Sentinel Driver, perform the following steps. 1. Under the Microsoft Windows NT Main group, double click on "Control Panel". (On NT 4.0 or later, select "Settings" from the Taskbar and click on "Control Panel") 2. Under the Control Panel double click on "Drivers". (On NT 4.0 or later double click on "Multimedia", select the "Devices" tab, and double click on "Other Multimedia Devices") 3. Select "Sentinel for i386 System" in the installed driver list box. 4. Click the "Setup" button. (On NT 4.0 or later, click on "Settings..." button. 5. Click the "Edit" button to edit an existing parallel port setting or click the "Add" button to add a new parallel port setting. Select "OK" after you finish the port configuration. 6. A dialog box with the message "Your driver setting has changed" is displayed. You will need to exit and restart Windows NT so that the new setting can take effect." 7. If you have any other application running at the background with unsaved data, choose "Don't Restart Now". Quit all the application and restart Windows NT, Otherwise select "Restart Now". ------------------------------------------------ 3.2 Windows NT Driver Un-install ------------------------------------------------ 1. Under the Microsoft Windows NT Main group, double click on "Command Prompt". (On NT 4.0 or later, Select "Run" from the Taskbar) 2. Change drive to the floppy drive containing the Driver Diskette. In case of diskette distribution, change the current directory to \WIN_NT. In case of CD-ROM distribution, change the current directory to \PRODUCT\DRIVERS\WIN_NT. (On NT 4.0 or later, click the "Browse..." button and select the directory described above) 3. Run driver setup program -- SETUPX86 (for Intel systems), SETUPPPC (for PowerPC systems), or SETUPAXP (for DEC Alpha systems) from the command prompt with the /u (or /U) switch. 1. Use Command-line options: /q /u - Quietly removes the existing driver. 2. Via Pull-down menu - Run setup program and select "Remove Sentinel Driver" from the "Function" menu. 4. When complete, a dialog box with the message "Sentinel Driver Removed" is displayed. 5. Click "OK" to continue. Note: Some files may not be removed until you restart your computer. ------------------------------------------------- 3.3 Recovery Mechanisms on NT-4.0 ------------------------------------------------- ---------------------------------------------------------------------------------- THIS SECTION APPLIES ONLY IF YOU HAVE SENTINEL DRIVER VERSION PD-5.16 AND EARLIER ---------------------------------------------------------------------------------- Rainbow has encountered an issue with the final release (build 1381) of WindowsNT 4.0. The following two scenarios will cause WindowsNT 4.0 to not boot properly: A. A change to the default configuration settings of Rainbow's System Driver prior to installing WindowsNT 4.0 (the installation will not complete successfully), or B. A change to the default configuration settings of Rainbow's System Driver after WindowsNT 4.0 is already installed (the re-boot will not complete successfully) Upon re-booting the machine, WindowsNT will display a blue screen to the the user with a message that an error has occurred in the NT Kernel. As of 9/30/96, Rainbow has released a new version of the Sentinel System Drivers, version PD-5.17, to resolve this issue. It is strongly recommended that the new driver (PD-5.17 or later) be downloaded (from the WEB page at www.rnbo.com or the electronic bulletin board at (714)450-7485) and installed. To recover from the blue error screen, use one of the following methods: Method 1: If the user falls under category "B" above, and the user currently has the blue screen on their machine, then they should go ahead and re-boot the machine. When WindowsNT is starting, the user will be prompted to press the SPACEBAR to return to the last known good configuration. Press the SPACEBAR as soon as this message appears. Then press the "L" key and press enter. WindowsNT should re-boot without problems. Remove the Sentinel System Driver by highlighting "Sentinel for i386 Systems" via the Control Panel / MultiMedia / Devices / Other MultiMedia Devices applet and press Remove. Re-boot the machine (this step is mandatory, do not skip this!), install the WindowsNT System Driver from the PD-5.17 (or later) release and restart the system. Method 2: If the user has already re-booted their machine in an effort to repair the system, then method 1 cannot be used. Instead, take the following steps assuming another operating system is installed or the file system is FAT (File Allocation Table) * Re-boot to another OS other than NT (or use a DOS floppy disk) * Rename sentinel.sys to temp.sys in the \winnt40\system32\drivers directory * Re-boot to WindowsNT 4.0 * Rename temp.sys to sentinel.sys in the \winnt40\system32\drivers directory * Remove the Sentinel System Driver by highlighting "Sentinel for i386 Systems" via the Control Panel / MultiMedia / Devices / Other MultiMedia Devices applet and press Remove. * Re-boot the machine (this step is mandatory, do not skip this!) * Install the PD-5.17 (or later) WindowsNT Sentinel System Driver * Re-boot the machine Method 3: If the user has already re-booted their machine in an effort to repair the system, then method 1 cannot be used. And, the user cannot use method #2 because they do not have another operating system to boot to, do not have a DOS boot disk, or their machine is a pure NT machine with a NTFS file system, follow these steps: * Re-boot the machine and access the CMOS setup program * Locate the settings for the parallel port. One of the options should be DISABLE. Change the port so it is disabled. This will prevent NT from detecting any parallel ports and cause parport.sys to not load. Since Rainbow's Sentinel driver depends on parport.sys, we too will not load. Exit CMOS and save the settings. * Allow the machine to continue with the boot process. * Remove the Sentinel System Driver by highlighting "Sentinel for i386 Systems" via the Control Panel / MultiMedia / Devices / Other MultiMedia Devices applet and press Remove. * Re-boot the machine (this step is mandatory, do not skip this!) * Again access the CMOS setup program and re-enable the parallel port. Be sure to save the settings. Allow the machine to continue to boot. * Install the PD-5.17 (or later) WindowsNT Sentinel System Driver * Re-boot the machine ------------------------------------------------- 3.4 Windows NT - DOS Device Driver ------------------------------------------------- It is possible, though unlikely, that on some systems, applications using the Watcom C/C++ with Rational DOS/4G and Microsoft Visual C/C++ with Phar Lap TNT DOS Extender may be unable to communicate with our Windows NT Device Driver. In the unlikely event that you experience problems running your application under Windows NT, a DOS Device Driver is provided which allows your application to communicate with the Windows NT Device Driver on systems where it otherwise could not. To install this device driver, do the following: 1. Copy the file SENTDOS.SYS to the target system's hard disk. 2. Add the following statement to the custom Config file used by your application's PIF file, or if your application does not use a custom Config file, to the system's CONFIG.NT file. device=%path%\sentdos.sys Where %path% is the actual path where SENTDOS.SYS resides. ------------------------------------------------- 4.0 Windows 3.x Driver Installation Procedure ------------------------------------------------- 1. Make a backup copy of the diskette. 2. Select File|Run under the Program Manager. 3. Type "A:\WIN_31\INSTALL.EXE" at the dialog box. Change the drive letter A: to the floppy disk drive where the Driver Diskette is located if you are running from a drive other than A: In case of the CD-ROM distribution, Type {CD-ROM DRIVE}:\PRODUCT\DRIVERS\WIN_31\INSTALL.EXE where {CD-ROM DRIVE} is the drive letter corresponding to CD-ROM drive on your system. There are three command line options: 1. /q Quiet mode. Normal dialogs (warning, information) are not displayed. Error messages are displaye ... ...

近期下载者：

相关文件：

评论：[我要评论] [举报此文件]

收藏者：