<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Copyright (C) 1985-2018 Intel in Intel® Fortran Compiler</title>
    <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Write-access-for-obj-file/m-p/1172062#M146198</link>
    <description>&lt;PRE class="brush:plain; class-name:dark;"&gt;Copyright (C) 1985-2018 Intel Corporation. All rights reserved.
 Intel(R) Compiler 18.0 Update 3 (package 210)

Setting environment for using Microsoft Visual Studio Shell 15.0 x86 tools.

C:\Program Files (x86)\IntelSWTools&amp;gt;cd \temp
C:\temp&amp;gt;ifort /c hello.f90

&lt;/PRE&gt;

&lt;P&gt;Jim Dempsey&lt;/P&gt;</description>
    <pubDate>Fri, 11 Jan 2019 21:35:49 GMT</pubDate>
    <dc:creator>jimdempseyatthecove</dc:creator>
    <dc:date>2019-01-11T21:35:49Z</dc:date>
    <item>
      <title>Write access for .obj file</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Write-access-for-obj-file/m-p/1172058#M146194</link>
      <description>&lt;DIV&gt;This is the source file:&lt;/DIV&gt;

&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;

&lt;DIV&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Program hello&lt;BR /&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; print *, 'hello world'&lt;/DIV&gt;

&lt;DIV&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; end program&lt;/DIV&gt;

&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;

&lt;DIV&gt;This is the command screen:&lt;/DIV&gt;

&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;

&lt;DIV&gt;Copyright (C) 1985-2018 Intel Corporation. All rights reserved.&lt;BR /&gt;
	Intel(R) Compiler 18.0 Update 3 (package 210)&lt;/DIV&gt;

&lt;DIV&gt;Setting environment for using Microsoft Visual Studio Shell 15.0 x86 tools.&lt;/DIV&gt;

&lt;DIV&gt;C:\Program Files (x86)\IntelSWTools&amp;gt;ifort /c C:\temp\hello.f90&lt;BR /&gt;
	Intel(R) Visual Fortran Intel(R) 64 Compiler for applications running on IA-32, Version 18.0.3.210 Build 20180410&lt;BR /&gt;
	Copyright (C) 1985-2018 Intel Corporation.&amp;nbsp; All rights reserved.&lt;/DIV&gt;

&lt;DIV&gt;error: can't open file hello.obj for write&lt;BR /&gt;
	compilation aborted for C:\temp\hello.f90 (code 1)&lt;/DIV&gt;

&lt;DIV&gt;C:\Program Files (x86)\IntelSWTools&amp;gt;&lt;/DIV&gt;

&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;

&lt;P&gt;I can turn off the "Read-only" attribute for the folder C:\temp, but when I execute ifort it gets changed back, and ifort can not generate the .obj file.&amp;nbsp;&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 17 Aug 2018 21:42:04 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Write-access-for-obj-file/m-p/1172058#M146194</guid>
      <dc:creator>PASeeger</dc:creator>
      <dc:date>2018-08-17T21:42:04Z</dc:date>
    </item>
    <item>
      <title>See https://software.intel</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Write-access-for-obj-file/m-p/1172059#M146195</link>
      <description>&lt;P&gt;See&amp;nbsp;https://software.intel.com/en-us/forums/intel-visual-fortran-compiler-for-windows/topic/784675&lt;/P&gt;</description>
      <pubDate>Mon, 20 Aug 2018 19:12:03 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Write-access-for-obj-file/m-p/1172059#M146195</guid>
      <dc:creator>Steve_Lionel</dc:creator>
      <dc:date>2018-08-20T19:12:03Z</dc:date>
    </item>
    <item>
      <title>while running the compiler</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Write-access-for-obj-file/m-p/1172060#M146196</link>
      <description>&lt;P&gt;while running the compiler via the command prompt, cd to the folder containing the code before trying to compile&lt;/P&gt;</description>
      <pubDate>Fri, 11 Jan 2019 03:39:03 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Write-access-for-obj-file/m-p/1172060#M146196</guid>
      <dc:creator>Baltaji__Omar</dc:creator>
      <dc:date>2019-01-11T03:39:03Z</dc:date>
    </item>
    <item>
      <title>And as Steve already</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Write-access-for-obj-file/m-p/1172061#M146197</link>
      <description>&lt;P&gt;And as Steve already explained, you should do program development in a folder that you created, where you will have full read-write permissions.&amp;nbsp; Never work in a folder that is part of the compiler installation.&lt;/P&gt;</description>
      <pubDate>Fri, 11 Jan 2019 20:37:34 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Write-access-for-obj-file/m-p/1172061#M146197</guid>
      <dc:creator>gib</dc:creator>
      <dc:date>2019-01-11T20:37:34Z</dc:date>
    </item>
    <item>
      <title>Copyright (C) 1985-2018 Intel</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Write-access-for-obj-file/m-p/1172062#M146198</link>
      <description>&lt;PRE class="brush:plain; class-name:dark;"&gt;Copyright (C) 1985-2018 Intel Corporation. All rights reserved.
 Intel(R) Compiler 18.0 Update 3 (package 210)

