fasm already has a DOS build, just use that.

do you try to reloop the TSC?
if it's the case, then, remember you will be dead a long time before.

maybe one day, i'll buy a XP PRO SP2 CD, and , innnnnns
in
inst
install it.

I was going to..

I just need a compiler.. that works on vista 64.. possible Nasm and convert the code from the dos. version... I think they have a 64 bit version..but not sure...

The TSC is nearing the increment into the 57th bit. Currently 0x00ED6C5885275A1E

so now, you just have to wait ~ 350 years.

2^64/0ED6C5885275A1E*19.5/12 = ~448.5 years

my head is not a good calculator. bad approximation..

I was trying the dos version - I just downloaded the Fasm Win32 Version and it works!!!! Yeah!!!!

in the download it does have a 64 bit example!!!...

Well it will allow win32 apps.. not console..

but its a start...

Oh, no wonder. Yes, it is a limitation of the CPU, when in 64bit mode you cannot run v8086 tasks.

Your problem sounds more like you are trying to run the DOS version of FASM instead of the Windows version. Vista 64, like XP 64, has no native capacity to run DOS programs, so the DOS version of FASM wouldn't work in XP 64 either.

Oh, your response indicating that this was indeed the problem just popped up. I was going to say that if you needed a native 64-bit assembler, GoAsm, YASM, FASM, MASM, and NASM all operate in 32-bit mode but it may be possible to goad the NASM folks into compiling a native 64-bit version. So for now the only native 64-bit assembler available is GAS.

I am just use to the dos version...
and just copied it from the other computer... lol..




Ya.. an oversite on my part... and the funny thing I new that...
Just was in a hurry to get all my software on it...

But thanks for the help...

for console, you need to have dosbox in XP. don't know if it's the same for 64 and vistahhhh.

but, one detail. dos version is not the best. fasmw is. it's an editor in high res, no crappy text mode, and you just have to press F9 to run the code, as with fasmd but better.

But I can still compile it on Vista and run the console apps in dosbox or qemu...

Thats good enough for me !!!

I think you mean more precisely DOS apps? Because console apps can be either 32bit or 16bit.

you can run dos code with 32 bits instructions. but it will be full of 66, 67 prefixes.
is it fast enough? for example the xhtml.com executable, can it run fast in dosbox?

Ya- but you know what I meant... lol
but I gues its best to be specific...




I will give it a try in Dosbox...

Everyone - Thanks again...

Erm, what is means you're USED TO DOS version. Its just freakin' FASM.EXE. What difference does it make is it FASM.EXE (16-bit) or FASM.EXE (32-bit). Either way you will use them FASM.EXE blah.asm.

I suggest you just let some other people replace your 16-bit version so you wouldn't SEE it This way everybody's happy. You can use your "DOS" FASM under Vista64

If you are refering to the command line.. Fasmw16726 command line works..
and win interface on Vista 64 works...

The dos version Fasm16726 Does not work on it..

The Fasmw16726.. Does work..

That was the prob... I was having - as I said - Ijust copied the version from the old computer to the new one...

I downloaded the win32 version and
Everything is good....

and no they should keep the dos version - for people that still use dos..
and for os devel... It is easier to port to a new OS.. like DexOS,Menuette.. did...


Thats what I have been using... sure there is no difference...
but I do not like the interface for fasmw and thought you had to use it...
As I found out... I still can use the comand line...
So again all is good...

I wonder who "they" are? If you mean a 64bit OS to support 16bit DOS then the emulator would be just like QEMU or BOCHS etc. so you already have DOS support