NTFS driver for DOS takes too much memory

If I remember right...long time ago, can't you just load the driver into expanded memory?
See this link for more info:
http://www.pcguide.com/opt/opt/ramDOS-c.html

I tried a lot of combinations without success,sometimes my computer reboot,sometimes it freezes. Expecially line DEVICE=EMM386.EXE NOEMS makes the computer reboot.

I tried memmaker too,but the computer freezes due to illegal istructions.

I've added this line inside the config.sys of FreeDOS :

DOS=high,auto
DEVICE=c:\mem\HIMEM.SYS

when FreeDOS starts,I see this message :

Kernel : allocated 34 diskbuffers : 18088 bytes in HMA and the computer freezes.

ok. remember that we have 3 solutions :

1) find an NTFS driver that takes less RAM memory and grub can run
2) find a version of dos higher than 8.0 with the set command with the /P parameter.
3) rewrite the script under dos 8.0 or less but using the choice command with the errorlevels instead of set /P.

Not that it matters, but curious as to why you need this nonstandard configuration.

Is this custom software that needs to run?

Can you tell us what you are trying to accomplish so that maybe we can help you find an alternative solution as the people at Sysinternals are generally pretty smart people and if they have made the "NTFS file system driver for dos/windows v.3.02R" there possibly may not be another as there may not be that great a need for this.

If you are trying to accomplish something with some common software, then please give us the name of this software so we can possibly find common solutions for your project.

I'm trying to make a script under DOS that determines what's the architecture,if 32 or 64 bit of the Operating System installed on the first hard disk. When I know it,I will use grub for DOS to boot the right version of Windows PE and with it I make the unattended installation of Windows XP/Vista and 7 at 32 and 64 bit. For example running WINDOWS PE 32 BIT I can migrate (using the USMT tool) configurations / settings from / to these O/S :

Windows XP 32 bit    ---to---> Windows XP 32 bit    
Windows XP 32 bit    -to-> Windows Vista 32 bit
Windows XP 32 bit    -to-> Windows 7 32 bit    
Windows Vista 32 bit –--to---> Windows Vista 32 bit
Windows Vista 32 bit –to-> Windows 7 32 bit    
Windows 7 32 bit      ---to--> Windows 7 32 bit    

and running WINDOWS PE 64 BIT I can migrate configurations/settings from / to these O/S:

Windows XP 64 bit    ---to---> Windows XP 64 bit    
Windows XP 64 bit    -to-> Windows Vista 64 bit
Windows XP 64 bit    -to-> Windows 7 64 bit    
Windows Vista 64 bit  –--to---> Windows Vista 64 bit
Windows Vista 64 bit  –to-> Windows 7 64 bit
Windows 7 64 bit      ---to---> Windows 7 64 bit    

and from / to these O/S :

Windows XP 32 bit    ---to---> Windows XP 64 bit    
Windows XP 32 bit    ---to---> Windows Vista 64 bit
Windows XP 32 bit    ---to---> Windows 7 64 bit    
Windows Vista 32 bit –--to---> Windows Vista 64 bit
Windows Vista 32 bit –--to---> Windows 7 64 bit    
Windows 7 32 bit     –--to---> Windows 7 64 bit

recommending that this question be reposted in the scripting forums although not sure what one is best to see if anyone has any ideas on how to help create the script that you're creating.

I emailed a friend who knows a lot about scripting so I'll check with him as well just having this question transferred to a scripting forum might turn up more results.

scripting forum ? why ? I've already written the script in batch language,the problem is how to boot Windows PE or how to read the NTFS file system from DOS or don't use the DOS...

Maybe someone has already done what you are trying to do so you don't have to reinvent the wheel.

yes,someone already did it,as explained here :

http://www.unet.univie.ac.at/~a0503736/php/drdoswiki/index.php?n=Main.NTFS

it seems that's possible to run MS-DOS 7.1 + Sysinternals NTFSDOS (Will result in NTFS support with LFN but FAT32 support without LFN),so I need to download MS-DOS 7.1 because it says that can run in pure real mode and is compatible with EMS/XMS/DPMI ...,can you help me to configure correctly the memory ? thanks

NTFS4Dos: http://www.free-av.com/en/products/11/avira_ntfs4dos_personal.html
This download creates a 1.44MB boot floppy with Win98SE Dos, a CD mounted as Z, and a ramdisk as Y. It was created by myself in the dark ages: http://www.computer-help.net/FTP-Files/Boot-98SE-CDasZ-RamDr-asY.exe Create one, then inspect the config.sys and autoexec.bat files.  You'll get back a lot of memory if you delete or REM out the CD drivers.
The trick with a succesful implementation of EMM386 is to use the X= , I= , and maybe the Mx switches to make it be happy in modern systems.  Why it is freezing on you is that, without theswitches, it is stomping on some portion of memory in the C000 to EFFF range that is not available for use.  Here is a reference to the switches: http://www.vfrazee.com/ms-dos/6.22/help/emm386.exe.htm

come case I tried :

device=himem.sys
device=emm386.exe ram

---> invalid opcode at FFFF

device=himem.sys
device=emm386.exe 512 frame=d000

---> not enough extended memory to load applications exec "C:\ntfs4dos.exe"

device=himem.sys
device=emm386.exe noems novcpi

---> bad or missing command line interpreter c:\command.com f:\fdos\bin /e:1024 /p=c:\fdauto.bat

what else ?

It seems that I've been lucky,this Memory configuration seems to work well. With it I can run the latest version of GRUB and the NTFS File System Driver for Dos/Windows v.3.02R (read only) by Mark Russinovich and Bryce Cogswell.

fdconfig.sys :

!lastdrive=z
!buffers=20
!files=40
!dos=high,umb
!dosdata=umb
!SET dircmd=/ogn /4
device=c:\himem.exe
shellhigh=c:\command.com c:\fdos\bin /e:1024 /p=c:\fdauto.bat

fdauto.bat

set cfgfile=c:\fdconfig.sys
LH keyb it
LH doslfn.com
LH ntfsdos.exe

thanks.