CompuServe Thread

#Apassist

11 messages in this thread
#98074From: Steve SetzerJan 3, 1995 11:10 AM
Ben, The test version of apassist just placed in the libraries works great (so far) but apassist still HAS to be in c: to work. I use a cx: for all non CBM commands, it is in my path and works great for 95% of whatever I put there but IM R/T and Autopilot does not find it (apassist) in cx:, it must be in c:. Is this a known condition? ..Steve ====>>> Motorola 68030 Inside <<<====
#98105From: Black Belt SystemsJan 3, 1995 2:25 PM
Steve, It's probably being called as "c:ApAssist". I don't recall offhand, but that would fit what you describe. –Ben …via AutoPilot
#98181From: Steve SetzerJan 4, 1995 5:55 PM
Ben, Is a problem with Apassist or the calling program? Can it be fixed, ie env. variable, tool type ect? Not very important but usefull. ..Steve ====>>> Motorola 68030 Inside <<<====
#98192From: Black Belt SystemsJan 4, 1995 11:54 PM
With the calling program. ApAssist can be run from anywhere.
#98226From: Steve AhlstromJan 5, 1995 3:35 PM
Not necessarily correct (tho not ApAssist's fault either). AutoPilot calls ApAssist with … sprintf(li, "run ApAssist %s", nt); ret = system(li); /* Attempt to start ApAssist */ More recent versions of AmigaDOS appear to have a problem with the PATH command. If you do not put ApAssist in c:, but do have its location in your path, it will not be found. However, if you assign that location to c: with the "add" modifier, it will be found.
#98244From: Black Belt SystemsJan 6, 1995 1:52 AM
Really… very interesting! I never tried to make a new C:, I just kept jamming stuff in there – it always worked, so I never had to "fix" it. 🙂 Well there you go. AutoPilot's doing the right thing, ApAssist doesn't care one way or the other, and AmigaDOS is biting the guy. Life is strange.
#98229From: Peter GreciJan 5, 1995 4:09 PM
"With the calling program. AppAssist can be run from anywhere." REALLY? how about in the dead sea at say 200 Fathoms on a rainy night 😉 Sorry Ben couldn't resist BTW has Winimages 3 begun shipping yet? Also quick question does it support any sort of Virtual Memory like Imagemaster does? or better yet does it have it's OWN Virtual RAM system? Twould be GREAT to work with it and PhotoCD images for touchup and then send it back out to Film 😉
#98245From: Black Belt SystemsJan 6, 1995 1:52 AM
WinImages 3 has NOT begun shipping yet. When this GIF thing began to break, we were about to go – then held back a couple of days to see what was going on, then a couple more… then one of our major customers got wind of some of the things we were putting in R4, and begged us to put them in R3… they were done and working, and so we gave in. 🙂 That gave us a few more days to consider the "GIF thing", and it upgrades the R3 version – which is a good thing, because R3 is going to ship _without_ GIF support, due to the Unisys legal position. A long answer for a simple question. R3 will go out the door next week. Definitely. WinImages uses Windows built-in virtual memory, so yes, that support is in there, you bet – works fine. And it works well with images taken from PhotoCD's – and they look pretty good, at least the hires ones do.
#98250From: John Toebes/SYSOPJan 6, 1995 7:30 AM
Will I like it? 🙂 <waving>
#98296From: Black Belt SystemsJan 7, 1995 1:18 AM
Oh yeah, you will. 🙂 <Waving Back> –Ben …via AutoPilot
#98278From: Peter GreciJan 6, 1995 3:40 PM
COOL!! Thanx Ben. Can't wait to see it!!!! Member of the Association of Media Professionals