DOCSLIB.ORG

Keypad and Troubleshooting Under MS-DOS Read Through All Steps Before Beginning

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Keypad and Troubleshooting Under MS-DOS Read Through All Steps Before Beginning Keypad and troubleshooting under MS-DOS Read through all steps before beginning. Steps below are specific for COM port 1 and COM port 2 configurations. FIRST, some steps to set the environment into a known working state that we'll work from: 1. Remove all other connected devices from the notebook 2. Disconnect any other attached devices including the IO bar from the notebook 3. Run a virus checker on your notebook 4. If possible complete a back up of at least your data before proceeding (not necessary just a common step of cautionary troubleshooting) As the Toshiba notebook restarts get into the BIOS settings. The steps below will ensure that your serial port is enabled and configured for COM1 (3F8H / IRQ 4) in the BIOS. For Non-Toshiba notebooks, please refer to your notebook user's guide on enabling and configuring your COM ports. 1. Press and Hold ESC right after the notebook completes the shutdown from above. 2. You'll get a Check system. Then Press [F1] key. 3. Press F1 key 4. Locate the Serial Port setup information (on many notebooks, you'll need to press the PgDn key to get to a second page). 5. Make sure the Serial Port is enabled and configured for COM1. 6. Press [END] key to save any changes you made and restart the notebook. Perform a clean boot to troubleshoot a possible hardware conflict. Follow the appropriate section below to boot clean (without any Autoexec.bat or config.sys files) For Windows 98 Restart the computer system. After the system has completed its BIOS check, (just before the Windows 98 logo screen) press and hold the CONTROL key (Ctrl) until the "Windows 98 Startup Menu" appears. Now press "Shift+F5" and the computer system should report "Windows is Bypassing your Startup files." For Windows 95 Restart the computer system. When the message "Starting Windows 95..." appears, press the F8 key. This will take you to the "Microsoft Windows 95 Startup Menu". Now press "Shift+F5" and the computer system should report "Windows is Bypassing your Startup files." For DOS® 6.0 or Higher Restart the computer system. When the message "Starting MS-DOS..." appears, press the F5 key and the computer system should report "MS-DOS has bypassed your CONFIG.SYS and AUTOEXEC.BAT". DOS 5.0 or Earlier Create a DOS "system disk" for drive A: with the "Format A: /S" command. Start the computer with this boot disk in drive A. Type Format a: /s and press ENTER (if you get a bad command or filename you'll need to ascertain the location of your MS-DOS files and type the complete path. For example, if they are in the DOS directory, type C:\dos\format a: /s and press ENTER). 1. After booting cleanly insert the Keypad driver diskette into Drive A and type A:\DOSINST and press ENTER. This will start the install process. 2. At the COM port screen, select COM1 3. At the testing screen, type on your keypad. The keypad is working and configured for the correct port when the keypad box turns dark. 4. If the keypad test fails you can select a different COM port setting and recheck. Although since the BIOS in the steps above was set to COM1 and the install program was set to COM1, this step is unnecessary. 5. If the keypad works here, but when your restart your notebook off of the hard disk drive it does not work, then there is a device driver conflict in either your config.sys or autoexec.bat files. Refer to the Software conflicts section next. Troubleshoot Software/device driver conflicts information If the keypad loads and works correctly when you boot clean as described in the above section, then there may be a conflict with something being loaded in the AUTOEXEC.BAT or CONFIG.SYS files. To determine the specific software causing the conflict, you will need to add back the contents of the AUTOEXEC.BAT and CONFIG.SYS files one line at a time until the mouse fails again. To add back the contents of the AUTOEXEC.BAT and CONFIG.SYS, follow the instructions below. DOS 6.0 or higher Using DOS 6.0 or later, restart the computer, press the F8 key when the message "Starting MS- DOS..." appears. The computer system should report "MS-DOS will prompt you to confirm each CONFIG.SYS command". At this point, press "Y" for each line you wish to load. Load one additional line each time and retest the mouse. When the keypad fails to load, or the symptom reappears, it is most likely the last line loaded is causing the conflict. Contact the vendor of the software for an update or more information about the software. Sometimes loading these utilities in a different order is all that is required to resolve the conflict. In general, we recommend loading the keypad driver before any other resident software. DOS 5.0 or earlier Using DOS 5.0 or earlier, copy the AUTOEXEC.BAT and CONFIG.SYS from the hard drive to the "boot disk" in the A: drive. Now open these files in a text editor and place a "REM" in front of any lines that load memory resident software. Restart the computer system with this boot disk and retest the mouse. If the mouse now loads correctly, remove the "REM' statements one line at a time, restart the system, and recheck the keypad device each time. When the conflict reappears, it will most likely be the last line reinstated which is causing the conflict. Contact the vendor of the software for an update or more information. Sometimes loading these utilities in a different order is all that is required to resolve the conflict. In general, we recommend loading the DOS keypad before any other resident software. Other Notes and Considerations 1. The DOS driver commands are all located on the diskette in a DOSDRV subdirectory. During the installation once the com port is selected by the user and confirmed during the test, the installation simply copies the appropriate driver file to c:\keypad subdirectory. For example, a COM1 selection would copy KEY1C.COM to C:\KEYPAD\KEYS.COM file. This is a back door method of swapping the driver for another one to use a different COM port. 2. The installation simply adds a line to the Autoexec.bat file c:\keypad\keys to execute the DOS driver. If the keypad works when this command is typed from the C:\ prompt manually, but not when MS- DOS is booted, then there is something in Autoexec causing this file to not get executed. Try editing Autoexec.bat and moving the line to the top of the file. 3. If the install fails refer to the two notes above (1) copy the correct file from the \DOSDRV directory on the disk to a folder on your harddrive, (2) add the command to the autoexec.bat file. For example, first create a folder named \KEYPAD on your C: drive. Second, if your serial port is designated as COM1, copy the KEY1C.COM to your hard drive. Lastly, add the command c:\KEYPAD\KEY1C to your autoexec.bat file. 4. The DOS driver has been tested under MS-DOS v6.22, as well as the Windows 95 and Windows 98 MS-DOS v4.xx. 5. The COM ports do need to be configured for standard IRQ and I/O resources. The driver will be unable to find a COM 1 on IRQ5 for example. The correct setting for COM1 is IRQ 4 and I/O 03F8 and for COM2 is IRQ3 and I/O 02F8. 6. If the serial ports appear to be correctly configured, then it is possible that a modem or other internal device in the system may be interfering with the serial port the keypad is trying to use. Try removing these devices to see if the conflict is eliminated. If the keypad works when these devices are removed, add them back one by one, and verify the keypad still works. If the keypad fails again, the last device reinstalled is most likely the conflicting hardware. Check the settings of this device and be sure it is not set to the same hardware settings as the serial port being used. If the symptoms continue, try the keypad on another system to verify that the keypad is working properly.
Load more

Recommended publications
  • Active@ Boot Disk User Guide Copyright © 2008, LSOFT TECHNOLOGIES INC
    Active@ Boot Disk User Guide Copyright © 2008, LSOFT TECHNOLOGIES INC. All rights reserved. No part of this documentation may be reproduced in any form or by any means or used to make any derivative work (such as translation, transformation, or adaptation) without written permission from LSOFT TECHNOLOGIES INC. LSOFT TECHNOLOGIES INC. reserves the right to revise this documentation and to make changes in content from time to time without obligation on the part of LSOFT TECHNOLOGIES INC. to provide notification of such revision or change. LSOFT TECHNOLOGIES INC. provides this documentation without warranty of any kind, either implied or expressed, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. LSOFT may make improvements or changes in the product(s) and/or the program(s) described in this documentation at any time. All technical data and computer software is commercial in nature and developed solely at private expense. As the User, or Installer/Administrator of this software, you agree not to remove or deface any portion of any legend provided on any licensed program or documentation contained in, or delivered to you in conjunction with, this User Guide. LSOFT.NET logo is a trademark of LSOFT TECHNOLOGIES INC. Other brand and product names may be registered trademarks or trademarks of their respective holders. 2 Active@ Boot Disk User Guide Contents 1.0 Product Overview ..........................................................................................................
    [Show full text]
  • Illustrated Tutorial: Creating a Bootable USB Flash Drive for Windows XP
    Illustrated tutorial: Creating a bootable Version 1.0 February 15, 2007 USB flash drive for Windows XP By Greg Shultz The ability to boot Windows XP from a USB Flash Drive (UFD) offers endless possibilities. For example, you might make an easy-to-use troubleshooting tool for booting and analyzing seemingly dead PCs. Or you could transport your favorite applications back and forth from home to work without having to install them on both PCs. However, before you can create a bootable UFD, you must clear a few hurdles. You saw that one coming didn’t you? The first hurdle is having a PC in which the BIOS will allow you to configure the USB port to act as a bootable device. The second hurdle is having a UFD that that will work as a bootable device and that’s large enough and fast enough to boot an operating system such as Windows XP. The third hurdle is finding a way to condense and install Windows XP on a UFD. If you have a PC that was manufactured in the last several years, chances are that its BIOS will allow you to configure the USB port to act as a bootable device. If you have a good qual- ity UFD that’s at least 512 KB and that was manufactured in the last couple of years, you’ve probably cleared the second hurdle. And once you’ve cleared those first two hur- dles, the third one is a piece of cake. All you have to do is download and run some free soft- ware to create the bootable UFD.
    [Show full text]
  • Volatility: Part 2 – Malware in Hiberfil.Sys
    Patrick Leahy Center for Digital Investigation (LCDI) Volatility: Part 2 – Malware in hiberfil.sys Written by Dan Doonan and Catherine Stamm Researched by Dan Doonan, Connor Hicks, David Leberfinger, and Catherine Stamm The Senator Patrick Leahy Center for Digital Investigation Champlain College December 4, 2012 Version: 0.1 – Volatility: – Review Date: 12/4/2012 Page 1 of 6 Patrick Leahy Center for Digital Investigation (LCDI) Disclaimer: This document contains information based on research that has been gathered by employee(s) of The Senator Patrick Leahy Center for Digital Investigation (LCDI). The data contained in this project is submitted voluntarily and is unaudited. Every effort has been made by LCDI to assure the accuracy and reliability of the data contained in this report. However, LCDI nor any of our employees make no representation, warranty or guarantee in connection with this report and hereby expressly disclaims any liability or responsibility for loss or damage resulting from use of this data. Information in this report can be downloaded and redistributed by any person or persons. Any redistribution must maintain the LCDI logo and any references from this report must be properly annotated. Contents 1 Introduction ................................................................................................................................3 1.1 Background .........................................................................................................................3 1.2 Research Questions ..............................................................................................................3
    [Show full text]
  • Chapter 3. Booting Operating Systems
    Chapter 3. Booting Operating Systems Abstract: Chapter 3 provides a complete coverage on operating systems booting. It explains the booting principle and the booting sequence of various kinds of bootable devices. These include booting from floppy disk, hard disk, CDROM and USB drives. Instead of writing a customized booter to boot up only MTX, it shows how to develop booter programs to boot up real operating systems, such as Linux, from a variety of bootable devices. In particular, it shows how to boot up generic Linux bzImage kernels with initial ramdisk support. It is shown that the hard disk and CDROM booters developed in this book are comparable to GRUB and isolinux in performance. In addition, it demonstrates the booter programs by sample systems. 3.1. Booting Booting, which is short for bootstrap, refers to the process of loading an operating system image into computer memory and starting up the operating system. As such, it is the first step to run an operating system. Despite its importance and widespread interests among computer users, the subject of booting is rarely discussed in operating system books. Information on booting are usually scattered and, in most cases, incomplete. A systematic treatment of the booting process has been lacking. The purpose of this chapter is to try to fill this void. In this chapter, we shall discuss the booting principle and show how to write booter programs to boot up real operating systems. As one might expect, the booting process is highly machine dependent. To be more specific, we shall only consider the booting process of Intel x86 based PCs.
    [Show full text]
  • Supporting Operating System Installation | 3
    cc01SupportingOperatingSystemInstallation.indd01SupportingOperatingSystemInstallation.indd PagePage 1 08/10/1408/10/14 4:334:33 PMPM martinmartin //208/WB01410/XXXXXXXXXXXXX/ch01/text_s208/WB01410/XXXXXXXXXXXXX/ch01/text_s Supporting Operating LESSON 1 System Installation 70-688 EXAM OBJECTIVE Objective 1.1 – Support operating system installation. This objective may include but is not limited to: Support Windows To Go; manage boot settings, including native virtual hard disk (VHD) and multi-boot; manage desktop images; customize a Windows installation by using Windows Preinstallation Environment (PE). LESSON HEADING EXAM OBJECTIVE Using a Troubleshooting Methodology Viewing System Information Using the Event Viewer Supporting Windows To Go Support Windows To Go Creating and Deploying a Windows To Go Workspace Drive Booting into a Windows To Go Workspace Managing Boot Settings Manage boot settings, including native virtual hard disk (VHD) and multi-boot Using BCDEdit and BCDBoot Configuring a Multi-Boot System Manage boot settings, including native virtual hard disk (VHD) and multi-boot Configuring a Native VHD Boot File Manage boot settings, including native virtual hard disk (VHD) and multi-boot Understanding VHD Formats Installing Windows 8.1 on a VHD with an Operating System Present Installing Windows 8.1 on a VHD Without an Operating SystemCOPYRIGHTED Present MATERIAL Managing Desktop Images Manage desktop images Capturing Images Modifying Images using DISM Customizing a Windows Installation by Using Windows PE Customize a Windows
    [Show full text]
  • Linux Boot Loaders Compared
    Linux Boot Loaders Compared L.C. Benschop May 29, 2003 Copyright c 2002, 2003, L.C. Benschop, Eindhoven, The Netherlands. Per- mission is granted to make verbatim copies of this document. This is version 1.1 which has some minor corrections. Contents 1 introduction 2 2 How Boot Loaders Work 3 2.1 What BIOS does for us . 3 2.2 Parts of a boot loader . 6 2.2.1 boot sector program . 6 2.2.2 second stage of boot loader . 7 2.2.3 Boot loader installer . 8 2.3 Loading the operating system . 8 2.3.1 Loading the Linux kernel . 8 2.3.2 Chain loading . 10 2.4 Configuring the boot loader . 10 3 Example Installations 11 3.1 Example root file system and kernel . 11 3.2 Linux Boot Sector . 11 3.3 LILO . 14 3.4 GNU GRUB . 15 3.5 SYSLINUX . 18 3.6 LOADLIN . 19 3.7 Where Can Boot Loaders Live . 21 1 4 RAM Disks 22 4.1 Living without a RAM disk . 22 4.2 RAM disk devices . 23 4.3 Loading a RAM disk at boot time . 24 4.4 The initial RAM disk . 24 5 Making Diskette Images without Diskettes 25 6 Hard Disk Installation 26 7 CD-ROM Installation 29 8 Conclusions 31 1 introduction If you use Linux on a production system, you will only see it a few times a year. If you are a hobbyist who compiles many kernels or who uses many operating systems, you may see it several times per day.
    [Show full text]
  • S.Ha.R.K. Installation Howto Tools Knoppix Live CD Linux Fdisk HD
    S.Ha.R.K. Installation Tools HowTo • Linux fdisk utility • A copy of Linux installation CD • A copy of Windows® installation CD Tullio Facchinetti University of Pavia - Italy • Some FreeDOS utilities • A copy of S.Ha.R.K. S.Ha.R.K. Workshop S.Ha.R.K. Workshop Knoppix live CD Linux fdisk Command action a toggle a bootable flag Download ISO from b edit bsd disklabel c toggle the dos compatibility flag d delete a partition http://www.knoppix.org l list known partition types m print this menu n add a new partition o create a new empty DOS partition table p print the partition table q quit without saving changes • boot from CD s create a new empty Sun disklabel t change a partition's system id • open a command shell u change display/entry units v verify the partition table • type “su” (become root ), password is empty w write table to disk and exit x extra functionality (experts only) • start fdisk (ex. fdisk /dev/hda ) Command (m for help): S.Ha.R.K. Workshop S.Ha.R.K. Workshop HD partitioning HD partitioning 1st FreeDOS FAT32 FreeDOS must be installed Primary 2nd Windows® FAT32 into the first partition of your HD or it may not boot 3rd Linux / extX Data 1 FAT32 format data partitions as ... Extended FAT32, so that you can share Data n FAT32 your data between Linux, last Linux swap swap Windows® and FreeDOS S.Ha.R.K. Workshop S.Ha.R.K. Workshop 1 HD partitioning Windows ® installation FAT32 Windows® partition type Install Windows®..
    [Show full text]
  • Flashboot User Manual
    FlashBoot User Manual © 2015 Mikhail Kupchik Contents 3 Table of Contents Foreword 0 Part I Introduction 5 1 Product................................................................................................................................... Overview 5 2 Why USB................................................................................................................................... Flash Disks? 5 3 Why FlashBoot?................................................................................................................................... 6 4 System................................................................................................................................... Requirements 7 5 Limitations................................................................................................................................... of Demo Version 8 6 Demo Version................................................................................................................................... -> Full Version 8 7 Support................................................................................................................................... & Feedback 8 Part II CD/DVD to USB conversions 9 1 Install ...................................................................................................................................full Win8/8.1/10 -> USB [BIOS mode] 9 2 Install................................................................................................................................... full
    [Show full text]
  • Active Boot Disk 12 Iso Download Active Boot Disk
    active boot disk 12 iso download Active boot disk. Active@ Boot Disk provides an impressive range of utilities for your hard disk and other storage devices. PC Win Boot. PC Win Boot is a System Rescue disc builder that enables you to make your own boot disk in minutes. Active Boot Disk. Active@ Boot Disk provides an impressive range of utilities for your hard disk and other storage devices. Similar choice. Programs for query ″active boot disk″ Acronis True Image Home. Acronis True Image, the most reliable, easy-to-use and secure personal backup software and the only backup that actively defends your files against ransomware. lost. Acronis Active Protection 2.0 . attacks. Active Disk Cloning - . create boot media . Active@ Boot Disk Creator. Active@ Boot Disk is a complete and functioning computer operating system on CD, DVD, or USB drive. Active @ Boot Disk is a complete . such as Active @ Disk Image, . DoD-compliant disk erasing . Active@ Partition Recovery. Active@ Partition Recovery allows you to recover deleted or damaged hard disk partitions from within either Windows or DOS. purposes. Active @ Partition . tools, Active @ Partition . and a boot disk creator. The . Active@ Disk Image. Active@ Disk Image is a PC disk image software that can do a backup as well as clone the full hard drive. Active @ Disk Image is a PC disk image . after booting up from Active @ Boot Disk Lite . Active@ LiveCD. Ultimate Boot Disk Active@ LiveCD combines a number of powerful tools that will enable you recover lost data . Ultimate Boot Disk Active @ LiveCD combines a . PTDD Super Fdisk.
    [Show full text]
  • Virtual Machine Part II: Program Control
    Virtual Machine Part II: Program Control Building a Modern Computer From First Principles www.nand2tetris.org Elements of Computing Systems, Nisan & Schocken, MIT Press, www.nand2tetris.org , Chapter 8: Virtual Machine, Part II slide 1 Where we are at: Human Abstract design Software abstract interface Thought Chapters 9, 12 hierarchy H.L. Language Compiler & abstract interface Chapters 10 - 11 Operating Sys. Virtual VM Translator abstract interface Machine Chapters 7 - 8 Assembly Language Assembler Chapter 6 abstract interface Computer Machine Architecture abstract interface Language Chapters 4 - 5 Hardware Gate Logic abstract interface Platform Chapters 1 - 3 Electrical Chips & Engineering Hardware Physics hierarchy Logic Gates Elements of Computing Systems, Nisan & Schocken, MIT Press, www.nand2tetris.org , Chapter 8: Virtual Machine, Part II slide 2 The VM language Goal: Complete the specification and implementation of the VM model and language Arithmetic / Boolean commands Program flow commands add label (declaration) sub goto (label) neg eq if-goto (label) gt previous this lecture lecture lt Function calling commands and or function (declaration) not call (a function) Memory access commands pop x (pop into x, which is a variable) return (from a function) push y (y being a variable or a constant) Method: (a) specify the abstraction (model’s constructs and commands) (b) propose how to implement it over the Hack platform. Elements of Computing Systems, Nisan & Schocken, MIT Press, www.nand2tetris.org , Chapter 8: Virtual Machine, Part
    [Show full text]
  • Application Note 007 at Command Reference Guide - ETH-M-LORA-AX
    Application Note 007 AT Command Reference Guide - ETH-M-LORA-AX Legal Notices: AT Command Reference Guide for Ethertronics LoRa modules ETH-M-LORA-AX Copyright © 2016 – 2017 by Ethertronics Inc. All rights reserved. The information presented in this document does not form part of any contract and may be changed without notice. No liability will be accepted by Ethertronics for any consequence of its use, and Ethertronics assumes no responsibility or liability whatsoever for any failure or unexpected operation resulting from using the information in this document. Table of Contents Preface .............................................................................. 1 AT+LORA@IM#RESET .................................................. 24 Definitions ....................................................................... 1 AT+LORA@IM#RUNDEBUG ............................................ 25 AT Command Line Syntax ..................................................... 1 AT+LORA@IM%THR ..................................................... 25 AT command prefix ........................................................ 1 AT+LORA@IM%RESULT ................................................. 26 Prefix extension ............................................................ 1 AT+LORA@IM%VERSION ............................................... 26 AT command body ......................................................... 1 AT+LORA@IM%CTRLFLAG ............................................. 27 Module name ..............................................................
    [Show full text]
  • Patching DOS 5 and up for the Pcjr
    Patching DOS 5 and up for the PCjr November 29th, 2020 [email protected] Background Patching DOS 5+ Theory of operation Preparing a DOS 5 disk Patching the DOS 5+ disk Create FORMATJR.COM Hard drive installation Fdisk and create a DOS partition Format the hard drive partition Appendix A - Wiping out a boot sector Background The PCjr shipped in 1983 in two configurations: a 64KB machine with no floppy disk drive or a 128KB machine with a single floppy disk drive. The architecture of the machine has the video buffer “borrow” memory from the main memory of the machine. With the standard 16KB video buffer this makes the available RAM either 48KB or 112KB. IBM never offered a hard drive solution. Adding extra memory to a PCjr became possible, but it required a device driver to be loaded at boot time. Microsoft, Tecmar, and other vendors provided device drivers with their memory expansions. The best of the device drivers was a shareware program called jrConfig written by Larry Newcomb. jrConfig can be downloaded from http://www.brutman.com/PCjr/pcjr_downloads.html. The original version of DOS that shipped with the PCjr was PC DOS 2.1. DOS versions 2.1 through 3.3 work on the machine as is. To run DOS 5 or later two things are required: ● Extra memory is required. While extra memory is useful for DOS 2.1 - 3.3, DOS 5 won’t even boot on a small system. I BM formally states the requirement is 512KB and the PCjr is not supported. ● DOS 5 can be patched to work on a PCjr even though it is not supported.
    [Show full text]