The Sinclair QL Forum

Hi Martyn,

No rush on my account, I still have a lot of figuring out to do.

Thanks for taking the trouble!

A year and a half on, did anyone have any joy with this on Ql-type hardware?

Hi Per! I developed the MEM driver a bit further than Simon's and Lau's originals and it works under SMSQe quite nicely. I'll digit out and share the (revised) source and binary when I'm back at my laptop. Hi Martyn, Is this still happening? I was hoping to test whether NASERVE blocks it, as tofo s...

Great! Looking forward. Thanks

I moved this from the Announcing availability of a QLNET driver for the Q68 (ND-Q68) topic. Re the MEM device and network security: <> Block, yes (simply don't start FSERVE or the mem driver), limit, well, no. QL designers believed in the good in people. You could maybe use Toolkit III, that allows ...

<> But anyways: Everything regarding to the QL regarding networking is a potential security risk and should only be operated behind a firewall - So don't use any of the many available online banking applications and don't run your business-critical enterprise applications on it ;) Oh sh*t! NOW you ...

What could be of interest in this context is the mem_ device driver which is part of the DIY toolkit (in the v_n section) - That allows you (amongst some really "magic" (or is it dubious?) other stuff) to PEEK and POKE into a remote machine's memory over QLAN (George Gwilt's NET_PEEK does...

bixio60 wrote: ↑Thu Mar 07, 2024 12:22 pm <>
This is the simple program that run on Q68:

110 ch=FOP_IN ("tcp_time.nist.gov:13")
<>

I just get Not found. What driver do you load?

So now we have Nasta, Wolfgang, Jan, Tobias, Stephan, Oliver, Fabrizio, Urs, Markus, Detlef, Diane, Per (likely), Graeme (possible), myself ... I'm sure I forgot someone. And these are only the well known names... I suspect this will become the most high-carat meeting in two decades :D Include me o...

Still thinking about it..