#View Charges bug?
9 messages in this thread
I found an odd little thing in using the view charges option. When I click on
the exit gadget, I get a requestor saying my workbench disk in drive 0 is write
protected (which it is). I am using a harddisk and have assigned Whap: to a
directory there and all else runs well. It appears to me that whap is trying to
write something to df0: while exiting the view charges area. All other
standard assignments (sys: c: s: fonts: l: etc…) are set for the harddisk so
I don't understand why Whap wants to do this. Any thoughts on the matter?
Thanks, Jim Marias (75436,126)
Well, if it's worth anything, I have Whap! on my hard drive and always leave
DF0: empty. In all the months that I've used whap!, I've never had any problems
with any error messages about DF0:
Jim Nangano
Looking for floating point lib or something that he didn't move over to the HD?
(Just guessing, I don't have it looking to DF0: either).
Then why would it come up with the write protected requester?
Jim Nangano
Perhaps looking to write something in T: ?
-larry
Jim,
I don't know. I just went through all of the billing options with no disk
in DF0:, everything was fine. It sounds like you might have forgotten to make
an assign to your HD. T: maybe? I don't know. Maybe if you upload your
complete startup-sequence I can tell what's causing it. Whap! makes no direct
reference to physical devices other than those you may have set up in the Edit
Parameters screen (messages, downloads, uploads).
Best,
-jcs-
Hi Jim,
I double checked my assigns and all seems fine, so I've gone ahead and
arced my startup-sequence. I will whap it up to the library when I send this
message…Filename: JKMstart.ARC
Don't bother spending much time on this as it is a rather lengthy and
non-commented script giving me a pretty nice environment to work (play) in. All
I need to do is hit the cancel gadget on the requestor and the Whap screen
comes back all safe and sound. So its nothing more than a tiny annoyance, and
I know you've got your hands full of other things.
Anyone else reading this, please feel free to DL it and if you have any
questions, comments or suggestions just let me know.
Thanks, Jim Marias (75436,126)
Jim,
Did you reassign t: to the HD: as well?
Doug
Doug,
Sure did. I've uploaded my startup sequence to the lib as well. Don't
know what's causing it, but it really is no problem as hitting cancel on the
requestor seems to work just fine.
Jim Marias