A little mentioning here, so that this thread doesn't scare some people sleepless. ;)

It's allways a security risc as long as something is connected to something else that reaches out of the inbound zone.

Full security is when the cords are cut off, or at least unplugged. ;)

If one where to compare security between for instance AmigaOS and Windows (because I know Windows since a long time). Even though Windows has a lot of programs and utilities for security, I think that AmigaOS is a lot more safe without anything.

Still, this can change over time.

The absolutely best solution is to connect through a firewall of some kind.

Browsers and mail is a potential risc, and has little to do with the operating system, so the problem is not so much AmigaOS. AmigaOS is not even close to Windows with all its inner connections by scripts to make things easy to use, but insecure as hell for beginners to handle. Even though I don't use AmigaOS 4, I don't think that even RoadShow has any of that potential riscs that Windows has. The greatest risc on the Amiga are the different 3rd party software that can be used and that's where the focus should be set.

Take care of a problem att the core - not it's symptoms in the operating system. That would be a good paroll for AmigaOS (and so far is, I think). Please don't demand that AmigaOS should have to use that armada of security programs that Windows has to use - that is only there for dampening symptoms, mostly not taking care of the problems.

Why should it be possible to delete files remote from a webserver on a client? Why should functions as this even be enabled, whithout the users knowledge? Microsoft claim that they do so because it makes things more easy. Maybe it was so in the beginning but today that ease of use demands a battery of software to cut some edge of the problems this ease of use was supposed to give.

Scripting is good and nice. Interconnections between different softwareres is powerful - up to a certain point. Windows is a great exampel of when this has gone long beyond that point a think. The user can easily do many things, but is (as a novice) not aware of the risc.

Luckily this is not the case with AmigaOS - mostly at least. And please let it stay that way. Don't demand a new Windows. Demand a light, powerful OS that makes it worthwhile to use instead of Windows. Do stuff the Amiga way.

Anyway, it's good that somebody is writing a guide to open the eyes of the potential risc of being connected to the internet. But please don't scare people.

I once got a virus on a Windows machine that started copying a mail all over that machine. Not long after that, it found a way to copy itself over Samba, to my Amiga. But as soon as i disconnected the Windows machine, the copying stopped - of course. The virus had no code to run on the Amiga.

This could very well happen on the Amiga in the future, so an open eye to the potential risc is good. A preparing for what to do if this becomes a reality is good.

I started using Basic on the C-64. I then went to Simon's Basic. Later I used Machine lightning and Basic lightning. I tried a couple of other languages too, like forth among a few others.

On the Amiga, I started with Amiga Basic and later I compiled my programs with ACE compiler. It made it more useful. I learned how to use the Amiga libraries with Amiga Basic.

Then I started using HiSoft DevPac (for assembler). A bit later then that I used Dice (a c-compiler).

After that I think I started using Blitz Basic 1.? and continued with Blitz until the last version. It's not supported since long time and is nowdays only available under Windows with a few different names for a little different approaches.

The coninuation of Blitz Basic on the Amiga, is AmiBlitz, which is bettter and free.

This Basic is not even closely like the old Basics, since it handles structures and procedures and other stuff, like c-compilers. It's even possible to imitate features from object oriented languages, like C++, Java and Ada, but not fully in any way.

Then you have Amos. The only version of Amos I think is really good, is Amos Professional. It allows you to make programs system friendly. I have allways problems with programs made in Amos - they doesn't start on my Amigas. I don't know why. But anything else works fine. Strange. But, I think that executables made in Amos Proffesional are fine.

Finally, I have one Basic to mention that I havn't seen yet in this thread. That's Pure Basic. It was developed until 2002 or smthng, and is at version 2.9? smthn atm.

It's a good and structured Basic, very much like AmiBlitz. It had a lot of potential, but with very weak support the Amiga version has stalled its progress towards new techniques like PPC and 3D.

However. This Basic is multi platform. It's available for Amiga (68k), Windows (x86), Linux (x86) and MacOS (PPC).

The Windows and Linux version are at version 4.01 atm and features a lot of fun stuff.

If only more Amigans would register, maybe that the Amiga version would develop to PPC and maybe even 3D.

The great thing is that I bought this Basic in 2000 or smthn for the Amiga, but I'm entitled to every new version to any new platform for the rest of my life. :) No use to pirate this software. I have even donated a little to show my appriciation for the project. And, yes. I'm mostly using the Windows version. :( *hiding in the shadows, defending myself with trying to make the amigaversion more popular*)

There are free test versions to download to try this Basic out before buying, and if one is to just see if Basic is something to use in the future.

But atm, from what's available for Classic, I would choose between AmiBlitz, Amos Professional and Pure Basic. Sorry that I don't mention GFA Basic, HiSoft Basic, but I think they are out of age, so to speak. Dunno if they support structures and assembler.

One thing that is very neat with AmiBlitz and Pure Basic, is that u can use assembler straight up in your Basic program. Very nice to make tight loops faster - if there is interest and need for it. Amos supports some assembler like instructions, but AmiBlitz and Pure Basic are like a more or less fully featured assembler. I know that Pure Basic has support for each and every version of 680x00 CPU. I don't know if AmiBlitz has this but I think there's support for FPU instructions - not sure though, since it's some time since I used Blitz/AmiBlitz.

A recommendation to learn a language. You can allways use books made for other platforms as long as they don't use external resources for that language. External resources are mostly stuff that is built into the operating system, but can also be other third party resources.

The overall techniques for programming are very much a like between languages and platforms.

One overall rule is to break down problems and start with the smallest pieces, building them together to what you need - like Lego. :) (if your not using Forth, which is a top down language, which brakes down a problem until you are at instruction level, then the program is ready)

A good thing to start learning a language is:
1. Observe the structure of the language.
2. Learn the mainly used structures - while/wend - if/then/else - for/to/next - etc. Find out how to print values to the screen and play with these structures until you feel familiar with them and understand when one structure is better to use than another (many are very much alike but with small differences).
3. Learn how varables work and learn the different datatypes and what they are good for.
4. Learn how to use structures.
5. Learn how to use linked structures.
6. Maybe even learn how to make objects and handlers (if you are into learning som object oriented programming - good for greater projects and projects involving many programmers). Also good for making code that is rather easily upgraded in the future - but can have a drawback of more preparing and slightly slower code, but not nescessarily.
7. Learn each and every feature library in the language (if the language has any). In Blitz/AmiBlitz/Pure/Amos there are many libraries for different stuff like timers/sprites/windows/gadgets/appgadgets/arexx-ports and so on.
8. Learn how to use external resources. Here's is when you get total control over your machine and can use what ever you like when ever you need it. Full power to the programmer. :D

Good luck!

(ps. I havn't mentioned ARexx as a programming language because it's more ment to be a scripting language for connecting different applications with each other. Of course it's possible to write programs with ARexx - even with advanced GUI-systems like MUI, but it's not as straight forward as basic or c is, even though it's easier than assembler. It's also just interpreted, and therefor very slow. The other Basics I have mentioned, C, assembler or any many other languages, are compiled before executing, making them allmost as fast as assembler in many cases. Not allways though, but for the most it's enough.)

Sorry, for my long answer, and sorry if my english isn't perhaps the best. I'm much more used to listen and read then to write english.