Thursday, January 28, 2010

Runtime blunder - all which You Need to Know About the Runtime blunder


Runtime Error, DBA, 1/24/09 by richardgin.org










One Response to “Application Runtime error 217 without using ThinApp CapturedUsingVersion=”







  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





















I'm working on this page:

http://198.106.206.166/gbs-matte-eyeshadow.html



When I select an option ("Click here to select") my table of options shows with the swatches. This works fine in FF and IE.



However, when I actually click one of the options, I'm using innerHTML to re-write the main table content. It works great in FF, but gives me an error in IE7.



I've read that this is usually caused by two issues: 1) nested form tags, which I don't have and 2) improper HTML that's being writting using the innerHTML, which I think I've checked a few times.



Anyone see what I'm missing here?



Thanks

doubt the program refurbish doesn't , you might possess issues together with a mental recall on your mechanism. regulating which caring of problem may take contacting the maker of a mental recall as well as possibly even a maker of your PC.Source: http://www.articlesbase.com/operating-systems-articles/stop-c0000221-unknown-hard-error-fix-1629202.html

No comments:

Post a Comment