OSDev.org

There is seriously lack of detail in the question.
Check this out: How_To_Ask_Questions.

Get back to your cave! =)

Why the big font? Anyway, I would presume that it's your filesystem driver that does the work, and not the kernel.. Your post lack all information needed to help you.

What filesystem are you using? What errors do you get? Have you actually implemented subdirectory support, and in that case can we have a look on the code that parses the path and is supposed to open the file? Have you checked the Wiki for FS info, and read the forum rules thread?

Is this in an os you are writing, or an existing os? Also what filesystem and are you accessing the fs in ring 0 or userland? Can you provide source? What happens instead of successfully opening the file?

You start by searching path in the current directory, and if there's a match, you check the next char in path whether it’s directory separator. If not, file not found, if yes, you cut off the part from path (including separator), set the current directory to what's just found, and repeat the whole procedure until EOS in path found.

current dir 0 (inode, cluster, whatever), path ’Apps\file.bin’
1st entry App (1), match, next char in path ’s’, not separator, no match
2nd entry Apps (2), match, next char ’\’, directory separator, match
current dir 2, path ’file.bin’
1st entry some.bin (3), no match
2nd entry other.bin (4), no match
3rd entry file.bin (5), match, next char in path: end of string, file found 5 (inode, cluster etc.)

Are you by any chance Yashas/KernelX/...?

turdus wrote: Are you by any chance Yashas/KernelX/...?

I don't think he is, yashas always coded in c...