• 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

Startup objects not... starting up

Started by RobertM, 2010.07.21, 01:39:28

Previous topic - Next topic

RobertM

Hi all,

The subject says it all. The specifics are as follows:

- eCS v1.2MR
- HPFS386 Boot Drive (has been since day two (literally, day two)
- Startup objects located in Startup folder
- SET RESTARTOBJECTS=STARTUPFOLDERSONLY, REBOOTONLY

I have removed "REBOOTONLY" and get the same results. My suspicions are this is an ini issue? Would this be a good guess?

Oddly, the system also ignores any JFS cache value over 64MB (only allocating 64MB regardless of the setting) even though the system has 2GB of physical RAM.

Thanks,
Rob


|
|
Kirk's 5 Year Mission Continues at:
Star Trek New Voyages
|
|


Fahrvenugen

Is this a machine you can safely do restarts on without disrupting production?  If so I'd be tempted to make backups of my ini files and rebuild them and see what happens.  The startup folder is an object of the desktop, and generally when desktop objects get messed up its an ini issue.

Just in case you need it...

cd c:\os2
attrib -r -s -h os2.ini
attrib -r -s -h os2sys.ini
ren os2.ini os2.backup
ren os2sys.ini os2sys.backup
makeini os2.ini ini.rc
makeini os2sys.ini inisys.rc

Then reboot.

See if your problem gets solved, if it does then for sure it is an ini problem.  You can try restoring the backup and running something like unimaint on them, or just start with the fresh desktop.


RobertM

Quote from: Fahrvenugen on 2010.07.21, 05:33:42
Is this a machine you can safely do restarts on without disrupting production?  If so I'd be tempted to make backups of my ini files and rebuild them and see what happens.  The startup folder is an object of the desktop, and generally when desktop objects get messed up its an ini issue.

Sadly, no... but I may have to... I have a feeling that my recent xcopy didnt copy some necessary extended attribute. I've got something on my laptop I can use to reset that stuff (a little REXX script someplace) which I may try first... after I dig out the damn tag for that folder...

Does anyone know... is it supposed to be <WP_STARTUPFOLDER>?

That way may save a reboot or three... failing that, I will try your method, then unimaint on some night when things are slow.

Something I miss (cannot recall where it's from either) is the timed and ordered Startup folder on my WSeB boxes. It is a MUCH better thing for me to be using so I can (in order, with slight delay for each) do:
- Initialize TCP stuff
- Initialize firewall and load rules
- Initialize REXX DLLs
- Initialize additional IP(s)
- Initialize Daemons

Though it's only a brief moment, if those things aren't loaded in the correct order, it can of course create issues such as:
- cgi scripts dont run (needs specific REXX DLLs loaded - I have eliminated the load calls from the rexx scripts to improve performance - even though it's negligible
- Firewall may not be active when MySQL starts
- Server daemons (FTP or web) may be active before firewall (this machine takes quite a beating from those attacking the Star Trek Phase 2 web properties).
- and so on.

Best,
Rob


|
|
Kirk's 5 Year Mission Continues at:
Star Trek New Voyages
|
|


Fahrvenugen

What about - rather then using the startup folder, just put the stuff in startup.cmd on the root of your boot drive, then you can start stuff in its particular order, if you need to wait / pause you can write it into the script, etc.

Most of my machines have everything going through starup.cmd (with the exception of one machine which has Priority Master/2 installed on it, everything is set to auto-start from Priority Master at different priority levels).

Then even if your desktop objects do get corrupted, the machine still boots up properly.

Just a thought.

RobertM

Quote from: Fahrvenugen on 2010.07.21, 07:55:00
What about - rather then using the startup folder, just put the stuff in startup.cmd on the root of your boot drive, then you can start stuff in its particular order, if you need to wait / pause you can write it into the script, etc.

Most of my machines have everything going through starup.cmd (with the exception of one machine which has Priority Master/2 installed on it, everything is set to auto-start from Priority Master at different priority levels).

Then even if your desktop objects do get corrupted, the machine still boots up properly.

Just a thought.


Thought about it... and may do it. Not sure yet what I am going to do. Everything is (finally!!! YAY!) moving to the main server in a bit. Only a few things left to do on it...
- Try different APIC method for SMP (only recognizes 2 of the 4 CPUs for some reason)
- Install the Broadcom NIC drivers
- Copy everything over and enable it.

Once done, that leaves me plenty of time to play with the other box.

-R


|
|
Kirk's 5 Year Mission Continues at:
Star Trek New Voyages
|
|


aschn

Quote from: RobertM link=topic=2468.msg16356#msg16356
date=1279665568

- eCS v1.2MR
- HPFS386 Boot Drive (has been since day two (literally, day two)
- Startup objects located in Startup folder
- SET RESTARTOBJECTS=STARTUPFOLDERSONLY, REBOOTONLY

Hi, I would say that your Startup folder has lost its startup
functionality and maybe the entry in OS2.INI is not synchronized
anymore with your current object handles.

It's not so hard to check that and to re-add it to the OS2.INI:

o  The ini application is "PM_Workplace:Startup".

  The contained keys point to the WPS handle(s) of the startup
  folder(s). The value is a "Y" with trailing nulls, or anything
  else (if you want to deactivate a startup folder manually and by
  ini editing).

o  How to get the handle of an startup folder object with eWP or XWP:

  Open the properties of the startup folder that contains your
  objects. On the Icon tab press the "Details..." button. You see
  the Object handle of that folder. (My is e.g. 0x3C779.)

o  Fix your OS2.INI with an ini editor:

  Go to the application "PM_Workplace:Startup". Add the hex value
  from above without the "3" as an ini key. (I have there "C779".)
  Add the value "Y.." = "59 00 00".

--
Andreas Schnellbacher

RobertM

Hi Andreas,

Oddly, eWP shows the handle has not changed, and the correct value is in the INI file (except perhaps the trailing nulls after the "Y"?)

Manually edited it to ensure the values were correct and no go. On to UniMaint I guess. Or recreating the INI files.

Thanks,
Rob


|
|
Kirk's 5 Year Mission Continues at:
Star Trek New Voyages
|
|


aschn

Hi Robert,

I would try something like the following script next:

/* */
call RxFuncAdd 'SysLoadFuncs', 'RexxUtil', 'SysLoadFuncs'
call SysLoadFuncs

class         = 'WPStartup'
title         = 'Startup'
location      = '<WP_OS2SYS>'
setup         = 'OBJECTID=<WP_START>;'
updatereplace = 'u'

rcx = SysCreateObject( class, title, location, setup, updatereplace)
if not rcx then
do
   say 'Error! rcx = 'rcx
   '@pause'
end

exit

If that still won't work, maybe the class "WPStartup" is not
registered anymore on your system.

Andreas

Pete

Hi Robert

Have you run checkini (from wptools) against the INI files? - it may help.

Regards

Pete

RobertM

Hi gang,

Yet to try either - but while researching and testing something else, I ran into this when running PHPINFO.PHP:

(Environment Variables)
RESTARTOBJECTS    NO

In digging through the config.sys file, I found just that entry (proper format of course) at the very end because of an IBMINST routine that I did not have the time to stop from loading... (inotherwords, a second entry for RESTARTOBJECTS).

Upon removing it, all is well.

Best,
Robert


|
|
Kirk's 5 Year Mission Continues at:
Star Trek New Voyages
|
|