Index
> Windows > Difference FASMW and FRESH IDE |
| Author |
|
|
shutdownall 11 Jul 2014, 15:16
Well, read carefully the documentation of GetFileSize.
http://msdn.microsoft.com/en-us/library/windows/desktop/aa364955%28v=vs.85%29.aspx Code: lpFileSizeHigh [out, optional] A pointer to the variable where the high-order doubleword of the file size is returned. This parameter can be NULL if the application does not require the high-order doubleword. Only the upper (!) dword of a (possible) qword will be stored in that variable. This means only in case the file size is bigger than eax or a dword (32 bit) - so only for files bigger 4 gigabyte you will have a (partly) result. |
|||
11 Jul 2014, 15:16 |
|
|
clamicun 12 Jul 2014, 13:45
Yes thank you, but I know that.
The fact is -like I wrote - that the same code compiled with FASM (using the same file - of course) gives me 1 in eax and the correct size in dateigroesse ! Compiled with FRESH eax gives the correct size and dateigroesse is 0 ! Strange ??? Check it out. |
|||
|
12 Jul 2014, 13:45 |
|
|
shutdownall 12 Jul 2014, 22:51
clamicun wrote: Compiled with FRESH eax gives the correct size and dateigroesse is 0 ! The same source at the same OS/machine ? And the same file ? It is recommended to use GetFileSizeEx instead of GetFileSize. And it is also recommended to use CreateFile with GENERIC_READ instead of the "obselete" OpenFile function. There are reasons why MS recommends to use newer functions. Code: OpenFile function Creates, opens, reopens, or deletes a file. Note This function has limited capabilities and is not recommended. For new application development, use the CreateFile function. |
|||
|
12 Jul 2014, 22:51 |
|
|
JohnFound 13 Jul 2014, 20:18
The IDE is not important Fresh IDE uses the same FASM compiler as FASMW. But the macro library you use in both cases is important. So, what macro library you use?
|
|||
|
13 Jul 2014, 20:18 |
|
< Last Thread | Next Thread > |
Forum Rules:
|