05-14-2005
it probably will, but they say use only vendor tested ram because if something fails, and the ram frys the box.. there goes your warrenty with it
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi, I am new to UNIX. I have a Sun Blade 150 worksation. I used a Dell monitor and Dell keyboard as input and output devices. However, workstation always told me that keyboard couldn't be found. I used Dell keyboard with USB and Dell keyboard with series connector. It all didn't work. Please help... (10 Replies)
Discussion started by: duke0001
10 Replies
2. Solaris
I'm not familiar with this particular machine and it's baffling me. For those that are familar with the workstation, allow me to paint a picture. If you were looking down on the machine (open) you would see the main board and then a riser board. On the left side of the riser board are jacks... (1 Reply)
Discussion started by: silversaleen68
1 Replies
3. Solaris
Hi, I've been a member for a while but have never posted. I have a Sun Blade 100 desktop and I just installed Solaris 10 and it is unbearably slow. I only have 128 Meg of RAM and need to upgrade. I have searched and found many online resources that have RAM, but I was wondering if anyone has... (12 Replies)
Discussion started by: BrewDudeBob
12 Replies
4. Solaris
We had to replace a hard drive in one of our Sun Blade 150s, but now it hangs during the Jumpstart. It will show 1 or 2 Timeout for ARP/RARP messages and then start the spinning numbers. It always stops at 2ae00 and just hangs there.
We have 1 combined jumpstart server and it is also our NIS+... (5 Replies)
Discussion started by: stottsja
5 Replies
5. Solaris
Hi, this is my 1st post here, I don't know is it proper or not for the question I have, but I may try ask anyway, since it is question about sun's hw/sw issue...
I have my blade 1000 installed additional memory kits, it was originally 2G memory installed on Group0(Bank 0/2) Dimm slots, I got... (5 Replies)
Discussion started by: netshu
5 Replies
6. Solaris
I have recently re-installed Solaris 10 on a Sun Blade 150 followed by a patch set (10_Recommended) dated 2011.12.05.
I have just noticed /bin/sun now returns false, rather than true. See below.
$ uname -a
SunOS myblade1 5.10 Generic_147440-07 sun4u sparc SUNW,Sun-Blade-100
$ /bin/sparc &&... (1 Reply)
Discussion started by: apmcd47
1 Replies
7. Solaris
Hello,
Ive just aquired a blade 150 off ebay.Im new to suns and are having a problem getting it to boot off the cdrom.Openboot continuously tries to do a network boot and I cant enter any commands.Im using an average pc keyboard and it definetly works.Thanks for any help.:wall: (3 Replies)
Discussion started by: chucky
3 Replies
8. Solaris
Hello,
I cant get my blade box to boot off the harddrive after installing solaris 10.I can get to a root prompt after issuing "boot cdrom -s".I tried booting off disk0 and disk1,but I get "the file just loaded does not seem to be executable".Thanks for any help.:wall: (4 Replies)
Discussion started by: chucky
4 Replies
9. Solaris
Hi everybody,
I'm having big troubles in installing Solaris 8 on a Sun Blade 150.
Here are some system specs:
Sun Blade 150 (UltraSPARC-IIe 550MHz)
RAM: 256MB
OBP 4.10.6 2003/06/06 12:30
POST 2.0.1 2001/08/23 17:13
When I try to boot from Solaris 8 CD with boot cdrom or... (10 Replies)
Discussion started by: Vortigern
10 Replies
10. Solaris
hello
i have a forte gamma camera Philips device . and its a medical device. this medical device is came with sun blade 150 pc and pegasys is printed on the sun blade pc .the problem is when i switched the power on , the sun blade runs and a white screen appear with the information about the... (6 Replies)
Discussion started by: moh_abaloo
6 Replies
PHFIG(3) MBK PHYSICAL STRUCTURE DEFINITIONS PHFIG(3)
NAME
phfig - mbk physical figure
DESCRIPTION
The phfig is used to describe a hierarchical level of a symbolic layout and may contain any of the legal physical objects needed for a lay-
out but a phfig. All coordinates are symbolic and therefor put on a virtual grid in booth x and y directions.
The declarations needed to work on phfig are available in the header file "/labo/include/mph402.h", where '402' is the actual mbk version.
The following C structure supports the description of the layout view :
typedef struct phfig {
struct phfig *NEXT;
struct chain *MODELCHAIN;
struct phseg *PHSEG;
struct phvia *PHVIA;
struct phref *PHREF;
struct phins *PHINS;
struct phcon *PHCON;
char *NAME;
char MODE;
long XAB1, YAB1, XAB2, YAB2;
struct ptype *USER;
} phfig_list;
NEXT Pointer to the next phfig present in ram.
NAME Name of the figure. It identifies a figure (or model), so it should be unique in order to warranty consistency of cells
libraries. In order to ensure this consistency, the NAME field must be filled with the disk file name while parsing,
and must be used as file name for driving.
PHINS Pointer to the head of the list of instances being used for the model description. See phins(3) for details.
PHCON Pointer to the head of the list of connectors (terminals) of the model. See phcon(3) for details.
PHSEG Pointer to the head of the list of segments (wires) of the model. See phseg(3) for details.
PHVIA Pointer to the head of the list of contacs and vias of the model. See phvia(3) for details.
PHREF Pointer to the head of the list of references of the model. See phref(3) for details.
XAB1, YAB1, XAB2, YAB2
Coordinates of the bottom left corner of the abutment box of the figure. The abutment box of a model represents the
external visibility of a figure and is what reference is made to when instanciating the model. One should well distin-
guish the abutment box from the bounding box, which is the smallest rectangle that includes all cell descriptors. The
size and position of the abutment box is a designer concern, and cannot be computed.
MODE Caracter indicating the status of the figure in memory. This field can take two values :
'A' all the cell is loaded in ram.
'P' only information concerning the model interface is present, that means connectors and the abutment box. All
other lists are empty.
MODELCHAIN Pointer to a chain list, see chain(3) for details, of names. These are the names of the models that are at least
instanciated once in the figure.
USER Pointer to a ptype list, see ptype(3) for details, that is a general purpose pointer used to share informations on the
model.
Remark : mbk's physical view of a cell is releted to it's logical view by means of connector names, that must be identical.
SEE ALSO
mbk(1), addphfig(3), getphfig(3), delphfig(3), loadphfig(3), savephfig(3), phins(3), phvia(3), phcon(3), phseg(3), phref(3), ptype(3),
lofig(3).
BUG REPORT
This tool is under development at the ASIM department of the LIP6 laboratory.
We need your feedback to improve documentation and tools.
ASIM
/LIP6 October 1, 1997 PHFIG(3)