SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Pastimes : A Novel Academy: 56ers in Annapolis -- Ignore unavailable to you. Want to Upgrade?


To: Cornstock who wrote (1909)11/11/1997 7:28:00 PM
From: Kulnor  Respond to of 2403
 
Peg,
check your email when you're back. The file you are looking for is studies.dat.
I posted a link to parity 1.5 in message
exchange2000.com

P



To: Cornstock who wrote (1909)11/11/1997 11:53:00 PM
From: Kulnor  Read Replies (3) | Respond to of 2403
 
[To all Investor Insight / Parity Users]
I wrote a utility to convert historical data created by the export to text utility from Investor Insight 2.0 to the ASCII file format supported by Parity 1.5
It's currently a win32 console application (meaning need to run fromthe dos prompt). If there is enough interest, I'll upgrade to a window application. If you are willing to beta-test, drop me a email and I'll send you a copy of the program.
You need to export the historical data from Investor Insight to a text file (by example microsft.txt) and then run the utility from the DOS prompt. It will convert the data to a file named '<stock_symbol>.par' (example msft.par). You can then use that file with parity 1.5

*Pascal*



To: Cornstock who wrote (1909)11/12/1997 4:15:00 AM
From: watcher  Read Replies (1) | Respond to of 2403
 
Peg, and all,

I likewise was unable to use parity by just copying the files to disk. I believe that Parity must be formally "installed" in order to run. Then, when a launch is attempted, it checks ...something...(can't be the Registry, as it runs under win3.1) and won't run unless that something is there.

I haven't tried moving Doug's copy to my installed copy...but that might work, and preserve Doug's prefs as well...

watcher

(Hey, Pascal, I might be up to porting your code to Visual Basic.)