Path: utzoo!mnetor!uunet!husc6!mit-eddie!ll-xn!ames!pasteur!ucbvax!FINTUVM.BITNET!FYS-MA From: FYS-MA@FINTUVM.BITNET (Matti Aarnio) Newsgroups: comp.sys.amiga Subject: Locked PRT: after reboot & GURU w/ MoveWindow Message-ID: <8802171935.AA19878@jade.berkeley.edu> Date: 17 Feb 88 13:31:49 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 57 Date: Tue, 16 Feb 88 14:59:00 PST From: Tom Gilheany Subject: Locked PRT: after reboot & GURU w/ MoveWindow [[ We have a Amiga related technical group running on bitnet, and this is question, where I hope you USENET-landians could help us. Post your answers, or mail them to me. Either way, our group will receive them in due time. /Matti Aarnio (co-owner/feed moderator of I-AMIGA -list on BITNET) ]] -----------------[Locked PRT: problems after Re-Boot]------------------------- The other day, I went to copy a text file to PRT: using CLI, and got the message object in use (it had apparently been locked by a program which was unable to free the lock). I re-booted the system, typed CTRL-D to wind up in CLI and tried the file copy again. Still got the error message "object in use" (i.e. it was still locked, even though nobody was using it). Apparently, since the printer device is disk-resident, there must be someplace on the WB disk that gets written to when PRT: is locked. (I don't know how this happened, whether CANCEL was clicked on when WB was requested, or whether the machine was turned off before a print was complete). Anyway, after a re-boot, the lock in software (as well as the program that created it) no longer exist (hopefully), but the printer device remains locked on the disk. This used to be a common problem under 1.1 on my A1000, but this is the first time I've locked a disk under 1.2 on my A2000. Surely someone else out there has experienced these problems. Is there a program available that will unlock the printer on the disk? *WHY* doesn't AmigaDOS unlock everything when it boots up??? ----------------------[GURUing MoveWindow Cmd]------------------------------- On another note: Has anyone had any trouble with the MoveWindow command (on one of the fish disks)? I put it as the first command in my s:startup-sequence to re-size my AmigaDOS window when the machine boots so that it fills the screen (I use MoreRows, so I have > 640x200). It worked like a charm for 2 weeks, then started GURUing, so I commented it out. Later, I uncommented it & it worked for a day, but the next day it started GURUing again (000000003). This seems to be a random problem...perhaps it wasn't FixHunked? On the days that it doesn't work, when I test from CLI, I get "Didn't found window", which is ridiculous, since it is supposed to work with any/all exisiting windows. Is there someplace in the system-configuration file that I can alter to get the window to open up to the right size (MoreRows modifies this file, why can't it also modify window-size when it modifies screen-size?). ----------------------------------------------------------------------------- Thanks to any/all who reply. -->TOM@SCU BITnet: TGILHEANY@SCU.BITNET .