"no 8087" message on Athlon XP CPU

[Joep van Steen]

Hello,

No but the test would only be, does it run, does it plain start without the error message.
The guy who reported the problem, gets the message as soon as he starts the program.

If you could try this it would help a lot, and we'll be able to tell for sure
that PB3.5 compiled apps do work with Athlon XP CPU as well.

Still, my utilities support the undeletion of NTFS partitions as well

Kind regards,


------------------
Joep

http://www.diydatarecovery.nl

[Lance Edmonds]

It is good to know you run an Athlon XP as well, please note however
that since my software uses int13h ext low level disk access, the software
is run from DOS, not a DOS box. Is that possible, you try this after booting
a clean DOS bootdisk?

My drives are all using NTFS... sorry!

------------------
Lance
PowerBASIC Support
mailto:[email protected][email protected]</A>

[Joep van Steen]

Anyone with a Athlon XP CPU that could test something for me (in pure DOS)?

Would be much appreciated!



------------------
Joep

http://www.diydatarecovery.nl

[Joep van Steen]

Hello,

Thanks for the quick answer!

It is good to know you run an Athlon XP as well, please note however
that since my software uses int13h ext low level disk access, the software
is run from DOS, not a DOS box. Is that possible, you try this after booting
a clean DOS bootdisk?

I include FreeDOS with my programs, we have already tried other DOS versions as well.

I do not suspect the file to be corrupt, all utilites in my
"DIY DataRecovery Kit" behave in the same manner on the users PC.

I have sent him a recompiled version with $FLOAT PROCEDURE statement included.
I am waiting for a response now, I was just curious if anyone else had
seen this.

Thank you!



------------------
Joep

http://www.diydatarecovery.nl

[Lance Edmonds]

We've had no reports of any compiler-related problems along these lines, so something is most likely either wrong with the app (ie, it may be 'damaged' or corrupt) or the environment variable '87' is set to "N" (87=N) on that system. I'm running an Athlon XP system here (running Windows 2000) and PB/DOS apps compiled with $FLOAT NPX detect the CPU just fine.

Please ask the customer to open a DOS box and type "SET 87" (without the quotes). If the response is "87=N" then you've found the problem... (apps compiled with $FLOAT NPX will not run if the environment variable 87 is set to N)

OTOH, you could recompile the app with $FLOAT PROCEDURE and see if that helps the customers situation (say, if the 87=N setting has been set up that way for some other application).

------------------
Lance
PowerBASIC Support
mailto:[email protected][email protected]</A>

[Joep van Steen]

Hello,

Has anyone ever come accross this?
Or can you test something for me on an Athlon XP?

One of the users of my (data recovery) utilities receives this
message as soon as he runs the program.

First I suspected the issue to be related to UPX which I use to pack
my exe's with.

The string "no 8087" however does appear in uncompressed exe's.
"Floating point" under opetions is set to NPX. I think the error
may be prevented by switching it to emulation, but it strikes me as kind of weird that
the XP would not offer "87 support".

Joep




------------------
Joep

http://www.diydatarecovery.nl