#Help Doesn't
9 messages in this thread
Ben:
Did you ever duplicate and solve the error involving the help feature of
IM? The error message was:
Can't open file imh_toc
Which I received when trying to do a "find."
This is VERY annoying when one is trying to get information on an aspect
of IMRT!
Right now I have several "locked" buffers and I'll be darned if I can
figure out:
1) How the buffers got locked
2) What this means
3) What to do to unlock the buffers
I looked in the Index under "buffers" and "locked" with no success in
resolving this situation.
The exit IM button is ghosted so I guess I'll have to re-boot to clear
this little problem.
So….
1) Did you duplicate and fix the problem? Can I get the fix?
2) How do buffers get locked and how do I unlock them?
3) How do I un-ghost the exit button?
-J
1 – probably – there are no known bugs in ApAssist at this time. But best
bet for a specific answer is as for 2 & 3…
2 & 3 – this is a complex set of questions that I'm not well prepared to
answer, online or not. Best bet is to call our technical support people at
(406) 367-5509 between 9-11 & 1-5 MST. They've got the complete list of
bugs, etc, that have been fixed to date, as well as the best hands-on feel
for things like locked buffers (which are usually, if I recall, the result
of PI modules that failed in a catastrohic manner which is almost always,
again, a low memory problem). The tech support people should be able to
step you thru these issues one at a time and give you the best possible
answers.
I'm much better at usage questions – I use IM R/t in a big machine (lots
of memory, etc) and I very rarely run into problems, so I'm not so hot at
diagnosing them anymore
.
–Ben
…via AutoPilot
Ben,
I'm having the same problem as Jay when using ApAssist's find function.
Works O.K. when searching "this document" or "loaded context" but when
searching the "entire database" it can't find the database. Seems IM looks
for files first by name then by name and path. When looking for the
"entire database" files, it looks only by name twice and then fails.
Sample SnoopDos report:
ApAssist Open aa_help OLD Fail
ApAssist Open IMDOC:aa_help OLD Okay
ApAssist Open bb_help OLD Fail
ApAssist Open IMDOC:bb_help OLD Okay
ApAssist Open imh_changes OLD Fail
ApAssist Open IMDOC:imh_changes OLD Okay
ApAssist Open imh_deinstall OLD Fail
ApAssist Open IMDOC:imh_deinstall OLD Okay
ApAssist Open IMRT_Manual OLD Okay
ApAssist Open imh_toc OLD Fail
ApAssist Open imh_toc OLD Fail
ApAssist Open imh_index OLD Fail
ApAssist Open imh_index OLD Fail
ApAssist Open hlp_toc OLD Fail
ApAssist Open hlp_toc OLD Fail
ApAssist Open hlp_index OLD Fail
ApAssist Open hlp_index OLD Fail
ApAssist Open clips/logo.pic OLD Fail
-Richard
Richard,
What version of ApAssist is this? The menu entry will tell you.
–Ben
…via AutoPilot
Ben,
I'm off to a good start in IM. I have the video which is tuned to 1.06 (I
think that is the version) and since mine is new, it is 1.50c. In the
portion of the tutorial about the palette, the video shows an area where
you can test out like an air brush (that's what is shown in the video).
I haven't found such an area in my version. Set me straight, please.
Thanks. L8r.
The video shows the palette for the OpalVision (which I think he does
mention in passing) The palette airbrush area is only available in AGA,
FC24 and OpalVision. That's not a difference between 1.06 and 1.50; it's a
difference between retargeted displays.
We had some serious difficulty trying to get that working in the std Amiga
grfx modes. :^(
–Ben
…via AutoPilot
Version 2.0. I believe it was installed with IM 1.5.
-Richard
OK, I guess I'll try and get in touch with tech support some time when I
get home in time.
-J
Jay,
I looked at the JPEG and the file is nonstandard – quite radically so.
There are undefined markers within the image body, and that is a Very Bad
Thing.
Some people just think it's ok to screw up a working format.
–Ben
…via AutoPilot