Matt,
the ATI-Rage128 graphics card is *not supported* by
the Psychtoolbox-OSX, because the Rage128 lacks some
hardware features that are needed. This doesn't get
detected by the 1.0.5 PTB - instead you'll get random
misbehaviour. The 1.0.6 pre-release would have detected
and reported this issue to you...
Second, you are using a dual-display setup with 2 gfx-cards
from different vendors -- this rare system configuration
may have uncovered additional bugs in PTB and/or "Tiger".
All PTB demos direct their output to the secondary
display, if present (screen 1) -- i suppose that's your
Rage 128 gfx-card.
So try to display your stims on the display with the
Geforce-card or disable dual-display mode and see
if it helps.
good luck,
-mario
--- In
psychtoolbox@yahoogroups.com, "freebies191"
<matthew.l.davidson@g...> wrote:
> I copied your "simple OSX img demo" from the files section. I
loaded
> into matlab and ran it only to get the same error as all my
previous
> attempts to display images. Screen 1 went black and after a few
> seconds the following buss error was displayed:
>
> simple OSX img demo
>
> At the end of the demo,
> press any key to quit
> or wait for 5.0 secs.
>
> -------------------------------------------------------------------
-----
> Bus error detected at Tue Aug 2 16:25:29 2005
> -------------------------------------------------------------------
-----
>
> Configuration:
> MATLAB Version: 7.0.4.352 (R14) Service Pack 2
> MATLAB License: 166564
> Operating System: Darwin 8.0.0 Darwin Kernel Version 8.0.0: Sat
Mar
> 26 14:15:22 PST 2005; root:xnu-792.obj~1/RELEASE_PPC Power
Macintosh
> Window System: The XFree86 Project, Inc (40300000),
display :0.0
> Current Visual: 0x22 (class 4, depth 24)
> Virtual Machine: Java 1.4.2_07 with "Apple Computer, Inc." Java
> HotSpot(TM) Client VM
> (mixed mode)
> Default Charset: US-ASCII
>
> r0 = a0727674 r8 = a02850c4 r16 = f0ffddc0 r24 = 0ee74908
> r1 = f0ffc5f0 r9 = 0000001c r17 = ffffffff r25 = 000000ff
> r2 = a0727274 r10 = 0000205e r18 = 00000000 r26 = f0ffddc0
> r3 = 00000000 r11 = 0f1377ac r19 = 000a46cd r27 = 00000000
> r4 = 0ee74908 r12 = 90728fa0 r20 = 00000000 r28 = 0e50cbe0
> r5 = 000000ff r13 = 00000005 r21 = 00000001 r29 = 00000600
> r6 = 00000600 r14 = f0ffdd60 r22 = 00000000 r30 = f0ffc670
> r7 = 00000001 r15 = 00000000 r23 = 00000002 r31 = 90728fb0
> cr = 24024428 lr = 90728fb0 xer = 00000004 ctr = 90728fa0
> vrsave = 00000000
> Stack Trace:
> [0] CoreFoundation:0x90728ff4
> [1] Screen.mexmac:0x0f12254c
> [2] Screen.mexmac:0x0f122200
> [3] Screen.mexmac:0x0f122c18
> [4] Screen.mexmac:0x0f11df98
> [5] Screen.mexmac:0x0f10efdc
> [6] Screen.mexmac:0x0f1116c0
> [7] Screen.mexmac:0x0f10fcdc
> [8] Screen.mexmac:0x0f117f68
> [9] libmex.dylib:mexRunMexFile + 116 bytes
> [10] libmex.dylib:Mfh_mex::dispatch_file(int, mxArray_tag**, int,
> mxArray_tag**) + 316 bytes
> [11] libmwm_dispatcher.dylib:Mfh_file::dispatch_fh(int,
> mxArray_tag**, int, mxArray_tag**) + 344 bytes
> [12] libmwm_interpreter.dylib:inDispatchFromStack + 1616 bytes
> [13] libmwm_interpreter.dylib:inCallFcnFromReference + 320 bytes
> [14] libmwm_interpreter.dylib:inInterp(inDebugCheck, int, int,
> opcodes, inPcodeNest_tag volatile*) + 5608 bytes
> [15] libmwm_interpreter.dylib:inInterPcodeSJ(inDebugCheck, int,
int,
> opcodes, inPcodeNest_tag*) + 224 bytes
> [16] libmwm_interpreter.dylib:inExecuteMFunctionOrScript(Mfh_mp*,
> bool) + 772 bytes
> [17] libmwm_interpreter.dylib:inExecCompScript + 480 bytes
> [18] libmwm_dispatcher.dylib:Mfh_file::dispatch_fh(int,
> mxArray_tag**, int, mxArray_tag**) + 344 bytes
> [19] libmwm_interpreter.dylib:inDispatchFromStack + 1616 bytes
> [20] libmwm_interpreter.dylib:inDispatchCall(char const*, int,
int,
> int, int*, int*) + 196 bytes
> [21] libmwm_interpreter.dylib:inInterp(inDebugCheck, int, int,
> opcodes, inPcodeNest_tag volatile*) + 5280 bytes
> [22] libmwm_interpreter.dylib:inInterPcodeSJ(inDebugCheck, int,
int,
> opcodes, inPcodeNest_tag*) + 224 bytes
> [23] libmwm_interpreter.dylib:in_local_call_eval_function(int*,
> _pcodeheader*, int*, mxArray_tag**, inDebugCheck) + 176 bytes
> [24]
> libmwm_interpreter.dylib:inEvalStringWithIsVarFcn(_memory_context*,
> char const*, EvalType, int, mxArray_tag**, inDebugCheck,
> _pcodeheader*, int*, bool (*)(void*, char const*), void*) + 2872
bytes
> [25] libmwm_interpreter.dylib:inEvalString + 48 bytes
> [26] libmwm_interpreter.dylib:inEvalCmdWithLocalReturnandtype
(char
> const*, int*, inDebugCheck) + 96 bytes
> [27] libmwbridge.dylib:mnParser + 572 bytes
> [28] libmwmcr.dylib:mcrInstance::mnParser() + 104 bytes
> [29] MATLAB:mcrMain(int, char**) + 400 bytes
> [30] MATLAB:run_main(void*) + 24 bytes
> [31] libSystem.B.dylib:0x9002c3b4
>
> This error was detected while a MEX-file was running. If the MEX-
file
> is not an official MathWorks function, please examine its source
code
> for errors. Please consult the External Interfaces Guide for
information
> on debugging MEX-files.
>
> If it is an official MathWorks function, please
> follow these steps in reporting this problem to The MathWorks so
> that we have the best chance of correcting it:
>
> 1. Send this crash report to segv@m... for automated analysis.
> For your convenience, this information has been recorded in:
> /Users/robertpa/matlab_crash_dump.1101
>
> 2. Also, if the problem is reproducible, send the crash report to
> support@m... along with:
> - A specific list of steps that will reproduce the problem
> - Any M, MEX, MDL or other files required to reproduce the
problem
> - Any error messages displayed to the command window
> A technical support engineer will contact you with further
> information.
>
> Thank you for your assistance. Please save your workspace and
restart
> MATLAB before continuing your work.
>
> Error in ==> shortimgdemo at 19
> [w, screenRect]=Screen('OpenWindow', screenNumber, 0,[],32,2);
>
> >>
>
>
>
> so...
> I am running Matlab version 7.0.4, on a powermac G4 with OSX
version
> 10.4 and 512mb of sdram. It has dual 533mhz procs. the hd is 60gb
> with 18gb still free. I have two displays both running 1024x768
@75mhz
> and millions of colors. The two video cards are an ATI Rage128 and
> NVIDIA GeForce2 MX(factory installed) both with the most current
> drivers.
>
> If anyone has suggestions as to how to fix this I would really
> appreciate it. Its getting to the end of the summer and without
this
> image display working I can't get any data. Thanks for the help
>
> -Matt
>
>
>
>
>
> --- In psychtoolbox@yahoogroups.com, "franswcornelissen"
> <f.w.cornelissen@m...> wrote:
> > Matt,
> >
> > I've posted a simple demo in the files section
> > <------ that's somewhere there.
> >
> > gr.
> >
> > frans
> >
> >
> >
> > --- In psychtoolbox@yahoogroups.com, Matthew Davidson
> <matthew.l.davidson@g...>
> > wrote:
> > > I Have been trying to display images using psych
> toolbox and
> > > matlab version 7.0.4 in macOS 10.3 and 10.4 with absolutely no
> success.
> > > Every demo and example I have tried has caused a bus error or
has done
> > > nothingHaving narrowed down the possible causes of the problem,
> it's either
> > > the screen function or I need to start on some
reinstallations. .
> I am
> > > wondering if someone would be good enough to post me a sample
> program that
> > > takes an image from a file and displays it to the screen using
the
> Screen()
> > > command. No frills or anything. If this doesn't work I am
going
> to have to
> > > ak my boss for a new copy of matlab. Thanks.
> > >
> > >
> > >
> > > -Matt