The Sinclair QL Forum

Peter wrote: ↑Mon Oct 16, 2023 6:24 pm Did you try to receive a directory of Q68's filesystem from the QL side? It crawls extremely here. (More than one page length, SGC, both sides SMSQ/E)

Yes, I did DIR s1_win1_ from the QL where the Q68 was station 1 and the QL station 2.

Hi Peter, The QL sending data feels similar as Q68 and the likes. E.g. getting the QL directory from the Q68 with DIR s2_win1_ feels fine. Receiving looks like slowing down to a few characters per second, e.g. when the QL tries to receive a Q68 directory with DIR s1_win1_. The best is to try yoursel...

\Thanks for the hint. Yes I have version 2.25, too. Did you already find the time to make a serial cable? I could also make it for you, but afraid of shipping to Netherlands again... Plenty of cables here, I just need to find a DB-9 connector (I've had plenty of them, just have to do some searching...

Which version of SERnet are you using, and how are the devices configured? Can't find the version at the moment. Likely the most recent one. If it is very important, I need to download some versions and compare the binaries. Configured to SRX1 and STX1, according to your driver. I believe the lates...

How much slower is the SERnet receive compared to two Q68s, or a Q68 and a PC? The QL sending data feels similar as Q68 and the likes. E.g. getting the QL directory from the Q68 with DIR s2_win1_ feels fine. Receiving looks like slowing down to a few characters per second, e.g. when the QL tries to...

Device I/O is controlled by the scheduler loop which executes at least every 20 ms if the machine is in user mode. Hmmm... if that leads to just one character received per 20 ms, it might explain the problem. But there should be not much CPU load and the loop should run much more frequently. Are yo...

Derek_Stewart wrote: ↑Sun Oct 15, 2023 10:17 am Sorry to divert attention away, but the talk about SuperHermes SER3, I remembered that the SuperHermes has 6 Serial ports:

I guess we need a QIMSI_SER_PORT command

Here is another MiniQ68 program for SER-QL transfer at 115200 Baud, sources included. It causes the green QIMSI LED to blink forever, after a receive overrun occured. (The LED toggling mechanism after every byte was removed.) I have tested the overrun detection to work. I see no overrun using SERNE...

Normally a device interrupt, or at least a polling/timer interrupt is required to trigger resume. (In general for a multitasking OS - not just for the QL). Fact is, the QL somehow does resume receive, otherwise SERNET wouldn't work at all. We better find out how. Device I/O is controlled by the sch...

I can confirm that SERNET works now, and FSERVE works on top. The Q68 getting a file or directory from the QL appears fast, although this involves the bitwise write access to the ROM port. I might speed this up a bit by unrolling the loop, as discussed by mail. The other direction (QL reading from ...