PSM: OS/2 Warp: Difference between revisions

From OS2World.Com Wiki
Jump to navigation Jump to search
Line 181: Line 181:


A dynamic Libpath can be very helpful in a network environment. Suppose you have an application that requires a Libpath statement to point to a directory on the file server to find the necessary DLLs to run the application. Before OS/2 Warp, you would have to modify the Libpath statement in the CONFIG.SYS file for each workstation that needed to run this application. Now, with OS/2 Warp's dynamic Libpath, you can create a CMD file with a SET BeginLibPath statement that points to the directory containing the DLLs and then loads the application. No changes have to be made to the workstations.
A dynamic Libpath can be very helpful in a network environment. Suppose you have an application that requires a Libpath statement to point to a directory on the file server to find the necessary DLLs to run the application. Before OS/2 Warp, you would have to modify the Libpath statement in the CONFIG.SYS file for each workstation that needed to run this application. Now, with OS/2 Warp's dynamic Libpath, you can create a CMD file with a SET BeginLibPath statement that points to the directory containing the DLLs and then loads the application. No changes have to be made to the workstations.
== Enhanced Boot Options==
When you boot OS/2 Warp, you will notice a white area with "OS/2" printed on the side of it in the upper left corner of your screen. When this white area appears, you can invoke some special functions during the boot process.
===Alt+F1===
You may be familiar with the Alt+F1 key sequence from previous versions of OS/2; it was used to recover your OS2.INI, OS2SYS.INI, and CONFIG.SYS files. This key sequence copied versions of these system files stored in the OS2\INSTALL subdirectory over the current files before booting the system. This was a good way of recovering these files if they were corrupted. The problem was that unless something was done in the meantime to update the files in the OS2\INSTALL directory, these files were the system's default files. This meant that your desktop was returned to the default desktop that you had immediately after installation. All your customizing was lost.
In OS/2 Warp, the Alt+F1 key sequence does things a bit differently. When you press Alt+F1 under OS/2 Warp, the system displays a menu titled Configuration and Recovery Options (see Figure 5). On this menu you have several choices. The first is to press Esc and continue the boot process without changing anything. The second is to press C to get an OS/2 command line so that you can make changes to your system manually. The third option is to press V, which resets the system to VGA mode. This allows you to boot in situations where you may not have specified the correct video drivers.
[[Image:os2warp-fig5.gif]]
'''Figure 5. OS/2 Warp Boot Configuration and Recovery Options'''
===Archived Desktops===
The Desktop's Settings notebook now has an Archive tab. When Archive is selected, the system will keep up to three generations of archives of your system files (OS2SYS.INI, OS2.INI, CONFIG.SYS, and STARTUP.CMD) and your customized Desktop settings.
After you have enabled the archive feature, the Alt+F1 boot menu displays the archives with their dates and times and gives you the ability to restore one of your archive sets. Each one of the archive sets is numbered, with 1 being your most recent archive and 3 your oldest. When you select one of these numbers, the system replaces your current system and Desktop files with the previously archived ones. The fourth option, (X), is to restore the original system files and Desktop from when the system was first installed. These new features provide a better chance of recovery if your system files or Desktop get corrupted.
===Alt+F2===
Alt+F2 provides valuable information when troubleshooting problems on your system. When you press Alt+F2 while the white area is on the screen, the system displays real-time information as the system boots.
As device drivers are loaded, the DEVICE statements are displayed at the bottom of the screen. This enables you to see the last driver executed if the system hangs while processing the CONFIG.SYS file. The last driver displayed is probably the one causing your boot problem. Now you can take steps to remove or correct that driver.
==Enhanced Formatting==
OS/2 Warp now supports fast File Allocation Table (FAT) formatting. Fast format, which is activated with the /Q option on a FORMAT statement, deletes the File Allocation Table and boot sectors without actually scanning the disk for bad sectors. As a result, the fast format completes in a fraction of the time of a regular format. Fast format is the default when formatting hard-disk drives, because today's hard disks seldom have any bad sectors. Diskette formatting defaults to the regular format. Fast format should only be used on diskettes that have already been formatted with the regular format that scans its sectors.

Revision as of 22:40, 18 October 2017

Reprint Courtesy of International Business Machines Corporation, © International Business Machines Corporation

By Edward Duhe'. IBM Corporation. Roanoke, Texas

