Dos 6.22 Iso

[Tiffany Crutch]

Imlooking to buy Dos and its hard to find and I would like to use something like 6.22 so it will be the most compatible for dos gaming and an SC55 for midi music that will run on a P2 500MHz CPU and a AWE64 and I have the chance to get 6.2 but I would like to know the main differences between Dos 6.2 and Dos 6.22 or does someone here in this forum have a 6.22 version that I can buy from them? I havnt used freedos yet but that is something im not interested in as my Dos PC is built fully retro and im trying to keep it that way

Yes, it was because of Double Space / Drive Space. 6.20 came with Double Space. MS was sued by the maker of Stacker because of it. 6.21 then came with no disk compression at all. Finally, 6.22 had Drive Space instead, which was basically Double Space but now with licenced code usage.

On a P2 I would go with the dos that ships with Win9x myself.

OK, its not the FULL dos OS but its only missing tools that you'll never use like disk compression, Anti virus, etc, Things that a dos gamming PC doesn't need anyway.

Plus you get Fat32 support, Remember Dos6.x is limited to 2GB partitions, bit of a pain on a 8GB or larger HDD.

I have a boot disk from 98se could I copy that to the root of my C: formatted as Fat32 and then make a folder called ? Eg command or programs and copy all the files from C:\Windows\Command like the way derSammler said im just running games I have no need for anything else and would version of dos would it be 7.1?

Basically, yes. Boot from that disk, do a format c: /s, copy command.com to c:\, and the rest to e.g. c:\dos. However, to have all DOS files, you need the OLDMSDOS folder from the Windows 9x CD and the files from c:\Windows\Command of an installed Win9x. You may also just extract the latter from the cab file.

I am aroused about any X86 motherboard that has full functional ISA slot. I think i have problem. Not really into that original (Turbo) XT,286,386 and CGA/EGA stuff. So just a DOS nut.

PS. If I upload RAR, it is a 16-bit DOS RAR Version 2.50.

Before I get into specs and everything else pertaining my PC, what could possibly cause DOS 6.22 to only detect 15mb out of all the available ram memory which amounts to a massive (for a retro rig) 1024mb?

I know DOS software has it hard detecting high-end single-core CPU's, and perhaps it's mistaken mine for one of those ancient CPU's whose architecture couldn't handle more than 15mb's, or perhaps it's merely a bad combination of memory settings.

