开源项目-p4tin-GoAws.zip

开源项目-p4tin-GoAws.zip,用go编写的go aws开发克隆。对我刚开始的评论要温和一点。

立即下载

上传者： weixin_38744435 时间： 2019-10-21

VB编程资源大全（英文源码 DirectX）

1,CODE_UPLOAD137411132001.zip
A 3Dimensional park with lolly pop trees and flying birds. Programmed with Direct3D (Retained Mode). A good program to learn some simple direct3d in. Requires the DirectX7 SDK to use
2,CODE_UPLOAD39693132000.zip
This code shows you how to use DirectX 7 and the RM Canvas control to create nice animations that are smooth and simple. It shows you how to create lights, frames animation and more.
3,CODE_UPLOAD140811232001.zip
Space Quest is the temporary name for the single player RPG (in progress) that currently P4R14H(art) and I(programming) are working on. It has nothing to do with space travel or anything (more Lord of the Rings-ish), just read the readme.txt in the zip
4,CODE_UPLOAD76727112000.zip
This shows you the basics of using Direct Draw and Direct Sound. It shows you how to create a sprite and move it around the screen
5,CODE_UPLOAD1093810242000.zip
CHECK THIS OUT! This is a really cool effect. Stand in the middle of a 3D world and use the mouse to rotate the camera around. All running at over 60 frames per second
6,CODE_UPLOAD15673312001.zip
This is a DirectX car game made in VB. I used Objects in this one so it should help some people. It's not very interesting but demonstrates a good way to make an OO Game. Hope you like this.
7,CODE_UPLOAD150532162001.zip
This is a complete screen saver made in VB5. It uses DirectX7. At first I wanted to make it compatible with older DirectX, but they only DirectX 7 and higher supports drawing primitives on surfaces. Now the code is simple and commented.
8,D3DSample.zip
This is a sample that demonstrates some basic Direct3D techniques.
9,biohazrdDD.zip
A library of DirectDraw graphics functions and subroutines. Being used in DDCK: MOC!
10,DXHelp.zip
Gives some meaningful error codes instead of the traditional archaic automation errors.
11,ColDet.zip
Detecting collisions between polygons.
12,AscPlay.zip
This sample will play animated .ASC files.
13 , avb-ddraw.zip
This is an Example of using Microsoft's Direct Draw Type Libs (below.)
14 , directx.zip
These are the Type Libs that go with Microsofts (tm) Direct Draw. There is an excellent example using these Libs above.

立即下载

上传者： zhangxucool 时间： 2007-10-24

ac69_sdk_v2012_p4.zip_2012_P4的SDK_AC69 杰理_AC69*_linebir_蓝牙音箱

杰理得蓝牙通讯程序，可用于蓝牙和FM音箱的开发。

立即下载

上传者： weixin_42662171 时间： 2022-07-15

cpuz 1.0 完美版

