• 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

Warp 4.52 + SMP + AHCI +ACPI

Started by Sigurd, 2012.02.15, 09:17:13

Previous topic - Next topic

Sigurd

Hi,

unfortunaltely the HP Slate turns out to be "uninstallable" with eCS or OS/2. As a sideeffect I did notice something else: I do have a Sony Viao VPC SB Laptop with Intel Core i7 Processor (i7 - 2620M). Unfortunately not eCS nor OS/2 can be installed here via CD/DVD as well, but while playing aorund for the Slate I dies create an updated Warp 4 DVD with UPDCD, it contains as well as the latest availiable Fixpacs:

- parts from eComStation:
 - ACHI driver

- other:
 SMP Kernel 104a_SMP from Warp 4

-> I installed this on another "OS/2" safe machines and made a clone with DFSEE via "Create Image File from a partition". Once I created the necessary partition next to windows 7 on the Sony Vaio I did "Restore" the file via DFSEE an installed the OS/2 Bootmanager.

Well - this OS/2 Warp 4.52 started very well, it detected two kernel (the Intel i7 2620 CPU has two "real" and in addition two "Hyperthreading" kernels) and in combination with the GENGRADD driver, offering the 1378X768 resolution of the 13.3 inch screen (NOT GLOSSY :-) ) with 16.7 Million colours-  (SNAP is not possible) it works really fast! The Crucial 128SSD is really quick.

So, encouriged by this unexpected success I tried to install ACPI on top of this, I used the 3.19.14 wpi from betazone, installed, rebooted and - GREAT! All 4 kernels there, the Power Icons was missing, so I used the Xwokplace function to recreate the Power Icon from there - and it does show the right Battery Life!

Problem (the only one I can see so far but did not test very much): the FAN is allways on and the system gets warm. A possible regression of the ACPI, but without ACPI there are the same effects.

(WLAN will for sure not go, LAN is not tested untill know, but it has a 3G/UMTS/HSPA option that I can may get to work.)

A picture can be found here (for those not registrated as a user here, for the otheres I do attach the picture):

http://www.commtalk.org/FileRepository/ForumAttachments/54-79446-Warp4Sony.png

So - encouriged by this I will try to Clone the eComStation 2.1 equipped with the ACPI 3.19.15 and see where this will lead me to with the Sony.

PLEASE NOTE: I know that it is usually not allowed to use AHCI nor ACPI with other OS/2 Versions than eComStation, but even though I will go on testing and hopefully this is interesting to some of you and this information may help eCS developers as well. And I will not distribute the OS/2 Merlin Clone, it is just for my "internal" use :-)


Sigurd

Hi,

to provide some more information here is what I tested with ACPI:

Added another picture as well.

Added ACPI tree as a file (to many caracters)
---------------------------------------------------------------
What thermal getts:

Show Thermal
Thermal zone "TZ01"
  Current temperature: 68 C ( 3412 K * 10)
  Critical temperature: 97 C ( 3702 K * 10)
  Thermal constant1: 1
  Thermal constant2: 2
  Thermal period: 50 sec * 10
  Passive cooling temperature: 74 C ( 3472 K * 10 )
Status 0x0 0 - No error
--------------------------------------------------------------
What GETTHRTHL getts:

Searching processors
------------------------------------
Processor [CPU0]  id:1 Possible for throttle setting
------------------------------------
Processor [CPU1]  id:2 Possible for throttle setting
------------------------------------
Processor [CPU2]  id:3 Possible for throttle setting
------------------------------------
Processor [CPU3]  id:4 Possible for throttle setting
------------------------------------
Processor [CPU4]  id:5 Possible for throttle setting
------------------------------------
Processor [CPU5]  id:6 Possible for throttle setting
------------------------------------
Processor [CPU6]  id:7 Possible for throttle setting
------------------------------------
Processor [CPU7]  id:8 Possible for throttle setting
------------------------------------
Usage: GetSet [CPUNumber Perfomance]
Pefomance 0...100 %

