Hiya,
I am new to this forum - thanks for having me! This is very much appreciated!
I own a NeXTcube Turbo since 1992 (when I started my studies in electronics), but didn't use it for the last 20 years.
Now I want to bring it back to life, but I have issues with my internal hard drives. One is soaked in oil - I will try to clean it and hope that I can get it up and running again. And the other one starts up, but gets stuck and I see the indication "Waiting for drive to get ready .....".
So I went ahead and bought a BlueSCSI (version desktop), but no matter which images I install, the NeXTcube does not recognise them.
What I do is that I setup the images in Previous (on my M1 MacBook Pro), and copy them over with a bluescsi.ini to an SD card.
Then I power on the NeXTcube, and press left Command, right Command and the top left key of the numeric block in order to stop the booting process.
Then I type in "bsd(1,0,0)" and press Return. But then nothing happens. When I power off the NeXTcube, and check the log file (log.txt), there is nothing that indicates that something is wrong.
Here the output of the log.txt:
Platform: BlueSCSI
FW Version: 2024.05.21-rel May 21 2024 21:21:44
I2C Supported
Flash chip size: 2048 kB
=== SD Card Info ===
SD card detected, FAT32 volume size: 14902 MB
SD Name: ASTC, MID: 0x74, OID: 0x4A 0x60
[159ms]
[159ms] === Global Config ===
[159ms] Reading configuration from bluescsi.ini
[159ms] Active configuration (using system preset "Generic"):
[160ms] -- Debug is enabled
[160ms] DBG -- Parity is enabled
[160ms] DBG -- ReinsertCDOnInquiry is disabled
[172ms]
[172ms] === Finding images in / ===
[173ms] == Opening /HD10.hda for ID: 1 LUN: 0
[343ms] ---- WARNING: file /HD10.hda is fragmented, see
https://github.com/BlueSCSI/BlueSCSI-v2/wiki/Image-File-Fragmentation[343ms] DBG ---- Read prefetch enabled: 8192 bytes
[343ms] DBG Skipping platformConfigHook due to DisableConfigHook
[343ms] ---- Image ready
[343ms]
[344ms] === ROM Drive ===
[344ms] Platform supports ROM drive up to 1692 kB
[344ms] ---- ROM drive image not detected
[344ms]
[344ms] === Configured SCSI Devices ===
[344ms] * ID: 1, BlockSize: 512, Type: Fixed, Quirks: None, Size: 2048048kB
[445ms]
[445ms] Initialization complete!
[477ms] INFO: Pico Voltage: 3.171V.
As you can see, it recognises the file "HD10.hda", but stops after the initialisation.
Any idea what I am doing wrong?
Thanks in advance for your help,
Kokomuck
Quote from: kokomuck on September 15, 2024, 12:43:57 PMHiya,
Thanks for the reply.
Here my bluescsi.ini file:
[SCSI]
Debug=1
System=Generic
EnableSCSI2=1
DisableConfigHook=1
DisableROMDrive=1
[SCSI1]
SectorsPerTrack=139
HeadsPerCylinder=4
So, those parameters were configured, but were not shown in the log file - sorry, should have mentioned that.
Any further ideas?
Thanks in advance,
Kokomuck
The latest firmware for the BlueSCSIv2 provides a separate profile for NeXT systems:
https://github.com/BlueSCSI/BlueSCSI-v2/releases/tag/v2024.10.26If you haven't already done so I would update the Firmware of the BlueSCSIv2 nad then set the profile in the bluescsi.ini by setting "System=NeXT" and then try again if the NeXT is able to detect the BlueSCSI and the HD image.
Quote from: don_apple on November 10, 2024, 12:46:36 PMThe latest firmware for the BlueSCSIv2 provides a separate profile for NeXT systems
Thanks a million for your suggestion. I got it working before this update, but I am still figuring out why things are working now. Once I am sure, I will post a summary.
In the meantime, I updated the firmware in order to use the "System=NeXT" feature, and it's working fine, as well. The new firmware makes the ini file a breeze to configure.
Thanks again,
Kokomuck