Author Topic: OS/4 Kernel and QSINIT - some more Questions  (Read 6309 times)

Sigurd Fastenrath

  • Sr. Member
  • ****
  • Thank You
  • -Given: 16
  • -Receive: 55
  • Posts: 412
    • View Profile
OS/4 Kernel and QSINIT - some more Questions
« on: September 25, 2014, 02:23:54 pm »
As I do have a clue about the basic things I have to do I would like to add some more features to the QSINIT on the OS/2-4 DVD. Even after reading most of the documentation I still have no idea what I have to do to achieve the following:

- I would like to have QSINIT to display Different OS/2 kernels in the boot menue, especially for the OS/4 kernel
- In combination with this I would like to make it boot with different config.sys files

i.e.:

-Bootoptions:

a - OS/4 Kernel and OS4ACPI
b - OS/4 Kernel without ACPI
c - OS/2 14.106W4 Kernel without ACPI
d - OS/2 14.106SMP Kernel without ACPI
e - OS/2 14.106SMP Kernel with ACPI 3.2203

-> I do know what the config.sys files mostly need to look like and what files are needed in the boot disk, my question is in witch way I have to modifies QSINIT.INI to choose the one I want.

i.e.:

for the options Qsinit (better the OS2LOADER of QSINIT) shall choose

a - OS/4krnl and config.4pa
b - OS/4krnl and config.4wa
c - OS/2krnl and config.uni
d - OS/2krnl and config.spa
e - OS/2krnl and config.swa

(I name the different config.sys like config.4pa wich means to me OS/4 kernel plus ACPI)

Thanks for hints!!








walking_x

  • Jr. Member
  • **
  • Thank You
  • -Given: 3
  • -Receive: 6
  • Posts: 97
    • View Profile
Re: OS/4 Kernel and QSINIT - some more Questions
« Reply #1 on: September 25, 2014, 02:52:01 pm »
Something like this?
OS4KRNL - name of OS/4 kernel file, OS2KRNL - 106W4, OS2KRNL.SMP - 106SMP.
But how resolve UNI/SMP DOSCALLS problem?

[config]
default=3
timeout=5

[kernel]
OS4KRNL = OS/4 Kernel and OS4ACPI, cfgext=4pa
OS4KRNL = OS/4 Kernel without ACPI, cfgext=4wa
OS2KRNL = OS/2 14.106W4 Kernel without ACPI, cfgext=uni
OS2KRNL.SMP = OS/2 14.106SMP Kernel without ACPI, cfgext=spa
OS2KRNL.SMP = OS/2 14.106SMP Kernel with ACPI 3.2203, cfgext=swa

Sigurd Fastenrath

  • Sr. Member
  • ****
  • Thank You
  • -Given: 16
  • -Receive: 55
  • Posts: 412
    • View Profile
Re: OS/4 Kernel and QSINIT - some more Questions
« Reply #2 on: September 25, 2014, 03:21:17 pm »
Something like this?
OS4KRNL - name of OS/4 kernel file, OS2KRNL - 106W4, OS2KRNL.SMP - 106SMP.
But how resolve UNI/SMP DOSCALLS problem?

[config]
default=3
timeout=5

[kernel]
OS4KRNL = OS/4 Kernel and OS4ACPI, cfgext=4pa
OS4KRNL = OS/4 Kernel without ACPI, cfgext=4wa
OS2KRNL = OS/2 14.106W4 Kernel without ACPI, cfgext=uni
OS2KRNL.SMP = OS/2 14.106SMP Kernel without ACPI, cfgext=spa
OS2KRNL.SMP = OS/2 14.106SMP Kernel with ACPI 3.2203, cfgext=swa


Ah - yes, thank you! DOSCALLS1 - that's a good point! For now I will change the "Uni" Kernel therefore with the SMP kernel and add MAXCPU=1 to config.sys.

