Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!umich!samsung!aplcen!haven!decuac!shlump.nac.dec.com!shodha.dec.com!elvira!ridder
From: ridder@elvira.enet.dec.com (Hans Ridder)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Writing to WCS
Message-ID: <634@shodha.dec.com>
Date: 23 Jan 90 23:33:48 GMT
References: <90012003501244@masnet.uucp> <20011@watdragon.waterloo.edu> <629@shodha.dec.com> <20080@watdragon.waterloo.edu>
Sender: news@shodha.dec.com
Organization: Digital Equipment Corporation, Customer Support Center
Lines: 29

In article <20080@watdragon.waterloo.edu> mwandel@tiger.waterloo.edu (Markus Wandel) writes:

>Fine and good, except the official, supported way, won't leave the WCS
>enabled, which was the goal of the whole exercise.  Try it.  I did,
>just to make sure.

Of course you're right! (he says, whacking his forehead with the palm
of his hand) How embarassing....  Sorry I made the lame assumption
that the KickStart RAM would be left enabled.  I jumped to that
conclusion myself, it didn't say that in the hardware manual.

Thanks for clearing it up.

But your code brought up a question in my mind (such as it is :-).  Is
CNOP really a no-op?  (i.e. can it be executed without any side
effects?)  You used it inline, so I guess it is.  I have never seen
that done before.  Most of the code I have seen uses it to align
labels and such to longwords, etc.

I'm learning all the time....

>Markus Wandel
>mwandel@tiger.waterloo.edu

-hans
========================================================================
  Hans-Gabriel Ridder			Digital Equipment Corporation
  ridder@elvira.enet.dec.com		Customer Support Center
  ...decwrl!elvira.enet!ridder		Colorado Springs, CO