4 ms·
Yeah win16 had AllocCStoDS and AllocDStoCS, one was documented the other wasn't. They also had the fabulously named PrestoChangoSelector which toggled the code/
by pacaro 5y ago
Yeah win16 had AllocCStoDS and AllocDStoCS, one was documented the other wasn't. They also had the fabulously named PrestoChangoSelector which toggled the code/data bit in the descriptor table
- throwaway2037 5y agoCool. I did some Google searching about PrestoChangoSelector and I found this: KnowledgeBase Archive An Archive of Early Microsoft KnowledgeBase Articles Q89560: Creating Dynamic Code Segments Using PrestoChangoSelector https://jeffpar.github.io/kbarchive/kb/089/Q89560/ https://jeffpar.github.io/kbarchive/kb/089/Q89560/
- bonzini 5y agoIIRC there was a documented ChangeSelector function that was actually not implemented, so you had to use the undocumented PrestoChangoSelector instead. Visual Basic used it to implement a direct threaded code interpreter. Some other functions had similarly great names: >>Anyway, I am not sure what type of person writes a function called "BozosLiveHere" and puts it into USER.EXE >This started out life with a non-bozo name as an undocumented function in Windows 3.0. >Windows 3.1 removed the undocumented function, but we found that some programs were using the undocumented function and started crashing. >So we reluctantly put the function back, but changed its name to "BozosLiveHere" so that nobody else would use it in the future. >A similar story exists for "TabTheTextOutForWimps".