- Timestamp:
- Dec 2, 2008, 3:08:52 PM (17 years ago)
- Author:
- KO Myung-Hun
- Message:
-
Updated documents for a history.
- Location:
- branches/fat32-0.9/src
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
branches/fat32-0.9/src/fat32.kor
r49 r73 1796 1796 1797 1797 - /FS ¿Í /EAS °¡ ÇÔ22 »ç¿ëμÉ ¶§, MOVE ¿Í REN ží·ÉÀÌ EA ÆÄÀÏÀ» ¿Ã1Ùž£°Ô 1798 (削除) (削除ここまで)Ã3ž®ÇÏÁö ŸÊŸÒœÀŽÏŽÙ. ÇØ°á.1798 (追記) (追記ここまで)Ã3ž®ÇÏÁö ŸÊŸÒœÀŽÏŽÙ. ÇØ°á. 1799 1799 1800 1800 - /FL(±âo»)ÀÌ »ç¿ëμÉ ¶§, FillDirEntry ¿¡Œ 8.3 ÀÌž§°ú ±ä ÀÌž§ÀÌ °°Ào ÆÄÀÏÀ» 1801 (削除) (削除ここまで)°¡ž®Å2ŽÙŽÂ °ÍÀ» ŸËÁö žøÇÕŽÏŽÙ. ÇØ°á.1801 (追記) (追記ここまで)°¡ž®Å2ŽÙŽÂ °ÍÀ» ŸËÁö žøÇÕŽÏŽÙ. ÇØ°á. 1802 1802 1803 1803 - /EAS °¡ »ç¿ëμÇÁö ŸÊÀžžé, ÀÌÁŠ FAT32.IFS ŽÂ oó EA žŠ žŠ 3Ñ°ÜÁÝŽÏŽÙ. … … 1810 1810 1811 1811 - /FS °¡ »ç¿ëμÇ°í, Žë»ó ÆÄÀÏÀÌ ÀÌ1Ì ÁžÀçÇÑŽÙžé, COPY ¿Í MOVE ží·ÉÀo Žë»ó 1812 (削除) (削除ここまで)ÆÄÀÏÀÇ ÀÌž§À» ÀÌ1Ì ÁžÀçÇÏŽÂ ÆÄÀÏÀÇ ÂaÀo ÀÌž§Àž·Î 1Ù2ߎώÙ. ÇØ°á.1812 (追記) (追記ここまで)ÆÄÀÏÀÇ ÀÌž§À» ÀÌ1Ì ÁžÀçÇÏŽÂ ÆÄÀÏÀÇ ÂaÀo ÀÌž§Àž·Î 1Ù2ߎώÙ. ÇØ°á. 1813 1813 1814 1814 - FS_COPY ¿¡Œ 'Žë»óÀ» °Ë»çÇÏŽÂ oÎoÐ' ÀÇ 1ú·1žŠ ÀâŸÒœÀŽÏŽÙ. … … 1817 1817 1818 1818 - CMD.EXE ¿¡Œ CACHEF32.EXE žŠ 3¡3œ ÈÄ¿¡ 'Ÿ2±â Ä3œÃ' μ\žóÀ» ŽÙœÃ œÃÀÛÇÒ ¶§ 1819 (削除) (削除ここまで)1®ÁŠ°¡ ÀÖŸúœÀŽÏŽÙ. ÇØ°á.1819 (追記) (追記ここまで)1®ÁŠ°¡ ÀÖŸúœÀŽÏŽÙ. ÇØ°á. 1820 1820 1821 1821 - CACHEF32.EXE ¿¡ 'Yes' žŠ °¡Á€Çϱâ À§ÇÑ /Y ¿ÉŒÇÀ» Ãß°¡ÇßœÀŽÏŽÙ. … … 1828 1828 1829 1829 - 32K Å©±âÀÇ Å¬· ̄œoÅÍžŠ °¡Áø FAT32 ÆÄÆŒŒÇ¿¡ ×ばつŒŒœoÇÒ ¶§ Æ®·ŠÀÌ 1ß»ýÇÏŽÂ 1830 (削除) (削除ここまで)1®ÁŠžŠ °íÃÆœÀŽÏŽÙ.1830 (追記) (追記ここまで)1®ÁŠžŠ °íÃÆœÀŽÏŽÙ. 1831 1831 1832 1832 - ÀÌÁŠ FAT32.IFS ŽÂ 32K ožŽÙ Å« Å©±âÀÇ Å¬· ̄œoÅÍžŠ °¡Áø FAT32 ÆÄÆŒŒÇÀ» 1833 (削除) (削除ここまで)ž¶¿îÆ®ÇÏÁö ŸÊœÀŽÏŽÙ.1833 (追記) (追記ここまで)ž¶¿îÆ®ÇÏÁö ŸÊœÀŽÏŽÙ. 1834 1834 1835 1835 - DBCS [0xHH5C ] ÄÚμå¿Í [1 1ÙÀÌÆ®-īŞī3a] °¡ ¿Ã1Ùž£°Ô o ̄È ̄μÇÁö ŸÊŸÒœÀŽÏŽÙ. 1836 (削除) (削除ここまで)SBCS ¿¡ Æ÷ÇÔμÈ DBCS Ã11ø° 1ÙÀÌÆ®°¡ ¿Ã1Ùž£°Ô o ̄È ̄μÇÁö ŸÊŸÒœÀŽÏŽÙ. ÇØ°á.1837 (削除) (削除ここまで)(ÀÌÀü¿¡ 1®ŒÈμÇÁö ŸÊŸÒœÀŽÏŽÙ.)1836 (追記) (追記ここまで)SBCS ¿¡ Æ÷ÇÔμÈ DBCS Ã11ø° 1ÙÀÌÆ®°¡ ¿Ã1Ùž£°Ô o ̄È ̄μÇÁö ŸÊŸÒœÀŽÏŽÙ. ÇØ°á. 1837 (追記) (追記ここまで)(ÀÌÀü¿¡ 1®ŒÈμÇÁö ŸÊŸÒœÀŽÏŽÙ.) 1838 1838 1839 1839 0.97 ÆÇ: 1840 1840 1841 1841 - oñ-LVM œÃœoÅÛÀ» À§ÇÑ ÆÄÆŒŒÇ Áö¿ø ÆÐÅ°Áö, PARTFILT.FLT ¿Í OS2DASD.F32 žŠ 1842 (削除) (削除ここまで)FAT32.IFS μå¶óÀÌ1ö ÆÐÅ°Áö¿¡Œ »°œÀŽÏŽÙ.1842 (追記) (追記ここまで)FAT32.IFS μå¶óÀÌ1ö ÆÐÅ°Áö¿¡Œ »°œÀŽÏŽÙ. 1843 1843 1844 1844 - MONITOR.EXE žŠ F32MON.EXE ·Î 1Ù2ÙŸúœÀŽÏŽÙ. … … 1853 1853 1854 1854 - FAT32 ÀÇ ÁŸ·á oÎoп¡ 1®ÁŠ°¡ ÀÖŸúœÀŽÏŽÙ. DBCS Áö¿øÀÌ Ãß°¡μÇŸúÀ» ¶§ œÇŒö°¡ 1855 (削除) (削除ここまで)ÀÖŸúœÀŽÏŽÙ. ÇØ°á.1855 (追記) (追記ここまで)ÀÖŸúœÀŽÏŽÙ. ÇØ°á. 1856 1856 1857 1857 - FAT32 μå¶óÀÌ1ö°¡, Win2X ¿Í WinXP °°Ào WinNT °è¿ÀÇ œÃœoÅÛ¿¡Œ žžμéŸîÁø 1858 (削除) (削除ここまで)ÆÄÀÏμéÀ» È®Àå ŒÓŒoÀ» °¡Áø °ÍÀž·Î ÀÎœÄÇÒ Œö ÀÖŽÂ °¡ŽÉŒoÀÌ ÀÖŸúœÀŽÏŽÙ. ÇØ°á.1858 (追記) (追記ここまで)ÆÄÀÏμéÀ» È®Àå ŒÓŒoÀ» °¡Áø °ÍÀž·Î ÀÎœÄÇÒ Œö ÀÖŽÂ °¡ŽÉŒoÀÌ ÀÖŸúœÀŽÏŽÙ. ÇØ°á. 1859 1859 1860 1860 - WinNT °è¿°úÀÇ È£È ̄ŒoÀ» À§ÇØ EA Ç\œÃ 1ÙÀÌÆ®°¡ 1Ù2îŸúœÀŽÏŽÙ. 0xEA ŽÂ 0x40, 1861 (削除) (削除ここまで)0xEC ŽÂ 0x80 Àž·Î.1861 (追記) (追記ここまで)0xEC ŽÂ 0x80 Àž·Î. 1862 1862 1863 1863 Áß¿ä: 0.97 ÆÇoÎÅÍ, EA Ç\œÃ 1ÙÀÌÆ®°¡ 1Ù2îŸúœÀŽÏŽÙ. ×ばつ·¡Œ ÀÌÀü ÆÇ¿¡Œ È®Àå … … 1871 1871 1872 1872 - WinNT °è¿¿¡Œ »ç¿ëÇÏŽÂ FAT32 o ̄ÁŸÀ» Áö¿øÇÏμμ·Ï TranslateName() žŠ 1873 (削除) (削除ここまで)°íÃÆœÀŽÏŽÙ.1873 (追記) (追記ここまで)°íÃÆœÀŽÏŽÙ. 1874 1874 1875 1875 - Level7 À» ¿Ã1Ùž£°Ô Áö¿øÇÏμμ·Ï FS_PATHINFO žŠ °íÃÆœÀŽÏŽÙ. … … 1886 1886 1887 1887 - CACHEF32.EXE °¡ ×ばつ¶ó¿îμå·Î œÇÇàμÉ ¶§, FAT32.IFS ÀÇ CP ¿Í ÇöÀç CP °¡ ŽÙžŠ 1888 (削除) (削除ここまで)¶§, °èŒÓÇØŒ '»ß-' ŒÒž®°¡ 3aŽÂ °ÍÀ» °íÃÆœÀŽÏŽÙ.1888 (追記) (追記ここまで)¶§, °èŒÓÇØŒ '»ß-' ŒÒž®°¡ 3aŽÂ °ÍÀ» °íÃÆœÀŽÏŽÙ. 1889 1889 1890 1890 - CACHEF32.EXE ÀÇ /CP ¿ÉŒÇÀÌ ÁŠŽë·Î μ¿ÀÛÇÏÁö ŸÊŽÂ °ÍÀ» °íÃÆœÀŽÏŽÙ. 1891 1891 1892 1892 - 0.98 ÆÇ¿¡Œ ŽëŒÒ1®ÀÚ o ̄È ̄ÀÌ 128 ožŽÙ ÀÛÀo ASCII ÄÚμå¿¡ ŽëÇØŒžž ÀÌ·çŸîÁöŽÂ 1893 (削除) (削除ここまで)°ÍÀ» °íÃÆœÀŽÏŽÙ.1893 (追記) (追記ここまで)°ÍÀ» °íÃÆœÀŽÏŽÙ. 1894 1894 1895 1895 - ¶§¶§·Î, Ÿ2±â Ä3œÃ(LAZY WRITE) ±âŽÉÀÌ ÄÑÁ® ÀÖÀ» ¶§, ÆÄÀÏÀ» o1»çÇÏ°í 3aŒ FAT 1896 (削除) (削除ここまで)»ço»ÀÌ ÀÏÄ¡ÇÏÁö ŸÊ°Å3a 'ÀÒŸî1öž° Ŭ· ̄œoÅÍ' °¡ 3aÅž3aŽÂ 1®ÁŠžŠ °íÃÆœÀŽÏŽÙ.1896 (追記) (追記ここまで)»ço»ÀÌ ÀÏÄ¡ÇÏÁö ŸÊ°Å3a 'ÀÒŸî1öž° Ŭ· ̄œoÅÍ' °¡ 3aÅž3aŽÂ 1®ÁŠžŠ °íÃÆœÀŽÏŽÙ. 1897 1897 1898 1898 - ÀÌÁŠ DBCS APIs ŽëœÅ¿¡ ULS APIs žŠ »ç¿ëÇÕŽÏŽÙ. … … 1901 1901 1902 1902 - »óÀ§ žÞžðž®(high memory, > 16MB) ¿¡ Ä3œÃ žÞžðž®žŠ ÇÒŽçÇϱâ À§ÇØ /H ¿ÉŒÇÀ» 1903 (削除) (削除ここまで)FAT32.IFS ¿¡ Ãß°¡ÇßœÀŽÏŽÙ.1904 (削除) (削除ここまで)'linalloc' 1®ÁŠ°¡ ÇØ°áμÉ Œö ÀÖÀ» °ÍÀÔŽÏŽÙ.1903 (追記) (追記ここまで)FAT32.IFS ¿¡ Ãß°¡ÇßœÀŽÏŽÙ. 1904 (追記) (追記ここまで)'linalloc' 1®ÁŠ°¡ ÇØ°áμÉ Œö ÀÖÀ» °ÍÀÔŽÏŽÙ. 1905 1905 1906 1906 - FAT32 ÆÄÆŒŒÇÀÌ ŸøŽõ¶óμμ, Ÿ2±â Ä3œÃ(LAZY WRITE) μ\žóÀ» ·ÎμåÇϱâ À§ÇØ /F 1907 (削除) (削除ここまで)¿ÉŒÇÀ» CACHEF32.EXE ¿¡ Ãß°¡ÇßœÀŽÏŽÙ.1907 (追記) (追記ここまで)¿ÉŒÇÀ» CACHEF32.EXE ¿¡ Ãß°¡ÇßœÀŽÏŽÙ. 1908 1908 1909 1909 - ÀÌÁŠ FAT32.IFS ŽÂ ÀÎÀÚμéÀÇ ŽëŒÒ1®ÀÚžŠ °¡ž®Áö ŸÊœÀŽÏŽÙ. … … 1938 1938 ŒœÅÍŽÂ ÁžÀçÇÕŽÏŽÙ. ¿Ö ×ばつ·2±î¿ä ? ^^ ÇÏÁöžž, ÀÌ°ÍÀo FAT32.IFS ÀÇ ±âŽÉ¿¡ŽÂ 1939 1939 ¿μÇâÀ» 1ÌÄ¡Áö ŸÊœÀŽÏŽÙ. 1940 (追記) (追記ここまで) 1941 (追記) 0.9.12 ÆÇ : (追記ここまで) 1942 (追記) (追記ここまで) 1943 (追記) - 3a»Û »óÅÂ(DIRTY)ÀÇ oŒ·ý¿¡ ŽëÇØ CHKDSK žŠ œÇÇàœÃÅ°žé CACHEF32 °¡ ×ばつŽÂ 1®ÁŠžŠ (追記ここまで) 1944 (追記) °íÃÆœÀŽÏŽÙ. (追記ここまで) 1945 (追記) (追記ここまで) 1946 (追記) - 0.9.11 oÎÅÍ USB ÀÌμ¿ ÀåÄ¡žŠ ¿¬°áÇßÀ» ¶§, USB ÀÌμ¿ ÀåÄ¡žŠ ÀÎœÄÇÏŽÂμ\ ¿À·£ (追記ここまで) 1947 (追記) œÃ°£ÀÌ °Éž®ŽÂ 1®ÁŠžŠ °íÃÆœÀŽÏŽÙ. (追記ここまで) 1948 (追記) (追記ここまで) 1949 (追記) - USB ÀÌμ¿ ÀåÄ¡žŠ 'eject' žŠ ŒöÇàÇÏÁö ŸÊ°í ÁŠ°ÅÇÏžé Æ®·ŠÀÌ 1ß»ýÇÏŽÂ 1®ÁŠžŠ (追記ここまで) 1950 (追記) °íÃÆœÀŽÏŽÙ. (追記ここまで) 1951 (追記) (追記ここまで) 1952 (追記) - Àбâ/Ÿ2±â ŒoŽÉÀ» °3Œ±ÇßœÀŽÏŽÙ.( Lars ŸŸ ) (追記ここまで) 1953 (追記) (追記ここまで) 1954 (追記) *** ŸË·ÁÁø 1®ÁŠμé *** (追記ここまで) 1955 (追記) (追記ここまで) 1956 (追記) - À©μμ°°Ào OS ¿¡Œ USB ÀÌμ¿ ÀåÄ¡žŠ »ç¿ëÇÒ ¶§, 'Free Space' °¡ oÎÁ€È®ÇÒ Œö (追記ここまで) 1957 (追記) ÀÖœÀŽÏŽÙ. ÀÌ ¶§¿¡ŽÂ, CHKDSK žŠ ŒöÇàÇØŒ ÀÌ 1®ÁŠžŠ 1Ù·ÎÀâ°Å3a, '/CALCFREE' (追記ここまで) 1958 (追記) ×ばつÀ» ÅëÇØŒ ÀÌ 1®ÁŠžŠ ÇÇÇÒ Œö ÀÖœÀŽÏŽÙ. (追記ここまで) 1940 1959 1941 1960 ============= -
branches/fat32-0.9/src/fat32.txt
r50 r73 1 1 2 (削除) (削除ここまで)=> For the latest changes in FAT32.IFS please look <=3 (削除) => at the bottom of this file. (削除ここまで)<=4 5 6 7 (削除) (削除ここまで)=== DISCLAIMER ===2 (追記) (追記ここまで) => For the latest changes in FAT32.IFS please look <= 3 (追記) => at the bottom of this file. (追記ここまで) <= 4 5 6 7 (追記) (追記ここまで)=== DISCLAIMER === 8 8 9 9 … … 11 11 that I am in no way responsible for any damage or loss you may suffer. 12 12 13 (削除) (削除ここまで)>> You should be aware of the fact that FAT32.IFS might <<14 (削除) >> damage the data stored on your hard disks. (削除ここまで)<<13 (追記) (追記ここまで)>> You should be aware of the fact that FAT32.IFS might << 14 (追記) >> damage the data stored on your hard disks. (追記ここまで)<< 15 15 16 16 If you cannot agree to these conditions, you should NOT use FAT32.IFS ! … … 23 23 24 24 Henk Kelder 25 hkelder@capgemini.nl (削除) (削除ここまで)25 hkelder@capgemini.nl(追記) (追記ここまで) 26 26 Certified daddy (by my kids) 27 27 28 My homepage for the latest version: (削除) (削除ここまで)28 My homepage for the latest version:(追記) (追記ここまで) 29 29 30 30 http://www.os2ss.com/information/kelder/index.html … … 34 34 ===================== 35 35 36 FAT32.TXT (削除) (削除ここまで)This file.37 PARTFILT.TXT (削除) (削除ここまで)A textfile about PARTFILT.FLT and DISKINFO.EXE38 39 FAT32.IFS (削除) (削除ここまで)The actual IFS.40 CACHEF32.EXE (削除) (削除ここまで)The cache helper program.41 UFAT32.DLL (削除) (削除ここまで)The module needed to run CHKDSK on FAT32 partition.42 F32STAT.EXE (削除) A program to change the DIRTY flag of FAT32 (削除ここまで)36 FAT32.TXT(追記) (追記ここまで)This file. 37 PARTFILT.TXT(追記) (追記ここまで)A textfile about PARTFILT.FLT and DISKINFO.EXE 38 39 FAT32.IFS(追記) (追記ここまで)The actual IFS. 40 CACHEF32.EXE(追記) (追記ここまで)The cache helper program. 41 UFAT32.DLL(追記) (追記ここまで)The module needed to run CHKDSK on FAT32 partition. 42 F32STAT.EXE (追記) A program to change the DIRTY flag of FAT32 (追記ここまで) 43 43 partitions. 44 MONITOR.EXE (削除) (削除ここまで)A program to monitor what FAT32.IFS is doing.45 46 PARTFILT.FLT (削除) (削除ここまで)A general partition filter device that allows FAT3247 partitions to be recognized by OS/2. 48 49 OS2DASD.F32 (削除) (削除ここまで)A modified version of OS2DASD.DMD that is an50 (削除) (削除ここまで)alternative for using PARTFILT.FLT. This modified51 driver also allows FAT32 partitions to be recognized 52 (削除) (削除ここまで)by OS/2. If you want to try this please rename it to53 (削除) (削除ここまで)OS2DASD.DMD and place it in your OS2\BOOT directory.54 (削除) (削除ここまで)Remember to make a backup copy of the orginal!55 56 PLEASE NOTE: that this driver is NOT at the latest 57 level and will probably NOT support the latest 58 (削除) (削除ここまで)features like removable disks etc.59 60 DISKINFO.EXE (削除) (削除ここまで)A diagnose program that will scan for and show61 all partitions. 44 MONITOR.EXE (追記) (追記ここまで)A program to monitor what FAT32.IFS is doing. 45 46 PARTFILT.FLT(追記) (追記ここまで)A general partition filter device that allows FAT32 47 partitions to be recognized by OS/2. 48 49 OS2DASD.F32 (追記) (追記ここまで)A modified version of OS2DASD.DMD that is an 50 (追記) (追記ここまで)alternative for using PARTFILT.FLT. This modified 51 driver also allows FAT32 partitions to be recognized 52 (追記) (追記ここまで)by OS/2. If you want to try this please rename it to 53 (追記) (追記ここまで)OS2DASD.DMD and place it in your OS2\BOOT directory. 54 (追記) (追記ここまで)Remember to make a backup copy of the orginal! 55 56 PLEASE NOTE: that this driver is NOT at the latest 57 level and will probably NOT support the latest 58 (追記) (追記ここまで)features like removable disks etc. 59 60 DISKINFO.EXE(追記) (追記ここまで)A diagnose program that will scan for and show 61 all partitions. 62 62 63 63 LIMITATIONS … … 69 69 - You cannot BOOT from a FAT32 partition. 70 70 - You cannot place the SWAPPER.DAT on a FAT32 partition. 71 - CHKDSK can diagnose a disk, but will only FIX lost clusters and an (削除) (削除ここまで)72 incorrect free space count. For all other errors, you'll need to run (削除) (削除ここまで)71 - CHKDSK can diagnose a disk, but will only FIX lost clusters and an(追記) (追記ここまで) 72 incorrect free space count. For all other errors, you'll need to run(追記) (追記ここまで) 73 73 Windows95 and start scandisk to fix the problem. 74 74 Note: CHKDSK will always convert lost clusters to files and NEVER to 75 75 directories. if you want that, use SCANDISK. 76 76 - The FORMAT, RECOVER and SYS commands are not supported. 77 - Only last access date (and not last access time) is maintained by (削除) (削除ここまで)77 - Only last access date (and not last access time) is maintained by(追記) (追記ここまで) 78 78 FAT32.IFS. This is similiar to Win95 (OSR2). 79 79 80 - Long filenames are not by default supported in DOS and Win-OS/2 sessions, (削除) (削除ここまで)81 they use only the shortnames. (削除) (削除ここまで)80 - Long filenames are not by default supported in DOS and Win-OS/2 sessions,(追記) (追記ここまで) 81 they use only the shortnames.(追記) (追記ここまで) 82 82 Please see 'LONG FILENAMES IN OS/2 AND DOS SESSIONS' later is this file. 83 83 … … 88 88 maintenance tools will show non-existing drives and other nonsense. 89 89 90 - This version needs the native NLS support from OS/2. (削除) (削除ここまで)90 - This version needs the native NLS support from OS/2.(追記) (追記ここまで) 91 91 This means Warp 3 fixpack 26 or higher or Warp 4. 92 92 (You must have the LANGUAGE directory) … … 101 101 FAT32.IFS 102 102 CACHEF32.EXE 103 F32STAT.EXE (削除) (削除ここまで)103 F32STAT.EXE(追記) (追記ここまで) 104 104 MONITOR.EXE 105 105 … … 109 109 (Skip the next lines if you are using Warp Server for eBusiness) 110 110 Copy the following file to your \OS2\BOOT directory: 111 PARTFILT.FLT (削除) (削除ここまで)111 PARTFILT.FLT(追記) (追記ここまで) 112 112 113 113 =>Do NOT REPLACE your current OS2DASD.DMD with the version in the archive,<= 114 =>before you have read the remarks below about OS/2 and FAT32 and know you<= (削除) (削除ここまで)115 =>MUST use this DMD. You probably do NOT NEED IT! (削除) (削除ここまで)<=114 =>before you have read the remarks below about OS/2 and FAT32 and know you<=(追記) (追記ここまで) 115 =>MUST use this DMD. You probably do NOT NEED IT!(追記) (追記ここまで) <= 116 116 117 117 Make the following changes to the CONFIG.SYS: 118 118 119 IFS=x:\OS2\FAT32.IFS [options, see below] (削除) (削除ここまで)119 IFS=x:\OS2\FAT32.IFS [options, see below](追記) (追記ここまで) 120 120 (Install this one AFTER IFS=HPFS.IFS) 121 121 … … 124 124 125 125 (Skip the next lines if you are using Warp Server for eBusiness) 126 BASEDEV=PARTFILT.FLT /P 0B [/W] (削除) (削除ここまで)126 BASEDEV=PARTFILT.FLT /P 0B [/W](追記) (追記ここまで) 127 127 (The /W should not be specified if you do not want write access) 128 128 (The best location seems to differ depening on your configuration. Some 129 state FAT32.IFS will only work is PARTFILT is the first basedev, other (削除) (削除ここまで)129 state FAT32.IFS will only work is PARTFILT is the first basedev, other(追記) (追記ここまで) 130 130 claim it only works if PARTFILT is the last one.) 131 131 … … 142 142 The following options are supported: 143 143 144 /Q (削除) (削除ここまで)Quiet, not messages.144 /Q(追記) (追記ここまで) Quiet, not messages. 145 145 146 146 /CACHE:nnnn specifies the cache size in kilobytes. If omitted the default 147 (削除) (削除ここまで)cache size is 1024KB. Maximum cache size is 2048KB.148 (削除) (削除ここまで)*NOTE*149 (削除) (削除ここまで)Cache memory is allocated as FIXED memory, so if you have less150 (削除) (削除ここまで)than 16MB I suggest you set this option to 512KB or less.151 152 /MONITOR (削除) Set monitor ON by default. If omitted monitor is OFF. See (削除ここまで)153 (削除) (削除ここまで)MONITOR.EXE for more information.147 (追記) (追記ここまで) cache size is 1024KB. Maximum cache size is 2048KB. 148 (追記) (追記ここまで) *NOTE* 149 (追記) (追記ここまで) Cache memory is allocated as FIXED memory, so if you have less 150 (追記) (追記ここまで) than 16MB I suggest you set this option to 512KB or less. 151 152 /MONITOR(追記) Set monitor ON by default. If omitted monitor is OFF. See (追記ここまで) 153 (追記) (追記ここまで) MONITOR.EXE for more information. 154 154 155 155 /RASECTORS:n Read Ahead Sectors. 156 (削除) (削除ここまで)Specifies the minimum number of sectors to be read per read157 (削除) (削除ここまで)action and placed in the cache.158 If omitted the default differs per volume and equals the 159 number of sectors per cluster times 2. 160 (削除) (削除ここまで)The maximum treshold value used is 128.161 162 (削除) (削除ここまで)You should note that the actual sector IO per read action is163 (削除) (削除ここまで)NOT determined by an application, but by the IFS. For FAT access164 (削除) (削除ここまで)single sector reads are done. For Directory and Files IO reads165 are done on a cluster base. By setting the RASECTORS you can 166 (削除) (削除ここまで)define the minimum number of sectors the IFS will read from disk167 (削除) (削除ここまで)and place in the cache.168 169 /EAS (削除) (削除ここまで)Make FAT32.IFS support EXTENDED ATTRIBUTES.170 171 /H (削除) (削除ここまで)Use high-memory( > 16MB ) to allocate cache buffer.156 (追記) (追記ここまで) Specifies the minimum number of sectors to be read per read 157 (追記) (追記ここまで) action and placed in the cache. 158 If omitted the default differs per volume and equals the 159 number of sectors per cluster times 2. 160 (追記) (追記ここまで) The maximum treshold value used is 128. 161 162 (追記) (追記ここまで) You should note that the actual sector IO per read action is 163 (追記) (追記ここまで) NOT determined by an application, but by the IFS. For FAT access 164 (追記) (追記ここまで) single sector reads are done. For Directory and Files IO reads 165 are done on a cluster base. By setting the RASECTORS you can 166 (追記) (追記ここまで) define the minimum number of sectors the IFS will read from disk 167 (追記) (追記ここまで) and place in the cache. 168 169 /EAS(追記) (追記ここまで) Make FAT32.IFS support EXTENDED ATTRIBUTES. 170 171 /H(追記) (追記ここまで) Use high-memory( > 16MB ) to allocate cache buffer. 172 172 173 173 CACHEF32.EXE … … 179 179 - Set CACHE and READ-AHEAD parameters. 180 180 - Set Longname behaviour. 181 - Load a CP to UNICODE translate table for longnames and the default (削除) (削除ここまで)181 - Load a CP to UNICODE translate table for longnames and the default(追記) (追記ここまで) 182 182 codepage. 183 183 … … 190 190 CACHEF32.EXE supports the following options: 191 191 192 /? (削除) (削除ここまで)Shows help.193 194 /Q (削除) (削除ここまで)Terminates CACHEF32. CacheF32 will be unloaded from memory, lazy195 (削除) (削除ここまで)writing will stop. (Performance will degrade).196 197 /N (削除) (削除ここまで)Runs CACHEF32 without starting the deamon in the background, ans also198 (削除) (削除ここまで)clear fForceLoad flag.192 /?(追記) (追記ここまで) Shows help. 193 194 /Q(追記) (追記ここまで) Terminates CACHEF32. CacheF32 will be unloaded from memory, lazy 195 (追記) (追記ここまで) writing will stop. (Performance will degrade). 196 197 /N(追記) (追記ここまで) Runs CACHEF32 without starting the deamon in the background, ans also 198 (追記) (追記ここまで) clear fForceLoad flag. 199 199 200 200 /D:nn Sets the DISKIDLE value. See OS/2 online help on CACHE. … … 208 208 /L:ON|OFF Set lazy writing ON or OFF, default is ON 209 209 210 /P:1|2|3|4 Set priority for lazy writer. 1 is lowest, 4 is highest. (削除) (削除ここまで)211 Default 1 (= idle-time). This might be handy if the lazy-writter 212 (削除) (削除ここまで)doesn't seem to get any CPU due to heavy system load.213 214 /Y (削除) (削除ここまで)Assume yes215 216 /S (削除) (削除ここまで)Do NOT display normal messages217 218 /F (削除) (削除ここまで)Force lazy write deamon to be loaded.210 /P:1|2|3|4 Set priority for lazy writer. 1 is lowest, 4 is highest.(追記) (追記ここまで) 211 Default 1 (= idle-time). This might be handy if the lazy-writter 212 (追記) (追記ここまで) doesn't seem to get any CPU due to heavy system load. 213 214 /Y(追記) (追記ここまで) Assume yes 215 216 /S(追記) (追記ここまで) Do NOT display normal messages 217 218 /F(追記) (追記ここまで) Force lazy write deamon to be loaded. 219 219 220 220 Note 1: the /T option has been removed in version 0.83. 221 221 222 Note 2: if you notice that the /P options has any effect on your (削除) (削除ここまで)223 (削除) (削除ここまで)situation please let me know.222 Note 2: if you notice that the /P options has any effect on your(追記) (追記ここまで) 223 (追記) (追記ここまで)situation please let me know. 224 224 225 225 Note 3: Both /FS and /FL option has been removed in version 0.98. … … 232 232 233 233 For CHKDSK the following options are implemented: 234 /F (削除) (削除ここまで)Fixes problems (Currently UFAT32.DLL only fixes lost clusters,235 (削除) (削除ここまで)and an incorrect free space count.)236 /C (削除) (削除ここまで)Causes lost clusters to be automatically converted to files if the237 (削除) (削除ここまで)drive was in an inconsistent state at boot (No questions asked).234 /F(追記) (追記ここまで) Fixes problems (Currently UFAT32.DLL only fixes lost clusters, 235 (追記) (追記ここまで) and an incorrect free space count.) 236 /C(追記) (追記ここまで) Causes lost clusters to be automatically converted to files if the 237 (追記) (追記ここまで) drive was in an inconsistent state at boot (No questions asked). 238 238 /V:1 Causes CHKDSK to show fragmented files. 239 239 /V[:2] Causes CHKDSK to show details on all files checked.(default) … … 252 252 =========== 253 253 254 F32STAT can be used to query the clean shutdown state of a FAT32 drive. (削除) (削除ここまで)254 F32STAT can be used to query the clean shutdown state of a FAT32 drive.(追記) (追記ここまで) 255 255 It also allows you to alter the clean shutdown state. You could use this 256 256 feature if FAT32.IFS blocks access to the disk because it is dirty on boot, … … 263 263 The following options exist: 264 264 265 /CLEAN (削除) - Inform FAT32.IFS that the disk was clean on boot and may be used. (削除ここまで)266 The disk itself will be marked as clean on a succesfull shutdown. 267 (削除) (削除ここまで)(The internal dirty flag FAT32.IFS uses will be cleared.)265 /CLEAN(追記) - Inform FAT32.IFS that the disk was clean on boot and may be used. (追記ここまで) 266 The disk itself will be marked as clean on a succesfull shutdown. 267 (追記) (追記ここまで) (The internal dirty flag FAT32.IFS uses will be cleared.) 268 268 269 269 /FCLEAN - Inform FAT32.IFS that the disk was clean on boot and may be used. 270 The disk itself will also be marked as clean at that moment. 271 (削除) (削除ここまで)(The internal dirty flag FAT32.IFS uses will be cleared, but the272 (削除) (削除ここまで)marking on disk will also be set ok.)273 274 /DIRTY (削除) (削除ここまで)- Inform FAT32.IFS to set its internal dirty flag, and mark the drive275 (削除) (削除ここまで)dirty on disk. On shutdown the drive will be left dirty, so when276 (削除) (削除ここまで)booting Windows 95 (OSR2) SCANDISK will be fired.270 The disk itself will also be marked as clean at that moment. 271 (追記) (追記ここまで) (The internal dirty flag FAT32.IFS uses will be cleared, but the 272 (追記) (追記ここまで) marking on disk will also be set ok.) 273 274 /DIRTY(追記) (追記ここまで)- Inform FAT32.IFS to set its internal dirty flag, and mark the drive 275 (追記) (追記ここまで) dirty on disk. On shutdown the drive will be left dirty, so when 276 (追記) (追記ここまで) booting Windows 95 (OSR2) SCANDISK will be fired. 277 277 278 278 … … 282 282 Monitor will show (most) FAT32 actions on screen. This program is intended 283 283 for troubleshooting. Using F32MON will degrade performance since FAT32 must 284 send monitoring information to an internal buffer. This internal buffer is (削除) (削除ここまで)284 send monitoring information to an internal buffer. This internal buffer is(追記) (追記ここまで) 285 285 only 4096 bytes large, so if monitoring is on, but F32MON does not run, 286 286 logging information is lost. This will however only occur if /MONITOR is … … 288 288 289 289 If the /MONITOR command is not specified in the config.sys after the IFS= 290 statement monitoring is OFF by default, but starting MONITOR once will (削除) (削除ここまで)290 statement monitoring is OFF by default, but starting MONITOR once will(追記) (追記ここまで) 291 291 activate monitoring. 292 292 … … 300 300 F32MON [tracemask] [/S] 301 301 302 If tracemask is omitted it is set to 1. (削除) (削除ここまで)302 If tracemask is omitted it is set to 1.(追記) (追記ここまで) 303 303 304 304 The tracemask exists of a specific bit to show certain types of information. … … 318 318 319 319 e.g. 320 You want to see both FS_xxxx calls and cache related information. As (削除) (削除ここまで)320 You want to see both FS_xxxx calls and cache related information. As(追記) (追記ここまで) 321 321 tracemask you should use 1 + 4 = 5. 322 322 323 323 324 /S (削除) (削除ここまで)- Runs without output to the screen, but only to FAT32.LOG. This is325 (削除) (削除ここまで)usefull if F32MON sends so much messages to the screen that the326 (削除) (削除ここまで)program can't keep up with the IFS. Using /S only sends the output327 (削除) (削除ここまで)to FAT32.LOG so no time is lost in screen handling.324 /S(追記) (追記ここまで) - Runs without output to the screen, but only to FAT32.LOG. This is 325 (追記) (追記ここまで) usefull if F32MON sends so much messages to the screen that the 326 (追記) (追記ここまで) program can't keep up with the IFS. Using /S only sends the output 327 (追記) (追記ここまで) to FAT32.LOG so no time is lost in screen handling. 328 328 329 329 … … 335 335 MAKING OS/2 RECOGNIZE FAT32 PARTITIONS. 336 336 --------------------------------------- 337 OS/2 by itself does not recognize FAT32 partitions. This means that (削除) (削除ここまで)337 OS/2 by itself does not recognize FAT32 partitions. This means that(追記) (追記ここまで) 338 338 installing the IFS is useless if we can't make OS/2 recognize them. 339 339 … … 343 343 344 344 If you are using Warp Server for e-Business (AURORA) you must use the LVM to 345 create a Compatible volume. Do not try to use PARTFILT or the modified (削除) (削除ここまで)345 create a Compatible volume. Do not try to use PARTFILT or the modified(追記) (追記ここまで) 346 346 OS2DASD.DMD with this version of OS/2. 347 347 … … 350 350 ----------- 351 351 352 The version of OS2DASD.DMD (called OS2DASD.F32) supplied in this package is (削除) (削除ここまで)353 a modified version of this driver and is NOT at the latest level. (削除) (削除ここまで)354 This means that it is possible that some of the latest features in the (削除) (削除ここまで)355 IBM supplied driver may not be supported. Also, when installing new (削除) (削除ここまで)356 fixpacks, you should make sure that this version of OS2DASD.DMD is (削除) (削除ここまで)352 The version of OS2DASD.DMD (called OS2DASD.F32) supplied in this package is(追記) (追記ここまで) 353 a modified version of this driver and is NOT at the latest level.(追記) (追記ここまで) 354 This means that it is possible that some of the latest features in the(追記) (追記ここまで) 355 IBM supplied driver may not be supported. Also, when installing new(追記) (追記ここまで) 356 fixpacks, you should make sure that this version of OS2DASD.DMD is(追記) (追記ここまで) 357 357 not replaced. 358 358 … … 362 362 363 363 This version of OS2DASD.DMD has extra support for partition type 11 (hex B). 364 Partition type 12 (hex C), FAT32 through INT13 is NOT supported by this (削除) (削除ここまで)364 Partition type 12 (hex C), FAT32 through INT13 is NOT supported by this(追記) (追記ここまで) 365 365 driver. 366 366 367 Generally, it is not advised to use this version of OS2DASD.DMD, but to (削除) (削除ここまで)367 Generally, it is not advised to use this version of OS2DASD.DMD, but to(追記) (追記ここまで) 368 368 use the PARTFILT.FLT. 369 369 … … 383 383 By default Windows long file names (VFAT) are stored in UNICODE. 384 384 385 Since Warp 3 (fixpack 26?) OS/2 contains NLS support. (削除) (削除ここまで)386 CACHEF32.EXE now calls this NLS support to create a CP to UNICODE translate (削除) (削除ここまで)385 Since Warp 3 (fixpack 26?) OS/2 contains NLS support.(追記) (追記ここまで) 386 CACHEF32.EXE now calls this NLS support to create a CP to UNICODE translate(追記) (追記ここまで) 387 387 table during startup of your system. 388 388 389 389 Keep in mind that a table for only ONE codepage is loaded. Should you change 390 390 codepages (using CHCP) you must rerun CACHEF32 to load a new table, but keep 391 in mind OS/2 keeps different codepages per session so if you use CHCP to (削除) (削除ここまで)391 in mind OS/2 keeps different codepages per session so if you use CHCP to(追記) (追記ここまで) 392 392 change the CP that CP is only only valid for that session. 393 393 … … 399 399 and if the disk is not shutdown properly, SCANDISK is run. 400 400 401 FAT32.IFS also supports this feature. When CACHEF32 is called from the (削除) (削除ここまで)401 FAT32.IFS also supports this feature. When CACHEF32 is called from the(追記) (追記ここまで) 402 402 config.sys, it checks, via a call to the IFS the state of each FAT32 drive. 403 For each drive that is not shutdown properly, CHKDSK is fired. If no errors (削除) (削除ここまで)404 are found, or if only lost clusters where found and repaired, the drive is (削除) (削除ここまで)405 marked ok. (削除) (削除ここまで)403 For each drive that is not shutdown properly, CHKDSK is fired. If no errors(追記) (追記ここまで) 404 are found, or if only lost clusters where found and repaired, the drive is(追記) (追記ここまで) 405 marked ok.(追記) (追記ここまで) 406 406 407 407 If CHKDSK cannot solve the problem, the drive state is left dirty, and 408 NO FILES CAN BE OPENED AND NO DIRECTORIES CAN BE ADDED OR REMOVED. (削除) (削除ここまで)408 NO FILES CAN BE OPENED AND NO DIRECTORIES CAN BE ADDED OR REMOVED.(追記) (追記ここまで) 409 409 Shutting down the disk, leaves the disk marked as not properly shutdown. 410 You should boot Windows 95 and run SCANDISK on the drive to fix the (削除) (削除ここまで)410 You should boot Windows 95 and run SCANDISK on the drive to fix the(追記) (追記ここまで) 411 411 remaining problems. 412 412 … … 423 423 - The free space is not available on the disk. 424 424 425 FAT32.IFS will internally keep track of the free space and update it on disk (削除) (削除ここまで)425 FAT32.IFS will internally keep track of the free space and update it on disk(追記) (追記ここまで) 426 426 on shutdown. 427 427 … … 430 430 ----------- 431 431 432 All of the code is in plain 16 bits C (All of OS/2's IFS's are 16 bits!). (削除) (削除ここまで)432 All of the code is in plain 16 bits C (All of OS/2's IFS's are 16 bits!).(追記) (追記ここまで) 433 433 No assembly language code is used. 434 434 435 The MONITOR function takes a lot of time. Be sure to switch if off if you (削除) (削除ここまで)435 The MONITOR function takes a lot of time. Be sure to switch if off if you(追記) (追記ここまで) 436 436 don't need it. 437 437 438 You should probably experiment with the CACHEF32 options to get the best (削除) (削除ここまで)439 performance for your situation. (削除) (削除ここまで)440 441 The default for the LAZY WRITER is idle-time priority (/P:1). (削除) (削除ここまで)438 You should probably experiment with the CACHEF32 options to get the best(追記) (追記ここまで) 439 performance for your situation.(追記) (追記ここまで) 440 441 The default for the LAZY WRITER is idle-time priority (/P:1).(追記) (追記ここまで) 442 442 You'd might like to experiment with the /P option as well, especially if you 443 443 have performance problems with FAT32.IFS. 444 444 445 For best performance it is advised to keep the disk as defragmented as (削除) (削除ここまで)445 For best performance it is advised to keep the disk as defragmented as(追記) (追記ここまで) 446 446 possible. Use Windows 95 defrag to defrag the disk. 447 447 … … 460 460 even if the name conforms to 8.3. The case will be preserved. 461 461 462 Last access dates are maintained by FAT32.IFS. (削除) (削除ここまで)462 Last access dates are maintained by FAT32.IFS.(追記) (追記ここまで) 463 463 (but not the last access time since Win95 doesn't support it) 464 464 You can see these when using the detailed view of the drive object. … … 478 478 Extended Attributes are implemented in the following manner: 479 479 480 For each file or directory that has extended attributes a file is created (削除) (削除ここまで)481 with a name that consists of the file or directory name the EAs belongs to (削除) (削除ここまで)482 followed by ' EA. SF'. So if a file called 'FILE' has extended attributes (削除) (削除ここまで)483 these attributes are stored in a file called 'FILE EA. SF'. (削除) (削除ここまで)480 For each file or directory that has extended attributes a file is created(追記) (追記ここまで) 481 with a name that consists of the file or directory name the EAs belongs to(追記) (追記ここまで) 482 followed by ' EA. SF'. So if a file called 'FILE' has extended attributes(追記) (追記ここまで) 483 these attributes are stored in a file called 'FILE EA. SF'.(追記) (追記ここまで) 484 484 These EA files are given the hidden, read-only and system attributes. 485 485 486 FAT32.IFS will not show these files in a directory listing, but Windows 95 (削除) (削除ここまで)486 FAT32.IFS will not show these files in a directory listing, but Windows 95(追記) (追記ここまで) 487 487 can show them. 488 488 … … 490 490 ------------- 491 491 492 Also, to speed things up a bit, each file having extended attributes is (削除) (削除ここまで)493 marked by FAT32.IFS. For this mark an appearant unused byte in the directory (削除) (削除ここまで)492 Also, to speed things up a bit, each file having extended attributes is(追記) (追記ここまで) 493 marked by FAT32.IFS. For this mark an appearant unused byte in the directory(追記) (追記ここまで) 494 494 entry is used. The value for this byte is set to 0x40 for files having 495 495 normal EAs, to 0x80 for files having critical EAs, and to 0x00 for files … … 500 500 501 501 This byte (directly following the files attribute) is not modified while 502 running Windows 95 and neighter by SCANDISK or DEFRAG, but theoretically, (削除) (削除ここまで)502 running Windows 95 and neighter by SCANDISK or DEFRAG, but theoretically,(追記) (追記ここまで) 503 503 other programs running under Windows 95 could modify it. 504 504 505 505 If another program sets the value to 0x00 for a file that has EAs these EAs 506 will no longer be found using DosFindFirst/Next calls only. The other OS2 (削除) (削除ここまで)507 calls for retrieving EAs (DosQueryPathInfo, DosQueryFileInfo and (削除) (削除ここまで)506 will no longer be found using DosFindFirst/Next calls only. The other OS2(追記) (追記ここまで) 507 calls for retrieving EAs (DosQueryPathInfo, DosQueryFileInfo and(追記) (追記ここまで) 508 508 DosEnumAttribute) do not rely on this byte. 509 509 510 Also the opposite could, again theoretically, occur. Files not having EAs (削除) (削除ここまで)510 Also the opposite could, again theoretically, occur. Files not having EAs(追記) (追記ここまで) 511 511 could be marked as having EAS. In this situation only the performance of 512 512 directory scans will be decreased. … … 515 515 516 516 517 The drawbacks (削除) (削除ここまで)517 The drawbacks(追記) (追記ここまで) 518 518 ------------- 519 519 520 Currently, the drawback of using Extended Attributes is that directory (削除) (削除ここまで)521 scan performance has slightly decreased. (削除) (削除ここまで)520 Currently, the drawback of using Extended Attributes is that directory(追記) (追記ここまで) 521 scan performance has slightly decreased.(追記) (追記ここまで) 522 522 523 523 The overhead on opening or accessing individual files is hardly noticable. … … 536 536 537 537 538 If you can live with the small loss in performance while doing directory (削除) (削除ここまで)538 If you can live with the small loss in performance while doing directory(追記) (追記ここまで) 539 539 scans it is advised you specify /EAS after the IFS line in the CONFIG.SYS. 540 540 541 541 If you do not really need extended attribute support and you cannot accept 542 the decrease in directory scan performance then simply do not specify /EAS (削除) (削除ここまで)542 the decrease in directory scan performance then simply do not specify /EAS(追記) (追記ここまで) 543 543 after the IFS line in the config.sys. 544 544 … … 558 558 If not, tell me. 559 559 - If you are not sure, try the /MONITOR parameter after FAT32.IFS, 560 and after reboot look with monitor for FS_MOUNT calls. Send me (削除) (削除ここまで)560 and after reboot look with monitor for FS_MOUNT calls. Send me(追記) (追記ここまで) 561 561 the results. 562 562 - If a new drive letter is assigned, but FAT32.IFS fails, … … 564 564 - If you have a TRAP, please send me the CS:IP value of the trap. 565 565 566 If you have a program that doesn't work or returns errors, please run (削除) (削除ここまで)567 monitor.exe while you execute the program. After the error has occured, (削除) (削除ここまで)568 terminate monitor and send me a message describing what the problem is, as (削除) (削除ここまで)566 If you have a program that doesn't work or returns errors, please run(追記) (追記ここまで) 567 monitor.exe while you execute the program. After the error has occured,(追記) (追記ここまで) 568 terminate monitor and send me a message describing what the problem is, as(追記) (追記ここまで) 569 569 detailed as possible and include the FAT32.LOG that was created by monitor. 570 570 … … 572 572 SUPPORTED IFS FUNCTIONS 573 573 ======================= 574 FS_ALLOCATEPAGESPACE (削除) (削除ここまで): No575 FS_ATTACH (削除) (削除ここまで): No576 FS_CANCELLOCKREQUEST (削除) (削除ここまで): No, function is implemented in the KERNEL577 FS_CHDIR (削除) (削除ここまで): Yes578 FS_CHGFILEPTR (削除) (削除ここまで): Yes579 FS_CLOSE (削除) (削除ここまで): Yes580 FS_COMMIT (削除) (削除ここまで): Yes581 FS_COPY (削除) : Partly, unsupported actions are simulated by (削除ここまで)574 FS_ALLOCATEPAGESPACE(追記) (追記ここまで): No 575 FS_ATTACH(追記) (追記ここまで): No 576 FS_CANCELLOCKREQUEST(追記) (追記ここまで): No, function is implemented in the KERNEL 577 FS_CHDIR(追記) (追記ここまで): Yes 578 FS_CHGFILEPTR(追記) (追記ここまで): Yes 579 FS_CLOSE(追記) (追記ここまで): Yes 580 FS_COMMIT(追記) (追記ここまで): Yes 581 FS_COPY (追記) : Partly, unsupported actions are simulated by (追記ここまで) 582 582 command shell 583 FS_DELETE (削除) (削除ここまで): Yes584 FS_DOPAGEIO (削除) (削除ここまで): No585 FS_EXIT (削除) (削除ここまで): Yes586 FS_FILEATTRIBUTE (削除) (削除ここまで): Yes587 FS_FILEINFO (削除) (削除ここまで): Yes588 FS_FILEIO (削除) (削除ここまで): No589 FS_FILELOCKS (削除) (削除ここまで): No, function is implemented in the KERNEL590 FS_FINDCLOSE (削除) (削除ここまで): Yes591 FS_FINDFIRST (削除) (削除ここまで): Yes592 FS_FINDFROMNAME (削除) (削除ここまで): Yes593 FS_FINDNEXT (削除) (削除ここまで): Yes594 FS_FINDNOTIFYCLOSE (削除) (削除ここまで): Obsolete in OS/2 WARP595 FS_FINDNOTIFYFIRST (削除) (削除ここまで): Obsolete in OS/2 WARP596 FS_FINDNOTIFYNEXT (削除) (削除ここまで): Obsolete in OS/2 WARP597 FS_FLUSHBUF (削除) (削除ここまで): Yes598 FS_FSCTL (削除) (削除ここまで): Yes599 FS_FSINFO (削除) (削除ここまで): Yes600 FS_INIT (削除) (削除ここまで): Yes601 FS_IOCTL (削除) (削除ここまで): Yes - LOCK & UNLOCK, others are passed to OS2DASD.602 FS_MKDIR (削除) (削除ここまで): Yes603 FS_MOUNT (削除) (削除ここまで): Yes604 FS_MOVE (削除) (削除ここまで): Yes605 FS_NEWSIZE (削除) (削除ここまで): Yes606 FS_NMPIPE (削除) (削除ここまで): No607 FS_OPENCREATE (削除) (削除ここまで): Yes608 FS_OPENPAGEFILE (削除) (削除ここまで): No609 FS_PATHINFO (削除) (削除ここまで): Yes610 FS_PROCESSNAME (削除) (削除ここまで): Yes611 FS_READ (削除) (削除ここまで): Yes612 FS_RMDIR (削除) (削除ここまで): Yes613 FS_SETSWAP (削除) (削除ここまで): No614 FS_SHUTDOWN (削除) (削除ここまで): Yes615 FS_VERIFYUNCNAME (削除) (削除ここまで): No616 FS_WRITE (削除) (削除ここまで): Yes583 FS_DELETE(追記) (追記ここまで): Yes 584 FS_DOPAGEIO (追記) (追記ここまで): No 585 FS_EXIT (追記) (追記ここまで): Yes 586 FS_FILEATTRIBUTE(追記) (追記ここまで): Yes 587 FS_FILEINFO (追記) (追記ここまで): Yes 588 FS_FILEIO(追記) (追記ここまで): No 589 FS_FILELOCKS(追記) (追記ここまで): No, function is implemented in the KERNEL 590 FS_FINDCLOSE(追記) (追記ここまで): Yes 591 FS_FINDFIRST(追記) (追記ここまで): Yes 592 FS_FINDFROMNAME (追記) (追記ここまで): Yes 593 FS_FINDNEXT (追記) (追記ここまで): Yes 594 FS_FINDNOTIFYCLOSE(追記) (追記ここまで): Obsolete in OS/2 WARP 595 FS_FINDNOTIFYFIRST(追記) (追記ここまで): Obsolete in OS/2 WARP 596 FS_FINDNOTIFYNEXT(追記) (追記ここまで): Obsolete in OS/2 WARP 597 FS_FLUSHBUF (追記) (追記ここまで): Yes 598 FS_FSCTL(追記) (追記ここまで): Yes 599 FS_FSINFO(追記) (追記ここまで): Yes 600 FS_INIT (追記) (追記ここまで): Yes 601 FS_IOCTL(追記) (追記ここまで): Yes - LOCK & UNLOCK, others are passed to OS2DASD. 602 FS_MKDIR(追記) (追記ここまで): Yes 603 FS_MOUNT(追記) (追記ここまで): Yes 604 FS_MOVE (追記) (追記ここまで): Yes 605 FS_NEWSIZE(追記) (追記ここまで): Yes 606 FS_NMPIPE(追記) (追記ここまで): No 607 FS_OPENCREATE(追記) (追記ここまで): Yes 608 FS_OPENPAGEFILE (追記) (追記ここまで): No 609 FS_PATHINFO (追記) (追記ここまで): Yes 610 FS_PROCESSNAME(追記) (追記ここまで): Yes 611 FS_READ (追記) (追記ここまで): Yes 612 FS_RMDIR(追記) (追記ここまで): Yes 613 FS_SETSWAP(追記) (追記ここまで): No 614 FS_SHUTDOWN (追記) (追記ここまで): Yes 615 FS_VERIFYUNCNAME(追記) (追記ここまで): No 616 FS_WRITE(追記) (追記ここまで): Yes 617 617 618 618 … … 622 622 Version 0.10 - Initial Version 623 623 624 Version 0.20 (削除) (削除ここまで)624 Version 0.20(追記) (追記ここまで) 625 625 - Cache routines have been improved for performance. Removing 'old' sectors 626 from the cache is no longer needed. /T option for CACHEF32 has been (削除) (削除ここまで)626 from the cache is no longer needed. /T option for CACHEF32 has been(追記) (追記ここまで) 627 627 removed. 628 628 … … 631 631 - CHKDSK: Didn't recognize bad-sectors, has been fixed. 632 632 - CHKDSK: Had problems with recognition of some type of free clusters, 633 (削除) (削除ここまで)has been fixed.633 (追記) (追記ここまで) has been fixed. 634 634 - OS2DASD.DMD: Is now based on the latest version. (December '97) 635 635 … … 653 653 654 654 - Corrected a logical error where renaming a file or directory to an existing 655 directory caused the file or directory to be moved into the target (削除) (削除ここまで)655 directory caused the file or directory to be moved into the target(追記) (追記ここまで) 656 656 directory. Now FAT32.IFS returns an error. 657 657 658 - Changed CHKDSK so that if an error is found in on of the FATs CHKDSK (削除) (削除ここまで)658 - Changed CHKDSK so that if an error is found in on of the FATs CHKDSK(追記) (追記ここまで) 659 659 continues, but ignores the /F switch. Previously, CHKDSK would not do any 660 660 additional checks. 661 661 662 - Renaming a file or directory from the workplace shell didn't work because (削除) (削除ここまで)663 of two problems: (削除) (削除ここまで)664 (削除) (削除ここまで)- the WPS uses a strange algoritm to determine if the IFS supported665 long file names which appearantly failed with FAT32. 666 (削除) (削除ここまで)This has been corrected.667 (削除) (削除ここまで)- FAT32.IFS does not support EA's (yet), the WPS renames a file, tries668 (削除) (削除ここまで)to write EAs and since that fails renames the file back again.669 (削除) (削除ここまで)Now FAT32 returns NO_ERROR on the call used to write EAs.662 - Renaming a file or directory from the workplace shell didn't work because(追記) (追記ここまで) 663 of two problems:(追記) (追記ここまで) 664 (追記) (追記ここまで)- the WPS uses a strange algoritm to determine if the IFS supported 665 long file names which appearantly failed with FAT32. 666 (追記) (追記ここまで) This has been corrected. 667 (追記) (追記ここまで)- FAT32.IFS does not support EA's (yet), the WPS renames a file, tries 668 (追記) (追記ここまで) to write EAs and since that fails renames the file back again. 669 (追記) (追記ここまで) Now FAT32 returns NO_ERROR on the call used to write EAs. 670 670 671 671 - CHKDSK now is able to fix cross-linked clusters on the disk. 672 672 673 673 Version 0.41 674 674 … … 683 683 FAT32.IFS contained invalid blocks. 684 684 - Fixed a (BIG) problem with files or directories with long names where 685 if such a file was opened in a DOS session and in an OS/2 session (削除) (削除ここまで)685 if such a file was opened in a DOS session and in an OS/2 session(追記) (追記ここまで) 686 686 simultaniously OS/2 was unable to see that the same file was opened. 687 - Fixed a problem where read-only executables could not be run. (削除) (削除ここまで)687 - Fixed a problem where read-only executables could not be run.(追記) (追記ここまで) 688 688 - Fixed a problem where the algoritm used to determine the highest available 689 689 cluster number was incorrect. 690 690 - Fixed a problem were CHKDSK was unable to fix cross-linked files. 691 - Since some people complained that FAT32 would sometimes hang, (削除) (削除ここまで)691 - Since some people complained that FAT32 would sometimes hang,(追記) (追記ここまで) 692 692 I have modified the internal semaphore mechanism so an error message will 693 693 appear if a semaphore remains blocked for more than a minute. … … 697 697 protected with a semaphore but with a per sector inuse flag. 698 698 - Fixed a problem that caused INSTALL and MINSTALL to abort when FAT32.IFS 699 was loaded. The problem had to do with argument checking with FS_IOCTL (削除) (削除ここまで)699 was loaded. The problem had to do with argument checking with FS_IOCTL(追記) (追記ここまで) 700 700 calls. 701 701 - Fixed a problem that BRIEF, a populair editor under OS/2, trapped or hung 702 itself. The problem had to do with returning improperly formatted (削除) (削除ここまで)702 itself. The problem had to do with returning improperly formatted(追記) (追記ここまで) 703 703 information when querying EAs (FAT32.IFS does not support EAs!) 704 - Corrected a serious problem when a single file was opened more than once (削除) (削除ここまで)704 - Corrected a serious problem when a single file was opened more than once(追記) (追記ここまで) 705 705 and the file was modified using one of the instances. The other instance(s) 706 didn't pick up the changes and FAT32.IFS might trap. (削除) (削除ここまで)706 didn't pick up the changes and FAT32.IFS might trap.(追記) (追記ここまで) 707 707 708 708 Version 0.52 709 - Didn't handle closes from child processes that inherited open files (削除) (削除ここまで)709 - Didn't handle closes from child processes that inherited open files(追記) (追記ここまで) 710 710 properly so the final close would fail. 711 711 … … 717 717 - Changed CHKDSK to accept an /V:1 argument to only show fragmented files, 718 718 while /V[:2] also lists all files. 719 - Made it possible that renaming a file to a new name where only the (削除) (削除ここまで)719 - Made it possible that renaming a file to a new name where only the(追記) (追記ここまで) 720 720 case was changed worked. 721 721 … … 731 731 732 732 Version 0.63: 733 - Finally understood why CHKDSK failed on very large disks. UFAT32.DLL (削除) (削除ここまで)733 - Finally understood why CHKDSK failed on very large disks. UFAT32.DLL(追記) (追記ここまで) 734 734 accesses the disk using DosOpen with OPEN_FLAGS_DASD. In that mode default 735 735 behaviour is that the disk is accessed using physical byte offsets from the 736 beginning of the (logical) disk. Now since the maximum value in a 32 bit (削除) (削除ここまで)736 beginning of the (logical) disk. Now since the maximum value in a 32 bit(追記) (追記ここまで) 737 737 integer is 2^32 this value divided by 512 was the maximum sector that could 738 738 be read (= sector 8388608 = 4Gb disk size maximum). 739 Now UFAT32 uses the same trick as HPFS uses, via a call to DosFSCtl disk (削除) (削除ここまで)740 access is switched to sector mode so 2^32 sectors can be accessed. (削除) (削除ここまで)739 Now UFAT32 uses the same trick as HPFS uses, via a call to DosFSCtl disk(追記) (追記ここまで) 740 access is switched to sector mode so 2^32 sectors can be accessed.(追記) (追記ここまで) 741 741 This means CHKDSK can (theoretically) check disks upto 2048 gigabytes. 742 742 743 743 Version 0.64: 744 744 - Again a problem with CHKDSK, this time the file allocation check failed if 745 there were more than 65535 clusters assigned to a file. (削除) (削除ここまで)745 there were more than 65535 clusters assigned to a file.(追記) (追記ここまで) 746 746 - FAT32.IFS now reports fake cluster sizes and total and free cluster counts 747 whenever a DOS session queries free space. The maximum cluster size (削除) (削除ここまで)748 returned has been set to 32 Kb and the maximum for total and free clusters (削除) (削除ここまで)747 whenever a DOS session queries free space. The maximum cluster size(追記) (追記ここまで) 748 returned has been set to 32 Kb and the maximum for total and free clusters(追記) (追記ここまで) 749 749 is 65526 clusters so the maximum disk size in dos is reported as almost 2Gb. 750 - Encountered (and fixed) a trap that occured whenever a volume was flushed (削除) (削除ここまで)751 via a explicit call and there were still dirty sectors in call. (削除) (削除ここまで)752 It occured in code I changed in version 0.60 and this was the first time I (削除) (削除ここまで)750 - Encountered (and fixed) a trap that occured whenever a volume was flushed(追記) (追記ここまで) 751 via a explicit call and there were still dirty sectors in call.(追記) (追記ここまで) 752 It occured in code I changed in version 0.60 and this was the first time I(追記) (追記ここまで) 753 753 trapped on it, so the combination of factors appears unlikely. 754 754 - Modified FS_CHGFILEPTR so negative seeks will be handled properly and … … 757 757 assumed they were not used. Some users reported files beeing show twice in 758 758 some application so: I stand corrected and so is FAT32.IFS. 759 - Corrected a potential problem where (theoretically) files could be given (削除) (削除ここまで)759 - Corrected a potential problem where (theoretically) files could be given(追記) (追記ここまで) 760 760 a directory attribute. 761 - Changed the algoritme used when no large enough contiguous fat chain is (削除) (削除ここまで)761 - Changed the algoritme used when no large enough contiguous fat chain is(追記) (追記ここまで) 762 762 available and the fat chain has to be constructed from various chains. 763 763 Before the change an algoritme searching for individual free clusters was 764 used. Now FAT32.IFS searches the largest free chain assigns it and then (削除) (削除ここまで)765 searches for the next largest free chain until a chain long enough is (削除) (削除ここまで)766 created. This is still not very fast, but will only really occur of the (削除) (削除ここまで)764 used. Now FAT32.IFS searches the largest free chain assigns it and then(追記) (追記ここまで) 765 searches for the next largest free chain until a chain long enough is(追記) (追記ここまで) 766 created. This is still not very fast, but will only really occur of the(追記) (追記ここまで) 767 767 disk is rather full and very fragmented. 768 768 769 769 Version 0.65: 770 770 - Files with valid 8.3 lowercase filenames where returned by findfirst/next 771 in DOS sessions in lowercase as well. Some programs don't like that. (削除) (削除ここまで)771 in DOS sessions in lowercase as well. Some programs don't like that.(追記) (追記ここまで) 772 772 Now findfirst/next in DOS sessions always returns an uppercase name. 773 773 (This problem only occured when LFN's were hidden to DOS.) 774 774 - Corrected a problem where while filling the buffer for FindFirst/Next too 775 775 much data was initialized (due to using strncpy) and data was overwritten. 776 This was most appearant with OS/2 Commander that trapped on a FAT32 (削除) (削除ここまで)776 This was most appearant with OS/2 Commander that trapped on a FAT32(追記) (追記ここまで) 777 777 directory with many files. 778 778 779 779 Version 0.66: 780 780 - DosSetFileInfo returned an error (ERROR_INVALID_LEVEL) when trying to write 781 Extended attributes. Now FAT32.IFS reports NO_ERROR (But still doesn't (削除) (削除ここまで)781 Extended attributes. Now FAT32.IFS reports NO_ERROR (But still doesn't(追記) (追記ここまで) 782 782 write the EA!). This makes f.i. that the installation of the OS/2 783 783 Netscape pluginpack now works properly. … … 786 786 scan. This has been fixed. 787 787 - Modified the behaviour of DosSetFileInfo so that it will only set date/time 788 values in the directory. Before DosSetFileInfo also set the attribute, but (削除) (削除ここまで)788 values in the directory. Before DosSetFileInfo also set the attribute, but(追記) (追記ここまで) 789 789 I found that this also doesn't work on HPFS, so I modified the behaviour. 790 790 - Modified the default MONITOR logging so that (almost) all FS_XXXX calls are 791 shown with the return values given. (削除) (削除ここまで)791 shown with the return values given.(追記) (追記ここまで) 792 792 793 793 Version 0.70: 794 794 - Most significant change is the implementation of EXTENDED ATTRIBUTES. 795 Currently they will only be supported if /EAS is specified after FAT32.IFS (削除) (削除ここまで)795 Currently they will only be supported if /EAS is specified after FAT32.IFS(追記) (追記ここまで) 796 796 in the config.sys. Please read the chapter about extended attributes. 797 797 … … 807 807 to run (without a cache - slow!) 808 808 809 - Received a report about a possible memory leakage problem in FAT32.IFS. (削除) (削除ここまで)809 - Received a report about a possible memory leakage problem in FAT32.IFS.(追記) (追記ここまで) 810 810 Changed CACHEF32.EXE so when run, it will show the number of GDT selectors 811 811 currently allocated for FAT32.IFS. … … 815 815 DOS programs never access EA's, but EAUTIL can be used in DOS sessions, and 816 816 didn't work. Now it does. 817 - There was another problems with finding EAs when FAT32.IFS was set to the (削除) (削除ここまで)817 - There was another problems with finding EAs when FAT32.IFS was set to the(追記) (追記ここまで) 818 818 mode in which internally short names were used (CACHEF32 /FS). Now this 819 819 seems to work properly. 820 820 821 821 Version 0.72: 822 - Forgot build in the EA logic for creating and removing directories. Has (削除) (削除ここまで)822 - Forgot build in the EA logic for creating and removing directories. Has(追記) (追記ここまで) 823 823 been added. 824 824 825 825 Version 0.73: 826 - Using DosSetPathInfo, it was possible to create an EA file for a non (削除) (削除ここまで)826 - Using DosSetPathInfo, it was possible to create an EA file for a non(追記) (追記ここまで) 827 827 existing file. This lead f.i. to a ' EA. SF' file in the root directory. 828 828 This problem has been corrected. 829 - Changed a bit in the algoritm for making a short name for a file with a (削除) (削除ここまで)829 - Changed a bit in the algoritm for making a short name for a file with a(追記) (追記ここまで) 830 830 longname. 831 831 832 832 Version 0.74: 833 - Corrected a problem with DosFindFirst/next when the buffer wasn't large (削除) (削除ここまで)834 enough for the extended attributes and FAT32.IFS returned (削除) (削除ここまで)833 - Corrected a problem with DosFindFirst/next when the buffer wasn't large(追記) (追記ここまで) 834 enough for the extended attributes and FAT32.IFS returned(追記) (追記ここまで) 835 835 ERROR_EAS_DIDNT_FIT when more than one entry was placed in the resultbuffer. 836 Now FAT32.IFS returns this error only if the EA's of the first (削除) (削除ここまで)836 Now FAT32.IFS returns this error only if the EA's of the first(追記) (追記ここまで) 837 837 matching entry don't fit in the buffer. 838 (This error lead to the WPS giving an error that no matching entries were (削除) (削除ここまで)838 (This error lead to the WPS giving an error that no matching entries were(追記) (追記ここまで) 839 839 found on opening of a directory) 840 840 841 841 Version 0.75: 842 842 - Added a check for valid EA names. 843 - Added a translation mechanism for long filenames between the Windows (削除) (削除ここまで)843 - Added a translation mechanism for long filenames between the Windows(追記) (追記ここまで) 844 844 Character set and OS/2 character set. 845 845 See: WINDOWS & OS/2 CHARACTER SETS for more information. … … 852 852 - Corrected a problem when more then 512 lost chains were found. (CHKDSK can 853 853 only recover 512 lost chains at one run) 854 - Corrected a problem in OS/2 sessions (introduced in version 0.75) where (削除) (削除ここまで)854 - Corrected a problem in OS/2 sessions (introduced in version 0.75) where(追記) (追記ここまで) 855 855 valid 8.3 filenames in lowercase where always stored in uppercase. 856 856 857 857 Version 0.78: 858 - Corrected a TRAP that could occur when the cache is full with dirty (削除) (削除ここまで)858 - Corrected a TRAP that could occur when the cache is full with dirty(追記) (追記ここまで) 859 859 sectors and the oldest dirty single sector was flushed using a single flush 860 860 routine. The trap message was 'WriteCacheSector: VOLINFO not found!'. … … 866 866 an access violation. 867 867 - Corrected a problem with DosOpen when on Opening an existing file with only 868 the FILE_CREATE (OPEN_ACTION_CREATE_IF_NEW) bit set (and not the FILE_OPEN (削除) (削除ここまで)869 flag) the file was created while the open should fail. (削除) (削除ここまで)870 - Corrected a problem that the characterset translate tables would be (削除) (削除ここまで)868 the FILE_CREATE (OPEN_ACTION_CREATE_IF_NEW) bit set (and not the FILE_OPEN(追記) (追記ここまで) 869 flag) the file was created while the open should fail.(追記) (追記ここまで) 870 - Corrected a problem that the characterset translate tables would be(追記) (追記ここまで) 871 871 overwritten internally leading to all kinds of funny results. (Duplicate 872 872 directories etc) … … 876 876 877 877 Version 0.79: 878 - Rewrote the emergency flush routine so it will handle multiple FAT32 (削除) (削除ここまで)879 partitions better. (削除) (削除ここまで)878 - Rewrote the emergency flush routine so it will handle multiple FAT32(追記) (追記ここまで) 879 partitions better.(追記) (追記ここまで) 880 880 - Made some minor modifications in UFAT32.DLL (For CHKDSK). 881 881 - A trap was solved when an EA file could not be repaired … … 889 889 bytes large. 890 890 - Corrected a problem with DosOpen with the Truncate flag set and when the 891 target file already existed and had EAs. The open failed, but the file was (削除) (削除ここまで)891 target file already existed and had EAs. The open failed, but the file was(追記) (追記ここまで) 892 892 truncated and a lost cluster was created. 893 893 - Created PARTFILT.TXT file about PARTFILT and DISKINFO. 894 - Implemented an version check between the IFS and UFAT32.DLL (for CHKDSK) (削除) (削除ここまで)894 - Implemented an version check between the IFS and UFAT32.DLL (for CHKDSK)(追記) (追記ここまで) 895 895 and CACHEF32.EXE. 896 896 … … 902 902 the attribute. From 16 bits programs however, this doesn't seem to work on 903 903 FAT, HPFS and FAT32. Don't know why. 904 904 905 905 Version 0.82: 906 - Changed a bit in the algoritm for making a short name for a file with a (削除) (削除ここまで)906 - Changed a bit in the algoritm for making a short name for a file with a(追記) (追記ここまで) 907 907 longname (again). Now filenames starting with a dot are handled better. 908 - Changed the (internal) memory handling routines to use more then one (削除) (削除ここまで)909 selector so I could use this for FindFirst/Next handling instead of (削除) (削除ここまで)908 - Changed the (internal) memory handling routines to use more then one(追記) (追記ここまで) 909 selector so I could use this for FindFirst/Next handling instead of(追記) (追記ここまで) 910 910 allocation one selector per FindFirst/Next call. 911 911 This was neccessary because a DOS session can fire a lot of FindFirst calls 912 912 only for checking existence of files. Before the modification FAT32.IFS 913 913 could run out of memory after say a couple of hundred FindFirst calls. 914 (I found that OS/2 itself doesn't allow a DOS session to fire more then (削除) (削除ここまで)914 (I found that OS/2 itself doesn't allow a DOS session to fire more then(追記) (追記ここまで) 915 915 round 500 FindFirsts. After that OS/2 starts reusing find handles.) 916 916 I encountered this problem when trying to unarj the Novell Netware client … … 923 923 and unicode. This should work better for some NLS versions of OS/2. 924 924 - Added a switch to CACHEF32 to dynamically change the priority of the lazy 925 write thread. The default priority is still idle-time, but this can be (削除) (削除ここまで)925 write thread. The default priority is still idle-time, but this can be(追記) (追記ここまで) 926 926 changed to a higher priority. 927 927 - Did experiment a bit with lazy writing in general. In my own system it 928 improved performance somewhat. (削除) (削除ここまで)929 - Corrected a problem in PARTFILT where whenever a HIDDEN partition type (削除) (削除ここまで)928 improved performance somewhat.(追記) (追記ここまで) 929 - Corrected a problem in PARTFILT where whenever a HIDDEN partition type(追記) (追記ここまで) 930 930 was specified after /P this didn't always work properly. Now when a hidden 931 931 partition type is specified, the unhidden type is also handled by PARTFILT. … … 933 933 Version 0.84: 934 934 - Got a message from someone complaining that the change in PARTFILT made him 935 loose the ability to mount hidden 'normal' partitions since PARTFILT (削除) (削除ここまで)935 loose the ability to mount hidden 'normal' partitions since PARTFILT(追記) (追記ここまで) 936 936 presented all partition types as IFS. Now PARTFILT show normal partitions 937 by their actual types and only not-by-OS/2 supported types as IFS (削除) (削除ここまで)937 by their actual types and only not-by-OS/2 supported types as IFS(追記) (追記ここまで) 938 938 partitions. 939 - Increased performance for accessing large files by keeping track of first (削除) (削除ここまで)940 and last cluster for each open file, and even the current cluster for each (削除) (削除ここまで)939 - Increased performance for accessing large files by keeping track of first(追記) (追記ここまで) 940 and last cluster for each open file, and even the current cluster for each(追記) (追記ここまで) 941 941 open instance. 942 942 - Removed the limit for the maximum number of open files. … … 945 945 to allocated memory per open file. 946 946 Problems I encountered were trap D's and internal fatal messages. 947 - Changed the way monitor works. Introduced a 'trace mask'. See MONITOR (削除) (削除ここまで)947 - Changed the way monitor works. Introduced a 'trace mask'. See MONITOR(追記) (追記ここまで) 948 948 above. 949 949 … … 951 951 - A user pointed me at the problem that ReadOnly files cannot be renamed. 952 952 This problem has been corrected. 953 - Corrected a problem whenever a non-existing file was openen. If later the (削除) (削除ここまで)954 file was created this could lead to a trap (at least in theory: I haven't (削除) (削除ここまで)953 - Corrected a problem whenever a non-existing file was openen. If later the(追記) (追記ここまで) 954 file was created this could lead to a trap (at least in theory: I haven't(追記) (追記ここまで) 955 955 seen it nor heard it actually occured). 956 956 - Changed PARTFILT again. Whenever a hidden partition type was specified 957 partfilt also virtualized the unhidden type. So if /P 16 was specified, (削除) (削除ここまで)958 both types 16 and 6 were virtualized. This could lead to unwanted results. (削除) (削除ここまで)957 partfilt also virtualized the unhidden type. So if /P 16 was specified,(追記) (追記ここまで) 958 both types 16 and 6 were virtualized. This could lead to unwanted results.(追記) (追記ここまで) 959 959 960 960 So I modified the mechanism again. … … 966 966 For the partition types PARTFILT virtualizes the following rules apply: 967 967 968 Normal partition types (types 1, 4, 6, 7, but also 11, 14, 16 and 17) (削除) (削除ここまで)969 are reported to OS/2 with their actual -unhidden- partition type. (削除) (削除ここまで)968 Normal partition types (types 1, 4, 6, 7, but also 11, 14, 16 and 17)(追記) (追記ここまで) 969 are reported to OS/2 with their actual -unhidden- partition type.(追記) (追記ここまで) 970 970 971 971 Any other partition types specified after /P are reported as un-hidden IFS 972 partitions. (削除) (削除ここまで)973 Any other partition types NOT specified after /P are reported as their (削除) (削除ここまで)972 partitions.(追記) (追記ここまで) 973 Any other partition types NOT specified after /P are reported as their(追記) (追記ここまで) 974 974 actual -unhidden- type. 975 975 … … 980 980 Otherwise, OS/2 will not boot at all. 981 981 982 - CACHEF32.EXE did not properly handle the /P:x argument when specified in (削除) (削除ここまで)982 - CACHEF32.EXE did not properly handle the /P:x argument when specified in(追記) (追記ここまで) 983 983 CONFIG.SYS. The argument was lost. This has been fixed. 984 984 985 985 Version 0.86: 986 - Always thought that it was not allowed to the directory bit set in (削除) (削除ここまで)986 - Always thought that it was not allowed to the directory bit set in(追記) (追記ここまで) 987 987 DosSetPathInfo and therefor I rejected calls with this bit set. I was wrong. 988 988 Now DosSetPathInfo accepts the directory bit set (for directories only). 989 989 990 - Modified partfilt so it will also scan partitions inside a extended type F (削除) (削除ここまで)991 partition (partfilt is now on version 1.08). Modified DISKINFO.EXE to do (削除) (削除ここまで)992 the (削除) (削除ここまで)990 - Modified partfilt so it will also scan partitions inside a extended type F(追記) (追記ここまで) 991 partition (partfilt is now on version 1.08). Modified DISKINFO.EXE to do(追記) (追記ここまで) 992 the(追記) (追記ここまで) 993 993 same. 994 994 … … 1006 1006 - Modified CACHEF32.EXE so it will also run if UCONV.DLL cannot be loaded. 1007 1007 If that is the case, no UNICODE translate table will be loaded. 1008 - Solved a problem when a file was rename when on the case mapping was (削除) (削除ここまで)1008 - Solved a problem when a file was rename when on the case mapping was(追記) (追記ここまで) 1009 1009 changed. If the file had extended attributes the rename failed and the EA 1010 1010 was lost. … … 1012 1012 Version 0.88: 1013 1013 - DISKINFO still didn't show partitions inside an extended partition type F. 1014 - Fixed a potential problem in the lazy write routines. This could lead to (削除) (削除ここまで)1014 - Fixed a potential problem in the lazy write routines. This could lead to(追記) (追記ここまで) 1015 1015 sectors not being written when they should have. (have never seen it though) 1016 1016 - Made it work with Fixpack 10. (FP10 made FAT32.IFS trap) … … 1023 1023 - I've had a report from someone with a problem where the drives where mounted 1024 1024 after CACHEF32 had queried CACHE settings. Since the cache is allocated on 1025 first mount this didn't work. I have added a call to force the drives (削除) (削除ここまで)1025 first mount this didn't work. I have added a call to force the drives(追記) (追記ここまで) 1026 1026 to be mounted before CACHEF32 queries the cache settings. 1027 1027 - Fixed a small division by zero in CACHEF32 when the cache was zero sectors 1028 1028 large. 1029 1029 - Fixed the 'cannot find message file' problem in CACHEF32.EXE. 1030 - Some users keep having troubles with 'error cannot find SH". Just for (削除) (削除ここまで)1031 myself (削除) (削除ここまで)1030 - Some users keep having troubles with 'error cannot find SH". Just for(追記) (追記ここまで) 1031 myself(追記) (追記ここまで) 1032 1032 I added the filename there. 1033 1033 - Replaced an internal call (FSH_PROBEBUF) by a DevHelp call. 1034 - Fixed a trap I got due to a reentrancy problem in my memory allocation (削除) (削除ここまで)1034 - Fixed a trap I got due to a reentrancy problem in my memory allocation(追記) (追記ここまで) 1035 1035 routines. 1036 1036 - Changed the way data is kept per open file instance because I have received 1037 some reports from users that they got a 'ERROR: Cannot find the IO!" (削除) (削除ここまで)1037 some reports from users that they got a 'ERROR: Cannot find the IO!"(追記) (追記ここまで) 1038 1038 message. 1039 1039 - FAT32.IFS had its code segments marked as EXECUTEONLY. Now AURORA doesn't 1040 seem to like that and traps. The code segments are no longer marked this (削除) (削除ここまで)1040 seem to like that and traps. The code segments are no longer marked this(追記) (追記ここまで) 1041 1041 way but as EXECUTEREAD. 1042 1042 … … 1044 1044 - Found some problems with FS_COPY. If FS_COPY was copying a file the target 1045 1045 file was not protected from being deleted or renamed in another session. 1046 - Noticed that I had the default cache size incorrectly set to 128 Kb. (削除) (削除ここまで)1046 - Noticed that I had the default cache size incorrectly set to 128 Kb.(追記) (追記ここまで) 1047 1047 Modified it to 1024 kb and added a warning message if no /CACHE argument 1048 1048 is present. 1049 - FS_COPY didn't check if source and target where on the same partition. (I (削除) (削除ここまで)1049 - FS_COPY didn't check if source and target where on the same partition. (I(追記) (追記ここまで) 1050 1050 incorrectly assumed OS/2 did this check.). Now FS_COPY doesn't try to handle 1051 the copy when source and target are on different drives. This way the copy (削除) (削除ここまで)1051 the copy when source and target are on different drives. This way the copy(追記) (追記ここまで) 1052 1052 is done by OS/2 itself. 1053 - Modified the way data is written from the cache to disk. Instead of (削除) (削除ここまで)1053 - Modified the way data is written from the cache to disk. Instead of(追記) (追記ここまで) 1054 1054 instructing the Device Driver to write data directly from cache to disk, 1055 1055 the data is now first copied to another memory area thereby releasing the 1056 data in the cache a lot sooner. This way the IFS does not have to wait (削除) (削除ここまで)1057 for the device driver to finish before a specific sector in cache is (削除) (削除ここまで)1056 data in the cache a lot sooner. This way the IFS does not have to wait(追記) (追記ここまで) 1057 for the device driver to finish before a specific sector in cache is(追記) (追記ここまで) 1058 1058 available again. 1059 1059 The drawback is that this makes FAT32.IFS to use more (physical) memory. 1060 With a cache size of 2048 Kb, an additional 480 Kb is allocated. (削除) (削除ここまで)1061 With smaller cache sizes the additional data reduces relatively. (a cache (削除) (削除ここまで)1060 With a cache size of 2048 Kb, an additional 480 Kb is allocated.(追記) (追記ここまで) 1061 With smaller cache sizes the additional data reduces relatively. (a cache(追記) (追記ここまで) 1062 1062 size of 1024 Kb leads to an additional memory allocation of 240 Kb) 1063 1063 - Never had any error handling (message) in the routine that is called by the 1064 device driver to notify completion of the strategy2 request list. This (削除) (削除ここまで)1064 device driver to notify completion of the strategy2 request list. This(追記) (追記ここまで) 1065 1065 version has it. This is mainly to get more light on FAT32.IFS and aurora. 1066 1066 … … 1068 1068 - Got a report that FAT32.IFS ignored the fourth character of the extention. 1069 1069 Looking for the cause I found that FAT32.IFS created incorrect short name 1070 equivalents for files with a four character long extention. (削除) (削除ここまで)1070 equivalents for files with a four character long extention.(追記) (追記ここまで) 1071 1071 In that specific case the fourth character was ignored when creating 1072 the shortname. The effect was that e.g. a file called file.1234 and (削除) (削除ここまで)1072 the shortname. The effect was that e.g. a file called file.1234 and(追記) (追記ここまで) 1073 1073 file.1235 ended up having the same shortname. FAT32.IFS now 1074 no longer exhibits this behaviour, but you still might have double (削除) (削除ここまで)1075 shortnames in the same directory on your disk. I don't think SCANDISK (削除) (削除ここまで)1074 no longer exhibits this behaviour, but you still might have double(追記) (追記ここまで) 1075 shortnames in the same directory on your disk. I don't think SCANDISK(追記) (追記ここまで) 1076 1076 detects this problem. Please note this could only have happened with 1077 files having an extention of four chars for which all chars except the (削除) (削除ここまで)1077 files having an extention of four chars for which all chars except the(追記) (追記ここまで) 1078 1078 fourth extention char were equal. 1079 1080 To check this, set FAT32.IFS to use short names internally (CACHEF32 /FS), (削除) (削除ここまで)1079 1080 To check this, set FAT32.IFS to use short names internally (CACHEF32 /FS),(追記) (追記ここまで) 1081 1081 and in a DOS session do a DIR command. If you detect any duplicate names, 1082 1082 switch back to an OS/2 session and rename one of these files to another 1083 name and then rename it back to the original name. (削除) (削除ここまで)1084 1085 - Modified the calling of the strategy2 calls. Now FAT32.IFS no longer (削除) (削除ここまで)1083 name and then rename it back to the original name.(追記) (追記ここまで) 1084 1085 - Modified the calling of the strategy2 calls. Now FAT32.IFS no longer(追記) (追記ここまで) 1086 1086 request confirmation per individual sector. This fixes the problems 1087 with AURORA. (削除) (削除ここまで)1088 1089 The problem with AURORA (Warp Server for eBusiness) FAT32.IFS was (削除) (削除ここまで)1087 with AURORA.(追記) (追記ここまで) 1088 1089 The problem with AURORA (Warp Server for eBusiness) FAT32.IFS was(追記) (追記ここまで) 1090 1090 experiencing was caused by a bug in the Logical Volume Manager that did 1091 not properly confirm individual requests. Since FAT32.IFS now no longer (削除) (削除ここまで)1091 not properly confirm individual requests. Since FAT32.IFS now no longer(追記) (追記ここまで) 1092 1092 depends on this individual confirmation the bug is no longer relevant. 1093 1093 IBM did confirm this bug to me (October 1999) and promissed it would be … … 1095 1095 1096 1096 - Introduced a separate thread (from CACHEF32.EXE) that runs at time critical 1097 priority. The thread is awakened whenever the cache runs full with dirty (削除) (削除ここまで)1097 priority. The thread is awakened whenever the cache runs full with dirty(追記) (追記ここまで) 1098 1098 sectors and takes care of flushing these dirty sectors. 1099 1099 1100 - Corrected a problem with Extended Attributes when a file had very large (削除) (削除ここまで)1100 - Corrected a problem with Extended Attributes when a file had very large(追記) (追記ここまで) 1101 1101 extended attributes (almost 65536 bytes) the system would trap. 1102 1102 1103 1103 - Corrected a problem when a sector towards the end of the disk was read. 1104 Due to the read-ahead function 1 sector too far was read and the read (削除) (削除ここまで)1105 failed. (削除) (削除ここまで)1104 Due to the read-ahead function 1 sector too far was read and the read(追記) (追記ここまで) 1105 failed.(追記) (追記ここまで) 1106 1106 1107 1107 - Noticed that the diskspace under DOS was not correctly returned. The faked … … 1110 1110 1111 1111 - Until this version, the strategy2 routines did not set the flag to request 1112 the disk controller to cache the request on the outboard controller. I (削除) (削除ここまで)1112 the disk controller to cache the request on the outboard controller. I(追記) (追記ここまで) 1113 1113 did not set this flag since it didn't seem to matter on my own machine. 1114 1114 However, this version has the flag set since some of you might profit from … … 1116 1116 1117 1117 - Enlarged maximum amount of data that is flushed (when lazy writing is used) 1118 to 64 Kb. Hopefully, this will increase performance for those (削除) (削除ここまで)1118 to 64 Kb. Hopefully, this will increase performance for those(追記) (追記ここまで) 1119 1119 disk controllers that do not have the on-board cache enabled. 1120 1120 1121 1121 - Did an effort to solve the problem when a cluster chain becomes improperly 1122 terminated. FAT32.IFS simply ignores the problem now and assumes end of (削除) (削除ここまで)1122 terminated. FAT32.IFS simply ignores the problem now and assumes end of(追記) (追記ここまで) 1123 1123 file. 1124 1124 CHKDSK (UFAT32.DLL) detects and corrects this problem. … … 1127 1127 1128 1128 - When a FAT32 volume was not shut down properly the IFS did not allow files 1129 to be opened. This caused device drivers etc during shutdown not being (削除) (削除ここまで)1130 loaded from a FAT32 volume. Now FAT32.IFS allows files to be read from a (削除) (削除ここまで)1129 to be opened. This caused device drivers etc during shutdown not being(追記) (追記ここまで) 1130 loaded from a FAT32 volume. Now FAT32.IFS allows files to be read from a(追記) (追記ここまで) 1131 1131 dirty volume. 1132 1132 1133 - When a directory was moved the .. entry in that directory was not updated (削除) (削除ここまで)1133 - When a directory was moved the .. entry in that directory was not updated(追記) (追記ここまで) 1134 1134 to point to the proper parent directory. This has been corrected. 1135 1135 … … 1146 1146 Version 0.93: 1147 1147 1148 - Modified the way CHKDSK detect a bad cluster. (削除) (削除ここまで)1149 1150 - When the disk was dirty, CHKDSK was unable to rename a lost EA file to a (削除) (削除ここまで)1148 - Modified the way CHKDSK detect a bad cluster.(追記) (追記ここまで) 1149 1150 - When the disk was dirty, CHKDSK was unable to rename a lost EA file to a(追記) (追記ここまで) 1151 1151 proper file. This has been fixed. 1152 1152 … … 1162 1162 1163 1163 - Fixed a problem when running in 'Internal Shortname mode' that long files 1164 were not found. (削除) (削除ここまで)1164 were not found.(追記) (追記ここまで) 1165 1165 1166 1166 Version 0.95: … … 1305 1305 functionality of IFS. 1306 1306 1307 (追記) Version 0.9.12: (追記ここまで) 1308 (追記) (追記ここまで) 1309 (追記) - Fixed the problem that CACHEF32 is crashed after calling CHKDSK for dirty (追記ここまで) 1310 (追記) volume. (追記ここまで) 1311 (追記) (追記ここまで) 1312 (追記) - Fixed the problem the regonition of USB removable media takes very long time (追記ここまで) 1313 (追記) when inserting it since 0.9.11. (追記ここまで) 1314 (追記) This is because FAT32 always calculates free space on mount. Now, FAT32 (追記ここまで) 1315 (追記) calculates free space only if /CALCFREE specified or free space info was not (追記ここまで) 1316 (追記) stored on disk. (追記ここまで) 1317 (追記) (追記ここまで) 1318 (追記) - Fixed the trap when removing USB removable media without eject. (追記ここまで) 1319 (追記) (追記ここまで) 1320 (追記) - Improved Read/Write performance. By Lars. (追記ここまで) 1321 (追記) (追記ここまで) 1322 (追記) *** Known Problems *** (追記ここまで) 1323 (追記) (追記ここまで) 1324 (追記) - When using USB removable media with other OS such as Windows, free space can (追記ここまで) 1325 (追記) be incorrect. At this time, you should use 'chkdsk' to correct it or (追記ここまで) 1326 (追記) '/CALCFREE' to avoid it. (追記ここまで) 1327 (追記) (追記ここまで)
Note:
See TracChangeset
for help on using the changeset viewer.