Search results

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...

I checked the v1.2 and v1.3 ROM files and they are both OK. I also updated the above post with the ROM .zip file with the verification info. So, I will find/fix my disassembly error. Maybe just an offset problem Update: Yes - I was forgetting that offsets are relative to the start of each...

I received my 27C256s, so I will try the 1.3 ROM tonight. I did some manual disassembly on it and the declaration ROM doesn't seem right to me, but I will burn it and see. I have started to refresh my memory from SlotEqu.a, ROMEqu.a and Designing Cards and Drivers, and it didn't look like the...

Here are 2 of the manuals, plus the 1.0b tools CD from 1991 (for A/UX 2.0). I just opened a shrink-wrapped disk that is 30 years old! :D I was able to extract the A/UX Developer Tools 1.0b1 CD .iso via Nero on Windows. It mounts under SheepShaver as a .toast, albeit without desktop comments...

Some progress -- I got an external CD-ROM drive to rip the disk .iso. Also, since my original post, I have been thinking about old video boards and Spectrum/24 Series III v1.1 should work well under A/UX. In addition, Spectrum/24 PDQ should also work. And, given the changes that went into...

My Spec/8 III board is v1.2, so when I get the replacement ROM, I will compare the ROM against the enclosed file to make sure it matches for the sake of completenesws. But...much better to use v1.3 for the Spectrum/8 Series III anyway. I have mentioned SuperMac's VDI implementation in other...

That's it! I created a new .zip file with renamed ROMs, bitwise inverted files and a text file with the part numbers (in case anyone really cares what the part numbers were). Zip File Contents: Spectrum8SeriesIII-v1.2-ROM.bin Spectrum8SeriesIII-v1.3-ROM.bin S83-v1.2-Inverted.txt...

I found those - didn't see any indication of a clear version number...and those are the same files that are included in other archives. I have to de-invert them to check the versions.