#DOS 6.22 DOWNLOAD TORRENT CODE#
#DOS 6.22 DOWNLOAD TORRENT TORRENT#
#DOS 6.22 DOWNLOAD TORRENT WINDOWS#

Apart from that, the only other diff table to hand-make is setver.exe (because of extra entries in the version table). IO.620 and IO.622 are just IO.SYS, which is different in the two DOS versions (the latter can load drvspace.bin also), so we had to hand-make the fc/b output.Ĭ differs between the three dos versions 6.20, 6.21 and 6.22, so we would have to hand-make this diff table too. You could add extra entries for copyright date and start menu, which we don't here.

IO.SYS sets the dos version in the first four bytes. No further user intervention is needed save for some dos version checks, and the copyright date. MSDOS.SYS is pretty much a utility like debug.exe or edlin.exe. Here is the working part of the 'cvmod.dat' file that modifies the dos kernel on demand. Running some sort of 'delete if same' utility over 6.21 based on 6.20, pretty much guts 6.21 entirely.Ħ.22 is frighteningly so similar to 6.20/6.21 that one can quite easily get away with a 'real MS-DOS 6.30' project, and with little editing, a 'real MS-DOS x.xx' utility that consists of a handful of batch files and rexx scripts that pretty much does this (even down to the niceties of making DOSSHELL report the correct version in help | about. IO.SYS and MSDOS.SYS are identical here, although is different. MS-DOS 6.21 is pretty much a string hack of 6.20, in much the same way that this beta is of 6.22.

#DOS 6.22 DOWNLOAD TORRENT CODE#

This is not all that hard to do if you actually have access to the source code (like microsoft would in a legit beta), or if you can get two versions so close that the bulk of the code just differs by these tests (as we do with 6.21 and 6.22). It's pretty much a hacked version of 6.22, but still essentially 6.22.Ĭonsider on the other hand, that '607' 'MS-DOS 7 beta 1' is based on the 6.00 code, is actually something like msdos 7.00 to ver, to int21/30, and to int 21/3306. and are totally from 6.22 (They were missing)

README.TXT seems to be just a modified original from a far previous version, as some of the 'improvements' were included already in 6.00Ĭlarification.

Why use different PKLite versions all of a sudden, then move back to an older one?

#DOS 6.22 DOWNLOAD TORRENT WINDOWS#

FORMAT.EXE is packed with PKLite 1.12, whereas the one in Windows ME (which is supposedly newer than 6.30) is packed with 1.15.

Ver reports 6.22, MS always used unified version variables in DOS, so when it always reported the same version everywhere.

#DOS 6.22 DOWNLOAD TORRENT TORRENT#

I've seen this hack myself on various torrent sites and sites out there, all a bit different but basically the same. There's way too many things showing this is just a cut-paste with some hexediting involved. Mrpijey wrote:As OBattler above pointed out, this is indeed a hack and not a real beta. README.TXT seems to be just a custom made file, as some of the 'improvements' were included already in 6.00.Why change it all of a sudden and then change it back? FORMAT.EXE was actually FORMAT.COM in 6.22 as well as in the DOS version in Windows ME.Why use different PKLite versions all of a sudden, then move back to an older one? Correction: Win9x didn't use PKLite'd files at all. The binary version number is 0x06 0x16 (622), something that would have changed with a real compile of 6.30.COMMAND.COM, IO.SYS and MSDOS.SYS are bytewise identical with 6.22 except for the hexedit of the numbers from 6.22 to 6.30.Ver reports 6.22, MS always used unified version variables in DOS, so when it was set properly in the source it always reported the same version everywhere after compile.As OBattler above pointed out, this is indeed a hack and not a real beta.

Dos 6.22 download torrent