got windows 7? idealisation guide on how to enhance windows 7 to speed awake a performance

1. 
   ggeldorp Says:
   
   
   
   January 15th, 2010 at 7:25 pm
   
   

   The CapturedUsingVersion is used to determine which filesystem macros need to be expanded. Some extra macros were introduced in late Thinstall 3.3 versions, e.g. %Program Files Common%.

   
   

   Suppose the application installer created a file C:Program FilesCommon FilesAppFile.ext. Since you captured this using 4.0.3 that file will get stored in the project as %Program Files Common%AppFile.ext. With the CapturedUsingVersion setting intact, when the virtual app tries to open C:Program FilesCommon FilesAppFile.ext, this will get translated to %Program Files Common%AppFile.ext. That file exists in the project and everything works fine. Now, when you remove the CapturedUsingVersion, the runtime assumes the project was captured with an old Thinstall version which didn’t support the %Program Files Common% macro. So when the virtual app tries to open C:Program FilesCommon FilesAppFile.ext the runtime will translate it to %ProgramFilesDir%Common FilesAppFile.ext. That file does not exist in the project and the open fails.

   
   

   If you really had captured the app with that “ancient” Thinstall version, the file would have been stored as %ProgramFilesDir%Common FilesAppFile.ext, which is the path the runtime would use when there was no CapturedUsingVersion or when the CapturedUsingVersion setting indicated the old version.

   
   

   I guess the moral of the story is “CapturedUsingVersion: not just for fun and documentation, don’t mess with it”.

   
   
   

Comments

Name

Mail (will not be published)

Website

1. 
   ggeldorp Says:
   
   
   
   January 15th, 2010 at 7:25 pm
   
   

   The CapturedUsingVersion is used to determine which filesystem macros need to be expanded. Some extra macros were introduced in late Thinstall 3.3 versions, e.g. %Program Files Common%.

   
   

   Suppose the application installer created a file C:Program FilesCommon FilesAppFile.ext. Since you captured this using 4.0.3 that file will get stored in the project as %Program Files Common%AppFile.ext. With the CapturedUsingVersion setting intact, when the virtual app tries to open C:Program FilesCommon FilesAppFile.ext, this will get translated to %Program Files Common%AppFile.ext. That file exists in the project and everything works fine. Now, when you remove the CapturedUsingVersion, the runtime assumes the project was captured with an old Thinstall version which didn’t support the %Program Files Common% macro. So when the virtual app tries to open C:Program FilesCommon FilesAppFile.ext the runtime will translate it to %ProgramFilesDir%Common FilesAppFile.ext. That file does not exist in the project and the open fails.

   
   

   If you really had captured the app with that “ancient” Thinstall version, the file would have been stored as %ProgramFilesDir%Common FilesAppFile.ext, which is the path the runtime would use when there was no CapturedUsingVersion or when the CapturedUsingVersion setting indicated the old version.

   
   

   I guess the moral of the story is “CapturedUsingVersion: not just for fun and documentation, don’t mess with it”.

   
   
   

Comments

Name

Mail (will not be published)

Website

Hello Jerry,



Here is a short quote from our documentation:

Problem:

Using RadControls with RadScriptManager on your login page throws one of the following errors:

• ASP.NET Ajax client-side framework failed to load


• 'Sys' is undefined


• “Telerik.Web.UI” is undefined

Cause:

As the website denies access to all pages to unauthorized users, access to the Telerik.Web.UI.WebResource.axd handler is unauthorized. This causes the handler to serve the content of the login page instead of the combined scripts, hence the error.

Suggested solution:

Add a <location> section to the application configuration file to allow access to Telerik.Web.UI.WebResource.axd to all users, like:

Add location property

Source:http://www.articlesbase.com/operating-systems-articles/fix-svchostexe-application-errorsvchostexe-application-error-repair-1487023.html