abrams@convent.cs.columbia.edu (Steven Abrams) (09/27/89)
*-*-*-*-*-*-*-*-*-*-*-*-* *-*-*-NOVICE ALERT*-*-*-* *-*-*-*-*-*-*-*-*-*-*-*-* I'm attempting to build a minix system for the PS/2 model 70 using a bunch of source sent to a professor here (duchamp@cs.columbia.edu) from ast. To begin with, I don't have a minix platform to build on; I'm compiling on my AT clone using Turbo-C & Assembler. The C code is compiling fine, and I'm using library, tools, and commands files from an original unadulterated 1.3 P-H distribution. There are definate problems using the .s files, as they are not even remotely of the format that TASM, in any of its modes, can understand. I've been able to xlate most of it, but still have a few hitches. My questions are: 1) What memory model should I be using? Does it matter, as long as I am consistent? 2) What does the .byte directive do in the .s files? I believe that it instructs the assembler to output at that point in the file the exact byte that follows. This is, apparently a 286 instruction that the assembler that ast uses doesn't know how to handle. Is this correct? If so, how can I mimic this behavior in TASM? 3) How can I use the build command from DOS, since it expects a /dev/fd0 type device driver -- there's no such thing under DOS. 4) Ditto for mkfs!!?! I'm sure these questions have all been answered a million times before, but forgive me, I'm just a T.A. trying to impress a professor. Anyone with any info can e-mail me abrams@cs.columbia.edu or post to this group. ~~~Steve -- /************************************************* * *Steven Abrams abrams@cs.columbia.edu * **************************************************/ #include <std/dumquote.h> #include <std/disclaimer.h>