gregor@tikal.UUCP (Gregor Harrison) (12/11/86)
I have noticed a bug in the 1.2G1 (33.47) release of the workbench
that to the best of my knowledge has not been mentioned here. When
the ram disk icon is present on the workbench screen, the duplicate
command fails on icons in the ram disk. For example: bring up the
workbench. Start a cli window, and do a 'dir ram:' to bring up the
ram disk. Leave the cli window and pull some icon into the ram disk
icon. Open the ram disk. You should see your icon in the ram disk,
for instance, Clock. Now here is where the bug is. Select the icon,
and choose duplicate on the workbench menu. The file 'copy of ...'
will be created, and an autorequest comes up telling that the ram disk
is *full*. This happens even if there is plenty of free memory.
A 'list ram:' shows that the .info file was created correctly, but that
the main file 'copy of ...' has size 'empty'.
I think that this is happening because the program is checking the
free space available on the ram disk, which info always reports as
zero. This is clearly not enough for any *major* programs, so the
duplicate command aborts. Why the command doesn't check for space
before copying the .info file, I don't know.
--
EMAIL: {uw-beaver, fluke}!tikal!gregor
QUOTE: "This quote is false."
DISCLAIMER: "All opinions found above are my personal property,
and not that of Teltone, Inc."wagner@utcs.UUCP (12/20/86)
Interesting...is this our first 1.2 bug report? It happens on my real, live, actually paid money for it legitimate 1.2 system. One gets a screen flash and an error 221 in the title bar. Michael