Slashdot Mirror

Unreality's hands-on UT2003 preview April 17-2002 by Preacher Last weekend I got an invite to come to London for a game or 50 of Unreal Tournament 2003. Mark Rein sent me a mail sunday, saying I could come by monday for the test. Not only did I break a toe last week, but it woulda been impossible for me to go with such short notice anyway, so I did the second best thing. I decided to ask an english guy if he wanted the job. Luckily eVOLVE was at hand in our chatroom (#unreality on EnterTheGame), and he was more than happy to have a go at the game. (Lucky bastid) I sent him off with orders to wear something sassy, plus wink a lot to Jay Wilbur and Mark Rein, oh, and to get a lot of info. This is what he delivered to me earlier today: (Mark Rein promised us he would send along a shot or two from the game, and we will be posting them as soon as they arrive) Unreal Tournament 2003 - Hands-on Preview I never really enjoyed the previous Unreal games... Well actually I did, but I felt that Unreal Tournament 2003 is so shockingly great that you needed a smaller shock to soften the blow. Yes, that's true, on behalf of Unreality I was invited to a private room in a cybercafe somewhere near London to view and play UT2003. And you better believe it was worth it. For those of you who don't already know, UT2003 is the next planned release in the Unreal game series, intended as a kind of sequel to Unreal Tournament, and providing the multiplayer aspect to the series. Where UT had 5 player models to choose from out of the box, UT2003 will have almost ten times as many. Where UT had a pretty liberal poly limit, UT2003 has on average 100 times as high a limit. How is this possible using what is basically an enhanced version of the engine? Well, we'll get onto that later... Lets start with what really matters, the gameplay.

Unreality's hands-on UT2003 preview April 17-2002 by Preacher Last weekend I got an invite to come to London for a game or 50 of Unreal Tournament 2003. Mark Rein sent me a mail sunday, saying I could come by monday for the test. Not only did I break a toe last week, but it woulda been impossible for me to go with such short notice anyway, so I did the second best thing. I decided to ask an english guy if he wanted the job. Luckily eVOLVE was at hand in our chatroom (#unreality on EnterTheGame), and he was more than happy to have a go at the game. (Lucky bastid) I sent him off with orders to wear something sassy, plus wink a lot to Jay Wilbur and Mark Rein, oh, and to get a lot of info. This is what he delivered to me earlier today: (Mark Rein promised us he would send along a shot or two from the game, and we will be posting them as soon as they arrive) Unreal Tournament 2003 - Hands-on Preview I never really enjoyed the previous Unreal games... Well actually I did, but I felt that Unreal Tournament 2003 is so shockingly great that you needed a smaller shock to soften the blow. Yes, that's true, on behalf of Unreality I was invited to a private room in a cybercafe somewhere near London to view and play UT2003. And you better believe it was worth it. For those of you who don't already know, UT2003 is the next planned release in the Unreal game series, intended as a kind of sequel to Unreal Tournament, and providing the multiplayer aspect to the series. Where UT had 5 player models to choose from out of the box, UT2003 will have almost ten times as many. Where UT had a pretty liberal poly limit, UT2003 has on average 100 times as high a limit. How is this possible using what is basically an enhanced version of the engine? Well, we'll get onto that later... Lets start with what really matters, the gameplay.

Unreality's hands-on UT2003 preview April 17-2002 by Preacher Last weekend I got an invite to come to London for a game or 50 of Unreal Tournament 2003. Mark Rein sent me a mail sunday, saying I could come by monday for the test. Not only did I break a toe last week, but it woulda been impossible for me to go with such short notice anyway, so I did the second best thing. I decided to ask an english guy if he wanted the job. Luckily eVOLVE was at hand in our chatroom (#unreality on EnterTheGame), and he was more than happy to have a go at the game. (Lucky bastid) I sent him off with orders to wear something sassy, plus wink a lot to Jay Wilbur and Mark Rein, oh, and to get a lot of info. This is what he delivered to me earlier today: (Mark Rein promised us he would send along a shot or two from the game, and we will be posting them as soon as they arrive) Unreal Tournament 2003 - Hands-on Preview I never really enjoyed the previous Unreal games... Well actually I did, but I felt that Unreal Tournament 2003 is so shockingly great that you needed a smaller shock to soften the blow. Yes, that's true, on behalf of Unreality I was invited to a private room in a cybercafe somewhere near London to view and play UT2003. And you better believe it was worth it. For those of you who don't already know, UT2003 is the next planned release in the Unreal game series, intended as a kind of sequel to Unreal Tournament, and providing the multiplayer aspect to the series. Where UT had 5 player models to choose from out of the box, UT2003 will have almost ten times as many. Where UT had a pretty liberal poly limit, UT2003 has on average 100 times as high a limit. How is this possible using what is basically an enhanced version of the engine? Well, we'll get onto that later... Lets start with what really matters, the gameplay.

Unreality's hands-on UT2003 preview April 17-2002 by Preacher Last weekend I got an invite to come to London for a game or 50 of Unreal Tournament 2003. Mark Rein sent me a mail sunday, saying I could come by monday for the test. Not only did I break a toe last week, but it woulda been impossible for me to go with such short notice anyway, so I did the second best thing. I decided to ask an english guy if he wanted the job. Luckily eVOLVE was at hand in our chatroom (#unreality on EnterTheGame), and he was more than happy to have a go at the game. (Lucky bastid) I sent him off with orders to wear something sassy, plus wink a lot to Jay Wilbur and Mark Rein, oh, and to get a lot of info. This is what he delivered to me earlier today: (Mark Rein promised us he would send along a shot or two from the game, and we will be posting them as soon as they arrive) Unreal Tournament 2003 - Hands-on Preview I never really enjoyed the previous Unreal games... Well actually I did, but I felt that Unreal Tournament 2003 is so shockingly great that you needed a smaller shock to soften the blow. Yes, that's true, on behalf of Unreality I was invited to a private room in a cybercafe somewhere near London to view and play UT2003. And you better believe it was worth it. For those of you who don't already know, UT2003 is the next planned release in the Unreal game series, intended as a kind of sequel to Unreal Tournament, and providing the multiplayer aspect to the series. Where UT had 5 player models to choose from out of the box, UT2003 will have almost ten times as many. Where UT had a pretty liberal poly limit, UT2003 has on average 100 times as high a limit. How is this possible using what is basically an enhanced version of the engine? Well, we'll get onto that later... Lets start with what really matters, the gameplay.

