Thinkpad Yoga12" Web Page

Total Page：16

File Type：pdf, Size：1020Kb

Welcome at my "Thinkpad Yoga12" web page. Pen and Touch for Thinkpad Yoga12 with ArcaOS. This product is available free of charge and may be used at your own risk. Have fun. Click here for the ISC license. Description - Control ArcaOS with your finger or pen on a Thinkpad Yoga12. Installation Special Parameter Obtain this product here free of charge. Click here for source code. Click here for my home page. Installation Move Yoga12v01.zip into a directory of your choice and unzip it. Copy Yoga12.exe to your C:\OS2\BOOT directory. The Emulate Mouse Driver for OS/2 (ArcaOS, eComStation) is required. Obtain this product here free of charge. Move XSMOUSE10.ZIP into a directory of your choice and unzip it. Copy XSMOUSE.SYS to your C:\OS2\BOOT directory. The USB 2.0 Extended Control Driver for OS/2 (ArcaOS, eComStation) is required. Obtain this product here free of charge. Move USBECD23.ZIP into a directory of your choice and unzip it. Copy USBECD.SYS to your C:\OS2\BOOT directory. Look into your CONFIG.SYS file to determine which mouse device driver has been installed on your system. You may find AMOUSE.SYS or MOUSE.SYS and you need to add the STYPE=XSMOUSE$ parameter to that device driver statement and to insert the DEVICE=C:\OS2 \BOOT\XSMOUSE.SYS device driver statement just above it. Insert also the $FINGER$ and $STYLYS$ device driver statements and the RUN=C:\OS2\BOOT\YOGA12.EXE statement as shown below: DEVICE=C:\OS2\BOOT\XSMOUSE.SYS DEVICE=C:\OS2\BOOT\AMOUSE.SYS STYPE=XSMOUSE$ DEVICE=C:\OS2\BOOT\USBECD.SYS /D:06CB:7244:0005 /N:$FINGER$ /S /V DEVICE=C:\OS2\BOOT\USBECD.SYS /D:056A:00EC:0135 /N:$STYLUS$ /S /V RUN=C:\OS2\BOOT\YOGA12.EXE After that restart your system and the fun begins. Special Parameter C:\OS2\BOOT\YOGA12.EXE /v CAUTION: This parameter may only be used when invoked from a command prompt. /v - verbose. Specify this parameter to get debug output on stdout. © W.M.Brul 2019-2020, all rights reserved..

Copy Link

Recommended publications

