Noob needs Pi3B help...

Hi everyone,
Yep I said it, I‘m an absolute noob when it comes to RiscOS, Pi‘s and Linux.
That didn‘t hinder me wheb I successfully installed a Minecraft server for my kids on a Pi3B.

I thought I’d try something else.
I own an Acorn model B+ and a Master 128 and always wanted an Archimedes, but can’t find a suitable one.
So I thought, why not install RiscOS on my Pi3B and install an Archimedes Emulator.
So I downloaded NOOBS Lite (the full version doesn’t want to install RiscOS), selected RiscOS and away the install went.
Took about 2 minutes then came the reboot and I was greeted by the RiscOS desktop.

The problem I’m having is that after anything between 10s and a minute or 2 RiscOS goes from very snappy responses to responding to a mouse click in minutes rather than microseconds.

I have no idea why, being a noob, have no idea where to start looking for a solution.
I have tried several fresh NOOBS re-installs, tried a different micro SD card, tried installing using PINN and even directly downloaded a suitable RiscOS image from this very website, all with the same result as described above.

Google is no help either.

Can anyone shed some light on my predicament?

Thnx.

So I thought, why not install RiscOS on my Pi3B and install an Archimedes Emulator.

You know, the Archimedes ran RISC OS as well (though a slightly different version for complicated technical reasons). If you stick with modern software (anything that claims to be “26/32 neutral” or “32 bit compatible”, it’ll run directly on your machine without the need for an emulator.

The problem I’m having is that after anything between 10s and a minute or 2 RiscOS goes from very snappy responses to responding to a mouse click in minutes rather than microseconds.

Are you running any programs at this point, or does it happen by itself?

What is connected to the machine? Generic keyboard? Optical mouse?

Can you tell us the dates/sizes of your firmware? I’m not sure how boobs is laid out, in a normal install there are some files (start.elf and fix-up.dat) in the root directory along with the config file and the image that is to be run.

What version of RISC OS is actually running? Press F12 after boot and type *FX 0 (that’s a zero).

I’m not sure how boobs is laid out

Thank you autocorrect.

Please allow me to guide you to page 243 in your biology textbook, the chapter entitled the human reproduction system complete with suggestive line drawings.

Thank you autocorrect.

In this house it’s known as auto-bollox for obvious reasons.

Are you running any programs at this point, or does it happen by itself?

Nope I’m doing nothing more than clicking ie. on the raspi icon in the lower right corner to look at system stats. Or even just waiting and doing nothing after it boots.
The strange thing is, although RiscOS reacts to a mouse click with a couple of minutes delay, the mouse moves as snappy as before.

What is connected to the machine? Generic keyboard? Optical mouse?

A Logitech M705 Wireless mouse, Generic USB keyboard and a network cable.
RiscOS has a working connection to the internet via DHCP.

Can you tell us the dates/sizes of your firmware? I’m not sure how boobs is laid out, in a normal install there are some files (start.elf and fix-up.dat) in the root directory along with the config file and the image that is to be run.

I downloaded Noops, NIPP and the latest version of RiscOS from this website yesterday, they are version 5.24.

responding to a mouse click in minutes rather than microseconds.

You may have run into this USB bug. I can’t be sure as a NOOBS build works normally on my Pi 3B.

First thing to try: Plug the keyboard and mouse into an external USB hub (it doesn’t have to be a powered hub, but that would allow you to connect a wider range of devices).

If that doesn’t get rid of the problem, try a different make/model of USB keyboard/mouse. You may be using a keyboard/mouse that RISC OS doesn’t like for some reason.

As an aside: I was trying out a NOOBS build on my Pi 3B and I noticed it goes through the NOOBS startup process on every power-on before it boots RISC OS. I didn’t realise there was this extra delay, which can of course be eliminated if you “roll your own” SD card.

You may be using a keyboard/mouse that RISC OS doesn’t like for some reason.

These definitely exist. In about OS 5.18 I had a Microsoft mouse that killed the machine. Boot up and all is well. Use the keyboard and all is well. Nudge the mouse and lose the SD card! This problem was eventually fixed, as it no longer occurs in 5.24, but some mice can definitely cause weird behaviour.

With that said, I’m actually using a Logitech now and haven’t had any problems!

I downloaded Noops, NIPP and the latest version of RiscOS from this website yesterday, they are version 5.24.

If your devices work fine with Linux I would expect the pi beta rom (5.27) to fix this problem.

If your devices work fine with Linux I would expect the pi beta rom (5.27) to fix this problem.

If memory serves then Jeffrey did some changes that fixed problems with the mouse somewhere in the 5.25 labelled beta releases. Obviosly it’s easiest to obtain the 5.27 releases and there additional bug fixes and new features in the 5.27

Of course the standard advice applies: Make sure you use a matching updated HardDisc4 release.

If memory serves then Jeffrey did some changes that fixed problems with the mouse somewhere

My memory thinks it was Colin that did the USB changes.

The link Stuart Painting’s quotes above seems to confirm my memory!