Differences

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

--- jas:jas_dlls [2025/01/28 17:39] – [2025 01 28] 63.135.161.205
+++ 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 =====
@@ Line 11: / Line 22: @@
   * 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.
+  * 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 =====