解壓工具at

⑴ 怎樣製作解壓縮文件夾

首先把這些照片放在一個文件夾裡面，然後用滑鼠右鍵單擊文件夾-〉添加到壓縮文件夾-〉在窗口最左下選擇分段壓縮大小（1,457,664 - 3.5"）這個是3寸盤的，然後壓縮就可以了，把每一個都放入3寸盤，然後考入同一目錄，單擊一個解壓縮就可以了。

PS 需要你有Winrar
不會再問我QQ86881052

⑵ 關於Y560AT-ISE解壓文件的問題

更新一下主板驅動試試
驅動下載：
看一下主機後面的主機編號，然後到下列網址，在頁面中間第一個對話框把編號輸入查找
[url]http://support1.lenovo.com.cn/lenovo/wsi/Moles/Drive.aspx?seq=1[/url]

⑶ 誰能告訴我解壓縮文件的WINZIP怎麼使用

對於可解壓的文件只要選中點滑鼠右鍵就有解壓菜單了！
建議你還是使用 winrar 吧，支持的格式比較多，雖然有時候壓縮 rar 格式比 zip 格式慢些，但如果設置好了好多時候會壓縮比率更大一些！
最主要的是 winzip 解不了 rar ，而 winrar 可以解 zip ！

⑷ 怎樣解壓ZIP文件

呵呵，zip都不會用，winrar都沒有裝，就想當黑客了？？？

先要學會走路才好，

建議先安裝winrar，然後點擊那個zip，解壓，選擇路徑（就先選桌面，找一下感覺），確定。

winrar下載
http://www.jiuai.net/bencandy.php?id=2814

⑸ mac用什麼解壓縮工具好

TheUnarchiver多久沒更新了……作者都不管了吧。試試全能解壓，AppStore評分挺高的，界面也比其他解壓軟體好看多了！ 還有技術支持， 良心作品！

Mac Store 的下載鏈接放這 ，看看用戶評價都知道 ：

https://itunes.apple.com/app/id1127253508?mt=12&at=1001ldFh&ct=p

⑹ 如何打開RAR壓縮文件包

可以使用winrar進行解壓打開，具體的操作方法為：

1、打開網路，搜索winrar，並點擊打開一個下載網站。

⑺ 最大解壓文件

上傳了500M的zip後發現竟然沒有解壓，文件的這個選項文件類型顯示的是「file
style：data」那該怎麼辦？是用winrar壓縮成的zip的沒有exta的選擇該怎麼辦？可是傳了好久的······························解壓這么大的文件CPU佔有率一定很高，會不會被停空間？[]

⑻ 如何解包/編輯/打包android系統的boot.img文件

1
boot映像並不是一個完整的文件系統，它是一種android自定義的文件格式，該格式包括了2K的文件頭，後面緊跟著是用gzip壓縮過的內核，再後面是一個ramdisk內存檔，然後緊跟著第二階段的載入器程序（這個載入器程序是可選的，在某些映像中或許沒有這部分）。此類文件的定義可以從源代碼android-src/system/core/mkbootimg找到一個叫做bootimg.h的文件。
2
/*
** +-----------------+
** | boot header | 1 page ** +-----------------+
** | kernel | n pages ** +-----------------+
** | ramdisk | m pages ** +-----------------+
** | second stage | o pages ** +-----------------+ **
** n = (kernel_size + page_size - 1) / page_size ** m = (ramdisk_size + page_size - 1) / page_size ** o = (second_size + page_size - 1) / page_size **
** 0. all entities are page_size aligned in flash ** 1. kernel and ramdisk are required (size != 0)
** 2. second is optional (second_size == 0 -> no second) ** 3. load each element (kernel, ramdisk, second) at ** the specified physical address (kernel_addr, etc) ** 4. prepare tags at tag_addr. kernel_args[] is ** appended to the kernel commandline in the tags. ** 5. r0 = 0, r1 = MACHINE_TYPE, r2 = tags_addr ** 6. if second_size != 0: jump to second_addr ** else: jump to kernel_addr */

