Hello,
I am trying to get a third-party (non-MS) software installed under wine (it also requires dotnet 35 or 40). MySystem: FreeBSD.9.2_amd64_wine-1.7.0,1_winetricks-20130707. Wine-XP + dotnet35sp1 + msxml3.
In FreeBSD 64bit wine does not exist, so my wine is 32bit. The only solution I can think of is to isolate the error messages 1-at-a-time and solve them in each step.
Q1: If I should need to post full debug output, should I do it in this thread or new topic under Bugzilla? The immediate problem seems to be related to this message:
* System.Configuration.ConfigurationErrorsException: Error creating the Web Proxy specified in the 'system.net/defaultProxy' configuration section. ---> System.Net.Sockets.SocketException: Unknown error (0x273d)
* And elsewhere: fixme:ras:RasEnumConnectionsW RAS support is not implemented! Configure program to use LAN connection/winsock instead!
I had read in one of the wine-forum threads that the RAS-error message could be ignored and is not critical (?). I have samba4 installed on the system but not running as I am unsure how to properly configure it for the requirements of this software. Is there an easier method other than samba (an MS module perhaps)? How can I tell if samba/winsock is even needed? What is the advised solution to the "web proxy" error?
Q2: Which venue will get faster answers and broader coverage of issues: This forum or the wine-users mail list (http://www.winehq.org/mailman/listinfo/wine-users)?
Thanks.
wine32bit + dotnet35 on FreeBSD: Non-MS app does not install
-
Beeblebrox
- Newbie
- Posts: 1
- Joined: Fri Aug 16, 2013 1:47 am
Re: wine32bit + dotnet35 on FreeBSD: Non-MS app does not ins
Bugzilla is for reporting bugs, the forum is for user support. Before filing a new bug, please search bugzilla to make sure one does not already exist for your problem. If you do file a bug, attach the full output to it as a plain text file.
Here, if the log is not too long, just paste it in the body of your post. Otherwise, attach it as a text file (don't give it a .txt extension; the forum software will reject it).
The users' mailing list has much less traffic, but some very experienced users who don't check the forum. I'd post there, too. You can also ask on IRC.
Here, if the log is not too long, just paste it in the body of your post. Otherwise, attach it as a text file (don't give it a .txt extension; the forum software will reject it).
The users' mailing list has much less traffic, but some very experienced users who don't check the forum. I'd post there, too. You can also ask on IRC.
