Search results

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.

Wow this is fantastic work!!

@adespoton it would be really cool to find a working netboot floppy to dissect! So just to nail down this conversation with NETBOOT. I did some more testing, and can confirm no issues using this resource for a ROM/RAM disk driver.... as long as I change the resource & driver name to something...

Yes this could very well be the case. Just out of curiosity, I did a little digging using Resorcerer: OS 8.1- SYSTEM file contains a reference to NETBOOT in the BOOT3 resource. I could not get OS 8.1 to boot with the ROM disk inserted as NETBOOT. It wasn't until I just moved to the FREE...

OK I am calling it a night.... But made REAL progress today. Importantly, I have a question for all the smart people here. Have any of you tried overwriting the NETBOOT driver specifically on the 1024KB / 68040s? After using @zigzagjoe's nifty code to add the drive to the queue, I still could...

I think I am having way too much fun these days with 68Ks. A much younger version of myself is very envious of what we can do today with these machines!

So incredibly helpful! I did try to use the AddDrive() without any luck, and the comment below is probably why. AddDrive() is missing in the Retro68 library. /* FYI, missing in library with Retro68 */ /* void AddDrive(short drvrRefNum, short drvNum, DrvQElPtr qEl); */ Thanks all!

OK did a bit more poking at my driver today. Turns out 030 vs 040 was not the problem. My disk driver works great with System 7.0 and 7.1. But not with 7.5+. I really think this boils down to how I am adding the drive to the queue. I am using the Retro68 toolchain to compile my driver. I want...

So just out of curiosity, I threw my driver into the IIsi ROM and burned that to a SIMM. Works just fine in a IIsi but not the LC475. Maybe the code I am using is better suited for the 68030 than the 68040. Back to the drawing board.