DOCSLIB.ORG

Version 6.5, Still No Sound Support for Legacy Apps

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Version 6.5, Still No Sound Support for Legacy Apps Yeah, actually the problem is with DOS games (wink). We know DOSBOX is capable of doing the job for a long time, but still it just can't make every those good oldies run like they did in a real 80486 or 586 PC. Thus, I, along with some WS users (though little,) have been looking for one day that VMWare can make these games alive again. But every time just as the newer version came out, it broke my heart after every failed attempt to get the sound functioning under DOS. Now it's 2009, and the version number comes to 6.5...a respectful one considering the long period after WS 4.52, isn't it? So here we are my last test on VMWare Workstation's ability to support sounds under MS-DOS (BTW, I have not posted on VMTN forums for 4 years.) If my memory serves well, WS uses AudioPCI as the primary sound emulation base. I snapped the following two files back to prepare for the test: es1371driver.zip SBPCI128Setupus_w9x.exe OK, let's begin with the story about the first one. Just as I finished installing WIN98, I ran the setup program extracted from the file. Upon seeing the successful installation, I was happy. But after clicking into Device Manager the same old nightmare came: AudioPCI Legacy Drive wasn't working because no free IRQs available to use. This time I investigated carefully and executed the Hardware Troubleshooting Wizard. After following the suggestion to close a device which it listed to release a specific IRQ number (chose the BusLogic SCSI Adaptor,) still didn't work for the wizard telling me that device wouldn't discard its IRQ. The next choice was the LPT1 printer port. This time it worked. After two restarts of Windows the Legacy Drive looked normal in Device Manager. But when I headed to MS-DOS mode in WIN98 the VM halted after APINIT.COM's self-configuration failed. No, not again. There was one hope remaining: testing in the Command Prompt mode. Different results were found under two sets of settings: ● Starting with no SMARTDRV ● Starting with SMARTDRV The error messages generated from each above are listed in the second post. Note that the change of EMS or SNDSCAPE.INI (located in C:\WINDOWS for this example) didn't affect the results. The story about es1371driver.zip ends. Got a BSOD and failed to install the device...that's the poor end of the second story! Thank you for listening to a bored guy's chatter. ▲Sound Blaster PCI128 driver cannot be used within a Windows 98 VM. Error Messages [MS-DOS CONFIGURATIONS] [CONFIG.SYS] DEVICEHIGH=C:\WINDOWS\HIMEM.SYS DEVICEHIGH=C:\WINDOWS\EMM386.EXE 4096 [AUTOEXEC.BAT] SET BLASTER=A220 I7 D1 T2 SET SNDSCAPE=C:\WINDOWS LH C:\EAPCI\APINIT.COM [ERROR WITH SMARTDRV LOADED] Ensoniq AudioPCI Initialization Driver, Ver 4.26. Copyright(c) 1996-1998, Creative Technology Ltd., All Rights Reserved. PCI Audio @ Port 2000, IRQ 5 DOS/4GW error (2001): exception 0Eh (page fault) at 148:0043C38A TSF32: prev_tsf32 5120 SS 150 DS 150 ES 150 FS 0 GS 20 EAX 18101C EBX 194 ECX 180000 EDX 11A000 ESI 181000 EDI 1AE067 EBP 27000 ESP 45F62C CS:IP 148:0043C38A ID 0E COD 0 FLG 10202 CS= 148, USE32, page granular, limit FFFFFFFF, base 0, acc CF9B SS= 150, USE32, page granular, limit FFFFFFFF, base 0, acc CF93 DS= 150, USE32, page granular, limit FFFFFFFF, base 0, acc CF93 ES= 150, USE32, page granular, limit FFFFFFFF, base 0, acc CF93 FS= 0, USE16, byte granular, limit 0, base 13, acc 0 GS= 20, USE16, byte granular, limit FFFF, base 23C30, acc 93 CR0: PG:1 ET:1 TS:0 EM:0 MP:0 PE:1 CR2: 18101C CR3: 26000 Crash address (unrelocated) = 1:0000038A PCI audio driver NOT loading. [ERROR WITH NO SMARTDRV] Ensoniq AudioPCI Initialization Driver, Ver 4.26. Copyright(c) 1996-1998, Creative Technology Ltd., All Rights Reserved. PCI Audio @ Port 2000, IRQ 5 error: Could not allocate code/patch RAM below 4 Mbyte boundary. Try loading APINIT.COM before SMARTDRV.EXE or minimizing VDISK RAM. PCI audio driver NOT loading. .
Recommended publications
  • Linux Sound Subsystem Documentation Release 4.13.0-Rc4+

    Linux Sound Subsystem Documentation Release 4.13.0-Rc4+

    Linux Sound Subsystem Documentation Release 4.13.0-rc4+ The kernel development community Sep 05, 2017 CONTENTS 1 ALSA Kernel API Documentation 1 1.1 The ALSA Driver API ............................................ 1 1.2 Writing an ALSA Driver ........................................... 89 2 Designs and Implementations 145 2.1 Standard ALSA Control Names ...................................... 145 2.2 ALSA PCM channel-mapping API ..................................... 147 2.3 ALSA Compress-Offload API ........................................ 149 2.4 ALSA PCM Timestamping ......................................... 152 2.5 ALSA Jack Controls ............................................. 155 2.6 Tracepoints in ALSA ............................................ 156 2.7 Proc Files of ALSA Drivers ......................................... 158 2.8 Notes on Power-Saving Mode ....................................... 161 2.9 Notes on Kernel OSS-Emulation ..................................... 161 2.10 OSS Sequencer Emulation on ALSA ................................... 165 3 ALSA SoC Layer 171 3.1 ALSA SoC Layer Overview ......................................... 171 3.2 ASoC Codec Class Driver ......................................... 172 3.3 ASoC Digital Audio Interface (DAI) .................................... 174 3.4 Dynamic Audio Power Management for Portable Devices ...................... 175 3.5 ASoC Platform Driver ............................................ 180 3.6 ASoC Machine Driver ............................................ 181 3.7 Audio Pops
  • Running Telecom/TT-Link and Trafman Under Windows 7 (And Up) Using Dosbox

    Running Telecom/TT-Link and Trafman Under Windows 7 (And Up) Using Dosbox

    Running Telecom/TT-Link and Trafman under Windows 7 (and up) using DOSbox 3/31/2014 Documentation written for: Telecom/TT-Link V3.97 or later. TrafMan V6.43 or later. DOSbox V0.74 or later. COM/IP V4.9.5 or later. TrafMan & Telecom/TT-Link on Windows 7 Page 1 of 10 I. Introduction and Initial Emulator Setup Microsoft discontinued support for MS-DOS level programs starting with Windows 7. This has made the operation of Telecom/TT-Link and TrafMan on systems with a Windows 7 or later operating systems problematical, to say the least. However, it is possible to achieve functionality (with some limits) even on a Windows 7 computer by using what is known as a “DOS Emulator”. Emulator’s simulate the conditions of an earlier operating system on a later one. For example, one of the most common emulators is called DOSbox (http://sourceforge.net/projects/dosbox/ ) and it is available as a free download for both PC and Mac computers. DOSbox creates an artificial MS-DOS level environment on a Windows 7 computer. Inside this environment you can run most DOS programs, including TrafMan and Telecom/TT-Link. This document describes how to utilize the DOSbox emulator for running Telecom/TT-Link and TrafMan. It should be noted, however, that other emulators may also work and this document can serve as a guide for setting up and using similar DOS emulators as they are available. Initial DOSbox Emulator Setup: 1) Download the latest release of DOSbox (0.74 or later) to your PC and install it.
  • Sound-HOWTO.Pdf

    Sound-HOWTO.Pdf

    The Linux Sound HOWTO Jeff Tranter [email protected] v1.22, 16 July 2001 Revision History Revision 1.22 2001−07−16 Revised by: jjt Relicensed under the GFDL. Revision 1.21 2001−05−11 Revised by: jjt This document describes sound support for Linux. It lists the supported sound hardware, describes how to configure the kernel drivers, and answers frequently asked questions. The intent is to bring new users up to speed more quickly and reduce the amount of traffic in the Usenet news groups and mailing lists. The Linux Sound HOWTO Table of Contents 1. Introduction.....................................................................................................................................................1 1.1. Acknowledgments.............................................................................................................................1 1.2. New versions of this document.........................................................................................................1 1.3. Feedback...........................................................................................................................................2 1.4. Distribution Policy............................................................................................................................2 2. Sound Card Technology.................................................................................................................................3 3. Supported Hardware......................................................................................................................................4
  • Virtualization Technologies Overview Course: CS 490 by Mendel

    Virtualization Technologies Overview Course: CS 490 by Mendel

    Virtualization technologies overview Course: CS 490 by Mendel Rosenblum Name Can boot USB GUI Live 3D Snaps Live an OS on mem acceleration hot of migration another ory runnin disk alloc g partition ation system as guest Bochs partially partially Yes No Container s Cooperati Yes[1] Yes No No ve Linux (supporte d through X11 over networkin g) Denali DOSBox Partial (the Yes No No host OS can provide DOSBox services with USB devices) DOSEMU No No No FreeVPS GXemul No No Hercules Hyper-V iCore Yes Yes No Yes No Virtual Accounts Imperas Yes Yes Yes Yes OVP (Eclipse) Tools Integrity Yes No Yes Yes No Yes (HP-UX Virtual (Integrity guests only, Machines Virtual Linux and Machine Windows 2K3 Manager in near future) (add-on) Jail No Yes partially Yes No No No KVM Yes [3] Yes Yes [4] Yes Supported Yes [5] with VMGL [6] Linux- VServer LynxSec ure Mac-on- Yes Yes No No Linux Mac-on- No No Mac OpenVZ Yes Yes Yes Yes No Yes (using Xvnc and/or XDMCP) Oracle Yes Yes Yes Yes Yes VM (manage d by Oracle VM Manager) OVPsim Yes Yes Yes Yes (Eclipse) Padded Yes Yes Yes Cell for x86 (Green Hills Software) Padded Yes Yes Yes No Cell for PowerPC (Green Hills Software) Parallels Yes, if Boot Yes Yes Yes DirectX 9 Desktop Camp is and for Mac installed OpenGL 2.0 Parallels No Yes Yes No partially Workstati on PearPC POWER Yes Yes No Yes No Yes (on Hypervis POWER 6- or (PHYP) based systems, requires PowerVM Enterprise Licensing) QEMU Yes Yes Yes [4] Some code Yes done [7]; Also supported with VMGL [6] QEMU w/ Yes Yes Yes Some code Yes kqemu done [7]; Also module supported
  • Linux Hardware Compatibility HOWTO

    Linux Hardware Compatibility HOWTO

    Linux Hardware Compatibility HOWTO Steven Pritchard Southern Illinois Linux Users Group [email protected] 3.1.5 Copyright © 2001−2002 by Steven Pritchard Copyright © 1997−1999 by Patrick Reijnen 2002−03−28 This document attempts to list most of the hardware known to be either supported or unsupported under Linux. Linux Hardware Compatibility HOWTO Table of Contents 1. Introduction.....................................................................................................................................................1 1.1. Notes on binary−only drivers...........................................................................................................1 1.2. Notes on commercial drivers............................................................................................................1 1.3. System architectures.........................................................................................................................1 1.4. Related sources of information.........................................................................................................2 1.5. Known problems with this document...............................................................................................2 1.6. New versions of this document.........................................................................................................2 1.7. Feedback and corrections..................................................................................................................3 1.8. Acknowledgments.............................................................................................................................3
  • International Journal for Scientific Research & Development

    International Journal for Scientific Research & Development

    IJSRD - International Journal for Scientific Research & Development| Vol. 2, Issue 02, 2014 | ISSN (online): 2321-0613 Virtualization : A Novice Approach Amithchand Sheety1 Mahesh Poola2 Pradeep Bhat3 Dhiraj Mishra4 1,2,3,4 Padmabhushan Vasantdada Patil Pratishthan’s College of Engineering, Eastern Express Highway, Near Everard Nagar, Sion-Chunabhatti, Mumbai-400 022, India. Abstract— Virtualization provides many benefits – greater as CPU. Although hardware is consolidated, typically efficiency in CPU utilization, greener IT with less power OS are not. Instead, each OS running on a physical consumption, better management through central server becomes converted to a distinct OS running inside environment control, more availability, reduced project a virtual machine. The large server can "host" many such timelines by eliminating hardware procurement, improved "guest" virtual machines. This is known as Physical-to- disaster recovery capability, more central control of the Virtual (P2V) transformation. desktop, and improved outsourcing services. With these 2) Consolidating servers can also have the added benefit of benefits, it is no wondered that virtualization has had a reducing energy consumption. A typical server runs at meteoric rise to the 2008 Top 10 IT Projects! This white 425W [4] and VMware estimates an average server paper presents a brief look at virtualization, its benefits and consolidation ratio of 10:1. weaknesses, and today’s “best practices” regarding 3) A virtual machine can be more easily controlled and virtualization. inspected from outside than a physical one, and its configuration is more flexible. This is very useful in I. INTRODUCTION kernel development and for teaching operating system Virtualization, in computing, is a term that refers to the courses.
  • MX-19.2 Users Manual

    MX-19.2 Users Manual

    MX-19.2 Users Manual v. 20200801 manual AT mxlinux DOT org Ctrl-F = Search this Manual Ctrl+Home = Return to top Table of Contents 1 Introduction...................................................................................................................................4 1.1 About MX Linux................................................................................................................4 1.2 About this Manual..............................................................................................................4 1.3 System requirements..........................................................................................................5 1.4 Support and EOL................................................................................................................6 1.5 Bugs, issues and requests...................................................................................................6 1.6 Migration............................................................................................................................7 1.7 Our positions......................................................................................................................8 1.8 Notes for Translators.............................................................................................................8 2 Installation...................................................................................................................................10 2.1 Introduction......................................................................................................................10
  • Alsa-Sound-Mini-HOWTO

    Alsa-Sound-Mini-HOWTO

    Alsa−sound−mini−HOWTO Alsa−sound−mini−HOWTO Table of Contents Alsa−sound−mini−HOWTO..............................................................................................................................1 Valentijn Sessink valentyn@alsa−project.org.........................................................................................1 1. Introduction..........................................................................................................................................1 2. NOWTO − a quick install guide..........................................................................................................1 3. Before you start....................................................................................................................................1 4. How to install ALSA sound drivers.....................................................................................................1 5. Loading the driver................................................................................................................................1 6. Testing and using.................................................................................................................................2 7. Tips and Troubleshooting....................................................................................................................2 1. Introduction..........................................................................................................................................2 1.1 Acknowledgments..............................................................................................................................2
  • Download the Index

    Download the Index

    41_067232945x_index.qxd 10/5/07 1:09 PM Page 667 Index NUMBERS 3D video, 100-101 10BaseT Ethernet NIC (Network Interface Cards), 512 64-bit processors, 14 100BaseT Ethernet NIC (Network Interface Cards), 512 A A (Address) resource record, 555 AbiWord, 171-172 ac command, 414 ac patches, 498 access control, Apache web server file systems, 536 access times, disabling, 648 Accessibility module (GNOME), 116 ACPI (Advanced Configuration and Power Interface), 61-62 active content modules, dynamic website creation, 544 Add a New Local User screen, 44 add command (CVS), 583 address books, KAddressBook, 278 Administrator Mode button (KDE Control Center), 113 Adobe Reader, 133 AFPL Ghostscript, 123 41_067232945x_index.qxd 10/5/07 1:09 PM Page 668 668 aggregators aggregators, 309 antispam tools, 325 aKregator (Kontact), 336-337 KMail, 330-331 Blam!, 337 Procmail, 326, 329-330 Bloglines, 338 action line special characters, 328 Firefox web browser, 335 recipe flags, 326 Liferea, 337 special conditions, 327 Opera web browser, 335 antivirus tools, 331-332 RSSOwl, 338 AP (Access Points), wireless networks, 260, 514 aKregator webfeeder (Kontact), 278, 336-337 Apache web server, 529 album art, downloading to multimedia dynamic websites, creating players, 192 active content modules, 544 aliases, 79 CGI programming, 542-543 bash shell, 80 SSI, 543 CNAME (Canonical Name) resource file systems record, 555 access control, 536 local aliases, email server configuration, 325 authentication, 536-538 allow directive (Apache2/httpd.conf), 536 installing Almquist shells
  • Linux Hardware Compatibility HOWTO Linux Hardware Compatibility HOWTO

    Linux Hardware Compatibility HOWTO Linux Hardware Compatibility HOWTO

    Linux Hardware Compatibility HOWTO Linux Hardware Compatibility HOWTO Table of Contents Linux Hardware Compatibility HOWTO........................................................................................................1 Patrick Reijnen, <[email protected] (remove both "antispam.")>..1 1.Introduction...........................................................................................................................................1 2.Computers/Motherboards/BIOS...........................................................................................................1 3.Laptops..................................................................................................................................................1 4.CPU/FPU..............................................................................................................................................1 5.Memory.................................................................................................................................................1 6.Video cards...........................................................................................................................................2 7.Controllers (hard drive).........................................................................................................................2 8.Controllers (hard drive RAID)..............................................................................................................2 9.Controllers (SCSI)................................................................................................................................2
  • Challenges in Firmware Re-Hosting, Emulation, and Analysis

    Challenges in Firmware Re-Hosting, Emulation, and Analysis

    Challenges in Firmware Re-Hosting, Emulation, and Analysis CHRISTOPHER WRIGHT, Purdue University WILLIAM A. MOEGLEIN, Sandia National Laboratories SAURABH BAGCHI, Purdue University MILIND KULKARNI, Purdue University ABRAHAM A. CLEMENTS, Sandia National Laboratories System emulation and firmware re-hosting have become popular techniques to answer various security and performance related questions, such as, does a firmware contain security vulnerabilities or meet timing requirements when run on a specific hardware platform. While this motivation for emulation and binary analysis has previously been explored and reported, starting to either work or research in the field is difficult. To this end, we provide a comprehensive guide for the practitioner or system emulation researcher. We layout common challenges faced during firmware re-hosting, explaining successive steps and surveying common tools used to overcome these challenges. We provide classification techniques on five different axes, including emulator methods, system type, fidelity, emulator purpose, and control. These classifications and comparison criteria enable the practitioner to determine the appropriate tool for emulation. We use our classifications to categorize popular works in the field and present 28 common challenges faced when creating, emulating and analyzing a system, from obtaining firmwares to post emulation analysis. CCS Concepts: • Computer systems organization → Embedded and cyber-physical systems; Firmware; Embedded hardware; Embedded software; Real-time systems; • Hardware → Simulation and emulation. Additional Key Words and Phrases: Firmware re-hosting, system emulation, embedded systems, emulation fidelity, emulator classification, binary analysis, reverse engineering, emulation challenges ACM Reference Format: Christopher Wright, William A. Moeglein, Saurabh Bagchi, Milind Kulkarni, and Abraham A. Clements. 2020. Challenges in Firmware Re-Hosting, Emulation, and Analysis.
  • The Black Art of DOS Emulation on Raspberry Pi

    The Black Art of DOS Emulation on Raspberry Pi

    The Black Art of DOS emulation on Raspberry Pi Using FastDOSBox. By : [email protected] www.norisc-nofun.co.uk Version 1.0 – May 2013, Author : Franck / NoRiscNoFun , [email protected] – twitter : @Noriscnofun1 Table of Contents What is DOS emulation for who and for what ?..................................................................................3 Why choosing FastDOSBox for DOS emulation on the Rpi ?............................................................4 Installing FastDOSBox on the Raspberry Pi........................................................................................5 For RISC OS....................................................................................................................................5 For Raspbian....................................................................................................................................5 Recommended Raspberry Pi CPU settings for FastDOSBox..............................................................6 Recommended configuration settings for FastDOSBox......................................................................7 [dosbox] Section..............................................................................................................................7 [render] Section................................................................................................................................7 [cpu] Section....................................................................................................................................7