I will have to customize the Legacy Recovery image with System 7.1
That is now being discussed in this thread.
I will have to customize the Legacy Recovery image with System 7.1
It’s a possibility, I put some cores around, but couldn’t notice any difference.Maybe it’s just because the (too long?) ribbon câble of the SD extender is unshielded and thus picking up all sorts of interferences?
where did you order your SD extender from?
I honestly have no clue, it goes beyond my knowledge, I would need to study the specifications of the SD card standard.I wonder if BlueSCSI and BlueSCSI v2 expect specific voltage ranges in the data stream that the resistor is pushing down too low. Is a lower resistor needed?
Why do BlueSCSI or BlueSCSI v2 crash without the resistor in the SD extender?
Not yet, there is one thing outside my control before I release it in the mainline firmware - soon!is BlueSCSI-Toolbox wrapped into the latest firmware? I can't seem to locate the transfer utility.
I do think most or all of the 1x0 series powerbooks will have that 50 pin internal connector. It's for SCSI target disk mode, so the Mac can dynamically assign the SCSI ID of the internal hard drive for use with an external system. These drives use jumpers there at the back to set the SCSI ID, so the computer can just select the ones that are necessary.Hi everybody!
I just installed my BlueSCSI v2 in my Powebook 100 and it works fantastic!
I just have one question: the powerbook version of the BlueSCSI is 40 pins, but the connector inside my PB 100 is 50 pins. I checked the schematic and the first 40 pins correspond to the pinout of the BlueSCSI, moreover the schematic shows the connector as 40pins while the one in the machine counts to 50. Of the remaining 10, three are connected to something and seven unconnected. Is this a particularity of the PB 100 or is this a standard configuration?
Thanks!
This is an interesting tidbit to learn -- I always assumed that the motherboard did some advanced ROM-level trickery to present a different SCSI ID to the host Mac than what the internal drive is set to. It's maybe even more clever that the motherboard simply changes the actual ID of the drive itself!It's for SCSI target disk mode, so the Mac can dynamically assign the SCSI ID of the internal hard drive for use with an external system. These drives use jumpers there at the back to set the SCSI ID, so the computer can just select the ones that are necessary.
**Full Changelog**: https://github.com/BlueSCSI/BlueSCSI-v2/compare/v2023.04.10...v2023.07.03
**Discussion**: https://github.com/BlueSCSI/BlueSCSI-v2/discussions/48
**How to Update**: https://github.com/BlueSCSI/BlueSCSI-v2/wiki/Updating-Firmware
# Highlights
## New!
* Hardware: 2023_03a version of Centronics 50 Pin #24 - @androda
* Support for Atari ST ICD extensions #36 - @mynameistroy
* Validate Macintosh Disks #43 - @erichelgeson
* .bin/.cue support - @PetteriAimonen @saybur [CUEParser](https://github.com/BlueSCSI/BlueSCSI-v2/tree/main/lib/CUEParser)
* Various CD and Image Set fixes - @saybur @PetteriAimonen (see full changelog)
* Various CD SCSI commands and fixes - @saybur @PetteriAimonen (see full changelog)
* Monitor board supply voltage and warn if voltage drops too low. @PetteriAimonen https://github.com/BlueSCSI/BlueSCSI-v2/commit/6dd37e3f42a09aee0778ecb39ed306d422af8d22
* Log voltage when booting for troubleshooting - @erichelgeson https://github.com/BlueSCSI/BlueSCSI-v2/commit/ba4b5012ab53d15401dc7bdbc53fc4e436f7b8b9
* Improved OMTI support @Kars-de-Jong https://github.com/BlueSCSI/BlueSCSI-v2/commit/d7ccb9048036036c627a8c0972ffee7ee154e4df
* Add X68000 preset @erichelgeson https://github.com/BlueSCSI/BlueSCSI-v2/commit/be6d1adbbd64fb7de436efdb82d0d95c823124e8
* Add rudimentary support for tapes - @Kars-de-Jong https://github.com/BlueSCSI/BlueSCSI-v2/commit/cc3587d96af4e73f0f55a8c30d6d716e80e30f02
* More tape command implementations: Erase, Seek, ReadPosition, Write, ReadBlockLimits, WriteFilemarks (dummy result), Verify (dummy result) - @PetteriAimonen https://github.com/BlueSCSI/BlueSCSI-v2/commit/a75508c93da2d0ca1290a83be1580aec5bfefeb3, https://github.com/BlueSCSI/BlueSCSI-v2/commit/ea15cd2f25ad9021d4d4404948e4bb090deb12d4
## Fixes!
* Parity is properly ignored when Parity=0 #30 @mynameistroy
* Fix crash when using ID7 @erichelgeson https://github.com/BlueSCSI/BlueSCSI-v2/pull/43/commits/c26d4841df43d6040afc07ff6a81024a2194573a
* Set Inquiry standard version based on EnableSCSI2 setting @PetteriAimonen https://github.com/BlueSCSI/BlueSCSI-v2/commit/6b13c942f17393b71e6308479677768b6499e82a
* Fix crash when switching between FAT and exFAT formatted cards. @PetteriAimonen https://github.com/BlueSCSI/BlueSCSI-v2/commit/65a4566e0dcdff51ce4814fa5f007d08b2e5a0c8
* Add support for 2GB SD cards @PetteriAimonen https://github.com/BlueSCSI/BlueSCSI-v2/commit/66c1e47d298c273faec8458317ec60f7f0bb889c
* Fixes hard coded block sizes in multiple locations. #47 - @erichelgeson
## Chore!
* Update to [email protected] platform https://github.com/BlueSCSI/BlueSCSI-v2/pull/43/commits/ccb2295a13ec9d82def564160c408112cfb8b855 @erichelgeson
## New or changed config params
* `Parity` is now `EnableParity`
* `BlockSize` - allow block size to be overridden at the ini level
* `DisableConfigHook` - skip any defined Configuration Hooks
I must say that size reduction is impressive. Your new v2 DB24 seems to be roughly the same size as the v1.1 DB25, as per my observation of Kay Koba's photo here...Many thanks to @JDW (and others) for pushing us a bit harder on the design