In short, it wasn't the ebx to be placed in stdout, but from EAX, so empirically, we found that the variable was for withdrawal (and clearly for entry, and for the opening of the file) to move only from it.invoke GetStdHandle, STD_OUTPUT_HANDLE ;вывод числа на консоль mov stdout, eax invoke wsprintf, ADDR buf, ADDR ifmt, ebx ;форматирование числа для вывода invoke WriteConsoleA, stdout, ADDR buf, ;вывод числа BSIZE, ADDR cWritten, NULL invoke WriteConsoleA, stdout, ADDR crlf, 2, ADDR cWritten, NULL ; вывод новая строка (числа в столбик) The question remains: how can the PrimeNumbers draw out? it is created, but not used, and it can not be created with the same success. Each element in EAX is predetermined?

Read it. http://www.osronline.com/showThread.cfm?link=90397 It's all written about it, unless you're sure it's what you really need.

As first parameter https://msdn.microsoft.com/en-us/library/windows/desktop/dd145078%28v=vs.85%29.aspx accepts not the window identifier, but the identifier of the context of the device (in this case, the window identifier). The design of the device is simplified to compare with the drawing hottest.In your case, you need to get this identifier through a function. BeginPaint, draw a picsel, then release the context with help EndPaint♪Communication code WM_PAINT It' be like this:invoke BeginPaint, hwnd, addr ps invoke SetPixel, eax, 15, 20, 65285 invoke EndPaint, hwnd, addr ps It is also necessary to declare a variable pswhich is a structure https://msdn.microsoft.com/en-us/library/windows/desktop/dd162768%28v=vs.85%29.aspx ♪ It is likely that this structure is already defined in some of the MASM packages that are connected. addr - the key word for the variable address.For several challenges SetPixel For example:invoke BeginPaint, hwnd, addr ps push ebx mov ebx, eax invoke SetPixel, ebx, 15, 20, 65285 invoke SetPixel, ebx, 30, 20, 65285 invoke SetPixel, ebx, 45, 20, 65285 pop ebx invoke EndPaint, hwnd, addr ps This is an option without an additional variable. Under agreements stdcall and cdecl, the resulting procedures should not modify registers ebx♪ edi♪ esi (but may be modified eax♪ ecx♪ edxThat's why ebxe.g. may be used for temporary storage of values that should not be laundry with procedural challenges. But since procedure WndProc must also comply with the stdcall agreement, before modification ebx His meaning needs to be preserved and restored. It can be done either locally, around the location where the modification takes place. ebx (as shown in this example) either maintain at the beginning of the procedure and at the end (precede) ret- re-establish.Another comment is that the colour code is better to be written in pulp form, in this case. 00FF05hThen it's clear that this color is closer to green. 0x00bbggrraccording to the type description https://msdn.microsoft.com/en-us/library/windows/desktop/dd183449%28v=vs.85%29.aspx )

Well, here's the decision: .data? ps PAINTSTRUCT <> .code invoke BeginPaint, hwnd, addr ps invoke SetPixel, eax, 15, 20, 65285 invoke EndPaint, hwnd, addr ps

Judging by the text in the window, your original is retained in the UTF-8 code and is required by the fact of cp1251. Secure the source in the right code, then it's okay to get out.

COLOR_BACKGROUND-1 That's it. COLOR_SCROLLBAR♪ It's obviously not what you need. In addition, for some reason, when selecting such a systemic colour for the window when the size changes, the background does not change. The list of systemic flowers, look in https://msdn.microsoft.com/en-us/library/windows/desktop/ms633576%28v=vs.85%29.aspx or on the file. windows.inc from masm32 (all starting with COLOR_)To point out the specific color, you can create the "kisty" of the right color by a function. https://msdn.microsoft.com/en-us/library/windows/desktop/dd183518%28v=vs.85%29.aspx (Creatly, "create a whole bone." Her call will look like:invoke CreateSolidBrush, crColor where rcColor is https://msdn.microsoft.com/en-us/library/windows/desktop/dd183449%28v=vs.85%29.aspx Type 00BBGGRRh, BB is blue, GG is green, RR is red. The bright green colour will be codified as 0000FF00h, the more thick as 00007F00h. Other colours are mixed with three main colours, e.g. yellow is green + red (see). https://ru.wikipedia.org/wiki/RGB )For some flowers windows.inc There are their constants to set up in the function of brush or pencil:Black equ 000000h Blue equ 0FF0000h Green equ 00FF00h Cyan equ 0FFFF00h Red equ 0000FFh Magenta equ 0FF00FFh Yellow equ 00FFFFh White equ 0FFFFFFh Gray equ 080808h So, pre-enactment. windows.inc, you can create a green bone with such a challenge:invoke CreateSolidBrush, Green The value obtained (eax) must be recorded before the class is registered. wc.hbrBackground Where are you? COLOR_BACKGROUND-1)Something likes that: For reference: brush (brush) is used for bays, pencils (pen) for flooding various graphical objects. In this case, a whole (solid) bruise has been created, but it is possible to create whiplashes, for example.I understand COLOR_BACKGROUND-1 = white, COLOR_BACKGROUND = gray, COLOR_BACKGROUND+1 = black. We didn't. COLOR_BACKGROUND - it's the standard color of the window. COLOR_BACKGROUND+1 == COLOR_ACTIVECAPTION - the colour of the headline of the active window, COLOR_BACKGROUND-1 == COLOR_SCROLLBAR - Scollbar's color. These are systemic colors, they depend on the chosen Windows color scheme.

It doesn't show up because we have to record the window class, then call. CreateWindowEx, then start the cycle of the end messages.Read msdn, there should be examples.If you just have to show the window, it's easier to use. DialogBoxParam, then there's only one challenge to the function:start: invoke DialogBoxParam, 0, chr$("my_dialog"), 0, DialogFunc, 0 invoke ExitProcess, eax

Macrose szCALL Makes a pretty clever "hac," he defines the data area directly in the code segment and performs. call to the directive immediately following these data. Instruction call - it's practical. jmp at the designated address, push <адрес-след-инструкции> (i.e. she puts the return address in the glass). In the case of a szCALL The address of the next "instruction" is the address of the formed line, which is placed in the glass. If we want to put this address as an argument any function, it should be in the glass. To hand over the row address as RtlMoveMemory, we just need to put it in the right place, among other arguments:push 7 szCALL "string" push eax call RtlMoveMemory Although it's a WinAPI function to remembrance a short line of 7 byte, like, "high." You could write something like that.mov dword ptr [eax], "irts" ; Да, байты на intel платформе в обратном порядке mov word ptr [eax+4],"gn" mov byte ptr [eax+6],0

The mov team cannot move more than 4 Byte (on the 32-bit platform). I mean. mov mystring, "talff" It would be a mistake.mov doesn't support the way you're trying to copy. mov mystring, "talf",0 - it's actually three Operandas.mystring You have a double word (4 bytes), you want to put 5 byte.The right code will look like this..data mystring db 20 dup (?) ; выделяем место с запасом ... .code mov dword ptr mystring, "talf" mov byte ptr mystring+4, 0

The WideCharToMultiByte function serves this purpose. If you're still WinAPI, she'll be right there.

If the length of the line was not known in advance, then the only way to know its length is to find zero. It's convenient to use the instruction. http://www.kolasc.net.ru/cdo/programmes/assembler/scas.html ♪ This prefixed repne is scanning a buffer addressed to es:edi until it finds the bete specified in al (or looking for the first different from al bite when used with repe prefix). At the same time, the maximum size of the buffer is applied to the ecx, the instructions reduce it as the line is scanned and stops if they find what they were looking for or ecx to be 0.push es ; сохраняем es на всякий случай push ds pop es ; es=ds mov edi,адрес-строки mov ecx,300h ; Максимальная длина буфера xor eax,eax ; Будем искать 0, вообще достаточно al=0, но xor eax,eax быстрее cld ; Сканировать на увеличение адресов (df=0) repne scasb ; Сканируем строку, пока не найдем 0 ; es:edi - указывает на конец строки, ecx=остаток после конца строки mov eax,300h sub eax,ecx ; eax=длина строки, так же можно использовать edi-адрес_строки pop es P.S. to scan the lines retained in UTF-16, two zero Byte in a row, i.e. SCASW at AX=0.

.486 .model flat, stdcall option casemap :none __UNICODE__ equ 1 include C:\masm32\include\windows.inc include C:\masm32\include\masm32.inc include C:\masm32\include\gdi32.inc include C:\masm32\include\user32.inc include C:\masm32\include\kernel32.inc include C:\masm32\include\winextra.inc include C:\masm32\include\msvcrt.inc include C:\masm32\macros\macros.asm includelib C:\masm32\lib\masm32.lib includelib C:\masm32\lib\msvcrt.lib includelib C:\masm32\lib\gdi32.lib includelib C:\masm32\lib\user32.lib includelib C:\masm32\lib\kernel32.lib Main PROTO .data addrHeap dd 0 hMylp1 dd 0 .code start: invoke Main invoke ExitProcess,0 Main proc invoke GetProcessHeap mov addrHeap,eax invoke HeapAlloc,addrHeap,HEAP_ZERO_MEMORY,300h mov hMylp1,eax mov [hMylp1], input() mov eax, [hMylp1] invoke HeapFree,hmyHeap,NULL,hMylp1 Main endp end start

Same answer. https://ru.stackoverflow.com/a/504298/1365 - we need to get out. __UNICODE__ equ 1♪There are other problems in the code: for example, there is no instruction end at the end, which the programme will not be compiled, also at the end of the procedure Main No. retThat's why the program will be falling.