Unreality's hands-on UT2003 preview April 17-2002 by Preacher Last weekend I got an invite to come to London for a game or 50 of Unreal Tournament 2003. Mark Rein sent me a mail sunday, saying I could come by monday for the test. Not only did I break a toe last week, but it woulda been impossible for me to go with such short notice anyway, so I did the second best thing. I decided to ask an english guy if he wanted the job. Luckily eVOLVE was at hand in our chatroom (#unreality on EnterTheGame), and he was more than happy to have a go at the game. (Lucky bastid) I sent him off with orders to wear something sassy, plus wink a lot to Jay Wilbur and Mark Rein, oh, and to get a lot of info. This is what he delivered to me earlier today: (Mark Rein promised us he would send along a shot or two from the game, and we will be posting them as soon as they arrive) Unreal Tournament 2003 - Hands-on Preview I never really enjoyed the previous Unreal games... Well actually I did, but I felt that Unreal Tournament 2003 is so shockingly great that you needed a smaller shock to soften the blow. Yes, that's true, on behalf of Unreality I was invited to a private room in a cybercafe somewhere near London to view and play UT2003. And you better believe it was worth it. For those of you who don't already know, UT2003 is the next planned release in the Unreal game series, intended as a kind of sequel to Unreal Tournament, and providing the multiplayer aspect to the series. Where UT had 5 player models to choose from out of the box, UT2003 will have almost ten times as many. Where UT had a pretty liberal poly limit, UT2003 has on average 100 times as high a limit. How is this possible using what is basically an enhanced version of the engine? Well, we'll get onto that later... Lets start with what really matters, the gameplay.

Unreality's hands-on UT2003 preview April 17-2002 by Preacher Last weekend I got an invite to come to London for a game or 50 of Unreal Tournament 2003. Mark Rein sent me a mail sunday, saying I could come by monday for the test. Not only did I break a toe last week, but it woulda been impossible for me to go with such short notice anyway, so I did the second best thing. I decided to ask an english guy if he wanted the job. Luckily eVOLVE was at hand in our chatroom (#unreality on EnterTheGame), and he was more than happy to have a go at the game. (Lucky bastid) I sent him off with orders to wear something sassy, plus wink a lot to Jay Wilbur and Mark Rein, oh, and to get a lot of info. This is what he delivered to me earlier today: (Mark Rein promised us he would send along a shot or two from the game, and we will be posting them as soon as they arrive) Unreal Tournament 2003 - Hands-on Preview I never really enjoyed the previous Unreal games... Well actually I did, but I felt that Unreal Tournament 2003 is so shockingly great that you needed a smaller shock to soften the blow. Yes, that's true, on behalf of Unreality I was invited to a private room in a cybercafe somewhere near London to view and play UT2003. And you better believe it was worth it. For those of you who don't already know, UT2003 is the next planned release in the Unreal game series, intended as a kind of sequel to Unreal Tournament, and providing the multiplayer aspect to the series. Where UT had 5 player models to choose from out of the box, UT2003 will have almost ten times as many. Where UT had a pretty liberal poly limit, UT2003 has on average 100 times as high a limit. How is this possible using what is basically an enhanced version of the engine? Well, we'll get onto that later... Lets start with what really matters, the gameplay.

Unreality's hands-on UT2003 preview April 17-2002 by Preacher Last weekend I got an invite to come to London for a game or 50 of Unreal Tournament 2003. Mark Rein sent me a mail sunday, saying I could come by monday for the test. Not only did I break a toe last week, but it woulda been impossible for me to go with such short notice anyway, so I did the second best thing. I decided to ask an english guy if he wanted the job. Luckily eVOLVE was at hand in our chatroom (#unreality on EnterTheGame), and he was more than happy to have a go at the game. (Lucky bastid) I sent him off with orders to wear something sassy, plus wink a lot to Jay Wilbur and Mark Rein, oh, and to get a lot of info. This is what he delivered to me earlier today: (Mark Rein promised us he would send along a shot or two from the game, and we will be posting them as soon as they arrive) Unreal Tournament 2003 - Hands-on Preview I never really enjoyed the previous Unreal games... Well actually I did, but I felt that Unreal Tournament 2003 is so shockingly great that you needed a smaller shock to soften the blow. Yes, that's true, on behalf of Unreality I was invited to a private room in a cybercafe somewhere near London to view and play UT2003. And you better believe it was worth it. For those of you who don't already know, UT2003 is the next planned release in the Unreal game series, intended as a kind of sequel to Unreal Tournament, and providing the multiplayer aspect to the series. Where UT had 5 player models to choose from out of the box, UT2003 will have almost ten times as many. Where UT had a pretty liberal poly limit, UT2003 has on average 100 times as high a limit. How is this possible using what is basically an enhanced version of the engine? Well, we'll get onto that later... Lets start with what really matters, the gameplay.

Perhaps I knew here: http://www.dictionary.com/search?q=irony

This is more of a general rant than about the specifics of this case, but since the discussion has veered into general free speech issues, I think it's appropriate.

