• Welcome to OS2World OLD-STATIC-BACKUP Forum.
 

News:

This is an old OS2World backup forum for reference only. IT IS READ ONLY!!!

If you need help with OS/2 - eComStation visit http://www.os2world.com/forum

Main Menu

Fresh v1.2R install can not install lucide or others...

Started by NNYITGuy, 2009.04.24, 07:42:16

Previous topic - Next topic

NNYITGuy

Hello,

I just built a fresh v1.2R install.  I then downloaded and copied the runtime for libc into the os2/dll folder. and for good measure rebooted the system.  The WarpIn.exe from WarpIn Install/Remove folder does not execute.  I tried to install the Lucide v1.2 but the installer never started to the desktop.  I did install, before all of this WarpIn v1.0.17 to be current on WarpIn.

This is not my first day at the county fair.  I just can not find my problem.  I included the set statements from the config.sys and a dir of libc*.* items in the os2/dll folder.  Any hints? I thought at one time I found in the libc archives that a v6??? file was corrupted in one of the zip files.  I checked what I thought I remembered.  Please help...

Thank you,
Todd Simpson

------------------------------------------------------
REM [6] PATH STATEMENTS
LIBPATH=C:\PROGRAMS\RSJCD;C:\PROGRAMS\NETSCAPE\PROGRAM;C:\ECS\DLL;.;C:\OS2\DLL;C:\IBMGSK50\LIB;C:\IBMGSK40\LIB;C:\IBMGSK\LIB;C:\MPTN\DLL;C:\TCPIP\DLL;C:\IBMCOM\DLL;C:\OS2\MDOS;C:\;C:\OS2\APPS\DLL;C:\EMX\DLL;C:\JAVA11\DLL;C:\MMOS2\DLL;C:\MMOS2\FREEDB;
SET PATH=C:\PROGRAMS\NETSCAPE\PROGRAM;C:\ECS\BIN;C:\IBMGSK50\BIN;C:\IBMGSK40\BIN;C:\IBMGSK\BIN;C:\MPTN\BIN;C:\TCPIP\BIN;C:\IBMCOM;C:\OS2;C:\OS2\SYSTEM;C:\OS2\MDOS\WINOS2;C:\OS2\INSTALL;C:\;C:\OS2\MDOS;C:\OS2\APPS;C:\EMX\BIN;C:\JAVA11\BIN;C:\PROGRAMS\RSJCD;C:\MMOS2\FREEDB;C:\MMOS2;C:\MMOS2\MMPLAYER;
SET DPATH=C:\ECS\LANG;C:\MPTN;C:\IBMCOM;C:\OS2;C:\OS2\SYSTEM;C:\OS2\MDOS\WINOS2;C:\OS2\INSTALL;C:\;C:\OS2\BITMAP;C:\OS2\MDOS;C:\OS2\APPS;C:\MMOS2;C:\MMOS2\INSTALL;

------------------------------------------------------
[C:\os2\dll]dir libc*.*

The volume label in drive C is ECS-V1_2R.
The Volume Serial Number is 29E2:F015.
Directory of C:\os2\dll

4-14-04  4:37p       356,330      0 a---  libc05.dll
6-11-07 10:53p        48,142      0 a---  libc06.dll
6-11-07 10:53p        48,142      0 a---  libc061.dll
6-11-07 10:53p        48,142    225 a---  libc0611.dll
6-11-07 10:53p       157,124      0 a---  libc062.dll
6-11-07 10:53p     1,349,060      0 a---  libc063.dll
8-20-07  5:40a       957,123    226 a---  libc063x.dll
8-11-08  5:53a     1,353,252    226 a---  libc064x.dll
11-22-99 11:45a       210,916      0 a---  LIBCM.DLL
11-22-99 11:45a        57,340      0 a---  LIBCN.DLL
11-22-99 11:45a       192,386      0 a---  LIBCS.DLL
       11 file(s)   4,777,957 bytes used
                   20,884,542 K bytes free

[C:\os2\dll]
------------------------------------------------------
Todd J Simpson (IT Consultant)
Business Automation Technologies
(Professional Products and Services.  Business to Business...)

warpcafe

Hi Todd,

strange. Did you check if there is perhaps an entry added to popuplog.os2 on your boot drive whenever you launch Warpin? I could imagine a lot of possible causes, yet regarding the amount of pssible combinations of which-version-of-which-file... I think the best is to
- uninstall the current WarpIn (if possible)
- download the new WarpIn from scratch and re-install
- if that doesn't help, grab an "older" version of WarpIn and try the above

HTH, Cheers,
Thomas
"It is not worth an intelligent man's time to be in the majority.
By definition, there are already enough people to do that"
- G.H. Hardy

The Blue Warper

Hi, Todd!
Not sure about the cause of your problem.
This is just a minor post...

