When a user attempts to use the type command on a file that does not exist, a strange behavior crops up that shows no prompt for the user, but upon pressing return the invalid command message appears and use can continue as normal. After this happens, any subsequent type command ceases to function correctly and will exhibit this behavior. The problem exists on Bochs, Virtualbox, and all hardware I have tested thus far, leading to the conclusion that something in NOS is at fault. It sounds like a memory/stack tracking problem to me. Will continue testing to find the root of the problem.
When a user attempts to use the type command on a file that does not exist, a strange behavior crops up that shows no prompt for the user, but upon pressing return the invalid command message appears and use can continue as normal. After this happens, any subsequent type command ceases to function correctly and will exhibit this behavior. The problem exists on Bochs, Virtualbox, and all hardware I have tested thus far, leading to the conclusion that something in NOS is at fault. It sounds like a memory/stack tracking problem to me. Will continue testing to find the root of the problem.