OS/2, eCS & ArcaOS - Technical > Setup & Installation

Final Request for Help for the Final Warp 4 Image Clone

<< < (5/6) > >>

walking_x:
And Martin - I can publish code, in the future :)
It least, when I will be tired of it ;) Or when IBM publish the sources (because my loader is much more usable, than IBM`s ;)) I'm not planning to sit on sources until the end of time ;)

p.s. again - there are TWO alternative loaders: OS/4 and QS (my project) and I can tell only for myself.

Martin Iturbide:
Thanks walking_x

It is good to know that the door is open for discussion.  I didn't know you were the author of QSLoader, thanks for creating it.

Regards.

Sigurd Fastenrath:

--- Quote from: walking_x on April 09, 2013, 05:09:37 pm ---Ok, I am - an author of "QSINIT" - another one kernel loader (NOT OS/4). And I can tell only for myself: this loader was written from scratch (it has completely another structure and features). And I will not publish it under GNU licence :) Though I made this project for fun - it takes 3 years from me - and I won't grant its code to you, especially you.

--- End quote ---

I did test this Loader Yesterday as well. It worked OK but - as with the OS/4 Loader, even worse the eCS OS2LDR - I still have this weird boot hangs, I guess this is an ACPI/Memory/Driver conflict issue. This loader (was not hard to find with using google for QSINIT) reports the right amount of Memory as well, same as the OS/4 where eCS Loader fail. When "Loading" the loader offers a to switch via F9 to a menue but I did not test it.

I did install Suse Linux 12.3 alongside OS/2 and Windows 8 Pro, with AirBootManager I do have a triple boot Tablet yet.

I did look further into the sound problem as well - as the driver allways loads I still have sometimes sound, sometimes not. With the "unimix -list" and "unimix -card" commands I did receive this:
-----------------------------------------------------------
Command line mixer for UNIAUD32. Version 1.0
Detected UNIAUD version 20.20
Control ID: 1
Interface: virtual mixer device
Device(client): 0, subdevice (substream) 0
Name: [Speaker Playback Volume]
Index: 0
Element type: integer type
Count of values: 2
Value:
Bounds: min: 0, max: 87, step: 0
value 0: 87
value 1: 87
Control ID: 2
Interface: virtual mixer device
Device(client): 0, subdevice (substream) 0
Name: [Speaker Playback Switch]
Index: 0
Element type: boolean type
Count of values: 2
Value:
Bounds: min: 0, max: 1, step: 0
value 0: 1
value 1: 1
Control ID: 3
Interface: virtual mixer device
Device(client): 0, subdevice (substream) 0
Name: [Headphone Playback Volume]
Index: 0
Element type: integer type
Count of values: 2
Value:
Bounds: min: 0, max: 87, step: 0
value 0: 80
value 1: 80
Control ID: 4
Interface: virtual mixer device
Device(client): 0, subdevice (substream) 0
Name: [Headphone Playback Switch]
Index: 0
Element type: boolean type
Count of values: 2
Value:
Bounds: min: 0, max: 1, step: 0
value 0: 1
value 1: 1
Control ID: 5
Interface: virtual mixer device
Device(client): 0, subdevice (substream) 0
Name: [Internal Mic Boost Volume]
Index: 0
Element type: integer type
Count of values: 2
Value:
Bounds: min: 0, max: 3, step: 0
value 0: 0
value 1: 0
Control ID: 6
Interface: virtual mixer device
Device(client): 0, subdevice (substream) 0
Name: [Mic Boost Volume]
Index: 0
Element type: integer type
Seite 1
unimix09042013
Count of values: 2
Value:
Bounds: min: 0, max: 3, step: 0
value 0: 0
value 1: 0
Control ID: 7
Interface: virtual mixer device
Device(client): 0, subdevice (substream) 0
Name: [Capture Switch]
Index: 0
Element type: boolean type
Count of values: 2
Value:
Bounds: min: 0, max: 1, step: 0
value 0: 0
value 1: 0
Control ID: 8
Interface: virtual mixer device
Device(client): 0, subdevice (substream) 0
Name: [Capture Volume]
Index: 0
Element type: integer type
Count of values: 2
Value:
Bounds: min: 0, max: 63, step: 0
value 0: 23
value 1: 23
Control ID: 9
Interface: virtual mixer device
Device(client): 0, subdevice (substream) 0
Name: [Master Playback Volume]
Index: 0
Element type: integer type
Count of values: 1
Value:
Bounds: min: 0, max: 87, step: 0
value 0: 87
Control ID: 10
Interface: virtual mixer device
Device(client): 0, subdevice (substream) 0
Name: [Master Playback Switch]
Index: 0
Element type: boolean type
Count of values: 1
Value:
Bounds: min: 0, max: 1, step: 0
value 0: 1
[C:\mmos2]unimix -names
Command line mixer for UNIAUD32. Version 1.0
Detected UNIAUD version 20.20
ID: 1, name: [Speaker Playback Volume]
ID: 2, name: [Speaker Playback Switch]
ID: 3, name: [Headphone Playback Volume]
ID: 4, name: [Headphone Playback Switch]
ID: 5, name: [Internal Mic Boost Volume]
ID: 6, name: [Mic Boost Volume]
ID: 7, name: [Capture Switch]
ID: 8, name: [Capture Volume]
ID: 9, name: [Master Playback Volume]
ID: 10, name: [Master Playback Switch]
-------------------------------------------------------------------------


 so I modified my startup.cmd to this:


-------------------------------------------------------------------------
REM NET START REQ
REM @if errorlevel 2 C:\IBMLAN\NETPROG\lserr.exe
c:\mmos2\unimix -id1 -cnt0 -val87 -cnt1 -val87
c:\mmos2\unimix -id2 -cnt0 -val1 -cnt1 -val1
c:\mmos2\unimix -id3 -cnt0 -val87 -cnt1 -val87
c:\mmos2\unimix -id4 -cnt0 -val1 -cnt1 -val1
c:\mmos2\unimix -id5 -cnt0 -val3 -cnt1 -val3
c:\mmos2\unimix -id6 -cnt0 -val3 -cnt1 -val3
c:\mmos2\unimix -id7 -cnt0 -val1 -cnt1 -val1
c:\mmos2\unimix -id8 -cnt0 -val63 -cnt1 -val63
c:\mmos2\unimix -id9 -cnt0 -val87
c:\mmos2\unimix -id10 -cnt0 -val1
EXIT
---------------------------------------------------------------------

Sometimes the startup.cmd fails to set the values for some IDS, sometimes not, I guess this is where I get sound or not.
The (wihtout a problem) running Linux Installation did show me as well to have two Audio Adapters, The "Intel Display Audio 2805" - that is allways shown by UNIAUD Driver - and the Realtek HD269 - where the Microfone etc. are connected with.
I guess sometimes uniaud is loading both devices (but even while having sound the microfone does not work)  sometimes not.

Is there a way to load the UNIAUD driver twotimes?

And some very good news: Two finger touch is working as well now, thanks to Wim!  :-)

walking_x:
BIOS on EFI motherboards have a tonns of bugs ;) I've tested one on B75 chipset - and SPACE key in Installation CD initial setup (in text mode) was not working until BIOS update ;)
Trap can be caused by multiple reasons:
  * on later stages (just before PM) - new panorama + ACPI.
  * immediately after start - memory issues (list of usable memory in these BIOSes is some kind of chaos ;) - still thinking how to check it before use).

Another problem is - new APCIs patch something in IBM loader, or get some data from hardcoded offsets in it - and unable to do the same with alternative loaders. This is a bad method, when code is nailed up to 104 or 105_SMP kernel and loader.
I saw messages about successful results with /VW key only, i.e.:

    alternative loader + IBM kernel + new ACPI.PSD /VW

Sigurd Fastenrath:
I already had to use /VW switch as otherwise the boot process failed with "OS2AHCI can not reserve IRQ 19 - already claimed". I experimented with different kernel/loaders, the best results so far I get with OS/4 Loader + Kernel 104a_SMP.

Some other news:

- Wim gave me the merged Touch+Stylus Driver yesterday so that it is working right not with both at the same time - all credits to Wim for his - once again - splendid work!

- I think I can have less problems with Driver Loading during boot process if I can slow down the boot process a bit. The boot process with HPFS386 takes on this SSD only about 12 seconds, I guess it is just to quick to let OS/2 load all drivers, especially the whole sound driver. I already realized that some kind of "halt" was used with eCS 2.2 config.sys, I just have to take a closer look at this as I do not have eCS 2.2 running right now

- The LAN chip (RTL8169 with Mensys Multimac Driver) works very good when pluged into the Docking Station. But - once I want to start the Slate outside the docking station Boot Process stops while trying to load the RTL driver and needs an "ENTER". This does not happenend last year with eCS 2.1, the boot process continued with loading even if the LAN chip can not be seen be eCS. I have to take a closer look at this as well to get rid of this problem.

- At the weekend I will give WLAN another try :-)

Suggestions, hints, comments are highly appreciated!

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version