68020 SBC on VME Can't use the .ini file

[veachanderthal]

First post and first attempt ZuluSCSI device so be gentle with me.

I have a Motorola MVME 133XT 68020 SBC that I'm trying to run with a compact ZuluSCSI card. The system recognizes the SD card as a drive without SCSI errors, but throws a "bus error" if I try to access it. (Launch application or even a DOS command to see a DIR)

System boots fine on original Fujitsu Drive.
I'm guessing I may need something other than system defaults for configuration, but I can't seem to get the ZuluSCSi device to recognize the zuluscsi.ini file I downloaded. I have it on the SD Card named "zuluscsi.ini", but I get a "zuluscsi.ini not found" message in the terminal along with a blurb about using defaults.

I feel like I'm missing something simple. Like maybe I'm not using or naming the file properly.

 

[Phipli]

First post and first attempt ZuluSCSI device so be gentle with me.

I have a Motorola MVME 133XT 68020 SBC that I'm trying to run with a compact ZuluSCSI card. The system recognizes the SD card as a drive without SCSI errors, but throws a "bus error" if I try to access it. (Launch application or even a DOS command to see a DIR)

System boots fine on original Fujitsu Drive.
I'm guessing I may need something other than system defaults for configuration, but I can't seem to get the ZuluSCSi device to recognize the zuluscsi.ini file I downloaded. I have it on the SD Card named "zuluscsi.ini", but I get a "zuluscsi.ini not found" message in the terminal along with a blurb about using defaults.

I feel like I'm missing something simple. Like maybe I'm not using or naming the file properly.

Have you checked the log file in the ZuluSCSI?

 

[Phipli]

Also welcome to the forum, but just to warn you, this is mostly a Mac specific forum so we may struggle with the specifics of your machine / not be familiar, especially wrt what firmware/ software it is running.

 

[veachanderthal]

Have you checked the log file in the ZuluSCSI?

I have, but nothing has popped out at me.

Anything in particular you are thinking/looking for?

A friend figured out why the scsizulu.ini file wouldn't load. I didn't have file extensions turned on so windows 10 was naming the file zuluscsi.ini.ini

Rookie mistake. I'm going through the different parameters in the .ini file now experimenting with different things. I get an immediate bus error with quirk settings other that 2 (2=OMTI)

I have an OMTI board in the system but I believe it is only used to convert MFM data to SCSI for the old floppy drive.

In any case, with quirks set at 2, I get a "hard drive initialization error" and the systems defaults to the floppy. Not sure what that tells me.

either the setting is good and there are other settings that are wrong or setting it to 2 is bad so I don't reach other settings.

 

[Phipli]

I'll just tag the creator @rabbitholecomputing

But you might want to post the log file so people can look and see what is happening.

 

[veachanderthal]

I have, but nothing has popped out at me.

Anything in particular you are thinking/looking for?

A friend figured out why the scsizulu.ini file wouldn't load. I didn't have file extensions turned on so windows 10 was naming the file zuluscsi.ini.ini

Rookie mistake. I'm going through the different parameters in the .ini file now experimenting with different things. I get an immediate bus error with quirk settings other that 2 (2=OMTI)

I have an OMTI board in the system but I believe it is only used to convert MFM data to SCSI for the old floppy drive.

In any case, with quirks set at 2, I get a "hard drive initialization error" and the systems defaults to the floppy. Not sure what that tells me.

either the setting is good and there are other settings that are wrong or setting it to 2 is bad so I don't reach other settings.

Thanks for the response and the welcome.

I haven't pulled the CPU out of the system to check the firmware labels, but the initialization screen that comes up on powerup says .43 version proms.

The software its running is a forth based application written by a French nuclear medicine company in the 90s.

 

[veachanderthal]

I'll just tag the creator @rabbitholecomputing

But you might want to post the log file so people can look and see what is happening.

 

[veachanderthal]

This on is typical. I don't know what to make of the DMA info at the bottom.

 

[Phipli]

This on is typical. I don't know what to make of the DMA info at the bottom.

Try turning off SCSI2. I doubt a 68020 based SBC has SCSI2

 

[veachanderthal]

Try turning off SCSI2. I doubt a 68020 based SBC has SCSI2

