F5F Stay Refreshed Software Operating Systems Experiment with MS-DOS 5.00

Experiment with MS-DOS 5.00

Experiment with MS-DOS 5.00

C
Chickenzinho
Member
69
01-08-2026, 05:00 AM
#1
Hey Guys, around 5 minutes ago i got to know that you can boot from a vhd,img,iso,etc using EasyBCD,im doing a project in which ive successfully been able to boot MSDOS Version 5.00,now my questing is,can i create a FAT16 Partition on my drive and have DOS 5 Detec it ( I dont want to wipe the drive and even if i could dos cannot used 120 GB)then go to my dos 5 entry of that fdd img i added and do fdisk and all that and do sys c: and have it work? Thanks
C
Chickenzinho
01-08-2026, 05:00 AM #1

Hey Guys, around 5 minutes ago i got to know that you can boot from a vhd,img,iso,etc using EasyBCD,im doing a project in which ive successfully been able to boot MSDOS Version 5.00,now my questing is,can i create a FAT16 Partition on my drive and have DOS 5 Detec it ( I dont want to wipe the drive and even if i could dos cannot used 120 GB)then go to my dos 5 entry of that fdd img i added and do fdisk and all that and do sys c: and have it work? Thanks

S
Spaceface16518
Senior Member
564
01-09-2026, 11:48 AM
#2
It's interesting to consider the value of MSDOS in today's context.
S
Spaceface16518
01-09-2026, 11:48 AM #2

It's interesting to consider the value of MSDOS in today's context.

B
BlazedScar
Member
156
01-09-2026, 07:37 PM
#3
I'm someone who enjoys using DOS applications and older Windows versions, even though I'm working on a C2D with a core 2 duo and an SSD. It's better for real hardware than emulation, so the story is, I made a 2 GB partition and used fdisk in dos 5.6.22. It doesn't seem to recognize it. Now in Neosmat EasyBCD I need to indicate where my DOS partition is located, but it says it will find it automatically. I don’t have a choice. Also, specifying the drive in the advanced options doesn’t help—I often end up in a grub loader, which is similar to command.com. If you can help, that would be really appreciated.
B
BlazedScar
01-09-2026, 07:37 PM #3

I'm someone who enjoys using DOS applications and older Windows versions, even though I'm working on a C2D with a core 2 duo and an SSD. It's better for real hardware than emulation, so the story is, I made a 2 GB partition and used fdisk in dos 5.6.22. It doesn't seem to recognize it. Now in Neosmat EasyBCD I need to indicate where my DOS partition is located, but it says it will find it automatically. I don’t have a choice. Also, specifying the drive in the advanced options doesn’t help—I often end up in a grub loader, which is similar to command.com. If you can help, that would be really appreciated.

L
Luckaz
Member
50
01-17-2026, 10:51 AM
#4
Reminds me of my TRS-80 Model 1, Level 2 with the 8-inch floppy disk. Hmm, or maybe the Commodore 128? Either way, good luck with what you're dealing with. I can't recall the specifics from that time. Thanks.
L
Luckaz
01-17-2026, 10:51 AM #4

Reminds me of my TRS-80 Model 1, Level 2 with the 8-inch floppy disk. Hmm, or maybe the Commodore 128? Either way, good luck with what you're dealing with. I can't recall the specifics from that time. Thanks.

A
AliasFish
Junior Member
40
01-18-2026, 10:29 PM
#5
Yes, I understand what the default DOS label refers to. It's typically the starting point or entry point in a DOS program or system.
A
AliasFish
01-18-2026, 10:29 PM #5

Yes, I understand what the default DOS label refers to. It's typically the starting point or entry point in a DOS program or system.

I
IpSenKo
Member
61
01-18-2026, 11:54 PM
#6
MSDOS worked with a "master boot record" or MBR. I recall that older versions wouldn’t recognize a 2 gigabyte partition, though I’m not certain. There was no FAT32 file system—only FAT16. I remember needing to perform a low-level format, but it’s unclear whether this happened before or after using "FDISK." It seems the drive started as Drive C: because both A and B letters were reserved for floppies. The process didn’t seem straightforward, and opening a DOS environment inside Windows might have helped. I also tried that a few years ago with old games stored in the garage, but they just failed to boot. Good luck with your project!
I
IpSenKo
01-18-2026, 11:54 PM #6

MSDOS worked with a "master boot record" or MBR. I recall that older versions wouldn’t recognize a 2 gigabyte partition, though I’m not certain. There was no FAT32 file system—only FAT16. I remember needing to perform a low-level format, but it’s unclear whether this happened before or after using "FDISK." It seems the drive started as Drive C: because both A and B letters were reserved for floppies. The process didn’t seem straightforward, and opening a DOS environment inside Windows might have helped. I also tried that a few years ago with old games stored in the garage, but they just failed to boot. Good luck with your project!

E
ElLokito0324
Member
178
01-23-2026, 03:46 PM
#7
I’ve gathered some insights from my experience with retro DOS gaming. On today’s systems, using a virtual machine is often better than running DOS on a real partition. Here are the key points: FDISK is the tool for creating partitions in DOS. You don’t just create a partition and then use FDISK—you start with FDISK to make partitions, then format them. Most modern systems can’t run MBR, which was used until Windows XP; newer drives usually use GPT partitions. Windows XP didn’t include a boot manager that supports multiple OSes, so you’d need work arounds like separate hard drives and BIOS boot menus. Running DOS 6 or 7 might be more practical because they support FAT32, which is useful for older games and software. If you’re on very old hardware, it’s worth giving it a try, but unless you have genuine DOS hardware, a VM would be a better choice.
E
ElLokito0324
01-23-2026, 03:46 PM #7

I’ve gathered some insights from my experience with retro DOS gaming. On today’s systems, using a virtual machine is often better than running DOS on a real partition. Here are the key points: FDISK is the tool for creating partitions in DOS. You don’t just create a partition and then use FDISK—you start with FDISK to make partitions, then format them. Most modern systems can’t run MBR, which was used until Windows XP; newer drives usually use GPT partitions. Windows XP didn’t include a boot manager that supports multiple OSes, so you’d need work arounds like separate hard drives and BIOS boot menus. Running DOS 6 or 7 might be more practical because they support FAT32, which is useful for older games and software. If you’re on very old hardware, it’s worth giving it a try, but unless you have genuine DOS hardware, a VM would be a better choice.