------------------------------------------------------------------------
What GETTABLE getts:

Look table "-"
Error call ACPI CA 5 - The name was not found in the namespace

------------------------------------------------------------------------

What GETVALUE getts:

Status 0x0 0 - No error
Timer's resolution 24 bit
Status 0x0 0 - No error
Start ticks - 0
Call DosSleep(1000)...
Status 0x0 0 - No error
End ticks - 0
Time elapsed - 55327 mks

-----------------------------------------------------------------------

What ACPISTAT getts:

The version of ACPI.PSD that is installed is 3.19.14
The system is operating in Symmetric mode (Mode 2)
The kernel is 104a SMP

Number of IRQs available: 24
IRQ 00 count 5503
IRQ 01 count 303
IRQ 08 count 206618
IRQ 09 count 280
IRQ 12 count 19504
IRQ 20 count 27
IRQ 22 count 10615
IRQ 23 count 49

========== CPU0 ==================
ACPI name [CPU0]
IPIGenCount = 27723      IPICount    = 45336    
IPIHLT      = 0          IdleCount   = 253859     BusyCount   = 11345    
C1Count     = 0          C2Count     = 0          C3Count     = 0        
========== CPU1 ==================
ACPI name [CPU1]
IPIGenCount = 40102      IPICount    = 41015    
IPIHLT      = 0          IdleCount   = 11271      BusyCount   = 11270    
C1Count     = 0          C2Count     = 0          C3Count     = 0        
========== CPU2 ==================
ACPI name [CPU2]
IPIGenCount = 41831      IPICount    = 40627    
IPIHLT      = 0          IdleCount   = 7510       BusyCount   = 7509      
C1Count     = 0          C2Count     = 0          C3Count     = 0        
========== CPU3 ==================
ACPI name [CPU3]
IPIGenCount = 54097      IPICount    = 36775    
IPIHLT      = 0          IdleCount   = 7835       BusyCount   = 7833      
C1Count     = 0          C2Count     = 0          C3Count     = 0  

-------------------------------------------------------------------------------------------

What SCANPCI getts:

Bus:0 Dev: 0 Fnc:0   Class:0600   Hdr:00
Bus:0 Dev: 1 Fnc:0   Class:0604   Hdr:81
  Bridge 0->1..1
Bus:0 Dev: 2 Fnc:0   Class:0300   Hdr:00
Bus:0 Dev:22 Fnc:0   Class:0780   Hdr:80
Bus:0 Dev:26 Fnc:0   Class:0C03   Hdr:00
Bus:0 Dev:27 Fnc:0   Class:0403   Hdr:00
Bus:0 Dev:28 Fnc:0   Class:0604   Hdr:81
  Bridge 0->2..2
Bus:0 Dev:28 Fnc:1   Class:0604   Hdr:81
  Bridge 0->3..3
Bus:0 Dev:28 Fnc:2   Class:0604   Hdr:81
  Bridge 0->4..4
Bus:0 Dev:28 Fnc:3   Class:0604   Hdr:81
  Bridge 0->5..5
Bus:0 Dev:29 Fnc:0   Class:0C03   Hdr:00
Bus:0 Dev:31 Fnc:0   Class:0601   Hdr:80
Error PIN 0x0
Bus:0 Dev:31 Fnc:2   Class:0104   Hdr:00
Bus:0 Dev:31 Fnc:3   Class:0C05   Hdr:00
Bus:1 Dev: 0 Fnc:0   Class:0300   Hdr:00
Bus:2 Dev: 0 Fnc:0   Class:0280   Hdr:00
Bus:3 Dev: 0 Fnc:0   Class:FF00   Hdr:00
Bus:4 Dev: 0 Fnc:0   Class:0C03   Hdr:00
Bus:5 Dev: 0 Fnc:0   Class:0200   Hdr:00
Bridges found:
0:00.00  class:0600  type: 0  Bus H->0
      Dev: 2 (0x 2) Fnc:00 INTA IRQ's PCI:16
      Dev:22 (0x16) Fnc:00 INTA IRQ's PCI:16
      Dev:26 (0x1a) Fnc:00 INTA IRQ's PCI:23
      Dev:27 (0x1b) Fnc:00 INTA IRQ's PCI:16
      Dev:29 (0x1d) Fnc:00 INTA IRQ's PCI:20
      Dev:31 (0x1f) Fnc:00 INTA IRQ's PCI: 0
      Dev:31 (0x1f) Fnc:02 INTA IRQ's PCI:22
      Dev:31 (0x1f) Fnc:03 INTB IRQ's PCI:22
