On Wednesday 04 July 2007 19:56, George Woltman wrote: > At 02:31 PM 7/4/2007, you wrote: > > > Remember that mprime and prime95 looks for all the ini files and save > > > files in the same directory as the executable. You can change that > > > behavior with the -W command line argument. > > > >Hmmm. My impression is that mprime looks for its files in the current > > working directory. > > Then there is a bug in the Linux version. Hmmm, should I go fix it? > No. It's a feature. So far as I'm concerned, a correct one. Always have a special place to store executables, the directory is for non-executable files associated with the task. The operating system looks for executables on $PATH; even Windows (harking back to its DOS heritage - and DOS learned from unix) recognises that. The problem is that early DOS somehow got the idea that users were too lazy to file executables in sensible places, so allowed exe's in the current working directory to be run by default.
Maybe it didn't matter when "bulk storage" was a 160KB floppy drive. Here's the real point. If you have exe's in a special place, it's relatively easy to checksum them, compare the checksums and identify imposters which might have snuck in. If exe's are allowed to be scattered all over the place, this is a lot harder. I'd be happier if you fixed the windows version. Would probably annoy 99% of windows users, though. Fix the linux documentation if it's wrong. Otherwise, it's probably better to leave things as they are. Regards Brian Beesley _______________________________________________ Prime mailing list [email protected] http://hogranch.com/mailman/listinfo/prime
