#SAS from Workbench trble
39 messages in this thread
Okay, I give up. Has ANYBODY been able to get the SAS_C upgrade to Lattice
to work from Workbench? It works great from the CLI, but while I've got
lots of pretty icons, all I can do so far is invoke CED on the source
files. (Thanks to ASDG for LtoCED 🙂
I invoked lc:sascsetup as per the written instructions, and got all of the
icons set up.
The build icon opens a window and then closes it too fast for me to see any
error messages. Needless to say, contrary to the docs it doesn't invoke
LMK or LC on anything. I tried selecting the icon for my lmkfile and then
shift-clicking on the build icon, but that just invokes CED on my lmkfile.
<grin>
The options icon seems to work, but it has a bug. The extra include
directories are written into the SASCOPTS file as '-I<dir>', when the docs
say it should be '-i<dir>'. The capitalization seems to make a difference.
Anybody know from this brief description whats wrong??
Thanks in Advance!!!
Kev "300,000 km/sec – It's not just a good idea, its the law!"
Kevin
I have not had too much trouble getting SAS/C working from Workbench.
I'm not shure what your trouble is from your description. I guess you
should check the simple things first. 1) Do you have the 4 ASSIGNments in
your S:Startup-Sequence file
(LC: LIB: INCLUDE: and QUAD:)
and don't forget the "Path SYS:lc/c Add" line (assuming you have put
the lc directory in SYS:) 2) My build icon has LC:LMK in the DEFAULT
TOOL line. I simply double
click on build, with only one program file (.c) in the drawer it seems
to work ( I am about to find out soon what happens with a bunch of
source files in the drawer, but I haven't tried it yet) 3) I have found
I can most of the time catch the windows from slamming
down too fast by hitting the menu button (the right mouse button)
immediadely after double clicking on build. That freezes the window
until I relese the button. Also some error messages from some programs
will appear in the workbench screen title bar (I think that is if it
results from some system errors like file not found). Anyway try to
check the title bar, it may give some clue as to what's happening
(maybe).
Unfortunately I haven't messed with the include stuff in the options
icon to understand anything about that.
Wish I could be more help. If the first round of suggestions don't help
you can always come back for more. Eventually someone will probably figure
out what is or isn't happening.
Herbert L. Crowder
Herbert,
Taking your suggestions in order:
1) Checking the required assignments and paths was the first thing I
looked at!
2) I haven't tried BUILD with only one source file, I had run SASCSETUP
on an existing project with about 10 – 15 source files. I'll try it
tonite! Of course, that still doesn't explain why BUILD didn't use my
lmkfile!
3) I'll try the right mouse button trick tonite! After posting my
message last night, I was (after dozens of tries) able to make out the
error message that pops up as saying something like "Can't find Workbench".
Since Workbench was definitely loaded and running, I don't understand that
one! (Hmm, could it be SetCPU changing the name to FastBench thats the
problem???)
Thanks for the suggestions!
Kev "300,000 km/sec – It's not just a good idea, its the law!"
Kev… isn't that "299,820 km/sec" ???? <grin>
Ben
Amateur Radio Callsign is A A 7 A S
Ben,
<In best Maxwell Smart voice :>
"Would you believe rounding error got the better of me?"
Kev "300,000 km/sec – It's not just a good idea, its the law!"
Nah. In free space, 300,000 km/s is cool. Here on Earth, with Don watching
you, you gotta figure in velocity factor and go for just a *little* bit
slower. :^)
"I'm sorry sir, you were 180 km/s over the limit. We'll have to go see the
judge"
<running away, laughing>
Ben
Amateur Radio Callsign is A A 7 A S
Ben,
But at 300,000km/s you can't see the judge! He/she will be blue or
red shifted out of existance! <grin>
Don
Red shifted, to be exact. The judge would become a radio wave. 😎
— Ethan
and the traffic cop would never be able to catch up with you, since he
could never exceed c, unless he were a tachyon, then he couldn't sto
Ethan,
Nope…the judge would be red shifted if you were travelling away
from the judge. Blue shifted if traveling towards the judge.
Don
To Whoever suggested inserting the path LC: command before calling the
WorkBench, THANKS! That turned the trick, and I have no problem with using
LSE from the WB anymore.
Steve Eckhart
I thought I said red-shifted. I don't remember and I'm too lazy to check
through the message base to check! 8) Besides, this isn't all that
relevant.
— Ethan
We were trying to run away from the judge, I believe. If the fine is
based on how much over the speed limit you were traveling…
— Ethan
"Ignorance of the law is no excuse"
and…
the law always ins in the end. :^)
Ben
Amateur Radio Callsign is A A 7 A S
Now, if the judge is going the same speed as the speeder, one would have no
problem seeing same. And if said judge was going 299,820, as per the rules,
and the speeder was going 300,000, likely there would be little trouble
spotting the culprit, eh? I mean, we're talking less than a third of a
percent of lightspeed, with a log effect. :^)
Ben
Amateur Radio Callsign is A A 7 A S
Ben,
If you've ever been in a courtroom…you KNOW no judge moves fast.
Don
Yes, I know. :^) I had a "very interesting" divorce, once.
Ben
Amateur Radio Callsign is A A 7 A S
Ahh, but the problem is that the judge is moving at near-c as well! This
is, of course, the real reason behind the _perceived_ slowness of the
judicial system in America! 😉
Kev "300,000 km/sec – It's not just a good idea, its the law!"
I thought the sign said 669600000 MPH (honest officer 🙂
Greg
Kevin;
Sounds like you don't have the path command set.
73, bill
Bill,
The assignments and paths were the first thing I checked! Thanks for the
suggestion!!
Kev "300,000 km/sec – It's not just a good idea, its the law!"
Kevin;
OK, but I suggested checking the path because that is precisely what I
failed to do that resulted in my experiencing the behavior you are seeing.
73, bill
Bill, John Toebes gave me the solution! It seems that SetCPU was renaming
the Workbench screen to Fastbench, which kept the software from working.
The fix was simply adding "NOPATCH" to the SetCPU argument line. The bad
part is of course that now my drives are clicking again. 🙂
Kev "300,000 km/sec – It's not just a good idea, its the law!"
Let me guess… You have a 2500 (or equivalent) and am running with SETCPU
FASTROM If this is so, just change it to SETCPU FASTROM NOPATCH and
everything will work. The problem is that Setcpu changes the name of the
workbench task to fastbench and makes it so that LMK can not find the path.
THere are other programs that have the same problem but with slightly
different symptoms. If this doesn't help, please feel free to call SAS/C
technical support at (919) 677-8009.
John,
I'll try that right now, hold on a sec . . .
OK, that fixed it!! The BUILD icon works now, just as advertised!
Thanks a lot John!
Kev "300,000 km/sec – It's not just a good idea, its the law!"
Great. I'm glad that I could help out.
John,
I am curious, though, as to why no mention of this was in the docs. SetCPU
seems to me like a very common piece of an accelerated machines package.
Well, as you know, all's well that ends! <g>
Kev "300,000 km/sec – It's not just a good idea, its the law!"
SetCPU is "unofficial" software, and as such is a "use at your own risk"
item.
Ben
Amateur Radio Callsign is A A 7 A S
Very true about SetCPU being "unofficial" software, Ben. My comment was
meant to say "I don't know of anybody with an accelerated Amiga who ISN'T
using SetCPU" and to express my surprise that the testers at SAS apparently
aren't using SetCPU.
Clear as Mud?? <g>
Kev "300,000 km/sec – It's not just a good idea, its the law!"
I don't use SetCPU. It made both my 68020 and 68030 accellerators crash the
system if I simply set the fastrom option. After a few days of constant
crashing, I took it out and now have a stable system again.
My system seems to be 100% stable if I stick with the standard CBM
commands, toss all the ARP stuff, and don't open more than one interlace
screen.
Ben
Amateur Radio Callsign is A A 7 A S
Ben,
Hmm, very strange!
My system is a GVP 68030, 5MB RAM, FlickerFixer, using ARP 1.3, and the
latest WShell and ARexx (and a host of other things! Its nice to work for
a company that uses Amigas! 🙂 and I haven't had any problem with SetCPU.
The hardware has been stable for about 10 months now, and the software has
been stable for just about as long (not counting periodic upgrades, or the
stuff I wrote myself :).
Kev "300,000 km/sec – It's not just a good idea, its the law!"
Mine is CBM 030, 5mb ram, and flicker fixer. Crash city. :^(
Ben
Amateur Radio Callsign is A A 7 A S
Very Wierd, Ben. What version of the motherboard do you have? Mine is
6.2, I believe.
Kev "300,000 km/sec – It's not just a good idea, its the law!"
Because we always have run SETCPU with the NOPATCH option for all the other
software that was broken by it. Even Commodore has recommended that you
use the Nopatch option because it affects the SHELL icon from workbench.
We test it in as many environments as possible as well as let a large
number of beta testers run the software. Nobody reported the problem in
the beta stage that I was aware of.
Ah, that explains why nobody saw the problem! In any case, as noted
elsewhere in this thread, the latest version of SetCPU (v1.6) doesn't cause
this problem anymore.
John, thanks for taking the time to explain this!
Kev "300,000 km/sec – It's not just a good idea, its the law!"
No problem. I was just glad that I could help out.
Kev,
You could also do what I did, Zap SetCPU to change the occurance of "Fast"
to "Work", but leave the string "FastBench release…" alone in SetCPU.
This way you still get some mention of FastBench when on the WorkBench
screen and you can let SetCPU perform the patches (and no more noisy drive
clicks)!
73, Kelly
Kelly,
Hmm, I'll try to zap it today. In fact, one of my co-workers just
suggested the same thing. I guess I'm just a little bit leery of zapping
other peoples code! 🙂
Kev "300,000 km/sec – It's not just a good idea, its the law!"
Didn't SETCPU 1.6 correct this? When I was using 1.5 my title bar said
"FastBench release". However now that I'm running 1.6 my title bar says
"WorkBench release". I changed nothing in my s-s. I'm just using "SetCPU
FastROM".
Greg
Greg White / MicroSearch 72230,1617
We listen to our customers..carefully