I used the API GetFileSize wich return the file size in two 32bit registers, one is the high half of 64bit size number and the other is the low half.

I used a memory location of QWORD (WICH THE MASM RECONGNIZE) but i coulent find a way to put the number in this Memory location. i tryed to use the command movq, but the compiler yeld that the processor type is not comptible with this command although the processor type was 586 and 686.

help will be apritioated.
Posted on 2003-12-24 12:36:49 by XcalibEr
The low order DWORD is lowest in memory and then the high order DWORD:
.data

BIGINT QWORD ?

.code
mov DWORD PTR [BIGINT][0], eax ; least significant DWORD
mov DWORD PTR [BIGINT][4], edx ; most significant DWORD
.MMX for use of MOVQ.
Posted on 2003-12-24 13:06:23 by bitRAKE
Thnx
But i looked for Processor command to use it, so i understand i need to add the .mmx for it right?
Posted on 2003-12-24 13:24:45 by XcalibEr
Yes, use .MXX if you want to use MOVQ.
Posted on 2003-12-24 14:40:02 by bitRAKE
I used the API GetFileSize wich return the file size in two 32bit registers, one is the high half of 64bit size number and the other is the low half.


GetFileSize dosen't return a 64 bit number it only returns the low DWORD


DWORD GetFileSize(
HANDLE hFile, // handle of file to get size of
LPDWORD lpFileSizeHigh
// pointer to high-order word for file size
);
Posted on 2003-12-24 14:45:03 by ENF



GetFileSize dosen't return a 64 bit number it only returns the low DWORD


DWORD GetFileSize(
HANDLE hFile, // handle of file to get size of
LPDWORD lpFileSizeHigh
// pointer to high-order word for file size
);


Well u wrong.

The LOW DWORD return at eax, while the High DWORD return at the memory refrenced by lpFileSizeHigh
Posted on 2003-12-24 16:26:54 by XcalibEr

Well u wrong.

The LOW DWORD return at eax, while the High DWORD return at the memory refrenced by lpFileSizeHigh

that is what I was saying. From your orgiginal post I though that you were saying that GetFileSize returns a 64 bit value in edx:eax
Posted on 2003-12-25 07:00:15 by ENF

Yes, use .MXX if you want to use MOVQ.


what's that?
Posted on 2003-12-25 10:50:10 by comrade



what's that?


.MMX parsing macro to include MMX technology syntax in masm.
Posted on 2003-12-25 10:52:24 by wizzra
Comrade is just mocking bitrake. :grin:
Posted on 2003-12-25 10:53:41 by roticv
The only threat has been available for some time. PAE (page address extentions). As memory actually becomes 4 gig there is no where else to go, None the less I know that presently Microsoft is currently developing software for the new Intel's "Centrino" chip. It has rf capacity built in. Go to any "Starky's" coffee shop or most motels and hotels. RF internet links are available and Microsoft and Intel are busy with this new wave of product line. It wouldn't hurt us to get hip either,
Posted on 2003-12-26 04:36:27 by mrgone

Comrade is just mocking bitrake. :grin:


I was not mocking, I was :confused:. There is .mmx, .xmm, and now .mxx?!
Posted on 2003-12-26 12:19:07 by comrade
I suppose that is the new technology developed by Bitrake. :grin:
Posted on 2003-12-26 22:29:53 by roticv

Comrade is just mocking bitrake. :grin:
Comrade just doesn't know how slow my mind gets when my fingers get fast. :grin:
Posted on 2003-12-29 22:32:05 by bitRAKE