Thanks to the DMCA and similar restrictions, publishing information on cracking dongles (hardware keys for software) is basically illegal. Concrete details on how to crack a dongle definately is. The people putting up information on cracking dongles usually do so for the sole purpose of encouraging others to use illegal copies of software. Clearly the dominant use of this information is criminal.

So what's the harm in censoring this speech?

Well, several years ago I was asked to investigate adding copy protection to a new software product (now defunct). My initial research focused on "respectable" publications on the subject. I found almost nothing useful. If the information I found was to be believed, dongles were practically impossible to defeat. So I extended my search to cracker sites. Now I found something. I discovered that all dongle technologies have been defeated on a case by case basis. I discovered which dongle technologies were trivial to defeat and which were very hard to defeat. I learned specific, concrete weaknesses and arguments for and against dongles. With this information I was able to provide solid information for my employers to use to make a decision.

Let's say that the information on dongle cracking had been removed from the web. Well, my research would have been mostly fruitless. I would have had to largely rely on the misleading claims of the manufacturers themselves and reviews that didn't make serious attempts to defeat the dongles. However, the crackers would still have access to the information, passed around via instant messaging, password protected ftp, email, and other techniques. Dongles would still be insecure, but I wouldn't be able to make reasoned decisions about them.

Actually, I meant it the way it was spelled. And now that I look at it, dictionary.com has different ideas about what pablum and pabulum mean. But I meant insipid, yes.

In reply to the content of your comment: I'm not too great on my NT security, but I understand (from my own experimentation) that IE (at least parts of it) runs in the "system" context under win2k. Is this true? Does anyone care to explain why this is necessary? Why does it require elevated privileges?

I dunno. The last MS OS I actually installed and used for any length of time was Windows98SE. I've used Win2k and XP very briefly, and I had an NT4 machine at work for a while. So I'll have to guess:

Since IE is "part" of the OS, it must be able to interact with various underlying system calls outside the confines of any normal security model? Some Win32 pigs are more equal than others? Surely MS gives other developers similar hooks through their DevNet program...

-B

Actually, I meant it the way it was spelled. And now that I look at it, dictionary.com has different ideas about what pablum and pabulum mean. But I meant insipid, yes.

In reply to the content of your comment: I'm not too great on my NT security, but I understand (from my own experimentation) that IE (at least parts of it) runs in the "system" context under win2k. Is this true? Does anyone care to explain why this is necessary? Why does it require elevated privileges?

I dunno. The last MS OS I actually installed and used for any length of time was Windows98SE. I've used Win2k and XP very briefly, and I had an NT4 machine at work for a while. So I'll have to guess:

Since IE is "part" of the OS, it must be able to interact with various underlying system calls outside the confines of any normal security model? Some Win32 pigs are more equal than others? Surely MS gives other developers similar hooks through their DevNet program...

-B

>It's clear that the reason MSIE's 5 and 5.5 are losing users is becasue they're upgrading to 6.0. The "others" line on the chart has remained fairly constant.

Pffft. That's a load. The chart clearly shows a heavy decline and here's proof of it.

You don't say...

(You figuring it out yet?)

Yup.

What exactly IS a god/deity anyway? I know some AC will tell me to look it up, but there really isn't a coherent definition of what a "deity" is. Specifically, if you ask a Christian, a Hindu and a person who practices Chinese religion, you will get totally different definitions.

The most common pseudo-definition which tries to avoid most (though not all!) of these pitfalls bizarrely compares a "deity" with a human who lives right now. The critical problem with that position is that, if a person could go back in time with all the technology we have today, at some point in history, she would be called a goddess.

Nope. Sarcasm assumes irony. Check the definition. Calling someone a sniveling twit is only sarcastic if you have a high opinion of them, but they prefer that you didn't, which is a farly rare situation, I would guess.

That reminds me of the bar in my University halls in my first year, that insisted on the name "skiff" for the plastic pint "glasses" that beer was served in.

And there was me thinking a skiff was a boat.

I'll tell you, getting served beer in a real glass after a couple of years of the plastic monstrocities makes you really appreciate being in a proper pub :o)

