Hello Tomasz, List,
> > Are you sure? Shouldn't the "Connecting" stage fail first?
>
> Can you try:
>
> net use /delete *
>
> prior to any tests (to make sure you're not trying to be connected twice
> anywhere)?
>
Tried, - net use list is empty. I switched to a Win7 VM (32bit) for
testing
Am 01.06.2010 11:21, heiko.hel...@horiba.com wrote:
> > Tried - and failed with an administrative user "test". settings test is
> > odd:
> > "Executing as test" -> OK
> > "Connecting to \\wpkg\wpkg.js as \wpkg" -> OK
> > "Trying to read \\wpkg\wpkg.js" -> FAIL -> Access denied...
>
> > Tried - and failed with an administrative user "test". settings test
is
> > odd:
> > "Executing as test" -> OK
> > "Connecting to \\wpkg\wpkg.js as \wpkg" -> OK
> > "Trying to read \\wpkg\wpkg.js" -> FAIL -> Access denied...
> >
> > this doesn't make much sense, because
> > a) I can re
Am 19.05.2010 16:31, heiko.hel...@horiba.com wrote:
> So you're planning to use "runas" with the Administrator account I
guess. For
> sure this might be an option as well.
> This could have been a solution to the "broken Innosetup" installer
> problem some
> of us faced a while ago. Some ne
> So you're planning to use "runas" with the Administrator account I
guess. For
> sure this might be an option as well.
> This could have been a solution to the "broken Innosetup" installer
> problem some
> of us faced a while ago. Some new version of Innosetup was just hanging
during
> the inst
Hi Heiko,
On 18.05.2010 11:50, heiko.hel...@horiba.com wrote:
>> In addition I was under the impression that %TEMP% expands to %
>> SystemRoot%\temp
>> (c:\windows\temp) for the system account. At least I've never seen
>> it expanding
>> to systemprofile\AppData\Temp which looks anyway wrong, if a
> I agree that folder redirection makes it quite hard to track what is
really
> happening on the system. However I am running Windows x64 since
> years (since my
> first Windows Vista installation) and never had such issues yet.
>
> In addition I was under the impression that %TEMP% expands to %
Hi Heiko,
On 18.05.2010 08:32, heiko.hel...@horiba.com wrote:
> I'm currently and regularly running into the WOW64 mess while trying to
> make my wpkg-package collection "Win64-ready". The problem consists of
> two facts:
>
> * A 32 bit installshield .exe
> * the WOW brain-hurt diversion layer
>
Hello list,
I'm currently and regularly running into the WOW64 mess while trying to
make my wpkg-package collection "Win64-ready". The problem consists of two
facts:
* A 32 bit installshield .exe
* the WOW brain-hurt diversion layer
* MSI
* WPKG running as user SYSTEM and the SYSTEM profile sit
