create_child.c

[Andrew Czisny]

Anyone have any luck getting this to work as is? Any time I tried to
run it with such a long name bochs wouldn't run it. It didn't recognize
that an .exe extension was appended to it. When I shortened the name to
just create it ran fine in bochs. Any suggestions?

[Michail Turovskiy]

Yup, same here. I think the problem is with geekOS not liking long
program names. When it links in the executibles when you compile it,
create_child.c is called create_child, NOT create_child.exe as all the
other user programs.

You can still run it as-is by typing: "/c/create_child" however.


m.t.

Post by Andrew Czisny
Anyone have any luck getting this to work as is? Any time I tried to
run it with such a long name bochs wouldn't run it. It didn't recognize
that an .exe extension was appended to it. When I shortened the name to
just create it ran fine in bochs. Any suggestions?

[Iulian Neamtiu]

Yes, file names are limited to 12 characters, because /c/ is a FAT
filesystem which only allows 8 characters for filename, one for '.' and
3 for extension, hence 8+1+3=12.

This is a known limitation, don't worry about it.
Iulian

Post by Michail Turovskiy
Yup, same here. I think the problem is with geekOS not liking long
program names. When it links in the executibles when you compile it,
create_child.c is called create_child, NOT create_child.exe as all the
other user programs.
You can still run it as-is by typing: "/c/create_child" however.
m.t.

Post by Andrew Czisny
Anyone have any luck getting this to work as is? Any time I tried to
run it with such a long name bochs wouldn't run it. It didn't
recognize that an .exe extension was appended to it. When I shortened
the name to just create it ran fine in bochs. Any suggestions?