jaclaz Posted October 2, 2018 Share Posted October 2, 2018 13 hours ago, MERCURY127 said: I not think that installer use fdisk for write mbr... Which is good, so that or similar sequence of bytes is likely to be *in some other file*, as said (check point #3 above). The technique used to store the sequence of bytes is very likely to be similar. jaclaz Link to comment Share on other sites More sharing options...
MERCURY127 Posted October 2, 2018 Author Share Posted October 2, 2018 solved. D:\IF1808>fc /b SUWIN.0 SUWIN.EXE Сравнение файлов SUWIN.0 и SUWIN.EXE 0001F46E: 75 EB 0001F4CA: 74 EB WARNING: possible obvious side effects... Link to comment Share on other sites More sharing options...
jaclaz Posted October 2, 2018 Share Posted October 2, 2018 (edited) Good. In the meantime I checked (only out of curiosity) with gsar the expanded contents of the first files on win98 SE install (up to base4.cab) and besides the matches (9) in FDISK.EXE, there is ONLY a match for SUWIN.EXE: suwin.exe: 0xe6c2 suwin.exe: 1 match found and there the MBR is in its "expanded" 512 bytes form (though still missing the error messages) between a copy of the FAT12 (/16) and a copy of the FAT32 bootsectors. The error messages are a little past that at 0xEEDF in the form of strings "queerly" separated by Hex 24 character . jaclaz Edited October 2, 2018 by jaclaz Link to comment Share on other sites More sharing options...
rloew Posted October 3, 2018 Share Posted October 3, 2018 12 hours ago, jaclaz said: The error messages are a little past that at 0xEEDF in the form of strings "queerly" separated by Hex 24 character The Hex 24 '$' characters are the end of string delimiter used by DOS Calls such as INT 2109. Link to comment Share on other sites More sharing options...
jaclaz Posted October 3, 2018 Share Posted October 3, 2018 8 hours ago, rloew said: The Hex 24 '$' characters are the end of string delimiter used by DOS Calls such as INT 2109. Yep , but it remains "queer" because usually in MS programs (including FDISK) the strings are 00 terminated, in FDISK, there is - besides the 00 separator - a field for length of the string, as described by the given link, which - while being different from "normal" C programs string storage - makes (to me at least) more sense as this "length" field most probably simplifies the command used to write it. jaclaz Link to comment Share on other sites More sharing options...
jaclaz Posted October 4, 2018 Share Posted October 4, 2018 (edited) I pinged Daniel B.Sedory (The Starman) about the topic and he plans to make a page similar to : https://thestarman.pcministry.com/asm/mbr/WTC.htm but related to "where is the code" in 9x. For the moment he quickly checked a few more files and found another other copy of the MBR code in OEMSETUP.EXE. While the files tffsprop.dll and tformat.exe contain a copy of the "Standard" (since MS-DOS 3.30 and up to 95 A) MBR code: http://starman.vertcomp.com/asm/mbr/STDMBR.htm jaclaz Edited October 7, 2018 by jaclaz Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now