Big Endian/Little Endian problem perhaps?

What kind of processor is on the other end
of this comm link?

Is the comm link doing a full eight bits - does
it perhaps recognize any particular control
characters that the data could represent?

What format does the characteristic and the mantissa
(of the FP number) take?

RF (and software) Jim

    "Our ability to manufacture fraud has exceeded
     our  ability to detect it."

     - Al Pacino as Viktor Taransky in the movie 'Simone'



----- Original Message -----
From: "Claudio Tagliola" <tagliola@SOFTHOME.NET>
To: <PICLIST@MITVMA.MIT.EDU>
Sent: Saturday, August 24, 2002 1:32 PM
Subject: [OT] Floating point formats


> Hello all,
>
>
> I have a problem which doesn't belong here but I'm still turning to the
> piclist 'cause I know I can find a lot of skilled ppl here, who maybe can
> solve my problem.
>
> I'm working on an 186 AMD based micro. This this is programmed in Borland
> C++ 5. The problem I have is with floating points. As this this doesn't
have
> a fp processor onboard, I'm using Borlands fp emulation library (emu.lib).
> What I am trying to do is send a 32 bit float value over a certain
> connection, byte for byte. However, If I put them all together again on
the
> other side and hope to get the same float back, I am mistaken. Therefore,
I
> came to the conclusion the emu.lib uses a non standard (i.e. IEEE754), fp
> format. And I am at a loss which one that should be. Extensive googling
only
> gave me a bunch of unreadable pages and highly arcane info.
>
> Any ideas for this one?
>
>
> Best regards,
>
> Claudio Tagliola
>
> --
> http://www.piclist.com hint: To leave the PICList
> mailto:piclist-unsubscribe-request@mitvma.mit.edu
>

--
http://www.piclist.com hint: To leave the PICList
mailto:piclist-unsubscribe-request@mitvma.mit.edu