i thought thats the standard for all forums: 68kmla has it too

110€ plus shipping in Europe.
Original PSU included but no box and manuals.
Works under Mac OS 9 and X up to Lion

Raphael 

can´t reproduce that here.

That kind of doesn't make sense because 3x 512 + 1x 256 isn't an interleaved configuration yet the results are similar to the 1gb interleaved.
I will have some time over the next few days to test mine and I'll report back

Thanks refinery. I agree that it doesn't seem to make sense. Maybe it is because OS 9 only utilizes 1.5GB and as long as that’s available [especially when testing with QuickBench Classic (2.0) which IS OS 9 based] interleaving might not matter. Yet when one uses only the (2) 1GB sticks, interleaving can improve performance? Perhaps just as matched pairs of (4) 512MB can do?

The three 512MB sticks that I used (in J21, J22 and J23) were all matched and the same. The 256 of course, wasn't. And of course, depending upon just how your machine is configured or loaded up. This machine here is a bare bones sort of machine with a 128 GB SSD and no other internal cards, other than the GPU.

Before you get way out here in-the-weeds with me… if you’ve room to move the 1GB RAM in J22 to J23, you might then test with QuickBench Classic [2.0]. After moving the RAM to J23, boot up and zap the PRAM and then rebuild the desktop prior to running QuickBench. Otherwise you may only see results like what you might get from slots J21 & J22.

I just tested 2 different, new pairs of 1GB RAM in J21 and J23 and at first they all tested like the previous, non-interleaved results. I zapped the PRAM and rebuilt the desktop and retested after each pair change of RAM. QuickBench results then matched the previous interleaved results.

*QuickBench 4.0 runs only under OS X and thus, likely tests the full 2GB of RAM under OS X?

---

Also… just ran Apple Service Diagnostic (ASD v2.1.5 for the 2003 MDD) with one pair of the new 1GB RAM sticks installed and it PASSED every test. Like a big dummy... I didn’t select specific tests and it took over 35 minutes to complete ALL of its tests. I don’t like that I can’t simply screenshot the results & text - or all of the tests that ASD runs — but here’s a somewhat “reconstructed” iPhone image after only 15 minutes of runtime (it says 15 minutes, anyway).



Really like ASD v2.1.5 and wonder how it might test out with the original pair of 1GB RAM. (But not tonight.)

---

So again, likely more information than anyone really wants to know…

If a questionable J20 RAM slot wasn’t already enough to contend with here… a much closer inspection of the original (2) 1 GB modules provided yet another concern.



See that “Big S” on module #2? It’s in slot J23. But when I swap in into J21 — and module #1 into J23… I get a “Finder failure” message upon boot and reboot. (I’ll attempt to attach a SpecTek.pdf file below.) Swap the sticks back and no problem. Hmm?

And then upon a much closer examination of #2’s backside, what’s that? Missing TWO little capacitors? Yet it still seems to work fine, just as long as it remains in the J23 slot - with module #1 in the J21 slot.



Okay, that’s defintely more than enough for now!

That kind of doesn't make sense because 3x 512 + 1x 256 isn't an interleaved configuration yet the results are similar to the 1gb interleaved.
I will have some time over the next few days to test mine and I'll report back

Thank you! I wasn't aware of the read-only thing!

Checksums are only created for read-only disk images. Disk images created as read/write never have checksums.

I try to copy a whole volume as a folder into a image ".img" and write it back to a different hdd through ASR. - For an unknown reason to me ASR is mouning that there's no checksum. And indeed there is no. - How can I get this working please? Running under Mac OS 9.2.2 on a G4 Titanium Powerbook.

yeah, this would be amazing!

there is an updated NFS Manager version 6.0.  That helped a lot but I still had to change the server path as Tahoe renamed my computer.  Also I had to change my firewall setting.  But everything seems to work now.

Glad to know your NFS transfer capacity has been restored.