Re: [Ql-Users] SMSQ/E 3.35

2020-02-08 Thread Wolfgang Lenerz via Ql-Users



Hi,

>
> Something's wrong, I'm afraid.
>

yes it definitely is.

My local copy unzips OK.

I downloaded the file from my site, and indeed, no way you can unzip it, 
the file has a length that doesn't even correspond to the real length of 
the file (the real length, in bytes, is actually shown on the webpage). 
OK, I thought, some file corruption happened during uploaded.. I 
re-upped the file. The length of the file on the webpage was correct 
(the length is displayed via a small php script, so it takes the length 
of the file as it actually is on the site). Just to be sure, I 
downloaded the file again. And again, no way to unzip it as again it's 
not a valid zip file.
After some more re-up- and re-downloads, where I had the same problem, I 
tried various other things. The result is that I renamed the file (on 
the site, not locally!) to smsqe335b.zip (and edited the html page to 
point to that). Now it works - but the file is called smsqe335b.zip - I 
think one can live with that.


Isn't computing wonderful?

(Oh, and just to be sure that I wasn't dreaming, I then renamed the file 
to smsqe335.zip again -and edited the html file-, re-downloaded - not a 
valid zip file. Go figure).


Wolfgang
___
QL-Users Mailing List


Re: [Ql-Users] SMSQ/E 3.35

2020-02-08 Thread Jan Bredenbeek via Ql-Users
On Sat, 8 Feb 2020 at 06:47, Wolfgang Lenerz via Ql-Users <
ql-users@lists.q-v-d.com> wrote:

> Hi Brian, Jan
>
> Strangely enough, I can't reproduce the version problem here.
>
> To be extras sure, I downloaded the version uploaded yesterday and
> tested them of Q68 and QPC.
>
> All files should have the date of 07.02.2020 06:41 and, at least here,
> correctly identify as 3.35.
>

My fault - I copied the SMSQE.bin file to the wrong directory :-/


