Jump to content


  • Content Count

  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I would also recommend redesigning the battery circuit to use a safer chemistry. The chemistry that the 3.6 volt lithium batteries use is extremely toxic in addition to being corrosive.
  2. Looking at the schematic on the last page of the PDF, specifically the lower right hand corner: J1 10PINPWRCON is the connection to the internal greyscale board U12 IH5341 is the switch that controls whether built-in SE/30 monochrome or graphics card greyscale is used The internal greyscale signal comes from the IOB line, which originates from the Bt478 RAMDAC. (family datasheet: http://www.citylan.it/wiki/images/9/90/Bt471.pdf) The IOB line is the Blue RGB channel that also goes to the external monitor output. So basically — everything is pretty much the same as a standard graphics card (that is able to output at roughly 512x342), with the blue channel used for internal greyscale, and a switch IC used to switch back to monochrome when an external monitor is used. There are some other lines going to that connector for sync but I don't think there's anything terribly special about them. Would need to see the schematic of the CRT neck board to know for sure.
  3. balrog

    Microtech SCSI to USB adapter help

    I’ve recently used one of these with a Linux VM on a modern Mac to image an 80GB SCSI hard disk. Yes it took a while. Key takeaway: the adapter is not USB powered, but rather is powered by SCSI termination power. I used a Jaz drive to inject termination power, but another method could be used as well.
  4. There’s also a .sit file containing source code that you can only see if you select “show all files”. Be sure to check that out as well!
  5. I finally uploaded the Micron Xceed schematics and source code that I have and they can be found at the below archive.org URL. I believe these are for the Color 30 card, but I'm not certain. Hope this makes for useful information! https://archive.org/details/MicronXCeedTechDocs — you may have to click "Show All" under Download Options.
  6. balrog

    Second Wave PCI Nubus Expansion Box

    To solve the mystery, that was me. Sorry for reviving such an old thread. The box was a pn400 though, not a pn800.
  7. balrog

    Second Wave"s PCI -> NuBus Expansion Box & Others

    There's some information here about this thing that's fairly useful: http://web.archive.org/web/20060314030428/http://www.2ndwave.com/readme.asp?ProductID=53&mscssid=EQXWUBX3KQCS9LWV1G1K3T0KW9TT13S2 The general page with info on these is at: http://web.archive.org/web/20060314025641/http://www.2ndwave.com/support.asp?ProductID=53&mscssid=EQXWUBX3KQCS9LWV1G1K3T0KW9TT13S2 Drivers are available there too (the PN200 drivers should work with all versions).
  8. balrog

    Booting and gray screen...

    The structure of this ROM is as follows: 3 MB on ROM SIMM 1 MB on flash chips The ROM SIMM is not supposed to change, but the Flash chip can and did during development. This was the reason for only 3MB being checksummed: the last 1MB, which resided on the Flash chips, could easily be changed. Therefore, the fact that only 3MB was checksummed was NOT a bug, and was completely deliberate! What utility was used to dump? We usually recommend CopyROM from http://www.emulators.com/freefile/MACUTILS.ZIP because many other dumpers only grab the first 3MB or otherwise scramble the dump. Would it be possible for a re-dump to be taken with this version of CopyROM, as well as a screenshot of the CopyROM window? This would establish whether the ROMs actually are weird, or that the dump was bad. Thank you!
  9. balrog

    Booting and gray screen...

    None of these dumps seem have valid checksums. Could they possibly be redumped? When dumping, always take multiple dumps and verify that they match. If you've done this and they do match, then something weird is going on. Thanks!