Salford Survivor Project. 7,567 likes 724 talking about this. Salford Survivor Project is a service based in Salford for people that are at present or have in the past been in an abusive or violent. ⚠ Fairly Demanding: You'll need a recent Mac. System requirements: OS X 10.9.5, 2.2 Ghz Intel Core i3, 4 GB RAM, 10 GB HD space, NVIDIA Geforce 330M, ATI Radeon HD 3870, or Intel HD 3000 with 256 MB of Video Memory. Role-Playing: Medium: No: Wasteland 2: Director’s Cut: Wasteland 2: Director’s Cut.
If your Mac is using an earlier version of any Mac operating system, you should install the latest Apple software updates, which can include important security updates and updates for the apps that are installed by macOS, such as Safari, Books, Messages, Mail, Music, Calendar, and Photos. Welcome to the JumpCloud Tutorial Video Series!In this video, we'll be going over how to unbind your organizations's macOS systems from Active Directory, as. Jumper wire, Recommended through-hole diameter, 0.6, 0.8 phi mm JP Series Jumper wire, Pitch=1.27, 2.54mm MC Series Power source line, Recommended through-hole diameter, 0.6 to 0.8 phi mm PL Series Jumper pin, Various size are available. JX Series Jumper pin, small type, Combination with PC.
2000.12.19 - Charles W. Moore
In our last episode, your humble servantwas left dejectedly contemplating his SuperMac S900, which doggedly refused toboot normally from its Seagate ST32550N hard drive despite protractedefforts by his filial tech adviser.
In the intervening month or so, there has been some progress but noresolution. Following publication of the previous installment of thisongoing saga, I received emails from several readers offeringsuggestions. You can read them below; thanks to everyone who took thetime to write. Special thanks must go to a reader named Lisa, whoforwarded a veritable tech info library on Umax SCSI issues, some ofwhich is reproduced below.
I also want to thank Jason C. at Seagate Tech Support, who respondedto my query with another compendium of information, which is alsoexcerpted below.
One Friday afternoon, I decided to devote a couple of hours totrying some of the above mentioned suggestions. As it turned out, I wasstill at it at midnight.
Jumper Survivor Mac Os Download
Happily, the big S900 is not too bad to get inside, although toremove the CD-ROM drive it is necessary to remove both sides of thecase. It is a testament to the Umax designers that you can remove bothside panels and the front panel of the tower by removing just one thumbscrew and then pressing a few plastic tabs.
I popped out the CD-ROM drive and the hard drive, then comparedtheir SCSI configuration with the image on Seagate ST32550N Web pageand the instructions from Lisa.
The hard drive had originally been set that the default SCSI ID 0with no jumpers at all on the termination power setting pins. After myson's last battle with the SuperMac, the hard drive had ended up beingset at SCSI ID 1 and the CD-ROM drive at ID 0.
This time I decided to return the hard drive's ID to theconventional 0 and the CD-ROM drive to ID 3, as suggested by Lisa. Ialso put a jumper on the SCSI terminator power pins positioned to taketermination power from the SCSI bus, as suggested by Jason C. atSeagate.
At this point, with both the CD-ROM drive and the hard drive layingon the table attached to their SCSI ribbon cable umbilicals, I hit thestart button and was rewarded with happy booting sounds from the harddrive. 'Ah, it's fixed,' I thought hopefully. I pulled the plug,reinstalled the drives in their proper bays, and hooked the SuperMacback up to its monitor and peripherals.
It booted nicely and restarted smoothly several times - until I letit sit for an hour or so, after which it again refused to boot. At thispoint I was still running Mac OS 9.0.4, and I decided that it might beworthwhile to return closer to the S900's roots. I booted from a CD,then restarted from OS 9.0.4 on the hard drive, which worked fine, asusual, on the restart. I then transferred the installers for Mac OS 8,and the 8.1 update from a Zip disk, then restarted again from the CD,trashed OS 9.0.4, and installed a fresh copy of OS 8.1.
Eureka! The S900 booted nicely from OS 8.1 and continued to do sofor the next several days, although there was of course no support formy USB keyboard and mouse. I thought my problems were finally solved,at least sort of, until I got around to putting the case sides back onthe machine, which had been running naked since my a jumperadjustments.
Coincidentally or not, at that point the refusal to boot from thehard drive returned. Fine, I decided, at least I'll get USB supportback, which I did by dragging a copy of my backup OS 8.5.1 from one ofthe hard drive partitions on my PowerBook's hard drive onto theSeagate. It still wouldn't boot from cold, but I was able to installApple's USB Card Support Software Version 1.2 and use my favorite inputperipherals again.
And that's pretty much the status quo. In order to get the machinestarted up, I have developed the following drill: Hit the start button.One of two things will happen; either a 'happy Mac' icon will appear,quickly replaced by a blank floppy disk icon; or get a dialogue saying'this disk is unreadable' accompanied by a futile restart button.
In either case, what I do next is insert a bootable CD in the CD-ROMdrive, which will then spin up, but not boot. I hit the reset buttonand immediately press the manual CD - eject button on the drive, whichspits out the CD.
At that point, the machine will start to boot from the system on thehard drive, but it will hang before, or more likely just as, theextensions begin loading. I press the reset button yet again, and eighttimes out of ten the S900 will finally boot from its hard drivenormally and give no more trouble until it has been shut off again foran hour or more, after which one must repeat the above process.
The other two times out of ten, even goosing it with the CD (whatever that does) doesn't work, and I end up booting from OS 8.1 on a Zipdisk using the command-shift-option-delete key combination. Again, oncesuccessfully booted from the Zip disk, it will happily reboot from itshard drive. It also boots from a floppy with no hesitation at anytime.
If I were using the S900 has my everyday computer, this would beless onerous, as I could just leave it in sleep mode 24/7 (although mywife complains about the fan noise at night when I have tried this).However, it is my backup machine, and therefore one that I need tostart up only once every few days or so.
My next planned step will be to pick up a small SCSI hard drive onthe cheap and see if that will work as a 'boot disk.' Other WorldComputing has some 500 MB Quantum Fireballs with Apple ROMs for$21.95.
My current hypotheses are that there is either still someundiscovered weirdness in the SCSI configuration, or something eitherdefective or incompatible about the Seagate ST32550N Drive. I'll keepyou posted.
The Letters
From Chris:
Hi, I was reading your article about the SCSI drive problems and some ofyour problems sounded familiar. Don't know for sure if ya got the sameproblem, but I had the same problems with inability to remount my harddrive after the computer sat overnight and such. Kept reformattingthings and everything would be just fine. Restart a few times,everything works fine so I'd confidently go to bed. Get up in themorning, and it wouldn't fire up. Norton had a tendency to lose thedrive sometimes, too. This drove me crazy for like two weeks until I checked the internalSCSI ribbon for continuity. Kind of a pain, because there's so manypins to check. It turned out that about half of the cable was showinglittle or no continuity. I don't really know why it worked at all.After changing out the cable, everything's been fine. Like I said before, it might not be the same thing causing yourproblem, but you might want to check it out. Good luck, Chris
Hi Chris;
When the problem first cropped up, we tried three different internalSCSI ribbon cables, with no difference in results.
Also, the other hard drive we tried boots up fine on the samecable.
Thanks for the suggestion, though.
Best, Charles
From Lisa:
Dear Charles, Re: your SCSI probs. I can attest it's a real pain. I have one of those9 gig Seagates from hell, it's so big I had to build a SCSI tower justto hold the monster....so I will tell you some things to check on, andat the bottom are some crib notes from an obscure website I foundw/lots of Umax info. I hate to send a book, but its complicated. Morethan it should be. First thing...driver conflicts. HDT [FWB Hard Disk Toolkit] tries totake over everything, whether it can drive it or not (like the CD), andcauses hangs. If you use Intech drivers for CD and HDs, you won't havedrivers hanging your SCSI chain anymore. HDT came with my drives, too,but its worth the time, money, and trouble it takes to get rid of itand CDT. I don't use this for a driver 'cause I don't think itsOS 9 compatible, but if it scans the chain, it'll will tell youwhere the problem is...DiskWorks™ v3.4.1. I betcha it says theCD. 1-Make the CD-ROM last on the chain...I set mine at ID 3 and enableterm...check the parity and test jumpers cause they were set wrong onsome Umax CD-ROMs. The CD-ROM itself could be causing problems. If noneof this helps, try a different one and see. The three pairs to the left set the SCSI ID and should have jumpers onthe first two. Still reading from the left there should be a jumperover the fourth pair too to enable parity. Do not enable the fifth pairfor termination if a hard disk or other device is connected lower downthe same cable. The seventh set of pins from the left (second from theright) enable a Test function. The drive will not work normally when ajumper is installed here. Make sure that test jumper isn't on. One thing to keep in mind, however, is that the J700, S900, and S910 all have two independent SCSI busses.Apple PCI Macs (e.g., 9500) have aproblem with any SCSI devices on ID 5 - use ID 4 instead. And I noticedthey still don't like having the same ID number even if they are onseparate chains. Then you get into this messy thing about term power from/to thebus. Umax says... Sometimes when a SCSI device that supplies its own termination power ispowered down, the Macintosh will still start up because the SCSI bussignal is clean enough for the startup process to take place. However,there is no assurance that the bus signals will stay clean anduncorrupted, since the SCSI bus is not properly terminated in thissituation. SCSI devices that use the termination power provided by the Macintoshdo not have to be powered on for the SCSI bus to be properlyterminated. The termination power from the Macintosh provides thecorrect termination to the SCSI bus. This situation can be confused by the fact that some drives have both'TP' and 'TE' jumpers. With such a drive, TP will pass any terminationpower through to the next device on the chain but will not actuallyterminate anything; it merely maintains the integrity of thetermination signal down the line for whatever eventually will terminatethe signal/chain. (We at Umax Computer Corporation can't really thinkof any reason why one would want to defeat the termination signal atany point along the chain - at least not in a Mac OS system - so theintended value of such a TP jumper is obscure.) In order to actuallyterminate a device which has both TE and TP jumpers, one must jumperboth the TP and the TE positions on that device. Otherwise, withno Termination Power present, Termination Enable has nothing toenable. In other words, TP should always be enabled. Why didn't they just sayso? So if your drive is in the middle of the chain, you want TP enabled sothe signal Passes thru, but not TE, which would End it. See? Ensure theStart Delay jumper is not set. No Delay Motor Start, no Enable MotorStart. Only set the Termination jumper if it's the last physical drive.Set the jumper for Terminate Power from the SCSI Bus. Most Macintosh computers with SCSI drives provide internal terminationpower except.... The MacPlus, Portable, 100-series PowerBooks, 500-series PowerBooks, the PowerBook 1400, and Macs using ATA (IDE)drives do not supply SCSI termination power. See, it's a mess, isn'tit? This IMC place has more info on Umax stuff, but I can't get it to comeup right now, so I will include some in case its gone for good.... Ihave found more info searching Google for 'Pulsar' than for Umax.Search for 'Gossamer' for beige G3s bringsup some amazing stuff in Japan. Those Japanese boys make us look like abunch of girls. It doesn't bother me, 'cause I'm used to it. Next timeyou get mad at that Umax, look at that 600 MHz G3 sitting in a UmaxS900 running in Japan. If that ICM site doesn't work anymore, let meknow and I'll send you all I have on it. Lisa
There are several issues why a drive might not boot on yourMacintosh type of machine. Software, hardware and firmware problems toname the top three. First, lets review the hardware configuration to verify the drive isproperly setup correctly. Remember, the following rules apply in general to all types of SCSIsystems including Macintosh systems. These steps below should befollowed and are the correct way the drive should be configured.
Every SCSI device needs a unique SCSI ID. Verify all devices have aunique SCSI ID.
Every SCSI bus needs termination at both ends of the cable. TheSCSI card usually supplies one end of the cable with terminationautomatically, and the user is responsible for termination at the otherend. Most UltraWide and Ultra narrow systems have the last devicephysically on the cable supply termination by changing theconfiguration jumper on the drive. The ST32550N is an Ultra narrow 50 pin device and hastermination settings on the drive. Please see the following link: http://www.seagate.com/support/disc/scsi/st32550n.html Please see the following link for more information on what istermination: http://www.adaptec.com/support/faqs/scsitermination.html
Every SCSI bus needs termination power. Termination power suppliesthe active terminator on the drive or the cable, the power needed toterminate the bus. Most SCSI controller cards supply termination powerto the bus and the drive does not need to supply. On some Seagatedrives such as the ST32250N termination power will need to beconfigured for 'termination power from SCSI bus'.
SOFTWARE:Seagate's technical support department is an excellentsource for assistance with installation and troubleshooting of yourSeagate hard drive. Seagate drives are manufactured to a specificstandard (SCSI, ATA,MFM, etc.), not to a specific hardware platform oroperating system. If you need assistance with the installation,upgrade, or troubleshooting support for your system or operatingsystem, please contact your system or OS manufacturer or vendor forinformation specific to your configuration. The following is an extract from Apple's Tech Info Library: 'Drive Setup: Non-Apple Hard Drive Support The Drive Setup application is qualified for those hard drives whichwere shipped by Apple in Apple Macintosh/Power Macintosh computers.While DriveSetup may initialize non-Apple hard drives, Apple is unableto fully test or support issues that may arise from these hard drives.For non-Apple hard drives, Apple recommends that customers usethird-party formatting utilities http://til.info.apple.com/tech info.nsf/artnum/n30572).' If you are having a problem completely setting up your drive, you willhave to use a third-party utility. To date, the following companies have reported their respective driverversions to be compatible with Mac OS 9 and below:
Charismac (Anubis Plus 3.04 and newer) http://www.charismac.com/Support/systemcomp.html
FWB 4.X (Some restrictions apply. Check web site forversioncompatibility.) http://www.fwb.com/
Intech (Hard Disk SpeedTools 2.7) http://www.intechusa.com/
LaCie (Silverlining Pro 6.x, all versions http://www.lacie.com/
FIRMWARE: 1. Unfortunately, firmware can not be changed. If this drive is not anApple compatible drive or a general distribution drive, it may not beable to work. For example a drive that was made for a SUN or UNIXmachine will have incompatible firmware on the drive. This firmware cannot be changed by Seagate, and you will not be able to use thisdrive. Jason C. Seagate Technical Support
Step 1 - Download U-Boot only image and an Helios64 image build¶
To emulate the internal eMMC as USB Mass Storage, special u-boot image is needed.Download the microSD card image from here.
You will also need to download an OS image to write to the internal eMMC.
Go to Download and chose one of the latest build.
Important
OMV (OpenMediaVault) is only supported on Debian OS.
Armbian 20.08.8 and earlier version has bug that prevent system to boot from eMMC!
Jumper Survivor Mac Os Catalina
Step 2 - Writing U-Boot image to a microSD Card¶
You will need to use an image writing tool to write helios64_sdcard_u-boot-only.img.xz to microSD Card.
Under Windows, Mac OS or Linux (via Graphic Interface)¶
Etcher is a graphical SD card writing tool that works on Mac OS, Linux and Windows, this is the easiest method for most users. Etcher also supports writing images directly from XZ files, without any prerequired decompression. To write your image with Etcher:
Download Etcher and install it on your computer.
Insert the microSD Card inside your SD card reader (microSD to SD adapter might be needed).
Open Etcher and select the helios64_sdcard_u-boot-only.img.xz image file from your local storage.
Select the microSD Card you wish to write your image to.
Review your selections and click 'Flash!' to begin writing data to the microSD Card.
Under Linux (using dd via Terminal)¶
Armbian images are using XZ compression format, therefore we need xz-utils or xz tools to decompress the image first.
for Debian-based distribution (Debian/Ubuntu) you can install the utility using following command:
in RedHat-based distribution (RHEL / CentOS / Fedora Linux) users can use this command:
after installing the compression tool, you can now decompress the images:
finally we can write the images to sdcard using dd:
Note
/dev/sdX is where the microSD is mapped in your Linux machine, change the 'X' to your corresponding mapped device. If you set /dev/sdX to a wrong device then you might risk erasing a hard drive or different device than the designated microSD.
Step 3 - Wire Helios64¶
Warning
Always proceed with caution when manipulating 110/220V appliance.
Important
If your system has the UPS battery accessory installed, then check your board is really powered off before going any further. Check Front Panel System ON LED or Board System ON LED is off. If not off, then press Power-On Button for ~4 seconds until System ON LED goes off.
Insert the prepared microSD Card.
Connect your computer to the serial port with the Type-C to Type-A USB cable.
Connect Helios64 to your home network with the Ethernet cable. Choose LAN2 port if you have 2.5Gb network.
Plug-in the DC power connector. Don't power-up the Power Adapter yet.
If you are using Helios64 without an enclosure:
Step 4 - Power-Up Helios64¶
Now that everything is ready you can plug-in the AC adapter and push the Power-On Button.
If you are using Helios64 without an enclosure:
Step 5 - Writing an OS image to Internal eMMC¶
After you have powered-up Helios64, your computer should have detected a new storage device called Linux UMS disk 0.
Now write Helios64 OS image that you have downloaded in Step 1 to the above detected storage device.
Using Etcher¶
Open Etcher and select the Helios64 image file from your local storage.
Select 'Linux UMS disk 0' drive.
Review your selections and click 'Flash!' to begin writing data to the microSD Card.
Using dd via Terminal¶
Decompress the image:
finally we can write the image to eMMC using dd:
Replace the filename by the image file name you downloaded.
Note
/dev/sdX is where the 'Linux UMS_disk_0' is mapped in your Linux machine, change the 'X' to your corresponding mapped device. If you set /dev/sdX to a wrong device then you might risk erasing a hard drive or different device than the designated Helios64 internal eMMC.
Step 6 - Power-Down Helios64¶
Power down Helios64 by long pressing (~4 seconds) the Power Button and then remove the microSD card.
Jumper Survivor Mac Os 7
Now the setup is ready for its first start, go to First Start page for further instruction.