The Sinclair QL Forum

Rexx did make an appearance on the Amiga too - Arexx - and was quite a fully featured version of it.

I think Xedit was ported to Windows / Linux under the name Sedit - but not sure the source code ever got released, and it was, what processor that would have been for.

If you wanted to read / write from a QL file system, then you'd need to use an approach similar to QEP III - reserve some RAM to store your ROM image into, then go into a quiesced state (no interrupts, no jobs running, etc) then flash your code QEP III is able to multitask via "EPROM_M ...

EMACS?
Micro_EMACS?

I feel the urge to port Vi/Vim to the QL! :D :D :D

...

Cheers,
Norm. (Posting from outside the supermarket until we get broadband!)


NOOO!

I have to use vi a fair bit at work - and I have to say I hate it. It's similar enough to Xedit which I used to use on IBM ...

I would suggest forcing a system restart after programming the flash.

If you've changed base OS code - you want to ensure you re read it again.

As others have pointed out - even if your flashing routine was in RAM memory, and you made the whole process atomic with no interruptions or other ...

I favour a utility to do flash programming.

The timing loops can be avoided by using a facility that most flash vendors provide - which is a 'busy' bit that can be read - if it's still set, you loop around until it's cleared - then move onto the next bit/byte/block and so on.

I don't know if you are aware of retrobrew - but there's a chap there - Will Sowerbutts - who wrote a flashing utility for Z80 - I think source is available - but I understand it runs standalone - so doesn't need the OS - in fact, flashing the ROM on a QL would need it to be 'out of the OS' when ...

Have you got a picture of the chip to see what the label looks like?

You did mention the possibility of them being suspect...


With a bright light the text is visible


IMG_5047.jpeg


The K prefix seems to be used by several manufacturers - Not sure on the other codes under the part number ...

Have you got a picture of the chip to see what the label looks like?

You did mention the possibility of them being suspect...

The scanner has thrown up an issue with the AT24C256

It shows as both &54(&A8) AND &5C(&B8), confirmed as when unplugged both devices vanish

&54(&A8) works fine with both test programs

&5C(&B8) corrupts the end of the "page test" text
I thought maybe it was writing to Minerva, but on checking ...

So that Humidity and temperature device offers 2 modes - one using clock stretching (the hold commands) and one that doesn't use clock stretching - In the latter - you kick off your command to do the read, but then your program and the I2c bus are free to do other things, you come back at some point ...