Direct2d button

[zedd151]

Okay, I'll look at it in Windows 10 later on sometime. Lemme make a partition for it and...


Okay, I got windows 10 installing already now. (I got impatient) I'll put a copy of masm32 sdk there then try again.

[zedd151]

Okay, I got windows 10 installing already now...

Okay! Success! It runs fine in Windows 10 64 bit OS. Looks nice.   
Edit to add. Assembles fine as well.


Must be some sort of compatibility issue?
Anyone else having problems with Windows 7?

[jj2007]

Your project has serious setup issues, so serious that it won't build with a normal Masm32 SDK setup, but the executable from your archive runs fine on Windows 7-64.

Once upon a time, everybody in this forum used paths like ...

\Masm32\  and
\Masm32\include\

... and it worked on all members' machines, even if they had installed the Masm32 SDK on Z:\Masm32

Latest version, using makeit.bat

Code Select Expand

Microsoft (R) Incremental Linker Version 5.12.8078
Copyright (C) Microsoft Corp 1992-1998. All rights reserved.

LINK : fatal error LNK1117: syntax error in option "SUBSYSTEM:WINDOWS/DEBUG"

[BugCatcher]

I used the .686 directive so that the newer floating point comparison fcomip works. If I use the default sdk .486 I get errors also.

[zedd151]

I put .686 in the masm32rt.inc

I should have (or anyone else for that matter) mentioned yesterday, that modifying that include file is not a good idea. The more proper way is to change the source code to add the CPU there:

Code Select Expand


include \masm32\include\masm32rt.inc
.686
...

Otherwise everyone that uses your program will have to change their include file masm32rt.inc, if they need to re assemble it.