- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I just came across a strange thing - -
When I generate an unformatted sequential data file (Primes.DAT) I can read it from a program within
the same directory. But when I move it to another directory, that very same program can no longer read it.
Apparently I have to leave the file in place for it to remain usable by other programs.
Is this some kind of device to keep us from exporting an application? I know they do a similar
thing with EXE (application files) because they do not want us to ship those around (for free).
But I don't see why that should apply to DATA files. Any clarification on this?
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Bill
There should be no problem at allmoving data files about.
When you say the program "can no longer read it" what error code/message do you get?
It sounds like it couldbe a problem with the path to the file?
Les
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Bill,
Please explain your comment about EXE files. I have no clue as to what you are referring.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I was told that (and this could possibly be no longer the case) that when I make an executable with the Fortran libary/compiler, Microsoft and/or Intel has a way to keep me from making it available to others without paying a license fee. Perhaps that's why we have a professional version of VS, so that Microsoft gets a "slice of the pie."
Anyway, that used to be the case, but perhaps their policy is different now. I have noticed, however, that I cannot send a usable version (*.EXE) of an application I built myself to a friend, for example. But a professional version may not have that restriction.
Whether that policy also extends to the compiler, well that's another question. Intel could say "well you used our product, so we have a say as to how and when your application is distributed." That's the way it was during the Pre-Intel (Compaq) days.
That gets into some thorny legal issues, though, which I'm not qualified to answer. I wonder if anyone has challenged this? For example, Microsoft does not challenge someone who writes the great American novel using Microsoft Word. But they have no way of tracking it, of course.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Bill,
Whoever told you that is gravely mistaken. It has never been the case, not with Compaq either. Both the Intel and Microsoft licenses permit you to distribute your EXEs to anyone you want, in any number, free of charge (as long as you're not using an evaluation copy of the product). Any difficulty you have running programs sent elsewhere are due, usually, to missing run-time DLLs.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Debug exes should not be redistributed - or at least the debug runtimes should not.
That's the only restriction that I know of. It has always been possible to distribute release exes and runtimes from anyone's compiler, that I know of.
Les
PS You didn't tell us what the error message was

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page