throbber
&S>seagate
`
`November 1, 1995
`
`Seagate Technology
`8001 E. Bloomington Frwy.
`Bloomington, Minnesota
`55420
`
`Mr. Nathan Malek
`Marketing Assistant
`Patents and Technology Marketing
`1100 Washington A venue South, Suite 201
`Minneapolis, MN 55415
`
`RE: Maximum Transition Run (MTR) Codes for Data Storage Systems, University of Minnesota
`Docket No. 96025
`
`Dear Mr. Malek:
`
`Thank you for your letter; it provided the clarity that I needed. In your letter you asked three
`questions. Let me try to answer them for you.
`
`The first question is:
`a) Is this a technology that Seagate is interested in using?
`
`The MTR coding idea is something I expect to be a part of most future codes used in
`magnetic recording. Yes, Seagate is interested in the technology.
`
`The second and third questions are:
`b) Is this a technology you would like to see kept inside the consortium only?
`
`c) Is this a technology that Seagate would like to have exclusive rights to sub-license to other
`companies outside the consortium?
`
`Let me answer both of the questions by saying that Seagate's~ interest is to have royalty free
`access to the technology.
`
`Our business is to provide disc drives to the world, other activities such as sub-licensing would result
`in diverting rare and valuable talent away from the task of designing, building, and delivering disc
`drives.
`
`Seagate wants unrestricted access to the technology. How this technology is used by others is of no
`concern to Seagate.
`
`Robert E. Kost
`
`cc: Professor Jay Moon
`
`UMN EXHIBIT 2013
`LSI Corp. et al. v. Regents of Univ. of Minn.
`IPR2017-01068
`
`
`Page 1 of 1
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket