下面说一下我的经历吧，U盘突然就出问题了，插到电脑里读能读出盘符但是不能打开U盘，提示说没有格式化，但是进行格式化无法完成，到最后的时候就停住了，像死机一样。之前就在网上搜了半天，下了好多个软件试了又试，都不行，还好我没有把U盘扔了，呵呵，今天就把它搞活了~

       这个工具确实不错，其他的工具都不能读出我的U盘，这个一下就读出来了，让我感到有希望，于是，我就进行了低级格式化，最后~成功，不过有些块坏了，但是能用了，一个心结就这样解开了，嘿嘿。512M的U盘，现在显示的只有463MB了。

       提供一个下载地址吧，如果遇到同样问题的可以试试，如果不能解决你的问题，那就还得到网上搜啦

http://www.e-huashun.com/html/Drivers.htm  芯邦普通芯片量产工具

HugeInt.h:

#ifndef HUGEINT_H
#define HUGEINT_H

#include <iostream>

using std::ostream;

class HugeInt {
	friend ostream &operator << ( ostream &, const HugeInt & );

public:
	HugeInt( long = 0 );
	HugeInt( constchar * );

	HugeInt operator + ( const HugeInt & );
	HugeInt operator + ( int );
	HugeInt operator + ( constchar * );

	HugeInt operator * ( int );
	HugeInt operator * ( const HugeInt & );

private:
	short integer[ 30 ];

};

#endif

HugeInt.cpp:

#include <cctype>
#include <cstring>

#include "hugeint.h"

HugeInt::HugeInt( longvalue )
{
	for ( int i = 0; i <= 29; i++ )
		integer[ i ] = 0;

	for ( int j = 29; value != 0 && j >= 0; j-- ){
		integer[ j ] = value % 10;
		value /= 10;

	}

}

HugeInt::HugeInt( constchar *string )
{
	for ( int i = 0; i <= 29; i++ )
		integer[ i ] = 0;

	int length = strlen( string );

	for ( int j = 30 - length, k = 0; j <= 29; j++, k++ )

		if ( isdigit( string[ k ] ) )
			integer[ j ] = string[ k ] - '0';

}

HugeInt HugeInt::operator + ( const HugeInt &op2 )
{
	HugeInt temp;
	int carry = 0;

	for ( int i = 29; i >= 0; i-- ){
		temp.integer[ i ] = integer[ i ] + op2.integer[ i ] + carry;

		if ( temp.integer[ i ] > 9 ) {
			temp.integer[ i ] %= 10;
			carry = 1;

		}

		else
			carry = 0;

	}

	return temp;

}

HugeInt HugeInt::operator + ( int op2 )
{
	return *this + HugeInt( op2 );

}

HugeInt HugeInt::operator + ( constchar *op2 )
{
	return *this + HugeInt( op2 );

}

HugeInt HugeInt::operator * ( const HugeInt &mul )
{
	HugeInt temp;
	HugeInt tempT;
	HugeInt tempN;
	int carry = 0;
	int n = 0;

	for ( int i = 29; i >= 0; i-- ){
		
		for ( int t = 0; t <= 29; t++ ){
			tempT.integer[ t ] = 0;
			tempN.integer[ t ] = 0;

		}

		for ( int j = 29; j >= 0; j-- ){
			tempT.integer[ j ] = integer[ j ] * mul.integer[ i ] + carry;

			if ( tempT.integer[ j ] > 9 ){
				carry = tempT.integer[ j ] / 10;
				tempT.integer[ j ] %= 10;				

			}

 			else
				carry = 0;

		}
		
		for ( int y = 29; y >= 0; y-- )
			tempN.integer[ y - n ] = tempT.integer[ y ];

		++n;

		temp = temp + tempN;

	}

	return temp;

}

HugeInt HugeInt::operator * ( int mul )
{
	return *this * HugeInt( mul );

}

