similar to: Re: newbie question: why do I see root directory in wine, when n

Csillag Kristof wrote: > > > > > No "Z:" under Drives tab in winecfg? > > > Precisely. > > I intentionally deleted it, so that wine processes can not access the > stuff of other users. > If you've removed the Z: drive then Wine won't be able to open, save, or execute files in those directories, but there's no way to stop it from

Hi, This might be a stupid question; I checked the FAQ, but could not find a solution. In Wine Config, I have only two drives configured: C: is ~/.wine/drive_c D: is ~ Still, when I run winefile (or any other wine app), besides drives "C" and "D", there is a "/" drive, which is the root directory of my real file system. Why is it still there, even if I

dimesio wrote: > I think it's more a matter of not hiding them. As to whether there are reasons they can't be hidden or it's simply a matter of no one thinking it's important enough to submit a patch for it, that I don't know. It was decided that *NIX root shell view should show all directories and files accessible to user. This makes it simpler and closer to other native

a separate partition Reply-To: Csillag Kristof <kristof.csillag@ge.com>, 397758@bugs.debian.org Resent-From: Csillag Kristof <kristof.csillag@ge.com> Resent-To: debian-bugs-dist@lists.debian.org Resent-CC: Debian Xen Team <pkg-xen-devel@lists.alioth.debian.org> Resent-Date: Thu, 09 Nov 2006 09:33:19 +0000 Resent-Message-ID: <handler.397758.B.11630647553439@bugs.debian.org>

Processing commands for control at bugs.debian.org: > close 536176 3.3.1-2 Bug#536176: xen-utils-3.4: trying xen-3.4 once breaks xen-3.2 (?) 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug#536806: xen-utils-common - xend start fails Bug#538766: xen-utils-common: fail to start xend Bug marked as fixed in version 3.3.1-2, send any further explanations to

Hi, I have read your message about building a VirtualGL server in a xen domU at http://www.mail-archive.com/virtualgl-users@lists.sourceforge.net/msg00088.html . I plan to do exactly the same. Could you please share some of your experience? What HW have you chosen? Have you succeeded? According to the information at http://wiki.xensource.com/xenwiki/XenVGAPassthroughTestedAdapters ,

Hi all, I would like to get my system to work with IOMMU. (The long-term goal is VGA passthru.) System is as follows: CPU: Core 2 Duo E6600 MB: Foxconn G9657MA-8EKRS2H (w. latest bios: 631F1P61) Virtualization support is enabled in BIOS. (These is only one option.) Hypervisor: xen 4.0.0 from Debian, AMD64 Xen config: iommu=verbose output of xen dmesg is attached. HVM domains work (lasd tried

Hi, As it has been brought to my attention (by several parties), my current MB does not support VT-d. Since I don''t feel like purchasing a brand new system, I have searched for replacement MB-s that would fit into my existing uATX case, support my C2D CPU, and support at least 4x2GB ram. I have narrowed it down to the following four models: SUPERMICRO MBD-C2SBM-Q-O (Q35 chipset)

Hi there! My problem is the following: I am experimenting with virtualization with XEN. I am running WinXP in a HVM host with a Debian Gnu/Linux (Etch) dom0. I am also using audio emulation (sb16). This way, sounds from WinXP work fine. And here comes the problem: The HVM guest completely reserves the audio device; other software can not use it. (mplayer says this: alsa-init: using ALSA

> On Feb 27, 2017, at 1:36 AM, Kristof Beyls via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hi Mikael, > > Some noisiness in benchmark results is expected, but the numbers you see seem to be higher than I'd expect. > A number of tricks people use to get lower noise results are (with the lnt runtest nt command line options to enable it between brackets): > *

Hi all, I am running a VNC terminal server on a virtualized host, and I would like to add OpenGL support using VirtualGL, which relies on HW accelerated rendering on the server side. Since in my case the server is a domU, I need VGA Passthru for this. Therefore, I need a graphics card that supports virtualization. I am aware that the NVIdia Quadro FX 3800 card (and up) are guaranteed to work,

Two other things: 1) I get massively more stable execution times on 16.04 than on 14.04 on both x86 and ARM because 16.04 does far fewer gratuitous moves from one core to another, even without explicit pinning. 2) turn off ASLR: "echo 0 > /proc/sys/kernel/randomize_va_space". As well as getting stable addresses for debugging repeatability, it also stabilizes execution time

Hi, Could someone please explain me what is the current status of the jack audio back-end? (Both midi and audio.) The feature to switch back-end seems to have disappeared from winecfg, and I can't find anything useful in the docs either. Thank you for your help: Kristof

Hi Tobias, The metrics that you can collect in LNT are fixed per "test suite". There are 2 such "test suite"s defined in LNT at the moment: nts and compile. For more details on this, see http://llvm.org/docs/lnt/concepts.html#test-suites. AFAIK, If you need to collect different metrics, you'll need to define a new "test suite". I'm afraid I don't really

I'm new to wine; I'm having trouble running this game, which has been reported to work previously, in the test result http://appdb.winehq.org/objectManager.php?sClass=version&iId=4050, with wine 0.9.24 under Ubuntu 6.10 "Edgy". I'm running Debian lenny which has wine-0.9.44. Now I'm enough of a newbie with wine that I presume I'm using wine improperly (but not

> On Jul 4, 2017, at 2:02 AM, Tobias Grosser <tobias.grosser at inf.ethz.ch> wrote: > >> On Tue, Jul 4, 2017, at 09:48 AM, Kristof Beyls wrote: >> Hi Tobias, >> >> The metrics that you can collect in LNT are fixed per "test suite". >> There are 2 such "test suite"s defined in LNT at the moment: nts and >> compile. >> For

Hi, There was a new Python setuptools release (36.0.0) today, that caused this compatibility issue. The suggestion to stop breaking the builds is to add a static setuptools version on lnt's requirements.client.txt. The latest known compatible version is 35.0.2. I have tested it building a LNT sandbox and it seems to works. setuptools==35.0.2 I'll create a bug on LNT so we can

So, in the end looks like this setuptools 36 was deleted from pypi. There is an issue [1] open on setuptools. I can confirm by trying to force to install this version: $ pip install setuptools==36.0.0 Collecting setuptools==36.0.0 Could not find a version that satisfies the requirement setuptools==36.0.0 (from versions:<many version numbers>) No matching distribution found for

Hi, I'd like to accomplish te following but can't seem to find how: Share1 subdir1 subdir2 Share 1 that is connected by our Windows clients, should NOT be writable directly. This means, nobody (except a specified group/user?) should be able to create a top-level folder or file in this share. Write and execute rights through the subdir1 and subdir2 should however be left alone and

I'm new to the list and to Wine. I loaded wine wine-0.9.7-i486-S10.2 into Slackware 10.1 in order to run the Forte Agent newsreader. It was setup and running under Win4lin which I have discontinued. What would be the syntax to load Forte Agent and specify the old "start-in" directory used under Win4lin? wine ./agent something_for_start-in_directory ?? Does Wine have the