I still have to sort out in wich way I can modify UPDCD to choose for the later installation process exactly the combination that has been selected before.
But one step after another  ;)
And I am in contact with Zsolt for some things now  ::)

ivan

  • Hero Member
  • *****
  • Thank You
  • -Given: 2
  • -Receive: 35
  • Posts: 1002
    • View Profile
Re: OS/4 Kernel and QSINIT - some more Questions
« Reply #3 on: September 25, 2014, 05:57:53 pm »
There may be a few other files that need changing if you are using the SMP kernel - testcfg, resource and *.psd come to mind. 

walking_x

  • Jr. Member
  • **
  • Thank You
  • -Given: 3
  • -Receive: 6
  • Posts: 97
    • View Profile
Re: OS/4 Kernel and QSINIT - some more Questions
« Reply #4 on: September 25, 2014, 09:20:31 pm »
  I made at least one way now ;)
  New option - CALL. It launch QSINIT batch file when kernel is ready to launch.
  Because MEMDISK is FAT - it can be modified freely by QSINIT :)
  So:

OS4KRNL = OS/4 Kernel and OS4ACPI, cfgext=4pa, call=A:\setupos4.cmd
OS2KRNL = OS/2 14.106W4 Kernel without ACPI, cfgext=uni, call=A:\setupuni.cmd
OS2KRNL.SMP = OS/2 14.106SMP Kernel without ACPI, cfgext=spa, call=A:\setupsmp.cmd

 setupuni.cmd:
copy /q A:\DOSCALL1.UNI A:\DOSCALL1.DLL

 setupsmp.cmd:
copy /q A:\DOSCALL1.SMP A:\DOSCALL1.DLL

 Note - A:\ here because boot drive is A: in QSINIT (it uses own drive letters).

Sigurd Fastenrath

  • Sr. Member
  • ****
  • Thank You
  • -Given: 16
  • -Receive: 55
  • Posts: 412
    • View Profile
Re: OS/4 Kernel and QSINIT - some more Questions
« Reply #5 on: September 25, 2014, 10:48:18 pm »
  I made at least one way now ;)
  New option - CALL. It launch QSINIT batch file when kernel is ready to launch.
  Because MEMDISK is FAT - it can be modified freely by QSINIT :)
  So:

OS4KRNL = OS/4 Kernel and OS4ACPI, cfgext=4pa, call=A:\setupos4.cmd
OS2KRNL = OS/2 14.106W4 Kernel without ACPI, cfgext=uni, call=A:\setupuni.cmd
OS2KRNL.SMP = OS/2 14.106SMP Kernel without ACPI, cfgext=spa, call=A:\setupsmp.cmd

 setupuni.cmd:
copy /q A:\DOSCALL1.UNI A:\DOSCALL1.DLL

 setupsmp.cmd:
copy /q A:\DOSCALL1.SMP A:\DOSCALL1.DLL

 Note - A:\ here because boot drive is A: in QSINIT (it uses own drive letters).

Thanks, downloaded Version 294 :-) -> will give it a try during the weekend

EDIT: do I need the "cfgext" parts as well or can I add to the setupsmp.cmd 'copy /q A:\config.4pa A:\config.sys' so that I always have then the config file named config.sys for the further installation process - or is this done automatically via cfgext?
And I guess it is right that I can add more lines, like some for 'reserve.sys' or any kind of files wicht are needed in different versions but do have the same name?
« Last Edit: September 26, 2014, 07:39:54 am by Sigurd Fastenrath »

walking_x

  • Jr. Member
  • **
  • Thank You
  • -Given: 3
  • -Receive: 6
  • Posts: 97
    • View Profile
Re: OS/4 Kernel and QSINIT - some more Questions
« Reply #6 on: September 26, 2014, 02:06:23 pm »
And I guess it is right that I can add more lines, like some for 'reserve.sys' or any kind of files wicht are needed in different versions but do have the same name?
Yes, of course.
CFGEXT is common solution, it makes patches in loaded kernel data.
This required because there is no way to change HPFS/JFS during boot time (other than write a real driver for both).

