
|
[openbeos]
||
[Date Prev]
[08-2004 Date Index]
[Date Next]
||
[Thread Prev]
[08-2004 Thread Index]
[Thread Next]
[openbeos] Re: app_server: MMX/SSE help wanted
- From: Kian Duffy <myob87@xxxxxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Sun, 8 Aug 2004 18:29:04 +0100
On Sun, 08 Aug 2004 19:22:10 +0000, Christian Packmann
<christian.packmann@xxxxxx> wrote:
> On 2004-08-08 17:00:18 [+0000], Kian Duffy wrote:
>
> >> The XP certainly doesn't fake any kind of Intel CPU; the CPU
> >> identification in BeOS is broken, badly. It's no small feat to identify
> >> a CPU as Intel which returns a vendor ID of "AuthenticAMD". :)
> >
> > Well, if it was a true clone of Intel's SSE, it wouldn't crash BeOS. It
> > is a bad clone of it, hence the crash
>
> Okay, then let me know the instruction sequence on which an XP crashes, but
> a PIII/PIV doesn't. I've already checked the Intel docs (admittedly, not
> page to page), and so far I haven't found anything which would indicate an
> incompatibility.
I'd suggest you find someone with an Athlon XP to ask, I no longer
posess any AMD kit due to the number of times my Duron went on fire
(at rated speed with above rated cooling).
> > And hence the problems with the MMX optomised version of the Windows
> > 95 game "POD" on AMD systems.
>
> What kind of problems, especially problems relating to the XP?
The problems I had were not on an XP (I no longer use AMD kit, see
above), but on a Spitfire Duron. Basically, the game GPF'ed on loading
due to a misintrpretation of a MMX instruction. As I no longer have an
AMD system (or a Windows system), I can't check exactly what it was.
You needed the specific MMX version that came with Dell Dimension
H-series systems for that behaviour to happen, older versions were not
MMX enabled and later MMX versions worked on AMD CPU's with MMX.
Kian
|

|