Re: [Freedos-user] NTFS4DOS and FreeDOS - Works with UMBPCI, Fails with EMM386
Hi! 11-Июл-2005 17:51 [EMAIL PROTECTED] (Michael Devore) wrote to freedos-user@lists.sourceforge.net: MD> Never load a driver, shell, or application before HIMEM and EMM386. They MD> are fundamental first loaders as they configure your basic memory MD> situation. That SHELL command has got to come later in CONFIG.SYS. The MD> rest should be fine, although I'd still stick them afterwards for form's MD> sake. >>SHELL=a:\command.com /p >>1234?DEVICE=A:\FDOS\HIMEM.EXE SHELL is parsed later than any DEVICE statement, together with INSTALL and SET. And it not changes anything, beside internal buffer, where remembered argument of this statement. --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] NTFS4DOS and FreeDOS - Works with UMBPCI, Fails with EMM386
Hi Michael: Ok, this fails with BOTH UMBPCI and EMM386 in my Emachines T1600 and on an HP Pavillion P4. It works with UMBPCI and not EMM386 on a Dell D600. I guess I need to try DOS=HIGH without UMB, but I'm beginning to think NTFS4DOS is busted. Next step I suppose is to try MSDOS 6.22, like the instructions say, with UMBPCI and EMM386 on the two of these machines do. I also purchased a license from Datapol and I'm asking their tech support about this. We'll see if it was worth $25.00! Thanks again for all of your help. I will keep you posted. Mark > At 04:14 PM 7/13/2005 -0400, Mark Bailey wrote: > > >Will try DOS=HIGH only. Thanks! Too bad UMBPCI doesn't > >work on all the computers. :-( > > Well, if DOS=HIGH doesn't do it, I may have to d/l NTFS4DOS myself, force > 64K UMB, and see if I get the same fragmentation. Something bizarre going > on with NTFS4DOS anyway, what with it eating 400K of memory in conventional > if can't load in upper memory of 58K space. > > > > > --- > This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening > July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual > core and dual graphics technology at this free one hour event hosted by HP, > AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user --- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] NTFS4DOS and FreeDOS - Works with UMBPCI, Fails with EMM386
At 04:14 PM 7/13/2005 -0400, Mark Bailey wrote: Will try DOS=HIGH only. Thanks! Too bad UMBPCI doesn't work on all the computers. :-( Well, if DOS=HIGH doesn't do it, I may have to d/l NTFS4DOS myself, force 64K UMB, and see if I get the same fragmentation. Something bizarre going on with NTFS4DOS anyway, what with it eating 400K of memory in conventional if can't load in upper memory of 58K space. --- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] NTFS4DOS and FreeDOS - Works with UMBPCI, Fails with EMM386
Hi Michael: OK, I believe the application does use VGA graphics. :-( Will try DOS=HIGH only. Thanks! Too bad UMBPCI doesn't work on all the computers. :-( Mark Michael Devore wrote: At 08:23 AM 7/13/2005 -0400, Mark Bailey wrote: OK. Development Kernel, Development command.com, Development SYS, new emm386/himem, NTFS4DOS 1.4. The INSTALLHIGH failed. Interestingly, a "LOADHIGH" failed with ALMOST the same error and a little more information: DOS/32A fatal (1001): DOS reported insufficient memory, additional 1KB needed! Something is still fragmenting your upper memory by eating little bits away in the middle of large chunks you need. I can't figure out what's doing it. You have enough upper memory, you just don't have enough all in one block. Alright, another suggestion: if your application doesn't use VGA graphics and you're up for a bit of unorthodox reclamation, try keeping the last test CONFIG.SYS and adding I=A000-AFFF to your EMM386 line as another option. That will give another 64K block to upper memory. If you can reclaim the VGA graphics area for upper memory with EMM386, post us another MEM /F /X report so we can see if it is getting fragmented, as well. Second suggestion: Take out the UMB part of DOS=HIGH,UMB and just have DOS=HIGH. If NTFS4DOS can use upper memory directly from EMM386 instead of through the DOS interface, it just might work. Not all applications and drivers can directly use UMBs that way, though, so I don't know if it will work. --- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user --- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] NTFS4DOS and FreeDOS - Works with UMBPCI, Fails with EMM386
At 08:23 AM 7/13/2005 -0400, Mark Bailey wrote: OK. Development Kernel, Development command.com, Development SYS, new emm386/himem, NTFS4DOS 1.4. The INSTALLHIGH failed. Interestingly, a "LOADHIGH" failed with ALMOST the same error and a little more information: DOS/32A fatal (1001): DOS reported insufficient memory, additional 1KB needed! Something is still fragmenting your upper memory by eating little bits away in the middle of large chunks you need. I can't figure out what's doing it. You have enough upper memory, you just don't have enough all in one block. Alright, another suggestion: if your application doesn't use VGA graphics and you're up for a bit of unorthodox reclamation, try keeping the last test CONFIG.SYS and adding I=A000-AFFF to your EMM386 line as another option. That will give another 64K block to upper memory. If you can reclaim the VGA graphics area for upper memory with EMM386, post us another MEM /F /X report so we can see if it is getting fragmented, as well. Second suggestion: Take out the UMB part of DOS=HIGH,UMB and just have DOS=HIGH. If NTFS4DOS can use upper memory directly from EMM386 instead of through the DOS interface, it just might work. Not all applications and drivers can directly use UMBs that way, though, so I don't know if it will work. --- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] NTFS4DOS and FreeDOS - Works with UMBPCI, Fails with EMM386
Hi Michael: OK. Development Kernel, Development command.com, Development SYS, new emm386/himem, NTFS4DOS 1.4. The INSTALLHIGH failed. Interestingly, a "LOADHIGH" failed with ALMOST the same error and a little more information: DOS/32A fatal (1001): DOS reported insufficient memory, additional 1KB needed! Thanks again for your help. I think this application (NTFS4DOS) is potentially very useful for a broad range of FreeDOS users and will solve many problems for Amateur Radio users if it works reliably! Mark config.sys: - DOS=HIGH,UMB SHELL=a:\command.com a:\ /p DEVICE=A:\FDOS\HIMEM.EXE DEVICE=a:\fdos\emm386.exe x=test memcheck vds noems max=256M installhigh=a:\datapol\ntfs4dos.exe a:\command.com a:\ /p - autoexec.bat - ECHO Autoexec.bat - mem /x /f - Segment Size Name Type --- -- - 0271 9136 DOS system data 0273 192FILES data area 0280 2528HIMEM device driver 031f 3344EMM386 device driver 03f1 480FILES data area 0410 448LASTDRV data area 042d 2048STACKS data area 04ad 32 free 04b0 2992 COMMAND program 056c 64 MEM environment 057148240 MEM program 1139 580688 free 9f00 200704 reserved d00038480 free d96624416 free df5d 2304 free dfee 272 COMMAND environment Testing XMS memory ... INT 2F AX=4309 supported XMS version 3.00 XMS driver version3.11 HMA state existsA20 line stateenabled Free XMS memory 534377472 bytes Largest free XMS block534377472 bytes Free handles 69 Block Handle Size Locks --- --- 0 18029379841 1 18121054720 Free upper memory 65248 bytes Largest upper block 38496 bytes Memory TypeTotal Used Free Conventional 636K22K 614K Upper 64K 0K64K Reserved 324K 324K 0K Extended (XMS)522,936K 1,083K 521,853K Total memory 523,960K 1,429K 522,531K Total under 1 MB 700K22K 678K Largest executable program size 614K (628,944 bytes) Largest free upper memory block38K ( 38,496 bytes) FreeDOS is resident in the high memory area. - Michael Devore wrote: At 02:11 AM 7/13/2005 +, you wrote: [...] Try this. Take out everything except HIMEM, EMM386, and NTFS4DOS. Keep the SHELL and DOS=HIGH,UMB lines. Can the rest. Take out DOSDATA=UMB. Turn off TDSK, turn off the mouse, AUTOEXEC drivers, everything else. Reboot and report MEM /F /X. --- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] NTFS4DOS and FreeDOS - Works with UMBPCI, Fails with EMM386
At 02:11 AM 7/13/2005 +, you wrote: Hi Michael: Thanks again for the help. That didn't change the symptoms at all from just using NOEMS...still get the error from DOS/32A! What does DOSDATA=UMB do? I am booting from a USB floppy drive most of the time...occasionally from a CD with a 1.44MByte floppy disk image. Development kernel, command.com, and SYS command. New himem.exe/emm386.exe. Whatever's going on it's not happening from EMM386, but your figures don't make a lot of sense. DOS is handling UMBs and they are fragmented for no apparent reason. Try this. Take out everything except HIMEM, EMM386, and NTFS4DOS. Keep the SHELL and DOS=HIGH,UMB lines. Can the rest. Take out DOSDATA=UMB. Turn off TDSK, turn off the mouse, AUTOEXEC drivers, everything else. Reboot and report MEM /F /X. --- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] NTFS4DOS and FreeDOS - Works with UMBPCI, Fails with EMM386
Hi Michael: Thanks again for the help. That didn't change the symptoms at all from just using NOEMS...still get the error from DOS/32A! What does DOSDATA=UMB do? I am booting from a USB floppy drive most of the time...occasionally from a CD with a 1.44MByte floppy disk image. Development kernel, command.com, and SYS command. New himem.exe/emm386.exe. NTFS4DOS failed to load at all. config.sys: !LASTDRIVE=Z !BUFFERS=20 !FILES=40 !DOS=HIGH,UMB !DOSDATA=UMB echo NTFS4DOS included by permission from datapol gmbh, germany echo NTFS4DOS and this CD may only be used on "private computers" echo and for "private uses" echo See www.datapol.de/dpd. echo Mark Bailey, [EMAIL PROTECTED], July 12, 2005 - Alpha 1.0 SHELL=a:\command.com a:\ /p !MENUCOLOR=7,0 MENUDEFAULT=1,5 MENU 1 - Boot FreeDOS without NTFS4DOS MENU 2 - Boot FreeDOS with NTFS4DOS 12?DEVICE=A:\FDOS\HIMEM.EXE 12?DEVICE=a:\fdos\emm386.exe x=test memcheck vds noems max=256M 2?installhigh=a:\datapol\ntfs4dos.exe a:\command.com a:\ /p 12?DEVICE=a:\fdos\tdsk.exe 4096 -- mem /f /x Segment Size Name Type --- -- - 0271 6512 DOS system data 0273 192FILES data area 0280 2528HIMEM device driver 031f 3344EMM386 device driver 03f1 384TDSKdevice driver 0409 48 free 040d 2992 COMMAND program 04c9 96 MEM environment 04d048240 MEM program 1098 583264 free 9f00 200704 reserved d000 6368 DOS system data d002 64DEVICE data area d007 1904FILES data area d07f 2288LASTDRV data area d10f 2048STACKS data area d18f 3312 CTMOUSE program d25f28752 free d96524416 free df5c 2304 free dfed 288 COMMAND environment Testing XMS memory ... INT 2F AX=4309 supported XMS version 3.00 XMS driver version3.11 HMA state existsA20 line stateenabled Free XMS memory 530183168 bytes Largest free XMS block530183168 bytes Free handles 68 Block Handle Size Locks --- --- 0 18029379841 1 1812 41943040 2 18221054720 Free upper memory 55520 bytes Largest upper block 28768 bytes Memory TypeTotal Used Free Conventional 636K19K 617K Upper 64K10K54K Reserved 324K 324K 0K Extended (XMS)522,936K 5,179K 517,757K Total memory 523,960K 5,532K 518,428K Total under 1 MB 700K29K 671K Largest executable program size 617K (631,520 bytes) Largest free upper memory block28K ( 28,768 bytes) FreeDOS is resident in the high memory area. > At 01:31 PM 7/12/2005 -0400, Mark wrote: > > >OK, here is the config.sys file I used with emm386. Note > >that including NOEMS on the command line causes the > >installhigh to FAIL with: > >DOS/32A fatal (1002): DOS reported insufficient memory > > Well, the problem is here. You need the NOEMS option to free up that upper > memory to get NTFS4DOS into it. NTFS4DOS fails to load into the upper > memory after NOEMS and complains about it with a cryptic message from the > extender. This even though 64K UMB is available, same as with > UMBPCI. NTFS4DOS also using a horrible amount of conventional memory > beyond the 64K that's in upper memory when it does work, which makes me > think it has a bug. > > Ah! Just remembered a factoid. DOS/32A is one of those extenders that > fails if too much VCPI memory is available. Try this: Add NOEMS option > AND add the option MAX=256M too. That will limit VCPI memory below the > trouble-spot with it. Give us a MEM /F /X report with the NOEMS and > MAX=256M options in place. > > > > > --- > This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening > July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual > core and dual graphics technology at this free one hour event hosted by HP, > AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user --- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July
Re: [Freedos-user] NTFS4DOS and FreeDOS - Works with UMBPCI, Fails with EMM386
At 01:31 PM 7/12/2005 -0400, Mark wrote: OK, here is the config.sys file I used with emm386. Note that including NOEMS on the command line causes the installhigh to FAIL with: DOS/32A fatal (1002): DOS reported insufficient memory Well, the problem is here. You need the NOEMS option to free up that upper memory to get NTFS4DOS into it. NTFS4DOS fails to load into the upper memory after NOEMS and complains about it with a cryptic message from the extender. This even though 64K UMB is available, same as with UMBPCI. NTFS4DOS also using a horrible amount of conventional memory beyond the 64K that's in upper memory when it does work, which makes me think it has a bug. Ah! Just remembered a factoid. DOS/32A is one of those extenders that fails if too much VCPI memory is available. Try this: Add NOEMS option AND add the option MAX=256M too. That will limit VCPI memory below the trouble-spot with it. Give us a MEM /F /X report with the NOEMS and MAX=256M options in place. --- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] NTFS4DOS and FreeDOS - Works with UMBPCI, Fails with EMM386
Hi Michael: First, let me say thanks to you and Eric Auer and everyone else for the amazing support I've gotten in my efforts to learn and use FreeDOS. I've used many commercial operating systems, and this level of support is better than I have seen with any of them! OK, here is the config.sys file I used with emm386. Note that including NOEMS on the command line causes the installhigh to FAIL with: DOS/32A fatal (1002): DOS reported insufficient memory I was able to write these files directly to my NTFS WinXP disk while FreeDOS was running. I have also enclosed the same things from UMBPCI. Note that, as nearly as I can tell, the NTFS4DOS program did not load into high memory using emm386. EMM386 - config.sys - !LASTDRIVE=Z !BUFFERS=20 !FILES=40 !DOS=HIGH,UMB !DOSDATA=UMB echo NTFS4DOS included by permission from datapol gmbh, germany echo NTFS4DOS and this CD may only be used on "private computers" echo and for "private uses" echo See www.datapol.de/dpd. echo Mark Bailey, [EMAIL PROTECTED], July 12, 2005 - Alpha 1.0 SHELL=a:\command.com a:\ /p DEVICE=A:\FDOS\HIMEM.EXE DEVICE=a:\fdos\emm386.exe x=test memcheck vds DEVICE=a:\fdos\tdsk.exe 4096 installhigh=a:\datapol\ntfs4dos.exe a:\command.com a:\ /p - MEM /F - Segment Size Name Type --- -- - 027112880 DOS system data 0273 192FILES data area 0280 2528HIMEM device driver 031f 3344EMM386 device driver 03f1 384TDSKdevice driver 040a 64DEVICE data area 040f 1904FILES data area 0487 2288LASTDRV data area 0517 2048STACKS data area 0597 48 NTFS4DOSdata area 059b 335104 NTFS4DOSprogram 576c65280 NTFS4DOSdata area 675d 64 NTFS4DOSdata area 6762 16 NTFS4DOSdata area 6764 32 free 6767 2992 COMMAND program 6823 80 free 6829 3312 CTMOUSE program 68f9 96 MEM environment 690048240 MEM program 74c8 166032 free 9d52 272 COMMAND environment 9d64 6576 Memory TypeTotal Used Free Conventional 636K 427K 209K Upper 0K 0K 0K Reserved 388K 388K 0K Extended (XMS)522,936K29,691K 493,245K Total memory 523,960K30,506K 493,454K Total under 1 MB 636K 427K 209K Total Expanded (EMS) 32M (33,554,432 bytes) Free Expanded (EMS) 32M (33,538,048 bytes) Largest executable program size 209K (214,288 bytes) FreeDOS is resident in the high memory area. - MEM /X - Testing XMS memory ... INT 2F AX=4309 supported XMS version 3.00 XMS driver version3.11 HMA state existsA20 line stateenabled Free XMS memory 505082880 bytes Largest free XMS block505082880 bytes Free handles 63 Block Handle Size Locks --- --- 0 18028724481 1 1812 41943040 2 1822 15728641 3 1832 15728641 4 1842 31457281 5 1852 62914561 6 1862 125829121 7 18721054720 Upper memory not available Memory TypeTotal Used Free Conventional 636K 427K 209K Upper 0K 0K 0K Reserved 388K 388K 0K Extended (XMS)522,936K29,691K 493,245K Total memory 523,960K30,506K 493,454K Total under 1 MB 636K 427K 209K Total Expanded (EMS) 32M (33,554,432 bytes) Free Expanded (EMS) 32M (33,538,048 bytes) Largest executable program size 209K (214,288 bytes) FreeDOS is resident in the high memory area. UMBPCI example: config.sys - !LASTDRIVE=Z !BUFFERS=20 !FILES=40 !DOS=HIGH,UMB !DOSDATA=UMB echo NTFS4DOS included by permission from datapol gmbh, germany echo NTFS4DOS and this CD may only be used on "private computers" echo and for "private uses" echo See www.datapol.de/dpd. echo Mark Bailey, [EMAIL PROTECTED], July 12, 2005 - Alpha 1.0 SHELL=a:\command.com a:\ /p DEVICE=A:\FDOS\HIMEM.EXE DEVICE=a:\fdos\umbpci.sys DEVICE=a:\fdos\tdsk.exe 4096 installhigh=a:\datapol\ntfs4dos.exe a:\command.com a:\ /p - MEM /F - Segment Size Name Type --- -- --
Re: [Freedos-user] NTFS4DOS and FreeDOS - Works with UMBPCI, Fails with EMM386
At 08:03 AM 7/12/2005 -0400, Mark wrote: So far, NTFS4DOS INSTALLHIGH works with UMBPCI but not with EMM386. I have 213K of conventional memory free when running NTFS4DOS from the command line or using INSTALLHIGH with EMM386 and 550K of conventional memory free when using UMBPCI. We need a MEM /F report on the 213K conventional memory. If that doesn't show extended memory, a MEM /X report, as well. --- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] NTFS4DOS and FreeDOS - Works with UMBPCI, Fails with EMM386
Good morning, Michael, Eric, et al: The addition of "NOEMS" to the EMM386 startup in config.sys caused the following error when executing the INSTALLHIGH. DOS/32A fatal (1002): DOS reported insufficient memory It did eliminate the complaints about page frames and no suitable UMB memory block. The test computer is a Dell Inspiron D600 laptop, usually tied to a docking station and using a USB floppy drive or CD to boot FreeDOS. So far, NTFS4DOS INSTALLHIGH works with UMBPCI but not with EMM386. I have 213K of conventional memory free when running NTFS4DOS from the command line or using INSTALLHIGH with EMM386 and 550K of conventional memory free when using UMBPCI. In other words, entry 3 (without NOEMS) leaves insufficient conventional memory and entry 4 works as desired. config.sys for latest test: !LASTDRIVE=Z !BUFFERS=20 !FILES=40 !DOS=HIGH,UMB !DOSDATA=UMB !set dircmd=/ogn !MENUCOLOR=7,0 MENUDEFAULT=1,5 MENU 1 - Load FreeDOS including HIMEM XMS-memory driver MENU 2 - Load FreeDOS + HIMEM + EMM386 MENU 3 - Load NTFS4DOS with EMM386 MENU 4 - Load NTFS4DOS with UMBPCI SHELL=a:\command.com /p 1234?DEVICE=A:\FDOS\HIMEM.EXE 23?DEVICE=A:\FDOS\EMM386.EXE X=TEST MEMCHECK VDS NOEMS 4?DEVICE=a:\fdos\umbpci.sys 34?installhigh=a:\datapol\ntfs4dos.exe a:\command.com /k Without NOEMS, the INSTALLHIGH completes without error and NTFS4DOS is loaded, but it appears to be loaded into conventional memory. Using UMBPCI, it appears to be loaded into upper memory. Thanks again for all of your help. Mark --- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] NTFS4DOS and FreeDOS - Works with UMBPCI, Fails with EMM386
Never load a driver, shell, or application before HIMEM and EMM386. They are fundamental first loaders as they configure your basic memory situation. That SHELL command has got to come later in CONFIG.SYS. The rest should be fine, although I'd still stick them afterwards for form's sake. Besides that, in what you have, you have little free upper memory and what is there is being used by the EMS page frame. I strongly recommend specifying NOEMS on the EMM386 command line and regaining 64K of upper memory. That presumes you're not using an application which needs EMS, which you must not be if you're not loading EMM386 anyway. At 06:06 PM 7/11/2005 -0400, Mark Bailey wrote: I have NTFS4DOS working and loading high with FreeDOS! However, I have been unable to get it to load high with EMM386. I am using the latest development kernel, emm204x, and the latest UMBPCI. MEM reports 213K conventional memory with EMM386 and 550K conventional memory with UMBPCI! :-) Here is my config.sys file: !LASTDRIVE=Z !BUFFERS=20 !FILES=40 !DOS=HIGH,UMB !DOSDATA=UMB !set dircmd=/ogn !MENUCOLOR=7,0 MENUDEFAULT=1,5 MENU 1 - Load FreeDOS including HIMEM XMS-memory driver MENU 2 - Load FreeDOS + HIMEM + EMM386 MENU 3 - Load NTFS4DOS with EMM386 MENU 4 - Load NTFS4DOS with UMBPCI SHELL=a:\command.com /p 1234?DEVICE=A:\FDOS\HIMEM.EXE 23?DEVICE=A:\FDOS\EMM386.EXE X=TEST MEMCHECK VDS 4?DEVICE=a:\fdos\umbpci.sys 34?installhigh=a:\datapol\ntfs4dos.exe a:\command.com /k I have no idea why this doesn't work with EMM386. I get a strange warning from EMM386: selected page frame e000 not available, searching automatically using PAGEFRAME d000: no suitable UMB memory block found --- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] NTFS4DOS and FreeDOS - Works with UMBPCI, Fails with EMM386
Good day all: After some help and advice from Eric Auer and Michael Devore, I have NTFS4DOS working and loading high with FreeDOS! However, I have been unable to get it to load high with EMM386. I am using the latest development kernel, emm204x, and the latest UMBPCI. MEM reports 213K conventional memory with EMM386 and 550K conventional memory with UMBPCI! :-) Here is my config.sys file: !LASTDRIVE=Z !BUFFERS=20 !FILES=40 !DOS=HIGH,UMB !DOSDATA=UMB !set dircmd=/ogn !MENUCOLOR=7,0 MENUDEFAULT=1,5 MENU 1 - Load FreeDOS including HIMEM XMS-memory driver MENU 2 - Load FreeDOS + HIMEM + EMM386 MENU 3 - Load NTFS4DOS with EMM386 MENU 4 - Load NTFS4DOS with UMBPCI SHELL=a:\command.com /p 1234?DEVICE=A:\FDOS\HIMEM.EXE 23?DEVICE=A:\FDOS\EMM386.EXE X=TEST MEMCHECK VDS 4?DEVICE=a:\fdos\umbpci.sys 34?installhigh=a:\datapol\ntfs4dos.exe a:\command.com /k I have no idea why this doesn't work with EMM386. I get a strange warning from EMM386: selected page frame e000 not available, searching automatically using PAGEFRAME d000: no suitable UMB memory block found This may be unrelated! Thanks again for the help. I'd like to get it working with EMM386 and will be willing to help with testing. Mark Bailey --- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user