I disagree. When people post thanks, other people know that the solution posted actually *works*. This is important. When people search the messageboard for an answer it really, really, helps if the answer provided has helped somebody before. It can be very frustrating to follow somebody's advice only to find out later it could not possibly solve your problem. By saying 'thank you' you're not only being polite - you also save other people's time by confirming the solution's effectiveness. If you came up with another solution to the problem then that's worth posting too.

I solved the problem - it didn't have to do with dual monitors. For some reason, the problem was caused by a typo in one of the source files I was editing in VS - intellisense got upset. I thought it had to do with dual monitors because I had one cpp file open on one monitor, and one on the other. So at the same time I made a typo in the source code and I made the window span both monitors... I did all testing afterward with the same files (and in the same arrangement), so every test I did confirmed my dual monitor hypothesis. Anyway, thanks for the effort Jeffry.

I'm using the most recent NVidia drivers and a 5600 ultra vid card. (One digital out, one analog.) But I doubt my video card is to blame, all other applications work fine on both monitors - it's just visual studio that lets me down.

Not long ago I bought a second monitor, but VS 2005 doesn't seem to like it one bit. If I maximize VS in either of the two monitors it works just fine. If I maximize VS to cover both monitors entirely (I want to use both monitors so I can use "Vertical tab groups" to have several files visible at the same time) the application becomes unresponsive, but only on the PRIMARY monitor. I can write code just fine on my secondary monitor, everything's smooth, including code completion and visual assist tips. On the primary monitor my CPU spikes to 100% for roughly 5 seconds for every keypress. Does anybody know of a quick fix? Thanks a million!

"Do whatever you want with it just don't blame us if it breaks anything." That's pretty much what the MIT license is. The BSD license is quite similar. http://en.wikipedia.org/wiki/MIT_License[^] So yes, building Rugby on Rails would be allowed *if* you don't claim it's endorsed and/or written by the current RoR developers. I'm not sure about the name though - because Rugby/Ruby is so similar endorsement may be implied. Then again, IANAL.