CPU-Z 自读文件 ------------------ Version 1.56 版本号 1.56 October 2010 2010年10月 Contact : cpuz@cpuid.com 联系我们 ：cpuz@cpuid.com Web page: http://www.cpuid.com/cpuz.php 网站：http://www.cpuid.com/cpuz.php Validation page : http://valid.canardpc.com 确认页面 ：http://valid.canardpc.com Hall of Fame : http://valid.canardpc.com/records.php 名人堂 :http://valid.canardpc.com/records.php Forum : http://forum.canardpc.com/forumdisplay.php?f=74 社区 ：http://forum.canardpc.com/forumdisplay.php? CPUID SDK : http://www.cpuid-pro.com/devkits.php CPUID SDK介绍 ：http://www.cpuid-pro.com/devkits.php Configuration file (cpuz.ini) 配置文件 (cpuz.ini) ------------------------------ The configuration file must be named cpuz.ini and be present at the same directory level as cpuz.exe. It contains the following : 配置文件必须存放在cpuz.exe. 同一文件夹下名字为cpuz.ini [CPU-Z] TextFontName=Verdana TextFontSize=13 TextFontColor=000060 LabelFontName=Verdana LabelFontSize=13 PCI=1 MaxPCIBus=256 DMI=1 Sensor=1 SMBus=1 Display=1 ShowDutyCycles=0 UseDisplayAPI=1 - TextFontName : Font used for the information boxes. 信息框字体样式 - TextFontSize : Size of the font used for the information boxes. 信息框字体大小 - TextFontColor : Color of the font used for the information boxes. Value is expressed in hexadecimal, and consists in a classic Red/Green/Blue color code : RRGGBB 信息框使用字体颜色。RBG颜色：RRGGBB/000060 - LabelFontName : Font used for the label boxes. 标签框字体样式 - LabelFontSize : Size of the font used for the label boxes. 标签框字体大小 - Sensor : Set to OFF (or 0) disables sensor chip detection and voltages measurement. 1 to enable.传感器检测设置，1为开启、0为关闭 关闭后将不显示温度及电压 - PCI : Set to OFF (or 0) disables the PCI information. This disables chipset, SPD and, depending on the hardware, sensoring information. 1 to enable.PCI检测设置，1为开启、0为关闭 关闭后将不会显示主板、SPD及硬件传感器信息 - MaxPCIBus : Sets the maximum PCI bus to scan. Default value is 256. - DMI : Set to OFF (or 0) disables the DMI (Desktop Management Interface) information. This concerns BIOS vendor and version, motherboard vendor and revision. 1 to enable. DMI设置，1为开启、0为关闭。管壁厚 - SMBus : Set to OFF (or 0) disables SMBus information : SPD, and, depending on the hardware, sensoring information. 1 to enable.SMBUS设置，1为开启、0为关闭 关闭后将不会显示主板、SPD及硬件传感器信息 - Display : Set to OFF (or 0) disables the video card information reported in the validator. 1 to enable. 显示设备设置，1为启开、0为关闭 关闭后将不会显示显示设备信息 - ShowDutyCycles : Set to 1, switches the alternate clock computation method based on duty cycles. 0 to disable.占空比设置，1为开启、0为关闭 关闭后不会进行占空比计算时钟的方法 - UseDisplayAPI : Set to 1, uses the display driver to read the display adapters information. Parameters 参数 ---------- -txt=filename : Launch CPU-Z in ghost mode (no interface appears) and generates the register dump file (.txt) in the same directory as the exe file. 导出报告为txt文本格式 -html=filename : Same as "-txt" except it generates the html report. 导出报告为html超文本格式 -core=id : Displays clock speed of core #id (id can be set from 0 to Number of cores minus one). Keys ---- F5 : save the current tab in a bmp file F5 ：保存当前页面为bmp文件 F6 : save the current tab in the clipboard F6 ：保存当前页面在剪贴板中 F7 : save cvf file in the current directory F7 ：保存CVF在默认目录 Cache Latency Tool ------------------ The cache latency tool can be downloaded at that address : http://www.cpuid.com/download/latency.zip Cache Latency Tool下载地址 ：http://www.cpuid.com/download/latency.zip History 更新历史 ------- -------------------------------------------------------------------------------------------------- 1.56 - October 2010 - Intel Core i3/i5/i7 "2000" serie processors (Sandy Bridge) with new logos. - Intel Core i7 970 "Gulftown". - Intel P67 chipset. - AMD Phenom II, Athlon II and Sempron II "Caspian" processors. -------------------------------------------------------------------------------------------------- 1.55 - July 2010 - VIA VX900/VX900M and VN1000/VN1000M chipsets. - Intel Core i5-760, Core i7-875K and Core i5-655K processors. - Intel Core i7-940XM, 840QM, 740QM mobile processors. - Intel Core i5-450M, 540UM, 430UM, Core i3-370M mobile processors. - Intel Pentium P6000 processor. - New parameter in cpuz.ini : UseDisplayAPI -------------------------------------------------------------------------------------------------- 1.54 - March 2010 - Intel Core i7-880, Core i5-680, Core i3-550 processors. - Intel Xeon 5600 line (32nm) processors. - AMD Phenom II X6, Sempron II, Turion II, Turion II Ultra and Athlon II Mobile "Caspian" processors. - NVIDIA GeForce 320M chipset. - AMD 870/880G890GX + SB800/SB850 chipset. - Introduction of validation rooms. -------------------------------------------------------------------------------------------------- 1.53 - December 2009 - Fix validation issue with AMD Phenom processors (1.53.1). - Preliminary support for Intel Pinetrail platform (1.53.1). - Intel Core i7 930 & 950, Core i7 980X "Gulftown", Xeon W3565. - Intel Mobile Core i7/i5/i3 "Arrendale" (LV and ULV). - Intel "Clarkdale" platform improved support. - AMD Phenom FX-5000, Athlon II X2/X3/X4, Athlon L110. - AMD AM3 socket detection improved. - VIA VX800 and VX855 chipsets support. - ATI Radeon 2100 and Radeon X1250 support. - DirectX 11 detection fix. - Hardware virtualization support now reported as instructions set. - New HTML report with less information. -------------------------------------------------------------------------------------------------- 1.52 - July 2009 - Fix Core i7 clock bug (1.52.2) - New design with "Graphics" tab. - NVIDIA nForce 980a chipset support. - Intel Core i5 and Core i3 processors. - Intel Atom Z530, Pentium DC E6300 (2.8GHz) and Core 2 Solo processors. - Intel P55 and US15W chipsets preliminary support. - AMD Phenom TWKR support. - AMD Phenom X2 "Callisto" and Athlon X2 "Regor" processors. - AMD Opteron 6-core "Istanbul" processor. - Improved support for Windows 7. - New Intel logos. MD5 checksum : please refer to http://www.cpuid.com/cpuz.php#history -------------------------------------------------------------------------------------------------- 1.51 - April 2009 - New version with installer. - NVIDIA ION platform. - Intel "Clarkdale" processor preliminary support. MD5 checksum : please refer to http://www.cpuid.com/cpuz.php#history -------------------------------------------------------------------------------------------------- 1.50 - February 2009 - Improved support for AMD Phenom II processor. - Support for NVIDIA 740i chipset. - Several bug fixes. MD5 cpuz.exe (1.50) : E1C827C54F527404EDDA6D65DA0280D8 -------------------------------------------------------------------------------------------------- 1.49 - December 2008 - AMD Phenom II processor. - New Intel Core 2 models. - Improved loading time. - New online validation process. MD5 cpuz.exe (1.49) : B836E86B40D7AFAF99D9C512E8CC9FEF -------------------------------------------------------------------------------------------------- 1.48 - October 2008 - Improved support for Intel Core i7 (Bloomfield & Gainestown). - Intel Atom dual-core version support. - AMD Athlon "Kuma" processor support. - Alternate clock computation method based on "duty cycles" for Intel Core 2 processors (see ShowDutyCycles in cpuz.ini) MD5 cpuz.exe (1.48) : DB78FBF1F99B7709240B495E59758CCE -------------------------------------------------------------------------------------------------- 1.47 - August 2008 - Intel Core i7 processor. - Intel Core 2 Duo S Mobile processors. - NVIDIA MCP79/7A chipset. - AMD 790GX / SB750 chipset. MD5 cpuz.exe (1.47) : A7484EFA3C32BC968C248CB1237FF493 -------------------------------------------------------------------------------------------------- 1.46 - June 2008 - AMD Puma platform (Turion & Turion Ultra "Griffin"); - AMD Black Edition processors. - Intel Xeon EX "Dunnington". MD5 cpuz.exe (1.46) : C47432C41EC26156128F7B8E09E884CF -------------------------------------------------------------------------------------------------- 1.45 - May 2008 - Intel Atom Z500/Z510/Z520/Z530/Z540 processors. - Intel Core 2 Duo E7x00 processor. - AMD 45 nm Phenom (Dened & Shanghai) processors. - Intel P45 chipset. MD5 cpuz.exe (1.45) : DD4E540C04297CF93DC721166C13446E -------------------------------------------------------------------------------------------------- 1.44.2 - Mars 2008 - NVIDIA 650i, 680i, 750a/780a, 750i, 780i, 790i chipsets (1.44.2) - Intel G35 chipset (1.44.2) - Updated support for VIA chipsets (1.44.2) - Support for the new validator (1.44.1) - Preliminary support for VIA Isaiah processor. - Support for all VIA Model D processors: VIA C7-M, VIA C7-D, VIA Eden, VIA Eden. - Memory timings on Intel 5400A/B MCH (Skulltrail). - Fix AMD Phenom detection issue on Windows Vista 64. MD5 (1.44.2) : 81FB48A6EC7355E8D0DD71ADC2157CF6 -------------------------------------------------------------------------------------------------- 1.43 - January 2008 - Intel Skulltrail platform support (Core 2 Extreme QX9775 + 5400B MCH). - Intel X48 chipset detection. - AMD Athlon 64-LE 1600 and 1620 support. - Fix detection issues on unlocked Phenom (ES/BE). -------------------------------------------------------------------------------------------------- 1.42 - November 2007 - Intel Wolfdale/Yorkfield/Penryn CPUs support. - AMD Phenom and Opteron Barcelona support improved. - Current core selection menu (right click on the CPU page). - Loading progress. -------------------------------------------------------------------------------------------------- 1.41 - September 2007 - New CPU voltage monitoring. - Intel Xeon Tigerton support. - Intel IA64 CPUs support (Itanium / Itanium2)(special thanks to Rami Radi and Ray Hinchliffe). - AMD K10 Phenom preliminary support. - NVIDIA MCP73 support. - Intel XMP profiles support. - Memory modules nominal voltage. -------------------------------------------------------------------------------------------------- 1.40.5 - July 2007 - NVIDIA nForce 560 chipset support. - Intel Dynamic FSB technology support. - Athlon 64 X2 BE & Sempron LE (TDP 45W). - SiS671/FX/DX/MX northbridge support. - SiS968 southbridge support. -------------------------------------------------------------------------------------------------- 1.40 - May 2007 - VIA P4M800CE chipset support. - Preliminary support for Intel Penryn CPUs family (45 nm). - Intel Core 2 Duo E6x20, Pentium E2140/2160 processors recognition. - Intel P35, G33, G31, Q35, Q33, X38 chipsets support. - Intel GL960/GM965/PM965 chipsets support. - AMD Athlon 64 "Lima" processor support. - AMD Geode LX processor support. - NVIDIA nForce 520 chipset support. - New parameter "-console" to generate output in a command prompt (Windows XP only). - New icon. -------------------------------------------------------------------------------------------------- 1.39 - February 2007 - Windows Vista 64 support. - VIA CX700/VX700 chipset. - Added Merom XE (X7900/X7800) - Added "PCI" and "MaxPCIBus" in the ini file to configure PCI scanning. - Added "-core" parameter to display the clock speed of the specified core. - Lot of bug fixes. -------------------------------------------------------------------------------------------------- 1.38 - November 2006 - VIA P4M890 and P4M900 chipsets. - NVIDIA 650i and 680i chipset. - AMD Athlon 64 FX-7x processor. - Core 2 Duo E6850, E6750, E6650 processors. - socket 775 Xeon processor. - New parameters "-txt" and "-html" (see above). - Lot of bug fixes. -------------------------------------------------------------------------------------------------- 1.37 - October 2006 - Intel Core 2 Quad, Celeron 360, Mobile Core 2 Duo T5200 support. - Changed SSE4 to SSSE3 (Supplemental SSE3). - Added VIA VT8237A southbridge. - New HTML report. - Several bug fixes. -------------------------------------------------------------------------------------------------- 1.36 - August 2006 - New processor information display. - Intel 5000X/P/Z/V SPD support. - Intel Pentium D 925 & 945. -------------------------------------------------------------------------------------------------- 1.35 - June 2006 - ATI RS350, RS400, RS480/RX480, RS482, RD580/RX580, RS600/RD600, RS690, RS700 chipsets support. - ATI SB600 southbridge support. - Intel P965 chipset support. - Engineering samples Core based CPUs report. - Windows Vista product line report. -------------------------------------------------------------------------------------------------- 1.34.1 - May 2006 - AMD socket AM2/S1/F (rev F.) CPUs support. - Enhanced Performance Profile (EPP) memory information report. - Added Trc (bank cycle time) in DDR2 SPD report. - Added Trc (bank cycle time) on i925, i945, i955, i975 chipsets. - FB-DIMM DDR2 SPD information report. - Core 2 Duo names and logos added. - Turion 64 X2 logo added. - Several bug fixed. -------------------------------------------------------------------------------------------------- 1.33.1 - April 2006 - Intel i965 chipset support added. - Fix SPD detection problem on SiS 964/965/966 southbridges. - ODC (Odd Divisor Correct) for Athlon64 rev E. -------------------------------------------------------------------------------------------------- 1.33 - April 2006 - Memory Command Rate timing added. - Improved support for Intel Conroe/Merom CPUs. - Celeron M 420/430 Yonah. - Xeon Dual core Dempsey. - VIA C7-M CPU detection added. - VIA PT880, PT880 Pro, K8T900 chipsets support. - nVidia nForce 550/560/570 (MCP55) chipset support. - VIA VT8251 southbridge support. - Fixed HyperTransport information misreports (in dump file). - Added K6-2 and K6-III logos. -------------------------------------------------------------------------------------------------- 1.32.1 - March 2006 - New Intel logos. - Added Pentium D 925, Pentium EE 965. - Several bugs fixed. -------------------------------------------------------------------------------------------------- 1.32 - February 2006 - Athlon FX-60 detection added. - Athlon64 new memory dividers. - Celeron 35x Cedar Mill, Pentium D 805. - Core Solo & Core Duo detection improved. - VIA C7 CPU detection added. - Intel i975X, i945GT chipsets support. - ATI RD580 chipset support. - ULi smbus support improved. - Fix smbus conflict with ClockGen. -------------------------------------------------------------------------------------------------- 1.31 - November 2005 - Improved support for ATI RS480/482 chipsets. - GeForce 6100/6150 (nForce 410/430) chipsets support. - Intel E7520 chipset support. - New CPUs support : AMD Opteron socket 939, Intel Pentium 4 Cedar Mill and Presler, Intel Xeon Paxville, Intel Pentium M Yonah SC & DC. - Several bug fixed. -------------------------------------------------------------------------------------------------- 1.30 - August 2005 - Latest Sempron and Turion support improved. - Intel Xeon Potomac, Pentium M 780 support. - Improved Windows version report. - Support for SMBus on latest SiS bridges (964, 965, 966) and ULi bridges. - Increased clocks refresh rate. - Several bug fixed. -------------------------------------------------------------------------------------------------- 1.29 - June 2005 - New PCI devices report. - Switch for VCore report in .ini file. - VCore report on some uGuru mainboards. - Improved clocks computation. - Improved support for latest AMD CPUs, Celeron D 3x1 (EM64T). - Improved support for SiS 649, 650 and 656 chipsets, Intel 915PM chipset. - Improved stability when several instances of CPU-Z are running in the same time. - Restored html report in ghost mode (see "Parameters" chapter above). -------------------------------------------------------------------------------------------------- 1.28.6 - March 2005 - Support for Athlon 64 X2 CPUs - Support for i955X chipset - Bunch of bugs -------------------------------------------------------------------------------------------------- 1.28 - March 2005 - Support for SiS chipsets improved : 648FX, 649, 655FX, 655TX, 656 - Support for nVidia nForce4 SLI Intel Edition - Support for Intel Pentium D, Pentium XE, AMD Turion, Opteron 252 - New F7 key to simplifiy the creation of the validation file -------------------------------------------------------------------------------------------------- 1.27 - February 2005 - Support for Intel Pentium 4 6xx CPUs. - New validation system. - Hundred of bug fixes. -------------------------------------------------------------------------------------------------- 1.26 - December 2004 - VCore display on Pentium M CPUs. - New CPU clock computation. - Improved support of Transmeta CPUs. - Several bugs fixed. -------------------------------------------------------------------------------------------------- 1.25 - November 2004 - nVidia nForce4 chipset support - Intel Pentium 4J support - New button to refresh memory timings - Several bugs fixed -------------------------------------------------------------------------------------------------- 1.24 - September 2004 - AMD Sempron support - New memory SPD page - PCI-Express graphic interface support - Configuration file - External cache latency tool - Restored html report - Fix several bugs -------------------------------------------------------------------------------------------------- 1.23 - June 2004 - Intel i915P/G, i925X chipsets support - Intel LGA775 CPUs support - Intel's CPU number display - New AMD Athlon 64 steppings - New report in one file -------------------------------------------------------------------------------------------------- 1.22 - April 2004 - New CPUs : Xeon Nocona, Celeron Prescott - DDR2 memory support - Clock mode when iconized -------------------------------------------------------------------------------------------------- 1.21 - January 2004 - one file package 一个文件包 - Windows 64 support 支持Windows64位操作系统 - new chipsets support 新主板支持 - new CPU support : Celeron M, Pentium 4 "Prescott" 新CPU支持：赛扬 M，奔腾4 "Prescott" -------------------------------------------------------------------------------------------------- 1.20a - October 2003 - memory frequency and ratio on nForce2 - KT600 support 增加对威盛KT600芯片组支持 - W83627THF VRM mode - SPD read improvement SPD - Fix some memory leaks (DMI) 修复一些内存DMI信息 - Fix memory size report 修复内存大小报告 - Fix AGP side band status 修复AGP带宽状态 --------------------------------------------------------------------------------------------------

