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.
Non-Tech : Announcing: Wall Street Explorer for DATEK
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: Terence Wilson who wrote (116)7/17/1997 4:44:00 AM
From: Rene Madsen   of 244
 
Terence,

Thank you for your initiative; it is a very very good idea!

Unfortunately I can't make it work on any of my (two) PC's. I generally do not use IE as it (as most MS software) bugridden, and when it crashes (which it does often) it requires a complete reboot to get the PC running again.

As your program apparently use MSIE functions I installed MSIE 3.01 (without any of the "optional extras" - mail, news, etc - that shouldn't be necessary for WSX to run) but no: WSX violently crashes immidiately. The error is always the same:

----
STOCKWATCH.EXE caused fault #c0000005 in STOCKWATCH.EXE at address 014f:00410121

To date, 12 fatal errors have been recorded in this program. This particular error was recorded 12 times.

Reported By:
CrashGuard v2.0.1

Report Date:
17/07/97 10:38:34

WindowTitle:
Wall Street Explorer

Last Message:
MSG(0000087C, 0007, 00000B30, 00000000)

Program:
C:\PROGRAM FILES\WALL STREET EXPLORER\STOCKWATCH.EXE
(07/16/97 15:27 - 333824)

Registers:
EAX=00000000 CS=014f
EIP=00410121 EFLGS=00010246
EBX=00000001 SS=0157
ESP=0068ea34 EBP=0068ea38
ECX=007b3120 DS=0157
ESI=0041ea68 FS=2497
EDX=00000007 ES=0157
EDI=007b0d10 GS=0000

Bytes at CS:EIP:
8b 00 8b e5 5d c3 cc cc cc cc cc cc cc cc cc 55

Stack dump:
007b3120 0068eae4 0040f5d5 5f401018 00000001 007b0d10 0068ea64 5f40134a 5f409571 00000001 5f402216 0041ea68 00460078 0068eb30 5f48f8d7 ffffffff
---

Now, if it was just on one PC I would assume a problem somewhere else, but since these are two completely different PC's, running in different environments, generally without trouble, I must assume something is wrong with WSX.

Both PC's use MS Win95 OSR2 with FAT32 Filesystems - could this be a factor? Any ideas?

Rene
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  

HomeMailHotSubjectMarksPeopleMarksKeepersSettings
Terms Of UseContact UsCopyright/IP PolicyPrivacy PolicyAbout UsFAQAdvertise on SI
© 2025 Knight Sac Media.  Data provided by Twelve Data, Alpha Vantage, and CityFALCON News