1) Current WarpIn version is 1.0.18 ( ftp://ftp.netlabs.org/pub/warpin/warpin-1-0-18.exe ), though I don't think this is what prevents you from starting the app(s).

2) Does this only happen with Lucide or with any WarpIn app?

3) One thing you could try is trying starting your app's executable from the command line.  It will fail, but you should be left with a more meaningful error message than just double-clicking and seeing nothing happening...  For example, if some file (mostly a dll) is missing (or if the app just can't find it, for whatever reason), an error message should be shown saying that the program cannot find file xxxxxxx.xyz

If I got any new ideas, I'll come back...  Good luck!

NNYITGuy

Thanks Guys,

Well, I guess I forgot about popuplog.os2.  The contents are the same as the below snippet, just replicated over and over and over... I just checked for dupes, just to possibly rule it out, of the WPIRTL.DLL and found two versions.  The first is in c:\ecs\dll and the second is in c:\ecs\install\warpin.  Maybe this has nothing to do with it. But, I thought I would check and get the info anyways.

Thank you and best regards,
Todd


------------------------------------------------------------
[C:\]dir wpirtl.dll /s /p

The volume label in drive C is ECS-V1_2R.
The Volume Serial Number is 29E2:F015.

Directory of C:\ecs\dll

1-28-04  4:14p       847,951      0 a---  WPIRTL.DLL
        1 file(s)     847,951 bytes used

Directory of C:\ecs\install\WarpIN

3-12-08  1:17a       815,521      0 a---  wpirtl.dll
        1 file(s)     815,521 bytes used
Total files listed:
        2 file(s)     1,663,472 bytes used
                   20,883,655 K bytes free

[C:\]
------------------------------------------------------------
------------------------------------------------------------
04-24-2009  08:14:04  SYS3175  PID 006f  TID 0001  Slot 009c
C:\ECS\INSTALL\WARPIN\WARPIN.EXE
c0000005
1e162b4b
P1=00000001  P2=00000047  P3=XXXXXXXX  P4=XXXXXXXX 
EAX=00150a68  EBX=00000000  ECX=00000027  EDX=1e163ed0
ESI=00000000  EDI=00000000 
DS=0053  DSACC=f0f3  DSLIM=ffffffff 
ES=0053  ESACC=f0f3  ESLIM=ffffffff 
FS=150b  FSACC=00f3  FSLIM=00000030
GS=0000  GSACC=****  GSLIM=********
CS:EIP=005b:1e162b4b  CSACC=f0df  CSLIM=ffffffff
SS:ESP=0053:0015092c  SSACC=f0f3  SSLIM=ffffffff
EBP=0015097c  FLG=00012206

WPIRTL.DLL 0001:00022b4b
------------------------------------------------------------
Todd J Simpson (IT Consultant)
Business Automation Technologies
(Professional Products and Services.  Business to Business...)

Radek

The one which caused the crash is the "uppercased" one (it has been found on your LIBPATH first) - unless DosLoadModule() has specified the full path of course. The uppercased WPIRTL is from 2004, while the lowercased WPIRTL is from 2008. The DLLs are different, therefore, try to put the lowercased WPIRTL in c:\ecs\dll .

NNYITGuy

Hi Radek,

Thank you for your post.  Lucide installed properly after I renamed the wpirtl.dll in c:\ecs\dll and then copied the wpirtl.dll from c:\ecs\install\warpin.

Thank you,
Todd
Todd J Simpson (IT Consultant)
Business Automation Technologies
(Professional Products and Services.  Business to Business...)

The Blue Warper

#6
Todd,

while the safer path should be to wait for your feedback before, I think that, based on your finding two different versions of "wpirtl.dll", Radek's suggestion is correct.
I'd like to give you a different (perhaps more general) hint.  It's a good habit to periodically check the LIBPATH statement in the CONFIG.SYS, as some programs tend to place their own path at the beginning of the libpath list, thus causing the dot character "." to go further and further.  This character "." (to be followed by a semicolon ".;" ) should really go at the first place, because it refers to the current directory.
This way you globally instruct the system to search for DLLs in the current directory first (which is where the executable is actually located), thus avoiding such conflicts like the one you're experiencing (provided you're actually suffering from this very issue I'm referring to here...).

Regards




Update:
Just noticed your post, Todd.  It came when I was typing mine...  Glad you solved it!  Bye!

Pete

Hi Todd

A thought: eCS usually places libc* files in \ecs\dll - which is always before \os2\dll in an eCS generated config.sys LibPath.

You may want to consolidate all libc* files into \ ecs\dll to avoid possible future problems.

Regards

Pete

NNYITGuy

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


Todd J Simpson (IT Consultant)
Business Automation Technologies
(Professional Products and Services.  Business to Business...)