Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Sigurd Fastenrath

Pages: 1 ... 27 28 [29] 30 31 ... 39
421
Setup & Installation / Re: OS/4 Kernel and QSINIT - some more Questions
« 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) ::)

422
Setup & Installation / Re: OS/4 Kernel and QSINIT - some more Questions
« 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

423
Setup & Installation / Re: OS/4 Kernel and QSINIT - some more Questions
« 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?

424
Setup & Installation / Re: OS/4 Kernel and QSINIT - some more Questions
« 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  ::)

425
Setup & Installation / 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!!








426
Setup & Installation / Re: Need help with QSINIT Loader
« on: September 24, 2014, 04:55:35 pm »
Hi Sigurd,

Quote
It turned out that UPDCD produces the bootdisk.scr only for a short duration of time, pointing from there to the \tmp directory, that is as well only there for a short time in \UPDCD\BURN\BOOTIMGS - just to build the BOOTDISK.PF - and then both will be automatically deleted by the program.

I rememberd the way I took to change and modify the config.sys - (please see my thread at the german forum) - by adding a 'pause' command in the \UPDCD\LIB\updif.rlb - so I looked for the part, right before the bootdiskfiles are copied from the tmp directory.

So the program stopped as I wanted and I then copied the files I wanted to add to the \tmp directory and then continued the UPDCD process. Later I did as before as well - copying the files to DISK_0 and packed them, to complete the procedure.

Are you sure that the program stopped where you wanted? When I look at bootdisk1.png it seems to me that you paused after packing \temp into bootdisk.pf and your add to the \tmp directory has been done in vain.

Regards, Wim.

Hi Wim,

I have to apologize - you have been right! After looking at bootdisk1.png again I realized that this was an to early screenshot - in fact I changed the 'pause' to another line once I realized it did not work this way. I thought I attached the right screenshot, but it was wrong. Here it is attached.

Thanks again!

Sigurd

427
Setup & Installation / Re: Need help with QSINIT Loader - SUCCESS!!!!!!
« on: September 24, 2014, 08:40:37 am »
Thank you very much,

yes - I have to make a lot of minor and major changes still to do, but first of all I am trying to get in Contact with Zsolt Kaddar now, the author of UPDCD.

428
Setup & Installation / Re: Building an OS/4 Merlin DVD - FIRST BOOT!!!
« on: September 23, 2014, 08:48:54 pm »
Oh yeah, the basic system is up and running - please see the qsinit thread  8)

429
Setup & Installation / Re: Need help with QSINIT Loader - SUCCESS!!!!!!
« on: September 23, 2014, 08:34:47 pm »
And more....

430
Setup & Installation / Re: Need help with QSINIT Loader - SUCCESS!!!!!!
« on: September 23, 2014, 08:33:22 pm »
More pictures, and yes - the installation does start - but I have to see if it will finish   ::)

431
Setup & Installation / Re: Need help with QSINIT Loader - SUCCESS!!!!!!
« on: September 23, 2014, 08:31:26 pm »
Oh Baby I have got it!! 8) 8)!!!!

Replacing the changed membootfiles with thos form UPDCD did it!!!!!!
What a superb feeling!!!

I can now boot the Installation DVD and Enter the QSINIT Menue with all the benefits!! I can inspect the HDD, delete and add partitions, check the ACPI Table, the PCI ..... and play Tetris!!!

Das ist der absolute HAMMER!!!   8) ;D ;D ;D ;D ;D

I attach some pictures taken while booting the X200 Tablet PC.

I will write more when I calm down a bit  :D :D :D :D

Thanks for all your support! Now I have got a really god base to try more!!!!


432
Setup & Installation / Re: Need help with QSINIT Loader
« on: September 23, 2014, 06:42:08 pm »
Since OS2CSM.BIN does not appear on any of my CD/DVDs I have to ask where did you get it from and what is it supposed to do?

You could also try removing it and see if that allows you to book from the CD/DVD.

