Note: Several of the files linked to come from the Microsoft FTP server (often from the Microsoft Software Library (MSL description, MSL file index), and The peropsys directory (which is maintained by Microsoft Product Support, as described in the peropsys description). The FTP server has been known to be unreliable, including not working well with some FTP clients, and aborting transfers. It is therefore recommended to check the downloads before assuming they are successful. (The program WGET quite nicely detected the issue, and retried the downloads, resuming successfully.) (Another option, naturally, is to obtain the files from somewhere else, such as Microsoft's website using http URLs.)
Another release has been obtainable directly from Microsoft. In addition to the 1MSDOS62.EXE, 2MSDOS62.EXE, 3MSDOS62.EXE, README.NOW, and SETUP.BAT files (which are all identical to the above release), this one also comes with NEW4_622.TXT: Why Step Up to MS-DOS 6.22 (mirrored in a supplemental files area as README.TXT), DBLCONV.EXE, DESCRIPT.TXT, and an extracted copy of DBLCDESC.TXT (which is identical to the copy of the file that is also in the DBLCONV.EXE archive file). (Locally this file has been zipped as stepeng.zip, following the naming pattern of some other languages.) This release is available from the following locations:
They are also released by Microsoft with the filename pattern of STEPxxx.EXE, where the xxx is the country code that is mentioned on Q206071. These files are located with uppercase filenames in the Microsoft Software Library using uppercase filenames, and located with lowercase filenames somewhere under http://download.microsoft.com/download/ from a link that can be found from Q124434. Each of these files are zip files that contain 5 files, including NEW4_622.TXT: Why Step Up to MS-DOS 6.22 DBLCONV.EXE (The DoubleSpace Conversion Kit), DESCRIPT.TXT, and an extracted copy of DBLCDESC.TXT (which is identical to the copy of the file that is also in the DBLCONV.EXE archive file). These 4 files are all byte for byte identical to the English versions found in one of the MS-DOS 6.22 Step-Up English releases. Additionally, there is one included file, STEPxxx.EXE with the xxx replaced by the same country code, which is byte or byte identical to the appropriate (same-language) STEPUP.EXE release found from the peropsys/ directory. (There is no documentation, neither in the expected "native" language nor in English, stating that the large file can be renamed to end with .EXE and then run in order to create the native files.)
The locations from Q124434 are:
Some information about the MS-DOS 6.22 Step-Up:
MS-DOS 6.0 to 6.2 StepUp did exist. However, it seems to have disappeared from any Microsoft public (web/FTP) site (which, and this is complete speculation, might be due to the results of the legal action that led to the creation of version 6.21 of MS-DOS). (It had been distributed on the FTP site under /peropsys/msdos as msdos6.2/stepup.exe and possibly something else under msdos6.2/ENGLISH/. and /peropsys/MSDOS/msdos6.2/FRENCH/.) Q105607 is a list of the files in the 1MSDOS62.EXE and 2MSDOS62.EXE files from this version of MS-DOS StepUp. Q105619 is a file list from the 5.25 inch 1.2MB disks. Q105618 is a file list from the 90mm disks (commonly known as “1.44MB”, 3 1/2" floppy disks”. Q105609 contains the contents of the SETUP.BAT file.
Since the file is not distributed by Microsoft, third party sites are the only location to find this file that Microsoft publicly distributed. Although it is possible none of these files are authentic, here are some pointers to the files that appear most likely to be valid: MS-DOS 6.0 to 6.2 STEPUP.EXE (found from /download/utilities.htm on that server) (zipped locally as stepup/62to622.zip) matches the oldest copies that TOOGAM had saved, which appear to have been from 2005 and so may have been collected from some third party site(s) and may not have been verified to be authentic. I found a file MS-DOS 6.2 (Unofficial, untested archive of unknown origin) which seems to have the MS-DOS 6.2 files. 7-Zip was able to open the file without a problem. I also found 62stepup.exe (from ../msdos.htm on that site) which seems largely similar, but some files are different. (Not all files that exist in one package exist in the other, and the README.* file is formatted differently, with some slightly different verbage.) MS-DOS 6.2 upgrade Readme file (HTML) http://manmrk.net/tutorials/DOS/download/62stepup.exe (found from ../msdos.htm on that server) is another copy found, but not verified. Maybe the authentic file is 1,345,024 bytes, or 1,339,776 bytes?
A file identifying itself as MS-DOS 6 to 6.2
(German) was located at:
TOOGAM saved a copy of this file (probably on April 14, 2006), renaming the file. Since then it seems that German website has changed the location of the file, but the saved copy is stored at stepup/deu6to62.zip. Note that this file has not been verified to be authentic, but it is being provided anyway in hopes that it is and in recognition that finding other copies might not be very easy.
Perhaps DOS 6 to 6.2 upgrade could benefit from the following file:
( documented on IBM BBS listing at http://john.ccac.rwth-aachen.de:8000/ftp/mirrors/ps2supersite.homedns.org/pccbbs/allfiles.txt )
dos6to62.exe 29166 05-31-95 COUNTRY.SYS and KEYB.COM files ..."File contains MS-DOS versions of COUNTRY.SYS and KEYB.COM which allows upgrading of MS-DOS 6.0 w/o the error message that files cannot be upgraded. Installation: Download file. In DOS, change to the directory with the file. Type: DOS6TO62 C:\DOS to expand le into the DOS directory. Answer ""Y""es to overwrite files."
The different MS-DOS 6.xx packages are very nearly the same as each other (when reviewing what files they come with.) Some of the software in these “supplemental files” was found in earlier releases of MS-DOS.
Dos6supp.exe (MS-DOS 6.0 Supplemental Files) (from Q124382), and the identical file MS-DOS 6.0 Supplemental Files and the identical MS-DOS 6.0 Supplemental Files from the area maintained by “Microsoft Product Support”. This includes a COMMANDS.TXT, the second half of which is published online at Q97835.
An Archive of “MS-DOS 6 Technical Reference” describes each file in the supplemental disks to the MS-DOS 6 Resource Kit. Those contain Net.exe, whereas DOS6SUPP.EXE doesn't, but some of the filenames in that web page are described and are included here.
The “Microsoft Library” has files in the MSLFILES/ directory underneath ftp://ftp.microsoft.com/Softlib/ which also had a README.TXT file. (A list of other files in that directory can be found by viewing the MSLFiles directory or the index.txt file in the Softlib directory.)
The files in the area maintained by “Microsoft Product Support” were placed in the msdos/public/supplmnt/ subdirectory underneath the ftp://ftp.microsoft.com/peropsys/ location which had a readme.txt stating who maintained the area.
See also: MS-DOS 6.0 Resource Kit: Utilities page, Q96959 (NET.TXT), Q76297 (DOS 5 supp), AccessDOS
Note: Due to FDISK overwriting early blocks (destroying usability of pre-existing partitions that it changes), and an inability to set a file system type to something recognizable as a file system that isn't one of the few that MS-DOS supports, and also for compatibility reasons (LBA48 issues), there is free other software which is better in ways than MS-DOS's official FDisk client. (See Pre-Boot software section.)
MS KB Q263044: Official FDisk update for Win98 and Win98SE (old location: http://support.microsoft.com/support/kb/articles/Q263/0/44.ASP) (The FDisk patch's original filename is 263044usa8.exe for the English release. Q263044 has links for multiple languages.)
The Q263044 upgrade would be preferred over the older update Q245213: Upgrade to FDisk since older versions limit Non-MS-DOS partition end to 8GB.
A copy of the Scandisk.exe file can be created with MS-DOS 6.22 Step-Up using Setup /F (as noted in Q120768: Disks created by MS-DOS 6.22 Upgrade and Step-Up Setup /F). Running this ScanDisk file on older versions of MS-DOS will output “This version of Microsoft ScanDisk will work only with MS-DOS versions 6.0 and later.”
Q78557: EMM386 Troubleshooting recommends that if a SCSI disk controller (examples include ASPI4DOS.SYS and USPI14.SYS) before EMM386. Another recommendation is to load "SMARTDrive double buffer" before EMM386 (using (DEVICE=....smartdrv.exe /double_buffer and then later in AutoExec.bat using smartdrv.exe /L and then, if problems persist, to change the config.sys line to use /double_buffer+ instead of /double_buffer. For MS-DOS 5.x's smartdrv.sys, the double buffer driver is used with "device=smartdrv.sys /h+". Then suggests using different A20 drivers with /MACHINE: switch on HIMEM. The page gives info on what memory sections are scanned by default, and it varies based on the EMM386 version. For EMM386 from MS-DOS 5 the range is C800-DFFF, for Win3.1 and WfWG 3.1 C600-DFFF, and for MS-DOS 6.0 and later, WfWG 3.11 and later, it is C000-EFFF. (The article says it applies to EMM386 4.95 from Win95/98.)
Win95, 98, and 98SE do come with EMM386.EXE 4.95.
[#qbasic]: The upgrade to QBASIC, which can create DOS executable (*.EXE) files, is called QuickBasic, although that is not bundled with MS-DOS, nor has Microsoft distributed it for free (except as part of the MS-DOS 6.x Step-Up packages). Q72412 says that QBASIC (from MS-DOS 5.0, 5.0a, 6.0, 6.2, 6.21, or 6.22) may hang on some systems "because of the way the QBasic environment checks for the presence of a math coprocessor chip". To fix this, one can just SET NO87=NOMATH in the DOS environmental variables. "Setting NO87 does not affect other applications' use of a math coprocessor (with the exception of MS-DOS 6.00 DoubleSpace) because the application has to look for this environment variable." "The environment variable NO87 is a switch to tell the QBasic interpreter that there is no 80x87 chip in your machine." About QBASIC, "it doesn't actually use the coprocessor even if it successfully detects one." "The same problem occurs in QuickBasic version 4.5, but the QuickBasic environment can use the coprocessor if it is successfully detected.
The original version of MS-DOS Editor (1.0) was able to be run using EDIT.Com, but EDIT.Com wasn't an advanced program: It simply called QBASIC. QBASIC.EXE would act as the MS-DOS Editor if the first switch started with three or more characters of "/EDITOR". It also supported a /QHELP parameter to run MS-DOS help (which required the appropriate help file to work well). With Windows 95, a new MS-DOS Edit version was bundled that looked similar to the old version, but did not use QBASIC. (The new version supported multiple files.) (At least some versions of the MS-DOS Editor had some support for editing binary files, using a /## command where a specified number referenced how many columns to display on each line.)
For more information on QBASIC, see the (Q)BASIC programming language page.