ok ya OS/driver dev is beyond me at this point. so i could access my gpu this way? not that it is at my skill level to do any thing with it just wondering

i have a question that dose not pertain to this. i was using idiv and i devided -45 by 15 but the answer that came out was 286331150. what is causing this? any time i divide a negative number it acts like its unsigned.

Quote:

i have a question that dose not pertain to this. i was using idiv and i devided -45 by 15 but the answer that came out was 286331150. what is causing this? any time i divide a negative number it acts like its unsigned.

Try dividing 45 by -15. Just a guess.

that works but not the other way around whats the deal?

edit: about the other thing. how come some one hasn't figured out this information. i mean it's our computers right? maybe there is no use for this sort of thing. i guess gpu's are meant to be for graphics and aren't much good much else. who knows the infmation? hardware manufacturers like ATI and Nvidia or software developers like OpenGL and DirectX?

format PE console
entry main

include 'INCLUDE\MACRO\import32.inc'
include 'INCLUDE\MACRO\proc32.inc'

section '.data' data readable writeable

pausemsg db "pause>nul",0
saynum db "%i is the number",10,0
mynumber1 dd ?
mynumber2 dd -45
mynumber3 dd 15

section '.code' code readable executable

main:
        mov edx,0
        mov eax,[mynumber2]
        mov ebx,[mynumber3]
        div ebx
        mov [mynumber1],eax
        push eax
        push saynum
        call [printf]
        add esp,8
        push pausemsg
        call [system]
        add esp,4
        ret


section '.idata' import data readable
library msvcrt,'msvcrt.dll'

import msvcrt,\
printf,'printf',\
scanf,'scanf',\
system,'system',\
getchar,'getchar',\
realloc,'realloc',\
malloc,'malloc',\
free,'free',\
calloc,'calloc',\
exit,'exit'
    

        mov eax,[mynumber2]
        cdq                   ;sign extend eax -> edx:eax
        mov ebx,[mynumber3]
        idiv ebx