I work a lot with various flavours of systems. Many use FAT12 floppies, especially of course DOS machines like IBM PCs and IBM PS/2s, all OS/2 and NT (including RISC) machines, NEC, even DEC Alphas rely on them for booting. Additionally, FAT12 is a widely supported exchange FS on IBM formatted floppies.
Issue
Originally there were MS-DOS floppies but Disk-o-Matic presents them with a strong Atari branding, because besides all those systems, Atari ST uses them, too ;) I see Disk Jockey doesn't yet support all the other systems, but I guess at some point there will be a PC-style support, since that incorporates too many interesting SCSI machines.
Some resolution ideas
Check the file extension: Non-Atari floppies never use the ".st" extension 😁
Check the OEM string in the boot sector: It is set according to the OS while formatting, for example MSDOS5.0. Then present the image in an appropriate style.
Use a generic "FAT12", "IBM-style" or "DOS format" branding (following how back in the days you could buy 3.5" floppies either in "DOS" or "Macintosh" format) for all FAT12 images.
Situation
I work a lot with various flavours of systems. Many use FAT12 floppies, especially of course DOS machines like IBM PCs and IBM PS/2s, all OS/2 and NT (including RISC) machines, NEC, even DEC Alphas rely on them for booting. Additionally, FAT12 is a widely supported exchange FS on IBM formatted floppies.
Issue
Originally there were MS-DOS floppies but Disk-o-Matic presents them with a strong Atari branding, because besides all those systems, Atari ST uses them, too ;) I see Disk Jockey doesn't yet support all the other systems, but I guess at some point there will be a PC-style support, since that incorporates too many interesting SCSI machines.
Some resolution ideas
MSDOS5.0. Then present the image in an appropriate style.