ramdisk映像是一個最基礎的小型文件系統，它包括了初始化系統所需要的全部核心文件，例如:初始化init進程以及init.rc（可以用於設置很多系統的參數）等文件
看這里是不是顯得頭大呢，，，今天哥們分享的教程是比較簡單的，不需要認識這些東西是做什麼的，有什麼用，。只需要要一個簡單的工具就能實現你想要解包boot.img的問題。。。
3
下載一個ROM助手，網路搜索下就行，最好是官網下載，蘑菇論壇。
安裝並打開它，在主界面上你會找到「解包IMG」功能的按鈕，

4
點擊後把你的boot鏡像文件載入進去，等待幾分鍾，就能把boot的鏡像解開了 ，，上面提示打開文件夾，點擊之後，就能找到boot解開後的全部內容，在這里你想怎麼編輯就怎麼編輯。

看到木有boot解包就是這么簡單，其實ROM助手還可以解包recovery 、userdara等鏡像文件。只要用了就看到，步驟和上面的操作時一樣的 。

5
K！好了，修改大家就自己去奮斗吧，其實說實話，安卓本來基於LINUX就是在那系統下玩的，用WINDOWS的就比較吃虧了。。截止目前ROM助手還沒有打包功能，相信他們開發團隊很快就能完善這項功能的說。我這里根據我的經驗來分享下如何打包boot鏡像文件，這里需要用命令符
開始-運行-cmdd:回車cd boot回車bootimg --repack-bootimg 0x200000 "mem=211M console=null androidboot.hardware=qcom" 2048 4096
出現「output boot.img」的字樣就顯示打包成功
6
到這里就完全打包解包無壓力了，額，recovery userdara 解包打包，就直接按照這個操作步驟即可完成。

⑼ 如何解壓文件名是UTF8編碼的壓縮包

UTF8其實和Unicode是同類，就是在編碼方式上不同！
首先UTF8編碼後的大小是不一定，不像Unicode編碼後的大小是一樣的！

我們先來看Unicode的編碼：一個英文字母 「a」 和 一個漢字 「好」，編碼後都是佔用的空間大小是一樣的，都是兩個位元組！

而UTF8編碼：一個英文字母「a」 和 一個漢字 「好」，編碼後佔用的空間大小就不樣了，前者是一個位元組，後者是三個位元組！

現在就讓我們來看看UTF8編碼的原理吧：
因為一個字母還有一些鍵盤上的符號加起來只用二進制七位就可以表示出來，而一個位元組就是八位，所以UTF8就用一個位元組來表式字母和一些鍵盤上的符號。然而當我們拿到被編碼後的一個位元組後怎麼知道它的組成？它有可能是英文字母的一個位元組，也有可能是漢字的三個位元組中的一個位元組！所以，UTF8是有標志位的！

當要表示的內容是 7位 的時候就用一個位元組：0******* 第一個0為標志位，剩下的空間正好可以表示ASCII 0－127 的內容。

當要表示的內容在 8 到 11 位的時候就用兩個位元組：110***** 10****** 第一個位元組的110和第二個位元組的10為標志位。

當要表示的內容在 12 到 16 位的時候就用三個位元組：1110***** 10****** 10****** 和上面一樣，第一個位元組的1110和第二、三個位元組的10都是標志位，剩下的占湔�每梢員硎競鶴幀?BR>
以此類推：
四個位元組：11110**** 10****** 10****** 10******
五個位元組：111110*** 10****** 10****** 10****** 10******
六個位元組：1111110** 10****** 10****** 10****** 10****** 10******

UTF-7：A Mail-Safe Transformation Format of Unicode(RFC1642)。這是一種使用 7 位 ASCII 碼對 Unicode 碼進行轉換的編碼。它的設計目的仍然是為了在只能傳遞 7 為編碼的郵件網關中傳遞信息。 UTF-7 對英語字母、數字和常見符號直接顯示，而對其他符號用修正的 Base64 編碼。符號 + 和 - 號控制編碼過程的開始和暫停。所以亂碼中如果夾有英文單詞，並且相伴有 + 號和 - 號，這就有可能是 UTF-7 編碼。

關於UTF7的更多資料如下（都是英語的，如果想具體了解再看）：
UTF-7

A Mail-Safe Transformation Format of Unicode

Status of this Memo

This memo provides information for the Internet community. This memo
does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

Abstract

