Mapobjects IMS 2.0 System Requirements

Total Page:16

File Type:pdf, Size:1020Kb

Mapobjects IMS 2.0 System Requirements MapObjects IMS 2.0 System Requirements This PDF contains system requirements information, including hardware requirements, best performance configurations, and limitations, for MapObjects IMS 2.0. PC-Intel Windows 95 PC-Intel Windows 98 PC-Intel Windows NT 3.51 PC-Intel Windows NT 4.0 MapObjects IMS 2.0 on PC-Intel Windows 95 Product: MapObjects IMS 2.0 Platform: PC-Intel Operating System: Windows 95 Shipping/Release Date: July 21, 1998 Hardware Requirements CPU Speed: 90 MHz* *Minimum requirement. Processor: Pentium Class Processor Memory/RAM: Disk Space: 7 MB Notes: VGA or higher resolution monitor (Graphics card required) Limitations Product: At the time of release, MapObjects IMS 2.0 was supported on Windows 95, 98, NT 3.51 and NT 4.0. However, due to the Microsoft support cycle, Windows 95 and NT 3.51 are no longer supported. Refer to Microsoft support pages for OS lifecycle support status: http://support.microsoft.com/default.aspx?scid=fh;[ln];LifeWin Related Materials Platform: *Refer to product documentation for server and browser configuration information. MapObjects IMS 2.0 on PC-Intel Windows 98 Product: MapObjects IMS 2.0 Platform: PC-Intel Operating System: Windows 98 Shipping/Release Date: July 21, 1998 Hardware Requirements CPU Speed: 90 MHz* *Minimum requirement. Processor: Pentium Class Processor Memory/RAM: Disk Space: 7 MB Notes: VGA or higher resolution monitor (Graphics card required) Limitations Product: At the time of release, MapObjects IMS 2.0 was supported on Windows 95, 98, NT 3.51 and NT 4.0. However, due to the Microsoft support cycle, Windows 95 and NT 3.51 are no longer supported. Refer to Microsoft support pages for OS lifecycle support status: http://support.microsoft.com/default.aspx?scid=fh;[ln];LifeWin Related Materials Platform: *Refer to product documentation for server and browser configuration information. MapObjects IMS 2.0 on PC-Intel Windows NT 3.51 Product: MapObjects IMS 2.0 Platform: PC-Intel Operating System: Windows NT 3.51 Shipping/Release Date: July 21, 1998 Hardware Requirements CPU Speed: 90 MHz* *Minimum requirement. Processor: Pentium Class Processor Memory/RAM: Disk Space: 7 MB Notes: VGA or higher resolution monitor (Graphics card required) Limitations Product: At the time of release, MapObjects IMS 2.0 was supported on Windows 95, 98, NT 3.51 and NT 4.0. However, due to the Microsoft support cycle, Windows 95 and NT 3.51 are no longer supported. Refer to Microsoft support pages for OS lifecycle support status: http://support.microsoft.com/default.aspx?scid=fh;[ln];LifeWin Related Materials Platform: *Refer to product documentation for server and browser configuration information. MapObjects IMS 2.0 on PC-Intel Windows NT 4.0 Product: MapObjects IMS 2.0 Platform: PC-Intel Operating System: Windows NT 4.0 Shipping/Release Date: July 21, 1998 Hardware Requirements CPU Speed: 90 MHz* *Minimum requirement. Processor: Pentium Class Processor Memory/RAM: Disk Space: 7 MB Notes: VGA or higher resolution monitor (Graphics card required) Limitations Product: At the time of release, MapObjects IMS 2.0 was supported on Windows 95, 98, NT 3.51 and NT 4.0. However, due to the Microsoft support cycle, Windows 95 and NT 3.51 are no longer supported. Refer to Microsoft support pages for OS lifecycle support status: http://support.microsoft.com/default.aspx?scid=fh;[ln];LifeWin Related Materials Platform: *Refer to product documentation for server and browser configuration information. .
Recommended publications
  • Why Os/2 Failed: Business Mistakes Compounded by Memory Prices
    Mountain Plains Journal of Business and Economics Volume 10 Issue 1 Article 4 Date Published: 10-1-2009 Why Os/2 Failed: Business Mistakes Compounded By Memory Prices Eric G. Swedin Weber State University Davis Follow this and additional works at: https://openspaces.unk.edu/mpjbt Part of the Business Commons Recommended Citation Swedin, E. G. (2009). Why Os/2 Failed: Business Mistakes Compounded By Memory Prices. Mountain Plains Journal of Business and Economics, 10(1). Retrieved from https://openspaces.unk.edu/mpjbt/ vol10/iss1/4 This Case Study is brought to you for free and open access by OpenSPACES@UNK: Scholarship, Preservation, and Creative Endeavors. It has been accepted for inclusion in Mountain Plains Journal of Business and Economics by an authorized editor of OpenSPACES@UNK: Scholarship, Preservation, and Creative Endeavors. For more information, please contact [email protected]. 36 WHY OS/2 FAILED: BUSINESS MISTAKES COMPOUNDED BY MEMORY PRICES ERIC G. SWEDIN WEBER STATE UNIVERSITY DAVIS ABSTRACT In 2006, IBM ended their support of OS/2, closing the book on an ambitious effort to create a modern operating system for the personal computer. IBM and Microsoft released the OS/2 operating system in December 1987 to replace the primitive DOS with a more sophisticated, preemptive multitasking operating system for personal computers. This article argues that OS/2 failed because of the U.S.-Japan Semiconductor Trade Agreement of 1986, subsequent accusations of DRAM chip dumping by the United States, and the resulting tariffs on Japanese memory chips, led to a memory chip shortage that drove up memory prices.
    [Show full text]
  • Page 1 of 3 How to Enable NTLM 2 Authentication 2/8/2012 Http
    How to enable NTLM 2 authentication Page 1 of 3 Article ID: 239869 - Last Review: January 25, 2007 - Revision: 4.7 How to enable NTLM 2 authentication System Tip This article applies to a different version of Windows than the one you are using. Content in this article may not be relevant to you. Visit the Windows 7 Solution Center This article was previously published under Q239869 SUMMARY Historically, Windows NT supports two variants of challenge/response authentication for network logons: • LAN Manager (LM) challenge/response • Windows NT challenge/response (also known as NTLM version 1 challenge/response) The LM variant allows interoperability with the installed base of Windows 95, Windows 98, and Windows 98 Second Edition clients and servers. NTLM provides improved security for connections between Windows NT clients and servers. Windows NT also supports the NTLM session security mechanism that provides for message confidentiality (encryption) and integrity (signing). Recent improvements in computer hardware and software algorithms have made these protocols vulnerable to widely published attacks for obtaining user passwords. In its ongoing efforts to deliver more secure products to its customers, Microsoft has developed an enhancement, called NTLM version 2, that significantly improves both the authentication and session security mechanisms. NTLM 2 has been available for Windows NT 4.0 since Service Pack 4 (SP4) was released, and it is supported natively in Windows 2000. You can add NTLM 2 support to Windows 98 by installing the Active Directory Client Extensions. After you upgrade all computers that are based on Windows 95, Windows 98, Windows 98 Second Edition, and Windows NT 4.0, you can greatly improve your organization's security by configuring clients, servers, and domain controllers to use only NTLM 2 (not LM or NTLM).
    [Show full text]
  • Windows 95, Windows 98, Windows 98SE, and Windows ME Courtesy of Nashville Home Linux Solutions
    Important information for users of Windows 95, Windows 98, Windows 98SE, and Windows ME courtesy of Nashville Home Linux Solutions FACT: As of July 2006, Microsoft has officially ended support for Windows 95, Windows 98, Windows 98SE, and Windows ME (Millennium Edition). What does this mean for you? Microsoft©s end-of-support announcement means that users of Windows 95, 98, and ME will no longer receive security updates, bug fixes, and other patches for their computer©s operating system. It also means that future releases of Microsoft software (such as Media Player, Internet Explorer, and Outlook Express) will no longer support these operating systems. Users of these versions of Windows will not benefit from enhanced features and security in these new versions. Why should I be concerned? Windows 95, 98, and ME are based around the DOS operating system, an inherently insecure operating system. Users of DOS-based Windows will become increasingly at risk for viruses, spyware, malware, and system intrusions as new holes and exploits are discovered in these operating systems and the older software that runs on them. In addition, software vendors (including makers of anti-virus and other security products) will be phasing out support for these operating systems now that Microsoft has ended its support. If you are connecting your DOS-based Windows operating system to the Internet, you need to take action to secure your computer. What are my options? If you would like to continue to operate on your current hardware, you have a few options available to you: 1. Upgrade Windows Microsoft©s only currently-available Windows workstation operating system is Windows XP (Home or Professional).
    [Show full text]
  • Windows 95 and Window 98® Operating System
    ® Windows 95 and Window 98® Operating System Microsoft Base Cryptographic Provider FIPS 140-1 Documentation: Security Policy September 20, 2000 11:33 AM Abstract This document specifies the security policy for the Microsoft Base Cryptographic Provider (RSABASE) as described in FIPS PUB 140-1. CONTENTS INTRODUCTION .......................................................................... 1 SECURITY POLICY...................................................................... 2 SPECIFICATION OF ROLES ........................................................ 3 SPECIFICATION OF SERVICES................................................... 4 CRYPTOGRAPHIC KEY MANAGEMENT ..................................... 9 SELF-TESTS .............................................................................. 11 MISCELLANEOUS...................................................................... 12 FOR MORE INFORMATION ....................................................... 13 { TC "INTRODUCTION" \F SP }INTRODUCTION Microsoft Base Cryptographic Provider (RSABASE) is a FIPS 140-1 Level 1 compliant, general- purpose, software-based, cryptographic module. Like other cryptographic providers that ship with nternet Explorer 5.1 or later, RSABASE encapsulates several different cryptographic algorithms in an easy-to-use cryptographic module accessible via the Microsoft CryptoAPI. It can be dynamically linked into applications by software developers to permit the use of general-purpose FIPS 140-1 Level 1 compliant cryptography. Cryptographic Boundary The Microsoft
    [Show full text]
  • Starburn CD/DVD/Blu-Ray/HD-DVD Toolkit: Getting Started
    StarBurn Software Technical Reference Series StarBurn CD/DVD/Blu-Ray/HD-DVD Toolkit: Getting Started April 18, 2016 StarBurn Software www.starburnsoftware.com Copyright © Rocket Division Software 2001-2016. All rights reserved. Copyright © StarBurn Software 2009-2016. All rights reserved. StarBurn CD/DVD/Blu-Ray/HD-DVD Toolkit: Getting Started Page 1 of 13 StarBurn Software Technical Reference Series INTRODUCTION .................................................................................................. 4 KEY BENEFITS ..................................................................................................... 5 KEY FEATURES .................................................................................................... 7 SUPPORTED PLATFORMS .................................................................................. 11 SYSTEM REQUIREMENTS................................................................................... 12 CONTACTS........................................................................................................ 13 StarBurn CD/DVD/Blu-Ray/HD-DVD Toolkit: Getting Started Page 2 of 13 StarBurn Software Technical Reference Series COPYRIGHT Copyright © Rocket Division Software 2001-2016. All rights reserved. Copyright © StarBurn Software 2009-2016. All rights reserved. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, without the prior written
    [Show full text]
  • Windows 95 & NT
    Windows 95 & NT Configuration Help By Marc Goetschalckx Version 1.48, September 19, 1999 Copyright 1995-1999 Marc Goetschalckx. All rights reserved Version 1.48, September 19, 1999 Marc Goetschalckx 4031 Bradbury Drive Marietta, GA 30062-6165 tel. (770) 565-3370 fax. (770) 578-6148 Contents Chapter 1. System Files 1 MSDOS.SYS..............................................................................................................................1 WIN.COM..................................................................................................................................2 Chapter 2. Windows Installation 5 Setup (Windows 95 only)...........................................................................................................5 Internet Services Manager (Windows NT Only)........................................................................6 Dial-Up Networking and Scripting Tool....................................................................................6 Direct Cable Connection ..........................................................................................................16 Fax............................................................................................................................................17 Using Device Drivers of Previous Versions.............................................................................18 Identifying Windows Versions.................................................................................................18 User Manager (NT Only) .........................................................................................................19
    [Show full text]
  • Restoring from a Backup with Image for Windows
    User’s Guide TERABYTE UNLIMITED 10220 Lazy Bear Street Las Vegas, NV 89131 http://www.TeraByteUnlimited.com ASP Member Copyright © 1996-2007 by TeraByte Unlimited, All Rights Reserved. Trademarks BootIt, PHYLock, and TBIView are trademarks of TeraByte Unlimited. Microsoft, MS, MS-DOS and Windows are registered trademarks of Microsoft Corporation. IBM, PC-DOS and OS/2 are registered trademarks of the International Business Machines Corporation. All other trademarks and copyrights referred to are the property of their respective owners. Technical Support Policy Technical support is provided online. Software and documentation updates are available at www.terabyteunlimited.com. • The Image for Windows home page, with software and documentation update information, and support resources, can be found at www.terabyteunlimited.com/imagew.html. • A support knowledge base for all TeraByte Unlimited products, including Image for Windows, can be found at www.terabyteunlimited.com/kb. Registered users can email their questions to [email protected], if no suitable resolution is found via the aforementioned support resources. If the issue is not resolved via email, telephone support may be provided. Unregistered users will be provided technical support and product information through email only. In all cases, TeraByte Unlimited reserves the right to refuse any communication method that would incur a cost. Ombudsman Statement This program is produced by a member of the Association of Shareware Professionals (ASP). ASP wants to make sure that the shareware principle works for you. If you are unable to resolve a shareware-related problem with an ASP member by contacting the member directly, ASP may be able to help.
    [Show full text]
  • Unit 5 Windows 2000/XP History, and Data Management
    Unit 5 Windows 2000/XP History, and Data Management Copyright © 2002 Heathkit Company, Inc. All rights reserved. Microsoft Windows98 Microsoft WindowsMe Microsoft Windows 2000 Professional Microsoft WindowsXP 2 Windows 2000/XP or Windows 9x (95/98/Me)? Windows 9x Windows 2000/XP Runs on today’s Runs on “nearly any hardware, doesn’t run old hardware” well or at all on marginal hardware Secure, more difficult to Open, easy to configure configure Supports lots of Device support somewhat devices limited, so far 3 Windows XP or Windows 9x? If you need: Choose: Reliable, solid security Windows 2000/XP “Crash-proof” system Windows 2000/XP Support for older/slower Windows 9x machines Easy setup and configuration Windows 9x Support for that older scanner, Windows 9x CD Writer, NIC, Video, etc. 4 The Windows Business Consumer Universe 1990 Windows 3.1 Windows NT 3.51 Windows for Workgroups Windows NT 4 Windows 95 Windows 98 Windows 2000 Windows Me Today Windows XP Pro/Home 5 The Windows Business Consumer Universe 1990 Windows 3.1 Windows NT 3.51 Windows for Workgroups Windows NT 4 Windows 95 Windows 98 Windows 2000 Windows Me Today Windows XP Pro/Home 6 The TheWindows Windows Business Universe Consumer Universe 1990 Windows 3.1 Windows NT 3.51 Windows for Workgroups Windows NT 4 Windows 95 Windows 98 Windows 2000 Windows Me Today Windows XP Pro/Home 7 Windows XP Flavors • Windows XP Professional • Windows XP Home • Windows 2003 Server • Windows 2003 Enterprise Server • Windows 2003 Datacenter Server 8 Windows Package Types • Upgrade • Full Version
    [Show full text]
  • Remoteboot of Windows 95/98 from Os/2 Warp Server
    REMOTEBOOT OF WINDOWS 95/98 FROM OS/2 WARP SERVER MICHO DURDEVICH Abstract. We explain how to set up diskless Windows 95/98 workstations that remote boot from OS/2 Warp Server, using the 802.2 RIPL Service. We present several different configurations of Windows RIPL clients, and discuss a couple of interesting problems appearing in the game. The basics of the OS/2 Warp Server RIPL Service is presented, too. 1. Introduction This article is devoted to studying a very interesting way of integrating Windows with OS/2 Warp Server working environment. We shall explain in detail how to set up a remote boot diskless workstation to load Windows 95/98 (together with the appropriate applications) directly from an OS/2 Warp Server. This opens an exciting new possibility to extend IBM’s and Serenity Systems’ OS/2-based managed client philosophy to Win32 platforms. In other words, we are going to set up RIPL (Remote Initialization and Program Load) for Win95/98 clients. The main strategy used here is relatively straightfor- ward. The first real-mode phase of Win95/98 boot process is essentially a plain DOS. The transition to protected-mode regime occurs during the second boot phase, when the graphical part is loaded. Accordingly, our Win95/98 client will be under- stood, from the OS/2 Warp Server viewpoint, as a DOS client. This client will be configured appropriately, so it will be able to RIPL a full-blown version of Windows. It should be noted however, that this is not a documented feature of Windows nor OS/2.
    [Show full text]
  • Windows 95: Features
    Windows Windows 95: Features Introduction Windows 95 is the much-anticipated update to Microsoft’s popular Windows graphic user interface, or GUI. A GUI is designed to make computer tasks (such as file management) intuitive and easy for novices as well as experts, replacing clunky line-driven commands with pictures called icons. Unlike previous versions of Windows, the interface for Windows 95 is much more seamless, and does not require continual switching between program manager and file manager. Users familiar with the Macintosh operating system will recognize many elements of this interface, and cross-platform work will be easier than ever before. Windows 95 is also a more complete 32 bit operating system. The good side of this is that 32 bit applications are potentially faster than older ones, and more memory (RAM) will considerably improve overall system performance. The bad side is that users will be forced to upgrade both their applications and system RAM to take advantage of these performance benefits. Older applications will slow down performance when they are executing, and will not conform to new standards established in Windows 95—for example, longer file names. Minimum System Requirements The following should be considered the minimum acceptable hardware requirements for running Windows 95: • a 486/33 based PC or better • 8 MB of RAM • 500 MB of hard drive space • a double speed CD-ROM drive (though quad speeds are better for little increase in price) Users who customarily run multiple applications at the same time, or who run very large single applications (e.g., Photoshop), would want to add more RAM and a larger hard drive.
    [Show full text]
  • MICROSOFT WINDOWS Early Versions Main Articles: Windows 1.0
    MICROSOFT WINDOWS Early versions Main articles: Windows 1.0, Windows 2.0, and Windows 2.1x Windows 1.0, the first version, released in 1985 The history of Windows dates back to September 1981, when Chase Bishop, a computer scientist, designed the first model of an electronic device and project "Interface Manager" was started. It was announced in November 1983 (after the Apple Lisa, but before the Macintosh) under the name "Windows", but Windows 1.0 was not released until November 1985.[5] Windows 1.0 achieved little popularity and was to compete with Apple's own operating system. Windows 1.0 is not a complete operating system; rather, it extends MS-DOS. The shell of Windows 1.0 is a program known as the MS- DOS Executive. Components included Calculator, Calendar, Cardfile, Clipboard viewer, Clock, Control Panel, Notepad, Paint, Reversi, Terminal and Write. Windows 1.0 does not allow overlapping windows. Instead all windows are tiled. Only modal dialog boxes may appear over other windows. Windows 2.0 was released in December 1987 and was more popular than its predecessor. It features several improvements to the user interface and memory management.[citation needed] Windows 2.03 changed the OS from tiled windows to overlapping windows. The result of this change led to Apple Computer filing a suit against Microsoft alleging infringement on Apple's copyrights.[6][7] Windows 2.0 also introduced more sophisticated keyboard shortcuts and could make use of expanded memory. Windows 2.1 was released in two different versions: Windows/286 and Windows/386. Windows/386 uses the virtual 8086 mode of Intel 80386 to multitask several DOS programs and the paged memory model to emulate expanded memory using available extended memory.
    [Show full text]
  • 0672325756 A020101
    A Brief History of IIS A020101 Despite how ubiquitous you might think Microsoft is now on the Web—particularly the high use of the Internet Explorer product—you’d be forgiven for thinking that Microsoft was there right from the start. In fact, Microsoft came to the scene relatively late in terms of its own presence—and quite later still in terms of its IIS product. The first version of a Web server to be used and supported by Microsoft was the one running its Web site on Windows NT 3.51 using the European Microsoft Windows Academic Consortium (EMWAC) WWW software. This was 1994, and many of the bigger companies like Sun and the National Center for Supercomputing Applications (NCSA) had jumped on the bandwagon a few years earlier. IIS 1 The first noted version of IIS was IIS 1, born out of the EMWAC server and officially built and tested using Microsoft’s own Web sites before being formally released to the world in February 1996. IIS 1 incorporated and supported the three main protocols of the time—HTTP, FTP, and Gopher (a hierarchical file viewing system). IIS 1 also included support for CGI working with tools such as Perl to provide a dynamic envi- ronment and ISAPI that enabled developers to write custom applications that worked with IIS. 2 A020101 A Brief History of IIS This version also gave rise to a number of the basic features we expect to find in all versions of IIS today, including n Internet Services Manager (now part of the MMC) n Integration with the OS n Virtual Servers n Virtual Directories n Basic authentication and Windows NT LAN Manager authentication n Secure Sockets Layer support IIS 2 This was the first release of IIS that was bundled with an operating system.
    [Show full text]