Royalty-Free CIFS Technical Reference License Agreement This is a legal agreement ("Agreement") between the undersigned (either an individual or an entity) ("You" or "Company"), and Microsoft Corporation ("Microsoft"). The CIFS Technical Reference (as defined below) is available for You to reference, but if You want to implement the Technical Reference, You must sign and return this Agreement AS IS. This is an offer to be accepted only on the terms set forth in this Agreement. If You make any changes to this Agreement, the offer is revoked. RECITALS Whereas, the industry has requested that Microsoft set forth its license terms for CIFS (as defined below); Whereas, Microsoft is now setting forth those terms by making a license available. 1. Definitions 1.1 "CIFS" shall mean the common internet file system communication protocol described in the Technical Reference. 1.2 "Company Implementation" shall mean only those portions of the software developed by Company that implement CIFS for use on Non-Microsoft Platforms. 1.3 "End User" shall mean a third party customer or potential customer to whom a copy of Company Implementation is licensed, delivered, or otherwise provided primarily for such customer's or potential customer's use, and not for further sublicense or distribution. 1.4 "IPR Impairing License" shall mean the GNU General Public License, the GNU Lesser/Library General Public License, and any license that requires in any instance that other software distributed with software subject to such license (a) be disclosed and distributed in source code form; (b) be licensed for purposes of making derivative works; or (c) be redistributable at no charge. 1.5 "Non-Microsoft Platforms" shall mean any platform other than any version of a Microsoft client, embedded and server operating system product, including without limitation, Windows XP, Windows CE, Windows 2000 and Windows 95 operating system products, or successors of those products. 1.6 "Necessary Claims" shall mean those claims of a patent or patent application, including without limitation, United States Patents Nos. 5,265,261 and 5,437,013, which (a) are owned, controlled or sublicenseable by Microsoft without payment of a fee to an unaffiliated third party; and (b) are necessarily infringed by implementing the CIFS communication protocol as set forth in the Technical Reference, wherein a claim is necessarily infringed only when there are no technically reasonable alternatives to such infringement. 1.7 "Technical Reference" shall mean the Microsoft copyright document titled Common Internet File System (CIFS) File Access Protocol version 1.0 found at MSDN Downloads. 1.8 "Term" shall have the meaning assigned to it in Section 6.1. 2. Enhancements and Updates 2.1 Enhancements. Any Microsoft file system protocol enhancements beyond the Technical Reference are not licensed. 2.2 Updates. Updates to the Technical Reference are not licensed. In the event Microsoft elects to provide updates of the Technical Reference to Company, such updates will only be licensed by Microsoft under a separate written agreement or a written amendment to this Agreement. 3. License Grants 3.1 Copyright License. Subject to Section 3.3, Microsoft hereby grants Company a worldwide, royalty-free, non-exclusive, personal, non-transferable, non-sublicensable license to (a) make a reasonable number of complete copies of the Technical Reference and (b) use the Technical Reference for the sole purpose of developing Company Implementations. 3.2 Patent License. Subject to Sections 3.3 - 3.7, Microsoft hereby grants Company a worldwide, royalty-free, non-exclusive, personal, transferable, non-sublicensable, license under its Necessary Claims to (1) make, use, import, and (2) offer to sell, sell and distribute, directly or indirectly, to End Users, Company Implementations that fully comply with the Technical Reference. The above license is limited to implementing the CIFS communication protocol itself, and does not include any express or implied licenses or other rights to any underlying technology (operating system technology, local file system technology, etc.) that may be used to make a complete file server or other CIFS compatible device. 3.3 IPR Impairing License Restrictions. For reasons, including without limitation, because (i) Company does not have the right to sublicense its rights to the Necessary Claims and (ii) Company's license rights hereunder to Microsoft's intellectual property are limited in scope, Company shall not distribute any Company Implementation in any manner that would subject

Royalty-Free CIFS Technical Reference License Agreement This is a legal agreement ("Agreement") between the undersigned (either an individual or an entity) ("You" or "Company"), and Microsoft Corporation ("Microsoft"). The CIFS Technical Reference (as defined below) is available for You to reference, but if You want to implement the Technical Reference, You must sign and return this Agreement AS IS. This is an offer to be accepted only on the terms set forth in this Agreement. If You make any changes to this Agreement, the offer is revoked. RECITALS Whereas, the industry has requested that Microsoft set forth its license terms for CIFS (as defined below); Whereas, Microsoft is now setting forth those terms by making a license available. 1. Definitions 1.1 "CIFS" shall mean the common internet file system communication protocol described in the Technical Reference. 1.2 "Company Implementation" shall mean only those portions of the software developed by Company that implement CIFS for use on Non-Microsoft Platforms. 1.3 "End User" shall mean a third party customer or potential customer to whom a copy of Company Implementation is licensed, delivered, or otherwise provided primarily for such customer's or potential customer's use, and not for further sublicense or distribution. 1.4 "IPR Impairing License" shall mean the GNU General Public License, the GNU Lesser/Library General Public License, and any license that requires in any instance that other software distributed with software subject to such license (a) be disclosed and distributed in source code form; (b) be licensed for purposes of making derivative works; or (c) be redistributable at no charge. 1.5 "Non-Microsoft Platforms" shall mean any platform other than any version of a Microsoft client, embedded and server operating system product, including without limitation, Windows XP, Windows CE, Windows 2000 and Windows 95 operating system products, or successors of those products. 1.6 "Necessary Claims" shall mean those claims of a patent or patent application, including without limitation, United States Patents Nos. 5,265,261 and 5,437,013, which (a) are owned, controlled or sublicenseable by Microsoft without payment of a fee to an unaffiliated third party; and (b) are necessarily infringed by implementing the CIFS communication protocol as set forth in the Technical Reference, wherein a claim is necessarily infringed only when there are no technically reasonable alternatives to such infringement. 1.7 "Technical Reference" shall mean the Microsoft copyright document titled Common Internet File System (CIFS) File Access Protocol version 1.0 found at MSDN Downloads. 1.8 "Term" shall have the meaning assigned to it in Section 6.1. 2. Enhancements and Updates 2.1 Enhancements. Any Microsoft file system protocol enhancements beyond the Technical Reference are not licensed. 2.2 Updates. Updates to the Technical Reference are not licensed. In the event Microsoft elects to provide updates of the Technical Reference to Company, such updates will only be licensed by Microsoft under a separate written agreement or a written amendment to this Agreement. 3. License Grants 3.1 Copyright License. Subject to Section 3.3, Microsoft hereby grants Company a worldwide, royalty-free, non-exclusive, personal, non-transferable, non-sublicensable license to (a) make a reasonable number of complete copies of the Technical Reference and (b) use the Technical Reference for the sole purpose of developing Company Implementations. 3.2 Patent License. Subject to Sections 3.3 - 3.7, Microsoft hereby grants Company a worldwide, royalty-free, non-exclusive, personal, transferable, non-sublicensable, license under its Necessary Claims to (1) make, use, import, and (2) offer to sell, sell and distribute, directly or indirectly, to End Users, Company Implementations that fully comply with the Technical Reference. The above license is limited to implementing the CIFS communication protocol itself, and does not include any express or implied licenses or other rights to any underlying technology (operating system technology, local file system technology, etc.) that may be used to make a complete file server or other CIFS compatible device. 3.3 IPR Impairing License Restrictions. For reasons, including without limitation, because (i) Company does not have the right to sublicense its rights to the Necessary Claims and (ii) Company's license rights hereunder to Microsoft's intellectual property are limited in scope, Company shall not distribute any Company Implementation in any manner that would subject

