Re: [Freedos-user] Problems after adding more RAM
Hello, 2009/2/4 Eric Auer e.a...@jpberlin.de: FreeDOS KEYB 2.0 (pre4) Critical error: cannot allocate memory. DOS reported error: 8 For DISPLAY, you would expect XMS to be used, but for KEYB? That is MCB allocate, function 48h. Used to allocate data in an independent MCB block, so that KEYB is made independent from the problem by which you load a second keyboard layout which is bigger than the first one. I see you're also using 2.0-pre4, somewhat old. Anyway, I recommend forthcomming KEYB 2.01, which fixes several bugs (just in case). Aitor -- Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] Problems after adding more RAM
Hi! Recently I did expand my computer from 1 GB to 2 GB of RAM. Finally I checked that it's running well with Memtest86+ V2.11. I am also pretty sure that the harddisk can not be the problem as it's a mobile disk and working on other configurations ok. For now I found two strange behavior. At minimal configuration, just with himem and emm386. DEVICE=C:\FDOS\BIN\HIMEM.EXE DEVICE=C:\FDOS\BIN\EMM386.EXE FreeDOS KEZB 2.0 (pre4) Critical error: cannot allocate memory. DOS reported error: 8 Setting the RAM to use only a reasonable maximum did not help. DEVICE=C:\FDOS\BIN\HIMEM.EXE /MAX=3 DEVICE=C:\FDOS\BIN\EMM386.EXE MAX=3 DEVICE=C:\FDOS\BIN\HIMEM.EXE /MAX=3 /TESTMEM:ON DEVICE=C:\FDOS\BIN\EMM386.EXE MAX=3 NOEMS When using NOEMS the bug did not appear. (But therefore still others, crashing extenders and such.) The next strange thing is that I couldn't get ctmouse 1.8 and 1.9 to work for normally good applications such as FreeEDIT. It was working before well. To locate the bug I used minimal configuration files. When using shell=c:\fdos\bin\command.com /E:4096 the bug appears (was working before!), when using shell=c:\fdos\bin\command.com mouse will work again. I would like to prefer to continue to use /E:4096 and also to get the keyb/memory problems fixed. regards, -mr -- Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Problems after adding more RAM
Hi! Recently I did expand my computer from 1 GB to 2 GB of RAM. At minimal configuration, just with himem and emm386. Try updating to HIMEMX and JEMM386, but take care that those default to giving you as much RAM as possible, without trying to protect DOS apps from the horror of having unbelievably much of it ;-). You have various command line options to limit available RAM in various ways, when seen through various APIs. FreeDOS KEYB 2.0 (pre4) Critical error: cannot allocate memory. DOS reported error: 8 For DISPLAY, you would expect XMS to be used, but for KEYB? Did you try without EMM386 and/or without HIMEM? DEVICE=C:\FDOS\BIN\EMM386.EXE MAX=3 NOEMS When using NOEMS the bug did not appear. (But therefore still others, crashing extenders and such.) That most likely means that some of your UMB area is bad! With NOEMS, there is no page frame, and DOS can use more UMB for other things, so the bad area is touched later. You should try to find the right X=?-? option for EMM386. Modern computers and BIOSes do not always mark reserved UMB areas in ways that are visible to EMM386. For example MMIO or buffers of PCI controllers could be in UMB areas. The next strange thing is that I couldn't get ctmouse 1.8 and 1.9 to work for normally good applications... Let me guess, you have USB emulating PS/2 via BIOS support? Did you try CTMOUSE 2.1 already? shell=c:\fdos\bin\command.com /E:4096 the bug appears shell=c:\fdos\bin\command.com mouse will work again. CTMOUSE defaults to using UMB when possible, even if you do not use LH, so see above. Also, older versions of the CTMOUSE driver even try using ancient UMB interfaces in HIMEM (or even without?) but crash later. You either must use a command line option for CTMOUSE to tell it that it must not use UMB or you have to load EMM386 properly. I would like to prefer to continue to use /E:4096 How on earth can you have so much in your environment? Try the MEMORY command to see how much env FreeCOM uses, but take other the values with care, some are misleading. Eric -- Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