On October 11, 1994, IBM introduced OS/2 Warp Version 3, the next evolution of its premier 32-bit operating system. As its name implies, OS/2 Warp is fast and full of state-of-the-art features. This article describes the new features of OS/2 Warp, including performance enhancements, installation enhancements, usability improvements, printing enhancements, new applications, and more. Read on, and see what it's like to operate at warp speed!

OS/2 Warp Version 3, the eighth release of IBM's award-winning 32-bit OS/2 operating system, continues the tradition of running DOS better than DOS, Windows better than Windows, and OS/2 better than previous versions of OS/2. OS/2 Warp builds on the mature, stable environment that comes from years of refining the OS/2 operating system.

You can run OS/2 Warp on an entry-level computer system, typically 386 or above, with 4 MB of RAM. Although OS/2 Warp is targeted for the home and small business user, all users can benefit from its great performance, new function, and outstanding BonusPak applications.

This article outlines what is new in OS/2 Warp, focusing on the enhancements and changes in OS/2 itself. Also, it briefly describes the applications included in the OS/2 BonusPak that comes with OS/2 Warp. The BonusPak is an exciting addition to OS/2; it gives you full-function business and productivity applications and outstanding connectivity applications that will connect you to the information superhighway.

Two OS/2 Warp Products

OS/2 Warp Version 3 is available today, and OS/2 Warp Version 3 with WIN-OS/2 will be available in the first quarter of 1995. The only difference between these two products is how you get support for running Windows applications.

With OS/2 Warp Version 3, you must have Windows installed on your computer to run Windows applications on the OS/2 Desktop. OS/2 Warp dynamically links into your Windows code, when needed, to run your Windows applications.

OS/2 Warp Version 3 with WIN-OS/2 does not require Windows to run Windows applications. This version comes with WIN-OS/2, which provides the support for Windows applications.

Both of these products can be installed in three different environments that provide different capabilities.

  • No operating system previously installed: If you install OS/2 Warp Version 3 on a computer that does not already have an operating system installed, you will be able to run both DOS and OS/2 applications on the OS/2 Desktop. If you install OS/2 Warp Version 3 with WIN-OS/2, you will be able to run DOS, OS/2, and Windows applications on the OS/2 Desktop.
  • DOS previously installed: Either OS/2 Warp Version 3 or OS/2 Warp Version 3 with WIN-OS/2 can be installed on a computer that already has DOS 3.3 or higher installed. OS/2 Warp will automatically install the Dual Boot feature in this environment. This feature enables you to boot your computer to run either native DOS or OS/2.
If you install OS/2 Warp Version 3 in this environment, you can run both DOS and OS/2 applications on the OS/2 Desktop. If you install OS/2 Warp Version 3 with WIN-OS/2 in this environment, you can run DOS, OS/2, and Windows applications on the OS/2 Desktop.
  • DOS and Windows previously installed: This is the environment for which OS/2 Warp Version 3 was really designed. By installing OS/2 Warp Version 3 on top of DOS and Windows, you will be able to run DOS, Windows, and OS/2 applications on the OS/2 Desktop. You will also be able to take advantage of the Dual Boot feature to run in a native DOS plus Windows environment.
OS/2 Warp Version 3 installs over Windows 3.1, Windows 3.11, Windows for Workgroups 3.1, and Windows for Workgroups 3.11.
OS/2 Warp Version 3 with WIN-OS/2 will also install in this environment, giving you the same capabilities described for OS/2 Warp Version 3.

Also scheduled to be available during the first quarter of 1995 is OS/2 Warp Version 3 LAN Client. This member of the OS/2 family is targeted at the LAN-connected user. OS/2 Warp Version 3 LAN Client will include OS/2 Warp Version 3 with WIN-OS/2, the OS/2 Warp BonusPak, plus LAN Server Requester, NetWare Requester, LAN Distance Remote, System Performance Monitor/2 (SPM/2), and many other features designed for the connected user.


Enhanced Performance

OS/2 Warp has been re-engineered to appeal to a much larger audience, including users of entry systems--those that are typically found in the home or small-business environment. These systems usually have few resources, including limited memory. The re-engineering of OS/2 focused on accommodating these entry systems.

Reduced Memory Requirements

