{"id":9516,"date":"2024-10-12T21:17:10","date_gmt":"2024-10-12T21:17:10","guid":{"rendered":"https:\/\/www.hexacorn.com\/blog\/?p=9516"},"modified":"2024-10-12T22:31:40","modified_gmt":"2024-10-12T22:31:40","slug":"the-sweet16-the-oldbin-lolbin-called-setup16-exe","status":"publish","type":"post","link":"https:\/\/www.hexacorn.com\/blog\/2024\/10\/12\/the-sweet16-the-oldbin-lolbin-called-setup16-exe\/","title":{"rendered":"The Sweet16 – the oldbin lolbin called setup16.exe"},"content":{"rendered":"\n

I don’t even know how to start. I wrote about old InstallShield<\/a> setup before, and today’s topic is very similar – the old, yet still present setup file residing (on Win10, 11) in the following location:<\/p>\n\n\n\n

c:\\windows\\SysWOW64\\setup16.exe<\/pre>\n\n\n\n
Running it gives us this misleading message box #1:<\/p>\n\n\n\n
\"\"<\/a><\/figure>\n\n\n\n
After quick study of setup16.exe code I was able to determine what command line arguments it needed and then craft a simple example LST config to act as my setup file.<\/p>\n\n\n\n
The program accepts the switch -m that allows us to pass a name of an alternative LST file to it, so we can run a command like this:<\/p>\n\n\n\n
c:\\windows\\SysWOW64\\setup16.exe -m c:\\test\\test.lst<\/pre>\n\n\n\n
Creating a dummy file c:\\test\\test.lst and running the test we get this misleading message box #2:<\/p>\n\n\n\n
\"\"<\/a><\/figure>\n\n\n\n
After analyzing the code a bit more and then looking at some very old examples of LST files that can be found online I was able to quickly create a test file that worked…<\/p>\n\n\n\n
Additionally, I discovered that we can use -QT argument to run the program in a QUIET mode (no dialog box, no error messages).<\/p>\n\n\n\n
c:\\windows\\SysWOW64\\setup16.exe -m c:\\test\\test.lst -QT<\/pre>\n\n\n\n
This is the first working LST I have created:<\/p>\n\n\n\n