But with FAT we can do everything :)
So you can use common batch syntax here (echo, pause, or just "cmd" - to type dir and so on... ;)).
At this time the kernel is already loaded, but not started - and these operations do not touch it.

Sigurd Fastenrath

  • Sr. Member
  • ****
  • Thank You
  • -Given: 16
  • -Receive: 55
  • Posts: 412
    • View Profile
Re: OS/4 Kernel and QSINIT - some more Questions
« Reply #7 on: September 28, 2014, 08:44:51 am »
Hi,

I think I do make some progress, will publish a video about it so far this evening  ::)

As allways I do have some more questions - just as these things occur as I go on -- I do hope to do not bother here!

1. I wanted to add switches like "ALT+F2" and "ALT+F4" to the lines in os2loader.ini as arguments -> is this possible and do I have to use quotes? I tried it just like this:
os2krnl=OS/2 Kernel 106W4, cfgext=104, ALT+F2
but it does not react. During boot it shows something like "cannot find the argument -> "

2. In the "F9" apps menue there is the funciton "Diskmenue". After a short while I get used to it - is FAT32 the only option to "Format" a partition or what is needed to have the possibility to use HPFS or/and JFS instead?

Thank you very much in advance!

Sigurd

walking_x

  • Jr. Member
  • **
  • Thank You
  • -Given: 3
  • -Receive: 6
  • Posts: 97
    • View Profile
Re: OS/4 Kernel and QSINIT - some more Questions
« Reply #8 on: September 28, 2014, 10:50:13 am »
1. I wanted to add switches like "ALT+F2" and "ALT+F4" to the lines in os2loader.ini as arguments -> is this possible and do I have to use quotes? I tried it just like this:
os2krnl=OS/2 Kernel 106W4, cfgext=104, ALT+F2
but it does not react. During boot it shows something like "cannot find the argument -> "
ALTF2 - without space. In OS/4 archive there is a file "os2ldr.read.me" - QSINIT share all these options with OS/4.