0:01.00  class:0604  type: 1  Bus 0->1
      Dev: 0 (0x 0) Fnc:00 INTA IRQ's PCI:16
0:28.00  class:0604  type: 1  Bus 0->2
      Dev: 0 (0x 0) Fnc:00 INTA IRQ's PCI:16
0:28.01  class:0604  type: 1  Bus 0->3
      Dev: 0 (0x 0) Fnc:00 INTA IRQ's PCI:17
0:28.02  class:0604  type: 1  Bus 0->4
      Dev: 0 (0x 0) Fnc:00 INTA IRQ's PCI:18
0:28.03  class:0604  type: 1  Bus 0->5
      Dev: 0 (0x 0) Fnc:00 INTA IRQ's PCI:19
PCI Bus scan: 6 PCI buses found.
Sorting by routers:

Router: "\"  Current IRQ: 0 Possible IRQ:
End Scan

--------------------------------------------------------------------------
 
What ACPIIRQ gets:

Error turn on APIC, status f
Show ACPI IRQ routing
@
|
+*_SB_ T:[Device] STA:[0xffffffff]
  |
  +*PCI0 T:[Device] HID:[PNP0A08] CID:[PNP0A08] UID:[0] ADR:[0x0] STA:[0xffffffff]
==================================================
  Device  0x0016 Function ALL    INTA    Route to  IRQ16
  Device  0x0019 Function ALL    INTA    Route to  IRQ18
  Device  0x001a Function ALL    INTA    Route to  IRQ23
  Device  0x001b Function ALL    INTA    Route to  IRQ16
  Device  0x001c Function ALL    INTA    Route to  IRQ16
  Device  0x001c Function ALL    INTB    Route to  IRQ17
  Device  0x001c Function ALL    INTC    Route to  IRQ18
  Device  0x001c Function ALL    INTD    Route to  IRQ19
  Device  0x001d Function ALL    INTA    Route to  IRQ20
  Device  0x001f Function ALL    INTA    Route to  IRQ22
  Device  0x001f Function ALL    INTB    Route to  IRQ22
  Device  0x001f Function ALL    INTD    Route to  IRQ22
  Device  0x0001 Function ALL    INTA    Route to  IRQ16
  Device  0x0002 Function ALL    INTA    Route to  IRQ16