立即下载

上传者： jenly22 时间： 2011-03-19

02_0 KeilMDK搭建MSP432开发环境.pdf

一个非常值得推荐的PPT，分步骤详细阐述说明了如何在Keil MDK下搭建MSP432的开发环境，内容非常详细，很具操作性。

立即下载

上传者： hekexue 时间： 2020-09-18

Eclipse插件安装方法

Eclipse插件安装方法

立即下载

上传者： wdyq8687 时间： 2012-10-26

springboot基于JAVA的企业内部人员绩效量化管理系统_av7p4--论文-springboot毕业项目，适合计算机毕-设、实训项目、大作业学习.zip

首先包内含有部署教程以及环境，项目都是可以正常运行的，也可以从主页联---系我，了解资源。 在现代Web应用开发中，我们采用了一系列先进的技术和工具来构建高效、可扩展的系统。后端方面，Spring Boot框架为我们提供了一个快速开发的环境，而MyBatis和MyBatis Plus简化了数据库操作。为了处理JSON数据，我们选择了Gson和Jackson，同时利用Fastjson进行高效的数据解析。Hutool提供了各种便捷的工具方法，而Baidu AI SDK使得集成百度人工智能服务变得简单。Apache POI和Apache HttpClient分别用于处理Office文档和执行HTTP请求。前端开发使用了Vue.js框架结合Element UI组件库，以及jQuery和Bootstrap来实现响应式设计。我们还使用Vue CLI、ESLint、Babel等工具来优化前端开发流程。Sass帮助我们快速编写CSS，而Vuex和Vue Router分别解决了状态管理和路由问题。最后，Axios负责前端与后端之间的通信。这些技术协同工作，使得从数据库操作到前端界面构建的每一个环节都高效、可靠。 Spring Boot是Spring框架的一个模块，它简化了基于Spring应用程序的创建和部署过程。Spring Boot提供了快速启动Spring应用程序的能力，通过自动配置、微服务支持和独立运行的特性，使得开发者能够专注于业务逻辑，而不是配置细节。Spring Boot的核心思想是约定优于配置，它通过自动配置机制，根据项目中添加的依赖自动配置Spring应用。这大大减少了配置文件的编写，提高了开发效率。Spring Boot还支持嵌入式服务器，如Tomcat、Jetty和Undertow，使得开发者无需部署WAR文件到外部服务器即可运行Spring应用。 Java是一种广泛使用的高级编程语言，由Sun Microsystems公司（现为Oracle公司的一部分）在1995年首次发布。Java以其“编写一次，到处运行”（WORA）的特性而闻名，这一特性得益于Java虚拟机（JVM）的使用，它允许Java程序在任何安装了相应JVM的平台上运行，而无需重新编译。Java语言设计之初就是为了跨平台，同时具备面向对象、并发、安全和健壮性等特点。 Java语言广泛应用于企业级应用、移动应用、桌面应用、游戏开发、云计算和物联网等领域。它的语法结构清晰，易于学习和使用，同时提供了丰富的API库，支持多种编程范式，包括面向对象、命令式、函数式和并发编程。Java的强类型系统和自动内存管理减少了程序错误和内存泄漏的风险。随着Java的不断更新和发展，它已经成为一个成熟的生态系统，拥有庞大的开发者社区和持续的技术创新。Java 8引入了Lambda表达式，进一步简化了并发编程和函数式编程的实现。Java 9及以后的版本继续在模块化、性能和安全性方面进行改进，确保Java语言能够适应不断变化的技术需求和市场趋势。 MySQL是一个关系型数据库管理系统（RDBMS），它基于结构化查询语言（SQL）来管理和存储数据。MySQL由瑞典MySQL AB公司开发，并于2008年被Sun Microsystems收购，随后在2010年，Oracle公司收购了Sun Microsystems，从而获得了MySQL的所有权。MySQL以其高性能、可靠性和易用性而闻名，它提供了多种特性来满足不同规模应用程序的需求。作为一个开源解决方案，MySQL拥有一个活跃的社区，不断为其发展和改进做出贡献。它的多线程功能允许同时处理多个查询，而其优化器则可以高效地执行复杂的查询操作。 随着互联网和Web应用的快速发展，MySQL已成为许多开发者和公司的首选数据库之一。它的可扩展性和灵活性使其能够处理从小规模应用到大规模企业级应用的各种需求。通过各种存储引擎，MySQL能够适应不同的数据存储和检索需求，从而为用户提供了高度的定制性和性能优化的可能性。

