Latest Untested Version Crashes Immediately

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Install (Rainmeter-Latest-20090721-32bit.exe)
2. Turned off UAC
3. Attempted to start Rainmeter

Please use labels and text to provide additional information.

Environment:
OS: Vista 32 bit 

After download and Install, I removed the Administrative Privileges, and
attempted to start Rainmeter by Desktop shortcut.

I immediately get the following:
Rainmeter.exe has stopped Working

The following is the error codes from windows "View Problem details":

Problem signature:
  Problem Event Name:   BEX
  Application Name: Rainmeter.exe
  Application Version:  0.0.0.0
  Application Timestamp:    4a65db8d
  Fault Module Name:    MSVCR90.dll
  Fault Module Version: 9.0.30729.1
  Fault Module Timestamp:   488ef6c5
  Exception Offset: 0002eac0
  Exception Code:   c0000417
  Exception Data:   00000000
  OS Version:   6.0.6002.2.2.0.768.3
  Locale ID:    1033
  Additional Information 1: 20dd
  Additional Information 2: 607d88eeb0c057d3109c482eaecdd922
  Additional Information 3: c9ad
  Additional Information 4: bf33d644696a9d8058468a6ded006b1b

Read our privacy statement:
  http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409

Any questions, let me know

Original issue reported on code.google.com by evmckay on 21 Jul 2009 at 5:56

[GoogleCodeExporter]

Update:

I just verified that the latest version will run if and only if I have UAC Off, 
or I
am running with Administrative Privileges.

Still testing, will continue to note issues that I find here.

Original comment by evmckay on 21 Jul 2009 at 5:59

[GoogleCodeExporter]

Consideration.

Does this version require that you uninstall teh older versions before it?

Original comment by evmckay on 21 Jul 2009 at 6:04

[GoogleCodeExporter]

Rainy, one thing I would point out.

If the users install this new vesion over top of their exiting installation, 
they end
up with a Rainmeter.ini file in BOTH places. (In Program Files\Rainmeter and
APPDATA\Rainmeter) This would be ok, but you seem to be defaulting to using the 
one
in Program Files if it sees both. This invalidates the whole purpose of the 
exercise,
as now the user still has the UAC issue with Vista / Seven until they delete 
the .ini
file from Program Files, and there is no reason why they would know to do that, 
and
that they need to do it with Rainmeter shut down or Rainmeter just instantly
recreates the Rainmter.ini file in Program Files\Rainmeter and they are likely
suicidal by the time they are done chasing their tails.

What I did in RainThemes was to check for the .ini file in the current directory
(usually Program Files\Rainmeter) and set that as the "ini folder", then look in
APPDATA\Rainmeter, and if I find a Rainmeter.ini there as well, change the "ini
folder" variable to APPDATA\Rainmeter and from then on just ignore the one in 
Program
Files. This addresses the "backward compatibility" issue gracefully, as if the 
.ini
is in location A alone it uses it, if in B alone it uses that, and if in both A 
and
B, it uses B and ignores A.

If you don't do something like this, then there is going to be mass confusion, 
folks
are still going to get UAC errors and a lot of time is going to be spent 
explaining
this over and over...

Either that, or have the installer move the current .ini file to 
APPDATA\Rainmeter
during the install so they keep their settings.

Original comment by jsmor...@gmail.com on 21 Jul 2009 at 6:45

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Update 2009/07/21 1230 MDT

Ok, I just eliminated the Rainmeter.ini file from the Rainmeter program File. 
All is working good.

A suggestion is to move your original Rainmeter.ini file to the
C:\Users\******\AppData\Roaming\Rainmeter

I think also that the skins file needs to be moved as well as adjustments can be
made, via NotePad, but not with NotePad++ unless run as Administrator.

When making skin changes, we still need to approve changes via the UAC.

The installer should either move the original ini file or remove it all 
together, as
there will be a lot of confusion.

Original comment by evmckay on 21 Jul 2009 at 7:08

[GoogleCodeExporter]

I tested this build in some different environment, but the problem did not 
occur.

environment:
 - Windows 2000 sp4
 - Windows XP pro sp3
 - Windows Vista Ultimate
 - Windows 7 RC

note:
 - On Vista and 7, UAC is active
 - "Overwrite install", "Clean install", tested both.

The problem which is transferred to the virtual folder was solved by this build.
This build seems to do the behavior almost announced on Issue 2(#3). On Vista 
or 7, I
think that this build is suitable than surely old build.

Original comment by kenz0.sa...@gmail.com on 22 Jul 2009 at 1:33

• Added labels: Version-0.14.1

[GoogleCodeExporter]

Original comment by kenz0.sa...@gmail.com on 1 Aug 2009 at 4:17

• Changed state: Done