Search results

OK for the fun of the community, here is the mock code I threw together for this. I'm thinking of having a specific offset set aside in ROM to trigger this. So if the appropriate offset = 0x01, then run this routine to set the mouse tracking and volume. When burning the ROM, users could...

And interestingly, when you call WritePRAM (0xA038), the system really uses the WriteXPRAM (0xA052) trap to write the 20-bytes of PRAM from low memory back to the clock chip.

I used to collect these darn AOL disks. I had like 100 of them in a drawer at one point, back when floppies were a big thing. Like Blockbuster, this is the end of an old era. I look back fondly on the sound of an analog handshake and the world that opened up to me in the mid 90's.

With the "old" base PRAM, I think Apple's intent is for us to update the value in low memory directly, then call the WritePRAM trap (notice this is not WriteXPRAM). It appears that the WritePRAM trap will essentially copy all 20-bytes of PRAM from low-memory back into the clock chip. Certainly...

There are sellers that could sell you the ROM socket, such as JCM or CayMac. But how are your soldering skills? Admittedly for me I wouldn't trust myself to solder on a ROM socket. I would prefer to pay some money and send my board to a professional like CayMac to do the work :)

Pretty cool stuff here. I've thought about using AI to generate this type of classic Mac code. But I haven't made the leap yet, partly because it's sort of fun to learn this stuff and build it myself. But at some point I'll probably make the leap and give this a shot.

So this piqued my interest. I've been developing a new ROM disk driver for 1024KB ROMs. It is pretty far along, and a couple smart people have offered to beta test this before I share it out. You know, just in case there are some silly bugs :) But when I got home, I made a small tweak to the...

I know this is an old thread, but I wanted to share my thoughts. PRAM vs xPRAM is always a bit of a challenge. The PRAM is sort of sliced and diced in between the xPRAM bits. Attached is a pretty good file that explains the layout of the clock chip memory. You can follow this to find the PRAM...

OK I have an update on this. I did some more tracing with OS 8.0/8.1. It seems csCode 22 (kMediaIcon) does in fact execute correctly, and the ICN# gets applied. But csCode 21 (kDriveIcon) does not apply the ICN# on the drive in the Finder. I was able to get around this in OS 8.0/8.1 by...

That's a good idea, I'll try stepping through this in MacsBug next time I boot up that OS 8 machine. On a side note, I used quickdraw.h to paint a message on the screen each time either the kDriveIcon or the kMediaIcon control call came into the driver. Sure enough on any flavor of System 7...

Great info as usual @joevt! Yes, I dug through some of that material. From "The Monster Disk Driver Technote", I found this information. It could be possible that 8.0 and 8.1 are just stuck right in the middle- between the legacy kMediaIcon (7.X) and new (8.5) kdgMediaIconSuite. I'm digging...

Playing around in ROM code again, and I noticed a difference in behavior with System 7 and OS 8. Starting with Mac OS 8, the operating system no longer issued control code 22 to my ROM disk driver. (22 = get icon) I found Apple's Tech Note 1102, which has a very interesting mention about this...

Long weekend here in the States, with July 4. In between hiking, BBQ, and family time.... Spent quality time with some of my Macs. On my MacPlus, decided to run some wiring from the internal BlueSCSI to outside the case. Now no more constantly opening it up to get to the SD card. Hurrah! Also...

Still digging into this, I was wondering if anyone who has a Rominator v1 for the MacPlus... If you wouldn't mind sharing a dumped copy of your ROM? I'm attaching the one from mine. I am curious if the checksum BBBB BBBB is by design. Or if I need to modify that for the type of chips on my PCB.

Too funny, I just posted the same error I am having. Were you ever able to fix this?

I decided to play around with the Rominator v1 I installed in my MacPlus. When I dump out the ROM, the first bits are: BBBB BBBB. When running the Flash Tool v1.6 to update the boot chime, I get the following error: Error: Flash ID 3737, 8686 did not match any known device ID Looking at the c...

@adespoton 10-4 on that. I tried just about every combination of interrupt and calls to Debugger() in BII. The only thing I can get in response is a frozen screen. So time to move on to a different emulator.

That's a good point, I'm not even sure if MacsBug will work in Basilisk. But I'll spin up an app that calls Debugger(). That's a good start.

Does anyone know how to force a NMI inside Classic Mac (say 7.1) running inside Basilisk? Basically I want to break into MacsBug to disassemble some ROM code, and using Basilisk I can do this against a number of different ROMs. I am running Basilisk in Windows if it makes any difference. I...

Yep, did the same thing with my 145B. Now it is recognized as a 170. But it has a bit more umph now, which is really nice. Here is a quick doc I threw together from the Apple parts list, showing the interchangeable daughterboards for this series.