Frequently-asked question | Warning: WPDOS may not work well under Windows 10 | What to do if you must use Windows 10 with WP | Enable short filenames on drives other than C: | Restore non-working function keys | Printing | Batch files under Windows 10 | Generic icon only | Home page
This page concerns 32-bit Windows 10. If you have 64-bit Windows 10 (as you almost certainly do if you bought Windows 10 installed on a new computer), see this site's vDos-based vDosWP system or the DOSBox-based DOSBoxWP system for running WPDOS under 64-bit Windows.
You will have a 32-bit version of Windows 10 only if you upgraded from 32-bit Windows 7 or 8, or if you installed it yourself, or if you explicitly ordered it from one of the very few vendors who supply it. You will remember if you did any of these things. If you didn't do any of those things, then you have 64-bit Windows. If, and only if, you have a 32-bit version of Windows 10, then the rest of this page might be of interest to you.
I no longer recommend running WPDOS under 32-bit Windows. Use 64-bit Windows, and run either vDosWP or DOSBoxWP or both.
Q. Windows 10 includes something called Hyper-V that
lets me run Windows XP
in a window while running Windows 10 on my computer. Why don't you you write about it on this page?
A. Windows XP under Hyper-V is probably
one of the worst possible ways to run WPDOS that has ever been invented. See
another page on this site for further comments on this method.
Summary: You can continue to use WordPerfect for DOS under 32-bit Windows 10 by running it directly from within Windows, although you will not be able to use any graphics mode such as print preview. If you bought a new computer with Windows 10 installed, you almost certainly got 64-bit Windows 10, so you should stop reading this page and go to another page instead.
When you first run WPDOS under 32-bit Windows 10, Windows will prompt you to confirm that you want to run "16-bit" programs. You must answer Yes if you want to run WPDOS.
Warning: 32-bit Windows 10 causes the following problems with WPDOS:
(1) Unless you use Tame (which fixes this problem), WPDOS may run slowly under Windows 10.
(2) You will not be able to use any graphics mode in WPDOS, and WPDOS will instantly shut down if you attempt to use any of its graphics modes. This means that you will not be able to use Print Preview or graphics-editing mode in WPDOS 5.1 or any graphics or preview mode in WPDOS 6.x. If you absolutely must use graphics mode in WPDOS under Windows 10, consider using one of the additional methods described on this site's page about WPDOS under 64-bit Windows; those methods also work under 32-bit Windows, but should only be used if you need the traditional full-screen text mode or graphics mode in WPDOS.
(3) Windows 10 makes it impossible to run WPDOS in its traditional full-screen text mode (where the screen is entirely filled by WPDOS displaying a 25-line screen). If you need the traditional full-screen text mode of WPDOS, or if you need to use WPDOS in graphics mode, then you should use one of the additional methods described on this site's page about WPDOS under 64-bit Windows; those methods also work under 32-bit Windows, but should only be used if you need to have the traditional full-screen text mode or if you need to use graphics mode in WPDOS.
(4) The only reliable methods of printing from WPDOS under 32-bit Windows 10 seem to be the following
(5) Some of the advanced methods found elsewhere on this site - for example the macros that copy and paste between WPDOS and the Windows clipboard - may cause WPDOS to crash under 32-bit Windows 10.
(6) A minor but annoying detail: If you create or reuse a desktop shortcut for WPDOS, it can only appear on the Windows desktop as a plain white rectangle with an arrow in the lower-left corner. Desktop shortcuts for DOS-based applications running under 32-bit Windows 10 cannot display any other icon that you might wish to use. (See the workaround described elsewhere on this page.)
Note: Before performing the steps described here, you may need to disable Windows 10's User Access Control (UAC) security feature until you have completed making the changes. If Windows will not let you open the relevant files, or bothers you with prompts, download and run TweakUAC and turn off UAC or switch it to "quiet mode"; when you are finished making and testing the changes suggested here, run the utility again to restore UAC.
Follow these steps very carefully before attempting to run WPDOS with 32-bit Windows 10:
(1) Enable non-US keyboard if necessary. If, and only if, you do not use a US-English keyboard layout in WP, you must modify the Autoexec.nt file on your Windows 10 system to that DOS applications such as WPDOS use the keyboard that you need. Download this desktop shortcut EditAutoexec.nt to your Windows 10 desktop or some other convenient location (you may need to right-click on the links and select Save link as...). (Wait! What exactly does "right-click" mean?) Right-click on the file; choose "Run as Administrator" from the pop-up menu to edit the associated file in Windows Notepad; go the foot of the file and add this line (replacing xx with the two-letter abbreviation of your keyboard layout, for example, uk or nl):
kb16 xxClose and save the file. The change that you made will apply to the next DOS application you launch; you do not need to reboot your computer. Important: If you use any program that uses a special Autoexec.nt file, you must make this change in all such files.
(2) Install WPDOS. Install WPDOS to your Windows 10 computer. Install a desktop shortcut for WPDOS following the advice elsewhere on this site. Note that the shortcut will appear on the desktop as a plain white rectangle, no matter which icon you may select in the shortcut properties sheet. Specify on the Window tab that the program should open in either a window or full-screen, depending on which you prefer.
(3) Install Tame. Run WP. If it seems impossibly slow, install Tame now; otherwise, you may install Tame later.
Note: If you do not install Tame now, you may see an error message when you launch WPDOS: "NTVDM has encountered a System Error. A device attached to the system is not functioning." If you see this message, then open a command prompt (click the start menu and type "Cmd"), right-click over the title "Command prompt", select "Properties", click "Use legacy console (requires relauch)", then "Accept". Exit the command prompt (type "Exit" and press Enter), and relaunch WPDOS.
(4) Disable graphic mode. WPDOS will crash under Windows 10 if you switch to any graphics mode. To avoid this crash, close WPDOS and rename all the .VRS files in the WPDOS directory (rename them to something like .VR9 so that you can restore them in the future if you have any reason to do so); if the .VRS files are renamed, WPDOS cannot try to switch to graphics mode, and will display only a brief error message if you attempt to do so.
I am indebted to Mike Hoff for bringing this issue to my attention and pointing to the solution.
Read these clarifications first!
If your new Windows 10 system has drive letters other than the C: drive (or whatever drive contains your Windows system), then WPDOS will not be able to find (on those non-C: drives) any file that has a long filename (not a DOS-style 8.3 filenames and will not be able to find any file in a directory that has a long directory name (not a DOS-style 8.3 name). By default, when Windows 10 formats drives other than the C: drive, it disables "short filename creation."
You can test whether your system has this problem by opening a command prompt, navigating to a drive that is not your Windows drive, and then to a folder containing files or directories that have long filenames. Enter the command DIR /X which will display separate columns with long filenames and (if they exist) short filenames. If you do not see short filenames next to files with long names, then the problem exists on your system.
You can fix the problem by doing the following.
1. Click on the Start button, type cmd and wait for "Command Prompt" to pop up. Right-click on "Command Prompt" and choose "Run as administrator."
2. In the command prompt window, enter this command:
fsutil 8dot3name set 0
This tells Windows to create short filenames on all drives. (For details of the syntax see this Microsoft page.)
3. Restart your computer.
4. New files or directories that you create on all drives will now have short filenames. However, existing files that did not have short filenames earlier will not receive short filenames automatically.
5. To create short filenames for existing longname-only files or directories, the easiest method is to copy the existing file to a new filename (or the existing directory to a new directory) and delete the original. The copy will have a short filename.
6. Renaming a file or directory by copying it may be impractical in some cases. In that case, perform step 1 again to open an administrative command prompt, and enter a command like this for each file or directory that you want to rename:
fsutil file setshortname d:\path\to\longfilename.file longname.fil
The last two parameters are these: first, the full path to the file or directory for which you want to create a short filename, and, second, the short (8.3) filename that you want to see in WPDOS or any other DOS application. You can create any short filename you like; you do not need to use Windows' default method that uses a tilde and a number.
If your function keys do not perform their correct functions in WPDOS, any of a number of programs and settings could be the cause.
If almost all function keys produce unexpected results (for example, F5 types "^0"), you have probably pressed the "F Lock" key (found on some modern desktop keyboards and, on some laptop computers, next to the F12 key or some other location); press the "F Lock" key again to restore the normal function-key functions.
If Ctrl-F4 and other Ctrl-function key combinations do not perform correctly, you almost certainly have InterVideo WinCinema Manager or other InterVideo software running in the background, with an InterVideo icon in the Windows system tray (the panel at the far right of the taskbar at the foot of the screen). To regain the use of the function keys, run the Windows Task Manager (search the web to find out how to run it), click "More details", then the Startup tab, find the program that may be causing the problem, right-click on it, and select the option to disable it. Then restart your computer. You will still be able to use the InterVideo software, but you will not be able to run it by clicking an icon in the system tray.
If, in a similar way, if Alt-F5 or Alt-F10 does not perform its correct function, you probably have an ATI video card with software that interferes with Alt-F5 or an Acer computer with a backup program that takes over Alt-F10. Use the procedure described in the preceding paragraph to regain Alt-F5 by disabling the program called ATIPTAXX.exe, or to regain Alt-F10 by disabling the program CHECK.exe, and restart your computer to regain these function keys for WPDOS. If you have ATI video hardware and can't use Alt-F5, but you don't find ATIPTAXX.exe or some similar program name, go to the Control Panel, then Display; go to Settings, then Advanced, then Options, disable "Enable ATI taskbar icon application," click OK, and restart your computer.
Other programs may also seize control of function keys that you wish to use with WordPerfect. I have no way of knowing exactly which programs are at fault. The only way to find out is to run the Windows Task Manager (search the web to find out how to run it), click "More details", then the Startup tab, and (experimenting with each program, one at a time!) right-click on an entry and select the option to disable it. Then restart Windows to see if the function key you want has been restored. If you still cannot use the function key you want, run the Task Manager again, re-enable the program you tested, disable the next one on the list; then restart Windows. Continue until you find the program that has seized control of the function key. When you find such a program, please leave feedback so that others can avoid the same problem.
Note: Before performing the steps described here, you may need to disable Windows' User Access Control (UAC) security feature until you have completed making the changes. If Windows will not let you open the relevant files, or bothers you with prompts, download and run TweakUAC and turn off UAC or switch it to "quiet mode"; when you are finished making and testing the changes suggested here, run the utility again to restore UAC.
If your printer is a standard laser printer that is connected to your computer by a parallel port, then WP will print normally under Windows 10. If your printer is connected by a USB cable or across a network, but uses a WP printer driver (not one of the methods found on this site for printing to any Windows printer), then you can use one of this site's methods for printing to USB or networked printers. The most highly-recommended method is the DOSPrint method described elsewhere on this site; but you may also use the PrintFile method, as described elsewhere on this site.
If your default printer is an HP LaserJet (or compatible) and you find that nothing prints with the DOSPrint method, then you may need to install the PCL5 LaserJet driver, which is not normally used by recent Windows versions. Search the Internet for this installer file: upd-pcl5-x32-6.1.0.20062.exe and download and install it. Choose an easy-to-remember name for the printer that the installer sets up, and use that printer as the target printer in DOSPrint.
If you have a Windows-only printer and require one of this site's methods of printing to any Windows printer, then you may want to experiment with the methods on the linked page. Most, possibly all, of the methods described on that page should work with Windows 10.
Most batch files written for use in earlier versions of Windows (or DOS) will run under Windows 10. For security reasons, however, Windows 10 will not allow traditional batch files to perform certain actions, such as copying files. If you run WPDOS from a batch file that also performs such actions as copying a file, you must edit the batch file so that a command that now reads something like this:
copy thisfile.ext thatfile.extis changed by adding the command "cmd /c" (without quotation marks) at the start of the line so that it reads instead something like this:
cmd /c copy thisfile.ext thatfile.extThe same procedure may be required for other commands; feel free to experiment.
Note: Before performing the steps described here, you may need to disable Windows' User Access Control (UAC) security feature until you have completed making the changes. If Windows will not let you open the relevant files, or bothers you with prompts, download and run TweakUAC and turn off UAC or switch it to "quiet mode"; when you are finished making and testing the changes suggested here, run the utility again to restore UAC.
Desktop shortcuts for DOS-based
programs running under Windows 10 display only a blank generic icon, as in
the example shown here. When editing the properties sheet of a desktop shortcut,
you can select any icon you like, and the icon that you select will
appear in
the General tab of the properties sheet, but it will not appear on the Windows
Eight desktop. Only the generic icon will actually appear on the desktop.
This problem can be worked around in either of two ways:
Either (a) Create a batch file that runs the DOS-based program, create a shortcut to the batch file, and assign a custom icon to the shortcut. (For detailed information on creating and changing shortcuts, see another page on this site.) This workaround may cause minor problems in memory management, etc.; further information will be posted here when it becomes available. (But see the note elsewhere on this page about batch files under Windows 10.)
Note for experts: You may get slightly better results by creating a batch file that launches the shortcut (PIF) file for the program, not the program itself. (You will need to know how to identify the PIF file that you use; the extension .PIF is visible when you enter the DIR command in a command prompt window, but not in a Windows Explorer window. The contents of the batch file should be something like: start d:\path\to\WP.PIF (and enclose the path in quotation marks if there is a space anywhere in it) or (you may want to experiment): cmd /c start d:\path\to\WP.PIF (but of course, in both examples, you should use the actual path on your system, which is guaranteed not to be the example shown here). Before you do this, edit the PIF file so that its Program tab contains the full path to your WP program file and any command line switches, for example, e:\wp62\wp.com /r /tx /w-*,*,* - but remember that this example is only an example and is almost guaranteed not to work on your system. If you don't know what an "example" means, stop now and don't even think about attempting this.
Note: If you have WPDOS 5.1+ (Plus) or any version of WPDOS 6.x, use the program name wp.com as described above; if you have the original WPDOS 5.1 (not Plus), then use wp.exe instead.
Or (b) Right-click on the Windows desktop (Wait! What exactly does "right-click" mean?); select New from the pop-up menu, then Shortcut; enter cmd.exe when prompted to enter the location of the item; type a name such as "WPDOS" when prompted to type a name for the shortcut; click Finish; right-click on the resulting shortcut and choose Properties; on the Shortcut tab, in the Target field, do not change what you see there, but carefully move the cursor to the right of cmd.exe, type a space, then the following text (replacing c:\wp51 with the actual location of WPDOS on your system): /c c:\wp51\wp.com (note very carefully that this begins with a forward slash and the letter "c", then a space, then a directory location), then click on Change Icon and change the icon as described below.
Note: If you have WPDOS 5.1+ (Plus) or any version of WPDOS 6.x, use the program name wp.com as described above; if you have the original WPDOS 5.1 (not Plus), then use wp.exe instead.
If you use either of these workarounds, you may want to use one of the two
Windows 10-ready WP icons included in this
archive file;
the two images are based on the original Windows icons for WPDOS 6.x and 5.x.
Download the archive file to your Windows desktop; double-click on the archive
to open it; and copy one or both icons to your WP directory. (You may
need to disable User Access Control temporarily in order to do so.) Right-click on the
shortcut to your batch file
(Wait! What exactly does
"right-click" mean?); in the Program tab, use the
"Change Icon" button, and select one of the two icons. In this paragraph, the
WPDOS 6.x icon is on the left, the WPDOS 5.x icon on the right.
Alternatively, you may want to use one of the two
Windows 10-ready WP icons
included in this archive file; the two images are
based on the Novell and Corel logos used for Windows versions of WordPerfect.
Download the archive file to your Windows desktop; double-click on the archive
to open it; and copy one or both icons to your WP directory. (You may
need to disable User Access Control temporarily in order to do so.) Right-click on the
shortcut to your batch file
(Wait! What exactly does
"right-click" mean?); in the Program tab, use the "Change Icon" button,
and select one of these two icons. The two icons look like the images
attached to this paragraph, WPNovell.ico
on the left, WPCorel.ico on the right.
You may also use the more familiar WP icons available with earlier versions of Windows. For WPDOS 5.1, after pressing the "Change Icon" button in your batch file shortcut, type MORICONS.DLL in the filename field, and choose the familiar gray icon. For WPDOS 6.x, download this icon library file; copy it to your WPDOS directory; and, after pressing the "Change Icon" button in your batch file shortcut, navigate to your WPDOS directory, choose the file named WPICON60.ICL, and select the first icon in the library.