ROOL Forum: Recent posts

Tue, 14 Apr 2026 13:11:26 +0000

Nope… The paddles are directly connected to a RPi via GPIO… I can provide the source code I have so far, which indeed uses the CModule example from the DDE… Let me know how to get it to you if you want to take a look at what I have so far… I’ve had a demo of the hardware at a couple of shows over the last two years or so… Just struggling to find time (and docs/knowledge) to complete the driver…

Tue, 14 Apr 2026 13:10:39 +0000

All good now I opted for Uniprint, and it just works!, can’t be dealing with faffing around looking for stuff that might or might not work. I would highly recommend it

Tue, 14 Apr 2026 13:09:02 +0000

So in the interest of curiosity how does one, Fork the entire Opensource Gitlab that ROOL have, if someone wanted to progress RISCOS separately, because there is no fork option from what i can see without having an account directly to the ROOL Servers.

Tue, 14 Apr 2026 12:54:05 +0000

I have got my Brother HL-L2550DW working

Same here but Brother HL-L2400DW.

Tue, 14 Apr 2026 12:30:18 +0000

@Stefan
I have got my Brother HL-L2550DW working quite well using Dave Higton GetIPP, FindIPP and IPPTrnspt programs.

Tue, 14 Apr 2026 12:29:36 +0000

@George, I don’t think we are in a position to know whether this has been a gross waste of resources because we don’t know the maintenance load this would put on ROOL, which we are not in a position to judge (but ROOL are). Nothing is to be gained by second guessing what happened.

Martin wrote:

I think what all of us want is for everyone to work together without unnecessary conflict.

100% agree, and oddly enough little of the conflict seems to originate from ROOL or ROD themselves, but from the “factions” that have developed around them. I think the constant pressure for transparency is likely just to fuel the conflict. We don’t need the details, we don’t need transparency (which has a time/effort cost that may be best spent elsewhere). Lets just let people get on with developing cool stuff and be supportive.

It is possible that there was a conflict between ROOL and ROD, but perhaps they think being reticent about it is the best approach in order to maintain a possibility of working together in the future, and we (by constantly trying to open the can of worms) are making things worse? As I said, how are we benefitting from this?

Tue, 14 Apr 2026 11:50:20 +0000

Anyway, that ship has sailed, so let?s not keep on about it.

Indeed, but no supporter of ROOL and the platform generally can regard a system where £20k (25% of total bounty allocations, no less) will be spent duplicating functionality that already exists as satisfactory, or incapable of improvement. Simple question: if and when ROOL’s stack becomes available, how many people will actually use it? I’m sure all the actors involved in this situation were motivated by a sincere wish to do the best for the platform, but the upshot has been a gross waste of resources, as far as I can see. There must be a better way, surely?

Tue, 14 Apr 2026 11:39:21 +0000

OK, did a bit more digging and found the info buried in the printer’s manual.

This printer only supports PCL, so you’ll want to use a HP LaserJet driver with it, probably LaserJet 6.

There’s the PCL duplex drivers on !Store (free) from Richard Darby that should allow you to take full advantage of your printer’s features. However, I have not tried the PCL duplex drivers I’m afraid, as all my printers are postscript.

Hope this helps.

Tue, 14 Apr 2026 11:31:36 +0000

@Doug Webb: Sorry for having asked. Maybe you’ll try Google Search yourself? You’ll get nothing of worth and certainly not the website “https://www.sbellon.de/sw-modules.html”. Far better are the results of Brave Search (AI) for “RISC OS network printing” and “RemotePrinterFS”. They will give general explanations but not a certain website with software to download. Which is 20 years old, maybe that is the reason.
And installing the tool and finding out the exact command to write into the printer driver connections, the next.
BTW: The Brother Network printer I bought long ago because Brother is said to be very Linux-friendly. And they are. In Linux you start Mint or MX and the printer will be detected simply because it is connected via a network cable – and is correctly handled down to it’s ability for printing double-sided.
It’s always a problem if someone new signs on the RISC OS muster roll… but take the positive side: It will not happen all to often!

Tue, 14 Apr 2026 11:30:00 +0000

@Martin I think it varies by model. Because Postscript itself has/had a licence cost associated with it, many printer manufacturers developed their own postscript-compatible languages – Br-Script is one, Kyocera’s KPDL is another. If they are implemented at hardware level on the printer, they work with the RISC OS postscript drivers.

However some models handle this “in driver” rather than at the printer end, and those models tend to be problematic. Unfortunately Brother have (seemingly) removed a lot of the technical info about the printer that Stefan owns because it has been discontinued. This made it tricky for me to find the info I wanted (perhaps a longer search would have yielded results).

My own Brother colour laser multi-function printer (now around 10-12 years old) supports postscript (via hardware Br-Script) just fine, but there are models that don’t.

Tue, 14 Apr 2026 10:51:20 +0000

@Steve Fryatt I think it would be more accurate to say that I suggested an alternative course of action that could be achieved more cost effectively (possibly). It was in no way an attempt to claim a bounty – just a comment that it might be cheaper/quicker to integrate a piece of existing work than to do it from scratch. Perhaps that’s incorrect (but worth exploring?), but it would arguably be preferable than having two different solutions to the same nut. Each to their own, though.

For the purpose of clarity, I’m assuming the bounty claimant for that work would be someone of ROOL’s choosing, not ROD (who would do it for free if there was any certainty of acceptance). My assumption was that it would be procedurally better to have it vetted by a non-ROD person. ROOL have commented on the amount of time/work/effort that is required to merge a large project, so it seemed (to me) to be a possible use for bounty funds to reward whoever tackled that. Of course, that’s not up to me, but it was a suggestion (from the beginning).

Anyway, that ship has sailed, so let’s not keep on about it.