Path: chuka.playstation.co.uk!scea!greg_labrec@interactive.sony.com
From: Mark Jawad <jawad@uiuc.edu>
Newsgroups: scea.yaroze.programming.sound
Subject: Re: modifying a looping buffer
Date: Sun, 18 Jan 1998 03:28:27 -0600
Organization: Student at the University Of Illinois
Lines: 24
Message-ID: <34C1CB3B.72C3@uiuc.edu>
References: <3481DE9D.1E06@worldaccess.nl> <34BA8526.42E0@playstation.sony.com>
Reply-To: jawad@uiuc.edu
NNTP-Posting-Host: archbald-83.slip.uiuc.edu
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 2.02 (OS/2; I)

Rob Vawter wrote:
> 
> Perhaps using the siocons commands, but not with the Yaroze libraries.
>

I have a question somewhat related to this: I've looked at the source
for
SIOCONS, and realized that commands like WAR / WAW are actually located
within the DTLH program on the Yaroze side. Now, I've a feeling that
this
program is in the the area somewhere below 0x80090000 (well,
0x00090000), because when I quit any Yaroze program w/o the boot CD in
the drive, the 
Yaroze console pops up without a complaint. SO .. If the DTLH console is
stashed somewhere in the kernel area, then the WAR / WAW functions must
be in there somewhere also, right?

So why is it that we're not able to link them into our programs? Heck, 
If we were given the relative address of the function, and the
parameters
that is needs to have on the stack, we could easily write a wrapper
function to call them. What's the deal?

-Mark J., who would really like to bang on the sound hardware....