Jump to content

blindowl

6502
  • Content Count

    120
  • Joined

  • Last visited

Everything posted by blindowl

  1. Yeah, I have since then changed back to the stock ROM. I don't really have any use for the Rom-Inator extras. And the included 32-bit QuickDraw breaks most old Sierra games. The Mac will crash also with the stock ROM and MODE32 enabled, if no monitor is attached. But with the stock ROM I can easily disable 32-bit mode by holding down the Esc. key at boot. And if I need more than 8 MB of RAM I can always use the resistor workaround to fake an attached monitor. So the Pivot Color card now works fine with my SE/30!
  2. Thick bars in my case. But if you see thick bars or the ones you have is just a matter of the video ROM version (I think?).
  3. Vertical bars and chimes of death. Mine had a lot of visible corrosion around those chips, though.
  4. UI2-4 and UJ2-4, between the RAM sockets and the battery holder. They were to blame when I had similar issues.
  5. I just discovered that I actually can use the card in 32-bit mode (Mac ROM-Inator II) just fine. Only problem is that I need to have an external monitor hooked up all the time... If a monitor is not connected the Mac will crash after power-on. My workaround to boot the Mac without an external monitor is to add resistors to the RGB pins on the video port, to make it believe a monitor is connected. Please let me know if there's a better solution...
  6. Has anyone managed to get a Radius Pivot Color card to work in 32-bit mode? The card works fine in my SE/30 with 65 MB RAM when 32-bit mode is disabled, but as soon as it is turned on, I get a Sad Mac at startup. I recently bought a Mac ROM-Inator II and now I wanted to test if a 32-bit clean ROM would work better, but with the Radius card installed, the computer crashes immediately at startup with a black screen. The ROM version on the Radius card is 2.6, which I think is the final version? Is there a possible way around this problem?
  7. After some trial and error with different setups, my conclusion is that the problem is due to a bad cable. A standard DB25 cable is not good enough. I think I need to get a thicker and better shielded, purpose-built SCSI cable.
  8. If I connect the BlueSCSI with a DB25 extension cable (1.8 m) my SE/30s just stuck on a flashing ? at startup (ignoring the internal disk). But works with the Classic. I thought it could be a power issue so I hooked it up to USB power, but no change. Any idea what the issue can be? Crappy cable? Do I need to do any kind of modification to run the BlueSCSI on USB power?
  9. What kind of problems? What's the best way to wire the devices?
  10. Thank for your answers! I think I will build me a little SCSI box then!
  11. I previously asked this question in the BlueSCSI thread but it's a bit off-topic, so I'm continuing here instead. I have two external SCSI devices that I want to use at the same time, the BlueSCSI and an external Ethernet card. But only one SCSI port to connect them to. @erichelgeson suggested using and old SCSI enclosure, and I've looked around, but they are quite pricy. And big. So I'm trying to understand how the SCSI chain works and see if I can make my own "hub". Are all devices hooked up in parallel? Can I just take a breadboard and wire up two female DB25 to one male DB25? A
  12. If I want to daisy chain the BlueSCSI (connected externally) with another SCSI device, what are my options then? Are there SCSI splitters?
  13. If I format the internal drive with HD SC Setup and the BlueSCSI images with Lido (formatting the BlueSCSI images with the patched HD SC Setup always fails for me) results in my original issue: only the last 3 drives become available after startup. If I format the internal drive with HD SC Setup and the BlueSCSI images with HDT I can use a maximum of 2 images on the BlueSCSI. If I add more images the Mac will boot with a 0000000F 00000019 error. There seem to be something about more than 3 disks causing different issues (only on the Classic and SE, though). But honestly
  14. After updating the driver on the internal disks (Performa 460 and SE/30) with Hard Disk Toolkit 1.7.5, the machines can now boot with the internal disk connected without getting the 0000000F 00000001 error. I've also formatted all the BlueSCSI images with HDT 1.7.5. This combination works fine with both the Performa and the SE/30s. On the Classic and SE FDHD it will cause a "Sad Mac" and 0000000F 00000019 error. So on the Classic and SE I'm instead using Lido 7 for the internal disk. This combination works, but only with System 6.0.7... With 7.0.1 and 7.1 they will eith
  15. Yeah, I noticed your previous issues so I tried with two different cards, but the behaviour was exactly the same with both cards. I think you're on the track here. I just reformatted the internal disk in the Classic and updated its driver with Lido to see if matching drivers would solve the problem. But it just ended with the internal disk now also invisible after reboot... Instead I tried formatting the internal disk with Hard Disk Toolkit and then restarting. Now the disk appeared again. I then did the same with the missing BlueSCSI disks and after rebooting
  16. I've named them HD10_512.hda, HD20_512.hda and so on. Nothing in the log file hints of any error. I just connected the BlueSCSI to my Performa 460 and it won't boot at all when the device is connected. Sad Mac and 0000000F 00000001 error. Actually I got the exact same error yesterday on one of my SE/30 machines. Solution is to disconnect the internal drive and use only the BlueSCSI. It worked fine on the other SE/30 though. These are my results: 6 x Lido formatted, dd created images: Classic - only last three images mounted at startup SE - only las
  17. I put the kit together this weekend and am very happy with it, a great tool! However, I have some problems when trying to use multiple images (ID 1 to 6). When using the pre-made images (https://github.com/erichelgeson/BlueSCSI/blob/main/docs/MacHD.zip), my Classic and SE mount only the image with the highest ID (ID 6). I can mount the rest of the drives with Lido, but they are not available at startup. On my two SE/30 machines, all images are mounted at startup. I've also tried to create new images with dd and format them with Lido 7. Then the Classic and SE mount the
  18. Yeah, could be interesting! I’m planning on building a small MIDI-over-gamesocket board (https://paleotronic.com/2020/07/05/build-a-no-slot-midi-interface-on-the-apple-game-i-o-socket/). An audio interface sounds interesting too.
  19. I've been a Macintosh user since the early '90s but had never actually seen or used an Apple II in real life before. These machines were not particularly common here in Sweden back in the day. So when this Apple II+ including a lot of goodies appeared on an auction site, I could not help but snag it. It was sold in working condition but had been put to storage for 30 years and needed a thorough overhaul. Things that came with the Apple: • BMC Monochrome Monitor • Disk II Drive • Disk II Interface Card • Apple Language Card • Super Serial
  20. I think it's fixed now. One of the transistors on the interface card looked kinda strange. Upon closer inspection, I could see that the component had been replaced at some point. And the PCB had been slightly damaged during the replacement. I removed the transistor, cleaned the card and put it back again. And now the device starts up again. Hopefully it will last longer than overnight this time ...
  21. Yeah, belt is there and it spins if I move it by hand. My first thought when it started working (briefly) was that it came to life after I moved the belt/motor (after being still for 30 years...). I've tried that again but no luck. And the load-from-audio method I described actually causes the disk spin, so the motor/belt seems fine.
×
×
  • Create New...