hi there! i've been learning C++ for last 2 years and i know basic but i really want to know assembly too. any nice guides or books to use to learn from basics (i know nothing currently about asm). thankyou

I've installed it on a PII 400 with 64 Mb and I could hardly use it. Installed it on my main machine - PIII 650 with 256 Mb and it was just about usable, but some things were pathetically slow, like searching Help - that took over 2 mins to search for something. The new interface also seems rather slow. Berkut

Yeah - I've played guitar for 11 years, since I was 8, and I get hand cramp when playing bar chords for ages - I normally resort to first positions chords. No problem with anything else though, but I did have trouble with the Cello for the same reason - hand cramp. I've been using computers since I was around 7, so it could be something to do with RSI. Berkut

Yeah, I play the guitar (electric and acustic) there aren't any grades, a bit of Bass Guitar, Piano (grade 4 UK) and used to play the Cello (grade 4). Berkut

AccessCheckByTypeResultListAndAuditAlarm BuildImpersonateExplicitAccessWithName ConvertToAutoInheritPrivateObjectSecurity Some of the DirectX ones a quite interesting too. Berkut

> do you mean builds ? I was under the impression that debug build gave more info out about how you code works > then in release because each line is as you wrote it and not optimised. when I step into a release (with debug info) > build the code sometimes jumps back and forth between the lines as the compiler has optimised the code Yes. Debug build encodes in extra information that allows the debugger to understand what's going on in C++ (or whatever language you're using), so you can trace and make breakpoints easily referencing the code. But debuggers like softice (and even debug.exe that comes with windows NT) can debug Release build .exes, because they do it by machine code (assembly), because this is the language the operating system and computer understand. It's not as easy to debug this way - you have to know ASM, but it's still just as possible to set a break point in the same place, and even trace and run step-by-step as long as you know what you're looking for. You can even set break points whenever the program calls an API call, or a C runtime function. Berkut

LOL! Yeah, I've been using those funny //, /*, */ combinations much more recently . I thought about submitting an article or demo about this, but on seconds thoughts, I don't want to give crackers instructions to crack my programs - I know - selfish ;p. Berkut

Go over to www.fravia.org and have a look there. There are lots of lessons there, and also some pages on protection against crackers. The thing to remember is, anything you put in in way of protection, can easily be removed, bypassed or ignored by cracking, simply because most crackers know ASM assembly very well, and therefore using dissasemberlers , can know exactly what your program is doing, almost like them having the source code. *DO NOT HARD CODE ANY KEY OR ANYTHING* in a program - if you're going to do this, at least encrypt it (not just XOR or character swapping). This will make it much harder. Adding threads and timers also annoys crackers and makes it much harder to crack, especially using debuggers like softice. The best protection I've found - but it's not a safe method, is to use code that does work, but shouldn't - e.g., code that works in Release, but not debug. This basically means that debugging it won't work. I put a shareware program out about 1 1/2 years ago, and fairly soon it got cracked, and keygens were made for it. I completely re-wrote the protection and encryption in the next version, but it was still cracked. Purely by mistake, the version after that would not run in Debug mode - it hasn't been cracked or keygened for almost a year, since I left that code in - it makes debugging hard - I have to remove protection code - but it seems to work. Berkut

Hi, You can do it by changing the members of your CFileDialog before calling DoModal() : CFileDialog(TRUE, .......); dlg.m_ofn = ... if (dlg.DoModal() == IDOK) { // Do Open thing here } Hope this helps, Berkut

The only problem with getting people to click the OK button which says "Dear User, we have detected that you may be breaking the law. Please can you send the information required to prosecute you to us by choosing the ok button below.", is that they are incriminating themselves. As the relatively recents human rights court cases here in the UK regarding the letters people get sent after being caught by speed cameras asking them to state it was them driving - and thereby incriminating themselves - shows, it is against their human rights (for some strange reason.).

how can i put a tab at the bottom of view (over status bar) which allows to change view - like frontpage (Editor / HTML / Preview). thankyou berkut