立即下载

上传者： xiejiachao 时间： 2025-01-07

CPU-Z 1.47,CPU 查看工具

CPU-Z Readme file ------------------ Version 1.47 August 2008 Contact : cpuz@cpuid.com Web page: http://www.cpuid.com/cpuz.php Validation page : http://valid.x86-secret.com/ Forum : http://forum.x86-secret.com/forumdisplay.php?f=16 CPUID SDK : http://www.cpuid-pro.com/devkits.php CPU-Z is a freeware and can be freely distributed. Configuration file (cpuz.ini) ------------------------------ The configuration file must be named cpuz.ini and be present at the same directory level as cpuz.exe. It contains the following : [CPU-Z] TextFontName=Verdana TextFontSize=13 TextFontColor=000060 LabelFontName=Verdana LabelFontSize=13 PCI=ON MaxPCIBus=256 DMI=ON Sensor=ON SMBus=ON Display=ON - TextFontName : Font used for the information boxes. - TextFontSize : Size of the font used for the information boxes. - TextFontColor : Color of the font used for the information boxes. Value is expressed in hexadecimal, and consists in a classic Red/Green/Blue color code : RRGGBB - LabelFontName : Font used for the label boxes. - LabelFontSize : Size of the font used for the label boxes. - Sensor : Set to OFF disables sensor chip detection and voltages measurement. - PCI : Set to OFF disables the PCI information. This disables chipset, SPD and, depending on the hardware, sensoring information. - MaxPCIBus : Sets the maximum PCI bus to scan. Default value is 256. - DMI : Set to OFF disables the DMI (Desktop Management Interface) information. This concerns BIOS vendor and version, motherboard vendor and revision. - SMBus : Set to OFF disables SMBus information : SPD, and, depending on the hardware, sensoring information. - Display : Set to OFF disables the video card information reported in the validator. Parameters ---------- -txt=filename : Launch CPU-Z in ghost mode (no interface appears) and generates the register dump file (.txt) in the same directory as the exe file. -html=filename : Same as "-txt" except it generates the html report. -core=id : Displays clock speed of core #id (id can be set from 0 to Number of cores minus one). Keys ---- F5 : save the current tab in a bmp file F6 : save the current tab in the clipboard F7 : save cvf file in the current directory Cache Latency Tool ------------------ The cache latency tool can be downloaded at that address : http://www.cpuid.com/download/latency.zip History ------- -------------------------------------------------------------------------------------------------- 1.47 - August 2008 - Intel Core i7 processor. - Intel Core 2 Duo S Mobile processors. - NVIDIA MCP79/7A chipset. - AMD 790GX / SB750 chipset. MD5 cpuz.exe (1.47) : A7484EFA3C32BC968C248CB1237FF493 -------------------------------------------------------------------------------------------------- 1.46 - June 2008 - AMD Puma platform (Turion & Turion Ultra "Griffin"); - AMD Black Edition processors. - Intel Xeon EX "Dunnington". MD5 cpuz.exe (1.46) : C47432C41EC26156128F7B8E09E884CF -------------------------------------------------------------------------------------------------- 1.45 - May 2008 - Intel Atom Z500/Z510/Z520/Z530/Z540 processors. - Intel Core 2 Duo E7x00 processor. - AMD 45 nm Phenom (Dened & Shanghai) processors. - Intel P45 chipset. MD5 cpuz.exe (1.45) : DD4E540C04297CF93DC721166C13446E -------------------------------------------------------------------------------------------------- 1.44.2 - Mars 2008 - NVIDIA 650i, 680i, 750a/780a, 750i, 780i, 790i chipsets (1.44.2) - Intel G35 chipset (1.44.2) - Updated support for VIA chipsets (1.44.2) - Support for the new validator (1.44.1) - Preliminary support for VIA Isaiah processor. - Support for all VIA Model D processors: VIA C7-M, VIA C7-D, VIA Eden, VIA Eden. - Memory timings on Intel 5400A/B MCH (Skulltrail). - Fix AMD Phenom detection issue on Windows Vista 64. MD5 (1.44.2) : 81FB48A6EC7355E8D0DD71ADC2157CF6 -------------------------------------------------------------------------------------------------- 1.43 - January 2008 - Intel Skulltrail platform support (Core 2 Extreme QX9775 + 5400B MCH). - Intel X48 chipset detection. - AMD Athlon 64-LE 1600 and 1620 support. - Fix detection issues on unlocked Phenom (ES/BE). -------------------------------------------------------------------------------------------------- 1.42 - November 2007 - Intel Wolfdale/Yorkfield/Penryn CPUs support. - AMD Phenom and Opteron Barcelona support improved. - Current core selection menu (right click on the CPU page). - Loading progress. -------------------------------------------------------------------------------------------------- 1.41 - September 2007 - New CPU voltage monitoring. - Intel Xeon Tigerton support. - Intel IA64 CPUs support (Itanium / Itanium2)(special thanks to Rami Radi and Ray Hinchliffe). - AMD K10 Phenom preliminary support. - NVIDIA MCP73 support. - Intel XMP profiles support. - Memory modules nominal voltage. -------------------------------------------------------------------------------------------------- 1.40.5 - July 2007 - NVIDIA nForce 560 chipset support. - Intel Dynamic FSB technology support. - Athlon 64 X2 BE & Sempron LE (TDP 45W). - SiS671/FX/DX/MX northbridge support. - SiS968 southbridge support. -------------------------------------------------------------------------------------------------- 1.40 - May 2007 - VIA P4M800CE chipset support. - Preliminary support for Intel Penryn CPUs family (45 nm). - Intel Core 2 Duo E6x20, Pentium E2140/2160 processors recognition. - Intel P35, G33, G31, Q35, Q33, X38 chipsets support. - Intel GL960/GM965/PM965 chipsets support. - AMD Athlon 64 "Lima" processor support. - AMD Geode LX processor support. - NVIDIA nForce 520 chipset support. - New parameter "-console" to generate output in a command prompt (Windows XP only). - New icon. -------------------------------------------------------------------------------------------------- 1.39 - February 2007 - Windows Vista 64 support. - VIA CX700/VX700 chipset. - Added Merom XE (X7900/X7800) - Added "PCI" and "MaxPCIBus" in the ini file to configure PCI scanning. - Added "-core" parameter to display the clock speed of the specified core. - Lot of bug fixes. -------------------------------------------------------------------------------------------------- 1.38 - November 2006 - VIA P4M890 and P4M900 chipsets. - NVIDIA 650i and 680i chipset. - AMD Athlon 64 FX-7x processor. - Core 2 Duo E6850, E6750, E6650 processors. - socket 775 Xeon processor. - New parameters "-txt" and "-html" (see above). - Lot of bug fixes. -------------------------------------------------------------------------------------------------- 1.37 - October 2006 - Intel Core 2 Quad, Celeron 360, Mobile Core 2 Duo T5200 support. - Changed SSE4 to SSSE3 (Supplemental SSE3). - Added VIA VT8237A southbridge. - New HTML report. - Several bug fixes. -------------------------------------------------------------------------------------------------- 1.36 - August 2006 - New processor information display. - Intel 5000X/P/Z/V SPD support. - Intel Pentium D 925 & 945. -------------------------------------------------------------------------------------------------- 1.35 - June 2006 - ATI RS350, RS400, RS480/RX480, RS482, RD580/RX580, RS600/RD600, RS690, RS700 chipsets support. - ATI SB600 southbridge support. - Intel P965 chipset support. - Engineering samples Core based CPUs report. - Windows Vista product line report. -------------------------------------------------------------------------------------------------- 1.34.1 - May 2006 - AMD socket AM2/S1/F (rev F.) CPUs support. - Enhanced Performance Profile (EPP) memory information report. - Added Trc (bank cycle time) in DDR2 SPD report. - Added Trc (bank cycle time) on i925, i945, i955, i975 chipsets. - FB-DIMM DDR2 SPD information report. - Core 2 Duo names and logos added. - Turion 64 X2 logo added. - Several bug fixed. -------------------------------------------------------------------------------------------------- 1.33.1 - April 2006 - Intel i965 chipset support added. - Fix SPD detection problem on SiS 964/965/966 southbridges. - ODC (Odd Divisor Correct) for Athlon64 rev E. -------------------------------------------------------------------------------------------------- 1.33 - April 2006 - Memory Command Rate timing added. - Improved support for Intel Conroe/Merom CPUs. - Celeron M 420/430 Yonah. - Xeon Dual core Dempsey. - VIA C7-M CPU detection added. - VIA PT880, PT880 Pro, K8T900 chipsets support. - nVidia nForce 550/560/570 (MCP55) chipset support. - VIA VT8251 southbridge support. - Fixed HyperTransport information misreports (in dump file). - Added K6-2 and K6-III logos. -------------------------------------------------------------------------------------------------- 1.32.1 - March 2006 - New Intel logos. - Added Pentium D 925, Pentium EE 965. - Several bugs fixed. -------------------------------------------------------------------------------------------------- 1.32 - February 2006 - Athlon FX-60 detection added. - Athlon64 new memory dividers. - Celeron 35x Cedar Mill, Pentium D 805. - Core Solo & Core Duo detection improved. - VIA C7 CPU detection added. - Intel i975X, i945GT chipsets support. - ATI RD580 chipset support. - ULi smbus support improved. - Fix smbus conflict with ClockGen. -------------------------------------------------------------------------------------------------- 1.31 - November 2005 - Improved support for ATI RS480/482 chipsets. - GeForce 6100/6150 (nForce 410/430) chipsets support. - Intel E7520 chipset support. - New CPUs support : AMD Opteron socket 939, Intel Pentium 4 Cedar Mill and Presler, Intel Xeon Paxville, Intel Pentium M Yonah SC & DC. - Several bug fixed. -------------------------------------------------------------------------------------------------- 1.30 - August 2005 - Latest Sempron and Turion support improved. - Intel Xeon Potomac, Pentium M 780 support. - Improved Windows version report. - Support for SMBus on latest SiS bridges (964, 965, 966) and ULi bridges. - Increased clocks refresh rate. - Several bug fixed. -------------------------------------------------------------------------------------------------- 1.29 - June 2005 - New PCI devices report. - Switch for VCore report in .ini file. - VCore report on some uGuru mainboards. - Improved clocks computation. - Improved support for latest AMD CPUs, Celeron D 3x1 (EM64T). - Improved support for SiS 649, 650 and 656 chipsets, Intel 915PM chipset. - Improved stability when several instances of CPU-Z are running in the same time. - Restored html report in ghost mode (see "Parameters" chapter above). -------------------------------------------------------------------------------------------------- 1.28.6 - March 2005 - Support for Athlon 64 X2 CPUs - Support for i955X chipset - Bunch of bugs -------------------------------------------------------------------------------------------------- 1.28 - March 2005 - Support for SiS chipsets improved : 648FX, 649, 655FX, 655TX, 656 - Support for nVidia nForce4 SLI Intel Edition - Support for Intel Pentium D, Pentium XE, AMD Turion, Opteron 252 - New F7 key to simplifiy the creation of the validation file -------------------------------------------------------------------------------------------------- 1.27 - February 2005 - Support for Intel Pentium 4 6xx CPUs. - New validation system. - Hundred of bug fixes. -------------------------------------------------------------------------------------------------- 1.26 - December 2004 - VCore display on Pentium M CPUs. - New CPU clock computation. - Improved support of Transmeta CPUs. - Several bugs fixed. -------------------------------------------------------------------------------------------------- 1.25 - November 2004 - nVidia nForce4 chipset support - Intel Pentium 4J support - New button to refresh memory timings - Several bugs fixed -------------------------------------------------------------------------------------------------- 1.24 - September 2004 - AMD Sempron support - New memory SPD page - PCI-Express graphic interface support - Configuration file - External cache latency tool - Restored html report - Fix several bugs -------------------------------------------------------------------------------------------------- 1.23 - June 2004 - Intel i915P/G, i925X chipsets support - Intel LGA775 CPUs support - Intel's CPU number display - New AMD Athlon 64 steppings - New report in one file -------------------------------------------------------------------------------------------------- 1.22 - April 2004 - New CPUs : Xeon Nocona, Celeron Prescott - DDR2 memory support - Clock mode when iconized -------------------------------------------------------------------------------------------------- 1.21 - January 2004 - one file package - Windows 64 support - new chipsets support - new CPU support : Celeron M, Pentium 4 "Prescott" -------------------------------------------------------------------------------------------------- 1.20a - October 2003 - memory frequency and ratio on nForce2 - KT600 support - W83627THF VRM mode - SPD read improvement - Fix some memory leaks (DMI) - Fix memory size report - Fix AGP side band status --------------------------------------------------------------------------------------------------

