Differences

This shows you the differences between two versions of the page.

--- jas:jas_dlls [2025/01/17 17:12] – [2025 01 17] 63.135.161.154
+++ jas:jas_dlls [2025/01/30 22:27] (current) – [2025 01 30] 216.73.161.101
@@ Line 2: / Line 2: @@
 ====== Jas dlls ======
+===== 2025 01 30 =====
+  * the image I have been working with has been 64 bits all along, so I wasted my time trying to recreate a 32 bit dll using vs 2015
+  * I was once able to read pamresources.dll with this image, but I can no longer do so.
+  * I thought I corrupted the original dlls.icx, so I created dlls2 and dlls3 images
+  * neither one works even if I run just once after importing the needed maps.
+  * I mis-spelled aModuleName := 'pamRebbbsources.dll' and dlls.ws still ran to completion.
+  * I renamed pamresouces.dll to pamXXXresources.dll in the progFiles *x64) directy and dlls.ws still ran
+  * class variable iconCache in PamIcon starts off as and empty LookupTable.
+  * To do: run dlls.ws in a good Jas Dev JSO x86 image.
+===== 2025 01 28 =====
+  * used res hacker to dump contents of the good pamresources.dll to pamresources.rc
+  * edited pamresources.rc and commented out the first line about LANGUAGE
+  * following this https://www.codeproject.com/Tips/5349617/Creating-a-Resource-Only-DLL
+  * created a new project that is a dll and an empty project. saved it.
+  * add - > existing item added pamresources.rc
+  * under Project -> propertied -> linker -> advanced chnnged entry point to NOENTRY
+  * build solution created a new win32project3.dll of size 168 kb that looks ok in Res Hacker
+  * but the good pamresources.dll is 245K.
+  * the dlls.ws not longer works. I think I toasted my image.
+  * TO DO: use a jas open image and force a reload of the dll.
+  * modify PamHolder class>>loadModuleNamed: aModuleName notifyWindow: aWindow
+===== 2025 01 23 =====
+  * Several days of trying to get VS 2022 to do anything dll got nowhere.
+  * Downloaded and installed VS 2025 which has a simpler interface and some Internet help I found.
+  * Both VS installs take hours with no visual updates.
+  * But VS 2015 does not display some of the screens necessary to create a project. I suspect this is a Win 11 problem, The solution is a Win 7 or a Win 8 machine which could be used in the future.
+  * VS 2015 would not install on Chuck's Vista machine. Vista is between XP and 7.
+  * VS 2015 did install on my Lenovo with Win 8.1.
+  * VS 2015 needs two files documented in picture vs2015.png in C:\Users\donald\Pictures\000craigslist.
+  * created a pamresources.dll using VS 2015 and the non-Smalltalk source code/pamresources.rc as input.
+  * The pamresource.dll created is NOT the same as the real on and it is NOT a resource dll. It has a menu!
+  * Todo: try decomposing the real pamresources.dll using res hacker and the using that .rc file and the icons in VS 2015.
 ===== 2025 01 17 =====
   * Res Hacker can save the contents of a dll to an .rc or .res file
+  * under action, selecting save all resources saves the icons as individual files and creates an .rc file like this: //1000 ICON "ICON1000_1.ico"//
+  * An .rc file is a Resource Script.
+  * dlls.ws will read the 89 icons in pamresource.dll of 2007 in an x86 image.
+  * dlls.ws does not read any icons in either the x86 or x64 dlls in an x64 image.
+  * The x64 pamresource.dll created by the z:jas code is NOT the same and it is NOT a resource dll. It has a **menu**!
+  * Try using the z:jas project in VS2022 on the icons and .rc files in \temp\jasDlls
 ===== 2025 01 16 =====
@@ Line 131: / Line 176: @@
   * 250+ bitmaps referenced by a 4 digit id starting at 1000.
   * a symbol to id table is in a pool dictionary in PamKernel class.
-  * Example: PamIcon fromModule 'pamResources.dll' id 1102.
+  * Example: PamIcon fromModule: 'pamResources.dll' id: 1102.
   * PamIconHolder class LoadModuleNamed:notify: does the load,
   * source at \jas\JSO\Non-Smalltalk Source Code\working_pam