DOS 6.22 has a 64mb memory limitation, so even if you manage to get your problem solved, 6.22 is still not going to allow you to use all your memory. Later versions may ease the memory limitation but I'm not sure if they will go all the way to 1gb. DOS may also be having issues with your CPU. I know Windows 95 and 98 have issues with CPU's above 2.0 ghz so DOS may have a similar problem. The problem for Windows 95/98 was fixed with a patch (which you have to hunt for because I don't think Microsoft has it for download anymore) but I don't think they would have bothered to fix DOS.

It's worth noting that advanced memory managers such as QEMM may detect the whole thing and address as much as 256mb, but somehow they tend to break compatibility with certain games and I don't have time to go through a crapload of settings to locate the offender.

The reason you only see 15Mb it extended you forgot take in count of 1Mb conventional and upper memory equals 16Mb

Sound like you don't have something config rigth

You know MS-DOS 7.10 will recognize much more memory than 64MB and so will FreeDOS

As for QEMM you want 7.5 and is 256Mb limitation from what I recall

OP needs an XMS driver. XMS2 can see 64mb (himem.sys from msdos 6.22). XMS3 can see all (himem.sys from later versions of win9x). it is the dos apps that cannot see it so you need to use a virtual ramdisk to make use of the rest of ram. that's how i understood it back then.

Make sure it one from Win98 Second Edition and not Win98 Gold Edition

Also make sure you disable OS/2 64MB option set it to NoN-OS2 this know cuases problem as well

As sklawz point out some bios motherboard may have this option know as Memory hole at 15-16 MB you should disable it and if your motherboard has no ISA you will bot see that option.

The one you want himem.sys, 33191

It gose like this

Windows 95

Windows 95A with Service Pack 1 or as OSR 1.0

Windows 95B OSR 2.0

Windows 95B OSR 2.1 with USB Supplement

Windows 95C OSR 2.5 with USB Supplement and IE4

OSR = OEM Service Release

Windows 98 First Edition aka Gold

Windows 98 Second Edition aka SE

Windows Millennium Edition aka ME

There are 4 ver Microsoft Plus! = 95, 98, Kids and Game Pack

I was beta tester for ever one of ver above even WinNT4, WinNT5 aka Windows 200 and Windows XP

I hated ME and drop out of Vista half done I didn't want deal with carp agine like ME boy I was rigth Vista was a major failer.

Ok, I finally got around replacing himem.sys and it worked beautifully ? Not sure how much it actually managed to allocate, but the ancient mem.com reports about 68mb, which's more than enough anyways.

Our office recently received a new Voss machine, and the base pc attached to it needs some configuration work before we can connect it to the network and do all the updates and downloads it needs to work correctly. Usually, this would be no problem for me, except that this machine came with ONLY DOS 6.22. The information I need is How I can get this network card that is built into this machine attached to the system and working so that it will work with my network.

I had an idea that it might need drivers, but I am not sure how to get the system to read the flash drive ports on the front of the machine to read a flash drive with drivers on it, or even if it will since it is not a windows system.

I extracted the driver onto the disk this time, and now I have the PRO1000 and PRO100 directories. I am assuming that since this is a gigbit adapter that I should use the PRO1000 directory, however, there are a bunch of MS-DOS apps inside this directory and I am not sure which one to run.

Our office recently received a new Voss machine, and the base pc attached to it needs some configuration work before we can connect it to the network and do all the updates and downloads it needs to work correctly.

Hi all,

I have been trying to build root 6.22 from source file by following instructions on _from_source/. I tried including python2 and python3 also. When I am building using cmake, I get this error. Can you please help?

My CMOS setup correctly recognizes the geometry of the drive, (but does not support LBA). And FDISK in DOS 6.22 only recognizes 504MB. FDISK even shows the size of the primary partition as roughly 1GB out of a possible 504MB.

An alternative is to use IBM PC DOS 7.1 instead. This is the last ever member of the MS-DOS family. It includes native built-in FAT32 and LBA drive support. IBM made it available as a free download -- I describe this here: -on-linux.livejournal.com/59703.html

You will need to supply the rest of PC DOS 7.01 (also known as PC DOS 2000) to make a complete OS, but that is widely available; for example it came free with Microsoft VirtualPC, which itself is a free download now.

MS-DOS 6.22 only uses CHS (cylinder/head/sector) addressing to access disks, so it doesn't really matter if the BIOS supports LBA addressing. The CHS BIOS access method is also known as INT 13h, not to be confused with extended INT 13h which uses 64-bit addressing. The CHS BIOS interfaces MS-DOS uses for disk access supports drives up to just under 8 GiB, so this also about the limit for MS-DOS. (A bug in MS-DOS means that it crashes if a drive has 256 heads, so its limit is a bit smaller than the BIOS limit but still almost 8GB.)

The limit you've encountered is due to the intersection of the BIOS and IDE limits on CHS addressing being much less than either individually. The BIOS supports addressing up to 1024 cylinders, 256 heads and 63 sectors, while IDE supports up to 65536 cylinders, 16 heads and 255 sectors. Taking the minima of these three pairs (1024 16 63) gives you the 504 MiB limit.

To get around the 504 MiB limit many BIOSes supported CHS translation, where they converted BIOS CHS addresses to IDE CHS addresses using some sort of transformation. Apparently though your BIOS doesn't support this, otherwise the drive probably would've worked. You should check to see if your BIOS has some sort of "large" drive support you can enable.

If you're not booting off the hard drive then I think there were drivers for MS-DOS that performed CHS translation. According an old Microsoft KB article (KB126855) I found "SpeedStor from Storage Dimensions, EZ-Drive from Micro House, and Disk Manager from OnTrack Computer Systems" are possibilities. An IDE controller won't work unless it has its own boot ROM, one that can perform CHS translation.

I have MS-DOS 6.0 and the 6.22 upgrade from the MSDN subscriber downloads. In order to install the 6.22 upgrade, I have to install 6.0 first. The 6.22 download includes .IMG files from which I can boot, but the 6.0 download does not. I tried creating a bootable .ISO image from the 6.0 files, but that didn't work.

You need to FDISK and Format the C: drive. Then you can use the SYS command to transfer the system files to C:. After all this, run the 6.22 install again and you should no longer get the upgrade warning.

The installer called by autoexec.bat is busetup.exe, which will check the existence of installed DOS in the hard drive and reject installation if it is absent.Therefore, you need to run another installer, setup.exe. Boot with Disk 1 and rapidly press F5 when the "Starting MS-DOS..." message appears to skip autoexec.bat. Then manually run setup.exe. This allows for a fresh installation.

3a8082e126