立即下载

上传者： esupermary 时间： 2008-11-18

基于java的个性化图书推荐系统_1k4p4-springboot毕业项目，适合计算机毕-设、实训项目、大作业学习.zip

首先包内含有部署教程以及环境，项目都是可以正常运行的，也可以从主页联---系我，了解资源。 在现代Web应用开发中，我们采用了一系列先进的技术和工具来构建高效、可扩展的系统。后端方面，Spring Boot框架为我们提供了一个快速开发的环境，而MyBatis和MyBatis Plus简化了数据库操作。为了处理JSON数据，我们选择了Gson和Jackson，同时利用Fastjson进行高效的数据解析。Hutool提供了各种便捷的工具方法，而Baidu AI SDK使得集成百度人工智能服务变得简单。Apache POI和Apache HttpClient分别用于处理Office文档和执行HTTP请求。前端开发使用了Vue.js框架结合Element UI组件库，以及jQuery和Bootstrap来实现响应式设计。我们还使用Vue CLI、ESLint、Babel等工具来优化前端开发流程。Sass帮助我们快速编写CSS，而Vuex和Vue Router分别解决了状态管理和路由问题。最后，Axios负责前端与后端之间的通信。这些技术协同工作，使得从数据库操作到前端界面构建的每一个环节都高效、可靠。 Spring Boot是Spring框架的一个模块，它简化了基于Spring应用程序的创建和部署过程。Spring Boot提供了快速启动Spring应用程序的能力，通过自动配置、微服务支持和独立运行的特性，使得开发者能够专注于业务逻辑，而不是配置细节。Spring Boot的核心思想是约定优于配置，它通过自动配置机制，根据项目中添加的依赖自动配置Spring应用。这大大减少了配置文件的编写，提高了开发效率。Spring Boot还支持嵌入式服务器，如Tomcat、Jetty和Undertow，使得开发者无需部署WAR文件到外部服务器即可运行Spring应用。 Java是一种广泛使用的高级编程语言，由Sun Microsystems公司（现为Oracle公司的一部分）在1995年首次发布。Java以其“编写一次，到处运行”（WORA）的特性而闻名，这一特性得益于Java虚拟机（JVM）的使用，它允许Java程序在任何安装了相应JVM的平台上运行，而无需重新编译。Java语言设计之初就是为了跨平台，同时具备面向对象、并发、安全和健壮性等特点。 Java语言广泛应用于企业级应用、移动应用、桌面应用、游戏开发、云计算和物联网等领域。它的语法结构清晰，易于学习和使用，同时提供了丰富的API库，支持多种编程范式，包括面向对象、命令式、函数式和并发编程。Java的强类型系统和自动内存管理减少了程序错误和内存泄漏的风险。随着Java的不断更新和发展，它已经成为一个成熟的生态系统，拥有庞大的开发者社区和持续的技术创新。Java 8引入了Lambda表达式，进一步简化了并发编程和函数式编程的实现。Java 9及以后的版本继续在模块化、性能和安全性方面进行改进，确保Java语言能够适应不断变化的技术需求和市场趋势。 MySQL是一个关系型数据库管理系统（RDBMS），它基于结构化查询语言（SQL）来管理和存储数据。MySQL由瑞典MySQL AB公司开发，并于2008年被Sun Microsystems收购，随后在2010年，Oracle公司收购了Sun Microsystems，从而获得了MySQL的所有权。MySQL以其高性能、可靠性和易用性而闻名，它提供了多种特性来满足不同规模应用程序的需求。作为一个开源解决方案，MySQL拥有一个活跃的社区，不断为其发展和改进做出贡献。它的多线程功能允许同时处理多个查询，而其优化器则可以高效地执行复杂的查询操作。 随着互联网和Web应用的快速发展，MySQL已成为许多开发者和公司的首选数据库之一。它的可扩展性和灵活性使其能够处理从小规模应用到大规模企业级应用的各种需求。通过各种存储引擎，MySQL能够适应不同的数据存储和检索需求，从而为用户提供了高度的定制性和性能优化的可能性。

