similar to: Wine with CIFS home directory

Dear useRs, by a circular diagram representation I mean what you will get by entering this at your R promt: pie(1:5) Nice to have R as a lingua franca :-) The folowing quote is from page 360 in this very interesting paper: @article{SpenceI2005, title = {No Humble Pie: The Origins and Usage of a Statistical Chart}, author = {Spence, I.}, journal = {Journal of Educational and

> Dear useRs, > > by a circular diagram representation I mean what you will get by entering > this at your R promt: > > pie(1:5) > > Nice to have R as a lingua franca :-) > > The folowing quote is from page 360 in this very interesting paper: > > @article{SpenceI2005, > title = {No Humble Pie: The Origins and Usage of a Statistical Chart}, >

wineprefixcreate does not create a working registry. The system had a working set of .wine .reg files however installs of office2k failed. I then saved .wine and rebuilt it with wineprefixcreate. After this the original applications did not work. Is wineprefixcreate supposed to succeed at this? Thanks - Dan

Alexandre says we should have users try wineprefixcreate before having them blow away their old .wine directory. ---------- Forwarded message ---------- From: Alexandre Julliard <julliard at winehq.org> Date: Mon, Mar 31, 2008 at 2:44 AM Subject: Re: Proposal: versioning .wine directory To: James Hawkins <truiken at gmail.com> Cc: Austin English <austinenglish at gmail.com>,

I understand that it is applied automatically when needed, but there are times when one would want to run it manually. An example is when I want to literally create a new wine prefix such as env WINEPREFIX="/home/bamm/apps/myprog" wineprefixcreate to prepare a clean profile for future installation of myprog. I know that running setup with a WINEPREFIX would create the clean profile,

Hi! I have difficulties using WineTools 2.1.0 with WINEPREFIX set. It does not matter whether use wineprefixcreate or not. I want to start a new wine-Konfiguration from scratch: export WINEPREFIX=$HOME/.wine wineprefixcreate (or not) wt > /tmp/Fehlermeldungen.wt 2>&1 When I try "Create a fake windows drive", WineTools doesn't create one although it said it did! I have

Hi, I've installed Wine version 20041201 on RedHat 9 and Winetools 210-jo, but when I try to execute Winetools (by typing wt2 on shell (as a user, not root), I just get all the error messages below. Any suggestions as to what I'm doing wrong, please? Best regards, Andy [andrew@Atlas2 andrew]$ wt2 bash: wt2: command not found [andrew@Atlas2 andrew]$ cd /usr/local/winetools [andrew@Atlas2

Does anyone have any idea what is causing wineprefixcreate to fail with these messages? output from running wineprefixcreate: wine: Unhandled page fault on write access to 0x003ffd80 at address 0x60a3d103 (thread 0009), starting debugger... wine: Unhandled page fault on write access to 0x003ffd80 at address 0x60a3d103 (thread 000b), starting debugger... err:seh:raise_exception

Hello Wine users, I've installed Wine 0.9.32 into an NFS-mounted dir on a RHEL 3 machine and it seems to work fine - I've even modified the /nfs_path/wine/bin/wineprefixcreate, so that an additional dir (c:/Perl) is created under ~/.wine for each user (by mere linking to /nfs_path/Perl) My problem is that currently each user of my Wine-installation has to run "wine regedit"

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 If I do: rm -r ~/.wine/ wineprefixcreate wine explorer /desktop=default,1200x900 winemine Then winemine opens in its own window. It does not open inside a fake desktop, which is what explorer /desktop is supposed to do. However, if I close winemine and run the same command again wine explorer /desktop=default,1200x900 winemine I get the correct

I've decided to try out some games with wine 1.1.4 to see if there is improvements (mainly with Bioshock) and, as always, I first created a prefix for those tests. My first surprise was this message : Code: Note: wineprefixcreate is deprecated and shouldn't be needed anymore. WINEPREFIX creation and updates now happen automatically when needed. So I said : "it's

Hi What is the general state of btrfs RAID6 as of kernel 3.13-rc1 and the latest btrfs tools? More specifically: - Is it able to correct errors during scrubs? - Is it able to transparently handle disk failures without downtime? - Is it possible to convert btrfs RAID10 to RAID6 without recreating the fs? - Is it possible to add/remove drives to a RAID6 array? Regards, Hans-Kristian -- To

When ~/.wine does not exist, or more specifically the system.reg does not yet exist, wineprefixcreate delivers the message "Failed to open the service control manager." I have tracked this down to the fact that HKLM\CurrentControlSet\Services does not yet exist when the msiexec.exe is registered and hence OpenSCManager fails. What is the proper way to register this key. In

By default Wine installs its fake-windows part into $HOME. I want rather have it on a separate partition, that I mount as /wine. How can I do this? What I have found was: http://wiki.jswindle.com/index.php/Advanced_Wine_User_Information#Changing_the_location_of_Wine.27s_installation My steps so far: - Installed Wine with Synaptic - # wineprefixcreate --prefix /wine - I find the fake directory

I'm not qualified to interpret the following messages I get when I do a wineprefixcreate from the console after an upgrade: preloader: Warning: failed to reserve range 00000000-60000000 preloader: Warning: failed to reserve range 00000000-60000000 err:dosmem:setup_dos_mem Cannot use first megabyte for DOS address space, please report preloader: Warning: failed to reserve range

This is on Fedora FC5 x86_64 rpm -q wine wine-0.9.14-1.fc5 winecfg wine: creating configuration directory '/home/nbecker/.wine'... X Error of failed request: GLXBadContext Major opcode of failed request: 143 (GLX) Minor opcode of failed request: 5 (X_GLXMakeCurrent) Serial number of failed request: 166 Current serial number in output stream: 166 wine: wineprefixcreate failed

I'm using a fresh install of Fedora Core 5 with the RPM install of Wine 0.9.12. When I run winecfg, it says "wine: creating configuration directory '/home/vince/.wine'..." as I expect it to. Following that is many lines of "Font metrics" progress with a few "fixme:font" messages. Nothing seems too unusual. But, when it gets to "Font metrics:

I'm having problems running a windows program (nulldc 1.0.3 but that's not important) under the latest version of wine, which is up and running (in 32 bit) on my 64-bit install of Fedora 14. I'm trying to compile a version of wine 1.1.32 under a separate prefix. I'm doing this in a way that has worked for me in the past under a 32-bit environment. As I say, I've compiled the

I have seen posts regarding WINEPREFIX so that Windows programs can be installed elsewhere than in the default .wine/drive_c/... folder. I have 2 or 3 Windows programs in the default folders which I run under Wine, and another program (Serif PagePlus 11) also in the default folder that does not run and I want to uninstall. Wine uninstall does not work for this program. I gather I can uninstall by

I have Wine wine-1.2.2 installed on mint 10 (extension of ubuntu 10~). I'm attempting to install ies4linux. I get the following error message """ our wine does not have wineprefixcreate installed. Maybe you are running an old Wine version. Try to update it to the latest version. """ I do believe that this is the latest version. But I cannot locate