• 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
Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - NNYITGuy

#61
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


#62
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
#63
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
------------------------------------------------------------
#64
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]
------------------------------------------------------
#65
Hi Pete,

I will send you off an email shortly...

Thanks,
Todd
#66
Hello,

I need a simple CLI applet for reading and copying info from TXT based log files.  The app needs to find the EOF and then look backwards one char at a time until a matched set of chars is found.  The app will then copy from that point to EOF to a separate TXT file.  The chars to be searched and identified must be defineable as an external param defined from the CL or from a text based INI file.

If the applet completes this task satisfactorily then other TXT based recognition features will be added for expanded functionality for an additional project.

Please respond to this post if you are interested in this programming task.  Any compiled language will be acceptable, but I would like to support the Sibyl or WDSibyl development platform.  Source code must also be provided as part of the finished applet.

I mentioned CLI above, but a GUI would be accepted for a WDSibyl developed applet.

Thank You and Best Regards,
Todd Simpson
#67
Please do tell of the solution that provides the LightScribe labeling capabilities...

Thankx,
Todd
#68
Hello All,

I bring to the discussion table the topic of CD-DVD labeling.  I recently have implemented the LightScribe  labeling technology for clients that use Windows for their desktop OS.  I would like to use this same labeling technology for my eCS based systems.

Is there a solution for us that currently implements the LightScribe labeling technology for eCS?

If there is not, is there enough of a need to have it built for our eCS platform? The LightScribe website also offers a free SDK.  I downloaded it and saved it for a future look see, but I have not had time to look at it to see what it contains.

Best Regards.
Todd Simpson
#69
Hello All,

Installed Virtualbox v161 from Paul's build.  Loads well.  Installed XP as a vm from an ISO. Works well. Created a second vm with XP.  Started the second vm and I get the following.  Located the VMMR0.dll and it exists in virtual box folder.  I added I:\VirtualBox to the path statements in config.sys.  I added the I:\VirtualBox to the working path for the app icon.  Below is  my copy of the error listing.

Is this a limitation of our OSE edition? Or is the a linking prob with the port? I saw this same item mentioned in a much earlier post, but I saw no solution from that post.

====
Failed to load VMMR0.r0.
VBox status code: -2 (VERR_INVALID_PARAMETER).


Result Code:
0x80004005
Component:
Console
Interface:
IConsole {d5a1cbda-f5d7-4824-9afe-d640c94c7dcf}

===

Thank you and best regards,
Todd Simpson
#70
Sorry Everyone,

I have been so busy.  No time to get back to this until now.  This message has to be short.

eCS 2.0 RC4 clean install to fresh hard disk with JFS boot partition.

Install completes and system is completely usable.  Reboots and cold boot are are perfect.  Install Warpin v1.0.17 as per Samba v3.0.28 WPI package.  Set UNIXROOT=C: as per Samba WPI install package request.  Samba WPI exits and wants a reboot before proceeding.

Reboot is good.  Also cold boot is good too.  Reboot again for good measure.  Everything still is good.

Install Samba WPI package.  Samba WPI requests a reboot.  I reboot.  System always hangs and last message at bottom left of screen is "Installing OS2LVM.DMD".  System never gets any farther.

ALT+F1 then F2 gets me to the same thing, "Installing OS2LVM.DMD".

I start the eCS installer from CD and get to CMD prompt.  Find current config.sys, copy it to *.samba, then copy a pre Samba config.??? to config.sys and exit CMD prompt.  Select reboot from Maintenance Menu.

System reboots to the same "Installing OS2LVM.DMD".

So, my belief is that something has possibly happened to JFS partition during install of Samba WPI or that something in the needed networking config somehow does not either work with JFS boot or something in the base code of eCS v2.0RC4.

My next step is to install to eCS v2.0RC4 to fresh hard disk on a HPFS partition exactly like I have installed to JFS.  That will not happen until this weekend.

Wow, it is so easy to get carried away with this stuff.  I constantly loose track of time... LOL HA HA HA  Good thing I really like what I do for living, or this would be really painful.

Best regards,
Todd
#71
Hi Everyone,

I installed and configured eCS 2.0RC4 and everything worked fine.  I then decided to install Samba server v3.0.28 WPI package.  The installer reported a successful install.  I then rebooted.  The boot process stopped at "Installing OS2LVM.DMD" and never progressed further.

I rebooted several times and the same result.  I even tried to boot to ALT + F1 and F2 to get to a command prompt.  That stopped at the same spot of "Installing OS2LVM.DMD".

I then re-installed again eCS v2.0RC4 successfully, then installed Samba v3.0.28 WPI successfully and rebooted.  The same boot stop as mentioned above.

On the first attempt above I had originally installed and then removed the PEER components as per prescribed in eCS based docs for samba installation.  The second eCS install did not have PEER installed and I confirmed the config.sys entries to make sure that it was clear of the eCS PEER items that needed to be removed prior to Samba install.

Is this an ACPI issue? Is this a boot with JFS issue? Should I be looking to other resources and documentation for eCS v2.0RC4 for assistance?

Thank you,
Todd
#72
Hi mohamadp,

The info you posted on the POPUPLOG.OS2 is from that date you posted.  So, appearantly you are experiencing a problem that is not recorded in POPUPLOG.OS2 as Moby stated.  My thinking was that the info from the error would be easier to post for analysis.

I am not an expert in the POPUPLOG info.  I have to look up the info as it happens.  Sometimes I would have to defer to support request to resolve it further.  But I will help out with the resources that I have and can find.

Regards,
Todd


#73
Hi mobybrick,

I did not know this about the IPE / "Full Screen Black TRAP".  So there is no recoding of this info to a file because there is no system intelligence to do the recording.  OK.  Just curious, would a PRNT SCRN work to record it to a device on LPT1: like BIOS issues?

Regards,
Todd
#74
Thank you all!  I will take everything in and check it all out.  It feels real good to get back this kind of positive response from the community.  I know we all really do have a good community here.  But I hear of other OS communities that get really do not have the team effort that we really show one and other here!

I will be testing the Intel and Broadcom and new 8169 drivers in the RC4 release.  I hope to post back in the future after I have tested.

Thanks Again!
Todd
#75
Hello All,

I just completed a transfer of 1.7 million files to a new SATA drive on a second machine.  I did not want to use PEER and did not want to install SAMBA just yet.  I used RSync port from Paul Smedley.  My original computer NIC configs did not work.  I completed the task by using a Intel/DEC 21041 10/100 NIC / driver with no problems.  But with such a large load for data replication I really wanted to use a gigabit NIC.

The Realtek 8169 or its driver originally as NIC#1 froze repeatedly.  I did not have a TRAP, but could not ping anything outside of the computer.  Other computers could ping all resources, but could get a response from the the Realtek NIC.  I have a gigabit switch plugged in to use the gigabit NICs.  I then used a 10/100 switch and the whole Rsync process went even farther but the Realtek NIC / driver quite yet again.  I swapped out the original Realtek NIC with another new Realtek NIC.  It failed the same way as the first.  I have used Realtek for so, so many projects and never had a problem with eCS or w32 based technologies.

So, after that long wind...  CAn someone make a recommendation on a rock solid NIC / driver for eCS?

Thank you,
Todd