Purchasing the book then going through the contents page and index for starters. It will pay for itself in a matter of hours."Īt the time of initial writing of this post, I could not find a softcopy of this book which means I had to do things the old-fashioned way when I comes to research. If you are going to program for Windows (3.1), buy this book. I purchased this book Programming Windows 3.1 by Charles Petzold from Amazon. Basically Windows 3.1, its API documentation and problems can’t be Googled easily, one has to rely on a more traditional method like books! Reference Book Typically, programmers will rely quite heavily on Google and Stackoverflow.Īlas, Win 3.1 only came during the dawn of the internet era and Google cannot help if relevant websites do not even exist. API DocumentationĪPI documentation and usage examples are very important when it comes to software development. I had to wade through many issues which I detail the following key ones. That’s many orders of magnitude smaller then the modern Slack app on the App store :P Let’s get down to the coding businessĬoding an ancient app presents some very unique challenges not seen when using modern toolchains and programming languages. That’s actually the first time I saw the network drive icon in File Manager. With Win 2K VM configured to use a bridged network and thus the same subnet, my native WFW 3.11 system can access the SMB share folder of the Win 2K VM as seen above. I can do intermediate testing on Win 2K since it can run 16-bit apps. VC++ 1.52 will access the source files using a mapped drive on SMB share and do the compilation. Primary development is done on the Mac with Visual Studio Code editor with the files residing on the Mac file system. Windows 10 and Mac cannot directly talk to the ancient SMB protocol used by WFW 3.11. We need to occasionally test our app on the actual ancient hardware with WFW 3.11 during development.Īlso, we can’t write our code directly on the Windows 2000 VM as it has limited software support for modern IDEs like Visual Studio Code not to mention security issues. Testing a 16-bit program on a 32-bit OS VM is not a very realistic scenario as VMs can be too perfect.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |