Hi, On Fri, Jul 5, 2013 at 11:01 AM, Bertho Grandpied <[email protected]> wrote: > > Steve Nickolas <usotsuki@bu...> wrote, on 2013-07-05 15:04 > >> http://www.ctyme.com/intr/rb-2711.htm > >> FreeDOS returns an OEM ID of 0xFD, which is distinct from other >> DOS implementations. > > I grasp it you mean the OEM code in BH from int 21/3000. > It is the first idea that jumps to mind, but > > *Is this really truthful in FreeDOS ?*
A quick check under DOSEMU does return 0xFD in BH (though I'm running latest kernel 2041 there). > Further, DOS "truever" 3306 function does not return an OEM ID, > does it? Apparently no. http://www.delorie.com/djgpp/doc/rbinter/id/41/27.html > I'd rather trust a FreeDOS-specific function which returned > the FreeDOS kernel version (as, e.g, 1.1) rather than a > function which pretends to be DOS 7.10, for a start ! There are some misbehaving programs out there (e.g. only enabling LFNs if 7.x is detected). Also, 7.x usually means FAT32 support (EDIT: and in the FAT16-only kernels, I think default version is 6.22). You can change the default in CONFIG.SYS with "VERSION=x.xx" or use the CALLVER util. http://ftp.ibiblio.org/pub/micro/pc-stuff/freedos/files/util/system/callver/ You can also check the FreeDOS kernel version with int 21h, 33FFh (returns DX:AX as pointer to version string). P.S. Even DR-DOS 7 lies for compatibility reasons, e.g. pretends to be IBM PC-DOS 6. So you have to call a separate function (int 21h, 4452h, aka "DR") to know for sure. http://www.delorie.com/djgpp/doc/rbinter/id/32/29.html ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ Freedos-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-devel
