Bill Arnold wrote on 2012-10-04:
> Tracy,
>
> If I remember right, INNO doesn't create a log file unless specified. I
> never turned it back off when I was finished dealing with some unique
> troubled clients machines.
> This line is in my [Setup] section:
> SetupLogging="yes"
> --------------------
>
> Yes. During the course of looking into this, I did turn on the INNO log
> using the command line parm:
>
> Setup.exe /LOG="C:\TESTFOLDER\INST.LOG"
>
> I'd prefer your method, but it puts the log into %TEMP% which means
> the customer would have to discover (using SET or some other means)
> what TEMP points to in order to retrieve it. One post on the subject
> shows code to copy the log somewhere,
> http://stackoverflow.com/questions/5116217/how-can-i-log-inno-setup-inst
> alla tions but it seems there should just be a var for this in the 1st
> place.
>
> I was thinking/hoping the log would reveal something about this problem,
but
> nooooooo :)
>
>
> Bill
>
Bill,
Windows+R, %temp%, {ENTER}
Those steps on XP, Vista, Windows 7 will open Windows Explorer to the
variable set as TEMP.
In VFP the command would be
_VFP.DoCmd([!START "" "] + getEnv("Temp") + ["])
Seeing the log file gives the clue that the files were found. I'll say the
problem exists after the setup completes.
Does the Admin user see the files, the standard user can not?
Tracy Pearson
PowerChurch Software
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