ostream &operator << ( ostream &output, const HugeInt &num )
{
	int i;

	for ( i = 0; ( num.integer[ i ] == 0 ) && ( i <= 29 ); i++ )
		;

	if ( i == 30 )
		output << 0;
	elsefor ( ; i <= 29; i++ )
			output << num.integer[ i ];

	return output;

}

main.cpp:

#include <iostream>

using std::cout;
using std::endl;

#include "hugeint1.h"

int main()
{
	HugeInt n1( 7654321 );
	HugeInt n2( 7891234 );
	HugeInt n3( "9999999999999999999999999" );
	HugeInt n4( "1" );
	HugeInt n5;
	HugeInt n6( 1234 );
	HugeInt n7( 3478 );

	cout << "n1 is " << n1 << "\nn2 is " << n2
		 << "\nn3 is " << n3 << "\nn4 is " << n4
		 << "\nn5 is " << n5 << "\nn6 is " << n6
		 << "\nn7 is " << n7 << "\n\n";

	n5 = n1 + n2;
	cout << n1 << " + " << n2 << " = " << n5 << "\n\n";

	cout << n3 << " + " << n4 << "\n= " << ( n3 + n4 )
		 << "\n\n";

	n5 = n1 + 9;
	cout << n1 << " + " << 9 << " = " << n5 << "\n\n";

	n5 = n2 + "10000";
	cout << n2 << " + " << "10000" << " = " << n5 << endl;

	n5 = n7 * n6;
	cout << n7 << " * " << n6 << " = " << n5 << endl;

	return 0;

}

输出结果为：

HugeInt HugeInt::operator * ( const HugeInt &mul )
{
	HugeInt temp;
	HugeInt tempT;
	HugeInt tempN;
	int carry = 0;
	int n = 0;

	for ( int i = 29; i >= 0; i-- ){
		
		for ( int t = 0; t <= 29; t++ ){
			tempT.integer[ t ] = 0;
			tempN.integer[ t ] = 0;

		}

		for ( int j = 29; j >= 0; j-- ){
			tempT.integer[ j ] = integer[ j ] * mul.integer[ i ] + carry;

			if ( tempT.integer[ j ] > 9 ){
				carry = tempT.integer[ j ] / 10;
				tempT.integer[ j ] %= 10;				

			}

 			else
				carry = 0;

		}
		
		for ( int y = 29; y >= 0; y-- )            // 移位处理
			tempN.integer[ y - n ] = tempT.integer[ y ];

		++n;

		temp = temp + tempN;

	}

	return temp;

}

       考虑到乘法运算，比如12 * 34，那么4先和12做乘法，然后3和12做乘法，之后两数相加得出结果，但是需要注意的是：3与12的乘积要左移一位后再与4和12的乘积做加法。依此类推，推之更大的数。

       主要是这个移位处理，费了我好多时间，终于搞定了~

消息循环的常见格式如下：

MSG Msg;

...

while ( GetMessage( &Msg, NULL, 0, 0 ) )

{

TranslateMessage( &Msg );

DispatchMessage( &Msg );

}

其中函数GetMessage的作用是从消息队列中读取一条信息，并将信息放在一个MSG结构中，其形式为：

GetMassage

( lpMSG,

  hwnd,

  nMsgFilterMin,

  nMsgFilterMax

)

值得注意的是，GetMessage函数中的参数nMsgFilterMin和nMsgFilterMax可实现对消息的过滤，即程序仅处理所确定的消息号范围内的消息，如果两个参数都为0，则不过滤消息。

TranslateMessag函数负责将消息的虚拟间转换为字符信息，其形式为：

TranslateMessage( lpMSG )

DispatchMessage函数将参数lpMSG指向的消息传送到指定窗口函数，其形式为：

DispatchMessage( lpMSG )

当GetMessage函数返回零值，检索到WM_QUIT时，程序将结束循环并退出。

