On May 13, 2:47pm in "Re: HARD DRIVE FOR SAM", you warbled:
] LOAD ABS filename$ (or similar variants -- all ABS filename$ tho')
]
] These will take a filename *AS IS* and use *THAT* in the current
] path -- it won't try and switch directory or anything. Helps keep
] compatibility with many systems that way.
You what?
] > I take it that each directory entry won't take 256 bytes if it is
] going to > be MS-DOS compatible...
]
] Yup.
If it's going to MS-Dos contemtible, can we make it so that you don't _have_
to be restrained to a maximum of 10 characters per filename? And don't make
it so that everything is stored in CAPITALS either.
MSDos? Ewwwwww...
] > PS Remember, if there is ever a decent C compiler for the Sam or any of
] > these new machines, that there is a book on how to write a Unix clone,
] > complete with source code (it is, of course, the Minix operating system
] > by Andrew S. Tanenbaum).
I really would hate to type in all of the minix source... do you get it on
disk?
I think that if you're going to have a unix system you _have_ to have a decent
compiler. Maybe adapt gcc so it produces code output that's Hyperstone
compatible or something, then just compile gcc with itself...
] I'm still not sure about UNIX... Although apparently MAT of ESI was
] planning on writing a UNIX style OS for the SAM -- available on disk
] soon? :)
UNIX is a brill. idea for the Engram. For the S^2 or sam it would be a waste
of time. Maybe make the filesystem similar though, cos unix's file-handling
is lovely.
] Si
Geoff ([EMAIL PROTECTED] / [EMAIL PROTECTED] -- INET)
__ __ __ An expert is someone | _NOW_ I finally understand why
|\ /|| || ) ( _) who can read the system | John Smith's Bitter...
||\/|||--||-( _\\ manual pages faster | These opinions are my own. If
|| ||| || \(__/ than anyone else... | anyone agrees, more fool them.
