Jump to content


  • Content Count

  • Joined

  • Last visited

Profile Information

  • Location
    Southern California

Recent Profile Visitors

338 profile views
  1. jeremywork

    PowerWave weirdness | picky about video card

    I would verify whether this behavior exists when running in your 4400, but here are a couple of my observations in a 9600: I've noticed many of my ATI cards from that era (Rage 128, Radeon PCI, 7000, 8500) will send a short (1-3 second) dark signal to the display before the system is ready to output video. This usually results in: Power on keyboard (num/caps/scroll light momentarily, as the fans/drives spin up) Startup chime just following startup RAM test (longer for more memory) Monitor awake - black screen 1-3 seconds later monitor returns to sleep 2-5 seconds later monitor awakens again, this time displaying the Mac's checkerboard pattern nearly immediately. I've found in cases where something inhibits startup, the ATI card will still wake the monitor the first time, but will remain inactive after the initial 1-3 seconds. For instance, if I install a 3dfx card alongside the ATI card, the 3dfx card will only allow the system to boot if it detects a monitor itself. With two screens: The ATI card does its initial flash, the 3dfx screen turns on, then the ATI screen turns on. With only ATI screen (3dfx card still installed): The monitor turns on, displays black for a few seconds, then goes back to sleep. No hard drive activity in the background. With only 3dfx screen (ATI card still installed): The monitor turns on normally and the system boots. The ATI control panel does not detect any hardware. If your Rage 128 also does the double-wake in your 4400, then I would ignore the symptom of the monitor turning on and just treat it as a normal no-video symptom. Beyond that I don't think I have any more specific advice, but I would see if those math tests still fail immediately following a PRAM reset. If the presence of the Rage 128 causes the PRAM to become corrupt that would be interesting to know/examine.
  2. jeremywork

    Sonnet Crescendo L2 500MHz 1M

    That thread was very helpful for identifying cards online. I've luckily come by a couple rev 1 OrangeLink cards and one of the Tango 2.0's (trio form factor.) As-is, the trio works for all purposes as a tango 1.0/2.0 as well. I might try sticking it in a 5500 or 6500 to see if it behaves any differently than the TAM. I know all the boards are the same, but I have found some things aren't happy with the TAM ROM, but work in my 5500.
  3. jeremywork

    Sonnet Crescendo L2 500MHz 1M

    It looks like Sonnet thought this would work at one point at least. And they continue to mention 6400 and 6500 support in the latest manual, still hosted by Sonnet. http://www.zone6400.com/files/Sonnet_Tempo_Trio.html One thing I hadn't considered was checking the firmware version. http://www.sonnettech.com/support/kb/kb.php?cat=344&expand=_a1_a3_a13_a2_b338_b440&action=b439#b439 The advisory on the 4.5.0 firmware states: (I think that's meant to say 4.5.0, not 3.5.0) edit: just caught it says Mac OS X versions, not Mac OS versions. Not contradictory. The advisory on the 4.0 firmware is only slightly contradictory: I'll see if I anything changes when I run the 4.0 firmware (going on the assumption that the one in my TAM was flashed with 4.5.0; seller did pull it from a Quicksilver so that's a good possibility.)
  4. Very cool, glad to see it already on macintoshgarden too. Thanks for doing this!
  5. This works in my Quadra 950 with an Apple tray loader (OS 8.1) The tray does need to be closed by hand, but it will eject regardless of whether there is a disc inserted. Nifty!
  6. jeremywork

    Sonnet Crescendo L2 500MHz 1M

    This is the one in my TAM. I'll have to grab a picture of the one in my 5500, but it was similar enough I assumed it was identical when I installed it. Also, once the Farallon FastENPlus extension is present, it is not necessary to load the built-in Ethernet extension, but verify the EtherTalk extensions are installed, (IIRC the Farallon installer doesn't include them.) Edit: Here's another source for drivers (v2.4). Zone6400 seems to indicate shutdown issues with this version for some people, but might be worth a shot if the others don't work: https://web.archive.org/web/20050301085121/http://www.proxim.com/support/all/maccard/software/dl2001-09-10g.html
  7. jeremywork

    Lessons from Quadra, PDS, and DOS adventures

    That theory makes sense, and yes, from what I've read the socket will physically accept later 3.3v DX4 and 5x86 processors (they can only operate with the proper interposer with VRM.) Are there significant downsides from running without bypass caps? Would the processor be more susceptible to crashing? Separate (probably dumb) question that I couldn't find a quick answer to: Can you convert the Houdini I to a Houdini II by adding a Vibra16 module? Are the ROMs different?
  8. I finally acquired a Reply extender for my DOS card- the original Reply card (without the Vibra 16 module, so maybe Houdini I) was also included with a Cyrix DX2-66, but several components were burned away on the back of the board, so I swapped it for the Houdini II with an Intel DX2-66 I already had. The Reply card should be repairable, but something clearly wasn't right (allegedly this was a working pull from a Q900.) When I installed the Houdini II in my Quadra 950, despite countless permutations of 7.1, 7.5, 7.6, 8.1, open Transport 1.1.1, 1.1.2, 1.3, and DOS drivers 1.5, 1.6.4, and pcSetup217f, the furthest I got was: the PC would begin booting and could be switched to, but as soon as the BIOS would search for devices to boot from, Mac OS would crash. If I started the PC without switching to it, this freeze would still occur, and force quitting Finder would allow me to go back to the PC setup control panel and stop the PC or switch to it. Starting the PC again would generally result in a freeze that would not be recoverable. This persisted with nothing else in the Nubus slots, and only a single Apple SCSI hard drive and Apple CD ROM installed, Floppy drive and Ethernet were working as well. In retrospect, the one thing I didn’t think to try was putting the 950’s serial ports in compatibility mode, but I doubt this would be the cause. I decided to pull out my Quadra 700 to test with, and then discovered something useful that wasted a couple hours: Using my Moniswitch setup, I learned the OEM Apple monitor cable I had previously connected to a IIci (with all pins populated) is incapable of transmitting the 832x624 resolution, while working fine at 640x480. This results in a seemingly no-video symptom while the OS boots in background, but after PRAM reset the video works- until the OS tries to reset to the last known setting, when the monitor turns off. I assumed the Quadra 700 had developed some problem with its VRAM (6x256k SIMMs installed, and I had moved it several times since last booted) and that 24-bit color was what was making the video signal go dead. After twice tearing the machine down to reseat them I tried a Radius video card and booted to the desktop, set the color settings, and as soon as I changed the resolution I figured it out… sigh. Those SIMMs are super-inserted now I guess! That cable also lead the PC Setup control panel to show a message about the monitor not being compatible. As a bonus though, after using a different cable I was able to run the DOS card in the Q700, despite it having a Quaddoubler/Quadra Overdrive Installed. Internet legend seemed to point to the PDS being disabled when running a Quaddoubler, but the Houdini II seems to work flawlessly so far on 7.6.1/OT1.3/PC Setup 1.6.4 (I blew out a floppy eject gear while installing the DOS drivers, but DOS 6.22 starts and runs while I wait for the 4-pack of replica gears I ordered. I swapped in what turned out to be a spare 800k drive, oops.) The Quaddoubled Q700 actually arrived to me with a 33MHz Daystar Quadra PDS 128k cache card installed, but no driver was installed on the included hard drive. When I installed the QuadControl cdev, it would immediately hard crash on load, without even a bombshell. It’s not clear to me whether this is a result of the PDS stepping up to the 50MHz speed of the 040 when the bus line is released, and the 33MHz parts on the cache not being able to handle that (typical wisdom says 40MHz is about as fast as it would probably overclock) or if instead it’s because the PDS stays at 25MHz bus speed, and the cache misses every other call when the processor steps up. In either case, the 33MHz cache works perfectly in the Quadra 950 that rejected the DOS card (with the same Quadcontrol cdev,) so I’m glad that both cards and both machines work one way around, but would still be curious to know if anyone has experience with similar DOS card symptoms (Later finding: the Q950 fails the Logic Board components diagnostic test, which my other 950/PPC passes. The error is not specific, but I have a third spare 950 board... will look further into this. PRAM reset fixed this, which I tried many of during DOS card troubleshooting. Good to know the board passes the test.) Otherwise all I can find points to issues with incompatible Nubus cards. I can confirm that the freeze happens much earlier if a Nubus Video card is present- nearly instantly, as the screen just begins to fade on its way to switch to the PC environment. The Q700 was benchmarked while the DOS environment was running, so the Quaddoubler is operating normally. Also side-note: The Q700's case door essentially closes without needing modification, It's just very difficult to align correctly, as there is essentially no clearance between the end of the SIMM slot and the card guide on the case lid. I've found success closing it with the tabs not quite inserted (lid overhanging the front of the case a smidge,) and then sliding it back as the door is nearly closed. This difficult alignment appears to be why some sources say you can squeeze the lid closed, while others say it's completely impossible.
  9. I took a longer look at this picture and have a couple more observations. My 840av is out for the count so I can't directly compare, but that internal bus reading looks too low- either the SCSI2SD will have no benefit in the SEIV, or there's some other bottleneck here. I get over 3MB/s on a period 230MB hard drive on a Quadra 700, and a bit over 4MB/s for a later 1.2GB drive on a 950. The 840av having a faster bus should put it even closer to the 5MB/s Synchronous limit of its SCSI controller. On the other hand, your SEIV is much faster than I can achieve in my 950. I can only get around 8MB/s on a 15k SCA>68pin, but that's almost all due to lack of full Nubus 90 support, which the 840av has.
  10. jeremywork

    Sonnet Crescendo L2 500MHz 1M

    Re-reading the readme, I now see it explicitly mentions only the USB and Firewire functions when describing the Trio: • This software installs an Open Firmware patch in Power Macintosh 6500 computers enabling them to fully support the Tempo Trio’s FireWire and USB ports. Oh well- I may compare my two Trios to make sure I get the same behavior from both. On a separate note, am I correct in remembering the patch just manually defines the resources for each of the two controllers on the Tango? If that's the case, it seems feasible to support the third controller on the trio. I am by no means an expert, but by analyzing the effect the patch has on the PRAM on the Gazelles, we could likely track down the info it patches to enable the USB and Firewire controllers. Then we'd compare to resources automatically pulled by a non-buggy PCI machine like the 9600, and derive a similar PRAM modification to enable the missing ATA controller. Is this something that's been done attempted already?
  11. jeremywork

    Sonnet Crescendo L2 500MHz 1M

    Very interesting to hear you get different results with different hardware. By the time I had a second Farallon card around, I had already found the working driver for the first one, and that same driver worked to run the second one in my 5500. (This machine is running a NewerTech 400/1M that the TAM refused to boot with, alongside an OrangeLink USB/FW- also no conflicts, in fact video playback is sometimes smoother than the TAM despite being two steps slower, in cases such as After Dark.) The Tempo Trio has been a project I've only begun tinkering with. I have a second one in my 9600 that I can boot from with no issues, so from an OS support standpoint it should work. I'm relying on the fact that the TAM works fine with the Tango 2.0 (the one that's a Trio with the ATA hardware missing) and that the firmware enabler Sonnet provided also mentions Trio support. The one time I did bodge the wiring together to connect my CF card to the Trio's ATA, the device wasn't recognized, but I can't be sure my power leads were effective (I just jammed wires into the respective pinholes on the built-in ATA cable.) I was able to use USB and Firewire over the Trio though, after putting the CF card back on internal ATA. Unfortunately my TAM needs both of its drives serviced; I have all the hardware ready, but haven't felt like starting that one yet. I have a CD150 on the SCSI bus, which is bootable, but the floppy drive read head is stuck blocking diskettes from being inserted, so I wasn't able to make a modified disk tools floppy. Next time I work on that I'll stick an external hard drive on SCSI and bring a molex splitter so I can be sure the CF card is properly powered. Might just try an old full size IDE hard drive powered off a sled, too. I had everything nicely routed and fitting with the fatback closed, so I'm not ready to give up yet!
  12. I'm not really sure, as once I was able to successfully create a 2GB Mac OS Standard partition, the system booted without trouble. I took some data from Anubis and TattleTech; perhaps comparing to yours will help you spot a discrepancy. The machine I'm running on is a Quadra 950 with its PPC upgrade enabled (SCSIManager 4.3 in ROM.) ANUBIS™ Log #1
  13. jeremywork

    Sonnet Crescendo L2 500MHz 1M

    My Farallon CSII card was quite finicky when it came to drivers. Most of the ones I tried resulted in intermittent lockups of the finder, corresponding to associated link lights on the card. I can double check next time I'm nearby the TAM, but I recall the drivers hosted on zone6400 working for me... http://zone6400.com/downloads/FastEther10-100+V2.2.1.sit If not, let me know and I'll grab the actual extensions off the TAM. It's working alongside a Crescendo 500 and a Tempo Trio, no conflicts or audio stuttering.
  14. The only SCSI2SD I have is the older PowerBook edition, and I haven't tested it with SEIVs. Having worked with hard drives on the SEIV though, I've found it refused to boot until I reduced the partition size (2GB Mac OS Standard worked in my case; I can have larger partitions, but if I select to boot from them I get a happy mac for only a split second before it disappears, and retries from the next available device.) Are you seeing the SCSI2SD when booted from another disk? I was able to format the drive on my SEIV with ANUBIS 3.0.1 (I suspect later versions would work too,) where few other utilities cooperated with the second SCSI controller. Did you successfully update the SEIV to 2.1rc2? I recall having to manually specify a Nubus slot ID, as I believe the auto detect feature doesn't work for the beta firmware.
  15. SEIVs need SCSIManager 4.3 in ROM to be bootable, which 68k machines generally predated, but I believe the two AV Quadras are the exception here. In my Quadra 950, the SEIV is bootable when running from a PPC upgrade card, as well. https://tidbits.com/1994/11/07/why-scsi-manager-4-3/