It is currently June 15th, 2024, 7:02 am

[Solved] Rainmeter can't load any skin named clock.ini in XP

Report bugs with the Rainmeter application and suggest features.
dragonmage
Developer
Posts: 1270
Joined: April 3rd, 2009, 4:31 am
Location: NC, US

[Solved] Rainmeter can't load any skin named clock.ini in XP

Post by dragonmage »

Confirmed by several people now. Rename any skin to clock.ini and Rainmeter throws a "No Meters" error.

Problem apparently does not occur in Win7.
User avatar
spx
Developer
Posts: 686
Joined: August 15th, 2009, 2:41 pm
Location: Osaka, JPN

Re: [BUG] Rainmeter cannot load any skin named clock.ini in XP

Post by spx »

This behavior is not a Rainmeter's bug. It's XP's limitation.
On XP, we cannot use Clock.ini, Win.ini, System.ini, etc., as Rainmeter's skin-ini filename. These ini filenames are handled as "IniFileMapping".

Administering the Windows NT Registry
How Does Mapping Work?

NT implements mapping by trapping the private profile API routines I mentioned in Chapter 1. Windows applications and components ordinarily use these calls to get and set data stored in INI files, but when there's a mapping entry, the NT kernel first checks for the presence of a mapping key. If one exists, and if it points to a key that contains data, that data is returned to the caller. If there's no mapping key, or if it points to an empty or non-existent Registry key, NT will go ahead and try to read the data from the INI file. The caller need never be aware that the data didn't come from the requested file.

Mapping only occurs when there's a mapping key in place. These keys are stored beneath the HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\IniFileMapping subkey. If you look there, you'll notice a number of subkeys with names like Clock.INI, Win.INI, and SYSTEM.INI. These keys tie sections of the old Win 3.1-style INI files to keys in the Registry so that old Windows 3.1 components like the Clock and the original media controller interface (MCI) will continue to find their settings.
IniFileMapping.jpg
User avatar
maminscris
Posts: 509
Joined: April 24th, 2009, 3:17 pm
Location: Bucharest, Romania Lat 44,43° Lon 26,1°

Re: [BUG] Rainmeter cannot load any skin named clock.ini in XP

Post by maminscris »

damn xp, we should make a trial to microsoft for discrimination, now that is why aranea clock did not load :evil:

thanks for the tip, we should put this in manual, do not rename skins like...
Zero at programing, zero at writing codes, so far 2 at making images
But I'm good at copy/paste, and I not always like this
Image
User avatar
Varelse
Posts: 61
Joined: April 22nd, 2009, 7:46 pm

Re: [BUG] Rainmeter cannot load any skin named clock.ini in XP

Post by Varelse »

That also explains why my System skin was giving me a [boot.description] error. It was named system.ini.
dragonmage
Developer
Posts: 1270
Joined: April 3rd, 2009, 4:31 am
Location: NC, US

Re: [BUG] Rainmeter cannot load any skin named clock.ini in XP

Post by dragonmage »

Thanks for clearing that up spx.
User avatar
Dave_W
Posts: 37
Joined: April 20th, 2009, 10:58 am

Re: [Solved] Rainmeter can't load any skin named clock.ini in XP

Post by Dave_W »

Well I never.

Can this go in the manual under the "Time" measure section? Only...well, I don't want to ADMIT how long I've just spent trying to figure out what the hell was wrong with my lovingly-crafted Clock.ini!
User avatar
maminscris
Posts: 509
Joined: April 24th, 2009, 3:17 pm
Location: Bucharest, Romania Lat 44,43° Lon 26,1°

Re: [Solved] Rainmeter can't load any skin named clock.ini in XP

Post by maminscris »

Dave_W wrote:Well I never.

Can this go in the manual under the "Time" measure section?
a section with do not name your skins: system.ini, clock.ini and so on
Zero at programing, zero at writing codes, so far 2 at making images
But I'm good at copy/paste, and I not always like this
Image