SCSI2SD reverting to default device config

[jessenator]

Every time I run the SCSI2SD utility, write the appropriate settings for a 68k mac (or any settings for that matter), and re-open the utility to double check, my settings are reverted to default.  

I've tried this on both Win7x64 and OS X 10.7 with the utility from CodeSRC. It recognizes the device, it writes the settings, and then after re-opening, I've got bupkis.. all the device configs are reset to defaults. (in reality I'm only writing one device)

Any thoughts or things to try to keep this from happening? 

Thanks

 

[Cory5412]

You might need to issue the command to read the configuration from the device - on the SCSI2SD v6, the utility always shows the defaults until you read in your device's config.

 

[jessenator]

Oh man... I feel so stupid. That worked :/  I have a v5.1, but yes, that was it. 

Thanks, Cory!

 

[jessenator]

I guess while I've got this thread going, is connecting to something like a SCSI enclosure with the fatty C50, to my machine going to cause too much resistance?
It's an old APS scsi drive, powered off, but just scav'ing the SCSI ribbon to the back of my IIsi.

 

[Cory5412]

I would say to give it a go, I actually have a similar enclosure I want to use exactly in this manner, but at worst, you can see about getting one of those power adapter pigtails and powering the enclosure.

 

[jessenator]

Got it working! And successfully patched System 7.5.3 and running MacBench just for fun

The only thing that's irks me a bit is termination: if it's on, I can't use external devices, if it's off I can't use it without a terminated device plugged in. Is there a dynamic termination for v5.1? Or is this another rookie mistake...

 

[NJRoadfan]

Real internal SCSI devices terminated in that manner. If you are using an external case without a termination switch, you were expected to plug a terminator into the open daisy chain SCSI connector in the back. There were some devices that attempted to detect that they were at the end of the chain and auto enable termination, but it was unreliable and caused headaches.

 

[jessenator]

Real internal SCSI devices terminated in that manner

My external is an old APS SCSI enclosure that I've been using with my Plus as a sort of catch-all storage (when I had a working bridge machine). It has the terminator plugged in like it should. It's only been when I switched to the SCSI2SD did I have problems with that external.

I'll have a look and see because the HDD that's bolted into the enclosure is definitely not the original, as the SCSI ID ribbon's pin connectors are not very secure. And maybe that's my problem. The actual SCSI ribbon is fine, but the activity LED always falls right off, so maybe the ID ribbon is the culprit.

 

[Cory5412]

Is it a very old APS enclosure or is it one of the SR2000 or one of their other more modern enclosures? At some point APS added, if I'm remembering correctly, built-in termination as a quality of life addition. You might need to disable that or disable the SCSI2SD's termination and rely on the case's termination, if it's one of the later ones that has it.

 

[jessenator]

Is it a very old APS enclosure or is it one of the SR2000 or one of their other more modern enclosures?

Sorry, this is the only photo I have of it at the moment:

Based on a google search, only seeing other enclosures that look more modern, I'm guessing this one is old as dino b@lls. I've probably looked before, but can't recall a date on the enclosure itself.

That's what I have been doing, when the SCS2SD's termination is off, using the enclosure's terminator. But my issues have been when the drive itself is switched on: I get a missing startup disk icon, as if there's a SCSI ID conflict or something. Which makes me think the not-so-tight pin connector is to blame. Boots right up on my Plus, though. 

When the SCSI2SD termination is on, like it should (?) do, I can't see the external at all. But again, I haven't checked this configuration since I opened the enclosure and fixed the connectors.