Royalty-Free CIFS Technical Reference License Agreement This is a legal agreement ("Agreement") between the undersigned (either an individual or an entity) ("You" or "Company"), and Microsoft Corporation ("Microsoft"). The CIFS Technical Reference (as defined below) is available for You to reference, but if You want to implement the Technical Reference, You must sign and return this Agreement AS IS. This is an offer to be accepted only on the terms set forth in this Agreement. If You make any changes to this Agreement, the offer is revoked. RECITALS Whereas, the industry has requested that Microsoft set forth its license terms for CIFS (as defined below); Whereas, Microsoft is now setting forth those terms by making a license available. 1. Definitions 1.1 "CIFS" shall mean the common internet file system communication protocol described in the Technical Reference. 1.2 "Company Implementation" shall mean only those portions of the software developed by Company that implement CIFS for use on Non-Microsoft Platforms. 1.3 "End User" shall mean a third party customer or potential customer to whom a copy of Company Implementation is licensed, delivered, or otherwise provided primarily for such customer's or potential customer's use, and not for further sublicense or distribution. 1.4 "IPR Impairing License" shall mean the GNU General Public License, the GNU Lesser/Library General Public License, and any license that requires in any instance that other software distributed with software subject to such license (a) be disclosed and distributed in source code form; (b) be licensed for purposes of making derivative works; or (c) be redistributable at no charge. 1.5 "Non-Microsoft Platforms" shall mean any platform other than any version of a Microsoft client, embedded and server operating system product, including without limitation, Windows XP, Windows CE, Windows 2000 and Windows 95 operating system products, or successors of those products. 1.6 "Necessary Claims" shall mean those claims of a patent or patent application, including without limitation, United States Patents Nos. 5,265,261 and 5,437,013, which (a) are owned, controlled or sublicenseable by Microsoft without payment of a fee to an unaffiliated third party; and (b) are necessarily infringed by implementing the CIFS communication protocol as set forth in the Technical Reference, wherein a claim is necessarily infringed only when there are no technically reasonable alternatives to such infringement. 1.7 "Technical Reference" shall mean the Microsoft copyright document titled Common Internet File System (CIFS) File Access Protocol version 1.0 found at MSDN Downloads. 1.8 "Term" shall have the meaning assigned to it in Section 6.1. 2. Enhancements and Updates 2.1 Enhancements. Any Microsoft file system protocol enhancements beyond the Technical Reference are not licensed. 2.2 Updates. Updates to the Technical Reference are not licensed. In the event Microsoft elects to provide updates of the Technical Reference to Company, such updates will only be licensed by Microsoft under a separate written agreement or a written amendment to this Agreement. 3. License Grants 3.1 Copyright License. Subject to Section 3.3, Microsoft hereby grants Company a worldwide, royalty-free, non-exclusive, personal, non-transferable, non-sublicensable license to (a) make a reasonable number of complete copies of the Technical Reference and (b) use the Technical Reference for the sole purpose of developing Company Implementations. 3.2 Patent License. Subject to Sections 3.3 - 3.7, Microsoft hereby grants Company a worldwide, royalty-free, non-exclusive, personal, transferable, non-sublicensable, license under its Necessary Claims to (1) make, use, import, and (2) offer to sell, sell and distribute, directly or indirectly, to End Users, Company Implementations that fully comply with the Technical Reference. The above license is limited to implementing the CIFS communication protocol itself, and does not include any express or implied licenses or other rights to any underlying technology (operating system technology, local file system technology, etc.) that may be used to make a complete file server or other CIFS compatible device. 3.3 IPR Impairing License Restrictions. For reasons, including without limitation, because (i) Company does not have the right to sublicense its rights to the Necessary Claims and (ii) Company's license rights hereunder to Microsoft's intellectual property are limited in scope, Company shall not distribute any Company Implementation in any manner that would subject

