identify this mobo


 
Thread Tools Search this Thread
The Lounge What is on Your Mind? identify this mobo
# 1  
Old 07-18-2007
identify this mobo

I have an old mobo (socket 7) which in a former life was used in a hotel room computer.

What I want to know is if anyone knows of a company that used/uses the following boot screen:

Quote:
ImOn


please wait for your computer to load............................
now from here on I get a infinite amount of 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04..............

Im convinced the 04 is from the 16mb ide flash module (the module didnt work at all in another computer)


Ow yes, almost forgot, it doesn't seem to be a standard form factor. The mobo power connection is only 6 pins (someone knows this form factor Im sure).

Any help with this is greatly appreciated.
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. UNIX for Beginners Questions & Answers

How to identify user?

Hi Team I have created some time back a user called "iuser" but I am not able to login with it. I am getting below error. # su - iuser su: user iuser does not exist tried to unlock the user still get same error # pam_tally2 -u iuser -r pam_tally2: pam_get_uid; no such user iuser... (7 Replies)
Discussion started by: scriptor
7 Replies

2. Hardware

mobo with built-in ssd and linux

hi, thinking of building a system around this mobo: GA-Z68XP-UD3-iSSD. this has an ssd built-in to the mobo that serves as a cache for the sata drives. does linux have a chance of working on this? or is it going to get confused. thanks (6 Replies)
Discussion started by: rtayek
6 Replies

3. Shell Programming and Scripting

Identify script please!

Have a script that I'm trying to adapt for something else, but I do not understand the following lines. Can anyone help? I know what expr does, `expr 8 + 2`, but: FILENAME=`expr //$FILE : '.*/\(.*\)'` UNPACKDIR=`echo $FILE | sed -e s/$FILENAME//g` Thanks (6 Replies)
Discussion started by: bound4h
6 Replies

4. AIX

Help about identify the SP of my OS (Aix5.3)

Hi, I need to know how can I identify, wich SP is installed in my OS (AIX5.3)? and how can I upgrade it? thanks a lot, (7 Replies)
Discussion started by: fdeivis
7 Replies

5. Shell Programming and Scripting

Need help to identify files

Hi, I have one problem. I want to identify all those files which are named according to the format <name>_<date>. I have tried using awk and grep in bash but i m not able to get it correct. Can someone please help? It's urgent !! (10 Replies)
Discussion started by: udayan_goswami
10 Replies

6. Shell Programming and Scripting

Identify root like user.

Hi All, I wanted to know if there is any way , in which a user could be identified. I need to diffrenciate between a root user and a root like user. Thanks! nua7 (4 Replies)
Discussion started by: nua7
4 Replies

7. UNIX for Dummies Questions & Answers

To identify process

i want a command to display all the process running for partical user and in all process i want to see only particular process details.. pls suggest comand like ps -ef (1 Reply)
Discussion started by: Babu154
1 Replies

8. AIX

to identify failed pv

Hi friends,.... am sindhiya, i have joined as AIX level 1 support. help me to identify the failed pv in vg which has some 4 physical volumes? (2 Replies)
Discussion started by: sindhiya
2 Replies

9. Shell Programming and Scripting

identify function

Does anyone know a shell command that identifies the functions from a C file? Thank you (7 Replies)
Discussion started by: xinfinity
7 Replies

10. Filesystems, Disks and Memory

identify hardware

Does anyone know a good script/tool for remote identification of hardware on a linux-based system (RH9/NLD) ? I'd like to know all the specifics like amount of memory, motherboard vendor, chipset and so on.... (0 Replies)
Discussion started by: patrickb
0 Replies
Login or Register to Ask a Question
TALK(1) 						    BSD General Commands Manual 						   TALK(1)

NAME
talk -- talk to another user SYNOPSIS
talk person [ttyname] DESCRIPTION
The talk utility is a visual communication program which copies lines from your terminal to that of another user. Options available: person If you wish to talk to someone on your own machine, then person is just the person's login name. If you wish to talk to a user on another host, then person is of the form 'user@host' or 'host!user' or 'host:user'. ttyname If you wish to talk to a user who is logged in more than once, the ttyname argument may be used to indicate the appropriate terminal name, where ttyname is of the form 'ttyXX'. When first called, talk sends the message Message from TalkDaemon@his_machine... talk: connection requested by your_name@your_machine. talk: respond with: talk your_name@your_machine to the user you wish to talk to. At this point, the recipient of the message should reply by typing talk your_name@your_machine It does not matter from which machine the recipient replies, as long as his login-name is the same. Once communication is established, the two parties may type simultaneously, with their output appearing in separate windows. Typing control-L '^L' will cause the screen to be reprinted. Typing control-D '^D' will clear both parts of your screen to be cleared, while the control-D character will be sent to the remote side (and just displayed by this talk client). Your erase, kill, and word kill characters will behave normally. To exit, just type your interrupt character; talk then moves the cursor to the bottom of the screen and restores the terminal to its previous state. Permission to talk may be denied or granted by use of the mesg(1) command. At the outset talking is allowed. FILES
/etc/hosts to find the recipient's machine /var/run/utx.active to find the recipient's tty SEE ALSO
mail(1), mesg(1), wall(1), who(1), write(1), talkd(8) HISTORY
The talk command appeared in 4.2BSD. In FreeBSD 5.3, the default behaviour of talk was changed to treat local-to-local talk requests as originating and terminating at localhost. Before this change, it was required that the hostname (as per gethostname(3)) resolved to a valid IPv4 address (via gethostbyname(3)), making talk unsuitable for use in configurations where talkd(8) was bound to the loopback interface (normally for security reasons). BUGS
The version of talk released with 4.3BSD uses a protocol that is incompatible with the protocol used in the version released with 4.2BSD. Multibyte characters are not recognized. BSD
January 21, 2010 BSD