How can the SCSI ID of the CD Device be determined?
How can the CD-ROM drive be mounted in UNIX?
How can the CD-ROM drive be mounted on Windows NT, Windows
95/98 and Windows 2000 platforms?
How can Pro/ENGINEER be installed if the CD device is
located on a remote node?
Why doesn't the graphical installation utility start when
setup is executed as root on UNIX systems?
Windows NT, Windows 95/95 and Windows 2000: What can prevent ptcsetup from being executed at the DOS
command line?
Why does Host ID return a blank value when selected from
the Graphical Installation Utility?
Why does the cpu_id command return "Failed to find network
adapter"?
Hewlett Packard:
If the CD-ROM drive is internal then follow the instructions on the table below to locate the SCSI ID. The first line of each row in the second column is the comand which should be executed followed by the third line which contains the output in which the number in bold is the SCSI ID.
| Platform | Command and Output
(see notes below) |
SCSI ID |
| DEC Alpha Unix | grep RRD /var/adm/messages | tail -1
(date &time) (computer) vmunix: rz5 at scsi0 bus 0 target 5 lun 0 (DEC RRD43 (C) DEC 1084)
|
5 (target #) |
| HP-UX 10.xx | insert the CD-ROM into the drive and type in the command
/sbin/fstype /dev/dsk/c?t#d0 on each device in the /dev/dsk directory.
The one that says "cdfs" is the SCSI device
|
- |
| IBM | lsdev -C -c cdrom -H
cd0 Available 00-08-00-40 CD-ROM Drive
|
4 (in the string 00-08-00-#0) |
| NEC | Check with the system administrator | - |
| SGI | hinv | grep CDROM
CDROM: unit 3 on SCSI controller 0
|
3 (unit #) |
| SUN4 (solaris 2.x) | Check with the system administrator | - |
The command to create this directory is:
mkdir /cdrom
| Workstation | CD Device Mounting Commands
(see notes below) |
| DEC Alpha UNIX | mount -t cdfs -o ro,nodefperm,noversion /dev/rz#c /cdrom |
| HP-UX 10.xx | /etc/mount -F cdfs -o ro,cdcase /dev/dsk/c?t3d0 /cdrom |
| IBM | mount -v cdrfs -o ro /dev/cd0 /cdrom |
| NEC | mount -F cdfs -o ro,fperm=0555 /dev/sr/c0t#d0 /cdrom |
| SGI | mount -t iso9660 -o ro /dev/scsi/sc0d#l0 /cdrom |
| SUN4 (solaris 2.x) | All Sun workstations automount to /cdrom |
Ptc.SETUP is executed on a UNIX machine by changing to the /tmp directory and typing:
[cdrom]/setup
The value '[cdrom]' is replaced with the path directory for the mounted CD-ROM device. On a Windows NT, Windows 95/98 or Windows 2000 machine, Pro/SETUP should start automatically. If it does not, the utility will start by double-clicking with the mouse on 'setup' in the CD-ROM drive within My Computer or Windows Explorer.
It is not required to install or configure the license server as root on UNIX, however on Windows NT and Windows 2000 workstations, if FLEXlm is being installed then an administrator or account with administrative priveledges (specifically to Services) is necessary. Afterwards, depending on the account type and permissions on the installed files, any user may configure the FlexLM license server through setup or ptcsetup.
If the CD device is located on a remote node, the following steps can be taken to perform a remote installation:
example: rcp /cdrom/setup royale:/tmp
/tmp/setup remote_hostname:/cdrom
where: remote_hostname is the hostname of the remote node and cdrom is the directory to which the Pro/ENGINEER CD is mounted.
example: /tmp/setup tower:/cdrom
For Windows NT/95/98/2000 workstations, if the device is shared out,
insert the cdrom and run it from the remote node on that shared device.
On many UNIX systems the DISPLAY environment variable is unset for the root user. Enter "echo $DISPLAY" to determine if the environment variable has been specified. If this command returns ":0.0" or "unix:0" as the variable value, the variable is set to the current working node. If the command does not return a string, the variable is unset. Enter "setenv DISPLAY hostname:0.0" in a C Shell to set the variable.
This error occurs when the prosetup command is issued from the loadpoint/install/unix directory. The command loadpoint/bin/ptcsetup should be entered to execute ptcsetup instead of prosetup.
This occurs when ptcsetup is executed from either of the loadpoint/bin or loadpoint directories. Change working directories to another working directory (/tmp is recommended) and execute ptcsetup. If the ptcsetup command is not found from this directory, enter the full path to ptcsetup: loadpoint/bin/ptcsetup. If more than one version of Pro/ENGINEER is installed, be sure to use the full path to the desired loadpoint.
Removal or absence of the \loadpoint\bin directory from the PATH variable will prevent ptcsetup from executing. Add the directory to the system PATH variable to ensure that it is available for all users.
Ensure that the machine has the required amount of disk space for a full installation of the PTC product to be installed. Also, this problem has also been reported with use of the Gateway2000 and the Mitsumi CD drive. The Mitsumi CD drive reads the Pro/ENGINEER files at a different rate than those currently recommended by PTC.
The problem results from Microsoft's initial lack of support for the AT API Drive. Microsoft has since made available a patch which was first available in "US Service Pack 2". As of the first shipment of Release 17.0 of Pro/ENGINEER, "US Service Pack 4" is available from Microsoft. This patch contains all previous service packs and may be installed to address this issue.
Gateway has been informed of the situation and should be contacted at 1-800-846-2000 should the above problem be encountered. The "US Service Pack 4" for Windows NT can be obtained from your Microsoft vendor or through Microsoft's website at http://www.microsoft.com.
This error occurs due to one or more of the following reasons:
This error occurs due to one or more of the following reasons:
The message "nst.exe - undefined variable" indicates that the workstation ethernet port is not terminated properly. Contact your HP vendor for instructions on proper termination.