Search results

I had three Astec AA13800 power supplies lying around and decided to recap them. I understand the Sony is preferable, but I have some lonely SE/30s. Here is my capacitor recap list in case that helps anyone else. C7, C8 330uF 220v 25x36 10mm lead spacing LGU2E331MELA C19 220uF 25v 8x15 3.5 lead...

I believe this is the answer. The program puts 1F in the CCR register (immediately before the endless loop branch), which must get pushed onto the stack in that arrangement when an interrupt occurs. So, just an extra way of making sure this is the actual return address. Seems like a good...

Attached is ResEdit with the code disassembly extension in the ResEdit Preferences file (put in the Preferences folder), and Resorcerer. I switch between them because sometimes ResEdit doesn't read the debugging labels or non-'CODE' resources correctly.

Are you disassembling the raw library or after it has been compiled into a program? I think you are looking at the raw library, which is before all the correct addresses have been inserted by the linker. Here is what the compiled library looks like at that location. My JSR has been linked to...

Wow. Not crazy if it works, I guess.

Okay. I upgraded the firmware. I repeated the tests and they produced the same results. No big deal. I'm happy with the performance improvements. Aside: I tested the IIfx with ZuluSCSI and MacSD with even a different video card and a different IIfx, across System 7.0.1, 7.1, 7.5, and 7.5.5, and...

Is called right at the end of INITPERF if it is successful in setting up everything else before that. It looks like PERFSETUP is using a parameter sent in for the magic offset. Here is where the magic offset is being saved in the global variable. It looks like PERFSETU doesn't perform the...

I agree! I just dumped the RAW .o from within CodeWarrior. To save memory and disk space, the linker only needs to take parts of the library. After collecting all the parts from the entire program, the linker fills in the final addresses everywhere. So, it is 0000 at this point in the process.

Rough draft analysis. link a6,#$0000 movea.l (sp)+,a6 move.b <Anon_05>+$0E,d0 // Move some global variable into D0. Maybe whether performance checking is currently enabled? beq.s PERFINTE+$4C // If it is zero, goto exit stuff move.w <Anon_05>+$04,d0 // Move some...

Agreed! That's the problem I've been dealing with as well.

Careful. It looks like that speaker is only 8 ohms.

You're correct. Old eyes, I'm afraid. [10ms] FW Version: 25.03.19-release Mar 19 2025 16:57:18 Doesn't seem like the newer firmware has any changes related to performance. Happy to update it if you want.

Using CodeWarrior 11, I can use either of the PerformLib.o libraries I attached earlier in this thread. It compiles, links, and runs just fine. Using the Basilisk II emulator, the report outputs but without apparently capturing any samples. Either the emulator is too fast when sampling at 4 ms...

Just received mine this weekend. I ran some quick performance tests comparing the standard 2022c v1.1 Atmel-based ZuluSCSI vs the new ZuluSCSI blaster and System 7.1. Note: Ignore seek times as SD cards do not have a drive head that needs to be positioned. Throughput is all that matters...

Good find!

PerformLib.o appears to be included as part of MPW. The version from the CD is from MPW 3.2.x. Attach is also a version from MPW 3.3. It may be in a newer library format that works with Retro68. If not, it appears that MPW 3.5 and later are available for download. The attached files are in...

PerformLib.o on the July 1992 Developer CD has the routines. Seems to be recognized by CodeWarrior 11.

I ran across an interesting header "Perf.h". https://github.com/laniku/sys71src/blob/main/Interfaces/CIncludes/Perf.h This seems to be something Apple created that checks application performance, as well as ROM usage, etc. Something @zigzagjoe and @ymk might be interested in, given they both...

Aside: I love how @cheesestraws guessed correctly immediately.

Well, I have good news and bad news. The good news is that your F4 is not blown. The bad news is that your F4 fell off. If you're feeling bold, you could short the fuse or put a penny in there. I have a box of modern polyswitch/PPTC fuses. I would simply solder in something with around 1...