Recent Posts

Topic: Bugs / How can this error happen?

What it was somehow falling into the first DEF FN as well?

Topic: Bugs / Zap Disassemble

Using Zap v tnk-11 (vrpc-dl) to disassemble code.

Clicking select on Zap iconbar.
Clicking memu:Mode.Code (over main window).
(Changes window from Txt to Code)
clicking select on 00000000 line.
Press ‘Enter’ (small window should open at botton of Zap window)
ie 00000000: ANDEQ R0,R0,R0
(This line can now be edited – ie ‘NOP’)

There seems to be a change in the OS between 5.23 (12-May-2017 and 12-Feb-2017.
This small window now does’t open – when ‘Enter’ is pressed – but appears when you type ie ‘NOP’.

RO version 5.25 Apr 23 2018 also does the same.

Any idea – Thanks

Topic: Announcements / FF_Cut

My tool do both…
Create the pieces from the cutpoint list and save in Scrap and merge them to a new file…
Before I do this with a Obey ;-)

Topic: Announcements / Good things come in small packages

Andrew was using what looked like one of these at the show – very dinky it looked too. Liked that all the wires were coming out of one side. Got me thinking about how you never get exactly what you want. I’d have preferred an internal HDD to the external esata connector and a box with the footprint of a HDD

Topic: Announcements / Good things come in small packages

No SATA, but eMMC.

Topic: Announcements / FF_Cut

Excellent idea. For my videos, I use 2 tools: one to cut beginning and end of files; one to merge videos. Point 1 can now be done the easy way under RISC OS :)

Topic: Announcements / IsocPlayer 0.05

Everything I need ;)

Topic: Community Support / An idiot's guide to OmniClient

I’ve done a fresh install of OS 5.24 on my Pi (I figured that it’d be a good opportunity to clean up some of the cruft) and I can’t remember how to set Omni up properly :)

On my previous build I had Omni starting at boot and automatically mounting my NFS share. On the new one I’ve done a “Save mounts” and have added an OmniMount line to the Startup file, but when I start Omni it pops up the “Mount NFS server” window (with the details pre-filled) and I need to manually click on Connect. How can I bypass this? I know I must be missing something simple, because after all I’ve done it before!

Edit: Typical; I managed to figure it out within ten minutes of posting. In Choices.Omni.Mounts I had to add my server name to the end of the file. In other words, instead of this:

NFS,username,O,server,/Users/username,nobody,"",

I had to change to this:

NFS,username,O,server,/Users/username,nobody,"",server

Interestingly the Mounts file from my previous install doesn’t have the server name in the Authentication field, but it seems to need it in 5.24’s version. I don’t know which version of Omni I was previously running, although it’s a bit moot now since it’s solved.

Topic: Community Support / Who likes manga?

Back on the Manga topic, I’m getting an abort on data transfer when trying to open Naruto. I suspect it’s a server-side issue as other manga work fine (which will make this a bit tricky to debug if they fix it before Rick can try it!) but obviously it shouldn’t crash the app :)

I’m running Manga 0.20, SecureSockets 1.05 and OS 5.24. I can supply a Debugger log on request.

Topic: Community Support / PackMan in 5.24

Mine’s still in $.Apps even after doing the update (with a backup of the conflicting files). I know what you mean about it creating new directories all over the place, but you can avoid that: When you choose to install an app, you get a window with the app’s icon. You can drag that icon into a Filer window, like you would in a Save As window.

I have a suspicion about what’s happened in my case: I think the 5.24 image is probably based on an older “RC” image, which originally had PackMan 0.8.3 installed. My guess is that someone at ROOL dropped PackMan 0.9.1 over the top of 0.8.3 using Filer, instead of letting PackMan update itself. PackMan’s database therefore thinks that 0.8.3 is still installed.

That’s just a guess, but it seems to correspond with what’s happening. Same with PipeDream, SUL and StrongHelp; I think they were previously installed via PackMan and subsequently updated via Filer without “telling” PackMan that they’ve changed.

Does this sound like a plausible theory?

Topic: Announcements / Wakefield Show 2018 New Game : Early Version

Thank you to everyone that bought the early version of Island of the Undead at the Wakefield show.

This game is still in beta at present and corrections are being made based on feedback from my beta testers.

Currently I’m targeting the 30th of April for upload to the Plingstore and fixing of any bugs raised during beta and the addition of more level data.

As usual, all game updates are free. For any of the existing AMCOG titles, please drop me a line via www.amcog-games.co.uk/about.htm if you have any bugs that you have found that you would like me to fix.

Thanks for your patience.

Best Regards,

Tony Bartram
www.amcog-games.co.uk

Topic: General / AMCOG Games : Beta testing

Thanks Mark. Hope your wrist gets better soon Rick & thanks for the detailed beta feedback.

François Vanzeveren – please would you drop me an email to info at amcog – games dot co dot uk so I can add you to the beta e-mail thread.

Thanks,

Tony

Topic: Community Support / PackMan in 5.24

Yes, in 5.23 from last year.

