On Sat, Jan 15, 2000 at 04:40:07AM +0100, Andreas Beck wrote:
i didn't do the correct code:
if (ggiResourceMustAcquire(dbs[writeframe]-resource))
if (ggiResourceAcquire(dbs[writeframe]-resource,GGI_ACTYPE_WRITE)!=0)
instead i did:
if (ggiResourceMustAcquire(dbs[writeframe]))
On Sun, 16 Jan 2000, W.H.Scholten wrote:
Rubén wrote:
On 2000/Jan/13, W.H.Scholten wrote:
Well, not precompiled. What I mean is that it uses an abstracted system
of pcm/mixer/synth/cd in directly accessable libraries. Compile the
libraries for a new audio system and the server
On Sun, 16 Jan 2000, Erik Thiele wrote:
[clip]
is everything in ggi a void* ?
This is a valid point. We do that void * stuff on pupose to make sure users
don't try to dereference stuff they shouldn't (bypassing the encapsulation
rule and the access layers). However in cases like
On Sat, Jan 15, 2000 at 01:32:12PM -0800, Jon M. Taylor wrote:
I will be working on a jmt3 release this weekend, so if anyone out
there has outstanding patches and wants them merged into jmt3, get them to
my by midnight PST. Jos, I have your latest ViRGE patches which you
posted to
Andreas Beck [EMAIL PROTECTED] writes:
How about if we #ifdef around that code. Windows will be the only OS
which can use an environment variable. The others would still be hard
coded.
Could be done, but I don't really like special solutions ...
There has been a giiGetConfDir()
Jos Hulzink [EMAIL PROTECTED] writes:
Please find attached a new update for the ViRGE driver. It does not much,
in fact it tries to detect memory size and enables interrupts. but this
was a merely a test to see if communication with the chip works. Now I can
really start to work on the
Marcus Sundberg wrote:
Andreas Beck [EMAIL PROTECTED] writes:
How about if we #ifdef around that code. Windows will be the only OS
which can use an environment variable. The others would still be hard
coded.
Could be done, but I don't really like special solutions ...
On Sun, Jan 16, 2000 at 12:27:20PM -0500, John Fortin wrote:
The idea I had was that the location of the config dir should be
stored in the Registry and retrieved from there. The environment
variable is not good, as in NT you actually have some security
wrt file permissions. I don't know
teunis [EMAIL PROTECTED] writes:
Q: Got a driver/protocol/divisioning chart? Some kinda explanation to why
things are laid out the way they are and maybe what parts do what?
I keep thinking of doing something akin to Windows Media system / modular
with divisions of modules. (ie: use
On 16 Jan 2000, Marcus Sundberg wrote:
Jos Hulzink [EMAIL PROTECTED] writes:
Please find attached a new update for the ViRGE driver. It does not much,
in fact it tries to detect memory size and enables interrupts. but this
was a merely a test to see if communication with the chip
On Sun, Jan 16, 2000 at 12:51:40PM -0500, John Fortin wrote:
If at all possible, it'd be nice if a user that hasn't got write
access to C: or to the system part of the registry can install
libggi (possibly by putting a config file in the same folder as libggi
or something).
If
John Fortin [EMAIL PROTECTED] writes:
If at all possible, it'd be nice if a user that hasn't got write
access to C: or to the system part of the registry can install
libggi (possibly by putting a config file in the same folder as libggi
or something).
If I go with a registry
If at all possible, it'd be nice if a user that hasn't got write
access to C: or to the system part of the registry can install
libggi (possibly by putting a config file in the same folder as libggi
or something).
If I go with a registry solution, which seems likely, I doubt I'll
On Sun, 16 Jan 2000, Christoph Egger wrote:
I agree. I'm subscribed to both lists too, and I don't like it, when I get
the same post twice times...
A procmail filter prevents that, but the point is clear now. Only wonder
why I didn't get complaints when sending KGICON patches...
Jos
Actually the whole point would be to have the registry entry in
the system section so random users can't tamper with it. However,
installing LibGGI as a user must also be supported, so I'd suggest
we have it in the user section for now. Then if we find a reason to
do something more secure we
Actually the whole point would be to have the registry entry in
the system section so random users can't tamper with it. However,
installing LibGGI as a user must also be supported, so I'd suggest
we have it in the user section for now. Then if we find a reason to
do something more secure we
16 matches
Mail list logo
