[Rpcemu] RPCEmu 0.9.4

In article
<CANc9Z=xbXjOyziiND38ooP9+Pipi+dZZJyWNaaR5q98rKXi5YA@mail.gmail.com>,
Peter Howkins <rpcemu.howkins@marutan.net> wrote:
> A new version of RPCEmu is available, 0.9.4
> http://www.marutan.net/rpcemu/

[Snip]

Excellent news as usual. Thanks folks :-)

Small problem and I wonder what it means...

RPCEmu 0.9.4 ROD 5.28

"Filing system HostFS: Must be given a name 640" presents during the boot
sequence, and after I click it away the boot sequence continues... but
some of the configs are missing.

To make sure, I have done the CLI
*configure filesystem hostfs
*configure boot

But that doesn't resolve it.

Any thoughts please?

Thanks

Dave

1) This does not happen with another new RPCEmu 0.9.4 and RISC OS 6.20
which boots and run without any problems.

2) I used to know a command that would show the boot list after the
emulator was run, but damned if I can remember it, anyone help with that
also?

Thanks Dave

--

Dave Triffid

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

[Rpcemu] RPCEmu with RISC OS 4.00 auUUP00-00 and Ursula0020 issues

Hi all,

I have been trying out the the Pace Internal RISC OS 4 roms with RPCEmu 0.9.3 and 0.9.4 and I have a couple of questions/comments:

1. Both Ursula0020 and auUUP00-00 only seem to work with the Interpreter version of RPCEmu, when trying the Dynamic Recompiler version on 0.9.3 it immediately crashes with the error "Bad PC 030b8000 030b8000". With 0.9.4, both roms cause RPCemu to displace a black window. I freshly compiled both versions of RPCEmu on KDE Neon 5.23 (Linux). Is this a known problem?

2. Does anyone know if any of the "stock" !Boot sequences available online will work with both of these versions?

Any help would be appreciated :)

Cheers,

Dan

[Rpcemu] RPCEmu 0.9.4

A new version of RPCEmu is available, 0.9.4    http://www.marutan.net/rpcemu/      ARM  	Performance gains on x86 and x64 dynamic recompiler.    	Many of the instructions that were not accelerated on the x64          architecture but were on x86 have now been implemented on x64.    	Refactoring of Dynamic Recompiler code.  	  	Many bugfixes.    	Accessing CP15 should only be permitted in privileged modes.    Network Address Translation  	You can now configure ports to be forwarded between your host          network and RPCEmu. This allows you to host servers under RPCEmu          that can be accessed by other machines on your network.  	(Note, this still does not enable the use of ShareFS)    Floppy Disc          Support HFE format floppy disc images. HFE disc images are          lower-level than ADF discs as they can also store the information          required for various copy protection systems. Contributed by          Sarah Walker.    VIDC          If you are not using VRAM you can now use up to 4MB of RAM for          video modes.    Other  	Fix the crash on shutdown or reset of RISC OS 5. Based on a          suggestion from Rob Sprowson.    GCC          Compiling with GCC 10 no longer needs a workaround for the common          symbols errors.        Matthew Howkins  Peter Howkins

[Rpcemu] RPCEmu at the RISC OS London Show, 30-10-2021

At the RISC OS Show, next weekend, in Feltham London, RPCEmu will be having

a stand.

It will be a great chance to catch up with people after a couple of years
and see all the latest projects.

On the RPCEmu stand we will be showing the latest features and also have
demonstrations of two work-in-progress advanced items that are due for
release in the future. [1]

Hope to see you there

Peter

[1] Don't worry too much if you can't make it, I'll post a summary here

afterwards :-)

[Rpcemu] Mercurial down?

Hi,

I tried (as I do regularly, i.e. once in 6 months...) to visit RPCEmu's
Mercurial repo, but the link failed:
http://www.home.marutan.net/hg/rpcemu
leads to a classic 404.

CLI hg also fails with 404.

Steffen aka hubersn

--
Steffen Huber LambdaComm System – Welcome to Trollinger Country
steffen@huber-net.de
Private homepage http://www.huber-net.de/
RISC OS Blog http://riscosblog.huber-net.de/

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

Re: [gccsdk] VFP vs FPA in library builds

In article <0FCB5232-FB88-479B-B2F4-4F722A086C78@bigblue.net.au>,
Alan Williams <ajw@bigblue.net.au> wrote:
> Rhett,
> I have found my work on that and I would be very happy if it saves you some time.
> There is a file where I was keeping track of what I had done and what I wanted to get done.
> I just zipped up the whole dir and bunged it here:
> http://riscix.info/nettle12.tgz
> There is a conflict in that you can't us this and the default build interchangeable as mine extends the book marks file format to hold the key name and the original version doesn't like this. I think I only extended the English template file correctly. That is any other languages will have English names for the extra fields.
> I believe it was building and running on RISC OS 4.39 when I looked at it last about 2015, but I know it spat it when I tried it on a pi. Normally I just telnet a linux box and ssh from there so I just worked around the issue and never got back to it.

> I also did some other work to make it more putty/iTerm2 like in that selected text is put on the clip board and adjust I think pastes.

After building your version using the GCCSDK autobuilder logging in using a
key worked OK on a RPi 4.


_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK

Re: [gccsdk] VFP vs FPA in library builds

In article <alpine.DEB.2.22.394.2110151354320.3902245@thelappy>,
Rhett Aultman <rhett@rhettaultman.com> wrote:


> On Fri, 15 Oct 2021, David Pitt wrote:

> > Nettle has just built here on the autobuilder but libsssh2 had to be built
> > first.

> Ah! I wasn't aware that it build through the autobuilder. I've noticed
> that the autobuilder tends to download checkpointed sources and clean up
> after itself following building, so I'm curious if there are ways to use
> it as an environment more friendly to active development and iteration?

> Apologies if these are basic questions to ask; I really did try to educate
> myself through the wiki first.

Adding the '-D' option to the build command will leave the folder in place
after building, Any dependencies should also get built automatically.


../autobuilder/build -v nettle -D

Assuming there's a build-setvars file with similar to below in the folder
the build command is run from.

GCCSDK_INSTALL_CROSSBIN=<path to autobuilder>/cross/bin
GCCSDK_INSTALL_ENV=<path to autobuilder>/env
RO_SHAREDLIBS=no
AB_ELFBUILD=yes


Then build with,

<path to autobuilder>/env/ro-make -f GNUmakefile


_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK