Remote Control via telnet

[em00k]

It would be nice to be able to control the emulator via external commands sent over telnet.

This would allow spectrum software to be integrated into modern desktop applications and controlled "remotely":

Such commands as :

read-memory [start] [end] - returns a stream of bytes from the spectrums memory
write-memoty [start]-[end] - writes a file as a data stream to the spectrum ram
send-key [ascii]

much like the great Zesaurx does,

[Cthutu]

What form does the stream of bytes take? ASCII hexadecimal or actual bytes?

[em00k]

It could be either, I suppose base 10 would be easiest. send-memory 16384 11 22 33 10 10 10 33 44 11 33 etc ‌

…

On 18 February 2018 at 21:33, Cthutu ***@***.***> wrote: What form does the stream of bytes take? ASCII hexadecimal or actual bytes? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AVLUTIW5Mmp9QU_PUwkBbze4mgTFeDULks5tWJcjgaJpZM4SJMYj> .

-- Cheers, David David Saphier david.saphier@gmail.com

[Cthutu]

So the format is whitespace-separated values. How would hex numbers be given? C-style or assembly style? e.g. 0x, $, # etc. On 18 February 2018 at 16:36, David Saphier <notifications@github.com> wrote:

…

It could be either, I suppose base 10 would be easiest. send-memory 16384 11 22 33 10 10 10 33 44 11 33 etc ‌ On 18 February 2018 at 21:33, Cthutu ***@***.***> wrote: > What form does the stream of bytes take? ASCII hexadecimal or actual bytes? > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <#1 (comment)>, or mute > the thread > <https://github.com/notifications/unsubscribe-auth/AVLUTIW5Mmp9QU_ PUwkBbze4mgTFeDULks5tWJcjgaJpZM4SJMYj> > . > -- Cheers, David David Saphier ***@***.*** — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAVRxvSQl28CBfnkUn7eUR9MM5ZkuXiKks5tWJfcgaJpZM4SJMYj> .

[Cthutu]

BTW, I am working on telnet server code at the moment :)

[em00k]

In Zesarux bytes are sent : send-memory 16384 00 11 45 etc and hex send-memory-raw 16384 000b2d which seems to me a pretty easy way to deal with it by Cesar. <https://mailtrack.io/> Sent with Mailtrack <https://chrome.google.com/webstore/detail/mailtrack-for-gmail-inbox/ndnaehgpjlnokgebbaldlmgkapkpjkkb?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality>

…

On 19 February 2018 at 00:57, Cthutu ***@***.***> wrote: So the format is whitespace-separated values. How would hex numbers be given? C-style or assembly style? e.g. 0x, $, # etc. On 18 February 2018 at 16:36, David Saphier ***@***.***> wrote: > It could be either, I suppose base 10 would be easiest. > > send-memory 16384 11 22 33 10 10 10 33 44 11 33 > > etc > > > > ‌ > > On 18 February 2018 at 21:33, Cthutu ***@***.***> wrote: > > > What form does the stream of bytes take? ASCII hexadecimal or actual > bytes? > > > > — > > You are receiving this because you authored the thread. > > Reply to this email directly, view it on GitHub > > <#1 (comment)>, or > mute > > the thread > > <https://github.com/notifications/unsubscribe-auth/AVLUTIW5Mmp9QU_ > PUwkBbze4mgTFeDULks5tWJcjgaJpZM4SJMYj> > > . > > > > > > -- > Cheers, > > David > > David Saphier > ***@***.*** > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <#1 (comment)>, or mute > the thread > <https://github.com/notifications/unsubscribe-auth/ AAVRxvSQl28CBfnkUn7eUR9MM5ZkuXiKks5tWJfcgaJpZM4SJMYj> > . > — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AVLUTBgYHl1lel0wdbgrAm_RFIqMhk7Cks5tWMbsgaJpZM4SJMYj> .

-- Cheers, David David Saphier david.saphier@gmail.com

[em00k]

Awesome :) ‌

…

On 19 February 2018 at 01:00, David Saphier ***@***.***> wrote: In Zesarux bytes are sent : send-memory 16384 00 11 45 etc and hex send-memory-raw 16384 000b2d which seems to me a pretty easy way to deal with it by Cesar. <https://mailtrack.io/> Sent with Mailtrack <https://chrome.google.com/webstore/detail/mailtrack-for-gmail-inbox/ndnaehgpjlnokgebbaldlmgkapkpjkkb?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality> On 19 February 2018 at 00:57, Cthutu ***@***.***> wrote: > So the format is whitespace-separated values. How would hex numbers be > given? C-style or assembly style? e.g. 0x, $, # etc. > > On 18 February 2018 at 16:36, David Saphier ***@***.***> > wrote: > > > It could be either, I suppose base 10 would be easiest. > > > > send-memory 16384 11 22 33 10 10 10 33 44 11 33 > > > > etc > > > > > > > > ‌ > > > > On 18 February 2018 at 21:33, Cthutu ***@***.***> wrote: > > > > > What form does the stream of bytes take? ASCII hexadecimal or actual > > bytes? > > > > > > — > > > You are receiving this because you authored the thread. > > > Reply to this email directly, view it on GitHub > > > <#1 (comment)>, or > > mute > > > the thread > > > <https://github.com/notifications/unsubscribe-auth/AVLUTIW5Mmp9QU_ > > PUwkBbze4mgTFeDULks5tWJcjgaJpZM4SJMYj> > > > . > > > > > > > > > > > -- > > Cheers, > > > > David > > > > David Saphier > > ***@***.*** > > > > — > > You are receiving this because you commented. > > Reply to this email directly, view it on GitHub > > <#1 (comment)>, or > mute > > the thread > > <https://github.com/notifications/unsubscribe-auth/AAVRxvSQl > 28CBfnkUn7eUR9MM5ZkuXiKks5tWJfcgaJpZM4SJMYj> > > . > > > > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <#1 (comment)>, or mute > the thread > <https://github.com/notifications/unsubscribe-auth/AVLUTBgYHl1lel0wdbgrAm_RFIqMhk7Cks5tWMbsgaJpZM4SJMYj> > . > -- Cheers, David David Saphier ***@***.***

-- Cheers, David David Saphier david.saphier@gmail.com