Royalty-Free CIFS Technical Reference License Agreement This is a legal agreement ("Agreement") between the undersigned (either an individual or an entity) ("You" or "Company"), and Microsoft Corporation ("Microsoft"). The CIFS Technical Reference (as defined below) is available for You to reference, but if You want to implement the Technical Reference, You must sign and return this Agreement AS IS. This is an offer to be accepted only on the terms set forth in this Agreement. If You make any changes to this Agreement, the offer is revoked. RECITALS Whereas, the industry has requested that Microsoft set forth its license terms for CIFS (as defined below); Whereas, Microsoft is now setting forth those terms by making a license available. 1. Definitions 1.1 "CIFS" shall mean the common internet file system communication protocol described in the Technical Reference. 1.2 "Company Implementation" shall mean only those portions of the software developed by Company that implement CIFS for use on Non-Microsoft Platforms. 1.3 "End User" shall mean a third party customer or potential customer to whom a copy of Company Implementation is licensed, delivered, or otherwise provided primarily for such customer's or potential customer's use, and not for further sublicense or distribution. 1.4 "IPR Impairing License" shall mean the GNU General Public License, the GNU Lesser/Library General Public License, and any license that requires in any instance that other software distributed with software subject to such license (a) be disclosed and distributed in source code form; (b) be licensed for purposes of making derivative works; or (c) be redistributable at no charge. 1.5 "Non-Microsoft Platforms" shall mean any platform other than any version of a Microsoft client, embedded and server operating system product, including without limitation, Windows XP, Windows CE, Windows 2000 and Windows 95 operating system products, or successors of those products. 1.6 "Necessary Claims" shall mean those claims of a patent or patent application, including without limitation, United States Patents Nos. 5,265,261 and 5,437,013, which (a) are owned, controlled or sublicenseable by Microsoft without payment of a fee to an unaffiliated third party; and (b) are necessarily infringed by implementing the CIFS communication protocol as set forth in the Technical Reference, wherein a claim is necessarily infringed only when there are no technically reasonable alternatives to such infringement. 1.7 "Technical Reference" shall mean the Microsoft copyright document titled Common Internet File System (CIFS) File Access Protocol version 1.0 found at MSDN Downloads. 1.8 "Term" shall have the meaning assigned to it in Section 6.1. 2. Enhancements and Updates 2.1 Enhancements. Any Microsoft file system protocol enhancements beyond the Technical Reference are not licensed. 2.2 Updates. Updates to the Technical Reference are not licensed. In the event Microsoft elects to provide updates of the Technical Reference to Company, such updates will only be licensed by Microsoft under a separate written agreement or a written amendment to this Agreement. 3. License Grants 3.1 Copyright License. Subject to Section 3.3, Microsoft hereby grants Company a worldwide, royalty-free, non-exclusive, personal, non-transferable, non-sublicensable license to (a) make a reasonable number of complete copies of the Technical Reference and (b) use the Technical Reference for the sole purpose of developing Company Implementations. 3.2 Patent License. Subject to Sections 3.3 - 3.7, Microsoft hereby grants Company a worldwide, royalty-free, non-exclusive, personal, transferable, non-sublicensable, license under its Necessary Claims to (1) make, use, import, and (2) offer to sell, sell and distribute, directly or indirectly, to End Users, Company Implementations that fully comply with the Technical Reference. The above license is limited to implementing the CIFS communication protocol itself, and does not include any express or implied licenses or other rights to any underlying technology (operating system technology, local file system technology, etc.) that may be used to make a complete file server or other CIFS compatible device. 3.3 IPR Impairing License Restrictions. For reasons, including without limitation, because (i) Company does not have the right to sublicense its rights to the Necessary Claims and (ii) Company's license rights hereunder to Microsoft's intellectual property are limited in scope, Company shall not distribute any Company Implementation in any manner that would subject

Royalty-Free CIFS Technical Reference License Agreement This is a legal agreement ("Agreement") between the undersigned (either an individual or an entity) ("You" or "Company"), and Microsoft Corporation ("Microsoft"). The CIFS Technical Reference (as defined below) is available for You to reference, but if You want to implement the Technical Reference, You must sign and return this Agreement AS IS. This is an offer to be accepted only on the terms set forth in this Agreement. If You make any changes to this Agreement, the offer is revoked. RECITALS Whereas, the industry has requested that Microsoft set forth its license terms for CIFS (as defined below); Whereas, Microsoft is now setting forth those terms by making a license available. 1. Definitions 1.1 "CIFS" shall mean the common internet file system communication protocol described in the Technical Reference. 1.2 "Company Implementation" shall mean only those portions of the software developed by Company that implement CIFS for use on Non-Microsoft Platforms. 1.3 "End User" shall mean a third party customer or potential customer to whom a copy of Company Implementation is licensed, delivered, or otherwise provided primarily for such customer's or potential customer's use, and not for further sublicense or distribution. 1.4 "IPR Impairing License" shall mean the GNU General Public License, the GNU Lesser/Library General Public License, and any license that requires in any instance that other software distributed with software subject to such license (a) be disclosed and distributed in source code form; (b) be licensed for purposes of making derivative works; or (c) be redistributable at no charge. 1.5 "Non-Microsoft Platforms" shall mean any platform other than any version of a Microsoft client, embedded and server operating system product, including without limitation, Windows XP, Windows CE, Windows 2000 and Windows 95 operating system products, or successors of those products. 1.6 "Necessary Claims" shall mean those claims of a patent or patent application, including without limitation, United States Patents Nos. 5,265,261 and 5,437,013, which (a) are owned, controlled or sublicenseable by Microsoft without payment of a fee to an unaffiliated third party; and (b) are necessarily infringed by implementing the CIFS communication protocol as set forth in the Technical Reference, wherein a claim is necessarily infringed only when there are no technically reasonable alternatives to such infringement. 1.7 "Technical Reference" shall mean the Microsoft copyright document titled Common Internet File System (CIFS) File Access Protocol version 1.0 found at MSDN Downloads. 1.8 "Term" shall have the meaning assigned to it in Section 6.1. 2. Enhancements and Updates 2.1 Enhancements. Any Microsoft file system protocol enhancements beyond the Technical Reference are not licensed. 2.2 Updates. Updates to the Technical Reference are not licensed. In the event Microsoft elects to provide updates of the Technical Reference to Company, such updates will only be licensed by Microsoft under a separate written agreement or a written amendment to this Agreement. 3. License Grants 3.1 Copyright License. Subject to Section 3.3, Microsoft hereby grants Company a worldwide, royalty-free, non-exclusive, personal, non-transferable, non-sublicensable license to (a) make a reasonable number of complete copies of the Technical Reference and (b) use the Technical Reference for the sole purpose of developing Company Implementations. 3.2 Patent License. Subject to Sections 3.3 - 3.7, Microsoft hereby grants Company a worldwide, royalty-free, non-exclusive, personal, transferable, non-sublicensable, license under its Necessary Claims to (1) make, use, import, and (2) offer to sell, sell and distribute, directly or indirectly, to End Users, Company Implementations that fully comply with the Technical Reference. The above license is limited to implementing the CIFS communication protocol itself, and does not include any express or implied licenses or other rights to any underlying technology (operating system technology, local file system technology, etc.) that may be used to make a complete file server or other CIFS compatible device. 3.3 IPR Impairing License Restrictions. For reasons, including without limitation, because (i) Company does not have the right to sublicense its rights to the Necessary Claims and (ii) Company's license rights hereunder to Microsoft's intellectual property are limited in scope, Company shall not distribute any Company Implementation in any manner that would subject

