中国DOS联盟

After loading IFS, it cannot run

It runs normally here with NTFSPRO and IFS

By the way, is it quite difficult for TODISK to break through and recognize NTFS drive letters after loading ntfs4dos or IFS under the current situation?

As per your request, this function has been added!

The usage is as follows: (Add -NTFSPRO or -IFS at the end of the original parameters)

For example:
TOdisk -P -NTFSPRO
In this way, the drive letter of the newly added NTFS partition will be displayed

TOdisk -P -IFS
In this way, the newly added NTFS and Linux, etc. drive letters will be displayed

For other functions of TODISK that support drive letters, the usage is the same
For example:

If G: is a newly added NTFS partition:
TODISK G: TO (D:\FILE) -NTFSPRO

(The functions that only support floppy drive letters to handle disk sectors (or with offsets) do not support hard drive letter parameters,
such as
TODISK -DWF ...
TODISK -PDB....
And similar functions above, these functions originally do not support hard drive letters...

It must be like this:
TODISK -DWF 1 123 34 FILE 12345
Wait,
However, only floppy drive letters are okay:
TODISK -DWF A: 123 34 FILE 12345
)




However, it is still recommended to use numbers to represent partitions: 1:2, 2:3, etc., which will not be wrong
If various disk drivers are loaded situationally, then the drive letters may be messed up.



It seems that the IFS driver does not support USB drives and mobile hard drives, and it seems that it cannot assign drive letters to them... Please note

Updated and uploaded!



NTFSPRO or IFS have very unstable support for NTFS under DOS, and are prone to data loss.

It is not recommended to use them to write to NTFS partitions!!

Last edited by GOTOmsdos on 2007-4-17 at 07:00 AM ]

I don't know if there is any problem with the version of the original poster. I will help you test it when I have time.

Originally posted by GOTOmsdos at 2007-4-16 04:15:


NTFSPRO and IFS both run normally here.

As per your request, this function has been added!

The usage is as follows: (add -NTFSPRO or -IFS at the end of the original parameters)

For example:
TOdisk - ...

By the way, there are also problems with the disk writing of NTFS by NTFS4DOS 1.9 cracked version on some computers.

For 100% write support, currently only the DOS version of Paragon Partition Manager 8.05 may be available.
See the link below
http://www.cn-dos.net/forum/viewthread.php?tid=29497&fpage=1&highlight=

I have tried the new version of TODISK. Indeed, it can display the drive letters after loading NTFS4DOS.
Input in DOS: 2:1 to (2:2\ccc.gho=c6)
As a result, the content of ccc.gho is:
zlib-1.2.3.f-GOTOmsdos-grub2linux-v1.0
Continue to input: 2:3 to (d:\eee.gho=c6) The result content is the same as above.
There was a prompt for the file name. After entering the file name, there was a prompt. Press Y and press Enter! But the operation was not successful.

Originally posted by cchessbd at 2007-4-16 08:56 AM:
I don't know if there are any issues with the version you provided.
I'll test it when I have time.

Well, okay! Thanks..

The bugs found have been fixed, and there are currently no new bugs....
You are welcome to test while playing whenever you have time...

Last edited by GOTOmsdos on 2007-4-16 at 11:19 AM ]

Originally posted by terse at 2007-4-16 09:07 AM:
Tried the new version of TODISK. Indeed, it can display the drive letters after loading NTFS4DOS.
Enter in DOS: 2:1 to (2:2\ccc.gho=c6)
As a result, the content of ccc.gho is:
zlib-1.2.3.f-GOTOmsdos-grub2linux-v1.0
Continue to enter ...

First:
2:2\FILE is not supported. Only drive letters can be used together with files.
In this case, TODISK will give the following warning:

2, Not a drive letter
Failed to create file "2:2\ccc.gho=c6"
Change to another file ,press C
Exit, press E
Y,N ?

Second:
It should be no problem. I don't know if it's a problem with NTFSPRO/IFS..
If NTFSPRO/IFS is not used normally, I guarantee there is no problem!
You can give it a try, don't load NTFSPRO/IFS, and see if the data is normal?
If it's normal, it means it's a problem with NTFSPRO/IFS..

