I tried it yesterday. I used the latest version of Kernel 2035a in February this year for Kernel.sys, and replaced Command.com with MS-DOS 7.10. But after making the boot disk and booting, I found some problems.
The Config.sys is as follows:
The content of Autoexec.bat is as follows:
(Note: The Himem.exe and emm386.exe used above are all versions of FreeDOS.
As a result, when entering the "cd\" command, the system prompts "Bad command or file name", but writing "cd \"(with a space in the middle) is okay. In addition, when using the cd command, if the directory does not exist, it should prompt "Invalid directory" but now it prompts "Invalid function". Pressing the up and down keys on the keyboard will automatically input the "^@" character, and pressing Ctrl+@ will become "^C" (that is, Ctrl+C). After booting the CCDOS Chinese character system, Ctrl+F10 appears the CCDOS system control prompt, which is normal, but originally Ctrl+F5 was to exit CCDOS, but now pressing it has no response?! I really don't understand that the FreeDOS kernel and MS-DOS 7.10's Command are still very incompatible!
FreeDOS's Command does not support long file names, otherwise I would not use MS-DOS...
In addition, my motherboard is Intel 845G. Using UMBPCI can only get 49k UMB. Using MS-DOS's Emm386 can only get 43k. Using FreeDOS's emm386 can get 112k? Putting FreeDOS's EMM386 into MS-DOS (IO.SYS) to use actually occupies dozens of k conventional memory! And it is not successful to load every time, sometimes it will make an error and make the system stop booting. FreeDOS's Command and UMBPCI still seem to be very incompatible. If using FreeDOS's emm386 to provide UMB, then command has 3-4k can be loaded into UMB, and if using UMBPCI, there is only dozens of bytes loaded into UMB.
It seems that there are still many bugs in FreeDOS!
[ Last edited by brglng on 2005-8-10 at 12:46 ]
The Config.sys is as follows:
!LASTDRIVE=Z
!BUFFERS=20
!FILES=30
!DOS=HIGH,UMB
!DOSDATA=UMB
!set dircmd=/ogn /4
!MENUCOLOR=7,0
MENUDEFAULT=1,5
MENU 1 - XMS Only
MENU 2 - XMS + EMM386 NOEMS
12?DEVICE=HIMEM.EXE
1?DEVICE=UMBPCI.SYS
2?DEVICE=EMM386.EXE NOEMS
12?SHELLHIGH=command.com /P
3?SHELLHIGH=command.com /D /P
The content of Autoexec.bat is as follows:
@ECHO OFF
PROMPT $P$G
LH DOSLFN /Z:CP936UNI.TBL
(Note: The Himem.exe and emm386.exe used above are all versions of FreeDOS.
As a result, when entering the "cd\" command, the system prompts "Bad command or file name", but writing "cd \"(with a space in the middle) is okay. In addition, when using the cd command, if the directory does not exist, it should prompt "Invalid directory" but now it prompts "Invalid function". Pressing the up and down keys on the keyboard will automatically input the "^@" character, and pressing Ctrl+@ will become "^C" (that is, Ctrl+C). After booting the CCDOS Chinese character system, Ctrl+F10 appears the CCDOS system control prompt, which is normal, but originally Ctrl+F5 was to exit CCDOS, but now pressing it has no response?! I really don't understand that the FreeDOS kernel and MS-DOS 7.10's Command are still very incompatible!
FreeDOS's Command does not support long file names, otherwise I would not use MS-DOS...
In addition, my motherboard is Intel 845G. Using UMBPCI can only get 49k UMB. Using MS-DOS's Emm386 can only get 43k. Using FreeDOS's emm386 can get 112k? Putting FreeDOS's EMM386 into MS-DOS (IO.SYS) to use actually occupies dozens of k conventional memory! And it is not successful to load every time, sometimes it will make an error and make the system stop booting. FreeDOS's Command and UMBPCI still seem to be very incompatible. If using FreeDOS's emm386 to provide UMB, then command has 3-4k can be loaded into UMB, and if using UMBPCI, there is only dozens of bytes loaded into UMB.
It seems that there are still many bugs in FreeDOS!
[ Last edited by brglng on 2005-8-10 at 12:46 ]
32位才是DOS未来的希望
个人网志：http://sololand.moe
个人网志：http://sololand.moe
