OK, since there's no formal place to report bugs in Enginuity right now, I figure here will do. Running Enginuity 0.4.1.b (774 won't run at all under OS X), only one ROM image can be opened at a time.

Steps to reproduce:

1) Launch the enginuity.jar app
2) Open ROM 1
3) Wait for ~2min as Enginuity builds the tables, note CPU load and disk activity
4) ROM opens and tables displayed
5) Open ROM 2
6) Wait for ~2min as Enginuity builds the tables, note CPU load and disk activity
7) CPU and disk activity stop, second ROM image is not open/displayed

I run mine through parallels, where did you find MAC versions of enginuity?

also are you running powerPC or Intel mac? and what OSX version?

luke

If you just take someone's C:\Program Files\Enginuity folder and copy it to your mac, you can launch the enginuity.jar executable.

I'm running on a MBP w/ 10.5, enginuity 0.4.1.b

I actually have to flash, and do most of the work, under XP Pro in VMWare Fusion. I just object to having to boot windows, give up that much ram, etc every damned time I want to do something with the car. Not to mention that running Enginuity under Windows is just S L O W compared to running it on the mac.

3) Wait for ~2min as Enginuity builds the tables, note CPU load and disk activity


Not to mention that running Enginuity under Windows is just S L O W compared to running it on the mac.

It takes ~5 seconds to open a ROM in Windows ..... Vista no less. It really takes 2 minutes on a Mac? Not trying to start a Windows/Mac fight, just curious.

Jeff

Yeah, in both Win and OS X, it takes a very long time. The strange thing is that it doesn't cause CPU or Disk load while it's doing it. It's like it's just waiting on something. The strange thing is it does it on our IBM laptop too. I wonder if it's because the VM on my macbook and the IBM are using the same system image for the windows install? I've updated the JRE on them so theyr'e both running current software. Who knows.

it takes about 10 seconds on my Mac

OK, that's crazy weird. I've never opened anything but a NA ROM, I wonder if they're somehow more difficult to open...

NA ROMs should be faster to open as they have less tables.

Dunno what to tell you, but I surely seem to be hitting all the interesting problems with this software.

I haven't used it with a mac, so there's not much I can tell you. However, there is a memory leak in Enginuity which can slow the opening of ROM files, depending on the amount of memory available. This occurs even when you close a ROM and open another. The more you open (even if you close each one), the slower it will load until eventually you need to exit and restart. It is something that will hopefully be fixed in a future update.

Hmm.. I do have the VM running in on 768MB of ram. Wonder if that's the problem? Now the question becomes "can I change anything about the vm without windows de-activating itslef" if I try to test that.