==================================================
     |
     +*LPCB T:[Device] ADR:[0x1f0000] STA:[0xffffffff]
        |
        +*H_EC T:[Device] HID:[PNP0C09] UID:[1] STA:[0xf]
           |
           +*ALSD T:[Device] HID:[ACPI0008] STA:[0x0]
           |
           +*BAT1 T:[Device] HID:[PNP0C0A] UID:[1] STA:[0x1f]
           |
           +*BAT2 T:[Device] HID:[PNP0C0A] UID:[2] STA:[0xb]
        |
        +*DMAC T:[Device] HID:[PNP0200] STA:[0xffffffff]
        |
        +*FWHD T:[Device] HID:[INT0800] STA:[0xffffffff]
        |
        +*HPET T:[Device] HID:[PNP0103] UID:[0] STA:[0xf]
        |
        +*IPIC T:[Device] HID:[PNP0000] STA:[0xffffffff]
        |
        +*MATH T:[Device] HID:[PNP0C04] STA:[0xffffffff]
        |
        +*LDRC T:[Device] HID:[PNP0C02] UID:[2] STA:[0xffffffff]
        |
        +*RTC_ T:[Device] HID:[PNP0B00] STA:[0xffffffff]
        |
        +*TIMR T:[Device] HID:[PNP0100] STA:[0xffffffff]
        |
        +*CWDT T:[Device] HID:[INT3F0D] CID:[INT3F0D] STA:[0xf]
        |
        +*PS2K T:[Device] HID:[PNP0303] STA:[0xf]
        |
        +*PS2M T:[Device] HID:[SNY9014] CID:[SNY9014] STA:[0xf]
        |
        +*SNC_ T:[Device] HID:[SNY5001] STA:[0xffffffff]
        |
        +*TPM_ T:[Device] HID:[IFX0102] CID:[IFX0102] STA:[0xf]
     |
     +*PDRC T:[Device] HID:[PNP0C02] UID:[1] STA:[0xffffffff]
     |
     +*EHC1 T:[Device] ADR:[0x1d0000] STA:[0xffffffff] SxD State:[0xff:ff:02:02]
        |
        +*HUBN T:[Device] ADR:[0x0] STA:[0xffffffff]
           |
           +*PR01 T:[Device] ADR:[0x1] STA:[0xffffffff]
              |
              +*PR11 T:[Device] ADR:[0x1] STA:[0xffffffff]
                 |
                 +*PHP0 T:[Device] ADR:[0x1] STA:[0xffffffff]
                 |
                 +*PHP1 T:[Device] ADR:[0x2] STA:[0xffffffff]
                 |
                 +*PHP2 T:[Device] ADR:[0x3] STA:[0xffffffff]
                 |
                 +*PHP3 T:[Device] ADR:[0x4] STA:[0xffffffff]
              |
              +*PR12 T:[Device] ADR:[0x2] STA:[0xffffffff]
              |
              +*PR13 T:[Device] ADR:[0x3] STA:[0xffffffff]
              |
              +*PR14 T:[Device] ADR:[0x4] STA:[0xffffffff]
              |
              +*PR15 T:[Device] ADR:[0x5] STA:[0xffffffff]
              |
              +*PR16 T:[Device] ADR:[0x6] STA:[0xffffffff]
              |
              +*PR17 T:[Device] ADR:[0x7] STA:[0xffffffff]
              |
              +*PR18 T:[Device] ADR:[0x8] STA:[0xffffffff]
     |
     +*EHC2 T:[Device] ADR:[0x1a0000] STA:[0xffffffff] SxD State:[0xff:ff:02:02]
        |
        +*HUBN T:[Device] ADR:[0x0] STA:[0xffffffff]
           |
           +*PR01 T:[Device] ADR:[0x1] STA:[0xffffffff]
              |
              +*PR11 T:[Device] ADR:[0x1] STA:[0xffffffff]
              |
              +*PR12 T:[Device] ADR:[0x2] STA:[0xffffffff]
              |
              +*PR13 T:[Device] ADR:[0x3] STA:[0xffffffff]
              |
              +*PR14 T:[Device] ADR:[0x4] STA:[0xffffffff]
              |
              +*PR15 T:[Device] ADR:[0x5] STA:[0xffffffff]
              |
              +*PR16 T:[Device] ADR:[0x6] STA:[0xffffffff]
     |
     +*HDEF T:[Device] ADR:[0x1b0000] STA:[0xffffffff]
     |
     +*RP01 T:[Device] ADR:[0x1c0000] STA:[0xffffffff]
==================================================
  Device  0x0000 Function ALL    INTA    Route to  IRQ16
  Device  0x0000 Function ALL    INTB    Route to  IRQ17
  Device  0x0000 Function ALL    INTC    Route to  IRQ18
  Device  0x0000 Function ALL    INTD    Route to  IRQ19
==================================================
        |
        +*WLAN T:[Device] ADR:[0x0] STA:[0xf]
     |
     +*RP02 T:[Device] ADR:[0x1c0001] STA:[0xffffffff]
==================================================
  Device  0x0000 Function ALL    INTA    Route to  IRQ17
  Device  0x0000 Function ALL    INTB    Route to  IRQ18
  Device  0x0000 Function ALL    INTC    Route to  IRQ19
  Device  0x0000 Function ALL    INTD    Route to  IRQ16
==================================================
        |
        +*RMSC T:[Device] ADR:[0x0] STA:[0xf]
     |
     +*RP03 T:[Device] ADR:[0x1c0002] STA:[0xffffffff]
==================================================
  Device  0x0000 Function ALL    INTA    Route to  IRQ18
  Device  0x0000 Function ALL    INTB    Route to  IRQ19
  Device  0x0000 Function ALL    INTC    Route to  IRQ16
  Device  0x0000 Function ALL    INTD    Route to  IRQ17
==================================================
        |
        +*NXUC T:[Device] ADR:[0x0] STA:[0xf]
     |
     +*RP04 T:[Device] ADR:[0x1c0003] STA:[0xffffffff]
==================================================
  Device  0x0000 Function ALL    INTA    Route to  IRQ19
  Device  0x0000 Function ALL    INTB    Route to  IRQ16
  Device  0x0000 Function ALL    INTC    Route to  IRQ17
  Device  0x0000 Function ALL    INTD    Route to  IRQ18
==================================================
        |
        +*RLAN T:[Device] ADR:[0x0] STA:[0xf]
     |
     +*SAT0 T:[Device] ADR:[0x1f0002] STA:[0xffffffff]
        |
        +*PRT2 T:[Device] ADR:[0x2ffff] STA:[0xffffffff]
     |
     +*SAT1 T:[Device] ADR:[0x1f0005] STA:[0xffffffff]
     |
     +*SBUS T:[Device] ADR:[0x1f0003] STA:[0xffffffff]
     |
     +*PEG0 T:[Device] ADR:[0x10000] STA:[0xffffffff]
==================================================
  Device  0x0000 Function ALL    INTA    Route to  IRQ16
  Device  0x0000 Function ALL    INTB    Route to  IRQ17
  Device  0x0000 Function ALL    INTC    Route to  IRQ18
  Device  0x0000 Function ALL    INTD    Route to  IRQ19
