CompuServe Thread

#LSe from WB

20 messages in this thread
#4022From: Kelly JordanNov 23, 1990 9:18 PM
I am trying to run LSE version 2.10 (the version that came with the 5.10 SAS upgrade) from WorkBench. Every time the program starts up, the message "Not enough memory to start LSE" comes up in a little window on the LSE window, then goes away after a few seconds. All the menu selections are ghosted and the close gadget does nothing. Everything works fine when LSE is started from the CLI (actually from AmigaShell via an alias). I know some people are going to suggest a different editor (grin), but I like the ability to call up the compiler and read error messages (which I get a fair amount of!) from within LSE. Is the ability to run LSE from WB meant to be a 2.0 only feature? 73, Kelly
#4023From: David ArtNov 23, 1990 9:41 PM
Kelly, I just tried it and LSE did startup OK for me by clicking on its icon. Is it possible that one of the assigns is missing? David
#4041From: Kelly JordanNov 24, 1990 9:05 AM
David, The assigns appear correct. Thanks any way. 73, Kelly
#4193From: John DraperNov 27, 1990 12:29 AM
Kelly, Have you checked to see if anything strange is in the icon (via the INFO selection). For example, if you have a large stack value set, it could cause something like you describe. -larry
#4458From: Kelly JordanNov 30, 1990 6:55 AM
Larry, I checked the icon. The stack is set at 8192 (I tried changing this from 4000 to 50000 with no change). The default tool is set to LC:LSE, and LC: is set to the c directory the SAS install script makes. I also have a copy of LSE in my C: directory, so I changed the tool to C:LSE – same thing; even typed in the path lc: represents the long way (dh2:lc/c/LSE) and the results are the same. No hair left where I pound my head against the desk! 73, Kelly
#4529From: John ToebesDec 1, 1990 12:00 AM
I'm comming in on the middle of this discussion so I don't know the question (and am having trouble navigating here to figure it out – help!) but if it is what I suspect – you can't seem to find LSE – there is a simple thing that you can do to make it right. Just make sure that LC: is in your path BEFORE you do the LOADWB. Don't do it in a StartupII because that sets a different environment. If you are still having trouble, don't hesitate to contact SAS/C technical support at (919) 677-8009.
#4556From: Kelly JordanDec 1, 1990 8:24 AM
John, I found the problem – the cause was what you suggested to Kevin – LSE is looking for WorkBench and I was running SetCPU 1.5 with the PATCH enabled – but there was no way I was going to do NOPATCH (I can't stand listening to the clicking drives), so I Zapped LSE to change the two occurances of WorkBench to FastBench. I guess I will have to do this to LMK if I ever get far enough to using it. I am not going to worry about undoing these changes until WB 2.0 becomes official in ROM. But since you came in the middle of the discussion (what there was of one), the problem was LSE would come up, but then report it doesn't have enough memory to start LSE, the program would have all the menu items ghosted, wouldn't listen to the close gadget, and the system would become very unstable. Hope we see more of you on here, John. One happy camper now… 73, Kelly
#4571From: John ToebesDec 1, 1990 4:48 PM
You would be better served to Zap setcpu so that it doesn't change the name from WorkBench to FastBench. That makes it work for other things too. Also remember that LMK and LC will also do the same thing. I will try and pop in once in a while, but time is limited. Other things are afoot too…
#4598From: Kelly JordanDec 2, 1990 6:01 AM
John, After Zapping all the SAS/C executables that have the string WorkBench to FastBench, I decided to change them all back to WorkBench and Zap SetCPU (1.5) so the internal change it makes to change the string "Work" to "Fast" was changed so it changes it to "Work", and I still have my FastBench title on WorkBench! Thanks again.. 73, Kelly
#4772From: John ToebesDec 5, 1990 6:20 PM
This is a wise choice – especially in light of the 5.10A patch that is now available.
#4800From: Bob RakoskyDec 5, 1990 11:39 PM
John, Will SAS ship the patches to me if I call the support line? I don't have an account on that other network, so I can't get them from there. Thanks. …BobR
#4817From: Don Curtis/SYSOPDec 6, 1990 2:21 AM
John, How is/are the patches being distributed? Must I get it from SAS by calling them or is it possible for you to post them here? I presume they are of no use to anyone who doesn't already have 5.1, so there should be no worry about the software getting into the hands of folks who didn't buy it. Don
#4942From: John ToebesDec 7, 1990 7:05 PM
SAS Institute will ship the patches if you call them. I am also uploading them here tonight for everyone on Compuserve to get access to them.
#4974From: Betty Clay/SYSOPDec 8, 1990 12:27 AM
John, Thanks for uploading them here. It is SO much easier to just download them – not to mention faster! Betty
#5003From: John ToebesDec 8, 1990 9:49 AM
You are welcome. We try to please.
#5004From: John ToebesDec 8, 1990 9:50 AM
Now if only Whap! worked on a 3000 I might be able to get on here more often… hint, hint steve…
#5029From: Betty Clay/SYSOPDec 8, 1990 9:35 PM
Lotsa requests for that, John. And if Steve's 3000 will just hurry and arrive, I suspect it will come faster than you think. Betty
#5039From: Steve AhlstromDec 9, 1990 12:31 AM
John, Still waiting for my 3000. I was supposed to get it today, but, since my dealer's giving it to me at cost, and he had a customer come in with cash in hand, he sold "my" machine to the customer. I'll have to wait 'til next week for another 3000 shipment to come in. I'm not getting it thru the dev program because I really can't afford the 3000 right now but my dealer is giving me $1500 for my 2000 — so, the price works out to be about the same ('cept I gotta pay sales tax) and balance is a bit more affordable. -sja
#4993From: Don Curtis/SYSOPDec 8, 1990 2:06 AM
John, Great! Thanks for uploading them. Don
#5096From: Michael McCormickDec 9, 1990 8:27 PM
Hi John, I downloaded and patched 5.10 to 5.10a just fine. Thanks for uploading the current patch. Keep up the good work! MikeM:)