Search results

It's a weird limitation because the MAC address is programmed into the chip by the driver every time you use it. So if they wrote their own driver or even disassembled and modified Farallon's they could make it fully configurable without changing the hardware.

If the voltage is high enough it'll work. I don't know what the valid range is for the 68HC05 off the top of my head, but I'd think 3 to 3.5 would probably cover it.

Right. The logic board is the issue, not the G3 (or G4!) CPU.

Honestly I ran mine for many hours in pretty high ambient temperatures and nothing bad ever happened. I did have to touch up the solder joints after many years though. If giving the monitor a good smack on the sides makes the picture react than you definitely have bad solder joints.

Here's the developer note. I haven't checked in depth but I think its the same as the one here: https://preterhuman.net/macstuff/techpubs/hardware/hardware2.html

I think there are some timing values in the MPC106 and a few other things that would need to be adjusted. Also potentially the 366 MHz would have had a newer/faster ATI chip. Differences from the developer note: - Rev A is a Rage II+DVD, Rev B & C are Rage Pro - Rev B supports both master and...

From an internal document I have, 4.5F3 is "Gossamer Speedbump", and is listed with a checksum of 78eb4234 and an MD5 of 9cc0e3e01bb02691b497d792ea3e9403. So not exactly this but close.

Given the Linux kernel note that it matches a Farallon card, maybe Farallon drivers would work?

It's not uncommon for two chips of the same make, type, and manufacture date to fail at the same time - we see it pretty often in 30+ year old arcade PCBs these days. That said, sorting out the logic analyzer would help a great deal to determine what's happening.

That makes sense. It's funny how over-engineered the 68k and the coprocessors were, and how every later model backed away from the complexity. I believe there was one '010 machine that could use the '851, but I don't remember which one now. There's also an Apple II slot card with an '881 (no...

So I've finally researched this properly and it's indeed an MC680x0 feature, at least for '020 and '030. In CPU space (function code 7), addresses of the form $0002xxxx access CIRs, Coprocessor Interface Registers. Bits 15-13 are the standard 3-bit coprocessor ID, same as you see in F-line...

The built-in video on some PowerBooks installs the VBL handler as a timer task because the hardware didn't support it.

The duplication that's happening looks like maybe the data bus buffers are marginal and not reliably latching new data. So I'd be suspicious of those - on the Portable they're the two 74AC245s between the modem slot and the main RAM array (and the ROMs are right below them, assuming the ports...

Yeah, I'd definitely try the easy things (clean 7.1 install, different slots) before going wild with a magnifying glass or a ohmmeter.

Ahh, didn't know about the Value040. This code at the start of the ROM definitely looks like LC support. ROM:52000040 cmpi.l #$350EACF0,d2 ; LC ROM:52000046 beq.s loc_52000060 ROM:52000048 cmpi.l #$35C28F5F,d2 ; LC II ROM:5200004E...

Likely a hardware problem, like a broken trace or something of that nature.

Gonna answer myself here. There's two strings in the ROM: 'Macintosh II, IIx, IIcx, IIci, IIsi, IIvi,',$D,' IIvx, SE/30, and Performa 600.',$D,'(ASIC support included)' and 'Macintosh LC and LC II',$D,'Performa 400, 405, 410 and 430',$D,'(ASIC support included)' Innnnnteresting. I haven't...

Awesome, thank you Bolle! LEM says the Turbo040 works on the II, IIx, IIcx, IIci, IIsi, IIvx, IIvi, and SE/30. Are those all with the same ROM on the card?

The cursor not moving when it's on that screen generally means there's a problem with the vertical blank interrupt. I wouldn't expect the System version to matter there since that mechanism for NuBus was the same since the original Mac II, but it might be worth a try.

Interesting. What type is the EPROM on the card? EPROM readers always read and write in little-endian by convention, so knowing if it's a 16 or 32 bit wide ROM would help when trying to figure out how to descramble it.