Sponsored Content
Full Discussion: Printer Error with Admintool
Top Forums UNIX for Advanced & Expert Users Printer Error with Admintool Post 50992 by Optimus_P on Friday 7th of May 2004 09:26:40 AM
Old 05-07-2004
why dont you list the commands you are trying.

and what you are trying to do.

admintool is very limited it is perfered that you use the command line utilities.
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Admintool

Hi, Does anyone here know where I can find out what commands admintool runs while adding a new user and setting up the account? Reason being is the script I am writting, I can add the user create the path. But it wont set the path for the user. The password well it wont add without... (1 Reply)
Discussion started by: merlin
1 Replies

2. UNIX for Dummies Questions & Answers

problem with admintool

hi, after i execute admintool, i got the below "Error, cant open display" what is wrong? thanks (5 Replies)
Discussion started by: yls177
5 Replies

3. UNIX for Dummies Questions & Answers

admintool : error display..

hi, i did the following 1) which admintool /bin/admintool 2) admintool Error: Can't open display: how to set the display then? i am using netterm to telnet to my sun server. (6 Replies)
Discussion started by: yls177
6 Replies

4. UNIX for Dummies Questions & Answers

Admintool

I am new to unix....How do I enable XWindows... Or for that matter, use Admintool. .....Pls. help. Thanks. PS. I am running Solaris 8. (3 Replies)
Discussion started by: d4jtwvb
3 Replies

5. Solaris

Admintool and rpc call

Hi all, I'm trying to launch admintool via an export DISPLAY. i get the message: Received communication service error 4: Remote procedure call timed out: program = 100087, version = 10 Just to say, i don't use nis/nisplus on my server... What to do? Thanx Jason (17 Replies)
Discussion started by: penguin-friend
17 Replies

6. Solaris

what happened to admintool?

what happened to admintool in Solaris10? (2 Replies)
Discussion started by: mndavies
2 Replies

7. Solaris

Admintool

How can I solve this admintool Error: Can't open display: (4 Replies)
Discussion started by: iwbasts
4 Replies

8. UNIX for Advanced & Expert Users

Does admintool write to eeprom?

Hi: I was setting up a modem on an Ultra5 running 2.6. (yes I know, how quaint) There are 15 systems that are interlinked but not accessible to the outside world. This will end soon with new updated sun systems but until then the system needs to be accessed by the outside world. Hence the... (1 Reply)
Discussion started by: mndavies
1 Replies

9. Solaris

HP Printer without SMC, Admintool, or Jetadmin

Jetadmin fails saying that it is not a network printer despite the fact that it is and can be pinged from UNIX. I am administering this remotely (long remote, I can't go there soon) and can't run smc or admintool. Any help configuring this spooler would be appreciated. (1 Reply)
Discussion started by: TT Fan
1 Replies
dosif(4)						     Kernel Interfaces Manual							  dosif(4)

NAME
DOSIF - DOS interchange format DESCRIPTION
The DOS Interchange Format (DOSIF) is the name given to the media format used by the DOS operating system. This format is based upon that used in IBM PC and PC AT and HP Vectra systems. Use the and commands to convert files between HP-UX and DOS file formats; see dos2ux(1). Use these utilities to retrieve information from a DOSIF volume. The dos*(1) utilities are the only HP-UX commands that can interact directly with the contents of a DOSIF volume. The only other way to interact with the contents of a DOSIF volume is to use an HP-UX DOS emulation or coprocessor facility such as SoftPC or the DOS Coproces- sor. The command cannot be used on a DOSIF volume because the operating system does not recognize it (see mount(1M)). When constructing file names for the dos*(1) commands, start with the HP-UX path name of the DOSIF volume, then add a colon followed by the file name: or This file naming convention is suitable for use only in arguments of the dos*(1) utilities. It does not constitute a legal path name for any other use in HP-UX applications. Metacharacters and can be used when specifying both HP-UX and DOS file names. These must be quoted when specifying a DOS file name, because file name expansion is performed by the DOS utilities, not by the shell. The dos*(1) utilities expand file names as described in regexp(5) in the section. By convention, if the HP-UX device name and a trailing colon are specified, but no file or directory name is provided (for example, the root of the DOS file system is assumed. EXAMPLES
Example 1 Specify DOSIF file accessed through HP-UX special file Example 2 Specify DOSIF file accessed through the DOS volume stored as HP-UX file SEE ALSO
dos2ux(1). dosif(4)
All times are GMT -4. The time now is 02:38 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy