Lines Matching refs:OS

49 	When to mark filesystem dirty so that OS/2 checks it.
63 As in OS/2, filenames are case insensitive. However, shell thinks that names
70 OS/2 ignores dots and spaces at the end of file name, so this driver does as
78 On HPFS partitions, OS/2 can associate to each file a special information called
81 variable length. OS/2 stores window and icon positions and file types there. So
107 incompatible with OS/2. OS/2 PmShell symlinks are not supported because they are
118 file has a pointer to codepage its name is in. However OS/2 was created in
120 support is quite buggy. I have Czech OS/2 working in codepage 852 on my disk.
121 Once I booted English OS/2 working in cp 850 and I created a file on my 852
123 Czech OS/2, the file was completely inaccessible under any name. It seems that
124 OS/2 uppercases the search pattern with its system code page (852) and file
127 Czech OS/2 another file in that directory, that file was inaccessible too. OS/2
133 modification saved me.  Never mix different language versions of OS/2 on one
136 would cause more problems than benefit with such buggy implementation in OS/2.
145 HPFS386 on OS/2 server is not supported. HPFS386 installed on normal OS/2 client
146 should work. If you have OS/2 server, use only read-only mode. I don't know how
156 OS/2 can't access files if the path is longer than about 256 chars but this
193 Old versions of this driver created sometimes unbalanced dnode trees. OS/2
200 again. Do it in Linux, not OS/2! If you see this message in directory that is
204 Bugs in OS/2
211 OS/2, OS/2 marks it as 'long'. chkdsk then removes this flag saying "Minor fs
214 File names like "a .b" are marked as 'long' by OS/2 but chkdsk "corrects" it and
279        not 100% ok, I have no info on it and OS/2 doesn't want to create them)
293 1.96   Added workaround for one bug in OS/2 (HPFS locked up, HPFS386 reported
311        Better directory handling; workaround for "unbalanced tree" bug in OS/2
334        Now it works with Japanese version of OS/2