立即下载

上传者： xiejiachao 时间： 2025-01-07

FishJoy_final.zip

源码参考，欢迎下载

立即下载

上传者： qq_61141142 时间： 2021-12-16

Oracle_EM_10g_Grid_Control_for_Windows安装步骤

Oracle_EM_10g_Grid_Control_for_Windows安装步骤

立即下载

上传者： shushi5566 时间： 2013-01-09

ac6905.zip_2012_P4的SDK_AC69*_AC6905_SH820-AC6905-2.0_ac6905_sdk

ac6905 sdk蓝牙通信SDK, 程序可以马上使用

立即下载

上传者： weixin_42659252 时间： 2022-07-15

apktool documentation

https://github.com/iBotPeaches/Apktool Introduction Basic First lets take a lesson into apk files. apks are nothing more than a zip file containing resources and compiled java. If you were to simply unzip an apk like so, you would be left with files such as classes.dex and resources.arsc. $ unzip testapp.apk Archive: testapp.apk inflating: AndroidManifest.xml inflating: classes.dex extracting: res/drawable-hdpi/ic_launcher.png inflating: res/xml/literals.xml inflating: res/xml/references.xml extracting: resources.arsc However, at this point you have simply inflated compiled sources. If you tried to view AndroidManifest.xml. You'd be left viewing this. P4F0\fnversionCodeversionNameandroid*http://schemas.android.com/apk/res/androidpackageplatformBuildVersionCodeplatformBuildVersionNamemanifestbrut.apktool.testapp1.021APKTOOL Obviously, editing or viewing a compiled file is next to impossible. That is where Apktool comes into play. $ apktool d testapp.apk I: Using Apktool 2.0.0 on testapp.apk I: Loading resource table... I: Decoding AndroidManifest.xml with resources... I: Loading resource table from file: 1.apk I: Regular manifest package... I: Decoding file-resources... I: Decoding values */* XMLs... I: Baksmaling classes.dex... I: Copying assets and libs... $ Viewing AndroidManifest.xml again results in something much more human readable In addition to XMLs, resources such as 9 patch images, layouts, strings and much more are correctly decoded to source form. Decoding The decode option on Apktool can be invoked either from d or decode like shown below. $ apktool d foo.jar // decodes foo.jar to foo.jar.out folder $ apktool decode foo.jar // decodes foo.jar to foo.jar.out folder $ apktool d bar.apk // decodes bar.apk to bar folder $ apktool decode bar.apk // decodes bar.apk to bar folder $ apktool d bar.apk -o baz // decodes bar.apk to baz folder Building The build option can be invoked either from b or build like shown below $ apktool b foo.jar.out // builds foo.jar.out folder into foo.jar.out/dist/foo.jar file $ apktool build foo.jar.out // builds foo.jar.out folder into foo.jar.out/dist/foo.jar file $ apktool b bar // builds bar folder into bar/dist/bar.apk file $ apktool b . // builds current directory into ./dist $ apktool b bar -o new_bar.apk // builds bar folder into new_bar.apk $ apktool b bar.apk // WRONG: brut.androlib.AndrolibException: brut.directory.PathNotExist: apktool.yml // Must use folder, not apk/jar file InfoIn order to run a rebuilt application. You must resign the application. Android documentation can help with this. Frameworks Frameworks can be installed either from if or install-framework, in addition two parameters -p, --frame-path

