search for: hypotetical

hi there. I hope this is the right place for asking this. After reading through the information about WINEPREFIX in the FAQ and the User Manual, I've still got some questions left: I (hypotetically) want to create a new clean wine-environment, install the winetricks d3dx9 package into it, and then run three applications in it. Would the following commands be the right way to do it? Code: WINEPREFIX=$HOME/.new_wine winetricks d3dx9 wine app1.exe wine app2.exe wine app3.exe Or do I need...

Hi everyone, I don't if this post belong to wine-devel or the forum so I'm putting it here now and in case I'm wrong I'll post to wine-devel. I try to retrieve Dungeon Keeper 2 resources (meshes, textures, sound etc.) in order to create an hypotetical clone of this game :D. Since I'm not a pro in hacking compression algorithm I didn't try to understand the DKII propretary image format, so I think I'd rather use wine to intercept DirectX Texture calls and save the textures. I just took a code that save a DirectDrawSurface (the game...

Here is what I imagined (just vague thoughts, nothing polished): Let's suppose we have a hypotetical library called "Free Universal Codec Kit" - ..um...well.. Frunick for short :) (Of course I am not proposing this name, I'm sure the suits in the industry would not like it...but for my example its OK ;) Now, an application should do something like this: #include <frunick.h>...

Here is what I imagined (just vague thoughts, nothing polished): Let's suppose we have a hypotetical library called "Free Universal Codec Kit" - ..um...well.. Frunick for short :) (Of course I am not proposing this name, I'm sure the suits in the industry would not like it...but for my example its OK ;) Now, an application should do something like this: #include <frunick.h>...

That's what UCI is trying to do. I'm hoping for just a simple unified Ogg interface for the audio codecs that Ogg supports. -dwh- On 31 Jan 2003, Csillag Krist?f wrote: > Here is what I imagined (just vague thoughts, nothing polished): > > Let's suppose we have a hypotetical library called > "Free Universal Codec Kit" - ..um...well.. Frunick for short :) > > (Of course I am not proposing this name, I'm sure the suits in the > industry would not like it...but for my example its OK ;) > > Now, an application should do something like this...

...d mail----- From: Csillag Kristóf <fenwick@freemail.hu> To: vorvis-dev@xiph.org, speex-dev@xiph.org, flac-dev@lists.sourceforge.net Subject: Unified codec interface Date: 31 Jan 2003 00:21:35 +0100 Here is what I imagined (just vague thoughts, nothing polished): Let's suppose we have a hypotetical library called "Free Universal Codec Kit" - ..um...well.. Frunick for short :) (Of course I am not proposing this name, I'm sure the suits in the industry would not like it...but for my example its OK ;) Now, an application should do something like this: #include <frunick.h>...

Hi, In the initial thread of the proposal for GlobalISel, I have mentioned that it may be interesting to have a kind of MachineModulePass. Marcello mentioned this would be useful for their current pipeline. I am interested in knowing: 1. If anyone else is interested for such concept? 2. What kind of information should we make accessible in an hypothetical MachineModule? I.e., how do you plan to

On Thu, 2007-07-19 at 23:13 +0300, S.?a?lar Onur wrote: > Hi; > > Remove -static from Documentation/lguest/Makefile, most distros only provides shared library form of zlib in their default installation. > And shared linking also provides litte tiny security for hypotetical security problems will be introduced by zlib :). Unfortunately, this introduces a security hole. See, the guest can access all memory up to LGUEST_GUEST_TOP, or 0xB8000000 on my machine. Without -static, we look like this: > cat /proc/4137/maps b7e0b000-b7e0d000 rw-p b7e0b000 00:00 0 b7e0d...

On Thu, 2007-07-19 at 23:13 +0300, S.?a?lar Onur wrote: > Hi; > > Remove -static from Documentation/lguest/Makefile, most distros only provides shared library form of zlib in their default installation. > And shared linking also provides litte tiny security for hypotetical security problems will be introduced by zlib :). Unfortunately, this introduces a security hole. See, the guest can access all memory up to LGUEST_GUEST_TOP, or 0xB8000000 on my machine. Without -static, we look like this: > cat /proc/4137/maps b7e0b000-b7e0d000 rw-p b7e0b000 00:00 0 b7e0d...