ramdisk problems
DRIE...@hlerul55.bitnet
I didn't quite like it, it looked more like an arcade game than it looked
like a RAM disk.
The second was the most important, though. It is documented (but I can't
remember where - sorry) that a desk accessory may under no circumstance
allocate memory dynamically. I can only guess at it, but I fear the Intram
doesn't do anything to correct potential problems with other programs,
that allocate memory and then in some way temporarily giving control to an
accessory.
On a related note, the reset survivable RAM disk works simply by setting
a memory management register to fool the ST into thinking it only has 512K
on board. Thus it cannot conflict with any other program that wishes to use
the same memory, because the memory simply doesn't exist !
And while I'm at it, at first the reset survivable RAM disk failed to work
for me I had put it on my normal startup disk, replacing the RAM disk
I used until then. The problem was a program I wrote to remove remnants of
RAMdisks from a former session after a reboot. This was necessary with
normal RAMdisks, to avoid them being assigned successive higher drive
letters each time you do a warm boot. It simply set ndrives to 1 and
drvbits to 00000011. After removing the remover, the reset survivable RAM
disk has saved me lots of frustration in the edit-compile-link-test-reboot
sequence !
- Bert Driehuis
Warner Young
How does one go about generating a menu bar / dialog using the .RSH
file from the RCS? That is, I want to write a program that contains all its
own resource information, without referencing a .RSC file, and I'm sure that
the .RSH file contains all the necessary information, except that I don't
know how to use it. Can someone help?
Also, on the RCS, what is the exact difference between a "panel" and
a "dialog"? The only difference I can see is that the objects in a "panel"
are all pixel-aligned, as opposed to character-aligned. Is that all?
Also, what version of RCS do we all have? I called Atari for an
update, and received v2.1 in the mail. Is that the newest one? And BTW,
for those of you who don't have v2.1 yet, it fixes the "monochrome" bug of
the previous release, so that you can view resources correctly even on a
color screen. However, v2.1 cannot load its own .RSC file; it simply locks
up when you try to do it.
Another question: why do you need to use Vsync() before switching
screen display locations? I've heard that occasionally there are jitters
or problems with the display, but I wrote a program to switch between two
screens a lot of times, and there's never any problem.
Neil, if you're reading, when are developers supposed to get GDOS?
A friend and I have been waiting quite a while for it.
Finally, using a desk accessory that checks the amount of free RAM
(essentially the one Tom Hudson released), I noticed that when I run a SMALL
program (15K or less, I think), I have more free memory while running it than
I do in the Desktop. There's about 33K more, in fact. Where is this stuff
when the Desktop is up? What's using it? And will GDOS take up more RAM?
How much more?
Whew! Sorry for all these questions, but I can't access the net
often, so I've gotta ask them now. In fact, after December 9th, if you
e-mail me directly, please write to rad...@cory.Berkeley.EDU.UUCP
Thanks, everyone, and have a merry Christmas, and a happy New Year!
Warner Young
"If I had something funny to say, I would.
Unfortunately, I am not affiliated with any rich, money-making people or
companies."