just.in.time
Well-known member
Any chance of getting that added as a paid option at order time, much like the Floppy-style Berg connector?It does not. Very few people use it by default, and for those that want it, it can be easily added.
Any chance of getting that added as a paid option at order time, much like the Floppy-style Berg connector?It does not. Very few people use it by default, and for those that want it, it can be easily added.
I second this. Ive never used any of the scsi-to-sd setups and I thought I had my SD card set up right. It just sadmacs my 475 when hooked up though.I just ordered mine, anyone make a quick start guide post for getting one of these setup yet? Sounds like setup should be easy if you go hunt for all the info but would be nice to have a precise write up. Guess I’ll do it when mine comes if no one else has done it yet. Seems crazy this doesn’t exist yet.
In those sorts of situations, it would generally be advisable to reach out to the vendor who sold you the product, for technical support. Have you?I second this. Ive never used any of the scsi-to-sd setups and I thought I had my SD card set up right. It just sadmacs my 475 when hooked up though.
Well, that's nice--I couldn't find that manual when I looked. I suggest you link it on your main site--perhaps in the resources dropdown? Right now it appears you can't get to it without the URL.In those sorts of situations, it would generally be advisable to reach out to the vendor who sold you the product, for technical support. Have you?
I'd recommend checking out http://zuluscsi.com/ZuluSCSI-Manual/#using-quickstart
There's additional documentation at
https://github.com/ZuluSCSI/ZuluSCSI-firmware/blob/main/README.md
Thanks for the feedback. All future recipients of ZuluSCSI boards will receive a link to the documentation above. The GitHub project itself is linkedin from the ZuluSCSI.com website
Nah, my mistake. It was my SD card I was using. It just took a minute to diagnose it. Managing a one year old toddler, a job, and the fact I do all the household work means my time is VERY limited.In those sorts of situations, it would generally be advisable to reach out to the vendor who sold you the product, for technical support. Have you?
I'd recommend checking out http://zuluscsi.com/ZuluSCSI-Manual/#using-quickstart
There's additional documentation at
https://github.com/ZuluSCSI/ZuluSCSI-firmware/blob/main/README.md
Thanks for the feedback. All future recipients of ZuluSCSI boards will receive a link to the documentation above. The GitHub project itself is linkedin from the ZuluSCSI.com website
Done! It's now linked under the resources drop-down on the main http://zuluscsi.com website.Well, that's nice--I couldn't find that manual when I looked. I suggest you link it on your main site--perhaps in the resources dropdown? Right now it appears you can't get to it without the URL.
Agreed.Also, I suggest you encourage your vendors to link to the manual.
Your feedback is appreciated. If there are areas within the documentation that you feel could use improvement, always feel free to shoot us an e-mail.That will definitely help new buyers. I guess I can toss the "getting started" doc I was putting together LOL
SelectionDelay
to zero in zuluscsi.ini, but whenever I try to copy a file to the virtual SCSI volume, my Mac Plus gives me the bomb alert with “illegal instructions”. Back in the day this used to be typically associated with termination problems in the SCSI chain, but it shouldn’t be possible here.@frankz what's the firmware version on the Mini? It's logged to zululog.txtI just purchased a ZuluSCSI Mini 1.0 for my Mac Plus. I was able to boot from a System 6.0.8 image by settingSelectionDelay
to zero in zuluscsi.ini, but whenever I try to copy a file to the virtual SCSI volume, my Mac Plus gives me the bomb alert with “illegal instructions”. Back in the day this used to be typically associated with termination problems in the SCSI chain, but it shouldn’t be possible here.
Does anyone have experience running a Mac Plus with ZuluSCSI? Any setting I should try? Thanks!
Thanks for your reply! The firmware version is:@frankz what's the firmware version on the Mini? It's logged to zululog.txt
Additional info: I am powering the ZuluSCSI mini from the termination power, for which I have modified the Mac Plus by installing a diode to provide 5V to pin 25 of the SCSI port. I can undo the modification and try to power the ZuluSCSI device from USB, if necessary.FW Version: 1.0.2 May 17 2022 08:12:51
Thanks. This is the latest released version of the firmware. What's the size of the exported volume? Have you tried one that's smaller? If you could create a file named zuluscsi.ini, and in it place the following in the [SCSI] section:Thanks for your reply! The firmware version is 1.0.2
That really sums it all up quite nicely!1. Reading about a new XXXXSCSI alternative made me happy
2. Reading the rest of the thread made me sick
Thanks! I’ve been using 2GB volumes (drive images, actually, with partition map and everything – should I use volume images instead?). I will try today to use a smaller 20MB one, and I will also disable SCSI2, enable debug, and report back.Thanks. This is the latest released version of the firmware. What's the size of the exported volume? Have you tried one that's smaller? If you could create a file named zuluscsi.ini, and in it place the following in the [SCSI] section:
[SCSI]
EnableSCSI2 = 0
...and see if that changes the behavior at all? You might also want to try adding "Debug = 1" to the INI file. This will enable rather verbose logging, and could be useful for us to troubleshoot the problem, if we can't figure things out.
They should always be drive images. the Macintosh ROM can not boot successfully from SCSI devices that don't include a partition map, to the best of my knowledge.Thanks! I’ve been using 2GB volumes (drive images, actually, with partition map and everything – should I use volume images instead?). I will try today to use a smaller 20MB one, and I will also disable SCSI2, enable debug, and report back.
Great thanks, I thought that was the case but I thought I might check anyway.They should always be drive images. the Macintosh ROM can not boot successfully from SCSI devices that don't include a partition map, to the best of my knowledge.
Has anyone thought about making a SCSI disk clicker like BMOW's floppy noise clicker? Get those nostalgic noises going. Interface it between your favorite SCSI emulator (or maybe optical drive since they don't make noises, really.)