- Store framework files into -t, --tag - Tag frameworks using Allow for a finer control over how the files are named and how they are stored. $ apktool if framework-res.apk I: Framework installed to: 1.apk // pkgId of framework-res.apk determines number (which is 0x01) $ apktool if com.htc.resources.apk I: Framework installed to: 2.apk // pkgId of com.htc.resources is 0x02 $ apktool if com.htc.resources.apk -t htc I: Framework installed to: 2-htc.apk // pkgId-tag.apk $ apktool if framework-res.apk -p foo/bar I: Framework installed to: foo/bar/1.apk $ apktool if framework-res.apk -t baz -p foo/bar I: Framework installed to: foo/bar/1-baz.apk Migration Instructions v2.1.1 -> v2.2.0 Run the following commands to migrate your framework directory Apktool will work fine without running these commands, this will just cleanup abandoned files unix - mkdir -p ~/.local/share; mv ~/apktool ~/.local/share windows - move %USERPROFILE%\apktool %USERPROFILE%\AppData\Local v2.0.1 -> v2.0.2 Update apktool to v2.0.2 Remove framework file $HOME/apktool/framework/1.apk due to internal API update (Android Marshmallow) v1.5.x -> v2.0.0 Java 1.7 is required Update apktool to v2.0.0 aapt is now included inside the apktool binary. It's not required to maintain your own aapt install under $PATH. (However, features like -a / --aapt are still used and can override the internal aapt) The addition of aapt replaces the need for separate aapt download packages. Helper Scripts may be found here Remove framework $HOME/apktool/framework/1.apk Eagle eyed users will notice resources are now decoded before sources now. This is because we need to know the API version via the manifest for decoding the sources Parameter Changes Smali/baksmali 2.0 are included. This is a big change from 1.4.2. Please read the smali updates here for more information -o / --output is now used for the output of apk/directory -t / --tag is required for tagging framework files -advance / --advanced will launch advance parameters and information on the usage output -m / --match-original is a new feature for apk analysis. This retains the apk is nearly original format, but will make rebuild more than likely not work due to ignoring the changes that newer aapt requires After [d]ecode, there will be new folders (original / unknown) in the decoded apk folder original = META-INF folder / AndroidManifest.xml, which are needed to retain the signature of apks to prevent needing to resign. Used with -c / --copy-original on [b]uild unknown = Files / folders that are not part of the standard AOSP build procedure. These files will be injected back into the rebuilt APK. apktool.yml collects more information than last version SdkInfo - Used to repopulate the sdk information in AndroidManifest.xml since newer aapt requires version information to be passed via parameter packageInfo - Used to help support Android 4.2 renamed manifest feature. Automatically detects differences between resource and manifest and performs automatic --rename-manifest-package on [b]uild versionInfo - Used to repopulate the version information in AndroidManifest.xml since newer aapt requires version information to be passed via parameter compressionType - Used to determine the compression that resources.arsc had on the original apk in order to replicate during [b]uild unknownFiles - Used to record name/location of non-standard files in an apk in order to place correctly on rebuilt apk sharedLibrary - Used to help support Android 5 shared library feature by automatically detecting shared libraries and using --shared-lib on [b]uild Examples of new usage in 2.0 vs 1.5.x Old (Apktool 1.5.x) New (Apktool 2.0.x) apktool if framework-res.apk tag apktool if framework-res.apk -t tag apktool d framework-res.apk output apktool d framework.res.apk -o output apktool b output new.apk apktool b output -o new.apk v1.4.x -> v1.5.1 Update apktool to v1.5.1 Update aapt manually or use package r05-ibot via downloading Mac, Windows or Linux Remove framework file $HOME/apktool/framework/1.apk Intermediate Framework Files As you probably know, Android apps utilize code and resources that are found on the Android OS itself. These are known as framework resources and Apktool relies on these to properly decode and build apks. Every Apktool release contains internally the most up to date AOSP framework at the time of the release. This allows you to decode and build most apks without a problem. However, manufacturers add their own framework files in addition to the regular AOSP ones. To use apktool against these manufacturer apks you must first install the manufacturer framework files. Example Lets say you want to decode HtcContacts.apk from an HTC device. If you try you will get an error message. $ apktool d HtcContacts.apk I: Loading resource table... I: Decoding resources... I: Loading resource table from file: 1.apk W: Could not decode attr value, using undecoded value instead: ns=android, name=drawable W: Could not decode attr value, using undecoded value instead: ns=android, name=icon Can't find framework resources for package of id: 2. You must install proper framework files, see project website for more info. We must get HTC framework resources before decoding this apk. We pull com.htc.resources.apk from our device and install it $ apktool if com.htc.resources.apk I: Framework installed to: 2.apk Now we will try this decode again. $ apktool d HtcContacts.apk I: Loading resource table... I: Decoding resources... I: Loading resource table from file: /home/brutall/apktool/framework/1.apk I: Loading resource table from file: /home/brutall/apktool/framework/2.apk I: Copying assets and libs... As you can see. Apktool leveraged both 1.apk and 2.apk framework files in order to properly decode this application. Finding Frameworks For the most part any apk in /system/framework on a device will be a framework file. On some devices they might reside in /data/system-framework and even cleverly hidden in /system/app or /system/priv-app. They are usually named with the naming of "resources", "res" or "framework". Example HTC has a framework called com.htc.resources.apk, LG has one called lge-res.apk After you find a framework file you could pull it via adb pull /path/to/file or use a file manager application. After you have the file locally, pay attention to how Apktool installs it. The number that the framework is named during install corresponds to the pkgId of the application. These values should range from 1 to 9. Any APK that installs itself as 127 is 0x7F which is an internal pkgId. Internal Frameworks Apktool comes with an internal framework like mentioned above. This file is copied to $HOME/apktool/framework/1.apk during use. Warning Apktool has no knowledge of what version of framework resides there. It will assume its up to date, so delete the file during Apktool upgrades Managing framework files Frameworks are stored in $HOME/apktool/framework for Windows and Unix systems. Mac OS X has a slightly different folder location of $HOME/Library/apktool/framework. If these directories are not available it will default to java.io.tmpdir which is usually /tmp. This is a volatile directory so it would make sense to take advantage of the parameter --frame-path to select an alternative folder for framework files. Note Apktool has no control over the frameworks once installed, but you are free to manage these files on your own. Tagging framework files Frameworks are stored in the naming convention of: -.apk. They are identified by pkgId and optionally custom tag. Usually tagging frameworks isn't necessary, but if you work on apps from many different devices and they have incompatible frameworks, you will need some way to easily switch between them. You could tag frameworks by: $ apktool if com.htc.resources.apk -t hero I: Framework installed to: /home/brutall/apktool/framework/2-hero.apk $ apktool if com.htc.resources.apk -t desire I: Framework installed to: /home/brutall/apktool/framework/2-desire.apk Then: $ apktool d HtcContacts.apk -t hero I: Loading resource table... I: Decoding resources... I: Loading resource table from file: /home/brutall/apktool/framework/1.apk I: Loading resource table from file: /home/brutall/apktool/framework/2-hero.apk I: Copying assets and libs... $ apktool d HtcContacts.apk -t desire I: Loading resource table... I: Decoding resources... I: Loading resource table from file: /home/brutall/apktool/framework/1.apk I: Loading resource table from file: /home/brutall/apktool/framework/2-desire.apk I: Copying assets and libs... You don't have to select a tag when building apk - apktool automatically uses the same tag, as when decoding. Smali Debugging Warning SmaliDebugging has been marked as deprecated in 2.0.3, and removed in 2.1. Please check SmaliIdea for a debugger. Apktool makes possible to debug smali code step by step, watch variables, set breakpoints, etc. General information Generally we need several things to run Java debugging session: debugger server (usually Java VM) debugger client (usually IDE like IntelliJ, Eclipse or Netbeans) client must have sources of debugged application server must have binaries compiled with debugging symbols referencing these sources sources must be java files with at least package and class definitions, to properly connect them with debugging symbols In our particular situation we have: server: Monitor (Previously DDMS), part of Android SDK, standard for debugging Android applications - explained here client: any JPDA client - most of decent IDEs have support for this protocol. sources: smali code modified by apktool to satisfy above requirements (".java" extension, class declaration, etc.). Apktool modifies them when decoding apk in debug mode. binaries: when building apk in debug mode, apktool removes original symbols and adds new, which are referencing smali code (line numbers, registers/variables, etc.) Info To successfully run debug sessions, the apk must be both decoded and built in debug mode. Decoding with debug decodes the application differently to allow the debug rebuild option to inject lines allowing the debugger to identify variables and types.-d / --debug General instructions Above information is enough to debug smali code using apktool, but if you aren't familiar with DDMS and Java debugging, then you probably still don't know how to do it. Below are simple instructions for doing it using IntelliJ or Netbeans. Decode apk in debug mode: $ apktool d -d -o out app.apk Build new apk in debug mode: $ apktool b -d out Sign, install and run new apk. Follow sub-instructions below depending on IDE. IntelliJ (Android Studio) instructions In IntelliJ add new Java Module Project selecting the "out" directory as project location and the "smali" subdirectory as content root dir. Run Monitor (Android SDK /tools folder), find your application on a list and click it. Note port information in last column - it should be something like "86xx / 8700". In IntelliJ: Debug -> Edit Configurations. Since this is a new project, you will have to create a Debugger. Create a Remote Debugger, with the settings on "Attach" and setting the Port to 8700 (Or whatever Monitor said). The rest of fields should be ok, click "Ok". Start the debugging session. You will see some info in a log and debugging buttons will show up in top panel. Set breakpoint. You must select line with some instruction, you can't set breakpoint on lines starting with ".", ":" or "#". Trigger some action in application. If you run at breakpoint, then thread should stop and you will be able to debug step by step, watch variables, etc. Netbeans instructions In Netbeans add new Java Project with Existing Sources, select "out" directory as project root and "smali" subdirectory as sources dir. Run DDMS, find your application on a list and click it. Note port information in last column - it should be something like "86xx / 8700". In Netbeans: Debug -> Attach Debugger -> select JPDA and set Port to 8700 (or whatever you saw in previous step). Rest of fields should be ok, click "Ok". Debugging session should start: you will see some info in a log and debugging buttons will show up in top panel. Set breakpoint. You must select line with some instruction, you can't set breakpoint on lines starting with ".", ":" or "#". Trigger some action in application. If you run at breakpoint, then thread should stop and you will be able to debug step by step, watch variables, etc. Limitations/Issues Because IDE doesn't have full sources, it doesn't know about class members and such. Variables watching works because most of data could be read from memory (objects in Java know about their types), but if for example, you watch an object and it has some nulled member, then you won't see, what type this member is. 9Patch Images Docs exist for the mysterious 9patch images here and there. (Read these first). These docs though are meant for developers and lack information for those who work with already compiled 3rd party applications. There you can find information how to create them, but no information about how they actually work. I will try and explain it here. The official docs miss one point that 9patch images come in two forms: source & compiled. source - You know this one. You find it in the source of an application or freely available online. These are images with a black border around them. compiled - The mysterious form found in apk files. There are no borders and the 9patch data is written into a binary chunk called npTc. You can't see or modify it easily, but Android OS can as its quicker to read. There are problems related to the above two points. You can't move 9patch images between both types without a conversion. If you try and unpack 9patch images from an apk and use it in the source of another, you will get errors during build. Also vice versa, you cannot take source 9patch images directly into an apk. 9patch binary chunk isn't recognized by modern image processing tools. So modifying the compiled image will more than likely break the npTc chunk, thus breaking the image on the device. The only solution to this problem is to easily convert between these two types. The encoder (which takes source to compiled) is built into the aapt tool and is automatically used during build. This means we only need to build a decoder which has been in apktool since v1.3.0 and is automatically ran on all 9patch images during decode. So if you want to modify 9patch images, don't do it directly. Use apktool to decode the application (including the 9patch images) and then modify the images. At that point when you build the application back, the source 9patch images will be compiled. Other FAQ What about the -j switch shown from the original YouTube videos? Read Issue 199. In short - it doesn't exist. Is it possible to run apktool on a device? Sadly not. There are some incompatibilities with SnakeYAML, java.nio and aapt Where can I download sources of apktool? From our Github or Bitbucket project. Resulting apk file is much smaller than original! Is there something missing? There are a couple of reasons that might cause this. Apktool builds unsigned apks. This means an entire directory META-INF is missing. New aapt binary. Newer versions of apktool contain a newer aapt which optimizes images differently. These points might have contributed to a smaller than normal apk There is no META-INF dir in resulting apk. Is this ok? Yes. META-INF contains apk signatures. After modifying the apk it is no longer signed. You can use -c / --copy-original to retain these signatures. However, using -c uses the original AndroidManifest.xml file, so changes to it will be lost. What do you call "magic apks"? For some reason there are apks that are built using modified build tools. These apks don't work on a regular AOSP Android build, but usually are accompanied by a modified system that can read these modified apks. Apktool cannot handle these apks, therefore they are "magic". Could I integrate apktool into my own tool? Could I modify apktool sources? Do I have to credit you? Actually the Apache License, which apktool uses, answers all these questions. Yes you can redistribute and/or modify apktool without my permission. However, if you do it would be nice to add our contributors (brut.all, iBotPeaches and JesusFreke) into your credits but it's not required. Where does apktool store its framework files? unix - $HOME/.local/share/apktool mac - $HOME/Library/apktool windows - $HOME/AppData/Local/apktool Options Utility Options that can be executed at any time. -version, --version Outputs current version. (Ex: 1.5.2) -v, --verbose Verbose output. Must be first parameter -q, --quiet Quiet output. Must be first parameter -advance, --advanced Advance usage output Decode These are all the options when decoding an apk. --api The numeric api-level of the smali files to generate (defaults to targetSdkVersion) -b, --no-debug-info Prevents baksmali from writing out debug info (.local, .param, .line, etc). Preferred to use if you are comparing smali from the same APK of different versions. The line numbers and debug will change among versions, which can make DIFF reports a pain. -f, --force Force delete destination directory. Use when trying to decode to a folder that already exists --keep-broken-res - Advanced If there is an error like "Invalid Config Flags Detected. Dropping Resources...". This means that APK has a different structure then Apktool can handle. This might be a newer Android version or a random APK that doesn't match standards. Running this will allow the decode, but then you have to manually fix the folders with -ERR in them. -m, --match-original - Used for analysis Matches files closest as possible to original, but prevents rebuild. -o, --output The name of the folder that apk gets written to -p, --frame-path The folder location where framework files should be stored/read from -r, --no-res This will prevent the decompile of resources. This keeps the resources.arsc intact without any decode. If only editing Java (smali) then this is the recommend for faster decompile & rebuild -s, --no-src This will prevent the disassemble of the dex files. This keeps the apk classes.dex file and simply moves it during build. If your only editing the resources. This is recommended for faster decompile & rebuild -t, --frame-tag Uses framework files tagged via Rebuild These are all the options when building an apk. -a, --aapt Loads aapt from the specified file location, instead of relying on path. Falls back to $PATH loading, if no file found -c, --copy-original - Will still require signature resign post API18 Copies original AndroidManifest.xml and META-INF folder into built apk -d, --debug Adds debuggable="true" to AndroidManifest file. -f, --force-all Overwrites existing files during build, reassembling the resources.arsc file and classes.dex file -o, --output The name and location of the apk that gets written -p, --frame-path The location where framework files are loaded from

立即下载

上传者： qxs820624 时间： 2016-07-21

ac69_sdk_v2012_p4_demo.zip

杰理蓝牙sdk，需要的可以下载哦，

立即下载

上传者： qq_32843811 时间： 2019-06-19