Hi,

I’ve at last completed all my Mac machine upgrades to this version.  No 
problems at all (apart from finger trouble right here).  It works on machines 
as far back as 2010, but not on one from 2008 due to the stipulated MacOS level 
not being available for the 2008 machine.

I’ve even tried the 2.27 RISC OS as it was declared stable for the 2.28 
release.  Again all works well.

Many thanks indeed for piling out this update, it gives RISC OS a whole 
different dimension to know that RPCemu is not only being updated but also 
built for the latest Macs and does the internet.  I can now take RISC OS with 
me wherever I go!

And the NAT-based networking just works, no fuss, no bother, brilliant.

Tim

-- 
Tim Powys-Lybbe                                                           
t...@powys.org
                        for a miscellany of bygones: http://powys.org/

> On 8 May 2020, at 2:51 pm, Timothy Coltman <li...@maemagel.com> wrote:
> 
> Hello all
> 
> Following yesterday's release of 0.9.3, I have built a Mac binary, which is 
> now available for download from its new home:
> 
> https://github.com/Septercius/rpcemu-dev/releases
> 
> The 0.9.3a release includes all the patches from the previous version, and 
> fixes two issues:
> 
> * The missing "hostfs" folder is now included in the "Data" directory inside 
> the DMGs.
> * The key you can hold down at startup to bring up the dialogue that prompts 
> you to choose where the emulator data (ROMs, CMOS, hard drive images, etc) 
> resides has been changed from CTRL to SHIFT.  This is to make it easier to 
> trigger the dialogue as the application starts (the Mac interprets CTRL+click 
> as a right click).
> 
> As ever, bugs/comments/suggestions are welcome.
> 
> Tim
> 
> 
> _______________________________________________
> RPCEmu mailing list
> RPCEmu@riscos.info
> http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu


_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu

Reply via email to