{"id":68,"date":"2013-07-12T13:00:31","date_gmt":"2013-07-12T12:00:31","guid":{"rendered":"http:\/\/blogs.kent.ac.uk\/psychotech\/?p=68"},"modified":"2013-07-30T12:24:07","modified_gmt":"2013-07-30T11:24:07","slug":"amos-text-output-work-around","status":"publish","type":"post","link":"https:\/\/blogs.kent.ac.uk\/hsstech\/2013\/07\/12\/amos-text-output-work-around\/","title":{"rendered":"AMOS Text Output Work Around"},"content":{"rendered":"<p>&nbsp;<\/p>\n<p>A known issue exists with AMOS 20 and later when using Staff and Student desktop PC\u2019s. When attempting to create a text output file, AMOS gives the error:<\/p>\n<p><i>\u201cThis output file is in an obsolete format.\u00a0 It can be viewed. However, some features of the output viewer will be unavailable<\/i>.<i>\u201d<\/i><\/p>\n<p><i><\/i>Unfortunately there is no fix for this issue as it stands. \u00a0We developed a stand-alone PC build with Information Services for the SP801 exam but the Staff and Student desktop builds currently, always create the error message that you see above.<\/p>\n<p>We do have a couple of work arounds that enable you to create, view and save your output files however:<\/p>\n<p><strong>Option 1:<\/strong><\/p>\n<p>When you get the error message click <i>OK<\/i>, you then get an option to save the file. \u00a0Save the file to a location you can find again in a moment, somewhere like the desktop for example.<\/p>\n<p>Now click <i>close<\/i> in the error message window and click on the red cross to close the AMOS output window.<\/p>\n<p>Open MS Word. Go to <i>File<\/i> and <i>Open<\/i>. Browse to the location that you saved your output file. Ensure the file type you are searching for is set to <i>All Files (*.*)<\/i> or you wont be able to find your output file. \u00a0Click <em>O<\/em><em>pen<\/em>. \u00a0It should open into MS Word quite happily.<\/p>\n<p>I would advise now saving the file as a .docx Word document so you won\u2019t need to go through that every time you open it.<\/p>\n<p><strong>Option 2:<\/strong><\/p>\n<p><strong><\/strong>As before save your file to a location you can find again in a moment. \u00a0This time we will change the file extension from .AmosOutput to .html this is a little more involved but has the advantage of keeping all the features that AMOS creates within the Output file. This is because the .AmosOutput file extension is really just a fancy .html document.<\/p>\n<p>First, it would be useful to able to see the file extensions of all your files, this Microsoft article will help you to show or hide Windows 7 file extensions:\u00a0<a title=\"http:\/\/bit.ly\/18aUAFN\" href=\"http:\/\/bit.ly\/18aUAFN\" target=\"_blank\">http:\/\/bit.ly\/18aUAFN<\/a><\/p>\n<p>Next, you need to find your Output file. \u00a0You should now be able to see the .AmosOutput at the end of the file name. \u00a0Right click on the file and select <em>Rename<\/em>. Delete the part that reads .AmosOutput and replace it with .html<\/p>\n<p>You can now open your Output file in Word, a Web Browser or any other html compliant piece of software. \u00a0By default the file will open in your default Web Browser, to open in another program you must right click, select\u00a0<em>Open with&#8230;<\/em> and browse to the new program.<\/p>\n<p>&nbsp;<\/p>\n<p>We realise that this situation is not ideal and apologise for any inconvenience. \u00a0Hopefully the above work arounds will relieve some of your frustrations. \u00a0At the moment AMOS is not officially supported by IBM on a virtualised Windows environment, which is what we run here at the University, this leaves me unable to give any sort of time frame on when a permanent solution will appear.<\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>&nbsp; A known issue exists with AMOS 20 and later when using Staff and Student desktop PC\u2019s. When attempting to create a text output file, &hellip; <a href=\"https:\/\/blogs.kent.ac.uk\/hsstech\/2013\/07\/12\/amos-text-output-work-around\/\">Read&nbsp;more<\/a><\/p>\n","protected":false},"author":29065,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[56647],"tags":[],"_links":{"self":[{"href":"https:\/\/blogs.kent.ac.uk\/hsstech\/wp-json\/wp\/v2\/posts\/68"}],"collection":[{"href":"https:\/\/blogs.kent.ac.uk\/hsstech\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.kent.ac.uk\/hsstech\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.kent.ac.uk\/hsstech\/wp-json\/wp\/v2\/users\/29065"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.kent.ac.uk\/hsstech\/wp-json\/wp\/v2\/comments?post=68"}],"version-history":[{"count":4,"href":"https:\/\/blogs.kent.ac.uk\/hsstech\/wp-json\/wp\/v2\/posts\/68\/revisions"}],"predecessor-version":[{"id":70,"href":"https:\/\/blogs.kent.ac.uk\/hsstech\/wp-json\/wp\/v2\/posts\/68\/revisions\/70"}],"wp:attachment":[{"href":"https:\/\/blogs.kent.ac.uk\/hsstech\/wp-json\/wp\/v2\/media?parent=68"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.kent.ac.uk\/hsstech\/wp-json\/wp\/v2\/categories?post=68"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.kent.ac.uk\/hsstech\/wp-json\/wp\/v2\/tags?post=68"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}