Falling into Infinity

MBRwizard

휘님 — Wed, 10 Sep 2008 02:32:38 GMT

MBRwizard is a powerful, yet flexible utility designed to assist with all types of Master Boot Record difficulties. Intially developed to overcome MBR problems introduced by disk imaging products such as Symantec Ghost and Acronis True Image, MBRwizard has become a popular utility for repairing all types of MBR problems, especially those caused by disk-2-disk (d2d) and system backup and recovery applications

MBR Operations

MBR 저장 또는 삭제

백업된 MBR 복구

Wipe MBR

훼손된 MBR 정정

새로운 MBR 생성

디스크 Signature 수정

파티션 테이블 엔트리 정렬

섹터 복사

존재하는 MBR 삭제

Partition Operation

파티선 삭제

숨기기/보이기 파티션

Bootable/Active 파티션 셋팅

파티션 타입 변경

추가기능

전체 디시크 안전하게 와이핑

부팅 메뉴 - 부팅 가능한 파티션 선택

영구적인 상태 바이트 유지

MBR의 내용을 갖는 ini 파일 생성

머신 종료/재부팅

Downloads

3개의 Release 버전(Windows XP/PE/2003, DOS/Win9x, Linux)이 있으며 3개의 Beta-Version이 있다.

Released Versions

Platform	Version	Release Date
Windows XP/PE/2003	1.53	August 24, 2004
DOS/Win9x	1.52	November, 11, 2003
Linux	1.52	November 11, 2003

Pre-release, Beta Versions

Platform	Version	Release Date	Notes
Windows XP/PE/2003	2.0 beta	November 15, 2005
Windows 64 bit	2.0 beta	November 15, 2005
DOS/Win9x	2.0 beta	November, 15, 2005	*does not include WipeDisk functionality

Operational Command

/List - Display the partitions listed in the MBR, their order in the MBR, partition type, size, and whether active or hidden. The Pos field indicates the order the partitions are laid out on disk, while MBRndx shows them as they're listed in the MBR.

/Disk=# - Selects the disk to use for all operations. This switch is always processed first, verifying that all operations specified on the command line will use the disk specified here. If not specified, Disk 0 will be used by default.

/Part=# - Selects the partition to use for all partition based operations. If not specified, partition '0' will be used by default. All operations use the physical location of the partition on the disk (the first column in /list), not the MBRndx field which simply identifies the current position of the partition entry in the MBR. Certain commands allow the action to be performed on all partitions, in this case /Part=* (asterisk) performs this functionality.

/Sector=# - Selects the sector to use with sector based operations. Sector 0 (MBR) will be used by default if not specified.

MBR Commands

/Save=filename - Saves the current MBR to a file, where filename is the path+filename used to store the file. Specifying /Sector=# on the command line will save the sector # specified rather than the MBR (Sector 0).

/Restore=filename - Reads an MBR file from filename, where filename is an existing path+filename containing the backed up contents of the MBR sector. Optionally, specifying the /Sector=# parameter will restore the file to sector # rather than 0 (MBR).

/Repair=# - Designed to create a new Master Boot Record on a blank disk, or fix a damaged, corrupt, or missing MBR. Specifying an option of '1' will save a PE/XP/2003 MBR to the specifed disk. This may be expanded to other OS formats if the need exists. Note, this option will not modify the partition table.

/Show=x - Shows the partition structure from a backed up MBR. Available options for x are a filename, the sector number containing the backup, or the word SECTOR if the contents have been previously saved to the hidden sector.

/Wipe=x - Selecting an option of 'mbr' will wipe the MBR clean, 'head' will wipe the first head or 63 sectors, and a range of sectors from x to y can be wiped by specifying /Wipe=x-y. This will effectively remove all information from the specified sectors of the disk.

/Sort - It isn’t uncommon for the partition entries in the MBR to be unsorted after reinstalling Windows or restoring a Ghost or Acronis disk image. This means that the partition order in the MBR won't match the order on disk. Normally this wasn’t a problem until Windows NT/2K/XP came along with its new boot loader, and the requirement that each partition entry in the boot.ini must point to the actual partition number. This option will sort the entries in the MBR to match their physical order on disk.

/IsSorted - Queries the partition entry order in the MBR and returns an ErrorLevel code based on the status of the partition entries: '0' = Sorted, '1' = Not Sorted

/Signature=x - Reads or Writes a new disk signature to the MBR. Specifying 'Zero' will clear the existing signature, otherwise an 8 digit hex entry can be entered for the signature. For example, /Signature= Zero, or /Signature= AC87AD87. Specifying /Signature with no options will display the existing disk signature.

/Copy=x - Copies the contents of one sector to another. The /Sector=x command will specify the source sector, and will be copied to the sector specified by /Copy. Please note, typically only the first 64 sectors (0-63) should be used as the destination, otherwise existing data on the hard disk may be overwritten. Selecting 0 as the target will overwrite and erase the contents of the MBR.

Partition Options

/Hide=# - Hides or Unhides the specified partition to the operating system. An option of '1' or 'Yes' will hide the partition, while selecting '0' or 'No' will set the partition visible. If /Part=* is specified all partitions will be hidden/unhidden.

/Active=# - Sets the specified partition status as active (bootable) or inactive. Specifying the parameter as '1' or 'Yes' will set the partition active, while an option of '0' or 'No' will set the partition non-bootable. /Part=* can be selected to set all partitions inactive. If setting the a hidden partition active, it will first be unhidden before being set active. Note for older operating systems: DOS and Win9x do not properly recognize multiple visible primary partitions, make certain any remaining primary partitions are unhidden if necessary.

