REMINDER - Stay logged in for at least 2 hours a week to get whitelisted.
Also it helps build a picture where our "good traffic" is coming from for detection scripts.
:o)
pixelpusher wrote: 07 Jun 2021 18:38
Renaming helps to start it, it still doesn't recognize an FPU nor an LineF emulation and just reports that no FPU was found when trying to start the FPU test.
This one will output COOKIE.TXT to see whats going on..
GB6B33.zip
EDIT:
I think I might see the problem now.. ill upload another PRG to try also shortly... (maybe this one will work now, but not 100% sure)
EDIT2:
GB6B33A.zip
You do not have the required permissions to view the files attached to this post.
pixelpusher wrote: 07 Jun 2021 18:38
Renaming helps to start it, it still doesn't recognize an FPU nor an LineF emulation and just reports that no FPU was found when trying to start the FPU test.
This one will output COOKIE.TXT to see whats going on..
GB6B33.zip
EDIT:
I think I might see the problem now.. ill upload another PRG to try also shortly... (maybe this one will work now, but not 100% sure)
EDIT2:
GB6B33A.zip
Unfortunately not. Still claims "FPU not present" in the "System" display and when starting the float math test it claims "FPU not found" and returns.
pixelpusher wrote: 08 Jun 2021 07:43
Unfortunately not. Still claims "FPU not present" in the "System" display and when starting the float math test it claims "FPU not found" and returns.
pixelpusher wrote: 08 Jun 2021 07:43
Unfortunately not. Still claims "FPU not present" in the "System" display and when starting the float math test it claims "FPU not found" and returns.
pixelpusher wrote: 08 Jun 2021 17:40
These should be 16 bit values (at least the low and high word of the cookie are just this), but in your display it exceeds 16 bit...
Not sure what you're referring to by display ? I don't display the cookie data anywhere on screen.
pixelpusher wrote: 08 Jun 2021 17:40
These should be 16 bit values (at least the low and high word of the cookie are just this), but in your display it exceeds 16 bit...
Not sure what you're referring to by display ? I don't display the cookie data anywhere on screen.
See correction in my previous post - and you're displaying (or logging) 0x00010001 in the cookie.txt (just as decimal)
pixelpusher wrote: 08 Jun 2021 17:50
See correction in my previous post - and you're displaying (or logging) 0x00010001 in the cookie.txt (just as decimal)
Yep. just easier to debug as is without me hunting for the syntax to convert to something else.
Am working on this currently to try and find the issue..