Recent content by joevt

I think #6 explains that we have a good copy of that bad rom. The ROM has version 2.26b6 and should have md5 = d1d3720c38143eb2bac86b8393318529 As for what I'm doing: I'm working on ANS emulation in DingusPPC. Maybe one day it will boot AIX or macOS. I am working on the emulation of...

Your first post says JB Weld Epoxy does not bound well to polycarbonate (poor chemical bond). But what about using JB Weld Putty for mechanical bonding? Maybe it can be used instead of metal plates/wires. You can drill into it to add screws or pins or other fasteners. If you melt wires into...

The app in my example was locked! After unlocking it, -d does work to remove (or hide) the FinderInfo. So both of these will remove the FinderInfo (or set it to zeros which hides it from the xattr -l command): sudo xattr -d com.apple.FinderInfo "ZTerm 0.9" sudo xattr -wx com.apple.FinderInfo...

The xattr command can't delete FinderInfo because in Mac OS X, on an HFS or HFS+ or APFS partition, FinderInfo is not an extended attribute or it contains info that cannot be removed - it can only be changed (using SetFile or xattr or other command). dumpxattr () { local thefile="$1" printf...

The file in my example has a resource fork without the type/creator that is in the FinderInfo. I think a correct implementation would not attempt to do any parsing of the resource fork. Metadata is ALWAYS externally stored regardless of whether a resource fork exists or not. It appears that...

It would be preferable to be able to have tension go all the way from the top of the rib to the other side so that new cracks can't happen anywhere in-between. I like the part at which shows how the hinge slides into place which perfectly illustrates your point that the ribs are part of the...

FinderInfo and ResourceFork are two separate file system objects so they can have different data. xattr -lpx com.apple.FinderInfo "/Volumes/Classic/System Folder/Mac OS ROM" | sed -ne '1,/^0*10 /p' com.apple.FinderInfo: 00000000 74 62 78 69 63 68 72 70 31 00 00 C8 01 73 00 00...

Do 0.8 mm drill bits like bending forces or are they brittle in the non-vertical direction? How wide are the ribs? How long are the ribs? We see the top of the rib. What's on the bottom of the rib (if you were to drill all the way through). What does the hinge look like when fully opened and...

That means there's more pins for U1 under U2?

Buy some programmable ROMs and a flasher? Get a ROM reader to verify the ROMs? It's probably one of these with 3 or 5 checksums: 0178 004afe97.005446ca.004b77c2.0054d986 2a8a4c7f2a38e0ab0771f59a9a0f1ee4 "1988-09 - 97221136 - Mac II FDHD & IIx & IIcx.ROM" ; Macintosh SE30 0178...

There are newer Flasher utilities that support later PowerPC Macs besides PDM and TNT but that doesn't matter for this ANS project. read 'XCOF' (128) ":Objects:xcoffResources:CopyToFlashPDM.xcoff"; read 'XCOF' (129) ":Objects:xcoffResources:CopyToFlashTNT.xcoff"; read 'XCOF' (130)...

Another note: "Flasher (TNT 0.6)" doesn't try to detect the ROM type before flashing. It says AMD for both AMD and Intel chips. "Flasher (TNT 0.6)" has direct drawing to the screen to show a progress bar - vertically oriented. 480 lines tall, 80 bytes wide. It fills up for each stage of the...

It appears that "Flasher (TNT 0.6)" cannot do Intel 28F020 chips because it's looking for a device ID of DB instead of BD from 8 of the chips. AM28F020.PDF has device ID 2A. It describes non-embedded erasing/programming commands (20h, A0h, 40h, C0h). AM28F020A.PDF has device ID 29. It describes...

In your screenshot, the first 4 bytes of the framebuffer is 07FFFFFF hex. That is 5 zero bits (black pixels) followed by 27 one bits (white pixels). The second line is 1FFFFFFF. The third line is the same as the second line but it should be 3FFFFFFF. The fourth and 5th lines begin with 5F but...

The first line begins at offset 0 of the frame buffer. The most significant bit (bit 7) of the fist byte is the top left pixel. 32 bits is 4 bytes. The most significant bit of a 4 byte value is bit 31 (left edge) and the bits count down to 0 (right edge). Check continuity between the date lines...