All Forums
 Help For Easy-PC Users
 Libraries and Components
 Libraries not 'visible' after install

Note: You must be registered in order to post a reply.
To register, click here. Registration is FREE!

Screensize:
UserName:
Password:
Format Mode:
Format: BoldItalicizedUnderlineStrikethrough Align LeftCenteredAlign Right Horizontal Rule Insert HyperlinkInsert Email Insert CodeInsert QuoteInsert List
   
Message:

* HTML is OFF
* Forum Code is ON
Smilies
Smile [:)] Big Smile [:D] Cool [8D] Blush [:I]
Tongue [:P] Evil [):] Wink [;)] Clown [:o)]
Black Eye [B)] Eight Ball [8] Frown [:(] Shy [8)]
Shocked [:0] Angry [:(!] Dead [xx(] Sleepy [|)]
Kisses [:X] Approve [^] Disapprove [V] Question [?]

 
Check here to subscribe to this topic.
   

T O P I C    R E V I E W
DavidM Posted - 19 Aug 2009 : 12:56:43
We've had a few reports of new installs of Easy-PC where the standard libraries don't show up in the program after installation is complete.

This problem may be restricted to Vista64, but the basic issue is that the folder in the Libraries dialog has been initialised to point to the Program Files area instead of the shared documents area where the library files have actually been placed.

We are working on reproducing and fixing the problem, but in the meantime it is rectified quite simply by going to Setup, Libraries, Folders, and Browsing to the folder where the library files have been placed. On Vista for example this would be under C:\Users\Public, probably in Documents\Easy-PC\Library, with some differences depending on the language variant of Windows etc.
1   L A T E S T    R E P L I E S    (Newest First)
DavidM Posted - 02 Sep 2009 : 17:12:20
This problem has finally been tracked down to a missing setting in the library directories section of the registry which should have been added during Setup. Setup was correctly installing the libraries in the right place, then adding the registry entries to point the folders to those libraries, but the absence of this extra setting meant that first-time invocation of the application was 'converting' the registry information when it didn't need to.

This issue will be fixed in the main Setup program for the next update. In the meantime it is easily rectified as per my previous post.