Thank you guys, for all your answers, there were very helpful for me. I decided that I will try to find job as cpp programmer and, if someone will hire me, to survive in a company. Also, as a side project, I'm starting to learn more easier and modern language. Thank you once again. It's great to have opportunity to advise older colleagues.

Sounds like Nokia Siemens. What you need to study for the test is probably not what you need for the interview. One of the best parts of this job requirements list; it is short. They have something specific in mind and they aren't looking for a long list of specifications. It's probably some very narrow project that's long-term. The worst part; big companies often like to use a form of standardized test, rather than just interviews, to resolve your placement. So even if the job doesn't require it they might well ask you what an RDBMS is or some sql questions. They might ask you to debug or show the output to a very simple program. They might ask you some basic questions about the difference between Windows and Unix. You're probably stuck working with the knowledge you have. Of course it doesn't hurt to bone up on some things. And it wouldn't kill you to treat this as a practice test. Since this is a test it will probably be in two parts; the first section would then be aptitude/IQ and the second will be domain specific. In that, you might be asked about specific acronyms. It should be mostly book learning rather than real experience. Make sure you know the OSI layer model and can write it out from memory. No serious details, just the order and approximate meaning of each layer. Revise (just guessing): -overloading operators -semaphores (how are they different) -zombie processes in unix -linked lists, trees, and the like -difference between a router and a bridge -pointers, arrays -how is a keystroke interpreted in windows Do not study too deeply into any of these unless you have a lot of time. They probably will want to know if you understand the basics of a lot of things and won't check for depth on too many. Use your testing skills; figure out the rules of the test (mark for wrong answers the same as non-answer or different? How much time to get all the questions done divided by how many questions?) All of the above is based on a lot of assumptions based on your comments to the others, so it might amount to a pile of crap when you walk in to the test. But you asked what we thought, and this is what I think you are headed for instead of a test for the very job for which you are applying. Then you'd want some other set of things for the actual interview. I'd read articles based on your keywords and be able to answer questions about why C versus C++ in embedded systems and things like that. Maybe see if you can get a download of VxWorks and p

It's a problem with the Kubuntu detecting to the generic monitor resolution, many monitors have the same problem with LINUX systems on physical machines. If you are using virtualbox install guest additions, Ubuntu pretty much scales to the host window (there might have been some minor fettling to add the screen resolutions below, I can't remember). Even without guest additions, adding the required monitor resolution you want to your xorg.conf file will fix your problem (at least there is a graphical interface now). Instructions here: http://www.internetspotter.com/2008/08/12/setting-your-screen-resolution-in-kubuntu-hardy/[^] Sort of a cross between Lawrence of Arabia and Dilbert.[^] -Or- A Dead ringer for Kate Winslett[^]

First of all, there isn't as big difference performancewise between those disks as you might think. The velociraptor has only a slightly higher sustained datarate, and if you would consider the 1.5 TB Caviar, it's even slower. But the latency is 30% lower. It's also serverclass when it comes to reliability, which the caviar certainly isn't. So it's more about how you're going to use the drives that makes the difference. If you read or write very large contiguous files in one go, the raid system is the clear winner. But if you read or write very many small files, then the single velociraptor will be the better choice. Also keep in mind that a cheap raid controller isn't fast. Check the sustained write speed if available. If you really want a fast system, you should consider one of these[^] instead. List of common misconceptions

vonpik wrote: So, you are saying that default...size of stack size is 1 MB? Yes. vonpik wrote: I solved this problem with using vector, Which gets its memory from the heap, not the stack. "One man's wage rise is another man's price increase." - Harold Wilson "Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons "Man who follows car will be exhausted." - Confucius