/Type=# - Modifies the partition type in the MBR. Please note that this does not attempt to convert the actual partition and file system to a new type. This is generally required when a partitioning or backup/restore program modifies the partition type and it needs to be restored back to the original type. The # specified must be directly followed by either a d (decimal) or h (hexadecimal) in order to properly identify the new type. This option must be used with /Partition in order to identify the partition being modified.

/Del - Deletes the specified partition. Specifying /Part=* removes all partitions on selected disk, while specifying both /Disk=* /Part=* removes all partitions on all disks.

Miscellaneous Options

/Shutdown=# -An entry of '1' will force Windows to shutdown, '2' will force Windows to shutdown and reboot. '3' shuts down without force, and '4' reboots without force. Note, using the Force options may cause data loss if open programs contain unsaved data. NT/2K/XP/2003 version only.

/WipeDisk=# - Wipes (overwrites) each sector on the disk in order to securely erase all data. Selecting an option of '1' write zeros to all sectors, additional methods coming. Please note, MBRwizard can not completely wipe the system disk (C: drive) when running from Windows, as the machine will blue screen once operating system files are overwritten. An alternative option is to securely wipe the disk from WinPE, which boots from CD or USB Flash Disk, and doesn't have the same limitations. This option is currently only available under the Windows version.

/Status=x - Stores or Retrieves the status byte located at offset 0x1b2 in the MBR, which is widely recognized as an unused section of the MBR. This option allows a single byte to be stored to this unused location of the hard disk, used mainly as a status indicator for provisioning or deployment projects. Specifying a value for 'x' will set the status byte, valid options are 0-255. Selecting /Status with no options will return the current byte upon program exit.

/Confirm - Any operation that performs a change to the MBR will now ask for user confirmation before making the change. Specifying /confirm on the command line overrides this request and defaults to Yes for each operation without prompting.

/BootMenu -This option will list the available, bootable partitions to the user, and set one active by secting from the menu

/Msg=# - Hides the status messages shown upon program exit. An entry of '1' indicates that no messages should be shown, '2'=No error messages, and '3'=No status messages displayed on success.

/Ignore - Attempts to continue the specified operation if an error occurs.

/Result - Displays the return code for visual verification of success/failure.

/? - Show command line options

이 글은 스프링노트에서 작성되었습니다.

AutoIt FAQ

휘님 — Wed, 10 Sep 2008 02:26:37 GMT

Frequently Asked Questions (FAQ)

This section gives some of the more frequently asked questions from the forum. If you can't find the answer you seek here then the forum should be your first port of call.

Questions

1. Why doesn't my old AutoIt v2.64 script run in v3?

2. Isn't v3 much more difficult than previous versions?

3. How can I convert my v2.64 scripts to v3?

4. Where is the "goto" command?

5. How can I run a DOS program from within AutoIt?

6. Why can I only use Run() to execute .exe and .com files? What about .msi / .txt and others?

7. Why do I get errors when I try and use double quotes (") ?

8. What do the window "title" and "text" parameters mean?

9. Why can't I print a variable using "My var is $variable"?

10. When I use Send() to send a variable odd things happen?

11. What is the difference between the return value and @error?

12. How can I exit my script with a hot-key?

13. How can I use a custom icon when compiling my scripts?

14. How can I make sure only one copy of my script is run?

15. What are the current technical limits of AutoIt v3?

16. I get a missing picture symbol in the Help file under the Examples.

1. Why doesn't my old AutoIt v2.64 script run in v3?

v3 has a different language structure to v2.64.

Previous versions of AutoIt were fine for what they were designed for - writing simple scripts to help with software installations. Over time people began using it for general and complicated scripting tasks. The old syntax and structure made this possible but very very difficult and cumbersome. The decision was made to make AutoIt more suitable for general automation tasks and to achieve that a more standard and basic-like language was made. This also means that if you already know a scripting language you will pick AutoIt v3 up easily.

2. Isn't v3 much more difficult than previous versions?

No. In fact in many instances it's much easier than previous versions as you don't have to try and force the language to do something it was never designed to do. It also uses a familiar BASIC-like language, and BASIC is known for being...well...basic :)

The vast majority of old AutoIt scripts were focused around software installation and clicking "Next" a lot in dialog boxes. Most of these scripts can be converted to v3 simply by adding a couple of brackets here and there. Here is an example of such a script in v2 and v3 (simulating a software installation with a few dialogs that have a Next button and a Finish button)

; v2.64 Script

WinWaitActive, Welcome, Welcome to the XSoft installation

Send, !n

WinWaitActive, Choose Destination, Please choose the

Send, !n

WinWaitActive, Ready to install, Click Next to install

Send, !n

WinWaitActive, Installation Complete, Click Finish to exit

Send, !f

WinWaitClose, Installation Complete

; v3 Script

WinWaitActive("Welcome", "Welcome to the XSoft installation")

Send("!n")

WinWaitActive("Choose Destination", "Please choose the")

Send("!n")

WinWaitActive("Ready to install", "Click Next to install")

Send("!n")

WinWaitActive("Installation Complete", "Click Finish to exit")

Send("!f")

WinWaitClose("Installation Complete")

Now, that wasn't so bad! :) As all "strings" are enclosed in quotes you no longer have to wrestle with problems caused by leading and trailing spaces in text. There is also fantastic support for many text editors so that when you are writing v3 scripts you can have syntax highlighting which makes everything much easier.

3. How can I convert my v2.64 scripts to v3?

The first thing you should ask yourself is "Do I need to convert my script?". v2.64 will continue to be downloadable and supported so don't update all your scripts just for the sake of it - well not unless you want to :)

There is a section in the Help file that shows how the commands in v2 and v3 are related - click here to see the page.

