Hi, Bernd wrote about OSCHECK: > verrrrrrrrrry nice! however still not safe to SYS C: if a bootsector is > analysed but contains a strange name. > Say, a KERNEL2.SYS.
I thought about "scan for *.SYS / *.COM in boot sector" but then I dropped the idea because I only wanted to protect the innocent, not the witty :-). Browsing the whole root directory seems to be more work than searching for "SYS with 8 uppercase ASCII chars in front of it" and "COM with 8 ...". Anyway, if you really want to break things, you can still call your kernel SHOOTMYF.OOT and then the heuristics will still fail. Intended use of OSCHECK: - first run WHICHFAT to detect CDROM/network drives - then run OSCHECK to detect the categories: 1. FreeDOS 2. MetaKern 3. MSDOS/"WinDOS" 4. PCDOS/DRDOS - finally use the boot sector backup and create a boot menu if category 3 or 4 detected (or use boot.ini after attrib -everything boot.ini if WinNT class system and boot.ini file detected), assume that the system is already bootable if category 2 detected and "just do SYS" for category 1. The current version already detects 99% of the cases so it drastically helps installer scripts to protect people from shooting into their own (Win-on-C:) foot. Eric ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click _______________________________________________ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
