OS2World OLD-STATIC-BACKUP Forum

OS/2 - Technical => Setup & Installation => Topic started by: claudiopache on 2007.11.28, 18:54:35

Title: error c0000005
Post by: claudiopache on 2007.11.28, 18:54:35
Hi folks. Recently we have bought a new Dell Server (Poweredge 840) and I need to install os/2 warp 3 for our logistic system.

After the installation, I proceeded with the FIXPACK atualization, but after the boot, an error appears and the system doesn't start.

the error is:
c0000005
P1=00000008  P2=00000580  P3=XXXXXXXX  P4=XXXXXXXX
..
..
..

Can anyone help me?

Thanks
Claudio

Title: Re: error c0000005
Post by: RobertM on 2007.11.28, 22:39:07
Unfortunately, as this is during the boot process, there are many possibilities... (I'm not sure if Warp 3 writes those errors to the POPUPLOG.OS2 file - but I dont think so... you can look for one on your boot drive and check - if it has a record of the issue, it will help in figuring out how to resolve it).

Basically, what is happening is that during boot, a process is trying to be loaded and is crashing... there can be many causes... the most common are one or a combination of:

Assuming it isnt an executable or driver that was replaced that is causing the problem (in which case you need to put the original back on the drive, or back out of the FixPack), one of these steps will work...

TRY #1 FIRST:

#1
What you can do is try booting to commandline... (you can use the Warp 3 floppies and select the option (Pretty sure it is F6 - Exit) when the blue install screen is up) and check the config.sys for errors. If you can't figure out what's wrong with the file, go to #2.


#2
You can compare the current config.sys file with the backed-up version (see #3 to find instructions on how to find the backup)... and from there you can try to figure out what changes were made and manually correct errors.

#3
At this point, if you haven't resolved the problem, if you want, you can email me a copy of the config.sys file (PM me for the email address), and I will see if I can find the error and fix it for you - or you can proceed to #4 and replace the current config.sys with the pre-FixPack one.



#4
Also, there should be a backup config.sys that was created during the FixPack install... you back up the current one (config.sys) to a different file name, and restore the pre-FixPack one. To determine which the pre-fixpack one is, simply do this... (at the commandline window you went to from booting off the floppies):

dir c:\config* /od

That will list all the config files in date order. Config.sys should be last - and the one before it should be the backup created by the FixPack Utility. Note: if you see multiple ones with dates/times near identical, it may mean that the FixPack Utility did multiple changes and created multiple backups... take the earliest one in the date range

For instance if your listing looks like this:

The volume label in drive C is WARPSERVER.
The Volume Serial Number is 297B:C015.
Directory of C:\

9-10-07   6:03p      9530          29  CONFIG.006
11-01-07   1:25p      9524          29  CONFIG.007
11-01-07   1:27p      9524          29  CONFIG.008
11-02-07   5:38p      9566          29  CONFIG.SYS

       4 file(s)     273785 bytes used
                  22655766 K bytes free


You would pick config.007 (and not .008)... so what you are doing is finding the original config.sys that was working, and in the above example, two backups were made during the FixPack install (which is unlikely).

-Robert
Title: Re: error c0000005
Post by: Pete on 2007.11.29, 14:15:29
Hi Claudio

As I understand it you have successfully installed Warp3 on a new system and then applied a fixpack?

I must admit to being surprised that Warp3 would even install on new hardware...

However, if it did install successfully then applying the fixpack seems to have caused the problem. I guess a read of the fixpack documentation to find out how to backout of the fixpack application is the way to go.

Not sure what the possible causes of a c0000005 error at boot are myself...

No file names mentioned anywhere on that screen?

Any way of checking what drivers did load? - might help identify where the problem comes from.

Regards

Pete
Title: Re: error c0000005
Post by: claudiopache on 2007.11.29, 14:50:32
Quote from: RobertM on 2007.11.28, 22:39:07
Unfortunately, as this is during the boot process, there are many possibilities... (I'm not sure if Warp 3 writes those errors to the POPUPLOG.OS2 file - but I dont think so... you can look for one on your boot drive and check - if it has a record of the issue, it will help in figuring out how to resolve it).

I wil check if some log was recorded

Quote
#2
You can compare the current config.sys file with the backed-up version (see #3 to find instructions on how to find the backup)... and from there you can try to figure out what changes were made and manually correct errors.

This was very helpful. I've compared the two files, but they are almost the same (except for the last line that sets an enviroment path var)

Quote
#3
At this point, if you haven't resolved the problem, if you want, you can email me a copy of the config.sys file (PM me for the email address), and I will see if I can find the error and fix it for you - or you can proceed to #4 and replace the current config.sys with the pre-FixPack one.

Sorry, what's PM? How can I email you the file?

Quote
#4
Also, there should be a backup config.sys that was created during the FixPack install... you back up the current one (config.sys) to a different file name, and restore the pre-FixPack one. To determine which the pre-fixpack one is, simply do this... (at the commandline window you went to from booting off the floppies):

I've tried this, but the same error appears. Probably some executable or dll that was modified.
I noticed that after the fixpack, theres a first boot (and it appears to be ok), when it process some locked files that wasn't modified yet. The second boot occurs the crash.


A friend of mine have done this instalation before in this Dell Poweredge 840 (but with a Pentium-D Dual Core inside). My server has a Xeon Quad Core. Could be this the problem?
Title: Re: error c0000005
Post by: El Vato on 2007.11.29, 17:33:12
Can you share with us a copy of your CONFIG.SYS ???

Is your OS/2 SMP enabled ???

What drive letter has been assigned to  your OS/2?

I might have an fixpaked (updated) bootable version of OS/2 3 around.  Can you download an image of a couple hundred MegaBytes and burn the image onto a CD???

Best regards.
Title: Re: error c0000005
Post by: Robert Deed on 2007.11.29, 19:39:05
If multicore is disabled in the bios and you are using a non-smp version of warp server you shouldn't be having a problem.  However, it is possible the newer kernel from the fixpack does not work well with that processor.  When warp 3 was created dual core processors did not exist on X86 architecture. 

You may want to find the newest kernel for the specific version of warp you have (smp or non smp) and try installing that from a command line boot before trying anything much more drastic. With warp3 most of my hangs in the past have always been the kernel, which is replaced with the locked files and therefor would fit the description of your problem.



Quote from: claudiopache on 2007.11.29, 14:50:32
Quote from: RobertM on 2007.11.28, 22:39:07
Unfortunately, as this is during the boot process, there are many possibilities... (I'm not sure if Warp 3 writes those errors to the POPUPLOG.OS2 file - but I dont think so... you can look for one on your boot drive and check - if it has a record of the issue, it will help in figuring out how to resolve it).

I wil check if some log was recorded

Quote
#2
You can compare the current config.sys file with the backed-up version (see #3 to find instructions on how to find the backup)... and from there you can try to figure out what changes were made and manually correct errors.

This was very helpful. I've compared the two files, but they are almost the same (except for the last line that sets an enviroment path var)

Quote
#3
At this point, if you haven't resolved the problem, if you want, you can email me a copy of the config.sys file (PM me for the email address), and I will see if I can find the error and fix it for you - or you can proceed to #4 and replace the current config.sys with the pre-FixPack one.

Sorry, what's PM? How can I email you the file?

Quote
#4
Also, there should be a backup config.sys that was created during the FixPack install... you back up the current one (config.sys) to a different file name, and restore the pre-FixPack one. To determine which the pre-fixpack one is, simply do this... (at the commandline window you went to from booting off the floppies):

I've tried this, but the same error appears. Probably some executable or dll that was modified.
I noticed that after the fixpack, theres a first boot (and it appears to be ok), when it process some locked files that wasn't modified yet. The second boot occurs the crash.


A friend of mine have done this instalation before in this Dell Poweredge 840 (but with a Pentium-D Dual Core inside). My server has a Xeon Quad Core. Could be this the problem?
Title: Re: error c0000005
Post by: RobertM on 2007.11.29, 20:22:47
Robert brings up some great points... though I am still amazed (as someone else here is) that you managed to get Warp 3 installed at all... from Dell's site:

"The PowerEdgeTM 840 server using the quad-core Intel® Xeon® 3200 series (Kentsfield) processors have up to 72% better performance than the Dell PowerEdge ..."


That's a pretty brand new technology... it's a single CPU Quad Core solution. So, here's a question (which may be relevant to your issues)... is it Warp 3 you are installing or Warp Server 4/Warp Server 4 Advanced?

Though Warp Server 4/Advanced is based off Warp 3, there were other things changed or added to the WS4 package - including, in the Advanced version, SMP support (which should not work with that system).

Truly, if you want to take advantage of that system, you would need either eCS 2.0 (GA version yet to be released), or to see if it has an option in the BIOS to select enabling and controlling the cores via MP1.1 or MP1.4 specs (unlikely, but you never know). If it supports an MP1.1 (or earlier) option, then Warp Server 4 Advanced should work with all the cores. If it supports 1.4 (or earlier), then WSeB or earlier will work - as well as any version of eCS with the SMP upgrade pack. If it does not support the earlier MP1.x methods, then you would need eCS 2.0 or be limited to one core.

Either way, Robert Deed's suggestion is a great place to start...
Title: Re: error c0000005
Post by: claudiopache on 2007.11.30, 13:43:29
We have to use the Warp 3 version, because of the the logistics system developer specifications. Something with the IBM DAE I think.

I tried to disable the multicore in Dell Server, but found nothing in setup. I will contact Dell for details.

A mate of mine suggested to search for another fixpack (a newer one). We found a xr_w040 version, but at IBM site I discovered that the Portuguese version latest fixpack is the xrpw035 (that  we already use) and the xr_w040 is only for the english version.

Besides your suggestions I will try to get this language version of the OS/2

Thanks for now
Title: Re: error c0000005
Post by: claudiopache on 2007.12.03, 21:01:13
After many tests we finally discover that the problem was not the quadcore, but the RAM 2GB DDR2 5300.

We have another Dell PE840 server with Pentium-D Dual Core and 512 MB DDR2 5300 of RAM, that was running well. We switch the memories and for our surprise the quadcore ran ok. With another server with 2GB RAM, but DDR1, the systems goes well too. The tests with just 1Gb also failed.

In another tests, we discover the point in config.sys that was producing the error. It is with the os2/boot/TESTCFG.SYS.  When we remarked it, the system started (with 1GB RAM) Even replacing this file with the version before the fixpack, the system still crashes.

Probably a driver the system is testing that causes the error. But which?

Does anybody knows it this testcfg.sys is really necessary?

Thanks all
Claudio
Title: Re: error c0000005
Post by: RobertM on 2007.12.04, 00:32:38
I think there is a patch for OS2LDR that may fix your issue. I am just not sure if it is available for Warp 3.

If the system is crashing on testcfg.sys, then I *think* it may be an attempt to configure a resource for a piece of hardware that is failing.

Whether you need it or not, I dont know. That would depend on the machine configuration.