One of the AutoIt v3 authors has written a utility to automatically convert v2 scripts to v3. Conversion is pretty good unless your code is a rats-nest of gotos :) You can find the converter in the "Extras" directory (Start \ AutoIt v3 \ Extras - or look in the directory that you installed AutoIt v3).

4. Where is the "goto" command?

Gone. It's evil. No, you can't ask why - it just is. It's like that lump of rock they find in the microwave at the end of the film Time Bandits :)

AutoIt v3 features most of the common "loops" in use today and with these Goto is no longer required. Look up While, Do, For, ExitLoop, ContinueLoop and Functions for the modern way of doing things :) And while you are looking at help file sections check out these on loops, conditional statements and functions. I promise you, once you have got the hang of such things you will be able to script in virtually any other language within a couple of minutes.

Just to get you started, the most basic use of Goto in version 2.64 was an infinite loop like:

:mylabel

...do something...

...and something else...

goto, mylabel

A simple v3 version of that is a While loop that is always "true".

While 1 = 1

...do something...

...do something else...

Wend

5. How can I run a DOS program from within AutoIt?

If you wanted to run something like a DOS "Dir" command then you must run it though the command interpreter (command.com or cmd.exe depending on your OS). The @Comspec macro contains the correct location of this file. You should use the RunWait() function as it waits for the DOS program to finish before continuing with the next line of the script. Here is an example of running the DOS Dir command on the C: drive: (effectively running the command command.com /c Dir C:\ )

