Quarterdeck Expanded Memory Manager QEMM, IPAc en icon k w m , though not by those who developed .... It was the most popular memory manager for the MS DOS and other DOS operating system s. QEMM product ... from QEMM 6.02, Manifest 1.13. Earlier versions of QRAM also supported the older 8086 and 8088 CPUs ... PA34 v onepage&q&f false ref QEMM Game Edition It is a version of QEMM that includes Quarterdeck GameRunner. Patches for regular QEMM do not work on QEMM Game Edition. QEMM MegaBundle In the version shipped with SideKick for Windows, it is a version with SideBar 1.00 1994 08 22 and QEMM 7.5. DESQview 386 It includes DESQview and QEMM 386. Competitors The principal competitors of QEMM were BlueMax ... system to bundle technology similar to QEMM 386, incorporating a 386 mode EMS manager called CEMM . QEMM was the first V86 memory manager on the market. Features tools QEMM driver QEMM provides access ... to be loaded before loading QEMM and still allow the use of QEMM s Stealth feature. MagnaRAM It is a memory ... with QEMM 97. MagnaRAM was also released as a separate utility. ref http www.highbeam.com doc ... rebooting. It was first release in 1990 01 11. It is shipped with QEMM and DESQView. QDPMI It is a DPMI 0.9 server driver. It requires 386 CPU and QEMM386. QEMM 50 60 It is a version of QEMM driver .... Stealth It can relocate memory assigned for CGA character set away from UMA. Beginning with QEMM ... allows DoubleSpace or DriveSpace to be loaded high. T386 It allows Toshiba laptops to work with QEMM ... in QEMM 4.23, 2 in QEMM 5, 32 in QEMM 6. MagnaRAM limit Maximum compression threshold setting is 100 for all versions of MagnaRAM 2.00 2.02, except for MagnaRAM 2.00 included with QEMM 8.00, which has the maximum setting of 80 . Memory limit QEMM 6.0 can manage up to 128MB EMS, 64MB XMS. QEMM 6.02 can manage up to 128MB EMS, 128MB XMS. EMBMEM 16 bit parameter limit was removed. QEMM 7.0 to 7.03 can manage up to 82MB memory. QEMM 7.04 can manage up to 256MB memory. QEMM 7.5 can manage up to 256MB ... more details
Memory manager may refer to DOS memory management Expanded memory manager 386MAX 386 sup MAX sup CEMM EMM386 QEMM Memory management disambig ... more details
DISPLAYTITLE 386 sup MAX sup 386 sup MAX sup Qualitas MAX was a computer memory manager for DOS based personal computer s. It competed with Quarterdeck s QEMM memory manager. It was manufactured by Qualitas . BlueMax was a special version designed for the IBM PS 2 with ROM compression to get the most of the Upper Memory Blocks. DPMIONE It is a DPMI 1.0 host component from Qualitas, written by Bob Smith of Sudley Place Software. External links http web.archive.org web 20100416151552 http www.qualitas.com download.htm Qualitas support page http www.sudleyplace.com dpmione DPMIONE Documentation File Version 0.91 DEFAULTSORT 386max Category Expanded memory managers DOS stub ... more details
DESQview 386 DESQview that shipped bundled with QEMM 386 DESQview DESQview X an X Window System X ... QEMM Quarterdeck Expanded Memory Manager , formerly QEMM 386 QEMM QRAM QRAM , an Intel 80286 based expanded memory manager QEMM MagnaRAM MagnaRAM GlobalStage IRC server run on irc.scifi.com until 2003 ... more details
, meaning that a misbehaving program could still crash the system. DESQview and QEMM To make maximum ... marketed it as a separate product, QEMM 386 Quarterdeck Expanded Memory Manager 386 . It became ... Intel Pentium processor, the 386 in QEMM was dropped. The combination package of DESQview and QEMM ... DESQview was able to use QEMM s features far beyond just the LIM EMS API, mapping most of the conventional ... run, but DESQview under QEMM could run as many instances of those programs as the EMS would allow. So ... t include support for the graphical features of MS Windows. The decline of QEMM started with the bundling ... with Windows. QEMM could still be used instead, notably with Windows 3.1x , but it only provided incremental benefits. Sales of QEMM declined. In August 1994, after three quarters of losses, the company ... of DESQview was released. QEMM was still developed after the discontinuation of DESQview, and a version ... more details
Unreferenced stub auto yes date December 2009 Pathworks was the tradename used by Digital Equipment Corporation of Maynard, Massachusetts Maynard , Massachusetts for a series of programs that eased the interoperation of Digital s minicomputer s with personal computer s. The server part of Pathworks ran on VAX VMS or Ultrix and enabled a DEC VAX or VAXcluster to act as a file and print server for client IBM PC compatible and Apple Macintosh Macintosh workstations. Pathworks server was derived from LanMan X , the portable version of OS 2 LAN Manager . Once installed onto the PCs, the Pathworks client provided the following features DECnet end node connectivity with the host systems PowerTerm 525 Terminal emulation software from Ericom File transfer software For clients running a GUI such as Windows 3.x, additional components available included an X window system server, allowing clients to access graphical apps running on VMS or UNIX hosts, and clients for DEC s ALL IN 1 email and groupware system. Although primitive by modern standards, Pathworks was very sophisticated for its time far more than just a file and print server, it made client microcomputers into terminals and workstations on a DEC network. LanMan normally ran across Microsoft s basic, non routable NetBIOS NetBIOS NetBEUI NetBIOS Frames protocol NBF protocol, but Pathworks included a DECnet stack, including layers like the LAT transport used for terminal sessions. The complexity of DECnet by 1980s PC standards meant that the Pathworks client was a huge software stack to have resident in MS DOS configuring the Pathworks client was a complex task, made more so by the need to preserve enough Conventional memory for DOS applications to run. To keep a reasonable amount of base memory free mandated the use of QEMM or a similar memory manager . Pathworks was available for both Windows and Mac computer systems. Category OpenVMS software Not a great cat given that most of PW lived on the PCs Tech stub ... more details
mergeto DOS memory management discuss Talk DOS memory management Suggest merge date December 2010 File IBM PC Memory areas.svg thumb The upper memory area is located between 640 KB and 1024 KB. In DOS memory management , the upper memory area UMA refers to computer memory memory between the address space addresses of 640 Kilobyte KB and 1024 KB Hexadecimal 0x A0000 0xFFFFF in an IBM PC or compatible. IBM reserved the uppermost 384 KB of the Intel 8088 8088 Central processing unit CPU s 1024 KB address space for Read only memory ROM , RAM on peripheral s, and memory mapped input output. For example, the monochrome video memory area runs from 704 to 736 KB 0xB0000 B7FFF . However, even with video RAM, the ROM BIOS and I O ports for expansion cards, much of this 384 KB of address space was unused. As the 640 KB memory restriction became ever more of an obstacle, techniques were found to fill the empty areas with RAM. These areas were referred to as upper memory blocks UMBs . Usage The next stage in the evolution of DOS was for the operating system to use upper memory blocks UMBs and the high memory area HMA . This occurred with the release of DR DOS DR DOS 5.0 in 1990. DR DOS built in memory manager, EMM386.EXE , could perform most of the basic functionality of QEMM and comparable programs. The advantage of DR DOS 5 over the combination of an older DOS plus QEMM was that the DR DOS kernel itself and almost all of its data structures could be loaded into high memory. This left virtually all the base memory free, allowing configurations with up to 620 KB out of 640 KB free. Configuration was not automatic free UMBs had to be identified by hand, manually included in the line that loaded EMM386 from CONFIG.SYS, and then drivers and so on had to be manually loaded into UMBs from CONFIG.SYS and AUTOEXEC.BAT . This configuration was not a trivial process. As it was largely automated by the installation program of QEMM, this program survived on the market indeed, it worked wel ... more details
, for example Quarterdeck Office Systems Quarterdeck s QEMM or the default EMM386 in MS DOS, PC DOS ... featured commercial solution was Quarterdeck s QEMM . A contender was Qualitas 386MAX 386 sup MAX sup ... more details
In computing, the Virtual Control Program Interface VCPI is a specification published in 1989 by Phar Lap company Phar Lap Software that allows a DOS program to run in protected mode , granting access to many features of the processor not available in real mode . It was supplanted by DOS Protected Mode Interface DPMI shortly after being introduced, due in large part to VCPI s inability to work in Windows 3.0 s protected mode. Overview Developed in cooperation with Quarterdeck Office Systems , VCPI is provided by an expanded memory manager in DOS e.g. CEMM , QEMM , later EMM386 . It was eclipsed by DPMI, most notably because it was not supported for DOS programs run in Windows 3.0 s native protected mode called 386 enhanced mode and because VCPI runs programs in Ring computer security Ring 0, which defeated the purpose of x86 protection. It also did not work with OS 2 2.0 and later. VCPI was only supported in Windows 3.0 real mode ref Cite web title KB81493 Using VCPI Programs with Windows url http support.microsoft.com kb 81493 en usIN publisher Microsoft Corporation quote Many MS DOS based applications use the Virtual Control Program Interface VCPI specification ... . These programs do not work with Microsoft Windows version 3.0 in 386 enhanced mode. They work in Windows in real mode and may work in standard mode. ref , some programs could run in Windows 3.x standard mode. ref Cite web title KB64478 Mathematica 387 and Mathlab 386 with Windows 3.0 url http support.microsoft.com kb 64478 publisher Microsoft Corporation quote These programs use the VCPI ... to access extended memory that conflicts with Windows in protected mode standard and enhanced . ref ref Cite web title KB82298 Windows 3.1 Standard Mode and the VCPI url http support.microsoft.com kb 82298 publisher Microsoft Corporation quote ... an MS DOS based application that uses extended memory probably will fail to run in the standard mode MS DOS box. ref ref Cite web title KB86018 Windows 3.1 Has Limited S ... more details
Office Systems Quarterdeck s QEMM product and Microsoft s EMM386 supported the expanded memory standard ... like QEMM might move the bulk of the code for a driver or TSR into extended memory and replace it with a small ... more details
systems such as QEMM or MemoryMax in DR DOS could achieve the same effect, adding conventional memory ... 5, but third party products from companies such as QEMM , also proved popular. At startup, drivers ... more details
About BBS software the substrate used to support electronic devices Printed circuit board Infobox software name PCBoard logo screenshot Deleted image removed File Pcboard300xXXX.jpg 300px caption Photograph of original software box, manuals, disks and license bag for PCBoard 15.2 developer Clark Development Company, Inc. released Start date 1983 discontinued yes latest release version 15.3 latest release date Start date and age 1996 09 latest preview version 15.4 beta latest preview date Start date and age 1997 06 operating system DOS OS 2 genre Bulletin board system status Discontinued license Proprietary software Proprietary website defunct PCBoard PCB was a bulletin board system BBS application first introduced for DOS in 1983 by Clark Development Corporation . Clark Development was founded by Fred Clark. PCBoard was one of the first commercial BBS packages for DOS systems, and was considered one of the high end packages during the rapid expansion of BBS systems in the early 1990s. Like many BBS companies, the rise of the Internet starting around 1994 led to serious downturns in fortunes, and Clark Development went bankrupt in 1997. Most PCB sales were of two line licenses additional line licenses in ranges of 5, 10, 25, 50, 100, 250 and 1000 were also available. A native 32bit IBM OS 2 version became also available with PCB V15.22 and higher. There were also a few tools available for PCBoard, which were specifically developed for the OS 2 2.0 and OS 2 Warp operating system. Multinode support PCBoard supported the 16C550 UARTS Universal asynchronous receiver transmitter universal asynchronous receiver transmitter , such as 16550 UART Fifo , 16554 UART and 16650 UART, which made it possible to run multiple nodes of the BBS on a single Computer multitasking multitasking computer using either using IBM OS 2 or the DOS multitasking tool DESQview in combination with the memory manager QEMM . Some sysop s tried to run PCBoard on the then new Windows 95 operating system ... more details
memory blocks was possible using third party software like QEMM . As such, on a 386 system, it could ... triggered a compatibility problem in the DOS UP feature of the third party memory manager QEMM ... more details
data acquisition file ADInstruments div id ADL ADL div MCA adapter description library QEMM div id ... Access GCGW div id CPS CPS div backup of startup files by QEMM ? autoexec.cps div id CPT CPT ... more details
Encyclopedia
top