One main design focus was performance and system requirements. When OS/2 2.x was announced, the minimum system requirement was stated as 4 MB of RAM. Although it was possible to run OS/2 2.x in 4 MB, the performance was, for the most part, unsatisfactory. By adding just 2 MB of RAM to your 4 MB OS/2 2.x system, you could gain significant performance advantages.

You will find that OS/2 Warp's performance on an entry-level 4 MB system is comparable to OS/2 2.11's performance on the same system with 6 MB.

Even on computers with 8 MB, 16 MB, 32 MB or more of RAM, you will still see a faster-running system under OS/2 Warp. On a high-memory system, OS/2 Warp's windows pop up faster, the populating of objects in a folder is faster, and the system runs more efficiently overall.

With its increased performance and decreased system requirements, OS/2 Warp is an excellent operating system choice for most personal computers shipping today.

Tuned-Up 32-Bit Window Management

The OS/2 Warp developers have extensively re-programmed and tuned the OS/2 kernel so that the system operates more responsively. Even though the kernel requires fewer system resources to run, it does not lack any features found in earlier kernels.

Performance gains were achieved by rewriting the OS/2 window-management system (PM-WIN) as 32-bit code and combining several of the PM-WIN dynamic link libraries (DLLs).

The 16-bit version of PM-WIN was a performance bottleneck, because on either side of the 16-bit PM-WIN component were the 32-bit shell (PMSHELL) and the 32-bit graphics engine (PMGRE). This scenario caused a large amount of "thunking" (converting 32-bit addresses to 16-bit, and vice versa) between the 32-bit components and the 16-bit PM-WIN.

Merging PMWIN.DLL with PMGRE.DLL and PMSHAPI.DLL into a single DLL called PMMERGE.DLL improved PM-WIN's performance as well. The logic is that the fewer DLLs required for the PM-WIN function, the less overhead required.

Improved Paging Subsystem

The paging subsystem was tuned to improve performance. It now uses memory more efficiently so that the most frequently used pages are in memory when needed. This reduces the amount of paging or swapping to disk, thereby reducing the overhead and time necessary to perform paging.

Enhanced Workplace Shell

The Workplace Shell includes performance enhancements, particularly during loading. The time it takes to populate folders, open objects, and load applications is faster than in earlier versions of OS/2.

There is now a fast-load option for Windows applications. In OS/2 2.x, when loading a Windows application, DOS was loaded first, then a Windows kernel, and finally the application. Once your first Windows application was running, and if you were using a shared Windows kernel, the next Windows application would load more quickly. This happened because DOS and the shared Windows kernel were already loaded by the first application.

With the new fast-load option enabled in the WIN-OS/2 Settings notebook, OS/2 Warp starts an OS/2 Windows session at startup. This OS/2 Windows session does not show up in the window list but is used by Windows applications that are started from the Desktop, allowing them to load more quickly. Windows programs that are set to run in a separate OS/2 Windows session do not benefit from the fast-load option.


Enhanced Installation

OS/2 Warp installation is greatly enhanced over OS/2 2.x. Most of the enhancements make installation much easier for the novice user. In the past, you had to identify your personal computer hardware to the OS/2 installation program for it to install the proper configuration. The OS/2 Warp installation program on the other hand, determines what kinds of hardware your computer has and decides which configuration it should install to support that hardware.

An Easy Installation option allows you to install OS/2 Warp with minimal interaction, while an Advanced Installation option gives you complete flexibility in installing and configuring your system. There are also some changes that affect the installation regardless of which option you select.

Easy Installation

The Easy Installation option is new in OS/2 Warp. Easy Installation lets you install OS/2 Warp with the push of one button--you don't have to answer questions or make decisions along the way.

When you select the Easy Installation option, the installation program detects what types of devices you have installed in your computer and selects the appropriate device drivers to support your hardware. For example, the installation program detects if you have a CD-ROM, and (if so) what type. It also detects your video type, whether you have a sound card, and much more.

The installation program then displays a configuration screen (see Figure 1), allowing you to verify the selections it has made. If you are satisfied with the installation program's selection, you click on the OK button to begin the installation.

Figure1. System Configuration Screen

In Easy Installation, the installation program always installs OS/2 Warp onto drive C:. If you want to install it onto a drive other than C:, you must use the Advanced Installation option.

The installation program installs components of OS/2 Warp based on your computer's hardware. For example, if the installation program detects Advanced Power Management (APM) capability in your computer, it installs the Advanced Power management support for OS/2.

