Sysinfo build 0.8.2.5 - OS2

This is a discussion on Sysinfo build 0.8.2.5 - OS2 ; Sir: There is an update to the System Information tool that Alexey Smirnov provides, available in Hobbes incoming. Just like the previous version of this tool, the PCI.ini file is bad, in that the Sysinfo/2 tool reports that it is ...

+ Reply to Thread
Results 1 to 18 of 18

Thread: Sysinfo build 0.8.2.5

  1. Sysinfo build 0.8.2.5

    Sir:

    There is an update to the System Information tool that Alexey Smirnov
    provides, available in Hobbes incoming. Just like the previous version
    of this tool, the PCI.ini file is bad, in that the Sysinfo/2 tool
    reports that it is unable to open. Neither may Goran Ivankovic fine
    tool INI Editor 1.2.0 open it. I can only surmise that there exist
    something different on my machine that stops the loading of this file.
    --
    Bill
    Thanks a Million!

  2. Re: Sysinfo build 0.8.2.5

    Hi Bill

    William L. Hartzell wrote:
    > Sir:
    >
    > There is an update to the System Information tool that Alexey Smirnov
    > provides, available in Hobbes incoming. Just like the previous version
    > of this tool, the PCI.ini file is bad, in that the Sysinfo/2 tool
    > reports that it is unable to open. Neither may Goran Ivankovic fine
    > tool INI Editor 1.2.0 open it.



    I've found those problems myself in the past couple of hours :-(


    I can only surmise that there exist
    > something different on my machine that stops the loading of this file.



    Not just your machine but 3 systems here as well - in fact attempting to
    run SysInfo/2 v0825 a 2nd time causes systems to lockup requiring use of
    either Power Off or Reset (depends on what is on the system case).

    I'm currently putting a report together for the (new ?)
    updater/maintainer and suggest anyone else running into problems with
    this app sends a report as well. Note the email address only seems to be
    available from the Splash screen at start.

    Regards

    Pete


  3. Re: Sysinfo build 0.8.2.5

    Hi Peter ..

    Peter Brown wrote:
    > Hi Bill
    >
    > William L. Hartzell wrote:
    >> Sir:
    >>
    >> There is an update to the System Information tool that Alexey Smirnov
    >> provides, available in Hobbes incoming. Just like the previous
    >> version of this tool, the PCI.ini file is bad, in that the Sysinfo/2
    >> tool reports that it is unable to open. Neither may Goran Ivankovic
    >> fine tool INI Editor 1.2.0 open it.

    >
    >
    > I've found those problems myself in the past couple of hours :-(
    >
    >
    > I can only surmise that there exist
    >> something different on my machine that stops the loading of this file.

    >
    >
    > Not just your machine but 3 systems here as well - in fact attempting to
    > run SysInfo/2 v0825 a 2nd time causes systems to lockup requiring use of
    > either Power Off or Reset (depends on what is on the system case).
    >
    > I'm currently putting a report together for the (new ?)
    > updater/maintainer and suggest anyone else running into problems with
    > this app sends a report as well. Note the email address only seems to be
    > available from the Splash screen at start.
    >
    > Regards
    >
    > Pete
    >


    Curiously, not seen here in any system so far, thankfully. I'm curious though.
    Here not seen on either MCP2 Fix Pack 5, or Warp 4 Fix Pack 15. However,
    what I did was to simply update the files in the earlier install by just
    unzipping this fix over the older files in the operating directory. In my case
    the PCI.INI file in the directory shows up now as:

    8-02-07 1:10p 558910 0 PCI.INI


    I can open it with a text editor. In the case of "E", it shows to have
    embedded nulls in that file, but telling it to open it anyway does produce a
    'load' from there.

    For whatever research and so on might be of help here, this is the entire
    directory content for the toolset after the update:

    12-10-06 8:31p 0 .
    12-10-06 8:31p 0 ..
    2-25-04 11:05p 1542 0 copyright.txt
    8-02-07 1:10p 558910 0 PCI.INI
    7-30-07 10:52a 27096 0 Readme.eng
    8-02-07 1:10p 49664 0 sicpubch.DLL
    8-02-07 1:10p 49664 0 sifilbch.DLL
    8-02-07 1:10p 40960 0 simembch.DLL
    8-02-07 1:10p 36352 0 sirntime.DLL
    8-02-07 1:10p 1497600 0 sysinfo.EXE
    10-24-04 7:29p 0 T3
    10-24-04 7:29p 0 T4
    1-16-02 11:12a 88375 61 theseus0.dll
    10-25-00 7:31p 59054 0 videocfg.dll

    Curiously also, when I open up the new toolset, the new master mode choice
    opening page which has the tab for the COMPONENTS pane has a very puzzling
    report here. It claims that the entire SOM framework section is based on the
    Slovenian Language on all the computers tested so far!

    Even more curious, on one computer it reports a VIRGE component video display
    driver based on the Turkish Language!

    And on one computer, this 'update' changed the desktop Icon for the program to
    what looks like an Olympic torch graphics pattern. But that didn't happen,
    with the same 'overinstall' technique I described above on any of the other
    desktop icons for this tool.

    Of interest also may be that I pulled my copy of this off Hobbs right away when
    it hit Hobbs in the preview menu, before it was even added to the formally
    recognized preview text mode on that Hobbs interface. From there it was
    distributed to the other computers from that same download file from Hobbs.
    Could it be that somehow what is on Hobbs is maybe not the same as the one I
    got and is 'munched' now? The file I got from Hobbs is below. But also may be
    of interest is the fact that I renamed it to an 8X3 file name to better allow
    it to fit on my FidoNet BBS system archives as:

    8-02-07 11:46a 877351 72 sinfo825.zip

    The install in each case was made from unzipping that file. And that file
    above was directly unzipped into the target directory as an update from that
    file name above.

    Just trying to help here.


    --


    --> Sleep well; OS2's still awake!

    Mike Luther

  4. Re: Sysinfo build 0.8.2.5

    On Fri, 3 Aug 2007 05:46:55 UTC, "William L. Hartzell"
    wrote:

    > Sir:
    >
    > There is an update to the System Information tool that Alexey Smirnov
    > provides, available in Hobbes incoming. Just like the previous version
    > of this tool, the PCI.ini file is bad, in that the Sysinfo/2 tool
    > reports that it is unable to open. Neither may Goran Ivankovic fine
    > tool INI Editor 1.2.0 open it. I can only surmise that there exist
    > something different on my machine that stops the loading of this file.


    For what it's worth - I deleted the old installation, dziped the new zip
    file, in my utilities folder (not on any boot drive), and it ran on
    ECS20RC1 and 1.2 with no problems.
    Ben

  5. Re: Sysinfo build 0.8.2.5

    On Fri, 3 Aug 2007 05:46:55 UTC, "William L. Hartzell"
    wrote:

    > Sir:
    >
    > There is an update to the System Information tool that Alexey Smirnov
    > provides, available in Hobbes incoming. Just like the previous version
    > of this tool, the PCI.ini file is bad, in that the Sysinfo/2 tool
    > reports that it is unable to open. Neither may Goran Ivankovic fine
    > tool INI Editor 1.2.0 open it. I can only surmise that there exist
    > something different on my machine that stops the loading of this file.


    For what it's worth, I deleted the old installation, unziped the new zip
    file in the same place (on a drive I use for utilities, not the boot
    drives) and it ran fime on ECS1.2 AND 2.0RC1.
    Ben...

  6. Re: Sysinfo build 0.8.2.5

    Another thought Peter ..

    Peter Brown wrote:
    > Hi Bill
    >
    > William L. Hartzell wrote:
    >> Sir:
    >>
    >> There is an update to the System Information tool that Alexey Smirnov
    >> provides, available in Hobbes incoming. Just like the previous
    >> version of this tool, the PCI.ini file is bad, in that the Sysinfo/2
    >> tool reports that it is unable to open. Neither may Goran Ivankovic
    >> fine tool INI Editor 1.2.0 open it.

    >
    >
    > I've found those problems myself in the past couple of hours :-(
    >
    >
    > I can only surmise that there exist
    >> something different on my machine that stops the loading of this file.

    >
    >
    > Not just your machine but 3 systems here as well - in fact attempting to
    > run SysInfo/2 v0825 a 2nd time causes systems to lockup requiring use of
    > either Power Off or Reset (depends on what is on the system case).
    >
    > I'm currently putting a report together for the (new ?)
    > updater/maintainer and suggest anyone else running into problems with
    > this app sends a report as well. Note the email address only seems to be
    > available from the Splash screen at start.
    >
    > Regards
    >
    > Pete
    >


    Is this maybe some curious glitch in the zip/unzip archive process? I'm using
    the following unzip version here:



    --


    --> Sleep well; OS2's still awake!

    Mike Luther

  7. Re: Sysinfo build 0.8.2.5

    Another thought here Peter ..

    Peter Brown wrote:
    > Hi Bill
    >
    > William L. Hartzell wrote:
    >> Sir:
    >>
    >> There is an update to the System Information tool that Alexey Smirnov
    >> provides, available in Hobbes incoming. Just like the previous
    >> version of this tool, the PCI.ini file is bad, in that the Sysinfo/2
    >> tool reports that it is unable to open. Neither may Goran Ivankovic
    >> fine tool INI Editor 1.2.0 open it.

    >
    >
    > I've found those problems myself in the past couple of hours :-(
    >
    >
    > I can only surmise that there exist
    >> something different on my machine that stops the loading of this file.

    >
    >
    > Not just your machine but 3 systems here as well - in fact attempting to
    > run SysInfo/2 v0825 a 2nd time causes systems to lockup requiring use of
    > either Power Off or Reset (depends on what is on the system case).
    >
    > I'm currently putting a report together for the (new ?)
    > updater/maintainer and suggest anyone else running into problems with
    > this app sends a report as well. Note the email address only seems to be
    > available from the Splash screen at start.
    >
    > Regards
    >
    > Pete
    >


    Is this maybe a glitch in the zip/unzip archive operations? I'm using the
    following unzip tool here:

    4-06-05 6:30p 147507 0 UNZIP.EXE

    --


    --> Sleep well; OS2's still awake!

    Mike Luther

  8. Re: Sysinfo build 0.8.2.5

    > There is an update to the System Information tool that Alexey Smirnov
    > provides, available in Hobbes incoming. Just like the previous version
    > of this tool, the PCI.ini file is bad, in that the Sysinfo/2 tool
    > reports that it is unable to open. Neither may Goran Ivankovic fine
    > tool INI Editor 1.2.0 open it. I can only surmise that there exist
    > something different on my machine that stops the loading of this file.


    Here it stops at analyzing the MMOS2 subsystem.
    It behaves at least a bit better than the old 0.8.20 version
    which caused a complete hang of the system at the same point
    in time it now simply closes.

    Unfortunately there is no log file nor an entry in popuplog.os2.

  9. Re: Sysinfo build 0.8.2.5

    Ben B. ProNews/2 User wrote:
    >>
    >> There is an update to the System Information tool that Alexey Smirnov
    >> provides, available in Hobbes incoming. Just like the previous version
    >> of this tool, the PCI.ini file is bad, in that the Sysinfo/2 tool
    >> reports that it is unable to open.

    >
    > For what it's worth - I deleted the old installation, dziped the new zip
    > file, in my utilities folder (not on any boot drive), and it ran on
    > ECS20RC1 and 1.2 with no problems.
    >

    I tried the same method. It is not a valid INI file. And Sysinfo cannot
    open it.
    WSeB v4.50 fp3.

    --
    jmm (hyphen) list (at) sohnen-moe (dot) com
    (Remove .AXSPAMGN for email)

  10. Re: Sysinfo build 0.8.2.5

    Hi

    Jim Moe wrote:
    > Ben B. ProNews/2 User wrote:
    >>> There is an update to the System Information tool that Alexey Smirnov
    >>> provides, available in Hobbes incoming. Just like the previous version
    >>> of this tool, the PCI.ini file is bad, in that the Sysinfo/2 tool
    >>> reports that it is unable to open.

    >> For what it's worth - I deleted the old installation, dziped the new zip
    >> file, in my utilities folder (not on any boot drive), and it ran on
    >> ECS20RC1 and 1.2 with no problems.
    >>

    > I tried the same method. It is not a valid INI file. And Sysinfo cannot
    > open it.
    > WSeB v4.50 fp3.
    >



    If you delete the supplied PCI.INI, run SysInfo/2 and close it a new
    empty PCI.INI is generated.

    I tried adding just the 10DE (nVidia) entries from my previous pci.ini
    file to this newly created, empty PCI.INI and running SysInfo/2.
    Result: locked up system.

    Regards

    Pete

  11. Re: Sysinfo build 0.8.2.5

    Am 03.08.07 10.26 schrieb Heiko Nitzsche:
    >> There is an update to the System Information tool that Alexey Smirnov
    >> provides, available in Hobbes incoming. Just like the previous
    >> version of this tool, the PCI.ini file is bad, in that the Sysinfo/2
    >> tool reports that it is unable to open. Neither may Goran Ivankovic
    >> fine tool INI Editor 1.2.0 open it. I can only surmise that there
    >> exist something different on my machine that stops the loading of this
    >> file.

    >
    > Here it stops at analyzing the MMOS2 subsystem.


    That is my problem as well. After having read the previous posts, I already
    thought, I'm the only one getting stuck ;-)

    > It behaves at least a bit better than the old 0.8.20 version
    > which caused a complete hang of the system at the same point


    Hmm, the old version used to run, but today after downgrading to it again, it
    also got stuck.

    > in time it now simply closes.


    Would be nice if it did here as well. Somehow it seems to clog the WPS thread,
    since CPU load stays below 10% on my K6-2/500, but WPS windows aren't
    refreshed, VIO windows don't accept any keyboard input and I cannot even kill
    Sysinfo/2 with Watchcat. It seems to be indestructible ;-)

    Only way to recover is to reboot, which isn't really that nice.

  12. Re: Sysinfo build 0.8.2.5

    Heiko Nitzsche wrote:

    > Here it stops at analyzing the MMOS2 subsystem.
    > It behaves at least a bit better than the old 0.8.20 version
    > which caused a complete hang of the system at the same point
    > in time it now simply closes.


    I had that problem with the old version too, although the last time I
    ran it was probably on my old system. The new version starts up fine
    here; one difference I can think of is that I'm using UniAud on the new
    system, whereas the old system had an ISA SB AWE64 card.

  13. Re: Sysinfo build 0.8.2.5

    William L. Hartzell wrote:
    > Sir:
    >
    > There is an update to the System Information tool that Alexey Smirnov
    > provides, available in Hobbes incoming. Just like the previous version
    > of this tool, the PCI.ini file is bad, in that the Sysinfo/2 tool
    > reports that it is unable to open. Neither may Goran Ivankovic fine
    > tool INI Editor 1.2.0 open it. I can only surmise that there exist
    > something different on my machine that stops the loading of this file.


    I have the same problem about opening the PCi.ini file. Other than that
    it runs fine unlike previous versions that often failed when gathering
    multimedia info. Of course this is a different computer with different
    sound card. Previous was an ISA proaudio card.
    Dave

  14. Re: Sysinfo build 0.8.2.5

    Sir:

    William L. Hartzell wrote:
    > Sir:
    >
    > There is an update to the System Information tool that Alexey Smirnov
    > provides, available in Hobbes incoming. Just like the previous version
    > of this tool, the PCI.ini file is bad, in that the Sysinfo/2 tool
    > reports that it is unable to open. Neither may Goran Ivankovic fine
    > tool INI Editor 1.2.0 open it. I can only surmise that there exist
    > something different on my machine that stops the loading of this file.


    To add more information, I deleted the previous install and unzip the
    new in its place. Even with the bad ini file, the program runs and
    displays most of the ordinary information. This version does not turn
    on the audio in my Tv card, so that is a fix. One thing I did notice is
    the font and look of the application has changed, and IMHO not for the
    better (sorry, if intentional, but it may be my fault if it is warpsan).
    Other than this, I did not see a change list and don't know what is
    new and improved. I am glad that someone has taken on the task of
    keeping this tool alive.
    --
    Bill
    Thanks a Million!

  15. Re: Sysinfo build 0.8.2.5

    New sub-thread for emphasis Will ..

    William L. Hartzell wrote:
    > Sir:
    >
    > There is an update to the System Information tool that Alexey Smirnov
    > provides, available in Hobbes incoming. Just like the previous version
    > of this tool, the PCI.ini file is bad, in that the Sysinfo/2 tool
    > reports that it is unable to open. Neither may Goran Ivankovic fine
    > tool INI Editor 1.2.0 open it. I can only surmise that there exist
    > something different on my machine that stops the loading of this file.


    I've been following this closely for all the posts so far. I've
    'over-installed' this now on a whole host of boxes here and elsewhere and seen
    none of this so far. The boxes are, as noted, on MCP2 FP5 and Warp4 FP17 (Yes
    I did make an error saying it was FP15 earlier). I've got original SB Live
    cards, SB Live 5.1 cards, IBM Uniaudio chipsets, IBM Thinkpad chipsets with the
    IBM audio drivers. And maybe one thing is of value as to why I've not seen
    this and others do.

    On every single one of the installations I have made absolutely sure that the
    Audio card/chipset is on a unique IRQ and there is no conflict there. I do
    understand that OS/2 can share IRQ's if the device driver is properly written
    to do that. Over the years I think that more of this IRQ 'shared' issue shows
    up which is harder to lick in PCI slot hardware instances. It is especially an
    issue with lockups, per my observation, in boxes where there are LAN card or
    chipset shared IRQ issues with the audio devices.

    Since I have yet to see this, is the lockup issue being reported here a result
    of some IRQ or port sharing/contamination which the SYSINFO tool cannot handle
    in some way?

    Just trying to help here.


    --


    --> Sleep well; OS2's still awake!

    Mike Luther

  16. Re: Sysinfo build 0.8.2.5

    Wolfi wrote:
    > Am 03.08.07 10.26 schrieb Heiko Nitzsche:
    >>> There is an update to the System Information tool that Alexey Smirnov
    >>> provides, available in Hobbes incoming. Just like the previous
    >>> version of this tool, the PCI.ini file is bad, in that the Sysinfo/2
    >>> tool reports that it is unable to open. Neither may Goran Ivankovic
    >>> fine tool INI Editor 1.2.0 open it. I can only surmise that there
    >>> exist something different on my machine that stops the loading of
    >>> this file.

    >>
    >> Here it stops at analyzing the MMOS2 subsystem.

    >
    > That is my problem as well. After having read the previous posts, I
    > already thought, I'm the only one getting stuck ;-)


    Mine seemed to stop here I waited as long as 5 minutes and nothing
    finally I walked away and when I came back it was open and working. I
    have no idea how long it took to load (>5 min , < 1 hr).

    >
    >> It behaves at least a bit better than the old 0.8.20 version
    >> which caused a complete hang of the system at the same point

    >
    > Hmm, the old version used to run, but today after downgrading to it
    > again, it also got stuck.


    You probably have mixed dll some from the old some from the new 1st in
    your path. This is possibly the reason for some of the other failures or
    maybe the lack of libc 0.63.

    >
    >> in time it now simply closes.

    >
    > Would be nice if it did here as well. Somehow it seems to clog the WPS
    > thread, since CPU load stays below 10% on my K6-2/500, but WPS windows
    > aren't refreshed, VIO windows don't accept any keyboard input and I
    > cannot even kill Sysinfo/2 with Watchcat. It seems to be indestructible ;-)
    >
    > Only way to recover is to reboot, which isn't really that nice.


    Interesting CAD killed it here without a problem.

    Gregg

  17. Re: Sysinfo build 0.8.2.5

    Mike Luther wrote:

    > this IRQ 'shared' issue shows up which is harder to lick in PCI slot
    > hardware instances.


    PCI devices are required to share IRQs with other PCI devices. There
    may be buggy drivers, though...

  18. Re: Sysinfo build 0.8.2.5

    Am 06.08.07 21.20 schrieb Gregg Young:
    > Wolfi wrote:
    >> Am 03.08.07 10.26 schrieb Heiko Nitzsche:
    >>>> There is an update to the System Information tool that Alexey
    >>>> Smirnov provides, available in Hobbes incoming. Just like the
    >>>> previous version of this tool, the PCI.ini file is bad, in that the
    >>>> Sysinfo/2 tool reports that it is unable to open. Neither may Goran
    >>>> Ivankovic fine tool INI Editor 1.2.0 open it. I can only surmise
    >>>> that there exist something different on my machine that stops the
    >>>> loading of this file.
    >>>
    >>> Here it stops at analyzing the MMOS2 subsystem.

    >>
    >> That is my problem as well. After having read the previous posts, I
    >> already thought, I'm the only one getting stuck ;-)

    >
    > Mine seemed to stop here I waited as long as 5 minutes and nothing
    > finally I walked away and when I came back it was open and working. I
    > have no idea how long it took to load (>5 min , < 1 hr).


    For me it was something like >= 30min, >1h.

    >>> It behaves at least a bit better than the old 0.8.20 version
    >>> which caused a complete hang of the system at the same point

    >>
    >> Hmm, the old version used to run, but today after downgrading to it
    >> again, it also got stuck.

    >
    > You probably have mixed dll some from the old some from the new 1st in
    > your path. This is possibly the reason for some of the other failures or
    > maybe the lack of libc 0.63.


    I'm already using libC 0.63 since quite a while, since other programs required
    it quite a bit earlier.
    All but one DLLs are sitting right in Sysinfo's own subdir and have all been
    updated. And the only different one is IBM's videocfg.dll (bld.level 14.052),
    which isn't part of the latest 0.8.2.5 package anymore anyway, since I got an
    updated one in d:\OS2\DLL\ (bld.level 14.105).

    >>> in time it now simply closes.

    >>
    >> Would be nice if it did here as well. Somehow it seems to clog the WPS
    >> thread, since CPU load stays below 10% on my K6-2/500, but WPS windows
    >> aren't refreshed, VIO windows don't accept any keyboard input and I
    >> cannot even kill Sysinfo/2 with Watchcat. It seems to be
    >> indestructible ;-)
    >>
    >> Only way to recover is to reboot, which isn't really that nice.

    >
    > Interesting CAD killed it here without a problem.


    Never here. When Sysinfo hangs (this and last version), then it always
    requires a reboot in order to recover. I never managed to just kill it.

    Wolfi

+ Reply to Thread