I uploaded the first new release in the 1.63 development series - see the bottom of the Download section. The new feature that makes the 1.64 (which was planed to be the final release with full AMD64 support) very near is the ability of outputting the PE programs for Win64 directly. The Windows package contains the PE64DEMO example Win64 program. Thanks to Feryno for doing a testing for me.

nice, we should make some FASM'64 party when it's out.

It is by accident that version .64 will be with full 64-bit support?

It was planned since a long time ago. I have set up the roadmap of adding AMD64-related features so that such final release would have number 1.64.

I'm leaving the city for a few days (or even more) now, in the meantime I encourage anyone having access to 64-bit machine, especially running AMD64 version of Windows, to test the new fasm.

Note that I have renamed few of the macro packages to names like IMPORT32.INC and PROC32.INC - because for Win64 these macros will have to be changed. With imports it's only matter of chaning "dd" to "dq" in the address table, with procedures it will be a lot of work probably (because Win64 uses FASTCALL convention - though, in my personal opinion, it's actually not really worth to write any "invoke" macro for FASTCALL, since this convention is so specific that it can be best optimized only by hand-made assembly). The export and resource formats are, AFAIK, the same in Win64 executables as in Win32 ones.

BTW, why whatsnew file in latest releases only contains notes about latest changes?

The whatsnew for development versions contains just the log of currently made changes during the development.
As for the whatsnew in "stable" release I have recently restarted it in a more versatile manner (taken from the development notes) and so after restarting it contains only one version notes now.

I can get the PE64DEMO.asm to compile, but it won't run.

Do you have more information? Error messages etc.

Of cource you have a 64 bit processor and are running WIN64 otherwise you will get the same error as me "PE64DEMO.EXE is not a valid Win32 application".

I stand corrected. I have the hardware, but apparantly the software is Win32. Damned salespeople, you can't trust 'em.

I'm not going to test 64bit user code anytime soon, because for me it seems completely useless.

If you have purchased a 64 computer, with Windows XP Professional (32), go to:

http://www.microsoft.com/windowsxp/64bit/upgrade/default.mspx

Before the end of July to get a "free" upgrade to 64.

Mine is "in the mail" hopefully

farrier

Sounds like a good deal, but I'm going to pass. I don't want to reformat my hard drive, lose my hardware warranty, lose my WinXP 32 licence, and run all my existing software on an emulator with hit/miss chances of working properly.

I'd install 64 bit linux before going through all that!

Kain, you can have multiple NT versions installed on your computer - including both 32 and 64 bit versions of XP. No sweat, no formatting required

From the microsoft upgrade site you link above, before applying for x64:

" In addition, you must read and agree to the following:

* By participating in this program, your 32-bit version of Windows XP Professional will no longer be licensed.
* The installation of Windows XP Professional x64 Edition requires you to format your hard drive. You must back up your files and settings prior to the installation or they will be erased. Microsoft is not liable for any loss of data as a result of this installation.
"

Perhaps I can get away by resizing my partitions and dual booting (if possible), but in either case, I'll lose my WinXP 32 licence so I won't be able to 'legally' boot up Win32.

Also both actions (installing Win64 on new partition or full HD wipe will void my manufacturer's warranty ( I still have about 8 months on that).

That sounds like you didn't get a good deal. I would have thought the hardware maker could not decide what OS you want to use!

Where is the sense in selling a 64 bit processor and then saying you cannot use 64 bit software?

Buy from somewhere else next time.

...OR you could tell THEM (the ones who sold you the PC) to upgrade to 64 without losing your data. That is their problem then. You can try to squeeze it into warranty I think (if they are not very bad people :S).

Today's 1.63.2 release brings many bugfixes and two new directives: "while" and "break" (look here for more info). They are not documented yet, but I will work on the updated documentation for 1.63/1.64 soon.

BTW, 10 August 2000 is the date of the first release of fasm for Win32, I think it would be nice to release 1.64 on the fifth anniversary of it.

Do you mean Win64 or the version 1.00 of fasmw?

I meant the fasm 1.04, which was the first version that had the PE output format support, and first version which contained the fasm executable for Win32 console.

The 1.63.3 is the promised documentation update - mainly in the chapter 2.2. Some new code samples are added and the old ones were revised. There is also the new section 2.2.5, which I had the largest problems with - I was sure these things should be documented, though I have feeling this piece of manual might be a bit hard and unclear. Please let me know your opinion.

I also added one missing feature - you can now mark the argument in macro definition as required by placing the * character after its name. The arguments marked as required have to get a non empty value. For example:

will require at least two and at most three arguments to be provided.