Jump to content

Scott Squires

68kMLA Supporter
  • Content Count

  • Joined

  • Last visited

Everything posted by Scott Squires

  1. You're just here to show off your 128k/512k running System 7.5+.
  2. Since 68k is supported in LLVM now, I wonder if it might make more sense to make a similar project as Retro68 but which uses LLVM. Or maybe add LLVM support to Retro68?
  3. Try some different sd cards. Not all sd cards support the interface used by bluescsi. If they all fail, check the soldering on the sd card slot.
  4. The board was not "announced" on Hackaday. They write about whatever they feel like and don't consult the creator about it. 99% of things blogged about on Hackaday are not for sale. There's really no good solution to having a place on the forum to look for the current status of anything. Because posts can't be edited, we can't direct people to a thread to check for the status. They would have to read the entire thread to know the status. Or at least start at the end and read backwards until they figured out enough context. But we know only a tiny percentage of people will do that.
  5. Truly genius. I had no idea that customized gate arrays were a product in that way, with a databook and everything. It makes absolute sense after the fact. But before powermax pointed it out I never would have guessed that was an "off the shelf" product line.
  6. The SIMMCHECK products tend to have special power supply requirements. They need lower voltage at specific current draw otherwise they can overheat. When using the 40-bit port, the SIMMCHECK power must be disconnected and only the 40-bit port power used, which is a different power spec than the main unit. Not sure of the power requirements for that configuration, because my unit is the SIMMCHECK II PLUS with built-in 30-pin, 72-pin, and 168-pin testers.
  7. I suspect it's just more a situation of what machines Kai had. And that he had a FDHD/SuperDrive, not an original SE. Those Vartas on the original SE just don't explode. (At least not yet.)
  8. Nice contribution, @superjer2000! People can use Nuvolink where it works, Daynaport where it doesn't. In time, hopefully the issues with the Nuvolink version can be figured out.
  9. The dd command does not do anything with "drive" images or "partition" images. It just moves bytes around. Which bytes, and what you use them for, is entirely up to you.
  10. Oh, yeah. One thing to keep in mind is that not all MicroSD cards support SPI.
  11. I think the stream started an hour before you posted? This forum isn't very clear about timestamps...
  12. Blue pills usually come programmed with a "blinky" app that does nothing more than blink the LED. So I wonder if this board has not been programmed with BlueSCSI firmware. A USB serial adapter only costs $10 and is a useful thing to have around.
  13. From a customer service perspective it seems a lot more sensible for the device to be configurable than to require every customer using it in a Plus to perform a component level modification to their machine. Especially considering that accommodating the Plus in the BlueSCSI design is basically free.
  14. (Even though it was working before the battery bomb doesn't mean that the PSU hasn't crapped out in the intervening time.)
  15. I'd like to re-emphasize testing the power supply voltages before you go replacing everything in sight on the logic board. An out of spec power supply will mean you'll never get troubleshooting feedback and you'll spend endless days tweaking the logic board to no effect.
  16. I agree that the toolbox is cumbersome. I don't think bypassing it is the answer. Personally, I would not be interested in using a UI library that didn't create native widgets. I wouldn't even be interested in using software written with such a library. (Maybe with the exception of games which sometimes make sense to do something completely different.) I just don't see any point to making software that ignores the platform UI on a platform that is defined by its UX. But you do whatever you like to do.
  17. Not sure if this is useful to you as I don't know off the top of my head for CUDA, but on the SE and other machines of that era, ADB is polled approximately every 11 ms. So not quite your 100 Hz. If it didn't change for CUDA then that could explain it.
  18. Here's a nickel, kid. Get yourself a better computer. =P https://dilbert.com/strip/1995-06-24
  19. And you're done! What's the best way to make a code block on this forum? ...
  20. It's a plain text file. The easiest possible thing to do. LOL
  21. Amazing! Of course, "disassembly" is the other hard part! I love that the SE is getting all this attention.
  22. Kai this is super awesome. Is he going to do the SWIM too? (The one John McMaster did was a different version.) Some day I want to implement an SE SWIM in FPGA so that people can upgrade their 800K SE to SE SuperDrive.
  23. The only thing I can think of is that your working directory may be different than the location of the config file. I don't use MacOS X, so don't know if it has any behaviors that might affect this. If your working directory is the same and it still doesn't work, you could try editing the config.go source file and set configFilename (near the top) to your config file's fully qualified path name. I would try to avoid that though, because it makes updating to newer versions more involved.
  24. The server code and wireshark plugin are now on GitHub. The license is AGPLv3. https://github.com/astrospark/bolorama
  25. Would you mind posting the MD5 hash of your CD image? Then we can know if they are the same or not.
  • Create New...