nein,don't put words in my mouth, i said i worked with java ^^ (in a windows enviroment) for 1 semester at uni. enough to do an extremely simple graphical blackjack game. Most of it forgotten by now (more than a year ago)
i want to learn python, so i'm starting to read some stuff. But useful GTK stuff still look like nuclear physics to me...

My error, I missed read your post I should of wrote java not python.

No not very geeky indeed Dos is rather useless for windows, i mostly use it when configuring Networks (ipconfig). It is nowhere near the utility of a terminal in linux, i think. Most windows user don't get nowhere near DOS. I don't worry much since all this stuff gets teached in courses i have to take later on on university, but getting an early start wouldn't hurt.

As a system administrator of an AD with 3k+ workstations i hit dos every day. Batch scripting can be one of the easiest ways for batch procesing, startup/login/administartion scripts in vbs, hta, batch... using runas with options and parameters not available in the gui.. using template .reg files that already have the path i want to get to in them.. i just change a key and value or whatever.. without spending the 10 minutes navigating that hack of a gui regedit...

and I hate windows. But there is still stuff you need dos for when u do real advanced work.

CLI is still the fastest and easiest way to do a lot of stuff on any OS...once u learn it.

I think yours would be an exceptional case, most the people i know even if they like computers dont mess much with the cmd. talking about my enviroment, maybe different for other people. Well i think this thread has gotten a bit off topic ^^, so i'll repeat my salute to all the users here. cheers

<sigh /> Common misconception, which I am compelled to correct about every third time I see it; nothing personal, just been about enough of them, so here goes:

shell != terminal
While in Windows, they are in fact the same (a terminal emulator is implemented in the shell, cmd.exe), that's really bad architecture in general.

Terminal emulators and shells are, and of right ought to be, mix-and-match; that said, practically any terminal or shell available on the N800 is more capable than the equivalent functionality in cmd.exe, so your statement would up being true, but an understanding of the way things really work helps a lot.

In Linux, and UNIX in general, a shell generally runs on a tty (in the sense of a character device), which could be a serial line to a hardcopy terminal, a glass terminal, a virtual console on the machine's console, or a pty; from a pty, you could have a screen session, a telnet/ssh/whatever link, or a terminal emulator at the other end. A shell can even run noninteractively, with input and output only to regular files.

so i had it backwards? XD In this forums i really am learning new stuff everyday. Thanks for the explanation, i am not too versed in the OS ways...I will learn i promise, just don't know how long will it take.