DOCSLIB.ORG

> What 3D Accelerators Does Carma Support

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
> What 3D Accelerators Does Carma Support -> What 3D accelerators does carma support? ------------------------------------------- 3Dfx only, but there is a 3Dfx patch for both the PC and the Mac. Cards that I have seen carma work on include (but are not limited to) The Diamon d Monster 3Dfx, Orchid rightous, Realvision Flash3D, Canopus Pure3D. Voodoo rush and Voodoo2 cards also work. Note that the Voodoo2 patch was created by a member of the Stainless Software programming team in his own time (for no reward), so be sure to thank Bruce. No other 3D chipsets are supported by carmageddon (There are no patches for card s like the rendition, powerVR, ViRGE, etc) Carmageddon 2 will have a full range of 3D accelerator support, Via direct3D The Mac 3Dfx patch was done by Techworks, and is unsupported (they don't give te chnical help) http://www.techworks.com/ ->What's a 3Dfx? ---------------- It's a 3D accelerator- a piece of hardware designed to do 3D math and draw polyg ons. However, a common mistake to assume all 3D accelerators are the same. They aren' t. The 3Dfx (Voodoo, voodoo rush, voodoo2) is a specific kind of 3D accelerator, and Carmageddon will only work with 3Dfx cards. (Voodoo/rush chipset) ->How do I know if I have a 3Dfx card? -------------------------------------- Well... if you have to ask, you don't have one. Sorry if it sounds blunt, but the 3Dfx cards are one of the more expensive 3D ac celerators, and you won't usually get one unless you specifically ask for it. This is further confused when computer stores say 'has a 3D card' without specif ying type, and it get worse when they say "3D effects card" or something similar ... Shops like to keep computer prices down, so they usually shove in an S3 ViRGE (o r something) and then make vague promises about 3D graphics capabilities. ->Why won't my non-3Dfx 3D accelerator work? -------------------------------------------- Games that offer 3D support can basically do it in one of 3 ways: 1) Direct3D- Microsoft's driver. It should be able to support all 3D cards (but in practice it rarely does) It is quite difficult to program in. 2) OpenGL- This is the library used by Quake/Q2 and many other games. Most good 3D accelerators (3Dfx, powerVR) work in OpenGL 3) Card specific- The game is modified for one specific chipset, using a dedicat ed library of functions. (For the 3Dfx, this is the Glide Libraries). This is wh at Carmageddon has, and it generally gives better picture quality and performanc e. Also, it's the only way of supporting 3D cards is DOS programs. (Like carmage ddon) ->How Do I install the 3Dfx patch? ---------------------------------- It should be already installed- this FAQ was included with the Auto installing p atch. ->I get a "Cannot Open General Settings File" error! ---------------------------------------------------- Make sure you have Glide 2.43 (or later) installed. If not, download it from www .3dfx.com ->The 3Dfx version doesn't work, help! -------------------------------------- Make sure you installed the patch correctly, And check you have the latest drive rs for your card. Make sure you have Glide 2.43 (or later) installed. If not, download it from www .3dfx.com If your card has more than 2 meg of texture memory (like the Pure3D), it will ca use problems. Before playing, type the line "set sst_tmumem_size=2" (This is already done for you if you run the batch file included) This sets the texture memory to 2 megabytes, and allows the 3Dfx version to run on one of these cards. Remember, you need at least 24 megabytes of RAM for the 3Dfx version, and prefer ably 32. The '-nocutscenes' switch will turn off the movies. If that's what's causing you r problem, it should let you play. ->The 3Dfx version crashes in win95, help! ------------------------------------------ The 3Dfx executables are DOS exe's. They do not run well under Win95. You should play in full DOS mode (re-boot to DOS mode), and remove all un-needed software from your autoexec.bat and config.sys files. (emm386.exe and your mous e driver are not needed and can be removed. Any TSR virus scanners and screen sa vers should also be removed.) ->The 3Dfx version has poor quality sound (or no sound) ------------------------------------------------------- This is an annoying little problem that seems to crop up for some people (usuall y with AWE sound cards). You might try downloading more recent software for your sound card (www.soundbla ster.com). An updated AWE TSR program may fix the sound. (Make sure you have the AWE TSR in your autoexec.bat) Additionally, check the sound volume in your DOS mixer. Set line-in and mic to z ero, all other should be at least half-way (depending on your speakers) There is also a 3Dfx sound fix patch that might help a little bit, and turning t he down 'sound detail' (in options) can help. Lastly, you can try putting the drivers CTSB16.SYS and CTMMSYS.SYS in your confi g.sys file. (Check sound card documentation if unsure) -------------------------------- RCS's Carmageddon 3Dfx FAQ, v1.3 Auto-Installer written by Robert Solomon ([email protected]) Note: It's not official, and questions about it should not be sent to SCi, Stain less or Interplay. The patch it installs isn't official, either, so any questions should be posted on a carmageddon message board. (You can send them to me if you prefer, but you' ll get a faster response on a message board.) Installer Version history: 0.9 Beta test, thanks Noodlez! 1.0 First release. Improved documentation, tweaked UI. 1.1c Upgraded to V2 alpha, greatly improved installation speed, added installati on progress graph. 1.2c More UI tweaks, updated FAQ's 1.2s Splat Pack version of above 1.3c Updated FAQ again, removed 2 meg limit for V1 cards (no longer needed). Add ed PIF shortcuts, HTML FAQ..
Load more

Recommended publications
  • Release Notes for X11R6.8.2 the X.Orgfoundation the Xfree86 Project, Inc
    Release Notes for X11R6.8.2 The X.OrgFoundation The XFree86 Project, Inc. 9February 2005 Abstract These release notes contains information about features and their status in the X.Org Foundation X11R6.8.2 release. It is based on the XFree86 4.4RC2 RELNOTES docu- ment published by The XFree86™ Project, Inc. Thereare significant updates and dif- ferences in the X.Orgrelease as noted below. 1. Introduction to the X11R6.8.2 Release The release numbering is based on the original MIT X numbering system. X11refers to the ver- sion of the network protocol that the X Window system is based on: Version 11was first released in 1988 and has been stable for 15 years, with only upwardcompatible additions to the coreX protocol, a recordofstability envied in computing. Formal releases of X started with X version 9 from MIT;the first commercial X products werebased on X version 10. The MIT X Consortium and its successors, the X Consortium, the Open Group X Project Team, and the X.OrgGroup released versions X11R3 through X11R6.6, beforethe founding of the X.OrgFoundation. Therewill be futuremaintenance releases in the X11R6.8.x series. However,efforts arewell underway to split the X distribution into its modular components to allow for easier maintenance and independent updates. We expect a transitional period while both X11R6.8 releases arebeing fielded and the modular release completed and deployed while both will be available as different consumers of X technology have different constraints on deployment. Wehave not yet decided how the modular X releases will be numbered. We encourage you to submit bug fixes and enhancements to bugzilla.freedesktop.orgusing the xorgproduct, and discussions on this server take place on <[email protected]>.
    [Show full text]
  • Powervr SGX Series5xt IP Core Family
    PowerVR SGX Series5XT IP Core Family The PowerVR™ SGX Series5XT Graphics Processing Unit (GPU) IP core family is a series Features of highly efficient graphics acceleration IP cores that meet the multimedia requirements of • Most comprehensive IP core family the next generation of consumer, communications and computing applications. and roadmap in the industry PowerVR SGX Series5XT architecture is fully scalable for a wide range of area and • USSE2 delivers twice the peak performance requirements, enabling it to target markets from low cost feature-rich mobile floating point and instruction multimedia products to very high performance consoles and computing devices. throughput of Series5 USSE • YUV and colour space accelerators The family incorporates the second-generation Universal Scalable Shader Engine (USSE2™), for improved performance with a feature set that exceeds the requirements of OpenGL 2.0 and Microsoft Shader • Upgraded PowerVR Series5XT Model 3, enabling 2D, 3D and general purpose (GP-GPU) processing in a single core. shader-driven tile-based deferred rendering (TBDR) architecture • Multi-processor options enable scalability to higher performance • Support for all industry standard PowerVR SGX Family mobile and desktop graphics APIs and operating sytems Series5XT SGX543MP1-16, SGX544MP1-16, SGX554MP1-16 • Fully backwards compatible with PowerVR MBX and SGX Series5 Series5 SGX520, SGX530, SGX531, SGX535, SGX540, SGX545 Benefits Multi-standard API and OS • Extensive product line supports all area/performance requirements OpenGL
    [Show full text]
  • GPU Developments 2018
    GPU Developments 2018 2018 GPU Developments 2018 © Copyright Jon Peddie Research 2019. All rights reserved. Reproduction in whole or in part is prohibited without written permission from Jon Peddie Research. This report is the property of Jon Peddie Research (JPR) and made available to a restricted number of clients only upon these terms and conditions. Agreement not to copy or disclose. This report and all future reports or other materials provided by JPR pursuant to this subscription (collectively, “Reports”) are protected by: (i) federal copyright, pursuant to the Copyright Act of 1976; and (ii) the nondisclosure provisions set forth immediately following. License, exclusive use, and agreement not to disclose. Reports are the trade secret property exclusively of JPR and are made available to a restricted number of clients, for their exclusive use and only upon the following terms and conditions. JPR grants site-wide license to read and utilize the information in the Reports, exclusively to the initial subscriber to the Reports, its subsidiaries, divisions, and employees (collectively, “Subscriber”). The Reports shall, at all times, be treated by Subscriber as proprietary and confidential documents, for internal use only. Subscriber agrees that it will not reproduce for or share any of the material in the Reports (“Material”) with any entity or individual other than Subscriber (“Shared Third Party”) (collectively, “Share” or “Sharing”), without the advance written permission of JPR. Subscriber shall be liable for any breach of this agreement and shall be subject to cancellation of its subscription to Reports. Without limiting this liability, Subscriber shall be liable for any damages suffered by JPR as a result of any Sharing of any Material, without advance written permission of JPR.
    [Show full text]
  • 3Dnow! Technology in Microsoft Directx
    AMD WHITE PAPER ™ 3DNow! Technology in Microsoft DirectX 6.0 Delivering Leading-Edge 3D Graphics Performance for the New Era of Realistic Computing ADVANCED MICRO DEVICES, INC. One AMD Place Sunnyvale, CA 94088 Contact: Dale Weisman Public Relations (512) 602-5820 Anne Camden Public Relations (512) 602-2120 Page 1 52588A May 28, 1998 AMD WHITE PAPER Overview This white paper explains how 3DNow!™ technology improves upon the mature x86 instruction set (now more than 20 years old) to provide PC users with a richer, 3D-enhanced computing experience. The benefits of 3DNow! technology can be achieved with minimal impact on existing and emerging x86 software thanks to the support of an industry standard: the DirectX application programming interface (API). This paper provides an overview of DirectX, a review of the graphics pipeline and how it is enhanced by 3DNow! technology, and a summary of how the 3DNow! instruction set is used in different software layers, as well as the impact of the new 3D instructions on each layer. Introduction: What is DirectX Technology? The DirectX API is a group of technologies designed by Microsoft to make Windows® based computers an ideal platform for running and displaying applications rich in multimedia elements, such as full-color graphics, video, 3D animation, and surround sound. Built directly into the Microsoft® Windows family of operating systems, DirectX is an integral part of the Windows 95/98 and Windows NT® 5.0 operating systems, as well as Internet Explorer 4.0. DirectX components may also be automatically installed on a PC by advanced multimedia games and applications written for the Windows 95 operating system.
    [Show full text]
  • It's Meant to Be Played
    Issue 10 $3.99 (where sold) THE WAY It’s meant to be played Ultimate PC Gaming with GeForce All the best holiday games with the power of NVIDIA Far Cry’s creators outclass its already jaw-dropping technology Battlefi eld 2142 with an epic new sci-fi battle World of Warcraft: Company of Heroes Warhammer: The Burning Crusade Mark of Chaos THE NEWS Notebooks are set to transform Welcome... PC gaming Welcome to the 10th issue of The Way It’s Meant To Be Played, the he latest must-have gaming system is… T magazine dedicated to the very best in a notebook PC. Until recently considered mainly PC gaming. In this issue, we showcase a means for working on the move or for portable 30 games, all participants in NVIDIA’s presentations, laptops complete with dedicated graphic The Way It’s Meant To Be Played processing units (GPUs) such as the NVIDIA® GeForce® program. In this program, NVIDIA’s Go 7 series are making a real impact in the gaming world. Latest thing: Laptops developer technology engineers work complete with dedicated The advantages are obvious – gamers need no longer be graphic processing units with development teams to get the are making an impact in very best graphics and effects into tied to their desktop set-up. the gaming world. their new titles. The games are then The new NVIDIA® GeForce® Go 7900 notebook rigorously tested by three different labs GPUs are designed for extreme HD gaming, and gaming at NVIDIA for compatibility, stability, and hardware specialists such as Alienware and Asus have performance to ensure that any game seen the potential of the portable platform.
    [Show full text]
  • Rredline™ Programming Guide
    RENDITION . 1675 North Shoreline Blvd. Mountain View, CA 94043 650-335-5900 . http://www.rendition.com . .Rendition. .......... RRedline™ Programming Guide Guide to the RRedline HAL for Vérité™ Graphics Rendering​ RRedline​ Programming Guide GETTING STARTED ​4 WHAT IS THE VÉRITÉ? ​4 WHAT IS RREDLINE? ​4 SUPPORTED PLATFORMS ​4 SUPPORTED COMPILERS ​5 VERITE VS. REDLINE ​5 THE BUILD ENVIRONMENT ​6 BUG REPORTING ​6 TRADEMARKS ​6 HELLO TRIANGLE ​7 SOME BOOKKEEPING ​7 WRITING ERROR HANDLERS​8 INITIALIZING RREDLINE ​10 Creating the Command Buffers ​11 Surfaces ​13 Other Data Structures ​16 Specifying the Source Function ​16 UTILITIES ​16 Issuing the Command Buffer ​17 Issuing the Command Buffer ​17 Page Flipping ​18 Clearing the Back Buffer ​19 RENDERING THE TRIANGLE​20 Choosing a Vertex Type​20 Drawing Triangles ​23 SHUTTING DOWN THE VÉRITÉ ​24 MODIFICATIONS TO HELLO TRIANGLE ​26 MODIFICATION ONE: SWITCHING BETWEEN FULL SCREEN MODE AND WINDOWED MODE ​27 PAGE FLIPPING IN A WINDOW ​27 INITIALIZING BUFFERS FOR A WINDOWED APPLICATION ​28 DISPLAY SWITCHING ROUTINE ​30 DE-ACTIVATING AND RE-ACTIVATING THE APPLICATION ​31 MODIFICATION TWO: DRAWING A TEXTURE MAPPED TRIANGLE ​34 CREATING AND LOADING THE TEXTURES ​34 FILTERING THE TEXTURES​36 SETTING THE SOURCE FUNCTION ​37 RENDERING THE TRIANGLE​38 FREEING THE TEXTURES ​40 RESTORING THE TEXTURES AND PIXEL ENGINE STATE ​41 MODIFICATION THREE: Z BUFFERING AND PERSPECTIVE CORRECTION ​42 CREATING AND USING A Z-BUFFER ​42 CLEARING THE Z-BUFFER ​43 RENDERING THE TRIANGLE​43 MODIFICATION FOUR: ALPHA BLENDING
    [Show full text]
  • John Carmack Archive - .Plan (1998)
    John Carmack Archive - .plan (1998) http://www.team5150.com/~andrew/carmack March 18, 2007 Contents 1 January 5 1.1 Some of the things I have changed recently (Jan 01, 1998) . 5 1.2 Jan 02, 1998 ............................ 6 1.3 New stuff fixed (Jan 03, 1998) ................. 7 1.4 Version 3.10 patch is now out. (Jan 04, 1998) ......... 8 1.5 Jan 09, 1998 ............................ 9 1.6 I AM GOING OUT OF TOWN NEXT WEEK, DON’T SEND ME ANY MAIL! (Jan 11, 1998) ................. 10 2 February 12 2.1 Ok, I’m overdue for an update. (Feb 04, 1998) ........ 12 2.2 Just got back from the Q2 wrap party in vegas that Activi- sion threw for us. (Feb 09, 1998) ................ 14 2.3 Feb 12, 1998 ........................... 15 2.4 8 mb or 12 mb voodoo 2? (Feb 16, 1998) ........... 19 2.5 I just read the Wired article about all the Doom spawn. (Feb 17, 1998) .......................... 20 2.6 Feb 22, 1998 ........................... 21 1 John Carmack Archive 2 .plan 1998 3 March 22 3.1 American McGee has been let go from Id. (Mar 12, 1998) . 22 3.2 The Old Plan (Mar 13, 1998) .................. 22 3.3 Mar 20, 1998 ........................... 25 3.4 I just shut down the last of the NEXTSTEP systems running at id. (Mar 21, 1998) ....................... 26 3.5 Mar 26, 1998 ........................... 28 4 April 30 4.1 Drag strip day! (Apr 02, 1998) ................. 30 4.2 Things are progressing reasonably well on the Quake 3 en- gine. (Apr 08, 1998) ....................... 31 4.3 Apr 16, 1998 ..........................
    [Show full text]
  • 4010, 237 8514, 226 80486, 280 82786, 227, 280 a AA. See Anti-Aliasing (AA) Abacus, 16 Accelerated Graphics Port (AGP), 219 Acce
    Index 4010, 237 AIB. See Add-in board (AIB) 8514, 226 Air traffic control system, 303 80486, 280 Akeley, Kurt, 242 82786, 227, 280 Akkadian, 16 Algebra, 26 Alias Research, 169 Alienware, 186 A Alioscopy, 389 AA. See Anti-aliasing (AA) All-In-One computer, 352 Abacus, 16 All-points addressable (APA), 221 Accelerated Graphics Port (AGP), 219 Alpha channel, 328 AccelGraphics, 166, 273 Alpha Processor, 164 Accel-KKR, 170 ALT-256, 223 ACM. See Association for Computing Altair 680b, 181 Machinery (ACM) Alto, 158 Acorn, 156 AMD, 232, 257, 277, 410, 411 ACRTC. See Advanced CRT Controller AMD 2901 bit-slice, 318 (ACRTC) American national Standards Institute (ANSI), ACS, 158 239 Action Graphics, 164, 273 Anaglyph, 376 Acumos, 253 Anaglyph glasses, 385 A.D., 15 Analog computer, 140 Adage, 315 Anamorphic distortion, 377 Adage AGT-30, 317 Anatomic and Symbolic Mapper Engine Adams Associates, 102 (ASME), 110 Adams, Charles W., 81, 148 Anderson, Bob, 321 Add-in board (AIB), 217, 363 AN/FSQ-7, 302 Additive color, 328 Anisotropic filtering (AF), 65 Adobe, 280 ANSI. See American national Standards Adobe RGB, 328 Institute (ANSI) Advanced CRT Controller (ACRTC), 226 Anti-aliasing (AA), 63 Advanced Remote Display Station (ARDS), ANTIC graphics co-processor, 279 322 Antikythera device, 127 Advanced Visual Systems (AVS), 164 APA. See All-points addressable (APA) AED 512, 333 Apalatequi, 42 AF. See Anisotropic filtering (AF) Aperture grille, 326 AGP. See Accelerated Graphics Port (AGP) API. See Application program interface Ahiska, Yavuz, 260 standard (API) AI.
    [Show full text]
  • Troubleshooting Guide Table of Contents -1- General Information
    Troubleshooting Guide This troubleshooting guide will provide you with information about Star Wars®: Episode I Battle for Naboo™. You will find solutions to problems that were encountered while running this program in the Windows 95, 98, 2000 and Millennium Edition (ME) Operating Systems. Table of Contents 1. General Information 2. General Troubleshooting 3. Installation 4. Performance 5. Video Issues 6. Sound Issues 7. CD-ROM Drive Issues 8. Controller Device Issues 9. DirectX Setup 10. How to Contact LucasArts 11. Web Sites -1- General Information DISCLAIMER This troubleshooting guide reflects LucasArts’ best efforts to account for and attempt to solve 6 problems that you may encounter while playing the Battle for Naboo computer video game. LucasArts makes no representation or warranty about the accuracy of the information provided in this troubleshooting guide, what may result or not result from following the suggestions contained in this troubleshooting guide or your success in solving the problems that are causing you to consult this troubleshooting guide. Your decision to follow the suggestions contained in this troubleshooting guide is entirely at your own risk and subject to the specific terms and legal disclaimers stated below and set forth in the Software License and Limited Warranty to which you previously agreed to be bound. This troubleshooting guide also contains reference to third parties and/or third party web sites. The third party web sites are not under the control of LucasArts and LucasArts is not responsible for the contents of any third party web site referenced in this troubleshooting guide or in any other materials provided by LucasArts with the Battle for Naboo computer video game, including without limitation any link contained in a third party web site, or any changes or updates to a third party web site.
    [Show full text]
  • 3Dfx Oral History Panel Gordon Campbell, Scott Sellers, Ross Q. Smith, and Gary M. Tarolli
    3dfx Oral History Panel Gordon Campbell, Scott Sellers, Ross Q. Smith, and Gary M. Tarolli Interviewed by: Shayne Hodge Recorded: July 29, 2013 Mountain View, California CHM Reference number: X6887.2013 © 2013 Computer History Museum 3dfx Oral History Panel Shayne Hodge: OK. My name is Shayne Hodge. This is July 29, 2013 at the afternoon in the Computer History Museum. We have with us today the founders of 3dfx, a graphics company from the 1990s of considerable influence. From left to right on the camera-- I'll let you guys introduce yourselves. Gary Tarolli: I'm Gary Tarolli. Scott Sellers: I'm Scott Sellers. Ross Smith: Ross Smith. Gordon Campbell: And Gordon Campbell. Hodge: And so why don't each of you take about a minute or two and describe your lives roughly up to the point where you need to say 3dfx to continue describing them. Tarolli: All right. Where do you want us to start? Hodge: Birth. Tarolli: Birth. Oh, born in New York, grew up in rural New York. Had a pretty uneventful childhood, but excelled at math and science. So I went to school for math at RPI [Rensselaer Polytechnic Institute] in Troy, New York. And there is where I met my first computer, a good old IBM mainframe that we were just talking about before [this taping], with punch cards. So I wrote my first computer program there and sort of fell in love with computer. So I became a computer scientist really. So I took all their computer science courses, went on to Caltech for VLSI engineering, which is where I met some people that influenced my career life afterwards.
    [Show full text]
  • PACKET 22 BOOKSTORE, TEXTBOOK CHAPTER Reading Graphics
    A.11 GRAPHICS CARDS, Historical Perspective (edited by J Wunderlich PhD in 2020) Graphics Pipeline Evolution 3D graphics pipeline hardware evolved from the large expensive systems of the early 1980s to small workstations and then to PC accelerators in the 1990s, to $X,000 graphics cards of the 2020’s During this period, three major transitions occurred: 1. Performance-leading graphics subsystems PRICE changed from $50,000 in 1980’s down to $200 in 1990’s, then up to $X,0000 in 2020’s. 2. PERFORMANCE increased from 50 million PIXELS PER SECOND in 1980’s to 1 billion pixels per second in 1990’’s and from 100,000 VERTICES PER SECOND to 10 million vertices per second in the 1990’s. In the 2020’s performance is measured more in FRAMES PER SECOND (FPS) 3. Hardware RENDERING evolved from WIREFRAME to FILLED POLYGONS, to FULL- SCENE TEXTURE MAPPING Fixed-Function Graphics Pipelines Throughout the early evolution, graphics hardware was configurable, but not programmable by the application developer. With each generation, incremental improvements were offered. But developers were growing more sophisticated and asking for more new features than could be reasonably offered as built-in fixed functions. The NVIDIA GeForce 3, described by Lindholm, et al. [2001], took the first step toward true general shader programmability. It exposed to the application developer what had been the private internal instruction set of the floating-point vertex engine. This coincided with the release of Microsoft’s DirectX 8 and OpenGL’s vertex shader extensions. Later GPUs, at the time of DirectX 9, extended general programmability and floating point capability to the pixel fragment stage, and made texture available at the vertex stage.
    [Show full text]
  • 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
    [Show full text]