AML's M7100 Wireless Linux Terminal

In its own way, the device opens new inroads for Linux to the infrastructure of commerce, the business back end that's a critical tool for management in commerce on any scale.
______________________

Comments

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Re: AML's M7100 Wireless Linux Terminal

Anonymous's picture

I've used this device and found it fit very nicely in my hand. It's size is mostly contributable to it's massive battery. In fact in my testing, the battery lasted for three days of continuous use (as compared to about 3 hours with the "Palm Pilot" type devices).

I simply used OpenSSH to secure the deficencies in the 802.11b network with no problems. By the way there is a "Function Lock" feature that allows single keystroke function keys.

In my experience most warehouse applications still require some sort of terminal emulation. Even when using the newer Microsoft based devices, most of the time they are simply running a telnet application (Windows seems like a total waste of memory and power).

Telnet on Windows CE Terminals?

Anonymous's picture

While this is generally possible, it's a waste of resources to do that, as you write.
I know a company that uses WinCE devices as Citrix clients; other companies develop .net-compact-framework applications for such devices.

I demo'd the M7100 at SCALE2X...

Anonymous's picture

My slides and demo code are at
kegel.com/linux/embed.
The demo was fun; it tied together a UPC database on the web
with the M7100. I built my own compiler using crosstool
rather than using any of the software that came with the M7100.

too big

Anonymous's picture

I know a lot of devices like this one, since my work focuses in warehouse logistics. Mobile terminals of that size were up-to-date 5 years ago, but have been replaced by smaller, more ergonomically terminals yet. Telnet and VT100 emulation have been the de-facto standard for such devices until recently, when the new generation (windows ce-powered) took place. From a security point of view, the transmitted data is so uninterestings that none of our customers care about that - they care more about the weakness of WEP which generally grants an attacker access to the network, no matter which protocol the mobil terminal speak. IMO this device is too late and offers little advantages compared to the older (DOS based) competing products, while it lacks some features of the newer (WinCE based) competitors.

one more complaint

Anonymous's picture

judging from the pictures, it looks this device has no function keys (F1, F2...) but the user has to press the "Func" key + the numeric key. Since function keys are the natural way to control an application on such a device, I consider it a major drawback if the user has to press more than one key for that.

Re: one more complaint

Anonymous's picture

Function keys can be "locked" on by pressing , then the number keys become function keys.

Re: one more complaint

Anonymous's picture

But users need number keys often, too. The tree major input devices of such applications are: barcode scanning, function keys and numeric keys. Cursor keys are less necessary (if the application is stream-lined), letter keys are very rarely needed (mostly for configuration).

Webcast
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers

Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.

Learn More

Sponsored by AMD

White Paper
Red Hat White Paper: Using an Open Source Framework to Catch the Bad Guy

Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6

Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.

Learn more about catching the bad guy in this free white paper.

Learn More

Sponsored by DLT Solutions