Quote
2. In the "F9" apps menue there is the funciton "Diskmenue". After a short while I get used to it - is FAT32 the only option to "Format" a partition or what is needed to have the possibility to use HPFS or/and JFS instead?
Format is self-implemented - I can`t call OS/2 version of format utilites :) So it format partition to FAT/FAT32 (depends on size).

I'm thinking about HPFS format, but this still too complex task. Any way, this is not a large problem, because no access to HPFS volumes (loader is able only read files from the root directory).

FAT/FAT32 - can be created, written, xcopy-ied and so on - so acts as target for temporary storage, for example. When I tried to move huge amount of files between 2 FAT32 partitions - it was faster, than in our famous FAT32.IFS :D

Sigurd Fastenrath

  • Sr. Member
  • ****
  • Thank You
  • -Given: 16
  • -Receive: 55
  • Posts: 412
    • View Profile
Re: OS/4 Kernel and QSINIT - some more Questions
« Reply #9 on: September 28, 2014, 11:51:41 am »
Thank you very much!

I guess it it not necessary to have HPFS - it is OK that I can create partitions and the OS/2 Installation process can recognize that there are partitions/LVMVolumes

I will show all of this in the upcoming video, please take a look at it later (I will post the link to it once it is finished) and correct me in case of errors or misunderstanding.

 ;) 8) ::)

Sigurd Fastenrath

  • Sr. Member
  • ****
  • Thank You
  • -Given: 16
  • -Receive: 55
  • Posts: 412
    • View Profile
Re: OS/4 Kernel and QSINIT - some more Questions
« Reply #10 on: November 17, 2015, 12:54:51 pm »
I am still experimenting with this and do have a problem now, hope to geht help and advice - thanks in advance!

I am Using:

QSINIT Loader Version 360, dated 2015-10-10
OS/4 Kernel Version 4473

This is what the OS2LDR.INI contains for OS/4 (i.e.):

os4krnl=OS/4 Kernel 4473 mit OS/4 ACPI, cfgext=o4a, call=A:\setupos4.cmd

This is what setupos4.cmd looks like:

copy /q A:\DOSCOS41.DLL A:\DOSCALL1.DLL
copy /q A:\harderr.smp A:\harderr.exe
copy /q A:\sesdd32.smp A:\sesdd32.sys


(All files are in place)

When I start and select this then I get the errormessage:

unable to open batchfile "A:\setupos4.cmd"

What do I miss?




« Last Edit: November 17, 2015, 12:58:03 pm by Sigurd Fastenrath »

Doug Bissett

  • Hero Member
  • *****
  • Thank You
  • -Given: 1
  • -Receive: 46
  • Posts: 1231
    • View Profile
Re: OS/4 Kernel and QSINIT - some more Questions
« Reply #11 on: November 18, 2015, 04:05:31 am »
Quote
unable to open batchfile "A:\setupos4.cmd"

I am not clear about exactly how you have this set up, but "drive A:" only works for FAT boot drives (or possibly FAT32, which probably won't work with OS/2). In my test system, my boot drive is JFS. If I drop to a QSINIT command line at boot, there is no A: drive. It says "Device not mounted". If it is a FAT drive, you need to mount it before you can use it (that may be done automatically for a FAT drive). Trying to mount a JFS drive appears to work, but it says it is not mounted if I try to use it. I expect that trying a HPFS drive would do the same.

Sigurd Fastenrath

  • Sr. Member
  • ****
  • Thank You
  • -Given: 16
  • -Receive: 55
  • Posts: 412
    • View Profile
Re: OS/4 Kernel and QSINIT - some more Questions
« Reply #12 on: November 18, 2015, 08:24:37 am »
Quote
unable to open batchfile "A:\setupos4.cmd"

I am not clear about exactly how you have this set up, but "drive A:" only works for FAT boot drives (or possibly FAT32, which probably won't work with OS/2). In my test system, my boot drive is JFS. If I drop to a QSINIT command line at boot, there is no A: drive. It says "Device not mounted". If it is a FAT drive, you need to mount it before you can use it (that may be done automatically for a FAT drive). Trying to mount a JFS drive appears to work, but it says it is not mounted if I try to use it. I expect that trying a HPFS drive would do the same.

Hi Doug,

thanks for this, what makes me wonder is that this worked before, QSINIT automatically grabbs Drive letter a: (see above posts) I still can not figure out what I might have changed. Everything else with QSINIT is working fine, i.e. booting the 14.106SMP Kernel works without issues. May be the "call" order is somehow broken with newer QSINIT. I hope to get some response or hint from the developer.

walking_x

  • Jr. Member
  • **
  • Thank You
  • -Given: 3
  • -Receive: 6
  • Posts: 97
    • View Profile
Re: OS/4 Kernel and QSINIT - some more Questions
« Reply #13 on: November 18, 2015, 11:13:00 am »
  A: is always mounted. When volume is FAT - its usable, for JFS & HPFS mounting gives some options too -  format, bpb dump...
  Nothing was changed in this part, i checked it - and it works (at least, on my test FAT volume ;)). Is cmd file really visible? Check it in QSINIT shell:
    dir a:\*.cmd
  because it looks absent (may be some FAT/disk image problems?)

Sigurd Fastenrath

  • Sr. Member
  • ****
  • Thank You
  • -Given: 16
  • -Receive: 55
  • Posts: 412
    • View Profile
Re: OS/4 Kernel and QSINIT - some more Questions
« Reply #14 on: November 18, 2015, 02:39:41 pm »
Hi Walking_X,

that is what it looks like if I do like you suggested.

So ist seems not to be there. May I placed the setup.cmd in the wrong place (here it resides on root of drive c:) ?

Thanks!