cas

Next m68k evening chat: Date: Friday 28th of May 2021, 20:30 H CEST (18:30H / 06:30 PM UTC) Information: http://m68k.info In the upcoming m68k chat we will talk to Dr. Volker Barthelmann, developer of the vbcc compiler, vasm assembler and vlink linker. vbcc is a highly optimizing portable and retargetable ISO C compiler. It supports ISO C according to ISO/IEC 9899:1989 and most of ISO/IEC 9899:1999 (C99). vbcc runs on and can produce code for a large number of platforms, such as m68k, Coldfire, PowerPC, 65(C)02, i386 (Linux, NetBSD), VideoCore IV (RasperryPi GPU) and even for the Z-Machine (Infocom Text-Adventure VM). See Volker's homepage http://compilers.de/ for more information on the vbcc compiler.

This might be of interest for 6502 coders as well, as vbcc can target 6502 and the Atari 8bit machines: Next m68k evening chat: Date: Friday 28th of May 2021, 20:30 H CEST (18:30H / 06:30 PM UTC) Information: http://m68k.info In the upcoming m68k chat we will talk to Dr. Volker Barthelmann, developer of the vbcc compiler, vasm assembler and vlink linker. vbcc is a highly optimizing portable and retargetable ISO C compiler. It supports ISO C according to ISO/IEC 9899:1989 and most of ISO/IEC 9899:1999 (C99). vbcc runs on and can produce code for a large number of platforms, such as m68k, Coldfire, PowerPC, 65(C)02, i386 (Linux, NetBSD), VideoCore IV (RasperryPi GPU) and even for the Z-Machine (Infocom Text-Adventure VM). See Volker's homepage http://compilers.de/ for more information.

Hi, the next m68k evening developers chat is tomorrow: Friday 6th November 2020, 19:00 H CET (18:00H / 06:00 PM UTC) Location https://meet.m68k.info/m68k (will be online before the meeting starts) Feature 1: New m68k target in Qemu - Laurent Vivier will talk about the existing QEMU Quadra 800 emulation and the linux-user mode. He will explain what are their limitations are, and then what a pure virtual machine can improve. We will see what the machine can do and how to use it. There will be a little demo. Feature 2: Chroot into m68k - a seamless m68k dev environment on Linux with Qemu This time it is less Atari ST specific, but interesting for m68k developers nonetheless See you there Carsten

Christian Zietz did a nice presentation about EmuTOS 1.0 on Atari machines during last weeks m68k online chat The video recording of that presentation is now online on http://m68k.info and on Youtube:

this can be true, I'm pretty sure I've found window.obj somewhere and used it from Turbo-Basic. When I switched over to ACTION!, I've made the ACTION! glue code, but never used it, as in ACTION! it is just simple to write own windowing routines. -- CS

Thanks for giving this information, I'm always interested in programming language concepts. I need to find some time to work with PL65 it seems

the current blog system is too heavy-weight, I plan to move to a lightweight static page blog system. I do not have much free time, so it is moving slowly. But there will be a new content and a new blog at some point of time. The regional group in Frankfurt is still doing strong, but I now live 300 KM away and have a small kid, so I'm not able to attend their meetings. But I meet with Beetle (Stefan) from time to time and do Atari stuff. Greetings Carsten

I've now added WINDOW.OBJ to the atariwiki page (attachment). I remember using these ASM routines first from Turbo-Basic, them later I wrote the ACTION! interface, but never really used it in any applicaitons. The WINDOW.OBJ has not been written by me, I don't remember the origins. -- CS

Sorry, my fault. I will look for the missing file in my disk collection and upload it. Wait for a message here ... Carsten

Just HTTP. I've build a protoype of the new Infothek system, but there was never consensus among the team members how to proceed, that is the reason why the files are still only available this way.

https://atariwiki.orgnow has a Certificate from the "let's encrypt" (Beta) project. To get a A+ ranking from ssllabs.com, I had to cut off some old operating-systems and browsers. This certificate should be trusted by major browsers. Please let me know if you encounter any issues

It has been almost 10 years since I've worked on this, as far as I remember I've contacted LCSI first and they connected me with Mr. Papert, as they didn't had any traces of Atari Logo (at the time). It might be worth a try to start the process again with contacting LCSI, or Cynthia Solomon ( https://en.wikipedia.org/wiki/Cynthia_Solomon).

Well, no. I was in contact with Mr. Seymour Papert (or his office) about Atari Logo back in Summer 2006. Then Mr. Papert had a terrible accident in December 2006 ( https://en.wikipedia.org/wiki/Seymour_Papert#Accident_in_Hanoi) and was unavailable, and I did not follow up. Not sure if I would like to bother him again with the question.

The certificate on the site changes every 6 month. Publishing a cert fingerprint in email or forum-posts does not scale, importing the sites certificate into the browser trust store also does not scale. The real solution is certificate verification via DNSSEC secured DNS, aka DANE. Unfortunaly DANE is not supported natively in the browsers today and requires an extension plugin. I guess we have to wait until the Mozilla/EFF certs are being available in summer.

I know them and I know the Mozilla blog post. I would trust them much less than CACert. Starting and running a certification authority, especially one that has the root-cert in the browsers, is not cheap. It is expensive. How can they offer for free? Some people in the security business I've talked to have suspicion that these two companies are at least partly controlled by their governments/secret services (StartSSL = Israel, Wosign = China). With StartSSL, the inital certificate is free, but any change/revoke in case of a security incident (such as Heartbleed) costs money https://www.techdirt.com/articles/20140409/11442426859/shameful-security-startcom-charges-people-to-revoke-ssl-certs-vulnerable-to-heartbleed.shtml I don't see these two companies as a trustworthy option for getting TLS certificates. I meet (some) CACert people at open source conferences. In person. Their procedures might not be without flaws, but in my view much more trustworthy than WoSign or StartSSL. Carsten