throbber
3/14/2016
`
`INi1Ill"N|L|i J.lE|l1'|I'lI
`
`Ameranth Wireless
`
`http://www.ameranth.com/press_re|eases/name_change.htm|
`
`Go
`
`MAR APR
`
`Iiilillliiilflllllii
`
`
`1 captures
`
`5 Apr 01 — 5 Apr 01
`
`|
`
`AMERANTH‘E
`
`WIRELESS SYSTEMS SOLUTIONS
`
`4 5
`2000 2001
`'
`_
`
`Home
`
`Contact Us
`
`Upcoming
`Events
`
`Products
`
`Customers
`
`Partners
`
`Corn pa I1;-.r
`Information
`
`N news
`
`Job
`Information
`
`1 TE. Rm:
`
`8
`
`8»
`
`Printer Fi'iend| Version
`FOR IMMEDIATE RELEASE
`
`Contact: Laura Smith 888-AMERANTH
`
`Ameranth Technology Systems Changes Name to
`Ameranth Wireless
`
`Developer of the 215' Century Restaurant® system for wireless ordering and payment processing finds new name more descriptive ofproduct
`offerings.
`
`SAN DIEGO, CA, March 6, 2001 —Ameranth Technology Systems, Inc. announced today that it has
`officially changed its name to Ameranth Wireless, Inc. This name change represents a rebirth of the
`company, which has traditionally supplied custom developed and integrated handheld software to large
`corporations. Ameranth found demand for their services so great, that development of a shrink-wrapped
`restaurant product was in order. This product, the 21st Century Restaurant® software version 2.0 for
`wireless ordering and payment processing, is currently in beta testing and will be available for integration
`with Aloha Tab|eService POS on March 8th. The company further felt that the name Ameranth Wireless
`better expressed their sound commitment to putting “Wireless to WorkT""
`
`“Ameranth makes software enabling PocketPC handhelds to wirelessly communicate with fixed
`information systems,” said Ameranth CEO W.J. Kitchen. “While we do help our customers in customizing
`and obtaining the whole system—inc|uding the hardware—we are focusing on the development of plug
`and play software products such as the 21st Century Restaurant for wireless ordering and payment
`processing. The name ‘Ameranth Wire|essT""’ is concise and helps us differentiate ourselves from VARs
`and systems integrators.”
`
`The 213‘ Century Restaurant software version 2.0 is being launched at Aloha Technologies Focus 2001
`show in Dallas, Texas, on March 8th. The software, which runs on Microsoft® Windows® Powered
`PocketPC handheld computers and communicates via Wireless Local Area Networks (WLANs,) interfaces
`with legacy POS systems for wireless tableside ordering and payment processing. The 21st Century
`Restaurant system is currently installed in two beta locations with Aloha Technologies POS.
`
`For more information, please visit www.ameranth.com or call 1 (888) AMERANTH.
`
`AMERANTH WlRELESS,"" INC (www.ameranth.com) is a leading provider of wireless system software
`to the hospitality industry. The Company’s software applications, which run on PocketPC wireless
`handheld computers, communicate with legacy back office systems over wireless LANs—moving the point
`of activity from fixed terminals to where it be|ongs—by the customer's side. Ameranth's 21st Century
`Restaurant system is set to become the industry standard for wireless ordering and payment processing in
`restaurants.
`
`For additional information you may e-mail info@ameranth.com
`
`Ameranth Wireless
`12230 El Camino Real, Suite 330
`San Diego, CA 9213o.2o9o
`Phone: 1
`— (888) -AMERANTH, FAX: (858)794-8222
`
`E-mail
`Gene-ra| Information:m
`Sales: sa|es@ameranth.com
`WebmasterI
`
`Starbucks V. Ameranth, CBM2015-00091
`https://web.archive.org/web/20010405182032/http://www.ameranth.com/press_re|eases/name_change.htmI
`1/2
`
`Starbucks, Ex. 1086
`
`Starbucks, Ex. 1086
`Starbucks v. Ameranth, CBM2015-00091
`
`

`
`3/14/2016
`
`Ameranth Wireless
`
`Ameranth WireIessCopyn'ght © 2000, All Rights Reserved.
`May not be reproduced in whole or part without written consent of Ameranth Technology Systems
`
`Starbucks V. Ameranth, CBM2015-00091
`https2//web.archive.org/web/20010405182032/http://www.am eranth.comIpress_re| easeslnam e_change.htm I
`2/2
`
`Starbucks, Ex. 1086
`
`Starbucks, Ex. 1086
`Starbucks v. Ameranth, CBM2015-00091

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