BlueSCSI on Macintosh Portable

JDW

Administrator
Staff member
Founder
Sep 2, 2021
2,785
2,176
113
55
Japan
youtube.com
Have these issues with the BlueSCSI and the Portable ever been fixed?

It’s a complex question to answer because this thread is 11 pages long. But I have done the work for everyone by summarizing this thread page by page.

THREAD SUMMARY TO DATE​

Page 1:​

@Sideburn started this thread with a question about how to eliminate a wake from sleep DELAY with his BlueSCSI and 5120 Portable (with Hybrid).

Page 2:​

Sideburn mentions 3 things:
  1. His BlueSCSI is set to HD0, which is what it should be for the Mac Portable.

  2. It was mentioned by @alxlab that you should: Never use a version of Apple HD SC Setup newer than 7.3.1 (which comes with System 7.0.1) or your Portable will crash while waking from sleep mode. But it’s not clear if Sideburn ever checked that driver version on his BlueSCSI.

  3. Sideburn found that constantly powering his BlueSCSI eliminated the Wake from Sleep DELAY.

Page 3:​

Talks about ways to source power for the BlueSCSI, and also mentions a new problem: after wake from sleep, the machine is slower until you Restart. @Androda chimed in to add that the problems cited should not be related to the Hybrid board.

Page 4:​

Talks about Lead Acid batteries and the discovery that having more than 4MB on an add-on RAM card triggers a severe performance slowdown.

Page 5:​

Presents deep analysis of the problem, concluding by saying there is nothing wrong with the RAM card itself — it’s the AMOUNT of RAM triggering the slowdown.

Page 6:​

Reiterates the problem by saying the slowdown is worse after wake from sleep (with more than 4MB on a RAM card).

Page 7:​

@SuperSVGA mentions a problem area that @Androda confirmed, but the thread ended there in July 2023 until I chimed in months later in Feb. 2024, asking about the Pico W (wireless) on my BlurSCSI v2 on my 5126 backlit Portable. Androda replied saying: “BlueSCSI Desktop PCB designs since 2023.09a have the correct pull resistors set and should not cause issues with waking from sleep.” But my BSv2 was older than that and lacked those resistors.

Page 8:​

Shows how to add the needed 2 resistors on older edition BlueSCSI v2 boards like mine. I also tested and confirmed the performance slowdown (26%!) exists due to having more than 4MB on a RAM card (in my case, from MacEffects). SuperSVGA then chimed in with the exact technical reason for the slowdown caused by having too much RAM. I then post a new discovery that the Portable freezes on Wake from Sleep due to WIFI access.

Page 9:​

A back-and-forth talk about what the problem could be.

Page 10:​

I confirmed earlier findings about keeping the BlueSCSI constantly powered, in that constantly powering the BlueSCSI resolves the Wake from sleep issue I discovered, triggered by WIFI use. I then asked if the Apple HD Setup “driver version” issue had been investigated, and the answer was No. The Portable supposedly needs driver version 7.3.1 or older, not 7.3.5 like most of us BlueSCSI owners tend to use. That’s an unanswered question to this very day. Anyway, Page 10 also talks about where to tap power to keep the BlueSCSI constantly powered, but I ultimately decided not to do that on my Portable because I think it presents the danger of an electrical short. My solution? Not great. After using my Portable and WIFI, I must shutdown instead of putting the machine to Sleep.

Page 11:​

Where we are now.


NEW INFO: someone is working on a new RAM Card that potentially could eliminate the performance slowdown while allowing you to use more than 4MB of RAM on a RAM card. I won't say anything more about who it is or what is happening, because the person working on it may decide not to release the product or have issues. But I do know something is being worked on, which is great because there aren't any RAM cards (newly developed) being sold right now, from what I understand.
 

eric

Administrator
Staff member
Sep 2, 2021
1,254
2,191
113
MN
bluescsi.com
Ordering it by page is confusing IMO, so just a summary:
  • BlueSCSI wake from sleep: Fixed since 2023.09a+ or a bodge for older ones.
  • BlueSCSI WiFi after sleep: No one has provided any logs of what the BlueSCSI is doing when this happens, or if the issue happens on a real daynaport device.
  • Slow down: unrelated to BlueSCSI - RAM card issue.
  • Driver version: someone with a portable should just test - should take 10 minutes.
 
  • Like
Reactions: dramirez and bakkus

David Cook

Active Tinkerer
Jul 20, 2023
248
322
63
Any access at all is sufficient, such as a simple tst.w $FC0200 instruction or running DM FC0200 from the debugger.

Really? I could just throw the tst instruction into the Quiet Portable init if that's all it is.

So, does that completely eliminate the slowdown when using 7MB of memory, or just the additional penalty after waking from sleep?
 
  • Like
Reactions: JDW

SuperSVGA

Tinkerer
Mar 26, 2022
78
48
18
So, does that completely eliminate the slowdown when using 7MB of memory, or just the additional penalty after waking from sleep?
This is only for the sleep issue affecting that space of RAM above 5MB if that register is not accessed after a reset. There may also be additional registers that affect access times as well.

The backlit Portable has faster RAM access times on the first 5MB of memory, and the rest uses the slower access times of the standard Portable. So on the backlit Portable memory above that space will appear slower in comparison.
 
  • Like
Reactions: JDW

joopmac

New Tinkerer
Jun 18, 2024
6
1
3
Reading about the "quiet portable init", is it available? It's to counter the slight noise?
 

Froggy814

New Tinkerer
May 6, 2026
49
13
8
Squaw Valley, CA
@joopmac
Can someone un-HQX that for me! I don't really now how to? But I really want it!
 

JDW

Administrator
Staff member
Founder
Sep 2, 2021
2,785
2,176
113
55
Japan
youtube.com
Can someone un-HQX that for me! I don't really now how to? But I really want it!
Remove the HQX encoding but keep it as a SIT file?

i suppose that would work and the file wouldn't get mangled when transfered across the internet, but if you cannot even decompress a SIT file (which may be true if you cannot remove HQX encoding), then that would be a problem because the file must be protected for transfer across the internet.

My advice is to install Stuffit Deluxe 16, which I uploaded to Macintosh Garden below, with my own serial number and all, for the express purpose of helping folks like yourself. It even works on my M1 Max 16" MBP running macOS Sonoma, but also works on old Intel Macs running Sierra, and possibly even El Capitan.


With Stuffit installed, you can remove encoding but leave the SIT, or remove encoding and decompress. You can even use the LEGACY function to create a legacy SIT that will decompress on many vintage Macs, although it isn't SIT v1.5. If you need SIT v1.5 for unstuffing on a System 6 machine, then just use Stuffit Deluxe 16 to create a Legacy SIT, then drop that SIT onto the following website so it gets repackaged as v1.5, and then pretty much anyone with any Mac and Stuffit Expander can decompress it.

 
  • Like
Reactions: Froggy814

David Cook

Active Tinkerer
Jul 20, 2023
248
322
63
Can someone un-HQX that for me!

The Macintosh OS was novel in that it allowed files to consist of two "channels". The first channel is called the "data fork" and is just like every other operating system. The second channel is the "resource fork" and stores icons and alert boxes and other cool Mac-like pieces.

Unfortunately, this technology did not become the norm. So, if you copy a classic Macintosh file to a modern PC, the second channel (the resource fork) is lost because it doesn't understand multi-channel files. This will corrupt applications and some documents.

HQX was invented a long time ago to combine everything about the file (including the "Get File Info" stuff) into the data fork only. You can then store and transmit the file safely on any computer. For example, you can even post the file to this forum. When the file eventually reaches a classic Macintosh, use StuffIt, BinHex, or Tiny Transfer to convert the file back into classic Macintosh format.

- David