I guess it has something to do with UPDCD and the bootprocess - it is a file that seems to be created and placed in the bootdisk.pf

http://www.os2world.com/past-news/80-software/3422-

As this problem did not occur before I think I will revome the changes I made to UPDCD with the memdisk files I updated.

433
Setup & Installation / Re: Need help with QSINIT Loader
« on: September 23, 2014, 01:05:49 pm »
Hi all,

first I have to apologize - I made so many attemps now. with each one producing the file temp.raw_00 wich I had to burn, that the last time I mixed them up  :-\

The same error message occured simply because I burned the same raw image as before...

I noticed this in the morning and burned the "rigt" new one that I built yesterday.
Once I started to boot this DVD it did stop even earlier than the one before, stating that:

OS2CSM.BIN is corrupted EDIT: this file is contained in bootdisk.pf and is 42 byte

- please see attached picture.

What might went wrong this time?

@Wim: Thanks for looking at this as well, I just placed the 'pause' where I thought it might make sense as I am not familiar with the Rexx commands used there - where would you place the command? But as far as I can see it did work - please see the screenshot of my last post (bootdisk6.png), where I did use e_pf.exe to extract the "new" bootdisk.pf I created right before with UPDCD. All the files I copied (i.e. QSINIT.LDI, hd4disk.add etc.) have been included.

Please note: at the screenshot below you can see that I already included memdisk files from 2009, and for me the German version  :)

Thanks to all of you - I am really hopefull to achieve my goal during the next time - thanks to your help!

Once I have finished all this I will ask Zsolt Kaddar if it is possible and allowed if he - or someone else - might include and automate these steps with an addition to UPDCD.
 

434
Setup & Installation / Re: Need help with QSINIT Loader
« on: September 22, 2014, 09:28:24 pm »
Hi Sigurd,

Could you post a list of the files in your bootdisk.pf?  There has to be either something missing or something causing a conflict.  Also did you unpack the memdisk from the iso Walking_X made and compared it with what you have?

Hi Ivan,

files - please see attached picture

iso - no, sorry, did not unpack it so far, will try tomorrow.


435
Setup & Installation / Re: Need help with QSINIT Loader
« on: September 22, 2014, 02:12:41 pm »
Hi Alex,
Ivan,
Walking_X

thank you very much for your hints and contribution - it is really appreciated!!

As it seemed to be to hard for me to get used to memboot and the .pf files I was thinking about the process of UPDCD. It came to my mind that - if UPDCD produces a bootdisk.pf - there must be a script bootdisk.scr somewhere.
But I was not able to find it in the UPDCD directory.
Therefore I looked into the UPDCD.LOG of my last attempt and searched for bootdisk.
And yes - I found some lines regarding this.  :D

It turned out that UPDCD produces the bootdisk.scr only for a short duration of time, pointing from there to the \tmp directory, that is as well only there for a short time in \UPDCD\BURN\BOOTIMGS - just to build the BOOTDISK.PF - and then both will be automatically deleted by the program.

I rememberd the way I took to change and modify the config.sys - (please see my thread at the german forum) - by adding a 'pause' command in the \UPDCD\LIB\updif.rlb - so I looked for the part, right before the bootdiskfiles are copied from the tmp directory.

So the program stopped as I wanted and I then copied the files I wanted to add to the \tmp directory and then continued the UPDCD process. Later I did as before as well - copying the files to DISK_0 and packed them, to complete the procedure.

So, I do have a new DVD now - I will burn it and give it a try! 

Let's see if this brings me one step ahead or...

@Walking_X: OS2BOOT is already inlcuded in the bootdisk.pf by UPDCD - I checked it.

 8)

EDIT: No - still the same error message..... I checked the bootdisk.pf -> extracted it with e_pf.exe -> the files QSINIT.LDI and so on are all included, so the way I packed them into the bootdisk.pf did work, but still there is something missing....
Will check later.

Pages: 1 ... 27 28 [29] 30 31 ... 39