Other than inserting the proper diskettes when prompted, all you have to do is shut down, then reboot OS/2 Warp.

Advanced Installation

The Advanced Installation option is very similar to OS/2 2.x's installation, with some notable exceptions.

Once you select the drive on which to install OS/2 Warp, you see the same System Configuration Screen displayed by Easy Installation (Figure 1). Just as in Easy Install, you can make changes to the system's selections, which OS/2 Warp made by detecting the hardware.

When installing OS/2 2.x, you were presented with a selection screen where you could "Learn the mouse," "Install preselected features," "Install all features," or "Select features." These options are not provided in OS/2 Warp. Instead, you are presented with the OS/2 Setup and Installation screen (Figure 2) where you can select the components you would like to install.

Figure 2. OS/2 Warp Setup and Installation

When installing OS/2 2.x, you were asked to make decisions about the installation at several different points within the installation process. For example, it wasn't until after all the diskettes were copied that the installation program asked you about migrating applications. In OS/2 Warp's installation, all of the questions are asked at the same time. As soon as you finish with the Setup and Installation screen, you are asked about application migration. Only after you answer all questions and make all decisions does the installation continue. Beyond that, you need only change diskettes as requested by the installation program until the installation is complete. Reboot, and your system is ready to run!

Automatic Changes to DOS CONFIG.SYS

Previous versions of OS/2 required manual changes to the DOS CONFIG.SYS file when installing the dual-boot feature. OS/2 Warp automatically installs the dual-boot feature when installed on a computer that is already running DOS and automatically modifies the DOS CONFIG.SYS files without requiring a reboot.

New BOOT Parameters

The BOOT command, used to boot between OS/2 and DOS in a dual-boot environment, has some new parameters. You can now issue a BOOT command with a /N parameter, for NOBOOT. This allows the boot records to be changed as before, but it suppresses the reboot and allows you to do an orderly shutdown. BOOT /Q displays which operating system (OS/2 or DOS) is designated to boot next.

New Diskette Format

The installation time has been reduced with OS/2 Warp. Also, the number of diskettes has been reduced by utilizing a new state-of-the-art compression algorithm called eXtended Density Format (XDF) technology. XDF extends the capacity of a 2.0 MB diskette from 1.44 MB to 1.86 MB, which reduces the total number of diskettes required. All of the diskettes are in 1.86 MB XDF format except the installation diskette and Diskette 1, which are still in 1.44 MB format.

Be aware that if you try to display the directory listing of an XDF diskette on an OS/2 2.x system, you will get a "File not found" error. This doesn't mean your diskettes are bad. To access the XDF diskettes, you must first load XDFLOPPY.FLT and a new version of either IBM1FLPY.ADD or IBM2FLPY.ADD in your CONFIG.SYS file.

XDF diskettes have a software write protection. This means that the XDF diskettes are read-only. You cannot write to or erase from any of the XDF diskettes. Use the XDFCOPY command to make copies of the diskettes.

Multimedia Installation

In OS/2 2.x, you had to install multimedia support separately from the OS/2 installation program. In OS/2 Warp, multimedia installation is integrated into the installation program; multimedia installs automatically when the appropriate system hardware is detected or when selected from the OS/2 Setup and Installation screen.

By default, the installation program does not install Multimedia Presentation Manager/2 (MMPM/2) or High-Performance File System (HPFS) if your system has less than 6 MB of RAM; however, you can use the Selective Install to add this support.

Multiple Printer Installation

OS/2 Warp's installation process allows you to install multiple printers. Previously, you could install only one printer during initial installation, requiring a much more complex process to install additional printers later. In OS/2 Warp, you can select multiple printers and assign them to the appropriate ports during the initial installation, so that all of your printers are available after installation.

Device-Driver Resource Manager

OS/2 Warp now benefits from a device-driver Resource Manager. The Resource Manager is itself a device driver that manages other device drivers and determines how they load. During installation, the Resource Manager scans input/output (I/O) ports, interrupt requests (IRQs), memory, direct memory access (DMA) arbitrations, and timers in an attempt to resolve conflicts between two device drivers.

