| Rating: | |
| Category: | |
| Year released: | |
| Author: |
|
| Publisher: |
Jump Development |
Jump Development Group
MacWEEK, David Ramsey
OptiMem RAM Charger is powerful, install-it-and-forget-it software that makes more memory available for keeping more applications and documents open. But that's only the beginning. It is revolutionary memory technology that works on today's big applications and document to make your Mac much more reliable and easier to use.
--------------------------------------------------------------------------------------
I can personally tell you that using this program has virtually eliminated application/system crashes due to shared memory. This is one of those "must have" programs for Mac OS 7, and once you've installed it and gotten familiar with it, you'll wonder how you ever got along without it.
--------------------------------------------------------------------------------------
Heads Up Display
Control Panel
Large Screen Preview of Back Cover:
http://img337.imageshack.us/img337/7316/ramchargerbackcover.jpg
----------------------------------------------------
Version 2.1.1 and 2.1.2 UPDATE are both included together in one of the main download links at the top of this page. A Change Log is also included. v2.1.x has the same compatibility as v3.0.1
----------------------------------------------------
CompatibilityANY Mac running Mac OS 7 up to and including 7.6.1
Comments
Manual uploaded.
Bolkonskij: That was on a different page and we left it at that, a stalemate. But I won't address your concerns here.
Don't carry your gripes onto this, another page. OK? Save your long winded accusations for the Forum please, your post contributed nothing to this upload. I've already moved on, it's time you did as well.
As far as removing a S/N from this page, I would have done that with anybody adding something that gives the false impression that this upload was incomplete.
The only problem I've ever had (so far) with ".DS_Store" files is that MacZip trips over them because of a pathname bug that its developer mentioned in his readme file. Of course, if they are wrapped inside a disk image it doesn't bother it one bit.
@xy:
Thanks for the post. An excellent read. The review was for RamCharger vers. 8 and Vitoarcs upload is vers. 3.x so perhaps there might still be some incompatibility here, maybe? Still, I didn't know that RamCharger can run on any Mac. So perhaps this would be quite useful on Mini vMac running as a Mac Plus with 4 MBs of RAM and SSW 7.x - RamDoubler can't go there unfortunately
@Vitoarc
You keep on telling me where I have to post something or what I have to add to my uploads. WTF? Don't get me wrong - I'm thankful for anyone correcting mistakes. I think every of us long-time contributors is. But what nobody of us likes is people who just burst in and think they ought to tell everyone on how to do things "right".
This attitude by a very few has already made so many great contributors leave MacGarden. I don't need to name them, because everyone here who is longer around than four weeks knows to whom I am refering.
You'll probably take it personal, though this posting is not intended to be solely about yourself. Rather for a few people here acting the same way.
Please try to step down a bit, contribute to where you can and otherwise let others allow to do so as well - EVEN if it should not fit your expectations of a perfect MacGarden. This is a community project - otherwise of course feel free to open up your own abandonware site where you place everything exactly the way you think it's right.
Mike Garden, regarding your question whether RAMCharger and RAMDoubler are compatible LowendMac says: yes, they are; both are also compatible with Virtual Memory:
http://lowendmac.com/tech/ramcharger/index.shtml
Have not tested this myself, though because I never used any of these tools.
@Vitoarc:
It wasn't that bad
As for using MacZip, this can also cause problems. I do use MacZip a lot but mostly for archives intended for any OS other than a Classic Mac OS, or unless I know the recipient will also have a copy of MacZip to do the extraction. - Why?
Because MacZip has its own scheme for preserving Macintosh Resource Forks in zip files. Similar to Mac OS X's "__MACOSX" hidden zip directory, MacZip stores data-forks and resource-forks separately. All MacZip resource-fork names are added to a special directory named "XtraStuf.mac". So, when extracting on a Mac using any zip extracting program other than MacZip you end up with an unwanted "XtraStuf.mac" folder containing the resource forks of whatever you zipped. And if your archive contains Macintosh executables, they are generally "stuffed", well and truly.
An exception to this is you can get MacZip to zip the data fork only into an archive. This is OK if you're zipping files that aren't dependant on Mac resource-forks for execution such as plain text files or jpeg and tiff images and CD image .iso's etc. But when archiving Classic Mac programs, these can be mostly resource-fork with very little code in the data-fork.
Aladdins Stuffit ".sit" seems to be the safest format to use, if only because most Classic Mac users seem to have a copy of the Stuffit Expander installed.
@Vitoarc:
I've DL'd your latest, there is only two ".DS_Store" files I can detect. None of these are in the disk image tho' and the disk image itself is good. I was able to write it to an actual floppy disk - remember those? I also installed it onto my Centris 660AV which is presently running Mac OS 8.1 - 17 years young and still going strong
I'll keep the RamCharger going on it for the meantime but its too early for me to say if I care for it being there. This product might be handy on Mac OS's before 7.6 - the Macs memory handling had improved a lot since then. I might install it onto Basilisk II next running Mac OS 7.1.1 and see if it likes that. But otherwise, I don't know very much about this program, such as Is it compatible with Ram Doubler? A program of a similar vintage and was extremely popular back in the good old days when 16 MB of RAM cost about $1000 (here in Australia).
The manual? if its already PDF'd then yes its always good to get a manual. But you shouldn't go out of your way here if the manual is hard copy requiring scanning and several pages long. The program has good on board "Balloon Help" and as annoying as that can be, it really is comprehensive enough to get you up and running with this program. -EOR
@ Mike Garden: Sorry about your bad experience. Yes all I would have had to do was use MacZip on my PPC and you wouldn't have had the problem. But I could swear that someone previously on MG told me it was OK to use the native Create Archive in OSX so I did. Anyway, I won't do that again.
I'd like your feedback on the latest download if you have the chance. And let us know what you think about this utility, and if you could use a full copy of a Manual. I'm thinking that the included README should suffice, but perhaps an uploaded manual would good.
Thanks Balrog. It looks like I need to become more familiar with ResEdit.
@Bolkonskij: If you want to post a S/N you can do that in a comment. Everything needed is already in the download. Thank you.
Use ResEdit to get info on the file, and change the visibility bit.
Balrog: Thanks for the tip. I'll do that.
As far as the .zip format, yes I used OSX but now I know I shouldn't.
Everybody just take a deep breath, and I'll improve this addition and will re-up. Since when do I not fix things?
[EDIT] If you don't want the DS_Store, than can someone please tell me how to make invisible files visible in Mac OS 7? There is an invisible .icon in the original disk but I can't copy it to make a new image on Mac OS 7 if I can't SEE IT. Thats why I copied using OSX, and why the DS_Store was generated.
And in case your wondering WHY the original disk had to be modified because I didn't emphasize it more in the description, here's the background: http://macintoshgarden.org/forum/ram-charger
Edit: Replaced 'xxx 7' with 'Mac OS 7' - IIGS User
If this is a DiskCopy 4.2 image, the resource fork isn't needed. I did some tests, and only *compressed* Disk Copy 6 images seem to have fundamental data in the resource fork.
As for getting rid of the .DS_Store, I'd make a floppy and do this on a real Mac.
@bertyboy:
No Classic OS to work in? B2 or Sheep? Ah well... Toast would not be such a bad thing then... As for the solution, I was really kind of hoping Vitoarc could work that one out for himself - still time y'know
I was going to take the original shareware folder for the app, and add in the serial provided by Vitoarc and Stuffit that. As soon a I start to modify folders in OSX you get the unwanted .DS_Store.
So the thinking was to add the original folder to a Toast image and add the serial from the download to that folder. No .DS_Store.
Looks like we have a solution anyway.
@bertyboy: I have to ask the dumb Q here. Why a toast image? All thats required, my guess is the ".sit" of the actual program installer. Anyways, there isn't anything wrong with what Vitoarc put up per se... its the format he archived and put it up in.
Perhaps when he wakes up today (our TZs differ I think) he might reconsider his methods and re-do his archive into a more suitable and user friendly medium. i.e; He would get better results if he'd used DropStuff or Deluxe running on Basilisk II (if he has nothing better) under a real classic Mac OS to create his archive.
Failing that. By all means. Put it up.
Here's the original upload unpacked on OS X and repacked into Stuffit format in OS8.6:
http://sharebee.com/1aa7b16f
What if I uploaded the original shareware from the magazine cover CD and included the serial ? In Stuffit v5.5 compessed Toast image.
bertyboy did say:
Besides the .DS_Store inside the actual Installer floppy image, too? Yes it does appear to be OK. It was the getting to it thats more of a problem IMHO. Someone without Mac OS X and trying this (even if using B 2 or SheepShaver on another OS), might find it difficult to unravel in its present form.
I have a few original unregistered copies from MacFormat / MacWorld cover CDs. Of course, they're Shareware, so they may require activation before they get back into a fully operational product.
Just checked the download, apart from the OSX .zip, it's a good copy.
Vitoarc mentions:
Thats not all, especially for those who don't have Mac OS X; As this is a Mac OS X zip file, that in itself can cause problems for anyone without Mac OS X
toc_collapse=1;
The file "OptiMem Installation.img" does not have a recognized file type. [ OK ]
The Checksum $2FECFE63, and Tags $00000000 appear in the Finder's "Get Info" dialog for the file and it can be mounted directly in Disk Copy 6.x without issue.
In brief: If this had been archived using a native Classic Mac OS, I feel there would likely be far fewer issues expanding and installing this DL on its intended target (a Classic Mac OS).