Royalty-Free CIFS Technical Reference License Agreement This is a legal agreement ("Agreement") between the undersigned (either an individual or an entity) ("You" or "Company"), and Microsoft Corporation ("Microsoft"). The CIFS Technical Reference (as defined below) is available for You to reference, but if You want to implement the Technical Reference, You must sign and return this Agreement AS IS. This is an offer to be accepted only on the terms set forth in this Agreement. If You make any changes to this Agreement, the offer is revoked. RECITALS Whereas, the industry has requested that Microsoft set forth its license terms for CIFS (as defined below); Whereas, Microsoft is now setting forth those terms by making a license available. 1. Definitions 1.1 "CIFS" shall mean the common internet file system communication protocol described in the Technical Reference. 1.2 "Company Implementation" shall mean only those portions of the software developed by Company that implement CIFS for use on Non-Microsoft Platforms. 1.3 "End User" shall mean a third party customer or potential customer to whom a copy of Company Implementation is licensed, delivered, or otherwise provided primarily for such customer's or potential customer's use, and not for further sublicense or distribution. 1.4 "IPR Impairing License" shall mean the GNU General Public License, the GNU Lesser/Library General Public License, and any license that requires in any instance that other software distributed with software subject to such license (a) be disclosed and distributed in source code form; (b) be licensed for purposes of making derivative works; or (c) be redistributable at no charge. 1.5 "Non-Microsoft Platforms" shall mean any platform other than any version of a Microsoft client, embedded and server operating system product, including without limitation, Windows XP, Windows CE, Windows 2000 and Windows 95 operating system products, or successors of those products. 1.6 "Necessary Claims" shall mean those claims of a patent or patent application, including without limitation, United States Patents Nos. 5,265,261 and 5,437,013, which (a) are owned, controlled or sublicenseable by Microsoft without payment of a fee to an unaffiliated third party; and (b) are necessarily infringed by implementing the CIFS communication protocol as set forth in the Technical Reference, wherein a claim is necessarily infringed only when there are no technically reasonable alternatives to such infringement. 1.7 "Technical Reference" shall mean the Microsoft copyright document titled Common Internet File System (CIFS) File Access Protocol version 1.0 found at MSDN Downloads. 1.8 "Term" shall have the meaning assigned to it in Section 6.1. 2. Enhancements and Updates 2.1 Enhancements. Any Microsoft file system protocol enhancements beyond the Technical Reference are not licensed. 2.2 Updates. Updates to the Technical Reference are not licensed. In the event Microsoft elects to provide updates of the Technical Reference to Company, such updates will only be licensed by Microsoft under a separate written agreement or a written amendment to this Agreement. 3. License Grants 3.1 Copyright License. Subject to Section 3.3, Microsoft hereby grants Company a worldwide, royalty-free, non-exclusive, personal, non-transferable, non-sublicensable license to (a) make a reasonable number of complete copies of the Technical Reference and (b) use the Technical Reference for the sole purpose of developing Company Implementations. 3.2 Patent License. Subject to Sections 3.3 - 3.7, Microsoft hereby grants Company a worldwide, royalty-free, non-exclusive, personal, transferable, non-sublicensable, license under its Necessary Claims to (1) make, use, import, and (2) offer to sell, sell and distribute, directly or indirectly, to End Users, Company Implementations that fully comply with the Technical Reference. The above license is limited to implementing the CIFS communication protocol itself, and does not include any express or implied licenses or other rights to any underlying technology (operating system technology, local file system technology, etc.) that may be used to make a complete file server or other CIFS compatible device. 3.3 IPR Impairing License Restrictions. For reasons, including without limitation, because (i) Company does not have the right to sublicense its rights to the Necessary Claims and (ii) Company's license rights hereunder to Microsoft's intellectual property are limited in scope, Company shall not distribute any Company Implementation in any manner that would subject

