Forum Rules and Etiquette

Our mission ...

This forum is part of our mission to promote the preservation of vintage computers through education and outreach. (In real life we also run events and have a museum.) We encourage you to join us, participate, share your knowledge, and enjoy.

This forum has been around in this format for over 15 years. These rules and guidelines help us maintain a healthy and active community, and we moderate the forum to keep things on track. Please familiarize yourself with these rules and guidelines.

Rule 1: Remain civil and respectful

There are several hundred people who actively participate here. People come from all different backgrounds and will have different ways of seeing things. You will not agree with everything you read here. Back-and-forth discussions are fine but do not cross the line into rude or disrespectful behavior.

Conduct yourself as you would at any other place where people come together in person to discuss their hobby. If you wouldn't say something to somebody in person, then you probably should not be writing it here.

This should be obvious but, just in case: profanity, threats, slurs against any group (sexual, racial, gender, etc.) will not be tolerated.

Rule 2: Stay close to the original topic being discussed
  • If you are starting a new thread choose a reasonable sub-forum to start your thread. (If you choose incorrectly don't worry, we can fix that.)
  • If you are responding to a thread, stay on topic - the original poster was trying to achieve something. You can always start a new thread instead of potentially "hijacking" an existing thread.

Rule 3: Contribute something meaningful

To put things in engineering terms, we value a high signal to noise ratio. Coming here should not be a waste of time.
  • This is not a chat room. If you are taking less than 30 seconds to make a post then you are probably doing something wrong. A post should be on topic, clear, and contribute something meaningful to the discussion. If people read your posts and feel that their time as been wasted, they will stop reading your posts. Worse yet, they will stop visiting and we'll lose their experience and contributions.
  • Do not bump threads.
  • Do not "necro-post" unless you are following up to a specific person on a specific thread. And even then, that person may have moved on. Just start a new thread for your related topic.
  • Use the Private Message system for posts that are targeted at a specific person.

Rule 4: "PM Sent!" messages (or, how to use the Private Message system)

This forum has a private message feature that we want people to use for messages that are not of general interest to other members.

In short, if you are going to reply to a thread and that reply is targeted to a specific individual and not of interest to anybody else (either now or in the future) then send a private message instead.

Here are some obvious examples of when you should not reply to a thread and use the PM system instead:
  • "PM Sent!": Do not tell the rest of us that you sent a PM ... the forum software will tell the other person that they have a PM waiting.
  • "How much is shipping to ....": This is a very specific and directed question that is not of interest to anybody else.

Why do we have this policy? Sending a "PM Sent!" type message basically wastes everybody else's time by making them having to scroll past a post in a thread that looks to be updated, when the update is not meaningful. And the person you are sending the PM to will be notified by the forum software that they have a message waiting for them. Look up at the top near the right edge where it says 'Notifications' ... if you have a PM waiting, it will tell you there.

Rule 5: Copyright and other legal issues

We are here to discuss vintage computing, so discussing software, books, and other intellectual property that is on-topic is fine. We don't want people using these forums to discuss or enable copyright violations or other things that are against the law; whether you agree with the law or not is irrelevant. Do not use our resources for something that is legally or morally questionable.

Our discussions here generally fall under "fair use." Telling people how to pirate a software title is an example of something that is not allowable here.

Reporting problematic posts

If you see spam, a wildly off-topic post, or something abusive or illegal please report the thread by clicking on the "Report Post" icon. (It looks like an exclamation point in a triangle and it is available under every post.) This send a notification to all of the moderators, so somebody will see it and deal with it.

If you are unsure you may consider sending a private message to a moderator instead.

New user moderation

New users are directly moderated so that we can weed spammers out early. This means that for your first 10 posts you will have some delay before they are seen. We understand this can be disruptive to the flow of conversation and we try to keep up with our new user moderation duties to avoid undue inconvenience. Please do not make duplicate posts, extra posts to bump your post count, or ask the moderators to expedite this process; 10 moderated posts will go by quickly.

New users also have a smaller personal message inbox limit and are rate limited when sending PMs to other users.

Other suggestions
  • Use Google, books, or other definitive sources. There is a lot of information out there.
  • Don't make people guess at what you are trying to say; we are not mind readers. Be clear and concise.
  • Spelling and grammar are not rated, but they do make a post easier to read.
See more
See less

How-To: workaround when your Sun Ultra-5/10 NVRAM no longer works

  • Filter
  • Time
  • Show
Clear All
new posts

    How-To: workaround when your Sun Ultra-5/10 NVRAM no longer works

    New member here... mainly just joined to sell off my old Sun and other ancient computer equipment. But, as I was digging through old files, I found stuff that I thought might be useful to the folks here so I'm posting it in hopes this becomes an archive for such info.

    As the old Sun systems get older, eventually the NVRAM dies. Of course, you could just replace the chip, solder on a connection to replaceable batteries, etc., but in the interim, here's a procedure you can follow that will set the datetime and hostid:

    1. power on system
    2. when you see “The IDPROM contents are invalid”, hit Stop-A
    3. enter the following commands at “ok” prompt:

    ok set-defaults
    ok 1 0 mkp
    ok 80 1 mkp
    ok 8 2 mkp
    ok 0 3 mkp
    ok 20 4 mkp
    ok c0 5 mkp
    ok ff 6 mkp
    ok ee 7 mkp
    ok 0 8 mkp
    ok 0 9 mkp
    ok 0 a mkp
    ok 0 b mkp
    ok c0 c mkp
    ok ff d mkp
    ok ee e mkp
    ok 0 f 0 do i idprom@ xor loop f mkp

    4. now, enter ‘banner’ and you should see:

    Ethernet address: 8:0:20:c0:ff:ee, Host ID: 80c0ffee.

    The commands in step #3 above manually program the Ethernet and Host ID to the values you see in the line above. Normally, these things are saved in the NVRAM chip when the battery is working. Bare in mind, the address 8:0:20:c0:ff:ee is a mock up address which should work fine as long as you don’t use the same mock up address on another machine on the same network. You can change the value of the last 3 bytes to anything you wish as long as it doesn’t conflict with another Sun machine’s address.

    5. now restart with:

    ok reset

    6. after the Solaris operating system boots up, login as ‘root’ and set the time with:

    root# date 0502212911

    This sets the date/time to May 2nd, 21:29 hours, 2011. The format is:


    mm=2 digit month, dd=2 digit day of month, HH=hours, MM=minutes, YY=last 2 digits of year

    You can also bore into the IC and break out the wires to the battery. I've done this on a number of my old SPARC's with a dremmel, solder some wires on and feed it a 3.3v or 5v battery (depending on which is applicable).

    "nvsave" or "nvstore" (depending on obp version) will try to write back your settings.

    one problem .. your setting the host ID to 80 hex. That's a U1. Whilst that may 'work' for many things, your potentially using the wrong kernel and some buses are enumerated based upon this value.

    nice guide though.


    Gives a little more depth on it.


      Hi, I've got a Sun Blade 100 on gumtree and it was working fine, except for the NVRAM not storing data. I found some resources on google where people did what you've. mentioned above. I've soldered a battery on the contacts of the NVRAM, put it back to the machine and reprogrammed it. Everyrthing was fine except that it was defaulting the boot to Net and I don't have a unix keyboard to abort the operation.

      Then thought on disconnecting the battery from the NVRAM to clean it up and then re-program it and define the boot-device to disk, however, my. machine doesn't boot anymore. I don't get a beep, nothing on screen... I tried to make my own serial connection to the serial port using a FTDI cable, but didn't get anything. Do you have a clue on what may be going on or any directions on how I can troubleshoot it?

      I'm afraid of going to eBay and spending 100+ dollars on a new NVRAM and it could be something else.


        You don't need a keyboard if you have a machine you can connect to the serial port and have a terminal emulator.

        The issue is that by default the PROM will run in diagnostic mode, which is why it's trying to net boot.

        You'll need to connect your PC/terminal to the serial port via a NULL modem cable, use 9600N1 (I believe for this age of machine) and don't connect a keyboard. Power on the machine and when it starts to try to net boot use the terminal program's "Send BREAK", or disconnect the serial cable and reconnect it at a pinch. The system will now drop into the OpenPROM command line.

        At this point type: setenv diag-switch? false

        You can power-off (using the "power-off" command), disconnect the serial cable, connect the keyboard and Bob's your aunty!