TM>Oh no, Vengeance is too ELITE to read an informative and interesting
 TM>echo like this one :) He calls OVERSEAS boards, so he's much too cool
 TM>to call local.
 
  Actually I think ages ago he did pop in to 64talk every now &
then, but I'm not sure. But he's so elite now (-:

 >  After all, we all know that -I- am the best!  (-:
 TM>Look, I think we all know by now... **I** am the only REAL
 TM>scener/coder/ musician... hey and even graphitician in the whole of the
 TM>southern hemisphere! Everyone else is just clawing off of my fame in air> Everybody is LAME except me. Period. 
 
 You? Yeah right! You absolutely pale in comparison to my god-like grip on
all aspects of the 64 scene! Bow at my feet! You are lower than lame to me!
HAHAHAHAHA....

  

 Ah, that's better. Almost turned into a veangance.. (-:

 TM>Hmm I usually use closed routines, and use the freeze on the AR to
 TM>change things, that way there's no clashing. I guess as you used to
 TM>code in the AR monitor exclusively you're used to editing as you go in
 TM>it too. :) I haven't had any problems with the ROM at $8000.. ? (except
 TM>when I had to switch off the fast-loader, and tried to save data from
 TM>under $8000.. always got the fastload ROM)

 Not so easy with NMI's. The AR usually locks up when I freeze while a
sample is playing. Well it is fine until I try to restart, when it just
cant handle it.. (:
 The problems with AR related distortion when playing samples is probably
due to my changing $01 every time I read a sample (so I can read them from
under the roms). It only happens in basic under fastload though, so it is
not a problem inside a demo etc.

later, Strobe/Menace

--- Ezycom V1.10b3 00f90038