Website:Walter Gregg

On this page: Main Content. Explanation of SYS0003 on CD. Action Fixing SYS0003 on CD. Details About SYS0003 on CD. References About SYS0003 on CD.

OS/2: SYS0003: The system cannot find the [CD-DVD] path specified

December 2016. Older versions of OS/2 may not be able to open certain CD/DVD folders or even list files within them.

Contents ↑

Explanation of SYS0003 on CD

The path named in the command does not exist in the CD-DVD directory prior to another path that would come after it in the expected sort order. When the system sees a path name that should follow the one it is seeking, it stops looking.

Contents ↑

Action Fixing SYS0003 on CD

Update the CDFS.IFS driver to version 14.103, 2005-07-28, as supplied with recent eComStation. This version does not have the sort order bug. You may use 'bldlevel \os2\boot\cdfs.ifs' to verify the version. Avoid versions known to have the bug, including 14.20 (1998-10-28 supplied with JCDFS) and 8.263 (1998-10-14) supplied with a Warp 3 fixpak. These alternatives may be used in an emergency:

Because of such issues it is much better to update the CDFS.IFS driver and not intentionally mangle folder names or degrade to the much shortened ISO-9660 names.

Contents ↑

Details About SYS0003 on CD

It's difficult to account precisely for the behavior of the system with the old driver. In the first place, it seems that only folder names are affected, not file names. In the second, for folder names, results don't quite match reason. As a hypothesis, it may cache CD folder names in case insensitive lexical order but when searching for names assume that it is in case sensitive ASCII order and terminates searches at the first folder name expected to come after the target. Consider the CD order: AB3 AC6 Ab2 Ac5 ab1 ac4. Hypothesizing that is is cached as ab1 Ab2 AB3 ac4 Ac5 AC6 we can predict what will be inaccessible, but we won't be quite correct:

Folder Expected Correct? Reasoning
ab1. Accessible? Yes. It is not preceeded by anything that comes later in CD order.
Ab2. Inaccessible? No. It is preceeded by ab1, which comes later in CD order. But it is read anyway.
AB3. Accessible? Yes. It is not preceeded by anything that comes later in CD order.
ac4. Accessible? Yes. It is not preceeded by anything that comes later in CD order.
Ac5. Inaccessible? Yes. It is preceeded by ab1 and ac4, which come later in CD order.
AC6. Inacessible? Yes. It is preceeded by Ab2, Ac5, ab1, and ac4, which come later in CD order.

It doesn't matter too much if we don't understand precisely what conditions trigger this bug. Whenever it bars our access to a CD folder is sure to be at the worst possible moment. The fix, as aforesaid, is the later version of CDFS.IFS.

Contents ↑

References About SYS0003 on CD

The bug is mentioned in the MkIsoFs readme.os2 file:

"Note that the Joliet implementation on OS/2 is buggy:

"It expects the file in the directories in the wrong order. While Microsoft wants the files to be in ASCII (binary) order, OS/2 likes to have the files in lexical order (uppercase and lowercase together). This makes CD's with Joliet attributes unreadable on OS/2 if there are files that start the same way but differ in case."

Several old newsgroup threads discuss the issue. For example, see:

Contents ↑

2016. (Walt.Gregg.Juneau.AK.US/6/os2-access-cd-folders;

 No Privacy