> > Speaking of the Q68, it appears that the SER_ commands like SER_BUFF
> > etc. still don't work. I discovered some months ago that this is caused
> by
> > an incorrectly named Thing ('ser_prt' while the SBASIC commands search
> for
> > 'ser_par_prt'). I'm not sure whether I've reported it here (I did so in
> the
> > QL forum but Wolfgang doesn't read that).
>
> I don't remember seeing it, but thanks - that'll be fixed in a new version.
>

Thanks in advance.

> So far I haven't been able to fix
> > this myself as SMSQMake stops with an 'invalid name' error at line 11330
> > when I try to build it.
>
> Load the menu extensions first, then it will work. I'll probably remove
> that anyway, but I'll have to check first if I use other parts of the
> menu extensions.
>

Okay, it assembles well now, thanks.


> > Another issue I've run into is the TCP device which, unlike UQLX, doesn't
> > report EOF when the other end has closed the connection, you'll just keep
> > waiting forever for input. (Yes, I've been doing a few networking
> > experiments lately, you'll see the results soon :-) ).
> >
>
> On what machine? (I presume SMSQmulator and will check).
>

It definitely does on QPC2 but I remember SMSQmulator had the same problem.


> > Well so far for the bug reports, thank you Wolfgang for keeping SMSQ/E
> > alive!
>
> Luckily enough, I'm not alone in that. Simply building SMSQ/E is now a
> fairly well automated process (SMSQEMake - when it works...) and making
> all of the new version files is, too - see the file "new_versions_bas"
> in the extra directory - it even makes the html files (I once even
> had the idea of building an ftp client, so that the upload to my site
> could be made automatically, but never actually started that,the main
> reason being that I know next to nothing about networking, let alone the
> ftp protocol).
>

And ftp is rather obsolete now and considered insecure :-).
I'm nearly finished implementing the Telnet protocol for QBOX, but I should
really have had to implement SSH with AES-256 and 4096-bit keys :(.
Fortunately there is an easy way to let the host OS do the SSH stuff and
forward the plain text to QBOX using Telnet.


> What is much more important than the build process is the people who
> make changes to SMSQ/E or find (and report!) bugs.
>
> Keep on QLing! (Somehow "keep on SMSQ/Eing" doesn't have the same ring
> to it).
>

Well, "keep on QDOS'ing" also doesn't sound very well, a bit too much like
"keep on DDOS'ing" :-)

Jan
-- 
*Jan Bredenbeek* | Hilversum, NL | j...@bredenbeek.net
___
QL-Users Mailing List


Re: [Ql-Users] SMSQ/E 3.35

2020-02-08 Thread Thierry Godefroy via Ql-Users
On Fri, 7 Feb 2020 07:04:44 +0100, Wolfgang Lenerz via Ql-Users wrote:

> SMSQ/E 3.35 is out now (wlenerz.com/smsqe).

When trying to unzip the archive I downloaded from your site (several
times, from both a browser with cleared cache and with curl & wget), I
get:

Archive:  smsqe335.zip
warning [smsqe335.zip]:  13830 extra bytes at beginning or within zipfile
  (attempting to process anyway)
error [smsqe335.zip]:  start of central directory not found;
  zipfile corrupt.
  (please check that you have transferred or created the zipfile in the
  appropriate BINARY mode and that you have compiled UnZip properly)

Something's wrong, I'm afraid.

Thierry.
___
QL-Users Mailing List


Re: [Ql-Users] E-mail etiquette: New subject, new message

2020-02-08 Thread Norman Dunbar via Ql-Users
Hi Marcus,

+1.

I raised this some time ago too. It made no difference sadly, however, your 
point about some web mail browsers using the subject to group messages makes 
sense. I hadn't thoughtbabout that. 

I use Thunderbird and it uses the message id, and the problem you mention 
drives me nuts! But I'm quite easily annoyed ;-)

Hopefully, it will stop. Sadly, I doubt it will. People at work do it too - 
then get upset because they replied to messages our team are deleting with a 
rule. Oops!

Here's hopeing


Cheers,
Norm.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
___
QL-Users Mailing List


Re: [Ql-Users] E-mail etiquette: New subject, new message

2020-02-08 Thread pjwitte via Ql-Users
A lot of people simply dont know this because they never view their 
mails by thread. I know I didnt, until I was told off about this some 
years ago. (I hope Ive managed to behave since then!)
On this list there also used to be a convention to top- or tail- reply 
(I can no longer remember which 'cause I do it so rarely these days) 
Tony Firshman used to ball us out regularly for misbehaving wrt this.
As anyone who tries to write programs for the QL "that just work out 
of the box" knows only too well, educating the general QLing public is 
a soul-destroying task. I guess we are a particularly idiosyncratic lot!

Id like to do better, truly I would. I can only keep trying ;o)
Per

On 08/02/2020 21:01, Marcos Cruz via Ql-Users wrote:

Hello.

Probably most of you know that e-mail messages contain, in their
metadata, a unique message identifier and also the unique message
identifier of the responded message, if any. These identifiers allow the
automatic hierarchic organization of messages into threads.

Sometimes in this list, messages that start a new subject, actually are
"responds" to other unrelated messages (even several years old). That is
unlogical, has no advantage, breaks the sense of the threads and makes
reading the list more difficult.

For example, the recent announcement of the 16th Sinclair QL Italian
meeting is a "respond" to the announcement of the 15th meeting (posted
in 2018-10), which was a "respond" to the announcement of the QDOS/SMS
reference manual 4.1 (posted in 2016-09).  And then, three days later,
the announcement of SMSQ/E 3.35 is a "respond" to the announcement of
the 16th Italian meeting...  As a result, without reason, both recent
and interesting announcements belong to (and are "hidden" in) a thread
started more than three years ago, and therefore they don't appear as
two independent new threads at the top of the current hierarchy of
messages in 2020-02, as they should.

I know some webmail services don't care about the message identifiers
and use the subject fields instead in order to recreate and display the
threads, but that's not the way e-mail is supposed to work.  Perhaps
that is the reason some users don't realise the trouble caused by
writing a new message by "replying" to whatever previous unrelated
message, instead of writing an actual new message.

Changing the subject in a thread only makes sense when the actual
respond naturally leads to a different topic, but there's a helpful
convention to mark that cases: "Re: New subject (Was: Old subject)".

Please remember a basic rule of e-mail (lists) etiquette: New subject,
new message; only respond to a message if you actually want to respond
to what that message contains.

Thank you in advance.

Kind regards.



___
QL-Users Mailing List


[Ql-Users] E-mail etiquette: New subject, new message

2020-02-08 Thread Marcos Cruz via Ql-Users
Hello.

Probably most of you know that e-mail messages contain, in their
metadata, a unique message identifier and also the unique message
identifier of the responded message, if any. These identifiers allow the
automatic hierarchic organization of messages into threads.

Sometimes in this list, messages that start a new subject, actually are
"responds" to other unrelated messages (even several years old). That is
unlogical, has no advantage, breaks the sense of the threads and makes
reading the list more difficult.

For example, the recent announcement of the 16th Sinclair QL Italian
meeting is a "respond" to the announcement of the 15th meeting (posted
in 2018-10), which was a "respond" to the announcement of the QDOS/SMS
reference manual 4.1 (posted in 2016-09).  And then, three days later,
the announcement of SMSQ/E 3.35 is a "respond" to the announcement of
the 16th Italian meeting...  As a result, without reason, both recent
and interesting announcements belong to (and are "hidden" in) a thread
started more than three years ago, and therefore they don't appear as
two independent new threads at the top of the current hierarchy of
messages in 2020-02, as they should.

I know some webmail services don't care about the message identifiers
and use the subject fields instead in order to recreate and display the
threads, but that's not the way e-mail is supposed to work.  Perhaps
that is the reason some users don't realise the trouble caused by
writing a new message by "replying" to whatever previous unrelated
message, instead of writing an actual new message.

Changing the subject in a thread only makes sense when the actual
respond naturally leads to a different topic, but there's a helpful
convention to mark that cases: "Re: New subject (Was: Old subject)".

Please remember a basic rule of e-mail (lists) etiquette: New subject,
new message; only respond to a message if you actually want to respond
to what that message contains.

Thank you in advance.

Kind regards.

-- 
Marcos Cruz
http://programandala.net
___
QL-Users Mailing List


Re: [Ql-Users] SMSQmulator 2.28

2020-02-08 Thread Badaman - sinclairql.es via Ql-Users
Hola!

El 8/2/20 a las 7:15, Wolfgang Lenerz via Ql-Users escribió:
>
>
> ¡Hola!
>
>>
>> This corrects a problem of loading images on the screen using lbytes.
> ...
>
> This must have been in there for quite some time, I wish somebody had
> told me about it earlier.
>
> ...


I've discovered it days ago, when I tried the new game P.I. Cole. I was
doing tests and just came to communicate the problem when I found this
good news.


>
>
>> I have seen that an entry called "JmenuItem1" appears in the File menu.
>
> Ooops. That's for something I may introduce in a future version.
>
>
>> Tell you that I tried the emulator in Haiku (BeOS) and it works
>> correctly in OpenJDK, but some characters are not shown in the menus.
>> for example, special characters such as the opening of interrogation or
>> exclamation, the letter ñ or the ellipses (...) that indicate that this
>> menu option will open another menu.
>>
>
> You're the first person I know that uses BeOS or it's descendants. Nice!


It is a system that I have always liked a lot and I need to spend more
time to get to know it better.


>
> I'm afraid that there's not much I can do about the characters not
> showing. Normally Java should use standard unicode (if there is such a
> thing).
>
> Can you normally display these characters on your system?
>
> It's not the fault of OpenJDK, as that's what I use here.


I have not tested with other java applications in BeOS yet, but the rest
of the applications installed in the system show these characters properly.

I also use OpenJDK on Linux and I don't detect that problem.


It may be something related to the configuration of the hpkg package or
to the configuration of my Haiku system.


>
> Wolfgang
>
>> Thank you for your work.
>>
>>
>> El 7/2/20 a las 11:34, Wolfgang Lenerz via Ql-Users escribió:
>>> Hi all,
>>>
>>> SMSQmulator 2.28 is out now.
>>>
>>> (www.wlenerz.com/smsqmulator)
>>>
>>> Have fun!
>>>
>>> Wolfgang
>>>
>>> NB Sorry if this gets double-posted, I haven't had a return yet...
>>> ___
>>> QL-Users Mailing List
>>
>>
>> ___
>> QL-Users Mailing List
>>
> ___
> QL-Users Mailing List


___
QL-Users Mailing List

[Ql-Users] testing

2020-02-08 Thread pjwitte via Ql-Users

I sent a response to something here, but it didnt arrive..

___
QL-Users Mailing List