Sponsored Content
Full Discussion: Hyperterminal
Top Forums UNIX for Dummies Questions & Answers Hyperterminal Post 9018 by LolapaloL on Sunday 21st of October 2001 04:03:30 PM
Old 10-21-2001
what about this.....

ummm...i dont know if this is relative..but im trying to connect to a remote pc using dos and some ip scanners...im having alot of trouble....i have connected to some...but now all i get is this pc is not accepting requests, and i dont know whats up
 

6 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Hyperterminal null modem connection to Solaris

I am new to Unix. I just got my SUN box from ebay with Solaris supposedly preloaded. The problem is I am unable to connect via Hyperterminal to Solaris, or more to the point, cannot tell if I have a successful connection and that solaris is the one not properly booted up. I hooked up a null... (3 Replies)
Discussion started by: seethams
3 Replies

2. Solaris

Solaris Hyperterminal

Hi all, I currently have my WinXP machine connected to my Sun server via serial cable then hyperterminal. I would like to connect my Solaris 10 machine to the server via serial cable but there doesn't appear to be a hyperterminal application included with Solaris 10. Anyone know of a... (3 Replies)
Discussion started by: bad-ash
3 Replies

3. UNIX for Dummies Questions & Answers

Hyperterminal problems

Im trying to log in to a Sun Ultra5 using a serial cable connected to a Window 2000's box running hyperterminal. When the machine boots up, I can see the output on the hyperterminal screen but the keyboard doesnt seem to work properly, preventing me from typing in the root password. Can anyone... (15 Replies)
Discussion started by: blakmk
15 Replies

4. Solaris

hyperterminal serial solaris 8

Hi All, I connected my serial connection to the installation of solaris 8 and sorry to tell you I use XP/hyperterminal, don't get mad on me... I might use ubuntu later. When I'm installing it, it's ask me below: What type of terminal are you using? 1) ANSI Standard CRT 2) DEC VT52 ... (3 Replies)
Discussion started by: itik
3 Replies

5. Solaris

conecting to t5120 with hyperterminal....

greetings. im a very new user to solaris (and to servers for that matter) and i need to conect to a t5120 sun server, i tried using the SER-MGT port on the back of the server, then to a rj-45/db-9 adaptor, and to a serial-usb adaptor (my laptop doesn't have a com port). when i try to conect with... (2 Replies)
Discussion started by: darklilith
2 Replies

6. Solaris

No prompt from Solaris to WinXP Hyperterminal

hi I am new to unix and have found a SPARCstation 5 in the shed. I'm told by my father that it was working when it was put there about 8 years ago. It seems to boot up and makes all the right noises, both discs appear to make a noise, the keyboard lights flash etc., etc., but i can't seem to get... (2 Replies)
Discussion started by: harrystrickland
2 Replies
usoc(7D)                                                              Devices                                                             usoc(7D)

NAME
usoc - universal serial optical controller for Fibre Channel arbitrated loop (SOC+) device driver DESCRIPTION
The Fibre Channel adapter is an SBus card that implements two full duplex Fibre Channel interfaces. Each interface can connect to a Fibre Channel arbitrated loop (FC-AL). The usoc device driver is a nexus driver and implements portions of the FC-2 and FC-4 layers of FC-AL. FILES
/kernel/drv/usoc 32-bit ELF kernel module /kernel/drv/sparcv9/usoc 64-bit ELF kernel module ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Architecture |SPARC | +-----------------------------+-----------------------------+ |Interface stability |Unknown | +-----------------------------+-----------------------------+ |Availability |SUNWusoc | +-----------------------------+-----------------------------+ SEE ALSO
fctl(7D), sbus(4), fcp(7D), fp(7D), ssd(7D) Writing Device Drivers Fibre Channel Physical and Signaling Interface (FC-PH) ANSI X3.230: 1994 Fibre Channel Arbitrated Loop (FC-AL) ANSI X3.272-1996 Fibre Channel Private Loop SCSI Direct Attach (FC-PLDA) NCITS TR-19:1998 Fabric Channel Loop Attachment (FC-FLA), NCITS TR-20:1998 DIAGNOSTICS
The following messages are logged and may also appear on the system console. On the console these messages are preceded by: usoc%d: where usoc%d: is the per-port instance number of the usoc controller. Fibre Channel is ONLINE The Fibre Channel loop is now online. Fibre Channel Loop is ONLINE The Fibre Channel loop is now online. Fibre Channel Loop is OFFLINE The Fibre Channel loop is now offline. attach failed: device in slave-only slot. Move soc+ card to another slot. attach failed: alloc soft state. Driver did not attach, devices will be inaccessible. attach failed: bad soft state. Driver did not attach, devices will be inaccessible. attach failed: unable to map eeprom Driver was unable to map device memory; check for bad hardware. Driver did not attach to device, devices will be inaccessible. attach failed: unable to map XRAM Driver was unable to map device memory; check for bad hardware. Driver did not attach to device, devices will be inaccessible. attach failed: unable to map registers Driver was unable to map device registers; check for bad hardware. Driver did not attach to device, devices will be inaccessible. attach failed: unable to access status register Driver was unable to map device registers; check for bad hardware. Driver did not attach to device, devices will be inaccessible. attach failed: unable to install interrupt handler Driver was not able to add the interrupt routine to the kernel. Driver did not attach to device, devices will be inaccessible. attach failed: unable to access host adapter XRAM Driver was unable to access device RAM; check for bad hardware. Driver did not attach to device, devices will be inaccessible. attach failed: unable to write host adapter XRAM Driver was unable to write device RAM; check for bad hardware. Driver did not attach to device, devices will be inaccessible. attach failed: read/write mismatch in XRAM Driver was unable to verify device RAM; check for bad hardware. Driver did not attach to device, devices will be inaccessible. SunOS 5.10 20 Jul 1999 usoc(7D)
All times are GMT -4. The time now is 07:49 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy