Sponsored Content
Operating Systems SCO Getting error sco unix 507 from cdrom:no controller for device you chosen Post 302645963 by Corona688 on Thursday 24th of May 2012 10:23:44 AM
Old 05-24-2012
USB floppies should all be the same 'kind', so to speak, AFAIK.
This User Gave Thanks to Corona688 For This Post:
 

10 More Discussions You Might Find Interesting

1. SCO

sco backup using CDROM

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

Accessing device with Prolific USB-serial controller.

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

from where i can find the CDROM device

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

SCO UNIX DAT Tape Device

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

CDROM will not eject - says device busy

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

SCO 5.0.7 no root disk controller found error during install

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

Loading SCO 507 on HP ProLiant ML350 G6

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

Change Disk controller in SCO 6.0.0

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

Cdrom device possibly missing?

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

SCO OS 6 Driver for LSIL SAS1064E Raid Controller

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
putdgrp(1M)						  System Administration Commands					       putdgrp(1M)

NAME
putdgrp - edits device group table SYNOPSIS
putdgrp [-d] dgroup [device...] DESCRIPTION
putdgrp modifies the device group table. It performs two kinds of modification. It can modify the table by creating a new device group or removing a device group. It can also change group definitions by adding or removing a device from the group definition. When the command is invoked with only a dgroup specification, the command adds the specified group name to the device group table if it does not already exist. If the -d option is also used with only the dgroup specification, the command deletes the group from the table. When the command is invoked with both a dgroup and a device specification, it adds the given device name(s) to the group definition. When invoked with both arguments and the -d option, the command deletes the device name(s) from the group definition. When the command is invoked with both a dgroup and a device specification and the device group does not exist, it creates the group and adds the specified devices to that new group. OPTIONS
The following options are supported: -d Delete the group or, if used with device, delete the device from a group definition. OPERANDS
The following operands are supported: dgroup Specify a device group name. device Specify the pathname or alias of the device that is to be added to, or deleted from, the device group. EXIT STATUS
The following exit values are returned: 0 Successful completion. 1 Command syntax was incorrect, an invalid option was used, or an internal error occurred. 2 Device group table could not be opened for reading or a new device group table could not be created. 3 If executed with the -d option, indicates that an entry in the device group table for the device group dgroup does not exist and so cannot be deleted. Otherwise, indicates that the device group dgroup already exists and cannot be added. 4 If executed with the -d option, indicates that the device group dgroup does not have as members one or more of the specified devices. Otherwise, indicates that the device group dgroup already has one or more of the specified devices as members. EXAMPLES
Example 1: Adding a new device group. The following example adds a new device group: example# putdgrp floppies Example 2: Adding a device to a device group. The following example adds a device to a device group: example# putdgrp floppies diskette2 Example 3: Deleting a device group. The following example deletes a device group: example# putdgrp -d floppies Example 4: Deleting a device from a device group. The following example deletes a device from a device group: example# putdgrp -d floppies diskette2 FILES
/etc/dgroup.tab ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
listdgrp(1M), putdev(1M), attributes(5) SunOS 5.10 5 Jul 1990 putdgrp(1M)
All times are GMT -4. The time now is 02:00 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy