Jump to content

New improved dosbox86


lamer0
 Share

9 posts in this topic

Recommended Posts

oh a general note to all the OSX porters, if a program has inline asm code and its using the 8 general purpose registers (ax,bx,cx,dx,di,pi,bp,ugh one more... can't think) make sure to push then pop them or OSX will give you a memory error. So remember to push then pop all your registers in inline code!

 

-Vic

Link to comment
Share on other sites

hey lamer0, i know this isn't the perfectly topic to say it

but please take a look again on your adium

 

it causing serious problems here with maxxuss 0.5, 0.5b and 0.5c sse2 patchs.

for example:

 

when i start my pc.

if i DON'T open the intel adium, i can open every application installed here

 

but... when i open adium, when i come up on my system after turn on or some else, i can't open intel and ppc rosetta applications because any app can't starts up, and there is alot of other minnors or serious bugs like the impossibility to restart, turnoff or logout the system, finder crashs seriously, etc.

 

i've notice about that and now i can confirm.

 

maybe you can talk with maxxuss for see whats happens in your build when ppl using his 0.5 amazing patches.

 

the other bug i told you is about the sound, and you tell me something sex bytes :)

well that is.

Link to comment
Share on other sites

Sorry, I really can't support it. The maxxius patch edits multiple files which adium might use and if things don't match up stuff will break. I can't be responsible for maxxius's patch. He replaced bunch of sse3 calls with sse2 calls all over the place. Some calls might not be binary compatible so adium will cause weird issues if it tries to access certain parts of the patched libs. It has nothing to do with adium but with the patch it self. You should inquire maxxius about this issue.

 

-Vic

Link to comment
Share on other sites

Sorry, I really can't support it. The maxxius patch edits multiple files which adium might use and if things don't match up stuff will break. I can't be responsible for maxxius's patch. He replaced bunch of sse3 calls with sse2 calls all over the place. Some calls might not be binary compatible so adium will cause weird issues if it tries to access certain parts of the patched libs. It has nothing to do with adium but with the patch it self. You should inquire maxxius about this issue.

 

-Vic

 

okay np

i will try to contact him about this inssue

 

thank you :)

Link to comment
Share on other sites

 Share

×
×
  • Create New...