CompuServe Thread

#Metascan Won't Load

25 messages in this thread
#81886From: Richard GraffMay 13, 1994 9:58 PM
Ben, When I try and use the scanning software with IM v1.50B, after selecting the module, I get sent back to the main IM screen instead of to the MetaScan screen. I re-installed v1.06r2 just to make sure that there wasn't anything wrong my hardware and the scanning software worked fine. The I re-installed v1.50B from scratch and still the scanning software wouldn't load. Any ideas? =Rick=
#81899From: Black Belt SystemsMay 13, 1994 11:30 PM
Ummm… out of memory? –Ben …via AutoPilot
#81925From: Dick SchnaseMay 14, 1994 10:57 AM
Ben>Ummm… out of memory? I sure like the way you guys addressed the 'Lowest common denominator' question regarding memory in the tapes. It has been my feeling for a long time that the LCD attitude among developers (except gammers) is/was a detrement overall to the Amiga community. Coding every application for the 2 MB machine with no hard drive really leaves a great number of people frustrated.
#81994From: Black Belt SystemsMay 15, 1994 1:19 AM
I think you're right. In fact, you can see numerous examples in CBM's behaviour with the Amiga system that contributed a great deal to the lack of serious software: Some things that come immediately to mind are the NON installation of ARexx on released systems, even recently; the lack of Amigas with hard drives, standard, for way way too long… things like that. I guess it's no longer a problem, though. –Ben …via AutoPilot
#82081From: Richard GraffMay 15, 1994 7:53 PM
Ben, I have 10 megs on my A1200, is that not enough memory? Plus, Metascan works fine with version 1.06R2 of IM, it just won't work with the 1.50B version I received recently. =Rick=
#82083From: Richard GraffMay 15, 1994 8:15 PM
Ben, Just to clarify how much memory I have available before running IM: Chip: 1,862,072 bytes Fast: 6,562,216 bytes Should that be enough to use the scan function? I'll try and call tech support tommorrow afternoon if I get home early enough. =Rick=
#82105From: Black Belt SystemsMay 15, 1994 10:33 PM
Rick, That's not all that much memory, really – depends totally on how big the area you are trying to scan. Let's say that you're scanning a 678×480 image. That's 768x480x4 bytes for the image, and 768x480x4 bytes for the undo buffer, if you use one. Which turns out to be 1.47 megabytes each, for a total of 2.94 megs. TO this you add the memory that IM takes, the memory that Metascan takes… and 10 megs might not be enough. Some scans are MUCh larger than 768×480; it's just a flick of the wrist to scan an image that would take ten megs all by itself. –Ben …via AutoPilot
#82169From: Richard GraffMay 16, 1994 2:28 PM
Ben, But I haven't even got to the point of being able to define a picture to scan becuase Metascan won't load after I select the epson scanner driver. Oh well, I guess I need to call tech support. =Rick=
#82174From: Richard GraffMay 16, 1994 3:50 PM
Ben, Ok, After a call to your tech department, the problem has been solved. I have been launching IM from Toolmanager and it seems that between version 1.06 and 1.5 you guys tightened up the path/assign requirements. If I launch IM from its icon, the scanning software works fine, however from Toolmanager it does not. Your tech guy (Dave) thinks that ToolManager is "swallowing" up the necessary assigns and/or paths. I guess i better dust off the Toolmanager DOC's and see if I can work around this. If you or anyone else has IM 1.5 worrking with toolmanager I would appreciate your imput. =Rick=
#82295From: Black Belt SystemsMay 18, 1994 12:11 AM
Hum – toolmanager, huh? And what, exactly, is Toolmanager? –Ben …via AutoPilot
#82305From: Richard GraffMay 18, 1994 8:06 AM
Ben, ToolManager lets you run programs from workbench via Dock Icons or by adding the programs to the Tools pull down menu of workbench. I have a dock Icon setup for IM to launch it from, but when I run IM from it it doesn't run properly, I didn't have this problem with the 1.06 version. I can specify that the program be run from workbench, or CLI, can add a path and default drawer, but I can't seem to find the right combination to make it work. Oh well, I guess I can always just "leave Out" the IM Icon, btw, ToolManager is in the Amigauser forum library. =Rick= – Richard Graff, Written 18-May-1994 @ 08:29:42 Using: Windows NavCIS TE 1.2
#82329From: Stephen BaileyMay 18, 1994 1:55 PM
Are you sure Toolmanager is in the AmigaUser library. I know there are many support archives for it there, but I had to get my copy from a local BBS, because the actual software wasn't available here. I think it's on a Fish Disk, but I'm not sure which one. A search would give you the number. Stephen Bailey Sawyer & Bailey Film and Video CIS # 72773,2451
#82401From: Richard GraffMay 19, 1994 7:21 AM
Stephen, In Lib 15 of AmigaUser: TM21.LHA (ToolManager 2.1 archive) – Richard Graff, Written 19-May-1994 @ 08:14:56 Using: Windows NavCIS TE 1.2
#82404From: Black Belt SystemsMay 19, 1994 9:10 AM
I see. What is (probably) happening is that ToolManager isn't passing along the WorkBench paths. IM R/t has some CBM-supplied code in it that captures the host paths from the workbench in a rather indirect manner; this is probably broken by ToolManager. It's *very* unfortunate, but when programs (such as IM R/t) are launched from the WorkBench, they do not get the path information that WorkBench itself was launched with from the shell. This is a crippling shortcoming of AmigaDOS. The workaround in Imagemaster is fragile – and there's not much we can do about it. –Ben …via AutoPilot
#82437From: Stephen BaileyMay 19, 1994 2:06 PM
PMFJI, but I run IM r/t 1.5 from a ToolManager icon all the time. No apparent problems I can see (except for that printing problem I asked about the other day…maybe that's related???). Anyway, just thought I'd chime in… Stephen Bailey Sawyer & Bailey Film and Video CIS # 72773,2451
#82634From: Black Belt SystemsMay 22, 1994 1:12 PM
Can you run ApAssist? And if so, what version of the OS are you running? (This is in regard to using toolmanager) –Ben …via AutoPilot
#82720From: Stephen BaileyMay 23, 1994 4:57 PM
ApAssist works fine. I am running WB 2.1. Stephen Bailey Sawyer & Bailey Film and Video CIS # 72773,2451
#82832From: Charles BlaquiereMay 24, 1994 9:42 PM
If the problem is related to Imagemaster's knowledge (or lack thereof) of its environment, why not have Toolmanager launch a small AmigaDOS script file? The script could simply 'cd' to the desired directory, set the stack, and call IM. Blaq!
#82950From: Black Belt SystemsMay 26, 1994 12:53 AM
Sounds like it might work – but it's not me with the problem. :^) –Ben …via AutoPilot
#82349From: Peter GreciMay 18, 1994 4:08 PM
d
#82359From: Vic WagnerMay 18, 1994 6:41 PM
Ben, Toolmanager is a 3rd party 'hang on' which caused us no end of difficulties when putting MetaScan together. Our main beta tester was using it from time to time and all sorts of things didn't wanna work.
#82406From: Black Belt SystemsMay 19, 1994 9:10 AM
Thanks, Vic – it appears to be eating the WorkBench paths (such as they are). –Ben …via AutoPilot
#82644From: Vic WagnerMay 22, 1994 3:08 PM
Ben, Yup, that's the conclusion we came to, tho I think it actually keeps all the WB paths that exist at the time it's run (I don't recall).
#82365From: Steve SetzerMay 18, 1994 8:14 PM
Ben, Richard explained ToolManager pretty well so I won't say further on it except it is an EXTREMELY popular program. As I am still on 1.06 myself I cannot attest to 1.5 problems but I do run 1.06 from ToolManager too. …Steve ====>>> Motorola 68030 Inside <<<====
#82407From: Black Belt SystemsMay 19, 1994 9:10 AM
Thanks, Steve. I guess I'll have to say that running IM R/t from ToolManager is a bad idea at this point. –Ben …via AutoPilot