Search results

I just bought one off of Dan Knight (of LEM fame) and should have it by the end of the week. Undecided if it’s going in my 700 or 950. Does RocketWare work at all under Mac OS 8?

I’ve also pulled all the VRAM and RAM, essentially running the 040 on a bare board. Even burned a stock Q700 ROM to a SIMM and booted with it, to no avail. At this point, I’m trying to get mouse movement before the flashing ? floppy (since I see no reason to involve SCSI at this point). 

Yes and I’ve just done so. No change. I once read something about TechTool’s PRAM zap to be more thorough than the usual method. The problem is there is no keyboard shortcut once you launch the app so I can’t actually do the zap.  Which led led me to the aforementioned ADB renewal/resets that...

I can (limited) navigate with the arrow keys and shortcuts where possible. Power key works to bring both up and down. Combinations like Cmd-Opt-P-R also register. 

CD is booting now. Same exact behavior.  Not that I think this is relevant but this is all onboard video up to this point. Recall this stated with an apparently bad/haywire Radius 24xj. 

Frozen and I’m booting from SCSI2SD, the original Barracuda and even a 7.1 floppy. And done so with and without the 601 PDS card when possible. What I haven’t done is to boot the Legacy Recovery CD. 

Yes - I usually use a 3-way ADB KVM but did away with it for this troubleshooting effort.  I’ve tried: * keyboard + mouse in separate ADB ports  * keyboard + mouse daisy-chained as usual to single ADB port * just keyboard * just mouse Both devices work fine on other machines. Only mouse...

Sure. The ADB ports are J3 and J4. The ASIC is U12 for reference.  Good thing I can’t sleep tonight! (US-Florida)

Here’s a picture of the above-mentioned ASIC 342S0440-B. I poked around the chip - each pin’s solder joint appears to be intact. I did notice the fuse above it but assume that blowing would be obvious AND be all or none?

Well, the great news is I got everything - including olePigeon's ROM image with the DayStar Turbo040 driver included. What I don't have is a working combination of that base ROM and the 8 MB ROM disk driver - also I would need to tinker with it to disable the memory test, but the Turbo 040...

Most definitely. The original owner never used it - I got the full box w/ manuals, etc. Everything you see in the video. Shame because, even though the 601 card is running at 66 MHz by way of the clock chip, could manage to get 80 out of it with the PP. Anyway, maybe it never worked because of...

@Swolfington Finally had a chance to take some measurements (I can't find my metric slide rule so I had to go with 1/16s) Looks like each rectangular button is 13/16" (.8125" or 20.6 mm) There is a gap of 2/16" (0.125" or 3.2 mm) So, unless I have fat fingers, that means an outer width (end...

Trag - thanks for the thorough reply on this. I wasn't able to find a CUDA chip on the Q700 board (nor a reset for the CUDA like I'm used to seeing on my Power Macs & G3. For what it's worth, I was trying to figure out how to get the Newer Technology PowerPump working on this machine (came...

Sorry again about the SIMM! But thrilled to see it’s been revived. It gives me hope for the boards I have in worse shape. 

Bolle, when you are burning these smaller ROMs (I believe Sunoo's IIcx ROM was only 256 KB), are you erasing/writing to the entire SIMM? Or are you appending to an existing ROM disk image? I can't get past this first step unless it's a full 4 MB/8 MB ROM.

Note to defunct manufacturers: go back in time before you started production and label your damn boards.

So, my Q700 that was only in my hands for about a month is suddenly having hardware/ADB issues as well as the 950 I've written about here. Background is above. Pardon the crosspost but I wouldn't normally hang out in the Peripherals section so maybe others wouldn't either... and this...

For the record, I LOVE this idea for all the reasons you mentioned in your OP.  A similar but less functional approach (but also less involved, electrically) would be to load all of your ROMs up once and select them from a basic UI/menu, like a FloppyEmu, RetroPie, etc. Now this isn't my...

So a slight update... Turns out I can resolve all of the video artifacts/interference by plugging the Thunder/24 back into its (or another) NuBus slot so this appears to involve the onboard video port/system.  Something's still amiss, though. I get what's literally called "double panic" trap...

Something that I'm not clear on after reading through the ROM-inator II docs & ROM hacking tutorial - using a stock IIsi as an example - (512 KB = 524,288 bytes) Shouldn't I be able to burn that to a 4 MB or 8 MB (MEGA) SIMM and, with the requisite shimming/bracing, it just works? And same...