The Linux Kernel Module Programming Guide
The Linux Kernel Module Programming Guide Peter Jay Salzman Michael Burian Ori Pomerantz Copyright © 2001 Peter Jay Salzman 2007−05−18 ver 2.6.4 The Linux Kernel Module Programming Guide is a free book; you may reproduce and/or modify it under the terms of the Open Software License, version 1.1. You can obtain a copy of this license at http://opensource.org/licenses/osl.php. This book is distributed in the hope it will be useful, but without any warranty, without even the implied warranty of merchantability or fitness for a particular purpose. The author encourages wide distribution of this book for personal or commercial use, provided the above copyright notice remains intact and the method adheres to the provisions of the Open Software License. In summary, you may copy and distribute this book free of charge or for a profit. No explicit permission is required from the author for reproduction of this book in any medium, physical or electronic. Derivative works and translations of this document must be placed under the Open Software License, and the original copyright notice must remain intact. If you have contributed new material to this book, you must make the material and source code available for your revisions. Please make revisions and updates available directly to the document maintainer, Peter Jay Salzman <[email protected]>. This will allow for the merging of updates and provide consistent revisions to the Linux community. If you publish or distribute this book commercially, donations, royalties, and/or printed copies are greatly appreciated by the author and the Linux Documentation Project (LDP).
[Show full text]
Introduction to Linux Kernel Driver Programming
IntroductionIntroduction toto LinuxLinux kernelkernel driverdriver programmingprogramming Introduction to Linux kernel driver programming The Linux kernel device model Authors and license ● Authors – Michael Opdenacker ([email protected]) Founder of Bootlin, kernel and embedded Linux engineering company https://bootlin.com/company/staff/michael-opdenacker ● License – Creative Commons Attribution – Share Alike 4.0 https://creativecommons.org/licenses/by-sa/4.0/ – Document sources: https://github.com/e-ale/Slides Need for a device model ● For the same device, need to use the same device driver on multiple CPU architectures (x86, ARM…), even though the hardware controllers are different. ● Need for a single driver to support multiple devices of the same kind. ● This requires a clean organization of the code, with the device drivers separated from the controller drivers, the hardware description separated from the drivers themselves, etc. Driver: between bus infrastructure and framework In Linux, a driver is always interfacing with: ● a framework that allows the driver to expose the hardware features in a generic way. ● a bus infrastructure, part of the device model, to detect/communicate with the hardware. Let’s focus on the bus infrastructure for now Device model data structures The device model is organized around three main data structures: ● The struct bus_type structure, which represent one type of bus (USB, PCI, I2C, etc.) ● The struct device_driver structure, which represents one driver capable of handling certain devices on a certain bus. ● The struct device structure, which represents one device connected to a bus The kernel uses inheritance to create more specialized versions of struct device_driver and struct device for each bus subsystem.
[Show full text]
The Linux Device File-System
The Linux Device File-System Richard Gooch EMC Corporation [email protected] Abstract 1 Introduction All Unix systems provide access to hardware via de- vice drivers. These drivers need to provide entry points for user-space applications and system tools to access the hardware. Following the \everything is a file” philosophy of Unix, these entry points are ex- posed in the file name-space, and are called \device The Device File-System (devfs) provides a power- special files” or \device nodes". ful new device management mechanism for Linux. Unlike other existing and proposed device manage- This paper discusses how these device nodes are cre- ment schemes, it is powerful, flexible, scalable and ated and managed in conventional Unix systems and efficient. the limitations this scheme imposes. An alternative mechanism is then presented. It is an alternative to conventional disc-based char- acter and block special devices. Kernel device drivers can register devices by name rather than de- vice numbers, and these device entries will appear in the file-system automatically. 1.1 Device numbers Devfs provides an immediate benefit to system ad- ministrators, as it implements a device naming scheme which is more convenient for large systems Conventional Unix systems have the concept of a (providing a topology-based name-space) and small \device number". Each instance of a driver and systems (via a device-class based name-space) alike. hardware component is assigned a unique device number. Within the kernel, this device number is Device driver authors can benefit from devfs by used to refer to the hardware and driver instance.
[Show full text]
Topic 10: Device Driver
Topic 10: Device Driver Tongping Liu University of Massachusetts Amherst 1 Administration • Today it is the deadline of Project3 • Homework5 is posted, due on 05/03 • Bonus points: ECE570 – 3 points, ECE670-5 points – Design exam questions – Process&threads, scheduling, synchronization, IPC, memory management, device driver/virtualization – Due: 05/01 • Survey project (ECE570/ECE670): 05/12 University of Massachusetts Amherst 2 Objectives • Understanding concepts of device driver, e.g., device number, device file • Understand the difference of kernel modules and device drivers • Learn how to implement a simple kernel module • Learn how to implement a simple device driver University of Massachusetts Amherst 3 Outline • Basic concepts • Kernel module • Writing device driver University of Massachusetts Amherst 4 Device Driver • A special kind of computer program that operates or controls a particular type of device that is attached to a computer University of Massachusetts Amherst 5 Device Driver • A special kind of computer program that operates or controls a particular type of device that is attached to a computer – Needs to execute privileged instructions – Must be integrated into the OS kernel, with a specific format – Interfaces both to kernel and to hardware University of Massachusetts Amherst 6 Whole System Stack Note: This picture is excerpted from Write a Linux Hardware Device Driver, Andrew O’Shauqhnessy, Unix world University of Massachusetts Amherst 7 Another View from OS University of Massachusetts Amherst 8 Type of Devices • Character device – Read or write one byte at a time as a stream of sequential data – Examples: serial ports, parallel ports, sound cards, keyboard • Block device – Randomly access fixed-sized chunks of data (block) – Examples: hard disks, USB cameras University of Massachusetts Amherst 9 Linux Device Driver • Manage data flow between user programs and device • Typically a self-contained kernel module – Add and remove dynamically • Device is a special file in /dev that user can access, e.g.
[Show full text]
Analyst® Device Driver 1.3 Release Notes 2 / 16 RUO-IDV-03-1997-E Contents
Analyst® Device Driver 1.3 Release Notes RUO-IDV-03-1997-E May 2018 This document is provided to customers who have purchased SCIEX equipment to use in the operation of such SCIEX equipment. This document is copyright protected and any reproduction of this document or any part of this document is strictly prohibited, except as SCIEX may authorize in writing. Software that may be described in this document is furnished under a license agreement. It is against the law to copy, modify, or distribute the software on any medium, except as specifically allowed in the license agreement. Furthermore, the license agreement may prohibit the software from being disassembled, reverse engineered, or decompiled for any purpose. Warranties are as stated therein. Portions of this document may make reference to other manufacturers and/or their products, which may contain parts whose names are registered as trademarks and/or function as trademarks of their respective owners. Any such use is intended only to designate those manufacturers' products as supplied by SCIEX for incorporation into its equipment and does not imply any right and/or license to use or permit others to use such manufacturers' and/or their product names as trademarks. SCIEX warranties are limited to those express warranties provided at the time of sale or license of its products and are SCIEX’s sole and exclusive representations, warranties, and obligations. SCIEX makes no other warranty of any kind whatsoever, expressed or implied, including without limitation, warranties of merchantability or fitness for a particular purpose, whether arising from a statute or otherwise in law or from a course of dealing or usage of trade, all of which are expressly disclaimed, and assumes no responsibility or contingent liability, including indirect or consequential damages, for any use by the purchaser or for any adverse circumstances arising therefrom.
[Show full text]
Reactos-Devtutorial.Pdf
Developer Tutorials Developer Tutorials Next Developer Tutorials Table of Contents I. Newbie Developer 1. Introduction to ReactOS development 2. Where to get the latest ReactOS source, compilation tools and how to compile the source 3. Testing your compiled ReactOS code 4. Where to go from here (newbie developer) II. Centralized Source Code Repository 5. Introducing CVS 6. Downloading and configuring your CVS client 7. Checking out a new tree 8. Updating your tree with the latest code 9. Applying for write access 10. Submitting your code with CVS 11. Submitting a patch to the project III. Advanced Developer 12. CD Packaging Guide 13. ReactOS Architecture Whitepaper 14. ReactOS WINE Developer Guide IV. Bochs testing 15. Introducing Bochs 16. Downloading and Using Bochs with ReactOS 17. The compile, test and debug cycle under Bochs V. VMware Testing 18. Introducing VMware List of Tables 7.1. Modules http://reactos.com/rosdocs/tutorials/bk02.html (1 of 2) [3/18/2003 12:16:53 PM] Developer Tutorials Prev Up Next Chapter 8. Where to go from here Home Part I. Newbie Developer (newbie user) http://reactos.com/rosdocs/tutorials/bk02.html (2 of 2) [3/18/2003 12:16:53 PM] Part I. Newbie Developer Part I. Newbie Developer Prev Developer Tutorials Next Newbie Developer Table of Contents 1. Introduction to ReactOS development 2. Where to get the latest ReactOS source, compilation tools and how to compile the source 3. Testing your compiled ReactOS code 4. Where to go from here (newbie developer) Prev Up Next Developer Tutorials Home Chapter 1. Introduction to ReactOS development http://reactos.com/rosdocs/tutorials/bk02pt01.html [3/18/2003 12:16:54 PM] Chapter 1.
[Show full text]
Detecting Exploit Code Execution in Loadable Kernel Modules
Detecting Exploit Code Execution in Loadable Kernel Modules HaizhiXu WenliangDu SteveJ.Chapin Systems Assurance Institute Syracuse University 3-114 CST, 111 College Place, Syracuse, NY 13210, USA g fhxu02, wedu, chapin @syr.edu Abstract and pointer checks can lead to kernel-level exploits, which can jeopardize the integrity of the running kernel. Inside the In current extensible monolithic operating systems, load- kernel, exploitcode has the privilegeto interceptsystem ser- able kernel modules (LKM) have unrestricted access to vice routines, to modify interrupt handlers, and to overwrite all portions of kernel memory and I/O space. As a result, kernel data. In such cases, the behavior of the entire sys- kernel-module exploitation can jeopardize the integrity of tem may become suspect. the entire system. In this paper, we analyze the threat that Kernel-level protection is different from user space pro- comes from the implicit trust relationship between the oper- tection. Not every application-level protection mechanism ating system kernel and loadable kernel modules. We then can be applied directly to kernel code, because privileges present a speciﬁcation-directed access monitoring tool— of the kernel environment is different from that of the user HECK, that detects kernel modules for malicious code ex- space. For example, non-executableuser page [21] and non- ecution. Inside the module, HECK prevents code execution executable user stack [29] use virtual memory mapping sup- on the kernel stack and the data sections; on the bound- port for pages and segments, but inside the kernel, a page ary, HECK restricts the module’s access to only those kernel or segment fault can lead to kernel panic.
[Show full text]
Guest OS Compatibility Guide
Guest OS Compatibility Guide Guest OS Compatibility Guide Last Updated: September 29, 2021 For more information go to vmware.com. Introduction VMware provides the widest virtualization support for guest operating systems in the industry to enable your environments and maximize your investments. The VMware Compatibility Guide shows the certification status of operating system releases for use as a Guest OS by the following VMware products: • VMware ESXi/ESX Server 3.0 and later • VMware Workstation 6.0 and later • VMware Fusion 2.0 and later • VMware ACE 2.0 and later • VMware Server 2.0 and later VMware Certification and Support Levels VMware product support for operating system releases can vary depending upon the specific VMware product release or update and can also be subject to: • Installation of specific patches to VMware products • Installation of specific operating system patches • Adherence to guidance and recommendations that are documented in knowledge base articles VMware attempts to provide timely support for new operating system update releases and where possible, certification of new update releases will be added to existing VMware product releases in the VMware Compatibility Guide based upon the results of compatibility testing. Tech Preview Operating system releases that are shown with the Tech Preview level of support are planned for future support by the VMware product but are not certified for use as a Guest OS for one or more of the of the following reasons: • The operating system vendor has not announced the general availability of the OS release. • Not all blocking issues have been resolved by the operating system vendor.
[Show full text]
ACPI Project for Ecomstation
The ACPI Project for eComStation David Azarewicz www.88watts.net [email protected] Warpstock USA 2012 About Me • I am primarily a hardware developer. I started my career designing hardware for IBM 360 mainframe clones. • I then joined a small company building Cray compatible computers where I did a little of everything including microcode and embedded systems hardware and software. • Since then I have worked on projects from auto industry process controllers, to home automation, to radiation effects testing for satellite electronics. • I have been using OS/2 and developing software for OS/2 since the beginning. • Being an experienced hardware developer gives me an advantage in writing device drivers. Warpstock USA 2012 - The ACPI Project - David Azarewicz - Page 2 of 20 This Presentation • What is ACPI? • What is the ACPI Project? • What does the ACPI Project software do? • The Big Picture • The benefits and limitations of the ACPI Project software • How to work around problems • Using ACPI in your applications • Questions Warpstock USA 2012 - The ACPI Project - David Azarewicz - Page 3 of 20 What is ACPI? • ACPI stands for Advanced Configuration and Power Interface • ACPI is supplied by your computer vendor and is part of your computer’s BIOS. • ACPI provides a standard interface to your computer’s hardware through a list of objects and methods called the ACPI tables. • Software can use the ACPI tables to learn about what hardware is available • Software can use the ACPI tables to do things in the system. • ACPI is an extremely large and complex topic and is not really the subject of this presentation.
[Show full text]
Evolutionary Sprint 2009/11
Evolutionary Sprint Evolutionary Sprint 2009/11 Speaker: Eugene Gorbunoff software http://ecomstation.ru Perspectives of eComStation 2008/11 “Build non-sinking constructions” 2007/11 “Change your mind” 2006/11 “OS/2 Village” software http://ecomstation.ru Perspectives of eComStation What is Evolutionary Sprint? ● Evolutionary = don't migrate to other platform ● Sprint = 2-3 years to improve situation (starting from fall 2006) software http://ecomstation.ru Perspectives of eComStation Contents of the presentation: (A) (B) (C) What's new? What is successful eCS? PC in 2010 Roles Make quick changes FAQ eComStation 3.0 We need new software software http://ecomstation.ru Perspectives of eComStation Key slide: #04-00 Sci-tech labs.. development of technologies.. software http://ecomstation.ru Perspectives of eComStation software http://ecomstation.ru Perspectives of eComStation Keep in mind.. eComStation 2.0 was started in 2002!! software http://ecomstation.ru Perspectives of eComStation What's new in 2009? # 05-00 eComStation 2.0 RC7, eComStation 2.0 GA Applications: * OpenOffice.org 3.1 GA * PMView (2009/05) improved for SMP/Panorama VESA * always the latest Thunderbird, Firefox * DFSee 10.0 New technologies: * Flash-player software http://ecomstation.ru Perspectives of eComStation What's new in 2009? # 05-02 ACPI * Poor support of users during 2009 * Intel ACPI source code 2008/12 * ACPI is patching the kernel on-the-fly (suspend/resume) * support of Embedded controller is implemented Hardware support: * CUPS (USB, debugging) software http://ecomstation.ru
[Show full text]
Warpstock 2018 Presentations Presenter Session Title Notes
Warpstock 2018 Presentations Presenter Session Title Notes Joe Suttle Public Speaking - You CAN do it! Lewis Rosenthal ArcaOS update In this session, Lewis Rosenthal, Managing Member of Arca Noae, LLC, will provide an update on the status of the 5.0 release cycle and expectations for 5.1. Lewis Rosenthal Creating an ArcaOS How to create an ArcaOS installation stick without an Session (1/2 slot) Bootable USB Stick OS/2, eCS, or ArcaOS system already up and running. from ANY Major OS Following onto the well-received session at Warpstock (with live demo) Europe this year, this edition will feature a live demonstration so that the audience may get a feel for walking through the process and just how quick it really is from start to finish. Lewis Rosenthal Forking an Open This session will discuss the reasoning behind splitting a Source Project: Why, project and taking the code in a different direction from the When, and How main development team. Sometimes, the issues are technological in nature, at other times, philosophical or even political. In no event, however, should the decision to fork be taken lightly or without great care. Afterward, providing clarity on the differences between the fork and the original project, without promoting disharmony, presents challenges of its own. Lewis Rosenthal DOS and WinOS/2 on What works, what doesn't, what Arca Noae is trying to do modern systems with about it, and how long that might take. Issues concern a ArcaOS broad range of brief topic points including long filenames, FAT32, extended attributes, memory management, video, and audio functionality.
[Show full text]
Universidad Nacional De San Agustín De Arequipa Escuela De Posgrado Unidad De Posgrado De La Facultad De Ingeniería De Producc
UNIVERSIDAD NACIONAL DE SAN AGUSTÍN DE AREQUIPA ESCUELA DE POSGRADO UNIDAD DE POSGRADO DE LA FACULTAD DE INGENIERÍA DE PRODUCCIÓN Y SERVICIOS VIRTUALIZACIÓN PARA LA ALTA DISPONIBILIDAD DE SERVICIOS WAN DE LA UNIVERSIDAD NACIONAL DE SAN AGUSTÍN Tesis presentada por el Bachiller: CHRISTIAN AUGUSTO ROMERO GOYZUETA Para optar el GRADO ACADEMICO DE MAESTRO EN CIENCIAS: INGENIERÍA DE SISTEMAS, CON MENCIÓN EN GERENCIA EN TECNOLOGÍAS DE LA INFORMACIÓN Asesor: MG. DANTE JESUS VELÁSQUEZ CONTRERAS AREQUIPA PERÚ 2018 PRESENTACIÓN Sr. Director del a Facultad de Postgrado de la Facultad de Ingeniería de Producción y Servicios Sres. Miembros del Jurado Examinador de tesis Doy a vuestra consireación el estudio de investigación titulado “VIRTUALIZACIÓN PARA LA ALTA DISPONIBILIDAD DE SERVICIOS WAN DE LA UNIVERSIDAD NACIONAL DE SAN AGUSTÍN”, el mismo que de ser aprobado me permitirá optar el título profesional de Maestro en Ingeniería de Sistemas con mención en Gerencia en Tecnologías de la Información. Arequipa, Diciembre del 2018 ____________________________________ Ing. Christian Augusto Romero Goyzueta DNI: 43244797 Dedicatoria Esta investigación está dedicada a mi esposa, hijos y toda mi familia. Agradecimientos Quiero agradecer a toda mi familia, a quienes me acompañan, colaboran y por haber permitido hacer esta investigación de la mejor forma. A las autoridades, docentes, asesores y colegas que han colaborado con la mejor disposición para apoyar esta investigación. TABLA DE CONTENIDOS LISTA DE FIGURAS ..................................................................................................................
[Show full text]