WNDCLASS

				typedef 
				struct _WNDCLASS { 
    UINT    style; 		//窗口类样式
    WNDPROC lpfnWndProc; 	//指向窗口函数的指针int     cbClsExtra; 	//分配在窗口类结构后的字节数int     cbWndExtra; 	//分配在窗口实例后的字节数
    HANDLE  hInstance; 		//定义窗口类的应用程序的实力句柄
    HICON   hIcon; 		//窗口类的图标
    HCURSOR hCursor; 		//窗口类的光标
    HBRUSH  hbrBackground; 	//窗口类的背景刷
    LPCTSTR lpszMenuName; 	//窗口类菜单资源
    LPCTSTR lpszClassName; 	//窗口类名
} WNDCLASS; 

Members

style

Specifies the class style(s). Styles can be combined by using the bitwise OR (|) operator. This member can be any combination of the following values:

Value
Action

CS_BYTEALIGNCLIENT
Aligns the window's client area on the byte boundary (in the x direction). This style affects the width of the window and its horizontal position on the display.

CS_BYTEALIGNWINDOW
Aligns a window on a byte boundary (in the x direction). This style affects the width of the window and its horizontal position on the display.

CS_CLASSDC
Allocates one device context to be shared by all windows in the class. Because window classes are process specific, it is possible for multiple threads of an application to create a window of the same class. It is also possible for the threads to attempt to use the device context simultaneously. When this happens, the system allows only one thread to successfully finish its drawing operation. For more information, see Device Contexts.

CS_DBLCLKS
Sends double-click messages to the window procedure when the user double-clicks the mouse while the cursor is within a window belonging to the class.

CS_GLOBALCLASS
Allows an application to create a window of the class regardless of the value of the hInstance parameter passed to the CreateWindow or CreateWindowEx function. If you do not specify this style, the hInstance parameter passed to the CreateWindow (or CreateWindowEx) function must be the same as the hInstance parameter passed to the RegisterClass function.

You can create a global class by creating the window class in a dynamic-link library (DLL) and listing the name of the DLL in the registry under the following keys:

HKEY_LOCAL_MACHINE\Software
\Microsoft\Windows NT\
CurrentVersion\Windows\AppInit_DLLs

Whenever a process starts, the system loads the specified DLLs in the context of the newly started process before calling the entry-point function in that process. The DLL must register the class during its initialization procedure and must specify the CS_GLOBALCLASS style.

CS_HREDRAW
Redraws the entire window if a movement or size adjustment changes the width of the client area.

CS_NOCLOSE
Disables Close on the window menu.

CS_OWNDC
Allocates a unique device context for each window in the class.

CS_PARENTDC
Sets the clipping region of the child window to that of the parent window so that the child can draw on the parent. A window with the CS_PARENTDC style bit receives a regular device context from the system's cache of device contexts. It does not give the child the parent's device context or device context settings. Specifying CS_PARENTDC enhances an application's performance. For more information, see Device Contexts.

CS_SAVEBITS
Saves, as a bitmap, the portion of the screen image obscured by a window. The system uses the saved bitmap to re-create the screen image when the window is removed. The system displays the bitmap at its original location and does not send WM_PAINT messages to windows obscured by the window if the memory used by the bitmap has not been discarded and if other screen actions have not invalidated the stored image. This style is useful for small windows (for example, menus or dialog boxes) that are displayed briefly and then removed before other screen activity takes place. This style increases the time required to display the window, because the system must first allocate memory to store the bitmap.

CS_VREDRAW
Redraws the entire window if a movement or size adjustment changes the height of the client area.

lpfnWndProc

Pointer to the window procedure. You must use the CallWindowProc function to call the window procedure. For more information, see WindowProc.

cbClsExtra

Specifies the number of extra bytes to allocate following the window-class structure. The system initializes the bytes to zero.

cbWndExtra

Specifies the number of extra bytes to allocate following the window instance. The system initializes the bytes to zero. If an application uses WNDCLASS to register a dialog box created by using the CLASS directive in the resource file, it must set this member to DLGWINDOWEXTRA.

hInstance

Handle to the instance that the window procedure of this class is within.

hIcon

Handle to the class icon. This member must be a handle of an icon resource. If this member is NULL, an application must draw an icon whenever the user minimizes the application's window.

hCursor

