Cross on my Macbook: unstable

[community@MixVibes]

Ok, let us know if the new battery will help you out!

[Blackbrook]

Unfortunately it does not. I will sell it as soon as I logout. Sad but true.

No one can ever tell me again that Mac rules the world of djing. They have exactly the same issues thatn windows machines have. My decision is clear: windows all the way!

Cheers,

Steve

[Support@MixVibes]

Sorry wasn't there...
Try to de-activate all wireless (bluetooth, wifi) and look into your application/utility/console, what the post boot log looks like.
Are you in 32 or 64bits mode ?

[Blackbrook]

Sorry wasn't there...

Don't worry!

Try to de-activate all wireless (bluetooth, wifi)

Done that without a result :-(

and look into your application/utility/console, what the post boot log looks like.

Did not do that. What is it good for?

Are you in 32 or 64bits mode ?

64 Bits

[Support@MixVibes]

and look into your application/utility/console, what the post boot log looks like.

Did not do that. What is it good for?

See how it is running (no errors ?)

Are you in 32 or 64bits mode ?

64 Bits

Try into 32bits mode to see, even if my iMac is running 64bits.

[Blackbrook]

and look into your application/utility/console, what the post boot log looks like.

Did not do that. What is it good for?

See how it is running (no errors ?)

There is just something in about the login manager (no error) and something about the printing server (cups). Nothing is specified as error.

Are you in 32 or 64bits mode ?

64 Bits

Try into 32bits mode to see, even if my iMac is running 64bits.

I was wrong! I did not check it and trusted the informations on the page. "uname -a" returns i386, there is definitely a 32 Bit CPU implemented.

Any further hints? Thanks!

Cheers,

Steve

[Support@MixVibes]

No I don't see why it wouldn't work, everything seems ok on the OS side, may be a hardware failure then, but I don't know how you could check.

[Blackbrook]

No I don't see why it wouldn't work, everything seems ok on the OS side, may be a hardware failure then, but I don't know how you could check.

Exactly that is the point. From the software side I do not see any chance to tweak or something that stops Cross from running flawlessly. Maybe it is hardware related but what could it be? The harddisk analysis says that it is working without erros, the RAM works fine and the CPU too, except the CPU is at this high level when Cross is working.

Cheers,

Steve