==================================================
        |
        +*PEGP T:[Device] ADR:[0x0] STA:[0xf]
           |
           +*DD01 T:[Device] ADR:[0x100] STA:[0xffffffff]
           |
           +*DD02 T:[Device] ADR:[0x410] STA:[0xffffffff]
           |
           +*DD03 T:[Device] ADR:[0x300] STA:[0xffffffff]
           |
           +*DD04 T:[Device] ADR:[0x301] STA:[0xffffffff]
           |
           +*DD05 T:[Device] ADR:[0x5] STA:[0xffffffff]
           |
           +*DD06 T:[Device] ADR:[0x6] STA:[0xffffffff]
           |
           +*DD07 T:[Device] ADR:[0x7] STA:[0xffffffff]
           |
           +*DD08 T:[Device] ADR:[0x8] STA:[0xffffffff]
     |
     +*B0D4 T:[Device] ADR:[0x40000] STA:[0xffffffff]
     |
     +*GFX0 T:[Device] ADR:[0x20000] STA:[0xffffffff]
        |
        +*DD01 T:[Device] ADR:[0x100] STA:[0xffffffff]
        |
        +*DD02 T:[Device] ADR:[0x410] STA:[0xffffffff]
        |
        +*DD03 T:[Device] ADR:[0x300] STA:[0xffffffff]
        |
        +*DD04 T:[Device] ADR:[0x301] STA:[0xffffffff]
        |
        +*DD05 T:[Device] ADR:[0x5] STA:[0xffffffff]
        |
        +*DD06 T:[Device] ADR:[0x6] STA:[0xffffffff]
        |
        +*DD07 T:[Device] ADR:[0x7] STA:[0xffffffff]
        |
        +*DD08 T:[Device] ADR:[0x8] STA:[0xffffffff]
     |
     +*AHCI T:[Device] ADR:[0x1f0002] STA:[0xffffffff]
        |
        +*PRT0 T:[Device] ADR:[0xffff] STA:[0xffffffff]
        |
        +*PRT1 T:[Device] ADR:[0x1ffff] STA:[0xffffffff]
        |
        +*PRT2 T:[Device] ADR:[0x2ffff] STA:[0xffffffff]
        |
        +*PRT3 T:[Device] ADR:[0x3ffff] STA:[0xffffffff]
        |
        +*PRT4 T:[Device] ADR:[0x4ffff] STA:[0xffffffff]
        |
        +*PRT5 T:[Device] ADR:[0x5ffff] STA:[0xffffffff]
  |
  +*LNKA T:[Device] HID:[PNP0C0F] UID:[1] STA:[0xb]
  |
  +*LNKB T:[Device] HID:[PNP0C0F] UID:[2] STA:[0xb]
  |
  +*LNKC T:[Device] HID:[PNP0C0F] UID:[3] STA:[0xb]
  |
  +*LNKD T:[Device] HID:[PNP0C0F] UID:[4] STA:[0xb]
  |
  +*LNKE T:[Device] HID:[PNP0C0F] UID:[5] STA:[0xb]
  |
  +*LNKF T:[Device] HID:[PNP0C0F] UID:[6] STA:[0x9]
  |
  +*LNKG T:[Device] HID:[PNP0C0F] UID:[7] STA:[0xb]
  |
  +*LNKH T:[Device] HID:[PNP0C0F] UID:[8] STA:[0xb]
  |
  +*ADP1 T:[Device] HID:[ACPI0003] STA:[0xf]
  |
  +*LID0 T:[Device] HID:[PNP0C0D] STA:[0xf]
  |
  +*PWRB T:[Device] HID:[PNP0C0C] STA:[0xf]
  |
  +*MEM2 T:[Device] HID:[PNP0C01] UID:[2] STA:[0xffffffff]
  |
  +*PTID T:[Device] HID:[INT340E] CID:[INT340E] STA:[0xf]
|
+*_TZ_ T:[Device] STA:[0xffffffff]
Status 0x0 0 - No error

------------------------------------------------------------------------------------

melf

/Mikael

Sigurd

Hi,

for whom it may interest:

- just tested the installation of Flash 11 - Installation went through without any issues, but did not test if it works because no Internet Connection possible till now

- just tested the installation of ACPI 3.19.15:
   -> ACPI WPI file refuses to install with the message: Unsupported OS
   -> Update from ACPI ZIP refuses to install with the message: (similar) not designed for this OS
   but there is a back door way so at least I was albe to get it to run (was not to hard....)

I think it would be a very very good idea to offer and sell Warp 4 user who do not want to by eComStation or still want to use Warp 4 - a separate ACPI.WPI - once it is finished - by mensys,  because as it seems to me it is not that hard to install a WPI file and it seems to work quit good with Warp 4.

Regarding the Sony:

- No LAN (Realtek GB driver from Mensys not working)
- No WLAN (unsupported adapter - as expected)
- Sound - problems with UNIAUD16.SYS that states - while UNIAUD32.SYS is loaded without issues - that there is not enough memory free.
- Grafic - Well, in 65thousand colour mode it is really usable, but with 16.7 Million colours it seems to be a bit slow - my first impression was that it seemed to be faster, but after using some fullsreenmode applications it turned out to be slower.

