Search results

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.

Well, the ROM I am using to test with is the LC475/Q605. Offset 1278 is the named resource that the INITNETBOOT routine attempts to open automatically. So I believe this takes care of executing the Open routine. My issue is with within the Open routine, getting the drive added to the queue. I...

Yes my bad, I'm still learning all the names in this community :) @zigzagjoe was the Joe I was referring to. Thanks all, this is all very helpful. And in a way so cool to get into 68K programming. A much younger version of me is very jealous right now. My new driver is pretty close. But I am...

Thank you @joevt and @cheesestraws. The 4-bytes of padding and alignment make sense to me now. @joevt yes I've been looking at your sample RAM disk driver as well. @Jockelill pointed that out to me a little bit ago :)

@joevt I do have a question, not sure if you can answer though. I am writing a new ROM/RAM disk driver from scratch, and in the Resource Header for drivers in the ROM, I am curious what the purpose bytes 33, 34, 35 and 36 are for?

Yeah, I think I got my 128MB SIMM that was specifically designed for "angled" sockets. Looking at my SIMM, the side that is angled towards the motherboard has much smaller (thinner) chips. Here is the link to the SIMM I bought from Amazon. I first made the mistake of buying a non-angled SIMM...

Did a quick move of the ROM disk driver to the free resource at offset 60080. Works like a charm, and the original ATBOOT resource is still available. Just gave it the generic name ROMDSK for now. It appears that pretty much all the 1024KB ROMs have these free resources. Might be a good...

@joevt your dumpromresources is just a fantastic tool, BTW! Wanted to pass along some kudos to you. Thanks for continuing to improve and enhance it. Those free resources were a surprise to me, too. I first noticed that because a free resource just happened to come after the ATBOOT driver...

OK disregard my last two posts. I actually wish I could delete them. But I started rebuilding the resource table in the C&Q 610 ROM, and I realized that the larger ATBOOT driver really was not stepping on the next resource after it. This ROM actually has a handful of bytes not in use in between...

Yes sure enough, did a quick test and moved the NETBOOT resource to offset 04 0F 10 (plenty of free space there). Had to adjust the NETBOOT resource header, and also adjust the next resource offset in the ATBOOT resource header. But this did the trick. NETBOOT driver, even though generally...

100%, you are right. ATBOOT and NETBOOT are different driver resources. There is a lot of free space in the C610 ROM, so I think the resource list could easily be rebuilt to push things around. I will attribute this overlap to laziness on my part :) But, I was also thinking of potentially...

Attached is a write-up for the Centris 610/650 & Quadra 800 (ROM checksum F1A6F343). The hacks in this document assume a 7MB ROM/RAM disk and the 8MB CAYMAC AUTO-SENSE ROM SIMM. Interestingly the size of the ATBOOT driver in this ROM is 4-bytes smaller than the ATBOOT driver in the LC475 ROM. So...

I think this is pretty darn cool, in my opinion. And you're keeping a Q840AV alive, which by itself is just awesome!