Re: Occasional traps or locks on WPS start

Well, the problem is that during shutdown, the drivers are informed of this event.

My experience is, that UNI kernel used with an OS/2 4.52 and not with OS/2 Server does not handle the switch to "Shutdown" mode correctly. WPS tries to flush the INIs (BTW: uncached)and this process is not completed. Consequently the "Handle" table in OS2SYS.INI, which is often written last and made up of many little records, may be corrupted. OS2SYS.INI must have an identical length before shutdown and after boot to a fullscreen CMD. via ALT-F1, provided that you gave the system a few minutes to quiesce before shutdown. So note size and date/time of OS2SYS.INI before shutdown and after boot to FS CMD and if they are different even by only a few bytes, this is a strong indication of a kernel problem.

Regards
Uwe



dam4z7v001@xxxxxxxxxxxxxx wrote:
Uwe Pilgram ha escrito:
Uwe Pilgram wrote:
dam4z7v001@xxxxxxxxxxxxxx wrote:
I have been running eComStation 2.0 beta 2 milestone 2 (my
subscription expired) for some months, but lately I find a strange
problem:

When the WPS starts, sometimes it gets lock repeating a loop of the
startup sound while the pointer freezes with the clock cursor.

The system detected an internal processing error at
location ##0168:fff1da1f - 000e:ca1f.

Some idea on what is causing these errors?

--
David Mediavilla

if your system can be started to a command shell by using ALT-F1 during
the boot blob then you most likely have corrupted INI-files. Try
Checkini.exe (see hobbes) to fix it. Because this requires a complete

I have already tried running Checkini and Cleanini before shutdown.
I'm not sure if it helps. Sometimes I get trouble even after running
them.

Uwe

I have forgotten to say that OS2SYS.INI sometimes gets corrupted during
shutdown. The "object to path" or "handle" table is not completely
written. This would exactly lead to the symptoms you describe. You can
see that easily when you note the size of OS2SYS.INI and compare it
after a bad start of WPS after boot. If smaller then OS2SYS.INI is

Comparing the sizes of bad and good INIs does not show very big
differences. Anyway, running XFix before the WPS start does not show
but a few problems and solving them is no guarantee.

corrupted. I could correct that by using kernel 14.105_W4 in my Warp
4.52 system (not ECS). No more problems with WPS since then.

I also have Beta 3 but could not install it. Perhaps I can extract it
and copy it from my maintenance partition.

Uwe

--
David Mediavilla

.

Relevant Pages

  • Re: blue screen of nothing
    ... This is a shutdown not boot problem. ... since installing the critical update that ... I've tried uninstalling the critical update and even uninstalled ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: boot.ini missing after bootcfg /rebuild
    ... Get Sysinternals' Process Monitor from the Microsoft site and set it to ... feature the utility will boot right through the shutdown process. ... went by Startup and recovery button from System Properties and I got an ...
    (microsoft.public.windowsxp.help_and_support)
  • RE: Manual reseal and hiding the "FBReseal" window on 1st boot?
    ... the new FBReseal.exe has the option to either shutdown or restart. ... I also now see the "Resealing in progress" message on my clones when i boot ... don't understand why this window appears on my clones. ...
    (microsoft.public.windowsxp.embedded)
  • Re: boot.ini missing after bootcfg /rebuild
    ... Get Sysinternals' Process Monitor from the Microsoft site and set it to monitor the boot.ini file. ... If you enable Process Monitor's Boot Logging feature the utility will boot right through the shutdown process. ... went by Startup and recovery button from System Properties and I got an ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Cold boot problems
    ... problem under ME, also I could cold boot from an ME shutdown, boot to the XP ... The problem only manifested after cold booting from an XP ... Once power to the motherboard has been cut for a few ...
    (microsoft.public.windowsxp.hardware)