Thanks Pete. I guess I still have the old thought path of OS2. Sometimes still think of OS2 being the primary and not eCS. Sometimes I am in a slight fog over troubleshooting eCS/OS2. That is probably because I really never have to trouble shoot it because it normally runs, runs and runs without incident...
Heya Blue Warper. I guess the ".;" in front is what is suppose to happen normally for LIBPATH. If it was in front, this issue would not have happened. But that is OK, and I know the is a method to why eCS install set that up differently. This was a fresh eCS v1.2R from the GA install CD. So I am sure that the current LIBPATH was created from the install process. The eCS paths are in front of the ".;". A few more minutes and maybe hours of thinking time I might have come up with the idea of the ".;" solution for LIBPATH. I have those troubleshooting thought paths way back in my brain from the days of DOS, Warp3, Windows 286, etc... LOL Kinda of a trip down memory lane. Thank you. I am also deleting the copy of WPIRTL.DLL from c:\ecs\dll and renaming back the original (Doing this all just to maintain original file placement integrity). Then placing the".;" in the front of all in LIBPATH, as you mentioned, and as I now recall, that this is where traditionally and program lib seeks make the best sense.
Thanks Warpcafe, I had forgotten about POPUPLOG.OS2. More troubleshooting forgetfulness. Your suggestion made things move in the right direction very quickly.
Also thanks to Radek. You gave me the the right direction of looking hard at WPIRTL.DLL and where it was in the folders and searched out in LIBPATH.
I, just because I really do care about eCS and v2, ran through the saved archive of RC6 and found the WPIRTL.DLL is only found in c:\ecs\install\warpin. AWESOME! All the external referenced LIBC*.DLL and GCC*.DLL are stored in c:\ecs\dll and not in c:\ecs\dll. AWESOME! I now made a permanent update in my own head about runtime dll placement to be in c:\ecs\dll! A mention of ".;" in the base install of eCSv2RC6. It is not in the starting position. This must be intentional, right?
THANK YOU ALL FOR YOUR ASSISTANCE! MAY OUR OS LIVE FOREVER!
Best regards,
Todd
Heya Blue Warper. I guess the ".;" in front is what is suppose to happen normally for LIBPATH. If it was in front, this issue would not have happened. But that is OK, and I know the is a method to why eCS install set that up differently. This was a fresh eCS v1.2R from the GA install CD. So I am sure that the current LIBPATH was created from the install process. The eCS paths are in front of the ".;". A few more minutes and maybe hours of thinking time I might have come up with the idea of the ".;" solution for LIBPATH. I have those troubleshooting thought paths way back in my brain from the days of DOS, Warp3, Windows 286, etc... LOL Kinda of a trip down memory lane. Thank you. I am also deleting the copy of WPIRTL.DLL from c:\ecs\dll and renaming back the original (Doing this all just to maintain original file placement integrity). Then placing the".;" in the front of all in LIBPATH, as you mentioned, and as I now recall, that this is where traditionally and program lib seeks make the best sense.
Thanks Warpcafe, I had forgotten about POPUPLOG.OS2. More troubleshooting forgetfulness. Your suggestion made things move in the right direction very quickly.
Also thanks to Radek. You gave me the the right direction of looking hard at WPIRTL.DLL and where it was in the folders and searched out in LIBPATH.
I, just because I really do care about eCS and v2, ran through the saved archive of RC6 and found the WPIRTL.DLL is only found in c:\ecs\install\warpin. AWESOME! All the external referenced LIBC*.DLL and GCC*.DLL are stored in c:\ecs\dll and not in c:\ecs\dll. AWESOME! I now made a permanent update in my own head about runtime dll placement to be in c:\ecs\dll! A mention of ".;" in the base install of eCSv2RC6. It is not in the starting position. This must be intentional, right?
THANK YOU ALL FOR YOUR ASSISTANCE! MAY OUR OS LIVE FOREVER!
Best regards,
Todd