Handle to the class cursor. This member must be a handle of a cursor resource. If this member is NULL, an application must explicitly set the cursor shape whenever the mouse moves into the application's window.

hbrBackground

Handle to the class background brush. This member can be a handle to the physical brush to be used for painting the background, or it can be a color value. A color value must be one of the following standard system colors (the value 1 must be added to the chosen color). If a color value is given, you must convert it to one of the following HBRUSH types:

COLOR_ACTIVEBORDER
COLOR_ACTIVECAPTION
COLOR_APPWORKSPACE
COLOR_BACKGROUND
COLOR_BTNFACE
COLOR_BTNSHADOW
COLOR_BTNTEXT
COLOR_CAPTIONTEXT
COLOR_GRAYTEXT
COLOR_HIGHLIGHT
COLOR_HIGHLIGHTTEXT
COLOR_INACTIVEBORDER
COLOR_INACTIVECAPTION
COLOR_MENU
COLOR_MENUTEXT
COLOR_SCROLLBAR
COLOR_WINDOW
COLOR_WINDOWFRAME
COLOR_WINDOWTEXT

The system automatically deletes class background brushes when the class is freed. An application should not delete these brushes, because a class may be used by multiple instances of an application.

When this member is NULL, an application must paint its own background whenever it is requested to paint in its client area. To determine whether the background must be painted, an application can either process the WM_ERASEBKGND message or test the fErase member of the PAINTSTRUCT structure filled by the BeginPaint function.

lpszMenuName

Pointer to a null-terminated character string that specifies the resource name of the class menu, as the name appears in the resource file. If you use an integer to identify the menu, use the MAKEINTRESOURCE macro. If this member is NULL, windows belonging to this class have no default menu.

lpszClassName

Pointer to a null-terminated string or is an atom. If this parameter is an atom, it must be a global atom created by a previous call to the GlobalAddAtom function. The atom, a 16-bit value, must be in the low-order word of lpszClassName; the high-order word must be zero.

If lpszClassName is a string, it specifies the window class name.

MSG

The MSG structure contains message information from a thread's message queue.

				typedef 
				struct tagMSG {     // msg 
    HWND   hwnd;     
    UINT   message; 
    WPARAM wParam; 
    LPARAM lParam; 
    DWORD  time; 
    POINT  pt; 
} MSG;

Members

hwnd

Handle to the window whose window procedure receives the message.

message

Specifies the message number.

wParam

Specifies additional information about the message. The exact meaning depends on the value of the message member.

lParam

Specifies additional information about the message. The exact meaning depends on the value of the message member.

time

Specifies the time at which the message was posted.

pt

Specifies the cursor position, in screen coordinates, when the message was posted.

POINT Structure

The POINT data structure has the following form:

				typedef
				struct tagPOINT {
   LONG x;
   LONG y;
} POINT;

The POINT structure defines the x- and y-coordinates of a point.

Members

x

Specifies the x-coordinate of a point.

y

Specifies the y-coordinate of a point.

RECT Structure

The RECT data structure has the following form:

				typedef
				struct tagRECT {
   LONG left;
   LONG top;
   LONG right;
   LONG bottom;
} RECT;

The RECT structure defines the coordinates of the upper-left and lower-right corners of a rectangle.

Members

left

Specifies the x-coordinate of the upper-left corner of a rectangle.

top

Specifies the y-coordinate of the upper-left corner of a rectangle.

right

Specifies the x-coordinate of the lower-right corner of a rectangle.

bottom

Specifies the y-coordinate of the lower-right corner of a rectangle.

Data Types

This topic lists the data types most commonly used in the Microsoft Foundation Class Library. Most of the data types are exactly the same as those in the Windows Software Development Kit (SDK), while others are unique to MFC.

Commonly used Windows SDK and MFC data types are as follows:

