Recent content by David Cook

One of my favorite things about this hobby is upgrading these old machines to their maximum potential. It's like fulfilling a promise.

That is an amazingly crisp image.

Check for capacitor damage around C2. There are a lot of traces related to the CLUTDAC (UJ10) that run nearby. See sheet 5 of 5 on the schematic.

I agree that the new order makes a lot more sense, particularly since events can be added during interrupts. So, an event can be posted as the other managers are initialized. In the 1983 (pre-launch) technical notes, they say: "Before using the Event Manager, you should call the Window Manager...

You are very kind. This only runs on "classic" B&W Macs because Andy is not calling Bill's Quickdraw routines (FillRect and CopyBits) -- which is ironic given the thread it is posted to. : ) It also won't likely run with MultiFinder active, which is also somewhat ironic given Andy's later work...

Extracted and converted to BinHex (aka Tiny Transfer) format

Bill Atkinson was one of my heroes. As a young software engineer, I spent many commutes and sleepless nights trying to figure out how regions worked. The best I could come up with was a tree of rectangles with an in/out/check-child-nodes flag to determine if a pixel should be drawn or not. A...

Updated Tiny Transfer attached. Fixed “Missing or incomplete footer” errors when the footer happens to fall on a boundary such this it is processed in parts rather than all at once. When sending via XModem, very compressible files can cause a delay before sending the next packet, because the...

If you want to be compatible with Apple's Switcher, don't forget to check it's low memory global before calling MFTopMem. Otherwise you'll crash (?) or get the wrong value. See Technical Note #158. That is so funny. I've been updating my Tiny Transfer program and cringing as I consume an...

Looks good. BTW: Gestalt in often implemented in compiler glue to provide basic services when the OS doesn't actually have Gestalt. Not sure whether Think C 4 provides that or not. For example, Apple provided this code, which (you'll be happy to see) mimics what you have already implemented...

I reuse parts across different models that I repair. Therefore, my capacitor list may not be optimized for this power supply. C19 C20 10x20 1000uf 10v 5mm ls A750MV108M1EAAE014 C18 13x25 2200uF 10v 5mm ls A750MW228M1CAAE010 C15 10x20 330uF 35v 5mm A750KW337M1VAAE020 C16, C21, C22 6.5x15 82uF...

Hold the phone! What is this? https://github.com/laniku/sys71src/blob/main/Interfaces/CIncludes/Perf.h Did Apple already create a performance library? You may just need to call this and then convert the report file into routine names via the debug data file.

BTW, it looks like Apple's Time Manager source code is available. It might help you understand what the stack (and registers) should like like when your routine is called. The exact Time Manager code will depend on your ROM / System. But, this might help...

Here's a possible approach. 1. Run a test program that shows an alert with it's address range when it starts up. Then have it do some heavy looping with occasional calls to WaitNextEvent/GetNextEvent. 2. Add a debug breakpoint in your Time Manager program. 3. Each time it breaks, dump the stack...

OMG. Your damage was far worse. I would not have even attempted your floppy restoration. Congrats on saving another Mac!