That's a good idea. I'll try that next. The drive I cloned that does boot the system is a SCSI2 drive, but there may be downward compatibility so that is would work with a SCSI1 device, but that's not the same thing as telling the Zuluscsi to emulate a scsi2 drive

 

[Phipli]

The software its running is a forth based application written by a French nuclear medicine company in the 90s.

Can I just check this isn't a high SIL application?

 

[GRudolf94]

The MVME133XT does not have a SCSI controller. I'm not sure this thread is in the right place, or even in the right forum, but to be any help we'd need to know what other cards are installed in the card cage. Your OMTI card is probably both SCSI and floppy controller, and any further interesting info is probably found in the docs for that, not the SBC's... If it has been archived, that is.

 

[veachanderthal]

Can I just check this isn't a high SIL application?

I really don't know.

 

[Phipli]

I really don't know.

Is it still doing its original job?

Is it bad if it stops working while in use?

 

[veachanderthal]

The MVME133XT does not have a SCSI controller. I'm not sure this thread is in the right place, or even in the right forum, but to be any help we'd need to know what other cards are installed in the card cage. Your OMTI card is probably both SCSI and floppy controller, and any further interesting info is probably found in the docs for that, not the SBC's... If it has been archived, that is.

That's true!

There is a SCSI peripheral board (Controller) in the rack and an OMTI 5200E Board. The OMTI, per my understanding is just to convert the floppy from MFM for the scsi controller. I believe the hard drive data goes directly to the controller even thought the cable is connected to the OMTI.

I don't have a lot of data on the SCSI peripheral Board. It was made by the French Nuclear Medicine company Sophy and has their labeling. I will look it up and see if I can find any data on it.

 

[rabbitholecomputing]

That's true!

There is a SCSI peripheral board (Controller) in the rack and an OMTI 5200E Board. The OMTI, per my understanding is just to convert the floppy from MFM for the scsi controller. I believe the hard drive data goes directly to the controller even thought the cable is connected to the OMTI.

I don't have a lot of data on the SCSI peripheral Board. It was made by the French Nuclear Medicine company Sophy and has their labeling. I will look it up and see if I can find any data on it.

Photos of the SCSI board would certainly be helpful. Preferably well-lit and with legible part numbers

 

[GRudolf94]

That's true!

There is a SCSI peripheral board (Controller) in the rack and an OMTI 5200E Board. The OMTI, per my understanding is just to convert the floppy from MFM for the scsi controller. I believe the hard drive data goes directly to the controller even thought the cable is connected to the OMTI.

I don't have a lot of data on the SCSI peripheral Board. It was made by the French Nuclear Medicine company Sophy and has their labeling. I will look it up and see if I can find any data on it.

The OMTI 5200 is a bridgeboard, from SCSI to ST506, plus floppy. So that checks out. If that SCSI HBA is custom and specific to this machine you're probably SOL on documentation, and also probably on getting anything much different from the factory-shipped disk to work with it. Will wait for pics

 

[Phipli]

Is it still doing its original job?

Is it bad if it stops working while in use?

Just re-flagging this question as it is important.

 

[veachanderthal]

Is it still doing its original job?

Is it bad if it stops working while in use?

It is scanning patients every day (when I'm not futzing with it).

If it stops working while scanning a patient it isn't desirable, but not the end of the world. Most of these systems are not on auxiliary power.

It requires a 40 second reboot process and maybe a minute or so of entering into the scanning protocol in order to resume.

There are several layers of mechanical safety independent of the computer that ensue it is safe in proximity to patients.

I'm not sure if that answers your questions, but that's what I think you were asking.

 

[Phipli]

It is scanning patients every day (when I'm not futzing with it).

If it stops working while scanning a patient it isn't desirable, but not the end of the world. Most of these systems are not on auxiliary power.

It requires a 40 second reboot process and maybe a minute or so of entering into the scanning protocol in order to resume.

There are several layers of mechanical safety independent of the computer that ensue it is safe in proximity to patients.

I'm not sure if that answers your questions, but that's what I think you were asking.

My recommendation is not to use a SCSI to SD card adapter.

If this device is working in a medical environment I would perhaps recommend buying an industrial SCSI to Compact Flash adapter and an industrial Compact Flash (these are not the same as the commercial ones you get from Amazon).

What I'm describing is more expensive, but also more appropriate for the situation, without meaning any disrespect.

There are products out there designed specifically for high reliability, and not primarily targeting hobbyists.