A device driver must ask the Resource Manager for access to a port before it can load at that location. The Resource Manager determines if there is already a device driver loaded there. If not, the requesting driver is allowed to load. If a driver is already at that location, the Resource Manager scans to find another location for the device driver to load. This avoids system hangs from device-driver conflict in an industry standard architecture (ISA) bus system.

For more information about the Resource Manager and how to interact with it, type RMVIEW ? on an OS/2 Warp command line.

Larger Migration Database

The Migrate Application function of the installation process has been enhanced by the addition of more than 300 popular DOS applications and games. OS/2 Warp automatically configures the DOS and Windows settings for these applications to optimize their performance in the OS/2 environment.

Selective Uninstall

Another enhancement is the capability to uninstall components of OS/2 Warp. Through the "Selective uninstall" object in the OS/2 System Setup folder, you can remove features you don't want or use, thus freeing up disk space on your system.

Installation Media

OS/2 Warp supports installation from diskette and CD-ROM as well as remote installation via redirected installation and through the unattended configuration/installation/distribution (CID) process. Multimedia and the additional BonusPak applications are not CID-enabled.

Enhanced Usability

Usability enhancements in OS/2 Warp include an improved Tutorial, a new LaunchPad, and a dynamic Libpath.

Tutorial

The Tutorial in OS/2 Warp has been completely redone. It guides you through an overview and tells you how to manipulate objects, set up applications, customize your Desktop, and more.

The Tutorial has features such as the "Practice" button and the "Do it" button (see Figure 3). With these buttons, you can practice what the Tutorial is teaching you, as well as actually perform that function from within the Tutorial.

Figure 3. OS/2 Tutorial

For example, if you are in the color customization section of the Tutorial, and you select the practice button, the Tutorial takes you back to your Desktop and displays a window with step-by-step instructions for getting to the color palette, changing colors, and getting back to the Desktop. To return to the Tutorial, just select the return button displayed with the step-by-step instructions. If you select the "Do it" button, the Tutorial brings up the color palette and allows you to drag and drop colors on your objects. To return to the Tutorial, just select the return button, and you will be right back where you were.

Another nice Tutorial feature is that it provides information from several different user perspectives: a new user to OS/2, a user who is already familiar with Windows, and (for the expert user) some advanced tips from OS/2 experts. A message window displays text explaining the content of the currently selected topic and how you might want to use that information.

By default, the Tutorial displays information for the new OS/2 user. If you select the Windows button, you see a comparison of Windows and OS/2 and an explanation of the different terms used in each environment. And, as mentioned above, the Expert button provides you with helpful ideas about the topic from expert OS/2 users. For example, under the Desktop topic in the Tutorial, the following messages are displayed for each of the three different types of users:

  • OS/2--The Desktop is a view of your work. The items on the OS/2 Desktop represent items you normally have in your room (for example, file cabinet, printer, folders, documents, shredder). These items are called objects.
  • Windows--The OS/2 Desktop is similar to the Windows Program Manager, although the Desktop includes additional functions. OS/2 objects are like icons in the Windows Program Manager.
  • Expert--All objects on the Desktop, including those you add, are stored in the Desktop directory on the drive where OS/2 is installed (typically drive C: or D:). Open the Drives folder to access the drive and the Desktop directory.

The Tutorial also has an index and graphical help that you can use for reference.

LaunchPad

The LaunchPad, shown at the bottom of Figure 4, is a special tool bar on the OS/2 Desktop. Any object placed on the LaunchPad can be accessed with a single mouse click. By putting your frequently accessed programs on the LaunchPad, you can have quick, easy access to them.

Figure 4. The OS/2 Warp LaunchPad

Following are several interesting aspects of the LaunchPad:

  • You can easily add an object to the LaunchPad by simply dragging and dropping the object onto it. To delete an object from the LaunchPad, drag the object you want to delete, and drop it onto the shredder object. Regular-size icons can be used on the LaunchPad, or mini icons can be used to reduce its size.
  • The LaunchPad can be made to float on top of the Desktop so that it is always visible, and it can be oriented either horizontally or vertically. If your LaunchPad is behind other windows and folders, you can bring it to the top quickly by double-clicking on the white space inside a folder.
  • The LaunchPad has drawers that can contain more objects. These drawers can be detached and placed anywhere on the Desktop that is convenient for you.
  • LaunchPad objects are shadows of other objects that can be customized through their Settings notebooks.
  • Many system functions such as lockup, shutdown, find, and invoking the window list are on the default LaunchPad.

Dynamic Libpath

The Libpath statement in the CONFIG.SYS file has been a part of OS/2 through all of its versions. The Libpath statement globally defines directories to be searched for dynamic link libraries (DLLs) when OS/2 programs are loading. Because this parameter, in previous OS/2 versions, was set globally for the entire system, it could only be specified in the CONFIG.SYS file. This meant that any changes to the Libpath statement required a reboot in order to take effect.

OS/2 Warp's dynamic Libpath enables you to specify a different Libpath setting for each program session. There are two settings variables: BeginLibPath and EndLibPath. BeginLibPath allows you to specify directories to be searched before the system global Libpath directories. EndLibPath lets you specify directories to be searched after the BeginLibPath and system global Libpath directories. Both BeginLibPath and EndLibPath can be set with the SET command or through application programming interfaces (APIs).

A dynamic Libpath can be very helpful in a network environment. Suppose you have an application that requires a Libpath statement to point to a directory on the file server to find the necessary DLLs to run the application. Before OS/2 Warp, you would have to modify the Libpath statement in the CONFIG.SYS file for each workstation that needed to run this application. Now, with OS/2 Warp's dynamic Libpath, you can create a CMD file with a SET BeginLibPath statement that points to the directory containing the DLLs and then loads the application. No changes have to be made to the workstations.

Enhanced Boot Options

When you boot OS/2 Warp, you will notice a white area with "OS/2" printed on the side of it in the upper left corner of your screen. When this white area appears, you can invoke some special functions during the boot process.

Alt+F1

You may be familiar with the Alt+F1 key sequence from previous versions of OS/2; it was used to recover your OS2.INI, OS2SYS.INI, and CONFIG.SYS files. This key sequence copied versions of these system files stored in the OS2\INSTALL subdirectory over the current files before booting the system. This was a good way of recovering these files if they were corrupted. The problem was that unless something was done in the meantime to update the files in the OS2\INSTALL directory, these files were the system's default files. This meant that your desktop was returned to the default desktop that you had immediately after installation. All your customizing was lost.

In OS/2 Warp, the Alt+F1 key sequence does things a bit differently. When you press Alt+F1 under OS/2 Warp, the system displays a menu titled Configuration and Recovery Options (see Figure 5). On this menu you have several choices. The first is to press Esc and continue the boot process without changing anything. The second is to press C to get an OS/2 command line so that you can make changes to your system manually. The third option is to press V, which resets the system to VGA mode. This allows you to boot in situations where you may not have specified the correct video drivers.

Figure 5. OS/2 Warp Boot Configuration and Recovery Options

Archived Desktops

The Desktop's Settings notebook now has an Archive tab. When Archive is selected, the system will keep up to three generations of archives of your system files (OS2SYS.INI, OS2.INI, CONFIG.SYS, and STARTUP.CMD) and your customized Desktop settings.

After you have enabled the archive feature, the Alt+F1 boot menu displays the archives with their dates and times and gives you the ability to restore one of your archive sets. Each one of the archive sets is numbered, with 1 being your most recent archive and 3 your oldest. When you select one of these numbers, the system replaces your current system and Desktop files with the previously archived ones. The fourth option, (X), is to restore the original system files and Desktop from when the system was first installed. These new features provide a better chance of recovery if your system files or Desktop get corrupted.

Alt+F2

Alt+F2 provides valuable information when troubleshooting problems on your system. When you press Alt+F2 while the white area is on the screen, the system displays real-time information as the system boots.

As device drivers are loaded, the DEVICE statements are displayed at the bottom of the screen. This enables you to see the last driver executed if the system hangs while processing the CONFIG.SYS file. The last driver displayed is probably the one causing your boot problem. Now you can take steps to remove or correct that driver.

Enhanced Formatting

OS/2 Warp now supports fast File Allocation Table (FAT) formatting. Fast format, which is activated with the /Q option on a FORMAT statement, deletes the File Allocation Table and boot sectors without actually scanning the disk for bad sectors. As a result, the fast format completes in a fraction of the time of a regular format. Fast format is the default when formatting hard-disk drives, because today's hard disks seldom have any bad sectors. Diskette formatting defaults to the regular format. Fast format should only be used on diskettes that have already been formatted with the regular format that scans its sectors.