I think it is because my PackMan is in $.Apps but for some reason it wants to install it someplace else like $.Apps.Utilities? I told it to go ahead and update (backing up the conflicts), then I went and found the new version and dropped it into $.Apps. Might have been able to do this directly from PackMan? It wasn’t obvious how so I just cheated. No doubt it’ll whinge about this the next time I run it. ;-)

It seems strange to me that:

• The Apps “device” is mostly built out of applications in $.Apps
• The Apps “device” doesn’t support directories
• It’s apparently now the done thing to organise apps in loads of tidy directories within $.Apps.

Uh…?

Topic: Community Support / PackMan in 5.24

I’ve downloaded and installed 5.24 onto my Pi 3 and I’m having an odd issue with PackMan.

The icon bar menu reports that it’s version 0.9.1 Beta, however the main PackMan window says that it’s 0.8.3 and that an upgrade to 0.9.1 is available. If I try to install it then I get a window telling me that there are file conflicts.

Is this happening to anyone else?

Edit: And a similar issue with PipeDream. The 5.24 image includes 4.55.04 but PackMan thinks that 4.52.5 is installed and offers to upgrade it. It also has upgrades to the already-installed versions of SharedUnixLibrary and StrongHelp. What’s going on here?

Topic: General / MiniUART

Nice work, Timo! It would be great to see the code.

Topic: Announcements / FF_Cut

Have made a skeleton solution for cutting videos.

Mplayer as a nested window in the main window play the video with the timeline via OSD (UnixFC, UnixFont, UnixHome must be seen by the filer). If the focus is on the mplayer window you can use the shortcuts for mplayer to navigate in the video. If the cursor is in the writable icons …
At this time only one video can used at the session. I play around with playlists. Should be possible to use more than one part.

After “start cutting” the pieces will be safed in scrap and added to a new file… The temporary stuff in scrap will be delete if the new video is ready.

Is not ready but usable at thei time. If anyone has a interest for testing, please contact me.

Topic: General / MiniUART

On the rPi there are two UARTS:
- PL11
- MiniUART
I’m in the process of writing code for the MiniUART of the rPi. This discussion was partly in another forum topic:https://www.riscosopen.org/forum/forums/5/topics/9229
I’m happy to announce that I can also read data now:

The code is written is written in C instead of assembler and uses the ROOL compiler

Topic: Bugs / How can this error happen?

This is highly artificial

There’s so many lovely little things like that, yes.

I wonder if it’s a CC instead of an 8B.

Topic: Bugs / How can this error happen?

execution is falling into the function

I missed the STOP messages. If it can execute 7059, and it has not got there from a GOTO, then it seems it has fallen through 7050. However, if at that time it was in a Function, then it would have returned from the THEN or ELSE. If it was not in a Function, it would have errored at 7050 with ‘Not in a Function’. Something is not as it seems. We need to find how it arrived at the STOP. *ReportStack would display the current outstanding PROCs or FNs on the stack at that point.

But I still bet on memory corruption somehow somewhere.

Topic: Bugs / How can this error happen?

This is highly artificial and almost certainly does not represent what you have, but it does reproduce the error.

PRINT FNmax(1,2)
END
7040 DEFFNmax(A%,B%)
7050 IF A%>=B% THEN =A% ElSE =B%

7060 DEFFNmin(a%,b%)
7070 IF a%>=b% THEN =b% ELSE =a%

It illustrates the clumsy way that BASIC interprets IF...THEN...ELSE.

I do not think it can be the source of your error, but another possible problem is that BASIC searches for the next ENDIF or ENDCASE if there is not one at the end a structure, and this can mean jumping out of a DEF into another further on in the program.

Topic: General / AMCOG Games : Beta testing

And they’re famously not good at riding bicycles.

Rick said

Brainssssss

Topic: Bugs / How can this error happen?

That means that there is plenty of time for something to overwrite the a% or b% variable space or even any of the chain of variable names starting in a and b that were allocated before a% and b%.

We have already established that execution is falling into the function:

Anyway: 7059 STOP has produced “Stopped” on a couple of occasions.

Topic: Bugs / Catastrophic WIMP bug

OK thanks, it’s where it has always been. Fingers crossed it works on RO6 too.

Topic: Bugs / Catastrophic WIMP bug

ROMPatch module is in RO4Patches directory and not in RO6Patches directory. I have not checked to see if it is elswhere

Topic: Bugs / Catastrophic WIMP bug

Rick mused

Especially since one chooses to skip an entire version number (add one potato) to make a point that few people were really interested in, leaving a legacy of buggered up RMEnsure versioning.

1. Everyone has been very silly
2. Saying RO5 is the only developed branch does not make the other versions conveniently disappear
3. There is still a certain degree of Pace-era “well it works for us” silo mentality going on

The RMEnsure ‘problem’ did not start with RO6, it has been going wrong since last century. For example, here is the version history of the !Help module:

I am not picking sides when I say that nobody should release different things with the same version number. Randomise the order if you must, but no doppelgängers!