STEIN@UCONNVM.BITNET (11/23/87)
Joe Beland posted a problem using Print Shop IIGS. If you only have 768K and have a ramdisk set up, you may not have enough free memory to load it under Prodos 16. Try eliminating the ramdisk (set its maximum size to 0) and turning off the computer before rebooting. The ramdisk size doesn't change until the power is shut off. That brings up the question -- does anyone know of a way of changing the ramdisk size without turning off the computer? ARPA: stein%uconnvm.bitnet@wiscvm.wisc.edu Alan H. Stein BITNET: STEIN@UCONNVM University of Connecticut UUCP: ...ihnp4!psuvax1!UCONNVM.BITNET!STEIN at Waterbury CompuServe: 71545,1500 Genie: ah.stein Department of Mathematics
jbeland@pnet01.cts.COM (Joe Beland) (11/23/87)
Alan H. Stein writes: >Joe Beland posted a problem using Print Shop IIGS. If you only have 768K >and have a ramdisk set up, you may not have enough free memory to load it >under Prodos 16. Try eliminating the ramdisk (set its maximum size to 0) >and turning off the computer before rebooting. The ramdisk size doesn't >change until the power is shut off. If I have *only* 768K? The manual says that Print Shop only requires 512K. Well, I solved that problem. I set up the ram disk with only 256K from the Control Panel. This way PS only sees 512k total. Supposedly, I should be able to set the ram disk to 512K and PS will then see 768K and should run under P16 from the GS Launcher. Seems like a lot of trouble to go through to run a program! Personally, I think Broderbunds copy protection is what's screwing it all up! There's no reason we should have to re-set ram, and cold boot everytime we want to run Print Shop. This is BullPucky! And then, try running other applications after you've quit PS. Especially ones that need more memory. Again, another ram reset and coldboot. I intend to write Broderbund software and voice my displeasure! Unless the copy they sent me is buggy, I'd like to see every owner of Print Shop GS send off a letter too. I've never seen software so damned picky! UUCP: {akgua, hplabs!hp-sdd, sdcsvax, nosc} !crash!pnet01!jbeland -or- {allegra, gould9, scgvax, ucbvax} !sdcsvax!jack!man!wolf!jbeland ARPA: crash!pnet01!jbeland@nosc INET: jbeland@pnet01.CTS.COM
prw@meccsd.MECC.MN.ORG (Paul R. Wenker) (11/24/87)
In article <8711230756.AA14752@crash.cts.com> pnet01!jbeland@nosc.MIL writes: > >If I have *only* 768K? The manual says that Print Shop only requires 512K. >Well, I solved that problem. I set up the ram disk with only 256K from the >Control Panel. This way PS only sees 512k total. Supposedly, I should be >able to set the ram disk to 512K and PS will then see 768K and should run >under P16 from the GS Launcher. > >Seems like a lot of trouble to go through to run a program! Personally, I >think Broderbunds copy protection is what's screwing it all up! There's no >reason we should have to re-set ram, and cold boot everytime we want to run >Print Shop. This is BullPucky! And then, try running other applications >after you've quit PS. Especially ones that need more memory. Again, another >ram reset and coldboot. > >I intend to write Broderbund software and voice my displeasure! >Unless the copy they sent me is buggy, I'd like to see every owner of Print >Shop GS send off a letter too. I've never seen software so damned picky! Don't be silly. Copy protection has nothing to do with memory usage. If you set up a 512k ramdisk in a 768k machine, that leaves only 256k for programs. You can't get a new system disk to boot in that configuration. And it's not protected. To the best of my knowledge, this is how the ramdisk stuff works. On cold start, the ramdisk manager (tool #13, "Used internally") gets the user selected size block of memory from the memory manager and uses that as the ramdisk. From that point on, that memory is considered by the memory manager to be in use and not available for others. Period. The ramdisk manager is considered to be just another program by the memory manager and gets the same treatment. For the same reason you don't want others writing over your memory, it doesn't want other writing over it's memory. The fact that a ramdisk is only reset on a cold start is actually rather nice. If my ramdisk was destroyed every time I had to reboot, I wouldn't bother using one. Think about it. Everytime there was a fatal system error, bye-bye ramdisk. Or everytime you had to run a program with no way out (i.e. Music Construction Set). I personally don't use the internal ramdisk. If you really want a ramdisk, the best bet is to buy an Apple II Memory Expansion Card ("Slinky" card). It's the megabyte card that works on a //e. ProDOS automatically formats it as a ramdisk on cold start, it's only destroyed by a power off, and it's completely independent of the GS's internal memory. If you get enough memory (1mb) you can load the entire system disk plus a few of your favorite programs into it and boot from it. -Paul R. Wenker -MECC
jbeland@pnet01.cts.COM (Joe Beland) (11/26/87)
Paul R. Wenker replys: (text deleted) >Don't be silly. Copy protection has nothing to do with memory usage. >If you set up a 512k ramdisk in a 768k machine, that leaves only 256k >for programs. You can't get a new system disk to boot in that >configuration. And it's not protected. (more text deleted) >From the rest of the text of your message, that's the best explaination I've heard so far and it make sense to me. Above you state that "..it's not protected" If you're refering to Copy Protection, take a look at page 41 of the manual. It is. In any case, you're explaination of how ramdisks work and how to use them has been very helpfull. I've since figured out how to get Print Shop GS to work without any problems and I'm having a fun time with it. However, this problem with ramdisk allocation should be stated in the manual Thanks for the help. ..joe UUCP: {akgua, hplabs!hp-sdd, sdcsvax, nosc} !crash!pnet01!jbeland ARPA: crash!pnet01!jbeland@nosc INET: jbeland@pnet01.CTS.COM