The Unicode Standard, version 2.0, and ISO/IEC 10646-1:1993(E) (as
amended) jointly define a character set (hereafter referred to as
Unicode) which encompasses most of the world's writing systems.
However, Internet mail (STD 11, RFC 822) currently supports only 7-
bit US ASCII as a character set. MIME (RFC 2045 through 2049) extends
Internet mail to support different media types and character sets,
and thus could support Unicode in mail messages. MIME neither defines
Unicode as a permitted character set nor specifies how it would be
encoded, although it does provide for the registration of additional
character sets over time.

This document describes a transformation format of Unicode that
contains only 7-bit ASCII octets and is intended to be readable by
humans in the limiting case that the document consists of characters
from the US-ASCII repertoire. It also specifies how this
transformation format is used in the context of MIME and RFC 1641,
"Using Unicode with MIME".

Motivation

Although other transformation formats of Unicode exist and could
conceivably be used in this context (most notably UTF-8, also known
as UTF-2 or UTF-FSS), they suffer the disadvantage that they use
octets in the range decimal 128 through 255 to encode Unicode
characters outside the US-ASCII range. Thus, in the context of mail,
those octets must themselves be encoded. This requires putting text
through two successive encoding processes, and leads to a significant
expansion of characters outside the US-ASCII range, putting non-
English speakers at a disadvantage. For example, using UTF-8 together

with the Quoted-Printable content transfer encoding of MIME
represents US-ASCII characters in one octet, but other characters may
require up to nine octets.

Overview

UTF-7 encodes Unicode characters as US-ASCII octets, together with
shift sequences to encode characters outside that range. For this
purpose, one of the characters in the US-ASCII repertoire is reserved
for use as a shift character.

Many mail gateways and systems cannot handle the entire US-ASCII
character set (those based on EBCDIC, for example), and so UTF-7
contains provisions for encoding characters within US-ASCII in a way
that all mail systems can accomodate.

UTF-7 should normally be used only in the context of 7 bit
transports, such as mail. In other contexts, straight Unicode or
UTF-8 is preferred.

See RFC 1641, "Using Unicode with MIME" for the overall specification
on usage of Unicode transformation formats with MIME.

Definitions

First, the definition of Unicode:

The 16 bit character set Unicode is defined by "The Unicode
Standard, Version 2.0". This character set is identical with the
character repertoire and coding of the international standard
ISO/IEC 10646-1:1993(E); Coded Representation Form=UCS-2;
Subset=300; Implementation Level=3, including the first 7
amendments to 10646 plus editorial corrections.

Note. Unicode 2.0 further specifies the use and interaction of
these character codes beyond the ISO standard. However, any valid
10646 sequence is a valid Unicode sequence, and vice versa;
Unicode supplies interpretations of sequences on which the ISO
standard is silent as to interpretation.

Next, some handy definitions of US-ASCII character subsets:

Set D (directly encoded characters) consists of the following
characters (derived from RFC 1521, Appendix B, which no longer
appears in RFC 2045): the upper and lower case letters A through Z
and a through z, the 10 digits 0-9, and the following nine special
characters (note that "+" and "=" are omitted):

Character ASCII & Unicode Value (decimal)
' 39
( 40
) 41
, 44
- 45
. 46
/ 47
: 58
? 63