The most important problem - the heat! I fear to burn the Laptop if I will use it more than 15 Minutes (Same has been last may when I bought this Laptop and tried eCS 2.1 installation with using the SSD in another Laptop for installation (the X200T).

So - IMPORTANT NOTICE: Be aware that modern Laptops can be destroyed by eComStation! (as it happened to me two years ago, when my first X200T's graphics adapter burned....)

Some pictures as well.

Blonde Guy

Thanks Sigurd, for your work. I have similar problems with some industrial customers. They must run Warp 4, not eComStation, and in my case they must run the operating system on FAT16. So I have to hack, perhaps not as elegantly as you have done, but with many of the same obstacles. I think a Warp 4 add-on would be an interesting repackaging of the eCS license. I would not ask for a discount; my customers do not suffer from poverty.
Expert Consulting for OS/2 and eComStation

Fahrvenugen

I seem to recall back when ecs first came out, I think there was an option to just install Warp 4.52 or eCS (since eCS essentially is a Warp 4.52 license with the additional eCS stuff added on).  By having the eCS license this allowed you to use any of the eCS specific stuff on after a base 4.52 install (unsupported of course)

I wonder if this would still be a possibility - not that anyone would expect that Mensys would  provide support for such a thing, but for anyone who needs Warp 4.52 with a few of the eCS 2.1  additional items (like ACPI, Flash, etc), if you could purchase a eCS 2.1 license, install a base Warp 4.52 setup, and then just add in yourself the few extras (again, this would be unsupported and meant for the people who really know what they're doing, or people who don't know what they're doing and just like taking risks with their system).  From a licensing standpoint I think as long as you've got the eCS 2.1 license you should be okay doing something like this, but perhaps someone more familiar with the license can clarify.



RobertM

For Warp Server based components (from WSeB v4.52 CP2PF), I've actually considered a different route. Install eCS v2.1, then install the needed WSeB components. In the end, it seems the easier approach (and there are tutorials online for how to do so with earlier builds of each).

Depending on what you desire your end result to be, that may be the easier route.

As a matter of fact, modifying the installer to do so wouldn't be too difficult - neither would be writing a secondary installer to install what other features one wants. The stuff to do so is all part of the CID functionality in Warp that allows unattended and semi-unattended installation. It's not the most difficult to accomplish (for such purposes), but it's not quite the simplest either.


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


rwklein

Quote from: Blonde Guy on 2012.02.16, 03:48:43
Thanks Sigurd, for your work. I have similar problems with some industrial customers. They must run Warp 4, not eComStation, and in my case they must run the operating system on FAT16. So I have to hack, perhaps not as elegantly as you have done, but with many of the same obstacles. I think a Warp 4 add-on would be an interesting repackaging of the eCS license. I would not ask for a discount; my customers do not suffer from poverty.

The reasons they want to run on Warp 4 these customers is understandable. For example if its a medical application and approved for a certain level. Then again its of course also almost completely nuts to expect to run an operating system from 1996.

Now if you know what you are doing then its not a problem. But we just ran into another costumer that wants to deploy OS/2 software on ATM. They simply have no clue how it works!
Don't ask me how often we have large companies send back a positive email that they had been fooling around to find 4 GB hard disks or use old NIC drivers.

With eComStation you just boot of CD and with the new user interface and hardware detection you get all of that. Besides that the eCS installer has an option to more or less make eCS look like Warp 4. (Same icons and desktop etc).

As for installing on FAT 16. As far as I can tell most companies do this because they don't have anything that supports HPFS and or JFS to create disc images (we have DFsee!). I consider using FAT 16 partitions for your OS/DATA basicly nothing but plain suicide.

Your milage may vary of FAT 16 bug of all file systems is the least robust one of the 3!
We had a company that needs to upgrade old Warp 4 equipment. It controls a portition of a factory line.
Law requires that you can press an emergency stop button. This will instanltly power off the computer (cut off power). This has resulted in data loss already... HPFS/JFS In that sense is much more robust in surviving that.

Off all companies that Mensys has sold eComStation to so far a few wants to stick with Warp 4. But honestly after there technicall guys looked at eComStation and ease of installation that requirement vaporized in all cases.

There might be exceptions to companies wanting to run Warp 4. But we have not realy encountered customers wanting to run Warp 4.  The requirement out of the OS/2 community is also very low.

Also from a commercial point of view it makes no sense for us to support Warp 4/MCP.
We would maybe do it if a comoany requires it and they have a fixed installation for a certain application.

But overall there is no demand out of the OS/2 comunnity and not with companies so far.

Roderick Klein
Mensys

rwklein

Quote from: Fahrvenugen on 2012.02.16, 22:02:20
I seem to recall back when ecs first came out, I think there was an option to just install Warp 4.52 or eCS (since eCS essentially is a Warp 4.52 license with the additional eCS stuff added on).  By having the eCS license this allowed you to use any of the eCS specific stuff on after a base 4.52 install (unsupported of course)

I wonder if this would still be a possibility - not that anyone would expect that Mensys would  provide support for such a thing, but for anyone who needs Warp 4.52 with a few of the eCS 2.1  additional items (like ACPI, Flash, etc), if you could purchase a eCS 2.1 license, install a base Warp 4.52 setup, and then just add in yourself the few extras (again, this would be unsupported and meant for the people who really know what they're doing, or people who don't know what they're doing and just like taking risks with their system).  From a licensing standpoint I think as long as you've got the eCS 2.1 license you should be okay doing something like this, but perhaps someone more familiar with the license can clarify.


Certain components are only licensed to run on eComStation. Like the Flash 11 product.

With eCS 1.0 and I think 1.1 came an MCP 2 disc. This was if you wanted to migrate your old Warp/MCP 1 install. I can't even remember. But the complete migration process thats build into Warp 4/MCP is well to say the least completely inferior to whats build into eCS.

While the migration with eCS will vary. The amount of precaitions build into the installer and what it call preserves is far better. Most migration problems occur duo to polluted INI files.

We will in the coming weeks publish a roadmap of eCS 2.11/3.0 what is planned. One new tool that is the pipeline is tool that cleans out dead wood out of your INI files automaticly (please note this being developed and tested by people that know what they are doing!). As some people might be not happy if there INI files are kept clean automaticly. You will also be able to turn off this feature!

But anyway as of eCS 1.1/1.2 the MCP disks went away and we have the migration build into eCS.

Roderick Klein
Mensys

Pete

Hi Roderick

Quote from: rwklein on 2012.02.17, 02:07:45
...
We will in the coming weeks publish a roadmap of eCS 2.11/3.0 what is planned. One new tool that is the pipeline is tool that cleans out dead wood out of your INI files automaticly (please note this being developed and tested by people that know what they are doing!). As some people might be not happy if there INI files are kept clean automaticly. You will also be able to turn off this feature!
...


At last!

That is something that has been missing from OS/2 based systems since the beginning.

I'm looking forward to not having to remember to run checkinin and cleanini every few weeks  :-)

Regards

Pete



Ben

Quote from: Pete on 2012.02.17, 14:41:56
Hi Roderick

Quote from: rwklein on 2012.02.17, 02:07:45
...
One new tool that is the pipeline is tool that cleans out dead wood out of your INI files automaticly (please note this being developed and tested by people that know what they are doing!). As some people might be not happy if there INI files are kept clean automaticly. You will also be able to turn off this feature!
...


At last!

That is something that has been missing from OS/2 based systems since the beginning.

I'm looking forward to not having to remember to run checkinin and cleanini every few weeks  :-)

Regards

Pete


Same here, Pete!

I was looking forward to the new version of Unimaint that Jim Read was working on, but I was sad to learn that Fate was unkind to him; I sincerely hope that he is doing well.

But this is the next best thing WRT OS/2 and INI files, for while I have the cleansing process simplified and smooth after all of these years, I'd much rather not bother with it at all.

R.K. and this new thrust, gets my vote!! (I mean a real vote, not like the fake, political vote, pretending to get a choice between two pre-approved, stinkin'-rich, self-serving, candidates, both painted from the same can of sh*t, and sharing blood.).   :o


Down with Corrupt-and-bloated INIs!!!!

Heheh.

;)