05-24-2012
The 6.0 install follows the Unixware install instructions, not Openserver. In order to retain the 5.0.7 system calls with the 6.0 install, you may have to select eafs or htfs file systems and not vxfs as it is not supported by 507. There is also an "Openserver compatibilty mode" kernel setting which might need to be turned on for your system calls. If you have Xenix compatible system calls, you may also need to install MP4 for 6.0.0
10 More Discussions You Might Find Interesting
1. SCO
I've installed a CD-RW rom using SCO OSR 5.0.7, but I cannot open the dev to perform backup (6 Replies)
Discussion started by: tsc_hk
6 Replies
2. Programming
I am trying to access DG-100 gps logger on Mac OS X with POSIX API. The device uses a Prolific usb-serial controller, and connect to the usb port on my mac.
After I install the Prolific driver, it shows up as /dev/tty.usbserial and /dev/cu.usbserial. The vendor has published the data format. So... (1 Reply)
Discussion started by: monkeybiz
1 Replies
3. Solaris
Hi,
I attached the CDROM device in sun 2500 system , Now i want to mount this device.
From where i can find the CDROM device.
Thnx.. (2 Replies)
Discussion started by: Aamir Sahil
2 Replies
4. SCO
Looking for specifically naming convention for a tape device for SCO Unix
What full system backup command should I use for SCO UNIX (1 Reply)
Discussion started by: jedimaster
1 Replies
5. Solaris
Hi,
I've seen similar posts on this board about ejecting CDROMs but I've tried the solutions people suggested but still cannot eject the CD. It's stuck in a production box so I can't reboot it...
bash-3.00# eject -f cdrom
/vol/dev/dsk/c0t0d0/sol_10_106_sparc/s0: Device busy
bash-3.00#... (14 Replies)
Discussion started by: jimmy54321
14 Replies
6. SCO
I'm "attempting" to install SCO 5.0.7 on an HP ML370 G4 server and am ready to bash the keyboard with head now. I keep getting the error message "WARNING hd: no root disk controller found" when running the bootable install cd.
I have a raid 5 array with an online spare created using 4 36.3 GB... (2 Replies)
Discussion started by: FrictionBurn
2 Replies
7. SCO
This is my first load of SCO OpenServer v5.0.7 on a HP ProLiant ML350 G6. When it asks me to identify the source media it can't find it no matter how I respond. The SCO compatible page says it used the on board SATA DVD-ROM on Port 2 of the embedded SATA controller with "Legacy IDE emulation (as... (8 Replies)
Discussion started by: farmboy
8 Replies
8. SCO
So today I tried to upgrade a customer from a Proliant with an HPSAS controller to an Intel server with a MEGASAS controller.
First, I downloaded the megasas driver from SCO and installed it on the old system.
Then I created a new Microlite Edge emergency boot cd with the new driver on it.
I... (2 Replies)
Discussion started by: jgt
2 Replies
9. HP-UX
Hello,
I am following the HPUX 11.31 install/update guide and I am trying to install "Update-UX" from the installation media. I put the CD into the drive, and I am trying to mount the device. The instructions state:Find the DVD-ROM device file name:
ioscan -C disk -f -n -k | more
A typical... (5 Replies)
Discussion started by: bstring
5 Replies
10. SCO
Hi all,
A client has an SCO OpenServer Server 6.0, that is running on an HP ProLiant Box and they lost the root password.
Its equipped with a Doal-Core Intel Pentium Processor. They don't have any media or emergency disk anymore.
I tried to boot with the CD Rom, then "Tools", then exit to... (7 Replies)
Discussion started by: thm2222
7 Replies
LEARN ABOUT HPUX
volcheck
volcheck(1) User Commands volcheck(1)
NAME
volcheck - checks for media in a drive and by default checks all floppy media
SYNOPSIS
volcheck [-v] [-i secs] [-t secs] pathname
DESCRIPTION
The volcheck utility tells Volume Management to look at each dev/pathname in sequence and determine if new media has been inserted in the
drive.
The default action is to volcheck all checkable media managed by volume management.
OPTIONS
The following options are supported:
-i secs Set the frequency of device checking to secs seconds. The default is 2 seconds. The minimum frequency is 1 second.
-t secs Check the named device(s) for the next secs seconds. The maximum number of seconds allowed is 28800, which is 8 hours. The fre-
quency of checking is specified by -i. There is no default total time.
-v Verbose.
OPERANDS
The following operands are supported:
pathname The path name of a media device.
EXAMPLES
Example 1: A sample of the volcheck command.
The following example
example% volcheck -v /dev/diskette
/dev/diskette has media
asks Volume Management to examine the floppy drive for new media.
The following example
example% volcheck -i 2 -t 600 /dev/diskette1 &
asks Volume Management if there is a floppy in the floppy drive every 2 seconds for 600 seconds (10 minutes).
FILES
/dev/volctl Volume Management control port
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWvolu |
+-----------------------------+-----------------------------+
SEE ALSO
eject(1), volcancel(1), volmissing(1) rmmount(1M), vold(1M), rmmount.conf(4), vold.conf(4), attributes(5), volfs(7FS)
WARNINGS
Due to a hardware limitation in many floppy drives, the act of checking for media causes mechanical action in the floppy drive. Continu-
ous polling of the floppy drive will cause the drive to wear out. It is recommended that polling the drive only be performed during periods
of high use.
SunOS 5.10 21 Feb 1997 volcheck(1)