| Click here to select a new forum. |
| Using Compact Virtual Memory 3.0.2 on a Mac SE (7.1) with a MacEffects Performer. |
Posted by: fergycool on 2024-12-23 07:41:43
Has anybody tried this and got it working OK? Lots of different threads suggest it works fine with many different accelerator cards. Plus I saw MicroMac's own pages suggest you try it.
However, when I've tried it everything seems to work fine and Finder shows the virtual "ram". However, there are two issues. AppleTalk is broken and whereas you can shutdown the SE, if you try to restart you get a few display glitches and then it hangs and you have to power cycle it.
I tried with the MM Performer 2.1 extension (in the Extensions folder with an alias in the Control Panel folder. This also comes with an AppleTalk patch extension, which does not really seem to do anything for me as AppleTalk works fine without it (without Compact Virtual of course!).
Thanks! |
Posted by: cheesestraws on 2024-12-23 07:43:30
Is Virtual loading before or after the accelerator driver? |
Posted by: fergycool on 2024-12-23 08:51:02
Is Virtual loading before or after the accelerator driver? Thanks. It's loading afterwards. Should it load before? I've tried changing the loading order of the Appletallk patch extension and the MM Performer one but not the Virtual extension. |
Posted by: cheesestraws on 2024-12-23 08:59:20
I know it has to load before on *some* accelerators though I must emphasise that in this case it is a wild guess rather than being based on deep knowledge... |
Posted by: fergycool on 2024-12-23 09:07:53
My apologies. It's loading first! Not sure why as there's nothing special about the naming. As far as I understand extension are loaded in alphabetical order? |
Posted by: fergycool on 2024-12-23 09:14:33
So on the tried and tested method of "if it does not work one way, try the other" I moved the Virtual extension to load after the MMPerformer extension. The first time it restarted after loading the MM Performer extension. But on the second boot is loaded up fine. Unfortunately it did not make a difference! Virtual memory is still working, but Appletalk and restarting are still broken. |
Posted by: Realitystorm on 2024-12-23 10:42:38
For virtual did you run the installer or just drop the extension in to the system folder? If I remember correctly virtual must be installed so it can detect what accelerator is in your system as part of the installation process. I remember having an issue with one of my accelerators that went away after I did an install vs. a copy. |
Posted by: fergycool on 2024-12-23 11:20:52
For virtual did you run the installer or just drop the extension in to the system folder? If I remember correctly virtual must be installed so it can detect what accelerator is in your system as part of the installation process. I remember having an issue with one of my accelerators that went away after I did an install vs. a copy. Thanks. I ran the installer. It asked me what card was in there. The closest one was a Micromac one but I cannot actually remember which one! I will rerun the installer. |
Posted by: cheesestraws on 2024-12-23 11:37:00
As far as I understand extension are loaded in alphabetical order?
Approximately. Here's more detail than you needed or wanted 🙂 [and from memory, too, so may be slightiy inaccurate].
Extensions/INIT resources are loaded by file type, and within each file type they're loaded alphabetically.
First are loaded script extensions, which have a file type of 'scri'. These are intended to add support for other writing systems, and they are loaded before the System attempts to display any text.
After that, 'adev's are loaded, which are AppleTalk drivers. After that, AppleTalk itself is loaded.
After that, INITs (normal Extensions) are loaded, and then INIT resources in cdev files. The immediate practical upshot of this is that control panels always INIT after INITs, and some drivers that really want to load early masquerade either as 'scri's or, more riskily, 'adevs'. |
Posted by: fergycool on 2024-12-24 02:19:54
Approximately. Here's more detail than you needed or wanted 🙂 [and from memory, too, so may be slightiy inaccurate].
Extensions/INIT resources are loaded by file type, and within each file type they're loaded alphabetically.
First are loaded script extensions, which have a file type of 'scri'. These are intended to add support for other writing systems, and they are loaded before the System attempts to display any text.
After that, 'adev's are loaded, which are AppleTalk drivers. After that, AppleTalk itself is loaded.
After that, INITs (normal Extensions) are loaded, and then INIT resources in cdev files. The immediate practical upshot of this is that control panels always INIT after INITs, and some drivers that really want to load early masquerade either as 'scri's or, more riskily, 'adevs'. Thanks for that! Interesting. |
Posted by: fergycool on 2024-12-24 07:15:04
I saw that some clever sleuth (@David Cook) has unearthed some more recent Accelerator drivers - Gemstart 3.0 that were designed for 7.1. I gave these a spin. They work fine for enabling the accelerator, but unfortunately they show the exact same issues. |
Posted by: fergycool on 2024-12-28 07:43:13
I just had another play with Compact Virtual. I tried MacTCP with the DaynaPort drivers since the SE has a BlueSCSI. With the Compact Virtual EXTEND MEMORY option toggled on this also fails to work (for me!). But if I toggle it OFF Appletalk and TCPIP work fine. Also the Gemstart 3.0 extension allows me to restart fine. With the MM Performer 2.2.1 extension restarting the SE hangs with EXTEND MEMORY enabled.
Both extensions give similar performance as tested with Speedometer 3.23. |
| 1 |