Set O (optional direct characters) consists of the following
characters (note that "\" and "~" are omitted):

Character ASCII & Unicode Value (decimal)
! 33
" 34
# 35
$ 36
% 37
& 38
* 42
; 59
< 60
= 61
> 62
@ 64
[ 91
] 93
^ 94
_ 95
' 96
{ 123
| 124
} 125

Rationale. The characters "\" and "~" are omitted because they are
often redefined in variants of ASCII.

Set B (Modified Base 64) is the set of characters in the Base64
alphabet defined in RFC 2045, excluding the pad character "="
(decimal value 61).

Rationale. The pad character = is excluded because UTF-7 is designed
for use within header fields as set forth in RFC 2047. Since the only
readable encoding in RFC 2047 is "Q" (based on RFC 2045's Quoted-
Printable), the "=" character is not available for use (without a lot
of escape sequences). This was very unfortunate but unavoidable. The
"=" character could otherwise have been used as the UTF-7 escape
character as well (rather than using "+").

Note that all characters in US-ASCII have the same value in Unicode
when zero-extended to 16 bits.

UTF-7 Definition

A UTF-7 stream represents 16-bit Unicode characters using 7-bit US-
ASCII octets as follows:

Rule 1: (direct encoding) Unicode characters in set D above may be
encoded directly as their ASCII equivalents. Unicode characters in
Set O may optionally be encoded directly as their ASCII
equivalents, bearing in mind that many of these characters are
illegal in header fields, or may not pass correctly through some
mail gateways.

Rule 2: (Unicode shifted encoding) Any Unicode character sequence
may be encoded using a sequence of characters in set B, when
preceded by the shift character "+" (US-ASCII character value
decimal 43). The "+" signals that subsequent octets are to be
interpreted as elements of the Modified Base64 alphabet until a
character not in that alphabet is encountered. Such characters
include control characters such as carriage returns and line
feeds; thus, a Unicode shifted sequence always terminates at the
of a line. As a special case, if the sequence terminates with the
character "-" (US-ASCII decimal 45) then that character is
absorbed; other terminating characters are not absorbed and are
processed normally.

Note that if the first character after the shifted sequence is "-"
then an extra "-" must be present to terminate the shifted
sequence so that the actual "-" is not itself absorbed.

Rationale. A terminating character is necessary for cases where
the next character after the Modified Base64 sequence is part of
character set B or is itself the terminating character. It can
also enhance readability by delimiting encoded sequences.

Also as a special case, the sequence "+-" may be used to encode
the character "+". A "+" character followed immediately by any
character other than members of set B or "-" is an ill-formed
sequence.

Unicode is encoded using Modified Base64 by first converting
Unicode 16-bit quantities to an octet stream (with the most
significant octet first). Surrogate pairs (UTF-16) are converted
by treating each half of the pair as a separate 16 bit quantity
(i.e., no special treatment). Text with an odd number of octets is
ill-formed. ISO 10646 characters outside the range addressable via
surrogate pairs cannot be encoded.

Rationale. ISO/IEC 10646-1:1993(E) specifies that when characters
the UCS-2 form are serialized as octets, that the most significant
octet appear first. This is also in keeping with common network
practice of choosing a canonical format for transmission.

Rationale. The policy for code point allocation within ISO 10646
and Unicode is that the repertoires be kept synchronized. No code
points will be allocated in ISO 10646 outside the range
addressable by surrogate pairs.

Next, the octet stream is encoded by applying the Base64 content
transfer encoding algorithm as defined in RFC 2045, modified to
omit the "=" pad character. Instead, when encoding, zero bits are
added to pad to a Base64 character boundary. When decoding, any
bits at the end of the Modified Base64 sequence that do not
constitute a complete 16-bit Unicode character are discarded. If
such discarded bits are non-zero the sequence is ill-formed.

Rationale. The pad character "=" is not used when encoding
Modified Base64 because of the conflict with its use as an escape
character for the Q content transfer encoding in RFC 2047 header
fields, as mentioned above.

Rule 3: The space (decimal 32), tab (decimal 9), carriage return
(decimal 13), and line feed (decimal 10) characters may be
directly represented by their ASCII equivalents. However, note
that MIME content transfer encodings have rules concerning the use
of such characters. Usage that does not conform to the
restrictions of RFC 822, for example, would have to be encoded
using MIME content transfer encodings other than 7bit or 8bit,
such as quoted-printable, binary, or base64.

Given this set of rules, Unicode characters which may be encoded via
rules 1 or 3 take one octet per character, and other Unicode
characters are encoded on average with 2 2/3 octets per character

plus one octet to switch into Modified Base64 and an optional octet
to switch out.

Example. The Unicode sequence "A<NOT IDENTICAL TO><ALPHA>."
(hexadecimal 0041,2262,0391,002E) may be encoded as follows:

A+ImIDkQ.

Example. The Unicode sequence "Hi Mom -<WHITE SMILING FACE>-!"
(hexadecimal 0048, 0069, 0020, 004D, 006F, 006D, 0020, 002D, 263A,
002D, 0021) may be encoded as follows:

Hi Mom -+Jjo--!

Example. The Unicode sequence representing the Han characters for
the Japanese word "nihongo" (hexadecimal 65E5,672C,8A9E) may be
encoded as follows:

+ZeVnLIqe-