Re: [Wrapper-user] Problems with 3.5.7 under Windows XP

[Christian M. <chr...@ta...>]

Karel,

I'm very sorry for the delay. Japan was out on a long weekend and I
couldn't check my mails on a regular basis.

I'm also using a Win XP SP2, but not having the issue. I tried this
morning various things to things in order to reproduce the situation,
however no avail. Also installing the Wrapper 3.5.6 and
starting/stopping/removing with 3.5.7 and vice versa did work as
expected. So I'm not really sure on what's the cause for this for your
customer.
The cmd you and your customer were seeing this is a administrator cmd?

Also, when you were seeing ...well... nothing, did you just get back
to the prompt instantaneously or after a short time or was it
blocking? If blocking, what did you do then?
Was something written into the log file? If yes, could you send me the output?

Best Regards,
Christian

On Thu, Feb 10, 2011 at 10:31 PM, Karel Vervaeke <ka...@ou...> wrote:
> Hm, a customer is having the same problem, using a non-emulated
> machine running Win XP SP2.
> They don't have a lingering wrapper.exe (and there is no write lock on
> the log files). The testwrapper works
> I'm trying to find more details which could cause the difference, but
> it may take a while. In the mean time they will use 3.5.6.
>
> Regards,
> Karel
>
> On Tue, Feb 8, 2011 at 5:42 PM, Karel Vervaeke <ka...@ou...> wrote:
>> The test wrapper sample commands (-i, -r, -t ... ) seem to work, both
>> with absolute and with relative paths.
>>
>> I found the problem, but can't reproduce it anymore:
>>
>> I wanted to delete the log files (to make sure I was looking at the right one),
>> but I couldn't - they were still in use by a process. Checking the
>> task manager I found that there actually was a wrapper process
>> running. After killing that
>> I could delete the files AND the 3.5.7 wrapper started working again.
>>
>> I don't know where that that running wrapper.exe process came from.
>> It's possible that this was still lingering from before the upgrade
>> (i.e. a 3.3.6 wrapper.exe), so that would be a border case not worth
>> further investigation.
>>
>> Thanks for the quick reply,
>> Karel
>>
>> On Tue, Feb 8, 2011 at 4:25 PM, Christian Mueller
>> <chr...@ta...> wrote:
>>> Karel,
>>>
>>> Thank you for your mail.
>>>
>>> I have tested the Wrapper on any supported Windows platform (2K, 2K3, XP,
>>> Vista, 7, 2K8) prior to the release of 3.5.7 and all tests there went
>>> successful.
>>> I'm not sure so what could cause this. Actually the UAC part of the code
>>> won't get called until the distribution appears to be Vista or later.
>>>
>>> When you run wrapper.exe -i ..\conf\wrapper.conf you said you don't get any
>>> output on your cmd. Can you check the log file if anything was written in
>>> there?
>>>
>>> I haven't tried virtualbox yet, but will also check on this in order to
>>> narrow it down.
>>>
>>> Best Regards,
>>> Christian
>>>
>>>
>>> On Tue, Feb 8, 2011 at 11:28 PM, Karel Vervaeke <ka...@ou...>
>>> wrote:
>>>>
>>>> We recently upgraded from 3.3.6 to 3.5.7. Things work find under
>>>> various Linux machines,
>>>> but on windows XP, calling the wrapper with -i/-r or -t doesn't seem to do
>>>> anything (there's no output,
>>>> even with the log levels set to DEBUG in the conf file). When running
>>>> the 3.5.7 wrapper without arguments it still displays the help
>>>> information.
>>>>
>>>> When using 3.5.6 it works fine. Could this be related to the
>>>> privilege elevation stuff implemented for Vista & co?
>>>>
>>>> My XP install is running on a virtualbox virtual machine; I'm running
>>>> the wrapper as an administrator. -- Let me know if you need more
>>>> information (I don't know what else to include).
>>>> I don't have access to a Vista machine, so I didn't check if it works
>>>> there.
>>>>
>>>> Can anyone confirm this?
>>>>
>>>> Regards,
>>>> Karel
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
>>>> Pinpoint memory and threading errors before they happen.
>>>> Find and fix more than 250 security defects in the development cycle.
>>>> Locate bottlenecks in serial and parallel code that limit performance.
>>>> http://p.sf.net/sfu/intel-dev2devfeb
>>>> _______________________________________________
>>>> Wrapper-user mailing list
>>>> Wra...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
>>> Pinpoint memory and threading errors before they happen.
>>> Find and fix more than 250 security defects in the development cycle.
>>> Locate bottlenecks in serial and parallel code that limit performance.
>>> http://p.sf.net/sfu/intel-dev2devfeb
>>> _______________________________________________
>>> Wrapper-user mailing list
>>> Wra...@li...
>>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>>
>>>
>>
>
> ------------------------------------------------------------------------------
> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
> Pinpoint memory and threading errors before they happen.
> Find and fix more than 250 security defects in the development cycle.
> Locate bottlenecks in serial and parallel code that limit performance.
> http://p.sf.net/sfu/intel-dev2devfeb
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>