11/14/2022 0 Comments Rufus ms dos 6.22 iso![]() Regarding the read-only thing, I looked into it today, and from what I can tell, those in the industry tend to also run the legacy programs using ISOs from bootable USBs, so it doesn't look like that issue will introduce any problem. Is this not the case?Īs I said on the other thread, I don't think the multibooting will be a problem, as unlike with the DOS version, there's nothing to really suggest that multibooting will introduce any new problems. I extend the same question to you - what's meant by FAT32 support? My USB is FAT32, and I always assumed that if I get to the point where DOS 6.22 boots successfully from it, then compatibility isn't the issue. MS-DOS 7.0 onwards can access you have to run a specific version of MS-DOS to run legacy programs on very expensive hardware, then surely you can afford to have a DEDICATED DOS ONLY USB stick. Is there a specific process involved in creating a bootable DOS image from files? Am I missing something? I even experimented with making it bootable from within ImgBurn, using the original ISO as the boot file, but still couldn't get it working. I tried doing it today - I extracted all the files from the original DOS 6.22 ISO, and used ImgBurn to write those files as well as the legacy executables into a new ISO. This is why I currently prefer using WinSetupFromUSB, which boots by default into grub4DOS resulting in a simple but good-looking boot menu from the outset.Īs for the final method, at this point that definitely seems like the more attractive, easiest option. I tried E2B when initially trying to set this up, but I'm not fond of the E2B boot menu and found that it added way too many nested menus and menu items for me that would take a while to customise to my heart's content. Does the USB need to formatted as FAT16 just to see the legacy program files on the USB? I always assumed that if it runs on the USB that it should also be read files from it? The USB is definitely formatted as FAT32, and as mentioned, boots fine. It is possible to use a ramdisk (but then the whole stuff would be "volatile" ) or mount another volume (with a RW filesystem that MSDOS 6.22 can understand, which must then be ether FAT12 or FAT16) but it would be more complex and possibly (it really depends on the software) it may not work as that would be another (non-C:\ ) drive letter (there are possible workarounds/solutions to this issue, but they represent a further complication). iso is read only) and surely your software needs to save some info somewhere. iso is not usually a good idea (because the. DOS 7.1, but you can use the same with DOS and particularly DOS 6.22 as long as you use FAT16 and a disk size in the given range). You should make the RAW image larger than around 512 Mb (but not larger than 2 Gb) to make sure that both the BIOS of the VM and the real hardware detect the geometry as 255/63.įor a complete set of instructions (they are about FreeDOS and/or Windows 98, i.e. How exactly to do that is another thing, what I would personally ddo would be to make a "normal" install of the DOS into a VM (actually a specific one, the QEMU) on an image of suitable size and then dd the image to the USB stick. ![]() Try making a plain, partitioned, FAT16, non-multiboot USB stick with MS-DOS 6.22 and your software (and nothing else). Mind you there is no known reason to assume that the multibooting may EVER lead to any kind of "corruption" of the environment, but if you cannot risk to test the software with a newer DOS version, then you shouldn't risk (even if it is a little/tiny risk) that. MS-DOS 7.0 7.1 (aka Windows 95 OSR2) onwards can access you have to run a specific version of MS-DOS to run legacy programs on very expensive hardware, then surely you can afford to have a DEDICATED DOS ONLY USB stick. ISODOS, drive B: will contain your executables under MS-DOS and you can run from a FAT32 or NTFS USB drive.Įdited by steve6375, 16 July 2017 - 09:21 AM. You would need a DOS 7.1 ISO and a FAT32 USB drive.Īnother way would be to add you executables, etc. isodos file extension.Įdit - MS-DOS 6.22 does not support FAT32. However, if you want to run executables from the USB drive using your DOS 6.22 ISO, you will need to use the Make_E2B_USB_Drive.cmd button to make a FAT32 USB drive, then add your Windows and DOS ISOs by copying them over. It already contains a FreeDos menu entry which will allow you to boot to FreeDOS and run files on an NTFS or FAT32 USB drive. ![]() ![]() I am not sure that WinSetupFromUSB makes the USB drive visible as a BIOS drive - if you run FDISK when booted to DOS, can you see the USB drive listed by FDISK? If not then you may have to tweak the grub4dos menu for the DOS ISO.Įasy2Boot will do what you want easily (one menu and access to USB drive). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |