One neat feature of SBus cards is that they have a PROM whose contents firstly identify the card and its characteristics, and secondly may contain an optional software driver.
Restoring the SPARCstation IPX has been a fun project and it's great to finally have a working system of the sort that I desperately wanted to own as a teenager, but which was very far beyond my reach. In addition to which there are a few potential future projects that would make use of this and while somewhat more the slow burn type, I hope to eventually share details in due course.
Hi Andrew, congrats for a very good job to make this series for the little IPS ; I have changed all caps on my IPX psu with good nichicon pw series but I have the same issue you have on first psu. You have resolved? You find where is the problem?
My tracks on pcb are ok, the HV section work but the psu try to start for one second, then stop. I also tried to move the 5v trimmer, without luke. It would "kick" the fan briefly upon powering up and that was about it. At this point I switched to recapping another PSU and this one then worked. However, I did not change C and C, and it was suggested in the comments on the first post in this series that these should be changed also.
I haven't got round to trying that yet and I'm not sure when I will. Sorry I can't be of more assistance and hope you manage to bring your IPX back to life! Andrew Back seems to be too easy, but… on my psu the issue is on relay close to power cable! Opened and cleaned, and now work good ;-. Great series Andrew. By chance i was restoring an IPC and an IPX about the time you started your series so i have been following along and your posts have been very helpful.
I used the scheme of creating a virtual CDROM drive as the first image on a 32GB card and they laying out 4 more disks on the same card. So far i have SunOS 4. Im also going to install Solaris 2.
SunOS 4. Once done, it seems to work great. NetBSD 9. Its pretty usable however. Solaris 2. My goal is to have four complete OS's on the SD card so i can boot into any of them.
Like you I could not get the or timekeeper replacements to work on the IPX but the works fine on the IPC, which seems a bit odd. Anyway, great series, really enjoyed it! ToddVernon Thanks, Todd! And interesting to hear about your progress.
Are there details online anywhere for hacking SunOS 4. Configure the SunOS clients on your network to recognize the Backup server by defining an alias called "nsrhost" for your Backup server on each client. This section also shows you how to use NIS to configure the clients to recognize the Backup server. The server with the nsrhost alias is considered the primary Backup server.
For example:. Note - If you have more than one Backup server, you can only use one server as the NIS master, usually your primary server. For more information about how clients bind to Backup servers, refer to the nsr manual page. If you have clients of the same hardware platform as the Backup server, use the same software distribution media to install Backup on the clients.
Instructions for installing the client software on like clients are provided in this section. For clients with different hardware platforms, you need to purchase and install the client software separately.
Contact your local customer support office for information about the ClientPak software packages. In order for Backup clients to use the Backup server to back up and recover files, they must be able to use the Backup software.
There are two ways a client can access the Backup software. Caution - In order to back up a Backup client running Backup 4. For more information about the access control policies for the Backup commands, refer to "Restricting Client Access" in Chapter 3 of the Solstice Backup 4. If a client is not set up to share programs over the network, then you must install the Backup software directly on that client.
This section describes the software installation for SunOS clients that have the same software and hardware as the server. Copyright c Legato Systems, Inc. All rights reserved. The nsrexecd program restricts access to a select set of Backup servers. If a computer has more than one network interface, please interface's name one at a time. When you have completed installing the client software, remove the distribution media from the device and store it in a safe place.
The client-side nsrexecd program restricts access to a select set of Backup servers. Please enter the names of each computer running a Backup server that will back up this client, one name at a time.
If a computer has more than one network interface, please enter each. Once Backup is installed on both the server and the clients, refer to the Solstice Backup 4. Refer to the Solstice Backup 4. This section contains instructions for installing the Jukebox Software Module after installing the server software, and instructions for installing the server and device driver software simultaneously.
In the following sections, the term jukebox is used to refer to a variety of backup devices, including the following: autoloader, carousel, library, near- line storage, datawheel, and autochanger. If your jukebox is connected with a serial port, you do not need to install the driver.
Simply skip the instructions in this guide regarding the driver installation. However, you do need to configure and connect your jukebox by following the hardware instructions shipped with your jukebox. You must also properly enable and register your Autochanger Software Module. See Chapter 4, "Enabling and Registering Backup ," for information about enabling and registering the module.
If you are installing the Jukebox Software Module for the first time, skip this section. If you already have the Jukebox Software Module installed, you must first de-install the old driver before installing the new one. To de-install the driver, become root , and change to the directory where the driver was originally installed, then enter the deinstall command:.
Previous: Build Problems , Up: Top. If you don't specify this, the configure script will try to find a suitable C compiler. The default choice is gcc. If you wish to use a vendor compiler you must set CC to that compiler, and set other environment variables as described below to appropriate settings. If you don't specify this, the configure script will try to find a suitable Fortran and Fortran 77 compiler.
0コメント