Also, I just tried, load NTFSPRO, run TODISK with =C parameter (compression), and it will fail to compress. No problem without compression. (Found that NTFSPRO uses 138 KB of memory, and it's all in conventional memory!! My goodness!
However, it's also possible that there is a conflict between the ZLIB compression engine and NTFSPRO

With IFS, it's all okay (it only uses 80KB)

Last edited by GOTOmsdos on 2007-4-16 at 12:47 PM ]

Updates are as follows:
1
Modified the code related to reference pointers to make it safer.
2
Streamlined some code

Re - uploaded

Last edited by GOTOmsdos on 2007 - 4 - 17 at 07:00 AM ]

The only one that currently supports 100% writing is probably the DOS version of Paragon Partition Manager 8.05

Next, let's give it a try...

I don't know if there are any special requirements for TODISK?
Several times when booting to DOS, it freezes!
I know it's related to my AUTOEXEC and CONFIG.SYS files! (I could use TODISK in the afternoon),
Can a kind person post the contents of your AUTOEXEC.BAT and CONFIG.SYS, not all of them, or help me see what's wrong with mine! Also thank you!
(In addition, I found that without loading NTFS4DOS; using -NTFSPRO also gave an NTFS-mapped drive letter! That is, the result is the same before and after loading NTFS4DOS using the -NTFSPRO parameter)
My AUTOEXEC.BAT:
@ECHO OFF
tw /np N3 >nul
SET DIRCMD=/OGN /4
SET PROMPT=$P$G
SET HDPMI=16384
SET RAMDRIVE=x:\
XMSDSK 2048 %RAMDRIVE% /T /Y>NUL
PATH=%RAMDRIVE%;
COPY COMMAND.COM %RAMDRIVE%>NUL
SET COMSPEC=%RAMDRIVE%COMMAND.COM
MD %RAMDRIVE%TEMP
SET TEMP=%RAMDRIVE%TEMP
CD>%TEMP%\BOOTDRV.INI
vol>%TEMP%\VOL.TXT
cls
:start
call w.bat box (+white on +blue) @dos.scr:start
if errorlevel 100 goto end
if errorlevel 4 goto re
if errorlevel 3 goto end
if errorlevel 2 goto wdos
:x
IF EXIST dos.ex_ COPY dos.ex_ %RAMDRIVE%dos.zip>NUL
IF EXIST unzip.EXE COPY unzip.EXE %RAMDRIVE%unzip.exe>NUL
%RAMDRIVE%
cd\
unzip -d dos.zip >nul
del dos.zip >nul
menu
goto end
:wdos
mouse >nul
mousp >nul
DOSKEY >nul
DOSLFN /z:Cp936uni.tbl >nul
goto :eof
:re
r
goto end
:END
tw /q
mouse /q>nul
mousp /q>nul
DOSKEY /q>nul
DOSLFN /q >nul
cls
CONFIG.SYS content:
device=himem.sys /testmem:off
FILES=20
BUFFERS=30
SHELL=COMMAND.COM /P /F /E:4096
FCBS=4,0
STACKS=9,256
DOS=HIGH,UMB,AUTO
lastdrive=z

Last edited by terse on 2007-4-16 at 01:10 PM ]

Without loading NTFS4DOS; using -NTFSPRO also gives NTFS extended drive letters!

TOdisk gives additional drive letters independent of their program; it's just based on their logic. That is, if you don't run them, DOS system doesn't recognize these additional drive letters. But in TODISK, you can still use them to directly represent partitions instead of numbers! (This is also an interesting feature of TODISK, but it's not recommended)

For example: G: (NTFS partition, which is 1:5), and neither NTFSPRO/IFS is loaded

The following doesn't work:
TODISK C: TO (G:\FILE) DOS system doesn't recognize G:

The following works:
TODISK G: TO (C:\FILE) TODISK will convert it to the corresponding 1:5 and display it together
(But it's not recommended, it can make you confused. For personalized play, it's okay)

