similar to: wineprefixcreate fails relating GLX

Running wine 0.9.28, Ubuntu Edgy. nvidia 6800GT, dual-LCD w/ xinerama, nv-glx driver. Running winecfg always returns: wine: creating configuration directory '/home/myusername/.wine'... X Error of failed request: BadWindow (invalid Window parameter) Major opcode of failed request: 144 (NV-GLX) Minor opcode of failed request: 4 () Resource id in failed request: 0x24a Serial

Hello, after a fresh install on and amd64, nvidia, linux 2.6.16, i get this error after starting wine: bowman@discovery ~ $ winecfg wine: creating configuration directory '/home/bowman/.wine'... X Error of failed request: BadAlloc (insufficient resources for operation) Major opcode of failed request: 144 (GLX) Minor opcode of failed request: 3 (X_GLXCreateContext) Serial number

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 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

Hello, I'm trying to use wine 0.9.8 on netbsd current. I have seen that several personnes asked the question on this list, but none get a clear answer : Winecfg hangs (and no window open on X-window) after printing : wine: creating configuration directory '/homes/damien/.wine'... fixme:ntdll:FILE_GetDeviceInfo device info not properly supported on this platform I can stop winecfg

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,

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

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

Hi everybody! About the email bellow, I just want to add one thing. I noticed that wineprefixcreate does not create some folder it used to. For instance it does not make Program Files anymore? Is this normal? It seems a change to me. One more thing: some programs work when I call them with wine-kthread, but never when I use wine-pthread. Again: any hints? Thanks -------------------------------

try. wine --version retarn error wine: wineprefixcreate failed while creating '/home/paul/.wine' What I need do. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.winehq.org/pipermail/wine-users/attachments/20050728/6fe497db/attachment.htm

Hello Mike, I saw a posting from 2002 where you were asking about running Windows programs on top of WINE that would talk to GPIB devices. Did you ever get that working? I'm looking at some HTBasic code which has it's own drivers to talk go the GPIB card. They seem to be drivers that speak directly to the memory registers of the card. I would hope that this sort of communications

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

Tim Johnson wrote: > I have Wine wine-1.2.2 installed on mint 10 (extension of ubuntu > 10~). > I'm attempting to install ies4linux. > IEs4Linux is not supported here. If you need real IE, use winetricks to install it.

Winetricks is not a part of Wine, but it is supported here as it's an official side project and its creator is on the forums/mailing list. Winetricks is available from the Wine Wiki (see links at top of page) ( http://wiki.winehq.org/winetricks ). Just run winetricks by itself and navigate the menus, or type winetricks ie6 in a terminal to install Internet Explorer.

Tim Johnson wrote: > * DaVince <wineforum-user at winehq.org> [110301 16:34]: > > > Winetricks is not a part of Wine, but it is supported here as it's an official side project and its creator is on the forums/mailing list. > > > > > > Winetricks is available from the Wine Wiki (see links at top of > > page) ( http://wiki.winehq.org/winetricks ).

I get back from two weeks on the road, and try to VNC to my server and it fails. I ssh in and see that, yes vncserver is dead. I tried restarting it and see below for the failure messages plus my systemd setup. Can someone point me to trouble shooting why it says about resources (if that is the problem); # systemctl -l status vncserver@:3.service ? vncserver@:3.service - Remote desktop

I got vncserver working per: https://www.tecmint.com/install-and-configure-vnc-server-in-centos-7/ Then I went to set up a second instance, and have that for logging on to root: ========== cp /lib/systemd/system/vncserver at .service /etc/systemd/system/vncserver@:2.service vi /etc/systemd/system/vncserver@\:2.service replace <USER> with root systemctl daemon-reload systemctl start

Actually it is running: netstat -tuln | grep 590 tcp 0 0 0.0.0.0:5901 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:5902 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:5903 0.0.0.0:* LISTEN tcp6 0 0 :::5901 :::* LISTEN tcp6 0 0 :::5902 :::* LISTEN tcp6 0 0 :::5903 :::* LISTEN

OK, first time configuring vncserver on Centos7. I have read through a bunch of old messages here on vncserver and thought I had it. Obviously not. 1) cp /usr/lib/systemd/system/vncserver at .service /etc/systemd/system/vncserver at .service 2) vi /etc/systemd/system/vncserver at .service I changed <USER> in both places to root 3) systemctl daemon-reload 4) systemctl