Search results

@Bolle - yep. ;-) However, the 1600 board looks like a respin that probably has some improvements (and/or cost reductions). And yes, you have 2 1600s, albeit an older and newer one. There's no reason to pay more for a Thunder IV 1600 board...well there may be bug fixes - you should burn-in...

Bolle - have you tried swapping the ROMs on those boards? The 1600 just looks like a relayout of the 1360 board. Also, if the Radius ICs are post-merger rebrands, then all you need is the sRsrc data from the 1600 x 1200 sRsrc. However, BSR is obviously not the same since it must be...

There are some flags bytes in the vendor use fields. So, when you see what looks like a fixed value, you could just be looking at binary flags. Compare against SecondaryInit, etc. There are definitely run flags for Secondary INIT and QuickDraw 32. Also, there should be one for VideoOpen. The...

The easiest way to do the mods might be to just dump memory on a 1600x1200 board.

Historically, for Thunder boards, SMT was in the $c000000 range, SQD was in the $e000000 range and everything else was in the $d000000 range. But, don't quote me. Secondary INIT monkeys around with sRsrcs and the CLUT, so the $d0b0000 offset is probably the CLUT offset. There is also a 1-bit...

The empty functions are not errors -- they are most likely common code routines that had conditional flags that were compiled out (but still called). So...there is a bsr and rts and that's all. The delay is millisecond-based and uses TimeDBRA (low-memory global that holds the value for...

When you see an instruction like bfexts (bit-field extract with sign extension), it is probably interpreting a chip or board register. It extracts a bit value, sign extends it and then the code can do something with the resulting long value. It is simpler than multiple moves, btst, branches...

Sounds good. I may have commented on the A/UX thing somewhere else, but this thread is also a good place for it. I don't know if I knew that Mode32 called Close. Maybe back in the ancient days of yore. :D But yes to A/UX and if you check for Reset, you should see it being called under A/UX...

Amazing job! Wow! Looks cool. A few quick comments: There should be no issue in returning csBaseAddr. I'm not sure why it wasn't working for you. Maybe there is some library issue with the VDPageInfo rec? Don't know -- but, as you know, it is used in calls like VideoReset, etc. Anyway, should...

Looking at your data, the first long appears to be the resource length...and that would be typical. Every sRec starts with its length as a long. For example: Apple 13: 0x72 = 118 bytes; Length: 117 bytes + 1 pad SuperMac 19": same Through RasterOps 12", it's either 112 or 114 bytes. Again...

Just saw all of these messages. Sounds like progress. Sorry - I was forgetting about RAM refresh activity. I think that's a function of the video config. So, you could try using it as a secondary monitor and set a low-speed config like NTSC by using SuperVideo -- it should end up running at...

Good job finding the solder fractures. You should probably flux and reflow SQD01 and SMT02. Tapping only helps if the pin has intermittent contact. It could be a full open break/separation. However, the fact that you saw those 3 fractures means that others are likely. They could be anywhere...

Weird. Lots of information! A couple of issues: 1. The board has a default gamma table that is going to affect what you see on screen (but not the values in RAM). The default for all of these boards is usually the Apple Standard RGB Monitor Gamma. See Cards & Drivers. It derives from early...

Sounds like you are very close to the solution now. There could be via/pad fractures from impact or something hanging on the lines -- check the caps -- (and check any package fractures as you did before). Also, check SMT02 carefully. Definitely consider a chip clip - would be perfect for your...

Great job! Very thorough! Here is some additional information to add to your post: Micron Datasheet (at Jameco) for MT42C4256 : https://www.jameco.com/Jameco/Products/ProdDS/2280415.pdf For those who want to debug these VRAM devices, there are 28-pin SOIC chip clips that make wiring these...

The color/gray problem might point to a number of issues: 1. Bad data in a driver call. So, the driver misinterprets a color/gray flag in the paramBlock for SetMode -- or something like that. 2. PRAM gremlin as a consequence of whatever is going on with the card. 3. Some other random issue. I...

Right - so one way to track this one down would to write to a known address on the 68K side and wire the address bus on the card to see how the address is being decoded. You know the RAM mapping. Try to reproduce the problem starting at the base address -- like $E0000100 -- it's going to be...

Very useful info! Nice charts! Thunder, Spectrum PDQ+, Spectrum/24 IV and Spectrum/24 V are all very similar designs - mostly just marketing designations/rebranding and/or gimping (in the case of the PDQ+). Also, in terms of how things get moved around in accelerated mode -- one of the...

Oh - I see you have the Thunder 3.1 ROM in your picture. Perfect! We should compare benchmarks with my 1.6.0.1 version at some point to see if there were any accelerator speed-ups.

oh yeah - that one. Mashed pins, solder breaks, bad/missing parts and broken traces. :D