|
PureBytes Links
Trading Reference Links
|
As usual, I did not state the problem completely the first time around.
It is ONLY when CleanObject("Up1"); below is used that Hashnums32 shows
the runtime error: "Floating point invalid numbers in calculation". Just
adding the DefinedllFunc:--- does not cause the error. If I delete only
CleanObject("Up1"); then Hashnums32 works fine.
if currentbar=1 then begin
(your other DefineDllFunc)
DefineDllFunc:"c:\program
files\hashserv32\HashClient32.dll",FLOAT,"cleanObject",LPSTR;
CleanObject("Up1");
end;
where "Up1" comes from something like: putNo("Up1",N,7).
This cleans up, at the start of the program, only the object specified
("Up1") and not all objects in the program. Maybe some of you are not
using this. It is very handy and is new in Hashnums32.
I desperately need to find if others are having this same problem when
using "cleanobject("object");. If you are running Hashnums32 with sp3
would you be so considerate as to add the above definedllFunc to any of
your code and see if it works for you. If it does not, only a dialog box
shows which you can delete. Then delete the added code and you are right
back to your original code.
I can not get Stuart Okorofsky's GV32 DLL to work in sp3 either. Any one
have luck there?
wayne
P.S. I have tried the above in Win 2000 beta3 (RC2), TS2K sp3 and
cleanobject("") does not work there either. But Win 2000 does not use up
memory like W95.
>Has anyone had the DLLs, Hashnum32 or Stuart Okorofsky's GV32, NOT work
> in TS2K with sp3? Both work fine for me in sp2 but not sp3. I am running
> W95, 400MHz, 256 M ram. I had to back out of sp3 to sp2 to get the DLLs
> to work. I will post later how I did this while keeping most of my
> work.
>
|