Search results

Below is a quick comparison of the Thunder II boards and some additional thoughts. Thunder II GX 1360 pic below with 3x Bt458LPJ135, socketed DIP ROM and a 14.31818MHz clkRef for ICS1494. The DAC is an 85-pin plastic J-Lead package and marked as -135 -- likely indicates the top speed (135MHz)...

@eharmon You're very welcome! It has been a looong time since I used to do this stuff - yeesh - ...but it's definitely helping me remember -- especially hearing the name Ardent and seeing the clock docs. I wondered how you came up with the part number, but then I realized from the pictures that...

@eharmon - good! That may be the best you can do. It sounds like you are having clock alignment/rounding issues with the missing pixels. Here are my morning thoughts: I looked back in the thread and your monitor is the E178FP. From the Dell User Guide, the supported modes are as follows...

Sorry - I edited my post above to add some additional info. Your HSB-HEB should be 160 @ x8 (active area) and HES may be too high, but it depends on the expected monitor timing.

Great job! And I definitely now remember Ardent and masking upon seeing this discussion. The 130.48Mhz frequency for $0f probably translates to 1280x1024 at 7xHz (and possibly a 16x multiplier). And, the different mask versions probably just indicate an extension of the same setup. The base...

@eharmon -- Great -- so that pins down the clock devices, as follows: Thunder/24 flavor boards (including PDQ+) are CLK-02 Thunder II boards are CLK-03 Thunder IV are ICD2062B

@Arbee -- Thanks for looking that up on the Thunder IV. Yeah - good point about CLK-02. Could be. 14.31818MHz is also the frequency used by NTSC, but is called out in the ICD2062B spec.

@eharmon - sure - happy to help! :) I was thinking about this problem last night, and coming at things from a different engineering direction, focusing on the CLK-02 (or CLK-0?) IC might be helpful. We know certain things about it. It is the clock synthesizer (in the lower right-hand corner on...

A couple of other details: The counter registers should be read-only. So, writes to those registers should be ignored, but I have never tried to write to them. :D And, now that I think of it, the VINT function should be the same as TMS34061. The point of VINT was to set a value that would...

@olePigeon You can have that 8*24GC slot hog. :D

The DSP boards were mostly application-specific acceleration. For example, photoshop made use of them - I think that was the primary use...but that was a lot of users. There were other apps also, but the support had to be designed into the app.

Based on the info I have previously posted, the addresses and access should be as follows: Given a base of Superslot (e.g. $d0000000 as in eHarmons post above) + $c000000, the timing-related register offsets should be: SMT register offsets (words or longs -- take your pick -- either should...

SMT01 worked...but was very buggy. Very sensitive to timing and had issues decoding properly in slot $b. If you sneezed on it, it could crash. SMT02 fixed those issues. Similarly, there were problems and crashing issues with the original BSR02 that were corrected in BSR03. SQD was very solid. It...

The values after HTOT and VTOT are going to be the counters...and I think they are read only. So, if you poll them, you will see them turning over. HCNT follows HTOT and VCNT follows VTOT. Also, no reason to type blindly -- hook up the Thunder as a secondary screen. ;-) I think in the...

Hi eHarmon - It looks like you're missing 1 clock on either side of the horizontal display. So, reduce HEB by 1 and add 1 to HSB. Adjust HTOT as needed. For the clipping at the bottom, you can try adding 1 to VSB. If that doesn't work or isn't enough, then you may have to shift the entire...

SuperMac had custom timings for Apple, RasterOps, Radius, et. al. Everyone had to have their own proprietary timings to make things hard for consumers. But...SuperMac supported most/all of them. 16", 19", 21", Apple Portrait, MultiSyncs, etc. (and they were usually all in ROM)

Regarding the sRsrc format, for the Stock 1280x960, here is what I see by attempting pattern-matching vs. obvious data types and working forwards/backwards, etc.: original data: [00000076 1F320000 50020600 4F010101 000F001E 00BE00C9 0002002D 03ED03F0 FFFFFFFF 00E7FFFF 0000FFFF 00000000 00000000...

Ah, so you have the SuperMac VideoHelper stack that I posted a while back, eh? :D

@jmacz - In an earlier post, I think I mentioned about adjusting the vertical value. You have a working config at 1280x1024 with the caveat that it you can't see the entire vertical area. However, it should be easy to find the SMT02 timing offset in the sRsrcs. Try the following: 1. Take a...

The timing data is in the video sRsrcs. Just compare the sRsrcs and resolutions and it should become apparent. If you have a Thunder II 1360 and a Thunder IV 1360 side-by-side, you can compare the sRsrcs for the 1360 config to see if the timing values are the same. If they have common...