China DOS Union

NTFS4DOS.EXE is a tool for reading and writing NTFS formatted files. I first store this file in a logical drive letter (drive D) in FAT32 format, and then use a boot disk that supports this file to read it, so as to achieve the purpose of reading and writing NTFS formatted files. Can this process be simplified, and directly place this file in the boot disk, so that it can read this file in the boot drive letter as soon as it starts?

In the README file of the boot disk "GRUBDISK", it is stated that the "NTFS4DOS.EXE" file is in the external command file list of this boot disk. But after booting, when using the dir command, it is not seen, and neither is it seen when using the dir /as command. What's going on? Keep exploring

You can use the "NTFS.EXE" in the external command file table of the boot disk "GRUBDISK".

I don't quite understand the meaning of this post. ntfs4dos.exe is just an ordinary DOS external command. It should be able to run directly on any DOS boot disk.

Of course, I rarely use it, and I don't know what restrictions there are when putting it on the boot disk to start.

I used a USB drive boot disk (with only those three basic files) to test, and this external command cannot run. With other downloaded boot disks, some can and some can't. Actually, in terms of reading and writing under NTFS format, in my experience, IFS should be the best.

What is the error message that cannot run? Is it because there is not enough memory? If so, load himem.sys in config.sys.

It looks normal. First, there is "DO YOU USE THE VERSION OF NTFS4DOS ON PRIVITE COMPUTER ONLY" (Y/N). After entering "Y", there is a prompt of "G: DISK1 VOLUMEL 8037MB WINDOWS NT NTFS". But when I then enter G: after the cursor, it is "INVALID DRIVE SPECIFICATION". Changing to other ones like H: I: etc., also gets this prompt, and I can't enter the NTFS - formatted C drive at all.

The error message that cannot run is:
HARD DRIVE PARTITIONS NOT FOUND BY XP_SHELL

Hope to get your guidance, thanks in advance!

[ Last edited by renrenlove on 2007-2-6 at 12:13 PM ]

I suspect this problem may be related to the fact that ntfs4dos needs to write to the disk when running. Since I have hardly used this program myself, I can't help you judge. You can try it yourself:

1. Copy ntfs4dos.exe from the floppy disk to the hard disk and run it to see if it can succeed.
2. Add the function of creating a RamDisk on the boot floppy, and then copy ntfs4dos.exe to the memory disk and run it.

Everything depends on the feedback to decide the subsequent operations.

It is suggested to use IFS. There are many versions of it. Only one version works well, which is the one with the 850\866 files.

Today I've gained new knowledge again, really great!!!

First, thank you all for your enthusiastic help!

Just to explain, it's about making a USB drive bootable.

1. Loading ntfs4dos.exe into RamDisk and then executing it is ineffective! (Same prompt)
2. After selecting boot Dos 7.10 (win98se) Only on the boot floppy and then loading ntfs4dos.exe successfully!
Therefore, it's confusing!

Currently testing IFS, (the one with 850\866 files)
Also try copying ntfs4dos.exe to the hard drive and running it to see if it can succeed.

[ Last edited by renrenlove on 2007-2-6 at 09:56 PM ]

If all the above tests are not successful!
Then, after using IFS, it prompts that LFN has been loaded!
Why can it succeed when loading ntfs4dos.exe after selecting boot Dos 7.10 (win98se) Only to boot from the floppy disk? What is missing?
Still hope for guidance, thank you!

So it has nothing to do with whether it's put on a floppy disk or not, but rather with the configuration of different boot disks. This might be because another boot disk loaded a program that conflicts with ntfs4dos, or didn't load a program that ntfs4dos needs. Study the config.sys and autoexec.bat of the corresponding boot disk, and you should be able to find the reason.

Similar to the config.sys and autoexec.bat of the corresponding boot disk, the boot process is basically the same. The difference is that on the USB flash drive, change A:\ (drive) to C:\ (drive), so the action is completed in the same way. Creating XMSDSK is also successful, with the same size. Creating the TEMP folder on the default drive (USB flash drive) is also successful, and there is no CD-ROM loaded. According to the help of ntfs4dos, executing ntfs4dos /r20 creates a 20MB Ramdisk by ntfs4dos. It prompts that ntfs4dos has run, but not like the one executed on the floppy disk.

Continuing to look forward to guidance!