3.879 bytes

Service Hints & Tips

Document ID: MNOK-3T5R5N

Aptiva - How to get to an OS/2 Command Prompt

Applicable to: World-Wide

From the OS/2 desktop:
1. Double-Click on the OS/2 System icon.

2. Double - Click on the Command Prompts icon.

3. Double - Click on either the OS/2 Full Screen or the OS/2 Window icon.

When booting the system from the harddrive or the OS/2 Installation diskette:

1. When the white block and OS/2 appear in the upper left corner of the screen while booting up, press Alt + F1.

2. Press F2 when the selection menu appears.

When booting the system from the Aptiva Recovery diskettes:

1. Shut down the machine. Insert the first recovery diskette into drive A: and boot the system.

2. The machine will restart and read from the disk. A blue screen with an IBM logo will appear and prompt for recovery diskette number 2. Insert disk 2 and press the Enter key on the keyboard to continue.

3. An OS/2 Warp logo screen will appear, followed by an Aptiva Recovery menu that lists the following options:

Aptiva Recovery Menu

1) Recover the Aptiva OS/2 Warp Image

2) Recover Configuration Files

3) Edit Autoexec.bat

4) Edit Config.sys

5) Edit Startup.cmd

6) Go to OS/2 Warp Command Prompt

4. Select option #6 to get to an OS/2 Command Prompt.

When booting the system with the OS/2 Utility diskettes:

When booting up the system with the OS/2 Utility diskettes, follow the prompt to insert the second diskette and continue the boot process. The second Utility diskette takes you directly to an OS/2 command prompt screen.

Search Keywords

Hint Category

OS/2

Date Created

01-04-98

Last Updated

29-05-98

Revision Date

28-05-99

Brand

IBM Aptiva

Product Family

Aptiva

Machine Type

2144, 2168

Model

2R5; 2R7; 2R8; M30; M35; M50; 2R6; 4R7; 4R8; M40; M54; M58; P30; 2R0; M60; M70; 3R0; 3R8; 932; LS2; LSB; LP2; LPB; KP2; KPB; LL1; L10; K10; LL3; L30; K30; LL5; L50; K50; L33; K33; L35; K35; U33; U35; XP1; YP1; 27J; 28J; 63J; 64J; 65J; 70J; 71J; W30

TypeModel

Retain Tip (if applicable)

Reverse Doclinks
and Admin Purposes