Sent: Feb 10, 2009 8:58 AM
To: [email protected]
Subject: [Wine] Is there a hope for Serv-u 7.0.4.1?
I tried several thing but on the end I get no results,
first as a normal user you cant do nothing in wine with the serv-u, second you need to be logged as >a root
Can you explain why you have to be logged in as root? Is there a specific error you receive while running this program that states you have to be root or is it that the program will not run unless you are an Administrator? The first is a Linux level admin, the second is the generic name for the Windows Administrator. If it is the second, this program will not successfully run under Wine. Running Wine as root is highly discouraged, but in some cases necessary.
, third, in winxp compatibility mode serv-u would just explode with the error:
fixme:system:SystemParametersInfoW Unimplemented action: 4132 (SPI_GETDROPSHADOW)
This is not an error condition, but rather functionality that does not currently exist in Wine.
But when I had set it to the win2k emulation I got some results:
And after I tried to make some changes, serv-u just get to the "coma state", I mean when it tried to save settings it just get in some sleeping state and I have no solutions after that, here is the picture:
Sent: Feb 10, 2009 8:58 AM
To: [email protected]
Subject: [Wine] Is there a hope for Serv-u 7.0.4.1?
I tried several thing but on the end I get no results,
first as a normal user you cant do nothing in wine with the serv-u, second you need to be logged as >a root
Can you explain why you have to be logged in as root? Is there a specific error you receive while running this program that states you have to be root or is it that the program will not run unless you are an Administrator? The first is a Linux level admin, the second is the generic name for the Windows Administrator. If it is the second, this program will not successfully run under Wine. Running Wine as root is highly discouraged, but in some cases necessary.
Follow the old thread. It needs to bind to a low port. Root is
required, unless POSIX permissions are used.
Sent: Feb 10, 2009 8:58 AM
To: [email protected]
Subject: [Wine] Is there a hope for Serv-u 7.0.4.1?
I tried several thing but on the end I get no results,
first as a normal user you cant do nothing in wine with the serv-u, second you need to be logged as >a root
Can you explain why you have to be logged in as root? Is there a specific error you receive >>while running this program that states you have to be root or is it that the program will not run
unless you are an Administrator? The first is a Linux level admin, the second is the generic name >>for the Windows Administrator. If it is the second, this program will not successfully run under >>Wine. Running Wine as root is highly discouraged, but in some cases necessary.
Follow the old thread. It needs to bind to a low port. Root is
required, unless POSIX permissions are used.
I hate programs that do that. Of course, this maybe to get around firewalls and proxies. Not good coding practices. Use of POSIX is one way around this. I'll look at the orginal thread on-line. Got a date range for it?
Sent: Feb 10, 2009 9:12 AM
To: James Mckenzie <[email protected]>
Cc: [email protected]
Subject: Re: [Wine] Is there a hope for Serv-u 7.0.4.1?
On Tue, Feb 10, 2009 at 10:07 AM, James Mckenzie
<[email protected]> wrote:
loopdemack <[email protected]>
Can you explain why you have to be logged in as root? Is there a specific error you receive >>while running this program that states you have to be root or is it that the program will not run
unless you are an Administrator? The first is a Linux level admin, the second is the generic name >>for the Windows Administrator. If it is the second, this program will not successfully run under >>Wine. Running Wine as root is highly discouraged, but in some cases necessary.
Follow the old thread. It needs to bind to a low port. Root is
required, unless POSIX permissions are used.
I hate programs that do that. Of course, this maybe to get around firewalls and proxies. Not good coding practices. Use of POSIX is one way around this. I'll look at the orginal thread on-line. Got a date range for it?