• BOOL   A Boolean value.
• BSTR   A 32-bit character pointer.
• BYTE   An 8-bit integer that is not signed.
• COLORREF   A 32-bit value used as a color value.
• DWORD   A 32-bit unsigned integer or the address of a segment and its associated offset.
• LONG   A 32-bit signed integer.
• LPARAM   A 32-bit value passed as a parameter to a window procedure or callback function.
• LPCSTR   A 32-bit pointer to a constant character string.
• LPSTR   A 32-bit pointer to a character string.
• LPCTSTR   A 32-bit pointer to a constant character string that is portable for Unicode and DBCS.
• LPTSTR   A 32-bit pointer to a character string that is portable for Unicode and DBCS.
• LPVOID   A 32-bit pointer to an unspecified type.
• LRESULT   A 32-bit value returned from a window procedure or callback function.
• UINT   A 16-bit unsigned integer on Windows versions 3.0 and 3.1; a 32-bit unsigned integer on Win32.
• WNDPROC   A 32-bit pointer to a window procedure.
• WORD   A 16-bit unsigned integer.
• WPARAM   A value passed as a parameter to a window procedure or callback function: 16 bits on Windows versions 3.0 and 3.1; 32 bits on Win32.

Data types unique to the Microsoft Foundation Class Library include the following:

• POSITION   A value used to denote the position of an element in a collection; used by MFC collection classes.
• LPCRECT   A 32-bit pointer to a constant (nonmodifiable) RECT structure.

typedef

typedef type-declaration synonym ;

The typedef keyword defines a synonym for the specified type-declaration. The identifier in the type-declaration becomes another name for the type, instead of naming an instance of the type. You cannot use the typedef specifier inside a function definition.

A typedef declaration introduces a name that, within its scope, becomes a synonym for the type given by the decl-specifiers portion of the declaration. In contrast to the class, struct, union, and enum declarations, typedef declarations do not introduce new types — they introduce new names for existing types.

Example

//  Example of the typedef keyword
typedef unsigned  long   ulong ;

ulong  ul;      //  Equivalent to "unsigned long ul;"

typedef  struct  mystructtag
{
    int    i;
    float  f;
    char   c;
}  mystruct;

mystruct ms;    //  Equivalent to "struct mystructtag ms;"

typedef  int  ( * funcptr)();   //  funcptr is synonym for "pointer
                            //     to function returning int"

funcptr table[ 10 ];    //  Equivalent to "int (*table[10])();"

typedef  struct  tagMSG
{    HWND  hwnd;   //  获取消息的窗口句柄，若此参数为null，则可检索所有驻留在消息队列中的消息
     UINT  message;  //  消息编号
     WPARAM # wParam;  //  消息的附加信息
     LPARAM # lParam; 
     DWORD  time;  //  指定消息发送至消息队列的时间
     POINT  pt;  //  指定消息发送时，屏幕光标的位置
}  MSG;

typedef struct tagPOINT
{    LONG x;  // x和y分别表示屏幕的横坐标和纵坐标
      LONG y;
} POINT;

消息：
      VC++中存在几种系统定义的消息分类，常用的消息分类有窗口管理消息、初始化消息、输入消息、系统消息、剪贴板消息、控制处理消息、控制通知消息、滚动条通知信息、非用户区消息、文档界面消息、DDE（动态数据交换）消息、应用程序自定义的消息等。
系统定义的消息宏前缀：
BM   按钮控制消息；
CB   组合框控制消息；
DM   默认下压式按钮控制消息；
EM   编辑控制消息；
LB    列表控制消息；
SBM   滚动条控制消息；
WM   窗口消息；

windows 应用程序常用消息：

1.在你学习C++的过程中,你首先需要扎实的实践一本C++基础教程,这个教程不在深而在全.使你能够全览之.最好结合基本数据结构来练习.不要整天Hello World~~Hello MM的.

2.再下来你需要《(More)Effective C++》,它使你可以对C++也多了份思考,也了解到一些技巧和误区,不过,你需要同步实践,不然可能一时你并不能真正掌握这些技巧、避开误区.

