Re: ZoomFloppy with OpenCBM / VICE

From: silverdr_at_wfmh.org.pl
Date: Thu, 6 Dec 2012 00:02:48 +0100
Message-Id: <33B6D192-5D8B-4715-956A-C4F581861DCF@wfmh.org.pl>
On 2012-12-05, at 12:55, Uffe Jakobsen wrote:

>> I am yet to get ZoomFloppy work with my VICE.. I mean "my", not because I modified it but because I compile it myself for OSX. I have opencbm installed and working (tools like cbmctrl and d64copy work all fine) I configure with --enable-realdevice, I receive
>> 
>> checking for OpenCBM support... yes
>> 
>> I get no linker errors with opencbmlib.o
>> 
>> and still, in the end I get only:
>> 
>> "Real Device: Real device emulation is not available"
>> 
>> in the logs.
>> 
>> Any clues?
> 
> I haven't got my Mac at hand now so this is free from memory - so please forgive me if I've forgot something.
> 
> 
> I assume that you are compiling VICE from trunk (currently 2.4.x) ?

2.4 stable

> Please try to start VICE (x64 or x64sc) with "-verbose" option
> 
> The log should tell you wether libopencbm.so (alternatively libopencbm.dylib for MacOSX ) is found or not...

Thanks! That was a very good hint..

> VICE@MacOSX defaults to look for libopencbm in this location "/opt/opencbm/lib/libopencbm.dylib"

Now that's strange.. a hardcoded path to a nonstandard location?! I mean stuff installed with DarwinPorts goes to /opt/local/lib.. others are in /usr/lib or usr/local/lib and why to hardcode the path in the first place.. ?

I found the file, changed the hardcoded path to the expected "/opt/local/lib/libopencbm.dylib" and got it properly (I guess) opened:

"Real Device: 002-16d0-0504-ff-00 opened."

but then, when I try to use it, x64 hangs and in the logs it says:

Sound: Warning - Buffer drained
Warning - Your machine is too slow for current settings!
Received signal 11 (SIGSEGV), exiting.

Exiting...

even it it actually doesn't exit. It only hangs and has to be KILLed manually. Have you actually managed to get it working properly? If not, then I probably will have to ask on some VICE mailing lists.

-- 
SD!
       Message was sent through the cbm-hackers mailing list
Received on 2012-12-06 00:00:12

Archive generated by hypermail 2.2.0.