Search results

I see...bodges were done before the board ever left the factory...ROM01 upgrade would have come later. But in a nutshell, the presence of the bodges (and possibly the 'A' board revision?) suggests it started life as a ROM0 board? That would then suggest that I have a "real" Woz machine instead...

Hah, I was about to post asking "what are these bodges on the back of my IIgs board" when I saw this. I just found that my board has identical modifications: https://tinkerdifferent.com/threads/is-this-iigs-board-a-rom0-that-was-upgraded.2043/

I've had a IIgs "Woz" edition for awhile, and I finally took it apart to recap and retrobrite. It's always reported ROM1 when booting, so I kind of assumed that someone had just put the Woz top on a non-Woz machine. However, when I got it apart, I noticed a few things: The logic board is the...

I don't. I just have the power workstation and a few of their accelerators.

Oh snap, I started to remove the drive's PSU to recap it (why not?)...maybe I shouldn't turn this thing back on :LOL:

Anyone have experience using SCSI hard drives with an Apple II? I have yet to ever use a hard drive of any kind with any of my Apple II's, so I have no clue where to start with that, but I found this CMS SCSI card in one of my IIgs's: I also have this CMS model SD30U external SCSI drive...

Sure. At a high level, the way this works is it shoots a ray from the "eye" through every pixel in the view port. Each of those rays bounces around and builds up a color for that pixel. That means that there aren't any dependencies between pixels, or anything that would prevent shooting all...

Ya, and like I said...I have made zero optimization passes over any of that code...it was just "get something that looks correct on the screen" :)

Depends on the settings and window size :) Let's assume the default window size for consistency. Then, with the following settings: - Reflection = ON - Refraction = OFF - Shadows = ON - Specular = ON - Max Recursive Depth = 10 it takes ~47 seconds to render on the 040 IIci. Turning...

Ya, I've been following that...looks really cool! I haven't looked at the code at all, but I had some questions (that would probably be quickly answered if I did look at the code :) ): - Are you using QuickDraw primitives for rasterization? Like, basically transforming a scene-space triangle...

I assumed as much. Also, some of those routines can apparently be hand-optimized. And my implementations of things like sqrt(), pow(), and exp() are very simplistic and rely on some limitations (integer exponents only, etc). I remember using look-up-tables for some of those things, as well as...

So my "project" after chapters 4 & 5 was a simple ray tracer that allows configuring rendering options via menus. It currently only supports spheres (cause they're easy), and supports diffuse and specular shading, as well as reflections, basic shadows, and basic refraction/transparency...

Ya, that's how I would actually implement it. Just wanted to confirm that the kAEQuitApplication handler was the correct place to respond to that scenario (seems like it obviously would be, but my classic mac programming experience is currently limited to the first 5 chapters of this book :) )...

Ya, that's what I had to do to see keyUp events. I stored the current value of SysEvtMask in EventInit(), called SetEventMask(everyEvent), then set it back to the original when my program exits. What would be the recommended place to restore the original event mask if my program exited...

That looks to be doing the same as my EventTracker code (the code from book pretty much), and when I restart with EventTracker running, its kAEQuitApplication handler fires. I'm running 7.1 though. Does AEInstallEventHandler() return noErr for you?

I don't know the answer to that, but maybe the error string drawn after calling Gestalt() ("Problem in calling Gestalt!") is just too general in the interest of not complicating the example program? You could always do something like: err = Gestalt(gestaltAppleEventsAttr, &feature); if(noErr...

In case anyone experiences the same issue: I was having trouble getting the "EventTrigger" example program from Macintosh C Programming Primer to successfully send high-level events to the "EventTracker" example program. I triple checked my code as well as EventTracker's SIZE flags and creator...

Is it not in the thunderv1.2.3.sit file here? https://macintoshgarden.org/apps/micromac-accelerator-software

Is it a linker error or a compilation error? I get that linker error if I don't link against the MacTraps library. Did you link against the MacTraps library?

Sure...code is attached. I've only compiled it with ThinkC 6 on System 7.1. Be sure to link in the MacTraps library. I don't think this code will work on System 6 either (I think System 7 is needed for offscreen graphics worlds). Chapter 6 in this document was helpful, though I don't claim...