Emm386 Error 13
Contents |
days ago I posted a question about reducing a timing loop's CPU usagewhen running the program under Windows. Rudolf \"/dev/random\" loop to something like this
Emm386 Switches
would help: Repeat asm hlt end; GetTime(h,m,s,hun); Until (m <> OldMin) emm386 download OR keypressed; And indeed, this has the desired effect when working in Windows, but in DOS 6.22, EMM386 randomly emm386 driver not installed produces Error #13 when the program runs. However, I cannot reproduce this behaviour with simple short test programs that only use the loop above and some extra write operations to files
Emm386 Noems
or other small tasks like that... What's going on there? I suspect that some operations I do take longer than 1/18.2 sec and hlt messes things up, but I don't really consider this logical the loop halts the program until it has to do something and the time consuming tasks take place outside. Hmm, I hope there are still some people around who
Emm386 Setup
know "Assembly inside" ;-)! TIA Jrgen BTW: I am sure that the problem originates in the hlt command, as commenting it out solves the problem. But I need to use it or something with the same effect... Thu, 26 Jun 2003 00:17:59 GMT Joche#2 / 2 Once again: Timing routine (EMM386 Error 13) hi jrgen, Quote:>Hello everyone, >a few days ago I posted a question about reducing a timing loop's CPU >usagewhen running the program under Windows. Rudolf \"/dev/random\" >loop to something like this would help: >Repeat > asm hlt end; > GetTime(h,m,s,hun); >Until (m <> OldMin) OR keypressed; >And indeed, this has the desired effect when working in Windows, but in >DOS 6.22, EMM386 randomly produces Error #13 when the program runs. >However, I cannot reproduce this behaviour with simple short test >programs that only use the loop above and some extra write operations to >files or other small tasks like that... What's going on there? I suspect >that some operations I do take longer than 1/18.2 sec and hlt messes >things up, but I don't really consider this logical - the loop halts the
resources Windows Server 2012 resources Programs MSDN subscriptions Overview Benefits Administrators Students Microsoft Imagine Microsoft Student Partners ISV Startups TechRewards Events Community Magazine emm386 not installed--unable to set page frame Forums Blogs Channel 9 Documentation APIs and reference Dev centers
Freedos Emm386
Retired content Samples We’re sorry. The content you requested has been removed. You’ll be auto redirected upper memory block in 1 second. MSDN Library MSDN Library MSDN Library MSDN Library Design Tools Development Tools and Languages Mobile and Embedded Development .NET Development Office development Online Services http://computer-programming-forum.com/29-pascal/5a4f8e9d4ed08f8f.htm Open Specifications patterns & practices Servers and Enterprise Development Speech Technologies Web Development Windows Desktop App Development TOC Collapse the table of content Expand the table of content This documentation is archived and is not being maintained. This documentation is archived and is not being maintained. Emm386 Archived content. No warranty is made as https://msdn.microsoft.com/en-us/library/cc722864.aspx to technical accuracy. Content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist. Enables or disables EMM386 expanded-memory support on a computer with an 80386 or higher processor. The emm386 command also enables or disables Weitek coprocessor support. Do not use this command when you are running Windows. The EMM386 device driver, EMM386.EXE, provides expanded-memory support and also provides access to the upper memory area. For information about EMM386.EXE, see EMM386.EXE. On This Page Syntax EMM386.EXE Exit Expand Syntax emm386 [on|off|auto] [w=on|w=off] To display the current status of EMM386 expanded-memory support, use the following syntax: emm386 Parameters on|off|auto Activates the EMM386 device driver (if set to on), or suspends the EMM386 device driver (if set to off), or places the EMM386 device driver in auto mode (if set to auto). Auto mode enables expanded-memory support only when a program calls for it. The default value is on. w=on
display and want to conserve memory. 2.4 Using MemMaker with IBM LAN. 2.5 MemMaker and Adaptec SCSI devices. 2.6 Running MemMaker on a computer with PC Tools RAMBoost. 2.7 EMM386 detects an http://info.wsisiz.edu.pl/~bse26236/batutil/help/S2.HTM error in an application. 2.8 MemMaker no longer aggressively scans upper memory by http://www.oocities.org/geoff_wass/dBASE/GaryWhite/dBASE/FAQ/qemm.htm default. -Top- 2.1 Intel Expanded-Memory Driver (EMM.SYS) If you use Intel's EMM.SYS driver with Aboveboard, use EMM.SYS version 4.0 revision E if you an ISA system, or EMM.SYS version 4.0 revision D if you have an MCA or other system. Contact Intel for a free upgrade. 2.2 Running MemMaker on a Computer not installed with PC-NFS If you use PC-NFS network software, carry out the following procedure before you run MemMaker: 1. Open your MEMMAKER.INF file by using any text editor. This file is in the directory that contains your MS-DOS files. 2. Add the following line to the file: *NET 3. Save the file, and then run MemMaker. 2.3 You have a Super VGA display and want to conserve memory. emm386 error 13 If you use Microsoft Windows on an 80386 computer with extended memory and a Super VGA display, you can use the MONOUMB.386 file, in conjunction with MemMaker, to conserve conventional memory for running programs. To conserve memory if you have a Super VGA display: 1. Open your Windows SYSTEM.INI file, and find the [386Enh] section. 2. Add a DEVICE command for the MONOUMB.386 file, which is located in your MS-DOS directory. For example, if your MS-DOS files are in C:\DOS, add the following line to this section: DEVICE=C:\DOS\MONOUMB.386 3. Save the file, and restart your computer. 4. After your computer starts, run MemMaker by typing MEMMAKER at the command prompt. 5. Choose Custom Setup. On the Advanced Options screen, answer Yes to the question "Use monochrome region (B000-B7FF) for running programs?" Follow the instructions on your screen. 2.4 Using MemMaker with IBM LAN Before you run MemMaker, you might need to make adjustments to the parameters specified for your IBM LAN support driver, DXMC0MOD.SYS. In your CONFIG.SYS file, make sure that the DEVICE command that loads DXMC0MOD.SYS includes one of the following before you run MemMaker: o The first three parameters, as in the following example: DEVICE=C:\DXMC0MOD.SYS 4000000000
a