Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.forth > #135150
| From | Ruvim <ruvim.pinka@gmail.com> |
|---|---|
| Newsgroups | comp.lang.forth |
| Subject | Re: Back to the Forth Virus |
| Date | 2026-06-08 12:23 +0000 |
| Organization | A noiseless patient Spider |
| Message-ID | <1106c8c$37c1i$1@dont-email.me> (permalink) |
| References | <11069n1$3617t$1@dont-email.me> |
On 2026-06-08 11:40, clv2020 wrote: > > some years passed and now I would be interested to try Forth again. > > First question: Which Forth is used nowadays for PCs under Windows11? I > tried Win32Forth, ciForth and the old volksForth in an Oracle > VirtualBox. (gForth, bigForth, VFX, Swiftforth are too big for me for > the moment). What would you recommend? A small and modern Forth system that I like: Post4 <https://codeberg.org/SirWumpus/post4> However, at the moment, this system is not convenient enough when it comes to error reporting. I would like to recommend SP-Forth/4 (which I currently maintain), but at the moment, you need to manually rename "SPF.eng.ERR" to "SPF.ERR" in the "lib/" directory to make the system output error messages in English. This will be fixed in the next release. To obtain the bleeding edge executable, you need download sources and run "src/compile.bat". Ask me if you have any problem. <http://github.com/rufig/spf> > The second question: All Forth systems I tried showed critical virus > warnings from Google Chrome or Microsoft defender. Even an old > volksForth vf38141.arc - no modern archive utiliy could read this format > - was captured by Chrome. Win32Forth seems to be kidnapped on about each > start by the Defender. I'm not very amused to turn all IT security off > to use Forth. Is there a chance to solve this issue? > A reliable way is to build the executable file by yourself. Gforth can be build and used under WSL on Windows from a tarball; see the instruction at: <https://gforth.org/#:~:text=Build%20from%20Tarball> Aside from a number of dependencies and the lengthy build process, Gforth is quite user-friendly. -- Ruvim
Back to comp.lang.forth | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Back to the Forth Virus clv2020 <clv2020@vodafonemail.de> - 2026-06-08 13:40 +0200
Re: Back to the Forth Virus Jan Coombs <jan4etsept@murray-microft.co.uk> - 2026-06-08 13:16 +0100
Re: Back to the Forth Virus Ruvim <ruvim.pinka@gmail.com> - 2026-06-08 12:23 +0000
Re: Back to the Forth Virus Daniel Cerqueira <dan.list@lispclub.com> - 2026-06-08 13:56 +0100
Re: Back to the Forth Virus anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2026-06-08 15:40 +0000
Re: Back to the Forth Virus Daniel Cerqueira <dan.list@lispclub.com> - 2026-06-08 19:26 +0100
Re: Back to the Forth Virus anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2026-06-08 20:06 +0000
GForth reproducible builds (was Re: Back to the Forth Virus) Kragen Javier Sitaker <kragen@canonical.org> - 2026-09-02 14:40 -0300
Re: Back to the Forth Virus minforth <minforth@gmx.net> - 2026-06-09 01:01 +0200
Re: Back to the Forth Virus clv2020 <clv2020@vodafonemail.de> - 2026-06-10 13:13 +0200
Re: Back to the Forth Virus minforth <minforth@gmx.net> - 2026-06-11 10:01 +0200
Re: Back to the Forth Virus anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2026-06-11 17:28 +0000
Naming issues in create-does (was: Back to the Forth Virus) Ruvim <ruvim.pinka@gmail.com> - 2026-06-12 17:23 +0000
Re: Naming issues in create-does (was: Back to the Forth Virus) anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2026-06-12 17:52 +0000
Re: Naming issues in create-does (was: Back to the Forth Virus) anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2026-06-12 18:22 +0000
Re: Naming issues in create-does dxf <dxforth@gmail.com> - 2026-06-13 13:14 +1000
Re: Naming issues in create-does Ruvim <ruvim.pinka@gmail.com> - 2026-06-13 06:33 +0000
Re: Naming issues in create-does dxf <dxforth@gmail.com> - 2026-06-13 22:20 +1000
Re: Naming issues in create-does Ruvim <ruvim.pinka@gmail.com> - 2026-06-13 15:55 +0000
Re: Naming issues in create-does Ruvim <ruvim.pinka@gmail.com> - 2026-06-15 13:08 +0000
Re: Naming issues in create-does Hans Bezemer <the.beez.speaks@gmail.com> - 2026-07-23 19:58 +0200
Defining words in more than one step (was: Naming issues in create-does) anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2026-06-13 06:46 +0000
Re: Defining words in more than one step dxf <dxforth@gmail.com> - 2026-06-14 12:29 +1000
Re: Naming issues in create-does Ruvim <ruvim.pinka@gmail.com> - 2026-06-12 19:59 +0000
Re: Naming issues in create-does anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2026-06-13 10:25 +0000
Re: Naming issues in create-does Ruvim <ruvim.pinka@gmail.com> - 2026-06-13 15:30 +0000
Re: Naming issues in create-does anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2026-06-13 17:30 +0000
Re: Naming issues in create-does (was: Back to the Forth Virus) peter <peter.noreply@tin.it> - 2026-06-13 20:21 +0200
Re: Back to the Forth Virus dxf <dxforth@gmail.com> - 2026-06-09 12:14 +1000
Re: Back to the Forth Virus "Kerr-Mudd, John" <admin@127.0.0.1> - 2026-06-10 18:54 +0100
Re: Back to the Forth Virus dxf <dxforth@gmail.com> - 2026-06-11 16:32 +1000
Re: Back to the Forth Virus "Kerr-Mudd, John" <admin@127.0.0.1> - 2026-06-11 14:20 +0100
Re: Back to the Forth Virus Stephen Pelc <stephen@vfxforth.com> - 2026-06-09 10:22 +0000
Re: Back to the Forth Virus clv2020 <clv2020@vodafonemail.de> - 2026-06-10 15:55 +0200
Re: Back to the Forth Virus albert@SPENARNC.XS4ALL.NL - 2026-07-24 13:35 +0200
csiph-web