RunWait(@COMSPEC & " /c Dir C:\")

6. Why can I only use Run() to execute .exe files? What about .msi / .txt and others?

Only a few file extensions are usually "runable" - these are .exe, .bat, .com, .pif. Other file types like .txt and .msi are actually executed with another program. When you double click on a "myfile.msi" file what actually happens in the background is that "msiexec.exe myfile.msi" is executed. So to run a .msi file from AutoIt you would do:

RunWait("msiexec myfile.msi")

Or, run the command "start" which will automatically work out how to execute the file for you:

RunWait(@COMSPEC & " /c Start myfile.msi")

Or, use the ShellExecuteWait function which will automatically work out how to execute the file for you:

ShellExecuteWait("myfile.msi")

7. Why do I get errors when I try and use double quotes (") ?

If you want to use double-quotes inside a string then you must "double them up". So for every one quote you want you should use two. For example if you wanted to set a variable to the string: A word in "this" sentence has quotes around it! You would do:

$var = "A word in ""this"" sentence has quotes around it!"

or use single quotes instead:

$var = 'A word in "this" sentence has quotes around it!'

8. What do the window "title" and "text" parameters mean?

There is a detailed description here.

9. Why can't I print a variable using "My var is $variable"?

If you have a variable called $msg and you want to print in inside a MsgBox then this will NOT work:

MsgBox(0, "Example", "My variable is $msg")

It will actually print My variable is $msg . What you need to do is tell AutoIt to join the string and the variable together using the & operator:

MsgBox(0, "Example", "My variable is " & $msg)

Advanced: If you have many variables to add into a string then you may find the StringFormat() function useful. For example, if I wanted to insert $var1 to $var5 into a string then it may be easier to do:

$msg = StringFormat("Var1 is %s, Var2 is %s, Var3 is %s, Var4 is %s, Var5 is %s", $var1, $var2, $var3, $var4, $var5)

MsgBox(0, "Example", $msg)

10. When I use Send() to send a variable odd things happen?

If you are sending the contents of a variable then be mindful that if it contains special send characters like ! ^ + {SPACE} then these will be translated into special keystrokes - rarely what is wanted. To overcome this use the RAW mode of Send() that does not translate special keys:

Send($myvar, 1)

11. What is the difference between the return value and @error?

Generally a return value is used to indicate the success of a function. But, if a function is already returning something ( like WinGetText() ) then we need to have a way of working out if the function was successful, so we set @error instead.

12. How can I exit my script with a hot-key?

Ah, an easy one. If you want to make your script exit when you press a certain key combination then use the HotKeySet() function to make a user function run when the desired key is pressed. This user function should just contain the Exit keyword.

Here some code that will cause the script to exit when CTRL+ALT+x is pressed:

HotKeySet("^!x", "MyExit")

...

...

; Rest of Script

...

...

Func MyExit()

Exit

EndFunc

13. How can I use a custom icon when compiling my scripts?

You need to run the full compiler program (rather than just right-clicking a script and selecting compile). This page describes the compiler in detail.

14. How can I make sure only one copy of my script is run?

Use the _Singleton() function. See the User Defined Functions documentation for more information on _Singleton() and how to use it.

15. What are the current technical limits of AutoIt v3?

Here are details of the current technical limits of AutoIt. Please note that some of the limits are theoretical and you may run into performance or memory related problems before you reach the actual limit.

Maximum length of a single script line: 4,095

Maximum string length: 2,147,483,647 characters

Number range (floating point): 1.7E–308 to 1.7E+308 with 15-digit precision

Number range (integers): 64-bit signed integer

Hexadecimal numbers: 32-bit signed integer (0x80000000 to 0x7FFFFFFF)

Arrays: A maximum of 64 dimensions and/or a total of 16 million elements

Maximum depth of recursive function calls: 5100 levels

Maximum number of variables in use at one time: No limit

Maximum number of user defined functions: No limit

Maximum number of GUI windows: No limit

Maximum number of GUI controls: 65532

16. I get a missing picture symbol in the Help file under the Examples.

This should be the Open button that enable you to open the Examples in the Help file.

This issue is that the hhctrl.ocx isn't properly registered or corrupted.

Try registering it by doing "regsvr32 hhctrl.ocx" from the command prompt or check if the file is still valid.

이 글은 스프링노트에서 작성되었습니다.

tag : AutoIt, Programming

AutoIt GUI Reference - OnEvent Mode

휘님 — Wed, 10 Sep 2008 02:22:32 GMT

GUI Reference - OnEvent Mode

OnEvent 모드에서는 GUI가 사용자의 스크립트를 멈추도록 만드는 어떤 것을이 일어났는지 알기 위해 GUI를 항상 Polling하는 대신에 이벤트를 처리하기 위해 사용자가 미리 정의한 함수를 호출한다. 예를들어, 사용자가 Button1을 클릭하면 GUI는 사용자의 메인 스크립트를 중지시키고 Button1과 연관된 미리 사용자가 정의한 함수를 호출한다. 미리 정의된 함수의 호출이 끝나고 나면 메인 스크립트가 재시작된다. 이 모드는 Visual Basic forms metohd와 유사하다.

GUI가 실행될 때, 사용자의 메인 스크립트는 임의의 스크립트를 실행시킬 수 있다.

Default 모드는 MessageLoop 모드이므로 OnEvent 모드를 사용하기 전에 Opt("GUIOnEventMode", 1)을 호출해야 한다.

기본적인 OnEvent 형식

일반적인 OnEvent 코드의 형태는 다음과 같다.

While 1

Sleep(1000) ; Just idle around

WEnd

Func Event1()

; Code to handle event goes here

EndFunc

Func Event2()

; Code to handle event goes here

EndFunc

GUI 이멘트

OnEvent 모드에서 사용자 GUI는 다음과 같은 이벤트들을 생성할 수 있다.

컨트롤 이벤트

시스템 이벤트

GUI에 대해서는 GUISetOnEvent 또는 컨트롤에 대해서는 GUICtrlSetOnEvent가 정의되어 있고 둘중 하나의 이벤트가 발생하면 사용자가 미리 정의한 함수를 호출한다. 이벤트에 대해 미리 정의된 함수가 없다면, 그 이벤트는 무시된다. When inside this called function various macros will be set to values to help process the event.

매크로	설명
@GUI_CTRLID	메시지 또는 시스템 ID를 전달하는 컨트롤의 ID를
@GUI_WINHANDLE	메시지를 전달하는 GUI 핸들
@GUI_CTRLHANDLE	메시지를 전달하는 컨트롤의 핸들

Note : 다양한 이벤트에 대한 같은 함수를 사용하는 것은 가능하다. 이러한 경우 사용자가 필요한 것은 @GUI_CTRLID를 기반으로 한 액션을 처리하는 것이다. 예를 들어, 사용자는 모든 시스템 이벤트에 대해 동일한 함수를 등록할 수 있다.

컨트롤 이벤트

컨트롤이 클릭되거나 변화되면 컨트롤 이벤트가 발생한다. CUICtrlSetEvent를 통해 정의된 함수에 이벤트가 전달된다. 내부적으로 사용자가 정의한 함수에서 @GUI_CTRLID은 GUICtrlCreate...를 통해 컨트롤을 만들때 리턴된 controlID이 정의된다.

시스템 이벤트

GUI를 닫는 것과 같은 시스템 이벤트는 컨트롤 이벤트와 유사하게 전달되지만 컨트롤 이벤트는 @GUI_CTRLID에 의해 정의된다. 이벤트는 GUISetOnEvent에 의해 정의된 함수에 전달된다. 가능한 시스템 이벤트는 값은 다음과 같다.

$GUI_EVENT_CLOSE

$GUI_EVENT_MINIMIZE

$GUI_EVENT_RESTORE

$GUI_EVENT_MAXIMIZE

$GUI_EVENT_PRIMARYDOWN

$GUI_EVENT_PRIMARYUP

$GUI_EVENT_SECONDARYDOWN

$GUI_EVENT_SECONDARYUP

$GUI_EVENT_MOUSEMOVE

$GUI_EVENT_RESIZED

$GUI_EVENT_DROPPED

GUI 예제

사용자는 위에서 언급한 이벤트 메시지중 몇몇와 OnEvent를 사용하여 코드를 끝낼 수 있다.

#include

Opt("GUIOnEventMode", 1)

$mainwindow = GUICreate("Hello World", 200, 100)

GUISetOnEvent($GUI_EVENT_CLOSE, "CLOSEClicked")

GUICtrlCreateLabel("Hello world! How are you?", 30, 10)

$okbutton = GUICtrlCreateButton("OK", 70, 50, 60)

GUICtrlSetOnEvent($okbutton, "OKButton")

GUISetState(@SW_SHOW)

While 1

Sleep(1000)

WEnd

Func OKButton()

   ;Note : at this point @GUI_CTRLID would equal $GUI_EVENT_CLOSE,

   ; and @GUI_WINHANDLE would equal $mainwindow

   MsgBox(0, "GUI Event", "You pressed OK!")

Exit

EndFunc

Func CLOSEClicked()

   ;Note: at this point @GUI_CTRLID would equal $GUI_EVENT_CLOSE

   ; and @GUI_WinHandle would equal $mainwindow

   MsgBox(0, "GUI Event", "You clicked CLOSE! Exiting...")

   Exit

EndFunc

발전된 오퍼레이션과 다수의 윈도우

다수의 윈도우에서도 ControlID는 유일하다. 그러나 사용자는 어떻게 다수의 윈도우를 처리할 수 있을까?

여기 다른 Dummy 윈도우와 함께 처리하는 유사한 예제가 있다.

#include

Opt("GUIOnEventMode", 1)

$mainwindow = GUICreate("Hello World", 200, 100)

GUISetOnEvent($GUI_EVENT_CLOSE, "CLOSEClicked")

GUICtrlCreateLabel("Hello world! How are you?", 30, 10)

$okbutton = GUICtrlCreateButton("OK", 70, 50, 60)

GUICtrlSetOnEvent($okbutton, "OKButton")

$dummywindow = GUICreate("Dummy window for testing ", 200, 100)

GUISetOnEvent($GUI_EVENT_CLOSE, "CLOSEClicked")

GUISwitch($mainwindow)

GUISetState(@SW_SHOW)

While 1

Sleep(1000)

WEnd

Func OKButton()

   ;Note : at this point @GUI_CTRLID would equal $GUI_EVENT_CLOSE,

   ; and @GUI_WINHANDLE would equal $mainwindow

   MsgBox(0, "GUI Event", "You pressed OK!")

   Exit

EndFunc

Func CLOSEClicked()

   ;Note: at this point @GUI_CTRLID would equal $GUI_EVENT_CLOSE

   ; and @GUI_WinHandle would equal $mainwindow

   If @GUI_WinHandle = $mainwindow Then

      MsgBox(0, "GUI Event", "You clicked CLOSE! Exiting...")

      Exit

   EndIf

EndFunc

첫번째 변화는 GUISwitch 함수의 호출이다. 새로운 윈도우가 만들어지면 추후에 발생하는 GUI 오퍼레이션이 Default 윈도우가 된다.(컨트롤 생성을 포함해서) 이와 같은 예제의 경우, "Hello World" 윈도우를 통해 작업해야 한다. 그래서 Switch가 필요하다. 몇몇 GUI 함수는 호출하는 그 자체로 사용자가 윈도우 핸들의 사용하는 것을 허용한다. 이러한 함수들은 윈도우를 자동으로 스위치한다. 그러기 위해서는 다음과 같이 함수를 호출한다.

GUISetState(@SW_SHOW, $mainwindow)

위의 코드에서는 두 개의 윈도우에 대해 버튼을 "Close"하는 이벤트를 처리하기 위해 같은 OnEvent 함수를 사용했고 어떤 윈도우가 메시지를 전전달했는지 알기 위해 @GUI_WINHANDLE를 사용했다.(사용자가 Close 버튼을 클릭했을 때, 메시지는 메인 윈도우로부터 전달된 된다.) 사용자가 희망한다면 각각의 윈도우에 대해 함수들을 분리할 수 있다.

이 글은 스프링노트에서 작성되었습니다.

tag : AutoIt, Programming

AutoIt GUI Reference - MessageLoop Mode

휘님 — Wed, 10 Sep 2008 02:22:02 GMT

GUI Reference - MessageLoop Mode

Message-loop 모드에서 사용자 스크립트는 tight-loop에서 대부분의 시간을 보낸다. 이 루프는 GUIGetMsg 함수를 사용하여 GUI를 Pool한다. 이벤트가 발생할 때, GUIGetMsg 함수의 리턴 값은 이벤트에 대한 자세한 사항을 나타낸다. MessageLoop 모드는 AutoIt GUI에 대한 기본 메시지 모드이며 다른 가능한 모드는 OnEvent 모드가 있다.

In the MessageLoop mode you will only receive events while you are actively polling the GUIGetMsg function so you must ensure that you call it many times a second otherwise your GUI will be unresponsive.

기본 MessageLoop 형태

MessageLoop 코드의 일반적인 형태

Whilw 1

$msg = GUIGetMsg()

WEnd

Usually a tight loop like the one shown would send the CPU to 100% - fortunately the GUIGetMsg function automatically idles the CPU when there are no events waiting. Do not put a manual sleep in the loop for fear of stressing the CPU - this will only cause the GUI to become unresponsive.

GUI Events

GUIGetMsg가 리턴하는 이벤트 메시지는 세가지가 있다.

이벤트 없음(No Event)

컨트롤 이벤트(Control Event)

시스템 이벤트(System Event)

이벤트 없음(No Event)

이벤트가 없을 때, GUIGetMsg가 리턴하는 0을 처리하는 것을 기다린다.

컨트롤 이벤트(Control Event)

사용자가 컨트롤을 클릭하거나 변경하여 이벤트가 전달되면, 이 이벤트는 GUICtrlCreate... 함수들에 의해 컨트롤을 만들었을때 생성된 controlID에 해당하는 양수 값이다.

시스템 이벤트(System Event)

시스템 이벤트는 GUI를 닫는 것과 같은 음수 값이다. 다른 이벤트들은 아래와 같으며, GUIConstantEx.au3에 정의되어 있다.

$GUI_EVENT_CLOSE

$GUI_EVENT_MINIMIZE

$GUI_EVENT_RESTORE

$GUI_EVENT_MAXIMIZE

$GUI_EVENT_PRIMARYDOWN

$GUI_EVENT_PRIMARYUP

$GUI_EVENT_SECONDARYDOWN

$GUI_EVENT_SECONDARYUP

$GUI_EVENT_MOUSEMOVE

$GUI_EVENT_RESIZED

$GUI_EVENT_DROPPED

예제 GUI

GUI Referance page에서 아래에 있는 Hello World 예제를 보았다.

#include

GUICreate("Hello World", 200, 100)

GUICtrlCreateLabel("Hello world! How are you?", 30, 10)

GUICtrlCreateButton("OK", 70, 50, 60)

GUISetState(@SW_SHOW)

Sleep(2000)

자, 우리는 MessageLoop를 사용한 코드를 끝낼 것이며 몇몇 이벤트 메시지들을 위에서 설명했다.

#include

GUICreate("Hello Word", 200, 100)

GUICtrlCreateLabel("Hello World! How are you?", 30, 10)

$okbutton = GUICtrlCreateButton("OK", 70, 50, 60)

GUISetState(@SW_SHOW)

While 1

$msg = GUIGetMsg()

Select

Case $msg = $okbutton

MsgBox(0, "GUI Event", "You pressed OK!")

Case $msg = $GUI_EVENT_CLOSE

MsgBox(0, "GUI Event", "You clicked CLOSE! Exiting...")

ExitLoop

EndSelect

WEnd

발전된 GUIGetMsg와 다수의 윈도우

사용자가 다수의 윈도우들을 가지고 있더라고 Control_ID들은 유일하기 때문에, 위의 코드는 다수의 윈도우와 컨트롤이 있다 하더라도 잘 동작한다. 그러나 $GUI_EVENT_CLOSE 또는 $GUI_MOUSEMOVE와 같은 이벤트들을 처리할 때, 어떤 윈도위가 이벤트를 발생시켰는지 알아야 할 필요가 있다. 이것을 하기 위해서 사용자는 GUIGetMsg를 다음과 같이 호출해야 한다.

$msg = GUIGetMsg(1)

사용자가 파라미터 1을 가지고 호출하면 이벤트 값을 리턴하는 대신 배열을 리턴한다. 이 배열은 $array[0]에 이벤트 값을 저장하고 있고 윈도우 핸들($array[1]과 같은 남은 정보들을 저장한다. 이전 예제에서 두 개의 윈도우가 만들어졌다면, 코드를 다음과 같이 작성해야 한다.

#include

$mainwindow = GUICreate("Hello World", 200, 100)

GUICtrlCreateLabel("Hello World! How are you?", 30, 10)

$okbutton = GUICtrlCreateButton("OK", 70, 50, 60)

$dummywindows = GUICreate("Dummy window for testing ", 200, 100)

GUISwitch($mainwindow)

GUISetState(@SW_SHOW)

While 1

   $msg = GUIGetMsg(1)

    Select

      Case $msg[0] = $okbutton

         MsgBox(0, "GUI Event", "You pressed OK!")



      Case $msg[0] = $GUI_EVENT_CLOSE and $msg[1] = $mainwindow

         MsgBox(0, "GUI Event", "You clicked CLOSE on the main window! Exiting...")

         ExitLoop

   EndSelect

WEnd

첫번째 주요 변화는 GUISwitch 함수의 호출이다. 하나의 새로운 윈도우가 만들어지면 향후 GUI 작업을 위한 기본 윈도우가 된다.(컨트롤의 생성도 포함된다.) 사용자는 테스트 윈도우가 아닌 메인 "Hellow World" 윈도우를 가지고 작업하기를 원한다.몇몇 GUI 함수는 사용자가 함수 스스로 윈도우 핸들을 사용하도록 허락한다. 사용자는 다음 함수를 사용하여 사용될 윈도우 핸들에 대해 자동으로 전환할 수 있다.

GUISetState(@SW_SHOW, $mainwindow)

다음 변화는 GUIGetMsg 함수가 호출되는 방법과 이벤트들이 어떻게 확인되는지($msg[0]과 $msg[1]을 사용하여)에 대한 것이다. 이 스크립트는 Close 이벤트가 메인 윈도우로부터 발생하면 종료된다.

이 글은 스프링노트에서 작성되었습니다.

tag : AutoIt, Programming

AutoIt GUI Reference - GUI Concepts

휘님 — Wed, 10 Sep 2008 02:21:52 GMT

GUI Reference

AutoIt은 GUI를 구성하는 윈도우와 컨트롤을 쉽게 만들 수 있다.

GUI Concepts

GUI는 하나 이상의 윈도우를 가지고 있으며 윈도우는 하나 이상의 컨트롤들을 가지고 있다. GUI는 "Event Driven"으로 사용자가 버튼을 클릭하는 것과 같은 이벤트를 발생시킨다는 것을 의미한다. 사용자는 어떤 이벤트가 발생하기를 기다리는데 많은 시간을 소비한다. 이점이 다른 스크립트와 다른 점이다. 물론 GUI가 활성화 될 때까지 다른 일을 하도록 할 수 있다.

GUI 컨트롤

사용자가 윈도우에서 클릭할 수 있는 임의의 것들이 모두 컨트롤이다. AutoIt이 만들 수 있는 컨트롤은 다음과 같다.

Label - A plain piece of text.

Button - A simple button.

Input - A single line control that you can enter text into.

Edit - A multi-line control that you can enter text into.

Checkbox - A box that can be "checked" or "unchecked".

Radio - A set of circular buttons - only one can be active at once.

Combo - A list with a dropdown box.

List - A list.

Date - A date picker.

Pic - A picture.

Icon - An icon.

Progress - A progress bar.

Tab - A group of controls that are contained in tabs.

UpDown - A control that can be added to input controls.

Avi - Display an AVI format clip.

Menu - A menu across the top of the window.

ContextMenu - A menu that appears when you right click inside the window.

TreeView - A control similar to the windows file-explorer.

Slider - A control similar to the windows sound volume control.

ListView - A control displaying columns information.

ListViewItem - A control displaying item in a listview control.

Graphic - A control displaying graphics drawn with GUICtrlSetGraphic.

Dummy - A dummy user control

컨트롤은 GUICtrlCreate...와 같은 함수들의 집합으로 만들 수 있다. 컨트롤이 만들어지면 Control ID를 리턴한다.

Control ID는 양수이다.

각각의 Control ID는 유일하다.

Control ID는 AutoIt Window Info Tool에서 보여주는 Control ID와 같은 값이다.

GUI 기초 함수

함수	설명
GUICreate	윈도우를 생성한다.
GUICtrlCreate...	윈도우에 다양한 컨트롤을 생성한다.
GUISetState	윈도우를 보여주거나 숨긴다.
GUIGetMsg	이벤트가 발생한 것을 보기 위해 GUI를 Poll한다.
GUICtrlRead	컨트롤에서 데이터를 읽는다.
GUICtrlSetData	컨트롤의 데이터를 정의하거나 변환한다.
GUICtrlSet...	컨트롤에 대한 다양한 옵션을 변경한다.

GUI와 연관된 기초적인 상수를 사용하기 위해 #include 가 필요하다.

먼저 "Hello World"를 호출하는 윈도우를 만들어보자. 윈도우를 새로 만들면 Hidden 상태이므로 만드시 "show"해야 한다.

#include

GUICreate("Hello World", 200, 100)

GUISetState(@SW_SHOW)

Sleep(2000)

위에서 만든 윈도우에 텍스트와 OK 버튼을 추가하자.

텍스트는 30, 10 위치에 추가하고 버튼은 70, 50 위치에 폭 60픽셀로 추가한다.

#include

GUICreate("Hello World", 200, 100)

GUICtrlCreateLabel("Hello world! How are you?", 30, 10)

GUICtrlCreateButton("OK", 70, 50, 60)

GUISetState(@SW_SHOW)

Sleep(2000)

이제 OK 버튼을 클릭하여 어떻게 동작하게 해야 할까? 이와 같은 것을 하기위해서는 MessageLoop 또는 OnEvent 함수들을 통해 이벤트를 처리해야 한다. 기본값은 MessageLoop 모드이고 OnEvent 모드로 전환하기 위해서 Opt("GUIOnEventMode", 1)을 호출한다.

Message-loop Mode (default)

Message-loop 모드에서 사용자 스크립트는 tight-loop에서 대부분의 시간을 보낸다. 이 루프는 GUIGetMsg 함수를 사용하여 GUI를 Pool한다. When an event has occurred the return value of the GUIGetMsg function will show the details (a button is clicked, the GUI has been closed, etc.).

In this mode you will only receive events while you are actively polling the GUIGetMsg function so you must ensure that you call it many times a second otherwise your GUI will be unresponsive.

This mode is best for GUIs where the GUI is "king" and all you care about is waiting for user events.

See this page for a more detailed explanation of the MessageLoop mode.

OnEvent Mode

In the OnEvent mode instead of constantly polling the GUI to find out if anything has happened you make the GUI temporarily pause your script and call a pre-defined function to handle the event. For example, if the user clicks Button1 the GUI halts your main script and calls a previously defined user function that deals with Button1. When the function call is completed the main script is resumed. This mode is similar to the Visual Basic forms method.

This mode is best for GUIs where the GUI is of secondary importance and your script has other tasks to perform in addition to looking after the GUI.

See this page for a more detailed explanation of the OnEvent mode.

이 글은 스프링노트에서 작성되었습니다.

tag : AutoIt, Programming

AutoIt Tutorial - Simple Notepad Automation

휘님 — Wed, 10 Sep 2008 02:21:06 GMT

Tutorial - Notepad

다음 예제는 메모장을 자동으로 열고 임의의 문자를 자동으로 추가하고 메모장을 닫는 것을 보여준다.

우선 npad.au3라 불리는 빈 스크립트 파일을 만들고 파일을 수정한다.

메모장을 실행하기 위해서 AutoIt은 Run 함수를 사용한다. 이 함수는 간단하게 주어진 실행가능한 응용프로그램을 실행한다.

Run("notepad.exe")

WinWaitActive("제목 없음 - 메모장")

Send("This is some text.")

WinClose("제목 없음 - 메모장")

WinWaitActive("메모장", "변경된 내용을 저장하시겠습니까?")

Send("!n")

Run("notepad.exe") - 메모장 실행

WinWaitActive("제목 없음 - 메모장") - 메모장(제목 없음 - 메모장 이라는 제목을 갖고 있는)이 활성화 되는 것을 확인

Send("This is some text.") - 메모장에 This is some text. 입력

WinClose("제목 없음 - 메모장") - 메모장(제목 없음 - 메모장 이라는 제목을 갖고 있는)을 종료

WinWaitActive("메모장", "변경된 내용을 저장하시겠습니까?") - 제목이 "메모장"인 대화상자에 "변경된 내용을 저장하시겠습니까?"라는 문자열을 포함하고 있는 창이 활성화 되는 것을 확인

Send("!n") - 키보드 "ALT + n"을 입력

이 글은 스프링노트에서 작성되었습니다.

tag : AutoIt, Programming

AutoIt Tutorial - HelloWorld

휘님 — Wed, 10 Sep 2008 02:18:34 GMT

Tutorial - HelloWorld

Tutorial은 AutoIt 스크립트를 만들고 실행하는 기초를 설명한다. Tutorial은 이미 AutoIt V3가 Full Version으로 설치되어 있다가 가정한다.

스크립트를 만들 폴더에서 마우스 오른쪽 버튼을 클릭한 뒤, "새로만들기" -> "AutoIt v3 Script"를 선택한다.

만들어진 스크립트 파일의 이름을 "helloworld"로 수정한다.

스크립트 파일에서 오른쪽 버튼을 클릭하여 "Edit Script"를 선택한다.

다음 코드를 입력한다.

MsgBox(0, "Tutorial", "Hello World!")

MsgBox는 다음 파라미터(flag, title, message)들을 인자로 받는다.

스크립트를 저장하고 에디터를 닫는 후, 스크립트 파일을 더블클릭하여 실행시킨다.

MsgBox의 flag 파라미터를 살펴보면, flag의 값은 0부터 64의 값을 가질 수 있으며 각각의 flag 값은 메시지 박스의 종류를 나탄낸다.

MsgBox(64, "Tutorial", "Hello World!")

이 글은 스프링노트에서 작성되었습니다.

tag : AutoIt, Programming

Autoit Introduction

휘님 — Wed, 10 Sep 2008 02:16:27 GMT

v3.2.12.0

AutoIt v3 Homepage

Introduction

AutoIt v3 is a freeware BASIC-like scripting language designed for automating the Windows GUI and general scripting. It uses a combination of simulated keystrokes, mouse movement and window/control manipulation in order to automate tasks in a way not possible or reliable with other languages (e.g. VBScript and SendKeys). AutoIt is also very small, self-contained and will run on all versions of Windows out-of-the-box with no annoying "runtimes" required!

AutoIt was initially designed for PC "roll out" situations to reliably automate and configure thousands of PCs. Over time it has become a powerful language that supports complex expressions, user functions, loops and everything else that veteran scripters would expect.

Features:

Easy to learn BASIC-like syntax

Simulate keystrokes and mouse movements

Manipulate windows and processes

Interact with all standard windows controls

Scripts can be compiled into standalone executables

Create Graphical User Interfaces (GUIs)

COM support

Regular expressions

Directly call external DLL and Windows API functions

Scriptable RunAs functions

Detailed helpfile and large community-based support forums

Compatible with Windows 95 / 98 / ME / NT4 / 2000 / XP / 2003 / Vista / 2008

Unicode and x64 support

Digitally signed for peace of mind

Works with Windows Vista's User Account Control (UAC)

AutoIt has been designed to be as small as possible and stand-alone with no external .dll files or registry entries required making it safe to use on Servers. Scripts can be compiled into stand-alone executables with Aut2Exe.

Also supplied is a combined COM and DLL version of AutoIt called AutoItX that allows you to add the unique features of AutoIt to your own favourite scripting or programming languages!

Best of all, AutoIt continues to be FREE - but if you want to support the time, money and effort spent on the project and web hosting then you may donate at the AutoIt homepage.

Features in Detail

Basic-like Syntax and Rich Function Set

AutoIt has a BASIC-like syntax which means that most people who have ever written a script or used a high-level language should be able to pick it up easily.

Although it started life as a simple automation tool, AutoIt now has functions and features that allow it to be used as a general purpose scripting language (with awesome automation as well of course!). Language features include:

The usual high-level elements for functions, loops and expression parsing

A staggering amount of string handling functions and a Perl compatible regular expression engine (using the PCRE library).

COM support

Call Win32 and third-party DLL APIs

Built-in Editor with Syntax Highlighting

AutoIt comes with a customised "lite" version of SciTe that makes editing scripts easy. Users can also download a complete version of SciTe that includes additional tools to make things even easier.

Standalone and Small

AutoIt is a very small and standalone application with no reliance on massive runtimes like .NET or VB. All you need to run AutoIt scripts are the main AutoIt executable (AutoIt3.exe) and the script. Scripts can also be encoded into standalone executables with the built-in script compiler Aut2Exe.

International and 64-bit Support

AutoIt is fully Unicode aware and also includes x64 versions of all the main components! How many other free scripting languages can you say that about?

Key and Mouse Simulation

Much time has been spent optimizing the keystroke and mouse simulation functions to be as accurate as possible on all versions of Windows. All the mouse and keyboard routines are highly configurable both in terms of simulation "speed" and functionality.

Window Management

You can expect to move, hide, show, resize, activate, close and pretty much do what you want with windows. Windows can be referenced by title, text on the window, size, position, class and even internal Win32 API handles.

Controls

Directly get information on and interact with edit boxes, check boxes, list boxes, combos, buttons, status bars without the risk of keystrokes getting lost. Even work with controls in windows that aren't active!

Graphical User Interfaces (GUIs)

AutoIt v3 will also allow you to create some complex GUIs - just like those below!

And much, much more...

이 글은 스프링노트에서 작성되었습니다.

tag : AutoIt, Programming

Cross-Site Requestd Forgeries(CSRF) - Peter W

휘님 — Mon, 08 Sep 2008 06:10:54 GMT

From: Peter W <peterw@usa.net>

To: John Percival <john@jelsoft.com>

Cc: bugtraq@securityfocus.com, clambert@whitecrown.net, peterw@tux.org

Subject: Cross-Site Request Forgeries (Re: The Dangers of Allowing Users to Post Images)

Message-ID: <20010615011542.C22677@usa.net>

References: <04f901c0f437$4911b610$9701a8c0@wellingtoncollege.berks.sch.uk>

In-Reply-To: <04f901c0f437$4911b610$9701a8c0@wellingtoncollege.berks.sch.uk>; from john@jelsoft.com on Wed, Jun 13, 2001 at 07:33:04PM +0100

Cross-Site Request Forgeries(CSRF, pronounced "sea surf")

I hope you don't mind if I expand on this a bit. You've come across the tip, in my opinion, of a rather large iceberg. It's another Web/trust-relationship problem. Many Web applications are fairly good at identifying users and understanding requests, but terrible at verifying origins and intent.(Web 응용프로그램은 Request를 보내오는 근원지와 의도 파악이 어렵다.)

The problem isn't the IMG tag on the message board, it's the backend app you seek to attack via the IMG tag. And I suspect lots of Web apps are vulnerable. Lots. I've been to training on highly-regarded, widely-used, expensive Web app development frameworks, and none of the classes taught how to avoid the problems I will attempt to describe. In fact, they all seem to teach the "easy way" of handling what look like user requests, which is, of course, the vulnerable way.

Anyway, let's look at how your post relates to what I call CSRF.

On Wed, Jun 13, 2001 at 07:33:04PM +0100, John Percival wrote:

> This exploit shows how almost any script that uses cookie session/login data

> to validate CGI forms can be exploited if the users can post images.

> What is the problem? Well, by using an [img] (or HTML or or

>