UW2.0 didn't see my 2nd parallel port!! ???
Randy Suess
>DCU didn't see my 2nd parallel port and has no facility for
>adding one.
This is something I just ran into. How come DCU won't let
you ADD something that you know is there? I was installing
2.0 on a EISA system with a 1742 and wanted to also have
a 1542B for the tape drive, cdrom and other low volume drives.
I set the 1542B to INT 14 and I/O 334H, so the DCU of course
did not see it. However, it also has NO INSERT capability! So
there was no way for it to see the cdrom to install Unixware.
I was thinking about changing one of the other entries, such as
com2 to adsc, but instead put the cdrom temporarily on the 1742,
installed Unixware, then used pdiadd to install the 1542b.
It then worked great.
I actually do not see the use of DCU on installation.
--
An uncaged Phoenix has no friends.
Randy Suess - ra...@chinet.com - The gapers block on the Information Hiway
Jim Hohman
: DCU didn't see my 2nd parallel port and has no facility for
: adding one.
: Also, I see that you don't manually edit *device/lp any more.
: So, ... how do I make UW2.0 recognize my second parallel port??
: Thanks,
: Pete
While it is regrettably true that the autoconfiguration feature of
UW2.0 will not automatically detect your second parallel port, you
can use the DCU (Hardware Setup icon in the desktop) to add the second
serial port.
Select "Software Device Drivers"
Scroll to "Miscellaneous"
Move the cursor to "lp"
Hit "<F5> New" to add a new driver entry
Specify the I/O resources used by the second parallel port (there
is no good standard for this, unfortunately). Note that the values
presented represent the values for the first port!
Apply the change (<F10>, I think)
Return to the main menu
Apply the changes.
Unload the LP module (if it's loaded) via modadmin. You may have
disable printing to get the driver to unload.
When the driver is loaded again, there will now be an entry for the
second port (/dev/lp1).
---------------------------------------------------------------------
Jim Hohman Vox: 908-522-6312 E-mail: j...@summit.novell.com
SPEAKING ONLY FOR MYSELF, NOT MY EMPLOYER
Jim Hohman
: In article <D6ox5...@mccc.edu>, Pete Holsberg <p...@mccc.edu> wrote:
: >DCU didn't see my 2nd parallel port and has no facility for
: >adding one.
: This is something I just ran into. How come DCU won't let
: you ADD something that you know is there? I was installing
: 2.0 on a EISA system with a 1742 and wanted to also have
: a 1542B for the tape drive, cdrom and other low volume drives.
: I set the 1542B to INT 14 and I/O 334H, so the DCU of course
: did not see it. However, it also has NO INSERT capability! So
: there was no way for it to see the cdrom to install Unixware.
: I was thinking about changing one of the other entries, such as
: com2 to adsc, but instead put the cdrom temporarily on the 1742,
: installed Unixware, then used pdiadd to install the 1542b.
: It then worked great.
: I actually do not see the use of DCU on installation.
: --
: An uncaged Phoenix has no friends.
: Randy Suess - ra...@chinet.com - The gapers block on the Information Hiway
The DCU *can* be used to insert entries. You must go to "Software
Drivers", select the appropriate device type (or all device drivers),
find your device driver, hit <F5> to create a new entry, and fill in
the appropriate parameters. The default parameters are presented as
a reference for what fields are of interest.
This is possible during installation OR on the run-time system.
For the changes to take effect, the driver whose configuration
was modified must be reloaded (this is not a concern during
installation since the DCU is run before *any* drivers are loaded)
There is some nice documentation on how to use the DCU in the
System Owners Handbook. Chapter 7, I believe.
Does this help?
Pete Holsberg
Randy Suess <ra...@chinet.chinet.com> wrote:
=In article <D6ox5...@mccc.edu>, Pete Holsberg <p...@mccc.edu> wrote:
=>DCU didn't see my 2nd parallel port and has no facility for
=>adding one.
=
= This is something I just ran into. How come DCU won't let
= you ADD something that you know is there?
Yeah!
= I was thinking about changing one of the other entries, such as
= com2 to adsc, but instead put the cdrom temporarily on the 1742,
= installed Unixware, then used pdiadd to install the 1542b.
= It then worked great.
But is there a pdiadd for I/O Ports????
Randy Suess
>Randy Suess (ra...@chinet.chinet.com) wrote:
>: This is something I just ran into. How come DCU won't let
>: you ADD something that you know is there?
>The DCU *can* be used to insert entries. You must go to "Software
>Drivers", select the appropriate device type (or all device drivers),
>find your device driver, hit <F5> to create a new entry, and fill in
>the appropriate parameters.
Sigh... I musta looked at the manuals a dozen times....
Thanks!
Pete Holsberg
Mail Processes
>In article <D6pw5...@chinet.chinet.com>,
>Randy Suess <ra...@chinet.chinet.com> wrote:
>= you ADD something that you know is there?
>
>Yeah!
It will, but it has to be done in the Software section of the DCU. The
Hardware section only lists components which are presently known to
the system...
Steve
Prof. Peter J. Holsberg
>Pete Holsberg (p...@mccc.edu) wrote:
>: So, ... how do I make UW2.0 recognize my second parallel port??
>While it is regrettably true that the autoconfiguration feature of
>UW2.0 will not automatically detect your second parallel port, you
>can use the DCU (Hardware Setup icon in the desktop) to add the second
>serial port.
.....details deleted
>Apply the changes.
>Unload the LP module (if it's loaded) via modadmin. You may have
>disable printing to get the driver to unload.
>When the driver is loaded again, there will now be an entry for the
>second port (/dev/lp1).
Thanks, Jim! That wprked just fine, and I didn't have to unload the LP
module to get it to work.
One thing -- dcu is very picky about errors. I made a typo and even
though it seemed to accept the correction, it always told me that I
had a conflict. I ended up exiting from dcu and reentering.
Pete
Drangula D. M.
> This is something I just ran into. How come DCU won't let
> 2.0 on a EISA system with a 1742 and wanted to also have
> a 1542B for the tape drive, cdrom and other low volume drives.
> I set the 1542B to INT 14 and I/O 334H, so the DCU of course
> did not see it. However, it also has NO INSERT capability! So
> there was no way for it to see the cdrom to install Unixware.
> I actually do not see the use of DCU on installation.
The DCU does indeed allow you to do this. Simply select software drivers
from the DCU during installation, then select Host Bus Adapters. Move to
the driver you wish to use, in this case adsc. If the driver is not selected
already, select it using the SPACE bar. Then press F5 for the New function.
Specify the new I/O address and/or IRQ on the form provided, press F10 and
continue with the installation.
Make sure you exit the DCU with the Apply changes menu selection.
There is an opportunity to enter the DCU after the last HBA floppy has
been used.
mike Drangula | e-mail: dran...@summit.novell.com
Novell - Unix System Group | phone: you're kidding, right?
Summit, NJ | disclaimer: I only speak for myself.
copyright 1995, dran...@summit.novell.com. All rights reserved. Permission
for reproduction by USENET and like free facilities explicitly allowed. No
other reproduction rights are granted or implied.
Pete Holsberg
>The DCU *can* be used to insert entries. You must go to "Software
>Drivers", select the appropriate device type (or all device drivers),
>find your device driver, hit <F5> to create a new entry, and fill in
>the appropriate parameters. The default parameters are presented as
>a reference for what fields are of interest.
>This is possible during installation OR on the run-time system.
>For the changes to take effect, the driver whose configuration
>was modified must be reloaded (this is not a concern during
>installation since the DCU is run before *any* drivers are loaded)
>There is some nice documentation on how to use the DCU in the
>System Owners Handbook. Chapter 7, I believe.
Actually, it's chapter 6 and it's not as nice as what you posted! It
would be nice for the terms to be explained so that a person who knew
about IRQs, and I/O addresses could have a fighting chance at
selecting correct values for the *other* entities.
Pete