Acpi 2.12: Error Can't open file cpprrt36.msg for msg 5004

Discussion of ACPI driver (Power management, multi-processor support, PnP)
Paavo Nurminen
Posts: 22
Joined: Thu Jun 08, 2006 12:50

Acpi 2.12: Error Can't open file cpprrt36.msg for msg 5004

Postby Paavo Nurminen » Tue Sep 12, 2006 11:31

Installed Acpi 2.12 and apm to ecs 1.2/P4 system.
On boot up I get several error messages 'Can't open file CPPRRT36.MSG for message 5004 (SYS0318). Finally it stopped and required Enter to continue. Then it continued.
Booted system twice and first time cpu monitor went to 99,9 %. The message file was
found from ecsmt path. Going back to acpi 2.11 cured the problem. What is wrong?

Paavo Nurminen

User avatar
Pasha
Posts: 82
Joined: Fri Apr 21, 2006 14:17

Re: Acpi 2.12: Error Can't open file cpprrt36.msg for msg 50

Postby Pasha » Tue Sep 12, 2006 12:18

Paavo Nurminen wrote:Installed Acpi 2.12 and apm to ecs 1.2/P4 system.
On boot up I get several error messages 'Can't open file CPPRRT36.MSG for message 5004 (SYS0318). Finally it stopped and required Enter to continue. Then it continued.
Booted system twice and first time cpu monitor went to 99,9 %. The message file was
found from ecsmt path. Going back to acpi 2.11 cured the problem. What is wrong?

Paavo Nurminen


Need more info. What say about error, try remming AcpiDaemon, apm.add ?

Paavo Nurminen
Posts: 22
Joined: Thu Jun 08, 2006 12:50

Postby Paavo Nurminen » Wed Sep 13, 2006 09:29

When I remmed out

run=x:\os2\acpidaemon.exe

message file problem disappered. However, shutdown did not work properly (did not power off). Then I started acpidaemon.exe from command line. During shutdown I refused to kill acpidaemon.exe, and power off worked correctly. This is the first version to produce acpidaemon.log file:

13 Sep 09:28:05 AcpiDaemon Build date: Sep 7 2006 14:04:36 is started
13 Sep 09:28:05 AcpiDaemon Detect ACPI.PSD Version: 2.12 ACPICA.ADD Version: 2.12 ACPI32.DLL Version: 2.12 .IRQ9 used
13 Sep 09:28:05 AcpiDaemon Start addr PSD:f92e010e Start Adr driver:ffdf5000
13 Sep 09:28:05 AcpiDaemon Detect ACPI APM version 1.4
13 Sep 09:28:05 AcpiDaemon Busy called 55318 C1 called 473159 C2 called 0 C3 called 0
13 Sep 09:28:05 AcpiDaemon PSD Busy called 0 Idle called 0
13 Sep 09:28:05 AcpiDaemon "\_S1_" Acepted
13 Sep 09:28:05 AcpiDaemon "\_S3_" Acepted
13 Sep 09:28:05 AcpiDaemon "\_S4_" Acepted
13 Sep 09:28:05 AcpiDaemon "\_S5_" Acepted
13 Sep 09:28:05 AcpiDaemon Choice STATE_S3
13 Sep 09:28:05 AcpiDaemon ACPI thread is starting ID 0x2
13 Sep 09:28:05 AcpiDaemon Check cfg thread is starting ID 0x3
13 Sep 09:28:05 AcpiDaemon LID thread is starting ID 0x3
13 Sep 09:28:05 AcpiDaemon PwrButton thread is starting ID 0x3
13 Sep 09:28:05 AcpiDaemon ======== APM thread is starting =========
13 Sep 09:28:05 AcpiDaemon LID device not finding, finish thread


Paavo Nurminen

Robert_L
Posts: 49
Joined: Thu Jul 13, 2006 18:00
Location: Germany

Postby Robert_L » Wed Sep 13, 2006 10:55

Paavo Nurminen wrote:'Can't open file CPPRRT36.MSG for message 5004 (SYS0318).


CPPRRT36.MSG should be copied to \OS2\SYSTEM to diplay the actual error message. This msg file used to be part of the VACPP compiler v3.6. I don't have it at hands right now, but maybe someone can send it to Paavo.

Paavo Nurminen
Posts: 22
Joined: Thu Jun 08, 2006 12:50

Postby Paavo Nurminen » Wed Sep 13, 2006 16:00

Thank you Robert,

I do have file CPPRRT36.MSG in my system. It is part of eCSMT distribution. I copied it to \OS2\SYSTEM directory and removed REM from RUN = X\\OS2\Acpidaemon.exe.
Result: New error messages, at least seven (7) of them:

Can't open
?: The file name is "", a null pointer, or an invalid DDNAME.

Press Enter to continue...

Now Pasha, you have more information.

Paavo

Robert_L
Posts: 49
Joined: Thu Jul 13, 2006 18:00
Location: Germany

Postby Robert_L » Wed Sep 13, 2006 17:16

Paavo Nurminen wrote:Can't open
?: The file name is "", a null pointer, or an invalid DDNAME.


I saw the same error message when I commented out the line "logfile = acpidaemon.log" from AcpiD.cfg. Maybe it also comes in case AcpiD.cfg is not in the ETC directory.

Paavo, verify that AcpiD.cfg is in \MPTN\ETC or wherever the ETC evironment variable points to.

Paavo Nurminen
Posts: 22
Joined: Thu Jun 08, 2006 12:50

Postby Paavo Nurminen » Thu Sep 14, 2006 10:00

AcpiD.cfg is in \MPTN\ETC. In previous experiments I had reference to acpid.log in RUN statement. First I removed itt, and got error message:

Can't open acpidaemon.log

Then I gave full path to the log file in AcpiD.cfg, and got error messages:

Can't open n:\acpidaemon.log

?: File is open.

... And then 'Press Enter...'. to continue.

But logging works and power off at shutdown works also.
How could we get rid of apparently unnecessary error messages at boot time?

Paavo

Paavo Nurminen
Posts: 22
Joined: Thu Jun 08, 2006 12:50

Postby Paavo Nurminen » Fri Sep 15, 2006 10:52

Temporary solution:
rem run=n:\os2\AcpiDaemon.exe
from CONFIG.SYS.

Create program object for AcpiDaemon.exe and put it's Shadow to Startup Folder.

Paavo

Paavo Nurminen
Posts: 22
Joined: Thu Jun 08, 2006 12:50

Postby Paavo Nurminen » Mon Sep 18, 2006 16:17

Now with version 1.5 of APM.ADD and corresponding AcpiDaemon.exe (13.9.2006) error messages are gone. However, suspend from Power icon hangs my machine (S1 and S3). Video is SciTech SNAP.

Paavo Nurminen


Return to “ACPI for eComStation”

Who is online

Users browsing this forum: No registered users and 2 guests

cron