iS-DOS — using a hard drive without an operating system

NemoFAQ #03

1. Please send me a catalog!

Fragment 1/2.

  1. Please send me a catalog!
  2. Is there a driver for working with an HD without ISDOS, or, even better, some software?

6300107 07.06.99


Dear N!

Regarding point 2: Point 2 is worded ambiguously.

The driver is supplied as part of the system, together with ISDOS. The driver by itself is pointless, since you can't use the volumes of information normally stored on a hard drive without an OS. (Unless, of course, you use the hard drive as a streamer or a “disk box” (for archiving).)

If what you mean is that you already have an OS, that’s a misconception too. ISDOS has undergone major changes over the last year or two, so the most sensible thing would be to buy the new version.

There is no software for working with a hard drive apart from operating systems. A hard drive without an OS is just a piece of hardware, even if you have drivers. It will be just as much a piece of hardware if the user doesn’t know how to use the OS. That’s not so terrible, since you can learn. The difficulty is that users tend to neglect this process and avoid it by every means possible. It’s difficult because working under an OS requires a somewhat different way of looking at and perceiving the system. It means changes in your brain. They’re very difficult, because you have to change familiar habits of thought. An OS is the meta-level of the software environment, since it performs operations on files at a formal level. It’s the environment in which files “live.” The OS structures them in a particular way and makes them operable. Just as the processor works with memory cells, the OS works with files. There’s a whole class of tasks for which having this meta-level is strictly necessary. If you don’t have any such tasks, then you don’t need a hard drive either—it’s easier to make do with TRDOS and floppies.

In fact, you can use an OS in the most primitive way—as a fast file loader. This is done in the KAY-1024 with the help of the “electronic C: drive.” It works as follows:

First, the OS is loaded. The structure needed for working with files—the meta-level—is created, then a TR-DOS-type file (“blank”) is loaded. After that, the structure is destroyed, the meta-level disappears, the system “climbs” back onto the hard drive (like a genie into a bottle), and control is handed over to TR-DOS.

Note that at the moment of loading, it is the OS that is running, with all its bells and whistles. If this process is written into the startup procedure, you might not even suspect that an OS exists (the autoexec file). You simply hit Reset and land on your favorite TRDOS disk. This is also how you can load the MMD BBS program, by the way. From ISDOS’s point of view, it’s just a “blank” of the .trd type, and keeping it on the hard drive is no trouble at all.

In principle, you can build your own OS starting from the drivers (and that’s exactly what the task would turn out to be). But you’d have to spend a monstrous amount of time and end up with a buggy product. What’s more, it wouldn’t be compatible with anything. In reality, though, it’s all relative. You can screw a car onto a nut, or a nut onto a car. The latter makes more sense.

(c) Nemo 07.06.99


° ° °

╔═════════════════════════════════════════════════════════════╗
║    Text typed from "real" letters at the firm (c)Nemo       ║
║                                                             ║
║              Technical editor - OPER.                       ║
║                                                             ║
║                    St. Petersburg-Moscow                    ║
║                         1999                                ║
╚═════════════════════════════════════════════════════════════╝

Share your thoughts about the article