3.提高,你需要：(下面的书可能已经讲烂了:))

  《Design Pattern》 ：个人感觉,设计模式虽说是一种思维方式,具体实现上,只是
                        对OOP语言的发掘和巧妙组合而已.而且这里组合是主要的,
                        特性是有限的,这本书中有几个模式没用虚特性的?
   C++ Standard Document: 在你用它来做专项研究的时候,就会体会到什么才叫真正的
                                          全而深 (自然指在语法和语义的阐述上). 
  《STL源码剖析》 ：没有深厚的功底,想来个闭门造车独挑STL源码是不可能的.
                                  不过,这本说也重在关键技术的讲解和引导罢了~~
                                   这里关于GP和STL的名著不少，本人没看过。不做品评。
  《 Inside The C++ Object Model》：最具价值的一本书,没了它,C++永远是个迷,哪怕
                                    你浸淫之N载~~
  《Moden In C++ Design》 ：这里的很多思路是你自己的思维很难接触到的~~：)
                            我不得不佩服Andrei Alexandrescu.

  市面上其它的C++书籍可牛车载,我感觉除了《The Design And Evolution Of C++》是异品,值得一读.其它的不建议花太多的时间,哪怕是Bjarne Stroustrup、Stanley B.Lippman等的作品.自然,你有时间读更好,反正我现在有点后悔,当初只顾多,不顾深读,反复读.经典的书不在本数多,在于每本读的遍数多.一经验之谈,BBS上经常有人,在介绍COM技术书籍时,想也不想的指出,入门级<<Inside The COM>>.是这样的吗?我想,正如Dale Rogerson所说,将这本书完全看懂,你就是COM专家了~~书中,作者很多话可能你没有注意到,因为你还不懂之,对之没感觉,一遍翻下来,感觉 哦~~简单~全看了 :) 这些书,跟国内的很多书籍最大的不同就是
国内书籍的作者写的出,可能自己还不懂:)Copy什么资料上的:)??

4.浸淫一门语言本身的语法语义再久,你不一定能够深入它的精妙之处.
  你需要学习应用这门语言的实作品(技术),你可以研究一些FrameWork或是一些具体的技术 如CORBA、COM等.就个人而已,有心接触C++十个月左右,对于Virtual的认识有过几次较大的的改变.在《 Inside The C++ Object Model》中算第一次,在《COM本质论》中关于COM对二进制兼容布局需求而用虚机制来解决是第二次,到目前为止,使我对virtual流下最深刻印象的是在Automation技术中组件由于环境是否有能力分析virtual结构而导致是否需要分发接口的问题.如果,整天抱着《C++语法语义深入》这样的书,我不知你何时才能真正了解C++很多的特性.
  即使你可以对别人说上一大套,这行啊~那不行啊~~云云~~:)

在这整个的过程中,我喜欢这样对学弟说,你需要经常将C++的各种特性在脑中反复混合酝踉,这也是我强调学基础时,要求教材知识点全的原因.经常的,为了研究某些特性而自由的写、修改、增加UseCase,是我自认为很好的一个习惯.整天记他人的经验之言,不知几个月后还记得几层:)?

   也许上面的叙述是概括了些:)?

   总之,我认为学习C++,需要多思考(譬如你想想为什么模板类继承不支持virtual、模板
                                   类继承,基类实例和继承类实例产生的关系是什么样的)、
                      多写usecase、
                      多将一堆特性混合酝晾（譬如模板类
                                  成员签名、多种嵌套模板类成员签名、嵌套类与包裹类生命期
                                 控制等等)
                     
                      要尽早选择应用方向(这点很重要,附加个人观点：大多数人认为理论很
                                         难，可是我要说：应用一样是有难度的:)).

                      将00工程学中的理论适时的来对照自己的行为.
    

后话：
    上面提到,就应用而已,比较语言的是没有什么意义的.然而我想说的是,不敢想象
没有经过C++锤炼的人,可以深入的研究C#(事实上，我一直也不人为C#比C++好学，只是他们的深入点是不同的，冒昧说一句，C++中很多难度是人为制造出来的),就目前的情况来说,还有就是由于C++历史、
社团、资源等因素.