Hi, Here is the decription of another annoying bug that I have been getting for a long time, in case anyone wants to try with their version. Please let me know what happens. By the way, who are you supposed to contact in Oz for JS support ? Over here its Roy Gillett who is always willing but some things need referring to the programmers. Graham.
--- On Mon, 20/7/09, Graham Douglas <ondastropic...@yahoo.co.uk> wrote:
From: Graham Douglas <ondastropic...@yahoo.co.uk> Subject: JS2 problems To: "roy gillett" <roy.gill...@ntlworld.com> Date: Monday, 20 July, 2009, 11:54 PM
I expect you remember me telling you about some other problems I had with JS a long time ago, which I believe neither you nor the Aussies could reproduce ? Well it still happens, and although I have a way of getting round it it still annoys me, but it also occurs to me that perhaps it has to do with the files I have imported because I never use any of those that come with JS. I'm attaching a file in .DAT format imported into JS, and I wonder if you could try the following sequence on it on your machine to see if you also get a RunTime Error Number 9 : out of Range ? When you have a spare moment. I open the file and go to Research--Criteria Search -- Moon Longitude, Zodiac Signs and select one sign. After running Search I save it as offered in a new file, and display the results using Research Graph and Tabulate. No problem so far. I quit qnd quit again to get out of this, and click back to Research Criteria Search where the previous selection is still highlighted in the List of Current Criteria, and the Division names are still as before. Now I click to highlight another zodiac sign without changing either the Data Type or Division Type and delete or clear the previously highlighted line in current Criteria. As soon as I then click Add for the new criterion up comes a box with Run Time Error 9, subscript Out of Range. The way I use to avoid this is that when I go back to the Criteria I first change the Data Type and Division Type boxes before changing the Data Type back to the one I am using from before.. I can then change the Type and do the Add and complete the new Criteria Search without the program shutting down. I'm not sure if we have discussed this exact example before but it happens to be a fairly simple one so I thought it would be a good example, and it has happened on every machine I have used over the last 2 or 3 years. Thanks again for your help beyond the call of duty with XL, at least this one is all about JS. Best Wishes, Graham.
On Aug 29, 7:06 pm, Graham Douglas <ondastropic...@yahoo.co.uk> wrote:
> Hi,
> Here is the decription of another annoying bug that I have been getting for a long time, in case anyone wants to try with their version. Please let me know what happens.
> By the way, who are you supposed to contact in Oz for JS support ?
> Over here its Roy Gillett who is always willing but some things need referring to the programmers.
> Graham.
[....]
>I open the file and go to Research--Criteria Search -- Moon Longitude, Zodiac Signs and select one sign. After running Search I save it as offered in a new file, and display the results using Research Graph and Tabulate. No problem so far. I quit qnd quit again to get out of this, and click back to Research Criteria Search where the previous selection is still highlighted in the List of Current Criteria, and the Division names are still as before. Now I click to highlight another zodiac sign without changing either the Data Type or Division Type and delete or clear the previously highlighted line in current Criteria. As soon as I then click Add for the new criterion up comes a box with Run Time Error 9, subscript Out of Range.
RM: It sounds like the problem has been your PC's because I just tried
it with that Military file on my 300Mhz and 1000 Mhz machines with
identical setups of Jigsaw and found everything worked as it should.
I must add that there are a couple minor differences in the way the
two PC's handle Jigsaw at times, but I forget what they are now, but I
know that the faster PC does things better than the several of my old
slower (2nd hand) PC's have done in the past.
I've never bothered with new PC's because I always prefer Macs and
only got PC's for astrology programs originally.
I don't know who offers support for Jigsaw in Australia, and have
never sought any, although I have swapped a few emails with the very
helpful programmer Graham Dawson, who then lived only a few miles
away. That was in relation to my suggested improvements to Jigsaw for
handling the new Solar Fire Events.
There's actually a whole lot of (non-critical) things wrong with
Jigsaw but I've never pushed for any improvements because it looks
like a very limited market that couldn't afford a lot of extra expense
improving it. The solution for me for all of my novel improvements was
to write my own "Poor man's Jigsaw" as I call it to myself, although
it's got me stumped how the real Jigsaw goes so fast!!
Hi Ray,
Thanks a lot for doing that. I've tried it on about 5 different machines over the last few years always with the same result and with every version current at the time.
I'm sure you are right about the size of the market, but if it was the program I still thought they should have fixed it by now. When I first bought it I fortunately ran a test with some known data and found two different problems that gave the wroing results and they did a patch pretty quickly. If I hadn't done this I'd have gone a long way down the wrong track with my work. I also felt that they should have been a bit apologetic and appreciated that I'd done a bit of free testing for them.
With the current problem I get the feeling it is because it hangs up on the last request it did which is why it thinks its got parameters out of range. Also the fact that it clears if you go in and out of another chart factor. Could that be not enough RAM do you think ? I'm going to buy a laptop eventually and it'd be good to get one that doesn't do this.
Regards,
Graham.
--- On Sat, 29/8/09, Ray Murphy <raymu...@tpg.com.au> wrote:
On Aug 29, 7:06 pm, Graham Douglas <ondastropic...@yahoo.co.uk> wrote:
> Hi,
> Here is the decription of another annoying bug that I have been getting for a long time, in case anyone wants to try with their version. Please let me know what happens.
> By the way, who are you supposed to contact in Oz for JS support ?
> Over here its Roy Gillett who is always willing but some things need referring to the programmers.
> Graham.
[....]
>I open the file and go to Research--Criteria Search -- Moon Longitude, Zodiac Signs and select one sign. After running Search I save it as offered in a new file, and display the results using Research Graph and Tabulate. No problem so far. I quit qnd quit again to get out of this, and click back to Research Criteria Search where the previous selection is still highlighted in the List of Current Criteria, and the Division names are still as before. Now I click to highlight another zodiac sign without changing either the Data Type or Division Type and delete or clear the previously highlighted line in current Criteria. As soon as I then click Add for the new criterion up comes a box with Run Time Error 9, subscript Out of Range.
RM: It sounds like the problem has been your PC's because I just tried
it with that Military file on my 300Mhz and 1000 Mhz machines with
identical setups of Jigsaw and found everything worked as it should.
I must add that there are a couple minor differences in the way the
two PC's handle Jigsaw at times, but I forget what they are now, but I
know that the faster PC does things better than the several of my old
slower (2nd hand) PC's have done in the past.
I've never bothered with new PC's because I always prefer Macs and
only got PC's for astrology programs originally.
I don't know who offers support for Jigsaw in Australia, and have
never sought any, although I have swapped a few emails with the very
helpful programmer Graham Dawson, who then lived only a few miles
away. That was in relation to my suggested improvements to Jigsaw for
handling the new Solar Fire Events.
There's actually a whole lot of (non-critical) things wrong with
Jigsaw but I've never pushed for any improvements because it looks
like a very limited market that couldn't afford a lot of extra expense
improving it. The solution for me for all of my novel improvements was
to write my own "Poor man's Jigsaw" as I call it to myself, although
it's got me stumped how the real Jigsaw goes so fast!!
On Aug 29, 11:47 pm, Graham Douglas <ondastropic...@yahoo.co.uk>
wrote:
> Hi Ray,
> Thanks a lot for doing that. I've tried it on about 5 different machines over the last few years always with the same result and with every version current at the time.
> I'm sure you are right about the size of the market, but if it was the program I still thought they should have fixed it by now. When I first bought it I fortunately ran a test with some known data and found two different problems that gave the wroing results and they did a patch pretty quickly. If I hadn't done this I'd have gone a long way down the wrong track with my work. I also felt that they should have been a bit apologetic and appreciated that I'd done a bit of free testing for them.
> With the current problem I get the feeling it is because it hangs up on the last request it did which is why it thinks its got parameters out of range. Also the fact that it clears if you go in and out of another chart factor. Could that be not enough RAM do you think ? I'm going to buy a laptop eventually and it'd be good to get one that doesn't do this.
Hi Graham,
It sounds like it could be a ram problem - not that I really
understand ram on PC's like I do on Macs - where you can dedicate ram
to any given program. My 300MHz m/c has 192MB and the 1000 MHz m/c has
248 MB and I just noticed on the Esoteric Technologies site that
Jigsaw (with XP) should have a min of 128MB but they recommend 256MB.
XP needs 64MB to run minimally. Let us know how much ram you are
using.
I suppose it must be unnerving at times when you come across bugs in
the program and wondering if Jigsaw is doing all the calculations
right, but I've found on hundreds of occasions that the results match
my own program's output.
He confirms that the total box always has zero, and in fact that if you ask for % or anything but raw scores in tabular form you get a zero in every cell !
Best wishes,
Graham.
--- On Sat, 29/8/09, Ray Murphy <raymu...@tpg.com.au> wrote:
On Aug 29, 7:06 pm, Graham Douglas <ondastropic...@yahoo.co.uk> wrote:
> Hi,
> Here is the decription of another annoying bug that I have been getting for a long time, in case anyone wants to try with their version. Please let me know what happens.
> By the way, who are you supposed to contact in Oz for JS support ?
> Over here its Roy Gillett who is always willing but some things need referring to the programmers.
> Graham.
[....]
>I open the file and go to Research--Criteria Search -- Moon Longitude, Zodiac Signs and select one sign. After running Search I save it as offered in a new file, and display the results using Research Graph and Tabulate. No problem so far. I quit qnd quit again to get out of this, and click back to Research Criteria Search where the previous selection is still highlighted in the List of Current Criteria, and the Division names are still as before. Now I click to highlight another zodiac sign without changing either the Data Type or Division Type and delete or clear the previously highlighted line in current Criteria. As soon as I then click Add for the new criterion up comes a box with Run Time Error 9, subscript Out of Range.
RM: It sounds like the problem has been your PC's because I just tried
it with that Military file on my 300Mhz and 1000 Mhz machines with
identical setups of Jigsaw and found everything worked as it should.
I must add that there are a couple minor differences in the way the
two PC's handle Jigsaw at times, but I forget what they are now, but I
know that the faster PC does things better than the several of my old
slower (2nd hand) PC's have done in the past.
I've never bothered with new PC's because I always prefer Macs and
only got PC's for astrology programs originally.
I don't know who offers support for Jigsaw in Australia, and have
never sought any, although I have swapped a few emails with the very
helpful programmer Graham Dawson, who then lived only a few miles
away. That was in relation to my suggested improvements to Jigsaw for
handling the new Solar Fire Events.
There's actually a whole lot of (non-critical) things wrong with
Jigsaw but I've never pushed for any improvements because it looks
like a very limited market that couldn't afford a lot of extra expense
improving it. The solution for me for all of my novel improvements was
to write my own "Poor man's Jigsaw" as I call it to myself, although
it's got me stumped how the real Jigsaw goes so fast!!
> He confirms that the total box always has zero, and in fact that if you ask for % or anything but raw scores in tabular form you get a zero in every cell !
RM: Yes, but think of the publicity for the program if it gets shown
on "Ripley's Believe it or not" - you know, a summary you're having
when you are not having a summary of birth data :-))
> He confirms that the total box always has zero, and in fact that if you ask for % or anything but raw scores in tabular form you get a zero in every cell !
RM: Yes, but think of the publicity for the program if it gets shown
on "Ripley's Believe it or not" - you know, a summary you're having
when you are not having a summary of birth data :-))
On Aug 30, 9:27 am, Graham Douglas <ondastropic...@yahoo.co.uk> wrote:
> Hi Ray,
> Sorry don't get the joke here, can you explain about Ripley's ?
I was just thinking how unbelievable it is - 15 years of displaying
tables
in a research program that allegedly display:
* Proportion of total
* Percentage of total
* Proportion of average
* Percentage of average
for
* Birth hours
* Birth years
* Birth latitudes
* Birth longitudes
and all we have ever seen displayed for 15 years is 6292 zeros
in those 4 displays combined, AND (believe it or not) there's
only a few astrologers on the planet who think this is abnormal
and needs fixing.
Hi Ray,
Absolutely, I wonder what most of them use it for.
Keep up the good work,
Graham.
--- On Sun, 30/8/09, Ray Murphy <raymu...@tpg.com.au> wrote:
From: Ray Murphy <raymu...@tpg.com.au>
Subject: Re: Fw: JS2 problems
To: "Tropical Astrology Research" <tropical-astrology-research@googlegroups..com>
Date: Sunday, 30 August, 2009, 5:52 AM
On Aug 30, 9:27 am, Graham Douglas <ondastropic...@yahoo.co.uk> wrote:
> Hi Ray,
> Sorry don't get the joke here, can you explain about Ripley's ?
I was just thinking how unbelievable it is - 15 years of displaying
tables
in a research program that allegedly display:
* Proportion of total
* Percentage of total
* Proportion of average
* Percentage of average
for
* Birth hours
* Birth years
* Birth latitudes
* Birth longitudes
and all we have ever seen displayed for 15 years is 6292 zeros
in those 4 displays combined, AND (believe it or not) there's
only a few astrologers on the planet who think this is abnormal
and needs fixing.
|
