Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Search results for query: *

  • Users: mkbppt
  • Order by date
  1. mkbppt

    DEC AlphaServer Tape ejection

    The results of >>>show dev was mka400.4.0.200.0 MKA400 TLZ09 0305 apparently your tape drive was tlz, one of the tape drive series. Your your unability to eject the tape is probably the tape mangled inside. Be careful to pull it out, otherwise you will damage your drive.
  2. mkbppt

    DEC AlphaServer Tape ejection

    May be the device file is corrupted. If it a TZ tape try recreating the device file. It it is the first tape drive, first remove all /dev/nrmt0*. Then in /dev directory do this command ./MAKEDEV tz* If the TZ tape is connected and detected, then the associated device files will be created such...
  3. mkbppt

    DEC AlphaServer Tape ejection

    The command mt -d /dev/nrst0h offline or mt -f /dev/nrst0h offline and similar, should eject the tape out. But I had experience the same. The tape was not ejected even I pushed the button as suggested by dblair. Now I sacrificed the tape, changed it with exabyte, which had lower density...
  4. mkbppt

    Getting no disk found while installing Alpha from CDROM

    From >>> prompt, do command >>>show dev Is your harddisk shown there such as dka0. ... -> CDROM dkc1. ... -> Harddisk dkc3. ... -> Also harddisk etc You devices should be listed If not, may be you interface or cable is damaged If shown, then start from reinstallation the system.
  5. mkbppt

    Why Account Manager does not work?

    If you leave Account Manager (AM) or dxaccounts improperly or without using Exit command, then the application will create a lock file /etc/.AM_is_running. Next time if you try to run the application again, it will refuse because the lock file exists. To cure this, just delete...

Part and Inventory Search

Back
Top