Forum etiquette

Our mission ...

This forum is part of our mission to promote the preservation of vintage computers through education and outreach. (In real life we also run events and have a museum.) We encourage you to join us, participate, share your knowledge, and enjoy.

This forum has been around in this format for over 15 years. These rules and guidelines help us maintain a healthy and active community, and we moderate the forum to keep things on track. Please familiarize yourself with these rules and guidelines.

Remain civil and respectful

There are several hundred people who actively participate here. People come from all different backgrounds and will have different ways of seeing things. You will not agree with everything you read here. Back-and-forth discussions are fine but do not cross the line into rude or disrespectful behavior.

Conduct yourself as you would at any other place where people come together in person to discuss their hobby. If you wouldn't say something to somebody in person, then you probably should not be writing it here.

This should be obvious but, just in case: profanity, threats, slurs against any group (sexual, racial, gender, etc.) will not be tolerated.

Stay close to the original topic being discussed
  • If you are starting a new thread choose a reasonable sub-forum to start your thread. (If you choose incorrectly don't worry, we can fix that.)
  • If you are responding to a thread, stay on topic - the original poster was trying to achieve something. You can always start a new thread instead of potentially "hijacking" an existing thread.

Contribute something meaningful

To put things in engineering terms, we value a high signal to noise ratio. Coming here should not be a waste of time.
  • This is not a chat room. If you are taking less than 30 seconds to make a post then you are probably doing something wrong. A post should be on topic, clear, and contribute something meaningful to the discussion. If people read your posts and feel that their time as been wasted, they will stop reading your posts. Worse yet, they will stop visiting and we'll lose their experience and contributions.
  • Do not bump threads.
  • Do not "necro-post" unless you are following up to a specific person on a specific thread. And even then, that person may have moved on. Just start a new thread for your related topic.
  • Use the Private Message system for posts that are targeted at a specific person.

"PM Sent!" messages (or, how to use the Private Message system)

This forum has a private message feature that we want people to use for messages that are not of general interest to other members.

In short, if you are going to reply to a thread and that reply is targeted to a specific individual and not of interest to anybody else (either now or in the future) then send a private message instead.

Here are some obvious examples of when you should not reply to a thread and use the PM system instead:
  • "PM Sent!": Do not tell the rest of us that you sent a PM ... the forum software will tell the other person that they have a PM waiting.
  • "How much is shipping to ....": This is a very specific and directed question that is not of interest to anybody else.

Why do we have this policy? Sending a "PM Sent!" type message basically wastes everybody else's time by making them having to scroll past a post in a thread that looks to be updated, when the update is not meaningful. And the person you are sending the PM to will be notified by the forum software that they have a message waiting for them. Look up at the top near the right edge where it says 'Notifications' ... if you have a PM waiting, it will tell you there.

Copyright and other legal issues

We are here to discuss vintage computing, so discussing software, books, and other intellectual property that is on-topic is fine. We don't want people using these forums to discuss or enable copyright violations or other things that are against the law; whether you agree with the law or not is irrelevant. Do not use our resources for something that is legally or morally questionable.

Our discussions here generally fall under "fair use." Telling people how to pirate a software title is an example of something that is not allowable here.

Reporting problematic posts

If you see spam, a wildly off-topic post, or something abusive or illegal please report the thread by clicking on the "Report Post" icon. (It looks like an exclamation point in a triangle and it is available under every post.) This send a notification to all of the moderators, so somebody will see it and deal with it.

If you are unsure you may consider sending a private message to a moderator instead.

New user moderation

New users are directly moderated so that we can weed spammers out early. This means that for your first 10 posts you will have some delay before they are seen. We understand this can be disruptive to the flow of conversation and we try to keep up with our new user moderation duties to avoid undue inconvenience. Please do not make duplicate posts, extra posts to bump your post count, or ask the moderators to expedite this process; 10 moderated posts will go by quickly.

New users also have a smaller personal message inbox limit and are rate limited when sending PMs to other users.

Other suggestions
  • Use Google, books, or other definitive sources. There is a lot of information out there.
  • Don't make people guess at what you are trying to say; we are not mind readers. Be clear and concise.
  • Spelling and grammar are not rated, but they do make a post easier to read.
See more
See less

A few BlueSCSI PCBs available

  • Filter
  • Time
  • Show
Clear All
new posts

    A few BlueSCSI PCBs available

    I ordered a few BlueSCSI PCBs from gerbers, looks like I will have 3 extra. If anyone is interested I can send one to you for postage. Located in California, US.

    For those (like me ) who might not know what a BlueSCSI is:


      I have 1 extra still if anyone is interested. I put one of them together, haven't gotten it working yet. Strangely when powered on not connected to the Mac, it detects my sd card and the image files on it, which is confirmed by the log file written to the card. But when I power on connected to the Mac, it blinks its led indicating that the sd card is not detected. Strangely one time I started up, it did seem to detect it - and I got an odd sequence of happy Mac icon for about 1 second and then immediately jumping back to a blank screen, over and over. I'm suspecting that I may have gotten one of the fake bluepill boards the project page warns you about.


        Originally posted by bitfixer View Post
        I'm suspecting that I may have gotten one of the fake bluepill boards the project page warns you about.
        Ugh, ugly. Does yours have any traits of fakes described for example here?


          FWIW, I have had good success with keirf's test program ("blinky") described here
          for sorting out fakes and clones.


            Thanks. I tried the Blinky test, and this one does seem to pass. At least, it gets through all the checks and enters the endless RAM checking loop. The only thing that looked mildly curious was that there was I think a version byte, and one other status indicator after it that were zero. I don't know if that is a normal value or not.
            So, I'm not really sure one way or another about the specific bluepill board I have. It's also completely possible the problem is due to my own build issues. However, I'm confused by the fact that it can successfully write to the SD card, but only when not plugged into SCSI in the Mac.


              What kind of Mac is this? And are you powering the BlueSCSI board from the SCSI connector on the Mac or externally (via the Berg / "floppy power" connector? I've read up on BlueSCSI versus Macs this evening, and it seems that a few Mac models doesn't automatically provide power (or enough power for the BlueSCSI) via the SCSI connector.


                Mac SE/30. I tried it both with and without powering with 5v from the Berg connector, same result. When it powers on connected to the Mac in either case, the LED on the bluepill blinks I think 5 times, then pause, blinks again. Which is the same thing that happens if you power up without a microSD. If I power it from another source, it sees the sd and writes a log file to it.


                  Aha, my future "victim" for a BlueSCSI is also a SE/30
                  If the LED blinks (and you are sure the BluePill is programmed) then it doesn't see the correct file names on the microSD card, I think. Not sure it helps, you have probably already verified that.


                    It does recognize the image files correctly in the case that I power up not connected to the Mac. It writes a log file on the sd card with some information, showing the image files found and indicating that it was ready to enter its main loop.
                    I will try this again, this time wiring the correct pins on the bluepill straight to a breakout board I have for a microsd, to see if it's some sort of flaky connection. Although I don't really think so.
                    Another possibility is my method of programming the bluepill. The instructions indicate use of the STLinkV2 for programming, which I did not have. Instead I used a raspberry pi and the stm32flash utility, as described in this blog post:

                    This does seem to work just fine, and the fact that it does write files to the sd card indicate that it seems to have worked. But maybe there's some fuse setting that is not programmed this way, I don't know. I might just get the STLink device and try that out to compare. They are pretty cheap.


                      stm32flash should be fine - it will tell you if the programming failed. As long as there is only one binary to flash, there isn't much that could go wrong. And - you are getting the log file written to the SD card, this proves that the program on the BluePill is working. The fuses are mostly for setting crystal frequencies and such, so if something was seriously wrong you wouldn't even get that far.
                      And if you used that setup for programming the blinky test, that is another vote for your programming setup being good.

                      Do you have any other machines with a SCSI card in that you could try the BlueSCSI in? Like a machine with an Adaptec SCSI card and Linux / FreeBSD on it or something.


                        Good idea, I may have a Pc scsi card around somewhere, will have to look around for it. In the meantime, I did also try it in a known working Mac SE with the same result. Still confused by this one.