Okay, this is how a dynamic language would solve the problem: irb(main):003:0> "sys.fun.bar::foo.blah".gsub( /\.|::/, '`\0`' ).split /`/ => ["sys", ".", "fun", ".", "bar", "::", "foo", ".", "blah"] For those who don't know the language - it's Ruby. Admittedly, the code may be a tad obfuscated, but it sure is a lot easier to grok than an entire page of C# code! Cheers, Diederik

NDoc[^] is probably what you want. Works like a charm.

It looks like this license is similar to the one of the often praised PDF format. You're allowed to write software that supports the format and the specs of the format are readily available, but extending the document is prohibited. At least this way you don't get incompatibilities between versions of the XML Office format. If everybody's allowed to write software that uses the format then lock-in is almost impossible. And if the specs are available the 3rd party software can be 100% compatible, which is a big improvement.

PHP, although pretty nice has a few downsides: (1) poor unicode support and (2) it's not a very productive language due to the lack of standard components. Also, it doesn't encourage a separation of code and HTML, but with a bit of discipline that's no problem. ASP.NET is very nice, productive and easy to get started with. And you get to use Visual Studio. If you want to be as productive as possible you should check out RoR. It's still in beta, and it's not very well documented but it's nonetheless very impressive. http://www.rubyonrails.org/[^] Watch the movie in which somebody creates a functional blog in approximately 30 minutes. Regards, Diederik

As far as I can tell, no, he does not have the right. Saying "Do this or I won't pay you" sounds an awful lot like extortion to me. However, in a situation like this there is very little you can do about it. If you don't have the means to get real legal advice then you should aim for a compromise. Ask him -why- he wants ownership of the software you wrote. If he's willing to settle for shared ownership (i.e. both parties are allowed to do with the software whatever they like, so he can't get in trouble for doing something with software which partially belongs to you) you haven't really lost anything. Reference: [ Dutch page, official source on copyright matters - www.auteursrecht.nl[^] ] You can contact this institution of authorship and they will answer any legal questions you have for free. (They may need up to 3 weeks for an answer, according to the website) I'm not a lawyer and I don't know the details of the situation you're in, so take my advice with a grain of salt. Good luck! Diederik

If you are an employee copyright (even though it doesn't exist as such in the Netherlands) is automatically transfered to the company you work for. If you work as a contractor/consultant you keep the copyright on the software you write. This only applies, of course, if nothing is mentioned regarding copyright in the contract. Regards, Diederik

I'll let the solution speak for itself: (Using Haskell set logic) solution :: [(Int, Int)] solution = [ (apples, oranges) | apples <- [0..100], oranges <- [0..100], apples * 29 + oranges * 39 == 1999 ] Result:

[(38,23)]

Hence, the answer must be 38 apples. Haskell really shines sometimes. I don't think solutions really get more elegant than this. :-D

It's said that Microsoft's interviewing strategy changed significantly in the course of the last few years; the whole 'How do I move mount Fujji?' case seems a thing of the past. I recommend watching these movies: (Zoe Goldring and Gretchen Ledgard - What is it like to interview at Microsoft? - not even a year old) http://channel9.msdn.com/ShowPost.aspx?PostID=18472[^] And: (Gary Daniels and Evan Goldring - Mock whiteboard problem) http://channel9.msdn.com/ShowPost.aspx?PostID=19350[^] According to those videos and the interviewers themselves you can expect a whiteboard problem if you apply for a technical position. Good luck!

My computer --> Properties --> Advanced --> Settings (Startup and recovery) --> click on Edit. A notepad window will open with your boot.ini, if available. Good luck!

No offence taken. Unless people address me personally I won't take it personally. When somebody says 'soccer hooligans suck' you always see ten or so people jumping up from their chairs saying: "I like soccer but I'm not a hooligan!!". Not quite the same situation, but people often feel personally addressed when the statement is just a generalization derived from an observation. Colin Angus Mackay wrote: It depends how often people tell you that Exactly! Anything becomes annoying when it's said often, even if it's an innocent remark when seen as an independent incident. Which is why the Dutch newspapers work on my nerves lately, they keep repeating the same thing over and over: "immigrants are bad, etc, etc". It's not productive, they're just creating friction between the Dutch and the immigrants. And even worse, because of the bad light they cast on some ethnicities even those who are only similar in appearance to immigrants are treated as such. Bwech. Anyway, best stop ranting now.

I've read these message boards for several years now, but I've completely avoided posting in the Soapbox. Today, I'll make an exception because I'm Dutch (particularly from North Brabant). Firstly, I consider the terms 'The Netherlands' and 'Holland' equivalent. I've never heard of anybody feeling insulted by the term 'Hollander'. I prefer being called a 'Dutchman/Nederlander', but it's just a matter of taste. Your post was a bit of an eye-opener for me, because I'm guilty too of calling all the inhabitants of the United Kingdom English. The term 'Brits' is used only very rarely, everybody living in the UK is erroneously considered 'Engels' by us. If I write in English, I do make the distinction between the British and the English. And if somebody labelled me a German I'd politely tell him/her I live in a country just next to it and that I prefer to be called Dutch. I certainly wouldn't feel offended. A bit of cultural disenfranchisement.. so what? You English folk should lighten up. ;)

Naturally, but the power supply itself suddenly receives 5V on the ground. Because several different components are connected to the same ground (I assume) the power supply has to guarantee that the other components get enough juice even though the ground has 5 volt going through it. I don't know the how, what and why, but it just doesn't seem healthy to me. Then again, the ground of the PSU is connected to the ground of the fuse box (?) therefore it shouldn't really matter. Hmm. I never claimed it was bad for the fan, I claimed it might be bad for the PSU. Now it looks like it's just a minor short-circuit, which probably can't do any harm at all.

Ordinarily only the speed of the CPU and one other fan on the Motherboard can be speed controlled. The fans you connect directly to the power supply will always run at 12 volts. Unless, of course, you swap the 12 and 5 volt wire. Decent fans work just fine when they get only 5 volt and become nigh inaudible. Some websites suggest using the 12V wire as +, and the 5V wire as ground. This does result in a nice 7V difference, but your power supply might not like to too much. This solution doesn't cost anything, and it's guaranteed to work. When you want to build a silent PC it's important to remember that having a second element making the same amount of noise as the first one only result in a 3Db increase. Whereas the noise made by a fan running at higher voltages increases far more rapidly.

I think I've had the same problem once. I fixed my problem by adding a 'location'. Control panel -> 'Phone and location options' -> new

Have you tried deleting the project's ncb file? That may fix it.