I know it's related to my AUTOEXEC and CONFIG.SYS files! (I could use TODISK in the afternoon),

There should be no special requirements for TODISK, and I don't know if it conflicts with some drivers

I'll test it for you:
Is it XMSDSK TW MOUSP ...?

Just now, I tried XMSDSK, TW, MOUSCLIP, and there were no problems.

Now, comprehensively test all your configurations.

But, do you have such usages for your goto :eof (goto eof)?

The mark :x hasn't been used...

If there is no such file before unzip..., it can't be executed.

Last edited by GOTOmsdos on 2007-4-16 at 11:34 PM ]

Originally posted by GOTOmsdos at 2007-4-16 23:11:
Just tried XMSDSK TW MOUSCLIP and all are fine

Now, comprehensively test all your configurations,

But your goto :eof (goto eof)?

Are there such usages?

:x
This mark is not used...
...

:eof is an empty label I used. Is this usage incorrect? (Omitting it seems to continue the following actions)
:x is used to have a pause here for WBAT selection (Omitting it also seems to directly proceed to the following actions)
Can we add IF EXIST before unzip?
I will continue testing this afternoon;
Also: I am U disk boot and recognized as C: by the motherboard

:eof is an empty label I used. Is this usage incorrect? (Omitting it seems to continue the following actions)

goto :eof X
goto eof Y
Moreover, there should be something following it, otherwise an error occurs

:x is intended to have a pause here for WBAT selection (Omitting it also seems to directly proceed to the following actions)

With it, if there is nothing following, it still continues to execute

Can we add IF EXIST before unzip?

If not, the subsequent things can't be done

Another: I am using USB boot and it is recognized as C: by the motherboard

Of course, except for floppy mode (USB-FD), wherever you boot to, it is C:

************************************

Your AUTOEXEC.BAT/CONFIG.SYS, I tried. (I can't test programs I don't have...)

AUTOEXEC.BAT is as follows:
@ECHO OFF

rem tw32 /np N3 >nul
tw32 >nul
SET DIRCMD=/OGN /4
SET PROMPT=$P$G
SET HDPMI=16384
SET RAMDRIVE=x:\
XMSDSK 2048 %RAMDRIVE% /Y>NUL
PATH=C:\DOS71;%RAMDRIVE%;
COPY COMMAND.COM %RAMDRIVE%>NUL
SET COMSPEC=%RAMDRIVE%COMMAND.COM
MD %RAMDRIVE%TEMP
SET TEMP=%RAMDRIVE%TEMP
CD>%TEMP%\BOOTDRV.INI
vol>%TEMP%\VOL.TXT
cls

%RAMDRIVE%
cd\
mouse >nul
mousclip >nul
DOSKEY >nul
lh DOSLFN >nul
goto eof
:re

:END
tw32 /q
mouse /q>nul
mousclip /q>nul
DOSKEY /q>nul
DOSLFN /q >nul
cls
:eof


CONFIG.SYS is as follows
DOS=HIGH,UMB
devicehigh=c:\dos71\himem.sys /testmem:off
devicehigh=c:\dos71\emm386.exe noems
SHELL=COMMAND.COM /P /F /E:4096
lastdrive=z

$$$$$$$$$$$$$$$$$
Running TODISK above, no problem without compression, but compression fails when compressing

Loading EMM386.EXE RAM in CONFIG.SYS can compress it
Probably the ZLIB compression library has requirements for memory; roughly estimating, TODISK's total memory requirement is around 550-600, this isn't precisely tested... Maybe.

NTFSPRO can run, but compression is definitely not possible because memory is below 500!
IFS is completely没问题

Last edited by GOTOmsdos on 2007-4-17 at 01:57 AM ]

Just tried again, changed BUFFERS=30 in CONFIG.SYS to BUFFERSHIGH=10,0. Now can run TODISK. Found that the version from 04-15 13:27 can't recognize the USB flash drive when run for the first time on my machine, but others can; Thanks for GOTOmsdos's enthusiasm!