Royalty-Free CIFS Technical Reference License Agreement This is a legal agreement ("Agreement") between the undersigned (either an individual or an entity) ("You" or "Company"), and Microsoft Corporation ("Microsoft"). The CIFS Technical Reference (as defined below) is available for You to reference, but if You want to implement the Technical Reference, You must sign and return this Agreement AS IS. This is an offer to be accepted only on the terms set forth in this Agreement. If You make any changes to this Agreement, the offer is revoked. RECITALS Whereas, the industry has requested that Microsoft set forth its license terms for CIFS (as defined below); Whereas, Microsoft is now setting forth those terms by making a license available. 1. Definitions 1.1 "CIFS" shall mean the common internet file system communication protocol described in the Technical Reference. 1.2 "Company Implementation" shall mean only those portions of the software developed by Company that implement CIFS for use on Non-Microsoft Platforms. 1.3 "End User" shall mean a third party customer or potential customer to whom a copy of Company Implementation is licensed, delivered, or otherwise provided primarily for such customer's or potential customer's use, and not for further sublicense or distribution. 1.4 "IPR Impairing License" shall mean the GNU General Public License, the GNU Lesser/Library General Public License, and any license that requires in any instance that other software distributed with software subject to such license (a) be disclosed and distributed in source code form; (b) be licensed for purposes of making derivative works; or (c) be redistributable at no charge. 1.5 "Non-Microsoft Platforms" shall mean any platform other than any version of a Microsoft client, embedded and server operating system product, including without limitation, Windows XP, Windows CE, Windows 2000 and Windows 95 operating system products, or successors of those products. 1.6 "Necessary Claims" shall mean those claims of a patent or patent application, including without limitation, United States Patents Nos. 5,265,261 and 5,437,013, which (a) are owned, controlled or sublicenseable by Microsoft without payment of a fee to an unaffiliated third party; and (b) are necessarily infringed by implementing the CIFS communication protocol as set forth in the Technical Reference, wherein a claim is necessarily infringed only when there are no technically reasonable alternatives to such infringement. 1.7 "Technical Reference" shall mean the Microsoft copyright document titled Common Internet File System (CIFS) File Access Protocol version 1.0 found at MSDN Downloads. 1.8 "Term" shall have the meaning assigned to it in Section 6.1. 2. Enhancements and Updates 2.1 Enhancements. Any Microsoft file system protocol enhancements beyond the Technical Reference are not licensed. 2.2 Updates. Updates to the Technical Reference are not licensed. In the event Microsoft elects to provide updates of the Technical Reference to Company, such updates will only be licensed by Microsoft under a separate written agreement or a written amendment to this Agreement. 3. License Grants 3.1 Copyright License. Subject to Section 3.3, Microsoft hereby grants Company a worldwide, royalty-free, non-exclusive, personal, non-transferable, non-sublicensable license to (a) make a reasonable number of complete copies of the Technical Reference and (b) use the Technical Reference for the sole purpose of developing Company Implementations. 3.2 Patent License. Subject to Sections 3.3 - 3.7, Microsoft hereby grants Company a worldwide, royalty-free, non-exclusive, personal, transferable, non-sublicensable, license under its Necessary Claims to (1) make, use, import, and (2) offer to sell, sell and distribute, directly or indirectly, to End Users, Company Implementations that fully comply with the Technical Reference. The above license is limited to implementing the CIFS communication protocol itself, and does not include any express or implied licenses or other rights to any underlying technology (operating system technology, local file system technology, etc.) that may be used to make a complete file server or other CIFS compatible device. 3.3 IPR Impairing License Restrictions. For reasons, including without limitation, because (i) Company does not have the right to sublicense its rights to the Necessary Claims and (ii) Company's license rights hereunder to Microsoft's intellectual property are limited in scope, Company shall not distribute any Company Implementation in any manner that would subject

Royalty-Free CIFS Technical Reference License Agreement This is a legal agreement ("Agreement") between the undersigned (either an individual or an entity) ("You" or "Company"), and Microsoft Corporation ("Microsoft"). The CIFS Technical Reference (as defined below) is available for You to reference, but if You want to implement the Technical Reference, You must sign and return this Agreement AS IS. This is an offer to be accepted only on the terms set forth in this Agreement. If You make any changes to this Agreement, the offer is revoked. RECITALS Whereas, the industry has requested that Microsoft set forth its license terms for CIFS (as defined below); Whereas, Microsoft is now setting forth those terms by making a license available. 1. Definitions 1.1 "CIFS" shall mean the common internet file system communication protocol described in the Technical Reference. 1.2 "Company Implementation" shall mean only those portions of the software developed by Company that implement CIFS for use on Non-Microsoft Platforms. 1.3 "End User" shall mean a third party customer or potential customer to whom a copy of Company Implementation is licensed, delivered, or otherwise provided primarily for such customer's or potential customer's use, and not for further sublicense or distribution. 1.4 "IPR Impairing License" shall mean the GNU General Public License, the GNU Lesser/Library General Public License, and any license that requires in any instance that other software distributed with software subject to such license (a) be disclosed and distributed in source code form; (b) be licensed for purposes of making derivative works; or (c) be redistributable at no charge. 1.5 "Non-Microsoft Platforms" shall mean any platform other than any version of a Microsoft client, embedded and server operating system product, including without limitation, Windows XP, Windows CE, Windows 2000 and Windows 95 operating system products, or successors of those products. 1.6 "Necessary Claims" shall mean those claims of a patent or patent application, including without limitation, United States Patents Nos. 5,265,261 and 5,437,013, which (a) are owned, controlled or sublicenseable by Microsoft without payment of a fee to an unaffiliated third party; and (b) are necessarily infringed by implementing the CIFS communication protocol as set forth in the Technical Reference, wherein a claim is necessarily infringed only when there are no technically reasonable alternatives to such infringement. 1.7 "Technical Reference" shall mean the Microsoft copyright document titled Common Internet File System (CIFS) File Access Protocol version 1.0 found at MSDN Downloads. 1.8 "Term" shall have the meaning assigned to it in Section 6.1. 2. Enhancements and Updates 2.1 Enhancements. Any Microsoft file system protocol enhancements beyond the Technical Reference are not licensed. 2.2 Updates. Updates to the Technical Reference are not licensed. In the event Microsoft elects to provide updates of the Technical Reference to Company, such updates will only be licensed by Microsoft under a separate written agreement or a written amendment to this Agreement. 3. License Grants 3.1 Copyright License. Subject to Section 3.3, Microsoft hereby grants Company a worldwide, royalty-free, non-exclusive, personal, non-transferable, non-sublicensable license to (a) make a reasonable number of complete copies of the Technical Reference and (b) use the Technical Reference for the sole purpose of developing Company Implementations. 3.2 Patent License. Subject to Sections 3.3 - 3.7, Microsoft hereby grants Company a worldwide, royalty-free, non-exclusive, personal, transferable, non-sublicensable, license under its Necessary Claims to (1) make, use, import, and (2) offer to sell, sell and distribute, directly or indirectly, to End Users, Company Implementations that fully comply with the Technical Reference. The above license is limited to implementing the CIFS communication protocol itself, and does not include any express or implied licenses or other rights to any underlying technology (operating system technology, local file system technology, etc.) that may be used to make a complete file server or other CIFS compatible device. 3.3 IPR Impairing License Restrictions. For reasons, including without limitation, because (i) Company does not have the right to sublicense its rights to the Necessary Claims and (ii) Company's license rights hereunder to Microsoft's intellectual property are limited in scope, Company shall not distribute any Company Implementation in any manner that would subject