Search results

I understand that the newer serial driver also supports control codes to select the faster baud rates: "The SerialDMA driver supports two new csCodes, 115 and 230, by which its Control routine" See the attached tech note.

Wow. That is unexpected. An LC 475 printed directly on the case like the original LC III.

Ha! Did it look like this? Because I thought this was pretty bad when I acquired it. Manufacturing: "Boss, we have a problem. Corporate keeps coming up with random model names." Boss: "No problem. Just make a generic case and stick an Avery label wherever you can find a flat spot."

I recently purchased a Performa 467, primarily for the novelty of such an obscure model number. Other than bundled applications, it is identical to the LC III+. Both machines are just LC III computers with a boost from 25 MHz to 33 MHz. Some weird things were going on at Apple in 1993. Here are...

The LC III+ is simply an LC III bumped from 25 MHz to 33 MHz. The Performa 460 series (460, 466, 467) had identical hardware to the LC III+, but included additional application software. System Enabler 003 is for the LC III+. System Enabler 308 is for the Performa 460 series. Wait, what? The...

FYI: Apple planned to stuff a 16MHz and 25MHz IIci into an SE/30 package. They also planned to replace the IIcx with a 16MHz IIci. boxMacIIci EQU 5 ; Aurora 25MHz 3 slot package <3.6> boxAuroraCX16 EQU 8...

Yes, please share the control panel and extensions you have! I have not tried to remove the ram. The sockets seem similar to MicroMac SIMMdoubler right angle connector, which I was able to carefully finesse free.

Awesome

Very cool! Despite being told it is read-only, if the host tries to write anyway, will the write succeed? I ask only because I know the SCSI is faulty on these Macs, so I can't rely on them behaving themselves.

SetRect(&rct,0,from*9,winWidth, too*9); EraseRect(&rct); for(line=from; line<too; line++) Is the for loop supposed to be "line<=too". The EraseRect is going <=too.

Very clever.

Fascinating. Clean build, too. Tell us more about the values it monitors. What kind of issues can it help catch?

See my in-depth analysis below. When I side-stepped the 32-bit warning to allow the software to continue running, it crashes, My conclusion is that the code really does need changes to be 32-bit compatible...

Yes. As far as I know, Apple never actually got to the point of adding operating system calls for this. All the compilers should still be replacing the LM calls with direct access to low memory global variables.

Yes. At some point, Apple realized that global variables complicated the transition to multiple threads/CPUs and protected memory spaces. As a first step, they renamed all of the global variables to look like routines starting with "LM". One of these is named LMSetMBarHeight(); Had the MacOS...

Not 'inline' per se, but yes, it can include assembly subroutines. asm pascal void NullCaretHook(void) { move.l (a7)+, d0 preturn }

@Snial types faster than I do.

Try: SetCursor(&(qd.arrow)); As C and compilers matured, they corrected mistakes and used more "C standard" ways of accessing Mac features. Unfortunately, this broke some earlier source code. In the example above, rather than faking that arrow is a global variable, they define qd in the startup...

Thanks for the potential lead. That was originally my thought as well. However, the jumper connector was hard jumped for production. Check it out: The left side of the image is the slot output. SuperMac included the mounting pattern for a DE-9 connector, but obviously didn't populate it. So...

Ok. I desoldered the existing 64 MHz crystal and added a socket in its place. Unfortunately, the legs of the desoldered crystal were too short to fit snugly in the socket. So, I had to order a new 64 MHz crystal from Mouser (ECS-100AX-640). After arrival, I verified that the new 64 MHz crystal...