Alan,

Thanks for that bit. Even this Q&A are subject to different interpretation. My buisiness is building and testing VFP applications, so in a sense, pretty much all is related to Development and Testing. For example, my partipation on the UT is for testing and development purposes. In fact 90% of my internet trafic is related to development and business. So Can I be sued when MS catches me sending a general business E-Mail ? This makes no sense. If you're 100% strict about these rules, the MSDN package becomes worthless.

Does this mean that I cannot play a game of solitair when I have a dull moment ? Do I violate the license ? In a strict sense I do, but I think most people do agree this is not a problem. I own multiple Windows licenses for e.g. XP home, Window 2000, windows 98, Windows 95 and Windows NT 4.0. Most of my buisiness application not directly related to Development and Testing run from a Window 98 machine of which I own a NON-MSDN licences. So I'm O.K here.

But wait, My Windows 2000 server has a printer attached which I also use for NON - MSDN computers. I'm I violating the license ? To be honest, I don't care... Also, the W2K server acts as a router for all internet traffic whether it comes from a development PC or a Buisiness PC. And All PCs can login to Terminal Services to use the administrator account. I do not use the server for other general buisiness purposes, like running administrative software or using Exchange for an E-mail system, however. I could also install a LINUX server to do the same, but then again MS prohibits me in certain cases to use that server.

In a network with shared resources the whole licensing issue becomes very complex. And refuse to hire a lawyer to dig out my Licensing problems. It should have been clear at first sight.

>As much as I hate the licensing system, I do feel that if I've agreed to the license, I have, if nothing else, at least implied that I've read it. So I do read it. Do I always understand it? Probably not, and I may find myself unwittingly in violation due to interpretation differences, but I do try very hard to live up to the license.

I'm past that Line. Because of the language barrier, I often cannot figure out what is ment in detail. I do know that, I do own the appropriate licenses for what I'm doing. Since I'm the only developer and my business is about developing software and use the network for my business exclusively (O.K. I do send and recieve E-mails from friends occasionally), I Figure I'm allright. I don't care about each and every detail. I've got more important things to do than looking and solving that.

>I'm probably a dinosaur in that, and I hope with all my heart that MS will go so far over the line one day in their zeal to rule our lives that the legal system will finally step in and once and for all put an end to this nonsense.

>You mention that you have the MSDN - can I assume Universal? Well, I certainly hope you are not using your MSDN copy of Windows 2000 or XP on the computer that you use to send these messages. Since they are not directly involved with development and testing, you'd be in violation of your MSDN license.

I do have another interpretation than that, The use of the internet and the UT, is IMO directly related to developing software. If not, I agree I'm violating the license. I dont'feel much of installing other OSs (Windows 2000 workstation with Internet sharing, or going to Linux).

>This is from the MSDN Q&A on the MS website:
>
>

What do you mean by "production?" What are examples of test and development work?
>
>By "production" we mean any activity that is personal, for general business use,
>or not directly related to the testing and development of software applications.
>
>Examples of (prohibited) production use include:
>
>Installing Windows 98 to play games for entertainment.
>
>Installing Windows 2000 Server and Exchange Server to set up an e-mail system
>that you use to send personal and/or business-related e-mail.
>
>You may not use your MSDN Subscription as a substitute for purchasing a retail
>license for an operating system if you do more than develop and test on your
>computer.
>

>Pay particular attention to that last paragraph.

Again, this would say:

1. I may not play solitair in a dull moment.
2. I may send E-mails related to application development, but not to my friends
3. I may not let my wife write a small note in word.
4. I may not use my MSDN excell to make a TODO list unless its has to with development and testing.
5. I may not play a Music CD from my development PC because it has nothing to with Testing development.
6. I may surf to Sites related to Develpment and testing, but not to www.CNN.Com
7. I may not start the puzzle in VFP because it does not have anything to do with development.

Give me break. I'm in the opinion that these rules apply to another level than we are talking about. You may not use a MSDN licence to:

1. Run a business of multiple persons not related to software development or testing.
2. Have a large business application run on your SQL server.
3. Indeed, run Exchange as an E-mail system for more than one developer.
4. Use Office extensively for marketing stuff.
5. Use your Windows 2000 server for running business applications (other than you're developing) and as storage of business data.

IOW, This whole licensing thing is not a black or white thing. Even, if you're very strict, there are many things you do on your development machine that might violate the license.

Walter,