CompuServe Thread

Grabbit

6 messages in this thread
#83899From: Alan KaiserSep 6, 1987 10:05 PM
I tried to engage Grabbit tonight and was told it couldn't find printer.device by Grabbit. I looked in sys:devs and there it was. I even printed off something and it loaded fine then. I did get it to work by using my original WB copy, tho. So…has anyone encountered this before? Is there anything that interfers with Grabbit? I intend to copy the files off that wb disk onto another and see what happes. Thanks, Alan
#84273From: Mike SchulteSep 8, 1987 7:03 PM
If memory serves me correctly, that happened to me once, and I think the problem turned out to be there wasn't a large enough hunk of memory for the driver to load into. This was several months ago, so don't qoute me on it. If you run into the problem again you might want to run "frags" if you have it, to see what size memory chunks are free.
#84300From: Alan KaiserSep 8, 1987 10:07 PM
Whoa…frags?? I rebooted 3 times so there couldn't be a lack of free mem…. could there? I have pieced the diffs between the last time I used Grabbit and this time and it was the addition of MoreRows to the config and Run to Ram:. Alan
#84555From: Mike SchulteSep 11, 1987 11:47 AM
frags is a program that lists how many blocks and of what size the free memory is present as. Just having say 50k free doesn't mean that a program that uses 45k will load. But, right after you reboot most of the free memory will be in one large block unless your startup-sequence runs quite a few programs before it lets you have the cli (or workbench). Like I said before, it was a long time ago I had that problem, and I just can't remember what the problem was. Does your startup-sequence do any assigns that might make it impossible for Grabbit to find the disk files it needs?
#84618From: Alan KaiserSep 11, 1987 9:25 PM
Nope! Just a simple assign for my ram:c stuff. Basicly with a 512k machine I just load the basics to ram and avoid running programs that would eat ram or scatter things. I haven't messed with it since, but thinking about it, I would wager the MoreRows screen adjustment might be the culprit. Alan P.S. SYSOPs: I uploaded MoreRows after making sure none of the DLs contained "MoreRows". Either it was lost in the shuffle, ignored, or there is a copy of it uploaded, but under a false name. What gives?
#84665From: John DraperSep 12, 1987 3:46 AM
Alan, Morerows was uploaded on Feb 28th, and is in DL 9 as MOROWS.ARC Regards, Larry.