UPDATED · 7-23-2008
Enjoy.
_____________________________________
RetroOS:
CRYPTME.EXE = only for WinME
CRYPT9X.EXE = for all other Win9x editions: 95, 95a, 95B, 95C, 98, 98 SP1 + 98 SE(U) except WinME
Must not install CRYPT9X on WinME nor CRYPTME on Win9x!
Cryptology/SSL files are strictly meant for a specific OS.
98SE2ME has nothing to do with cryptology.
Crypt/SLL files are installed by default by MS IE (Internet Explorer) 4.x/5.x/6.x [or separately = (hot)fixes], and used by MS IE + MS OE (Outlook Express):
http://www.mdgx.com/ietoy.htm#HEP_____________________________________
erpdude8:
About your request to add a REG file into GRPHFLTS.EXE to comply with Win95 OSes limitation of not properly recognizing the DWORD string in INF files [0x00010001]:
IMHO:
About the REG_DWORD / REG_BINARY interpretation by Win95 OSes:
As long as a reg value is in hex format [not string = ASCII (REG_SZ)], it doesn't matter if it is DWORD or BINARY, because Win9x [all editions: 95, 98, ME] interprets it the same.
This is valid, of course, only for hex values 1 to 4 bytes (8 to 32 bits) long [00000000 = in DWORD format or 00,00,00,00 = in BINARY format].
Hex values longer than 4 bytes are supposed to be interpreted automatically as BINARY, because DWORD values can be only 1 to 4 bytes long [max length].
The only difference between the DWORD and BINARY formats is that the value sequence is coded backwards. Example:
"ValueName"=dword:01020304
"ValueName"=hex:04,03,02,01
which means the 4 groups of bytes are arranged backwards, but essentially the reg value is identical. This interpretation is internal to the OS [and transparent to the user], so it should not influence the format the registry values are implemented in, as long as a hex value doesn't go over 4 bytes in length.
More details [see REG_DWORD + REG_BINARY]:
http://www.mdgx.com/reg.htm#RTSExample [see Hex + Dword values = both work the same]:
http://www.mdgx.com/newtip6.htm#CDMAXHTH