You can, for example, put a line in a dynamic memory and fill it with a seat. Then remove it. Or in the glass. That, however, would be a lot more code than it is now, so I wouldn't advise that I'd be bitter.

We can use the function. printf from msvcrt.dll.This is an example:.386 .model flat,stdcall include c:\masm32\include\msvcrt.inc include c:\masm32\include\kernel32.inc includelib c:\masm32\lib\msvcrt.lib includelib c:\masm32\lib\kernel32.lib .DATA fmt db "%d",10,0 .CODE main PROC mov eax, 76313 push eax push offset fmt call crt_printf sub esp, 8 ; нужно выровнять стек на размер параметров, т.к. у crt_printf соглашение вызова cdecl ; или просто ; invoke crt_printf, addr fmt, eax ; тогда sub esp, 8 писать не нужно макрос invoke сам его добавит invoke ExitProcess, 0 main ENDP END main In fact, instead "%d" when the function is decommissioned printf Makes a decimal representation of the parameter given to her. Other options: %u - a decimal whole, %x - Sixteenth performance, %c - a symbolic performance, %s row (the parameter should be the row address) and other.Details on the format of the printf conclusion can be read here (themes for C, but the format of the withdrawal remains the same): http://www.realcoding.net/article/view/1633 And the symbols that control (which begins with ) are better to miss, it won't work on the assembler.There's still a macro printf, which is an example of:.386 .model flat,stdcall include c:\masm32\include\masm32rt.inc .CODE main PROC printf ("%d\n", 76313); invoke ExitProcess, 0 main ENDP END main Both examples are based on examples https://stackoverflow.com/a/34210350/4752653 ♪If anyone ever needs an example of the use of the function. printf of msvcrt.dll for flat assembler:format PE console entry start include 'win32ax.inc' section '.code' code readable executable start: cinvoke printf, <"%d", 10, 0>, 76313 invoke ExitProcess, 0 section '.idata' import data readable library kernel32, 'kernel32.dll', msvcrt, 'msvcrt.dll' include 'api\kernel32.inc' import msvcrt, printf, 'printf'

Suffice it. __UNICODE__ equ 1and the conclusion will be:6121824303642485460667278849096102108114120126132138144150156162168174180 I guess we need to add a line translation after each number.Also, the program will fall because you're on trial. Main No return instructions ret♪ In addition, before ret Reinstatement of the register ebx from the glazingpop ebx)

Here's 23, 24 lines:mov cx,a mov ax,b The mistake is translated to "The instructions must be one size." The problem here is you're trying to put the contents of the bonus a and b. dda registers ax♪ cx (16-bit). It's either necessary to change the size of the variables or take 32-bit registers. As the programme is generally 32-bit, registers and variables are more effective in using 32-bits.Another mistake: mul ax multiplying. ax And you need to. cx multiplied ax♪ You need a team. mul cx♪

And no, and yes. The fact is, the result of the declaration dd is just a sequence of byte in the binary, which is statically stored. So changing the size is nothing. dd is not a dynamic memory team - it just statically puts the binary in the right sequence of the Byte.If you want to give your memory, go to the operating system and ask. Through a system challenge.

If you're lynching from BATreep, try to use it. https://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/percent.mspx?mfr=true : %~s1For example:rem link.bat masm32\bin\link.exe /SUBSYSTEM:CONSOLE %~s1 (if you call him like link.bat "D:\Новая папка\YandexDisk\asm.code.obj")If you're calling C#, try to translate the file's name into a short version on your own. This is done:[DllImport("kernel32.dll", CharSet = CharSet.Auto, SetLastError = true)] static extern uint GetShortPathName(string path, StringBuilder shortPathBuf, uint bufSize); public static string ToShortPathName(string longName) { // запрашиваем желаемый размер буфера uint bufferSize = GetShortPathName(longName, null, 0); while (true) { var shortNameBuffer = new StringBuilder((int)bufferSize); // проверяем, подошёл ли буфер (избегаем race condition с внешним миром) uint result = GetShortPathName(longName, shortNameBuffer, bufferSize); // ошибка -> исключение if (result == 0) throw new Win32Exception(Marshal.GetLastWin32Error()); // хватило места -- хорошо if (result <= bufferSize) return shortNameBuffer.ToString(); // нет -- идём на следующий круг bufferSize = result; } }

As usual, you've got a default window coding cp1251, and a consol in vinda is a cp866. So you have three ways. The first, the simplest, is to keep the file in the cp866. Yeah, we're gonna need a little correction at first, but it's gonna work. The second way is to codify clearly. And there is. http://sadda.ru/pages/assembler-masm32/chartooem/chartooem.htm ♪ And the third most beautiful way is to use utf/unicode everywhere. In the linux, it's usually "shorts."