- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Please add these lines to the registry:
HKEY_LOCAL_MACHINE\Software\Microsoft\Command Processor
HKEY_LOCAL_MACHINE\Software\WOW6432\Microsoft\Command Processor
add the value DisableUNCC Check REG_DWORD and set the value of 0x1 (Hex).
My computer guy did this for me and it still will not work.
I am running Thermal Desktop, with Intel FORTRAN, on a network. Please help.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
These messages are coming from your Thermal Desktop application, not Intel Fortran. Please consult with your local administrative staff to resolve this problem.
For what it's worth, I found http://www.pctools.com/guides/registry/detail/1247/ regarding the instructions. My guess is that your application runs a command script that needs this Windows modification.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Still trying to trouble shoot the failure of Intel Fortran compiler from starting from inside thermal desktop. After working with the Thermal desktop vendor, they think the problem is related to the command line error that shows up as soon as the Intel Studio cmd prompt is opened (\common unexpected at this time). Screen shot is attached. Seems to be a problem with the path to the Intel compiler.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Of course it's Intel's fault that we are getting these *.pptx files instead of *.txt files because Intel doesn't enable Quick Edit mode on the CMD.EXE shortcuts that they provide.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Please do the following. From this command prompt session, type:
set PATH > path.txt
Attach the file path.txt to a reply here. I have seen this issue before - something else on your system inserted a string in PATH that is incorrect syntax. The error is actually coming from a Microsoft Visual Studio command file.
![](/skins/images/8B6E2C8F64F54CBD7F7262AA46F575DA/responsive_peak/images/icon_anonymous_message.png)
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page