From:	"Jeremy \"Bolthy\" Zimmerman" <jeremy@***********.COM>
Subject:	Re: ASIST assistance?
Date:	Mon, 4 May 1998 14:36:36 -0700

----------
> From: Brett Borger <bxb121@***.EDU>
> To: SHADOWRN@********.ITRIBE.NET
> Subject: Re: ASIST assistance?
> Date: Monday, May 04, 1998 2:09 AM
>
> Anyway, I agree with the rest of your argument...mostly. ASSIST
> translates "brain-code" into "compuspeak". What is the
equivilent on
> modern computers? Well, using the printer analogy, is the brain the
> primary or the periphiral? Let's say it's the peripheral (since
> we've all agreed that it is I/O).
>
> Modern: Type instructions into keyboard. Keyboard BIOS handles any
> interrupts and passes signals to OS, which translates into CPU
> commands.
>
> SR (Hot deck): Think instruction. ASSIST picks up and translates
> into MPCP commands.
>
> Thus, in this example, ASSIST does seem to be acting as OS as well as
> BIOS. (at least keyboard bios). But let's check output to be sure:
>

The flaw I'm seeing in this is that while ASIST does communicate various
commands to the the MPCP from the user's POV, there are things an OS does
that ASIST doesn't. Like memory allocation and management. The
"Artificial Sensory Induction System", but it's very name, is not likely to
do that sort of thing.

> Modern: CPU performs instruction set, which modifies video memory.
> This, in turn, is periodically scanned by the video BIOS (well,
> there's some sort of firmware driver on a video card) and translated
> into commands for an "electron gun", which in turn creates the
> picture.
>
> SR (hot Deck): MPCP performs instruction set (including any
> interaction with another system on the Matrix), and returns commands,
> which are picked up by ASSIST and translated into brain speak.
>
> So in this case the OS isn't really involved. (Although I have no
> doubt I missing something...Linix wouldn't burn out monitors this
> way...anyone want to help me out?)
>

That sounds fine as far as I know...

> Here's a thought though: Why would a deck have an OS? When you
> think about it, chips already ARE OS's, just minimally functional
> ones. Enough assembler classes have told me that the 68xxx series is
> quite different from Intel chips. All OS's on top of this are simply
> interfaces...ASSIST removes the need for that interface. Thus,
> ASSIST isn't really the OS...because there isn't one.
>
> A Turtle deck, however, would have to have BIOS and OS added.
> hmmm...
>


You're talking about the differences between machine code and the fluffy
interface that you get with MacOS and Win95, if I'm correct? Dunno... I
haven't taken that many in depth computer courses. I do know that there's
an OS on the MPCP, just because the BBB says there is. What use the deck
is in that situation is beyond me. But that's what it says. I suppose it
has to be able to manage the the allocation of active memory and storage
memory. I do like to think of it in the following terms, though.

If I disconnect my monitor, my mouse, and/or my keyboard, my computer will
still work. The usability is a little hindered, but the computer will
continue to function just splendidly nonetheless. I have had to do stuff
with one of those three missing, so it is possible. Just bloody difficult.

If I cripple Windows 95 and reboot, my computer has the ability to run
BIOS, and then promptly sit on it's hands and do nothing. It doesn't work.

If I turn off my simsense rig, aka my Artificial Sensory Induction System,
aka my ASIST, according to VR2.0, I now have a turtle or tortoise, or
whatever you want to call it. The OS is in the MPCP, so I don't need to
worry about it. Take out the MPCP, and I'd be screwed, but I can use my
deck without the ASIST interface provided I have an alternative I/O
resource available. I'd have to dig my keyboard and monitor out of storage
and deck like that, but it is still possible.