Search results

Ah - crap - it's the wrong part. I grabbed it, did all that work and just realized that it is a IIfx one, I think.

** SORRY - I GRABBED THE WRONG SWITCH - I HAVE TO LOOK AGAIN - WATCH THIS SPACE FOR AN UPDATE - I WILL ADD NEW PICS ** @Paralel @retr01 @Andy - I am home now. Attached below are the pictures of my SE Programmer's Switch after repairing it using the above-described heat gun method. Both prongs...

I posted the following historical/technical information about the SuperMac Enhance memory upgrade for the Mac 512Ke on 68kmla.org and am also posting it here to ensure that it survives in more than one location. Also, @JDW did some of the original sleuthing to find an answer. So, here it is...

Yes - as far as I can tell without destructive testing. I was able to fix and straighten mine using the above-described method, the fatigue appeared to be improved and the white/light crazing was gone. At any rate, the fatigue was not worse and the switch works after severe bending. I heated it...

You should be able to fix that issue with a heat gun. The prong will probably survive if you are careful. @retr01 's switch already shows the tell-tale plastic-fatigue-of-death stress highlights. Heating should allow you to address/reverse the fatigue.

Apple's switch design was kooky, weak, expedient and prone to user-induced failure based on design and materials, tempered by the fact that most users didn't open their cases (or use the switch in the first place). So, the scenarios that led to failure were behaviorally-limited (and may be more...

I needed a programmer's switch for my Macintosh SE/SpeedCard and looked around for a vintage one, but ended up getting a new MacEffects Clear Programmer's Switch. I decided against using a vintage switch because, even when they were new, they were somewhat brittle and lost clips under mild...

I vaguely remember Mobius, but I don't think I know anything about the SpeedScreen SE. Sorry.

🖥️🦃 - Now...if I can just dress this thing up like a turkey, when they put in the oven...mwahahaha!

@JDW It might be possible. I will try to shift a little time in that direction. I also need to wrap up my Mac II FPU testing. I will also try out my ProdigySE board. My 68K workspace is in video board chaos at the moment and I also have to get my drive storage sorted out.

@JDW re SpeedCard - I have been super busy for the past couple of months. I will still look at what we discussed. Otherwise, I have been trying to find a SpeedCard, but no luck If someone has one they would like to get rid of/sell, let me know.

I have been too busy over the past month or two to try it, but I plan to set it up on my 950. I have to make a cooled enclosure for my drive. Then I will try to set it up with a 1360 x 1024 board, assuming I can find a flat panel that works properly.

OK - sounds like it's probably a PPC-related issue. Thanks for the help everyone. I'm tired of SheepShaver's issues - the scrolling/paging click-slewing is poorly implemented and nearly impossible to use. Plus, no Macsbug/NMI support. Don't get me wrong -- I think that the emulators are...

Does anyone know about compatibility between Think C 6 and System 7.6.1? I am trying to use it under SheepShaver and it's not working very well. I get hard lock-ups or endless hanging when I try to build under SheepShaver. Back in the 80s and early 90s, I seem to remember Think C being buggy...

My C is definitely rusty, but in the d1 line above, isn't the () going to resolve before the +? Shouldn't it be: (double)(a + b)? I guess I have to go look at a freaking precedence table or something. Oh, I see -- never mind - that's what you were trying to show. I will look at the 68K later...

Just look at the 68K assembly - it will be immediately obvious what the problem is. If it's a compiler bug, then you will see it. Also, you may have better luck with the extended data type...or not. I forget...but will try it. Also, Think C has compiler options for code optimization and also...

Good general summary. Here are some additional considerations and reasons for walking the device tree: 1. Calling GetMaxDevice() and then assuming you can or should run on that screen may not necessarily be the right programmatic assumption. Walking the device tree allows you to see what's...

Regarding the mention above of going through all the devices, the way you would do that is to call GetDeviceList(), which returns the first device. Then, you might want to check the gdPMap of that device or do other checks. After that, the next device in the list is stored in "gdNextGD", so you...

Regarding checking the OS environment for the general presence of color (vs. specific gDevice depth), Gestalt calls are often very useful and important to know, but checking certain things via the Trap Manager can sometimes be more efficient/straightforward. Anyway, below is how to do a basic...

I extracted the Apple Sample Video ROM from the 1990 version of Designing Cards and Drivers. This example ROM was the original basis for SuperMac's Spectrum boards. I used it as an exercise to refresh my memory in Declaration ROMs, assembly, etc. I am most of the way through an initial...