Setting environment for using Microsoft Visual Studio Shell 15.0 x86 tools.

C:\Program Files (x86)\IntelSWTools&amp;gt;cd \temp
C:\temp&amp;gt;ifort /c hello.f90

&lt;/PRE&gt;

&lt;P&gt;Jim Dempsey&lt;/P&gt;</description>
      <pubDate>Fri, 11 Jan 2019 21:35:49 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Write-access-for-obj-file/m-p/1172062#M146198</guid>
      <dc:creator>jimdempseyatthecove</dc:creator>
      <dc:date>2019-01-11T21:35:49Z</dc:date>
    </item>
    <item>
      <title>In particular, don't do</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Write-access-for-obj-file/m-p/1172063#M146199</link>
      <description>&lt;P&gt;In particular, don't do development in a folder under Windows or Program Files. Unfortunately, the shortcut created by the install uses the install folder as a default. I'm not sure if the installer has the ability to change this.&lt;/P&gt;</description>
      <pubDate>Sat, 12 Jan 2019 15:36:33 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Write-access-for-obj-file/m-p/1172063#M146199</guid>
      <dc:creator>Steve_Lionel</dc:creator>
      <dc:date>2019-01-12T15:36:33Z</dc:date>
    </item>
    <item>
      <title>&gt;&gt; I'm not sure if the</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Write-access-for-obj-file/m-p/1172064#M146200</link>
      <description>&lt;P&gt;&amp;gt;&amp;gt;&amp;nbsp;I'm not sure if the installer has the ability to change this.&lt;/P&gt;&lt;P&gt;However, you can Right-Click on the shortcut, select properties, then in the Shortcut property tab, set the Start in property to a default folder of your preference (e.g. C:\temp or C:\workspace or ...)&lt;/P&gt;&lt;P&gt;Jim Dempsey&lt;/P&gt;</description>
      <pubDate>Sat, 12 Jan 2019 16:03:41 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Write-access-for-obj-file/m-p/1172064#M146200</guid>
      <dc:creator>jimdempseyatthecove</dc:creator>
      <dc:date>2019-01-12T16:03:41Z</dc:date>
    </item>
    <item>
      <title>Sure, or what I do is:</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Write-access-for-obj-file/m-p/1172065#M146201</link>
      <description>&lt;P&gt;Sure, or what I do is:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Copy the shortcut to my desktop&lt;/LI&gt;&lt;LI&gt;Change the Start In folder&lt;/LI&gt;&lt;LI&gt;Edit the path for Target to start with "%IFORT_COMPILER19%bin\"&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;This last means I can use the same shortcut to get the latest update and not have to find it in the Start menu. I also edit the Layout to increase the Window Size and Buffer Size.&lt;/P&gt;</description>
      <pubDate>Sat, 12 Jan 2019 16:33:46 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Write-access-for-obj-file/m-p/1172065#M146201</guid>
      <dc:creator>Steve_Lionel</dc:creator>
      <dc:date>2019-01-12T16:33:46Z</dc:date>
    </item>
    <item>
      <title>Quote:jimdempseyatthecove</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Write-access-for-obj-file/m-p/1172066#M146202</link>
      <description>&lt;P&gt;&lt;/P&gt;&lt;BLOCKQUOTE&gt;jimdempseyatthecove wrote:&lt;BR /&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;gt;&amp;gt;&amp;nbsp;I'm not sure if the installer has the ability to change this.&lt;/P&gt;&lt;P&gt;However, you can Right-Click on the shortcut, select properties, then in the Shortcut property tab, set the Start in property to a default folder of your preference (e.g. C:\temp or C:\workspace or ...)&lt;/P&gt;&lt;P&gt;Jim Dempsey&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Good point by Jim, I was going to write the same.&lt;/P&gt;&lt;P&gt;It's rather surprising the Parallel Studio installer sets up shortcuts with a "Start in" setting to a folder under&amp;nbsp;ProgFiles, a no-no from any software enterprise perspective:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="lnk.png"&gt;&lt;img src="https://community.intel.com/t5/image/serverpage/image-id/10376iFC7989242EE825E3/image-size/large?v=v2&amp;amp;px=999&amp;amp;whitelist-exif-data=Orientation%2CResolution%2COriginalDefaultFinalSize%2CCopyright" role="button" title="lnk.png" alt="lnk.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Why can't someone from Intel staff take an action item from this thread to loop back to the Parallel Studio packaging team to modify the shortcut(s) with user-friendly settings such as those described in Quote #8?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 12 Jan 2019 17:05:00 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Write-access-for-obj-file/m-p/1172066#M146202</guid>
      <dc:creator>FortranFan</dc:creator>
      <dc:date>2019-01-12T17:05:00Z</dc:date>
    </item>
    <item>
      <title>What would you suggest the</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Write-access-for-obj-file/m-p/1172067#M146203</link>
      <description>&lt;P&gt;What would you suggest the installer select for Start In? The only thing I can think of would be My Documents. But then I looked at what Microsoft Visual Studio does, and it also sets Start In to be the install folder, so I have to think that the mechanism for adding the shortcut doesn't provide that capability.&lt;/P&gt;</description>
      <pubDate>Sat, 12 Jan 2019 17:57:31 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Write-access-for-obj-file/m-p/1172067#M146203</guid>
      <dc:creator>Steve_Lionel</dc:creator>
      <dc:date>2019-01-12T17:57:31Z</dc:date>
    </item>
    <item>
      <title>Quote:Steve Lionel (Ret.)</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Write-access-for-obj-file/m-p/1172068#M146204</link>
      <description>&lt;P&gt;&lt;/P&gt;&lt;BLOCKQUOTE&gt;Steve Lionel (Ret.) wrote:&lt;BR /&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What would you suggest the installer select for Start In? ..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Why not Visual Studio XXXX folder in Documents?&amp;nbsp; Every shortcut in Intel Parallel Studio is specific to target platform (e.g., x64) but also the integration with a Visual Studio version.&amp;nbsp; And&amp;nbsp;Microsoft Visual Studio installer indeed creates a folder under Documents e.g., %user profile\Documents\Visual Studio 2017.&lt;/P&gt;</description>
      <pubDate>Sat, 12 Jan 2019 20:38:42 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Write-access-for-obj-file/m-p/1172068#M146204</guid>
      <dc:creator>FortranFan</dc:creator>
      <dc:date>2019-01-12T20:38:42Z</dc:date>
    </item>
    <item>
      <title>Not a bad idea, but I do have</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Write-access-for-obj-file/m-p/1172069#M146205</link>
      <description>&lt;P&gt;Not a bad idea, but I do have to wonder why VS itself doesn't do this.&lt;/P&gt;</description>
      <pubDate>Sat, 12 Jan 2019 22:31:22 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Write-access-for-obj-file/m-p/1172069#M146205</guid>
      <dc:creator>Steve_Lionel</dc:creator>
      <dc:date>2019-01-12T22:31:22Z</dc:date>
    </item>
  </channel>
</rss>

