Author Topic: Need help with QSINIT  (Read 19691 times)

karotlopj

  • Guest
Re: Need help with QSINIT
« Reply #15 on: June 02, 2016, 03:20:27 pm »
Just to be clear  what to expect.... These are the files I have in pxeroot:-

Quote
OS2KRNL            @#IBM:14.106#@_SMP  IBM OS/2 Kernel
hpfsmini.fsd
OS2LDR.INI
qssetup.cmd
QSINIT.LDI
OS2LDR              @#QS:0.17.0380#@  QSinit loader


OS2LDR.INI
Quote
[config]
default=1
timeout=15
[kernel]
os2krnl=Default boot
os2krnl=Show driver names, ALTF2
OS2LDR.OLD=Original boot, RESTART

qssetup.cmd
Quote
echo hello

dir

pause

RAMDISK Q:


What should I expect to see when I press [enter]  - 1. Default boot  to see if qssetup.cmd has done anything?

karotlopj

  • Guest
Re: Need help with QSINIT
« Reply #16 on: June 02, 2016, 03:29:54 pm »
I changed qssetup.cmd to uppercase and it works now....

Now, how do I boot OS/2 from this environment? I have a zipped up minimal OS/2 partition.

What do I call it and where should it go?

Doug Bissett

  • Hero Member
  • *****
  • Posts: 1593
  • Karma: +4/-2
    • View Profile
Re: Need help with QSINIT
« Reply #17 on: June 02, 2016, 07:45:48 pm »
I changed qssetup.cmd to uppercase and it works now....

Now, how do I boot OS/2 from this environment? I have a zipped up minimal OS/2 partition.

What do I call it and where should it go?

Read the last section of PAEDISK.TXT. It is a little more complicated than what you need, but it tells you exactly what to do.

walking_x

  • Full Member
  • ***
  • Posts: 101
  • Karma: +0/-0
    • View Profile
Re: Need help with QSINIT
« Reply #18 on: June 04, 2016, 08:52:06 am »
Read the last section of PAEDISK.TXT.
This is a good advice, I think ;)
Actually, you need something like this:

    RAMDISK Q: min=100 max=1900
    echo unzipping...
    unzip /q /boot FATOS2.ZIP c:\

"min" parameter should be larger, than your unzipped data size (i.e. it guarantee such disk size, even if no memory above 4Gb for it).

Unzip command here will download and unzip archive to ramdisk. Since this point you can modify disk data in QSINIT (for ex., edit config.sys in QSINIT`s text editor).

additional line into OS2LDR.INI
    [config]
    source=c

and additional line into CONFIG.SYS in zip, it must be ABOVE all storage drivers (danis, ahci, scsi) - to get priority in drive letter assignment (in case of conflicts).

    BASEDEV=HD4DISK.ADD

Put your FATOS2.ZIP to tftp and try.

Dave Yeo

  • Hero Member
  • *****
  • Posts: 4786
  • Karma: +99/-1
    • View Profile
Re: Need help with QSINIT
« Reply #19 on: June 04, 2016, 09:10:55 am »
Will the RAM disk work with less then 4GBs of ram installed?

walking_x

  • Full Member
  • ***
  • Posts: 101
  • Karma: +0/-0
    • View Profile
Re: Need help with QSINIT
« Reply #20 on: June 04, 2016, 10:13:24 am »
Yes, "min" parameter is, practically, memory size, which cut off from memory below 4Gb - to create disk with guaranteed size.
And "max" - will cut usage memory above 4gb (to stay in FAT 2Gb limit).

Ramdisk can be compounded from both memory types, actually - if you ask min=1000 on 4Gb PC, where only 700mb is mapped above 4Gb limit.
« Last Edit: June 04, 2016, 11:10:41 am by walking_x »

karotlopj

  • Guest
Re: Need help with QSINIT
« Reply #21 on: June 05, 2016, 08:37:21 am »
Read the last section of PAEDISK.TXT.
This is a good advice, I think ;)
Actually, you need something like this:

    RAMDISK Q: min=100 max=1900
    echo unzipping...
    unzip /q /boot FATOS2.ZIP c:\

"min" parameter should be larger, than your unzipped data size (i.e. it guarantee such disk size, even if no memory above 4Gb for it).

Unzip command here will download and unzip archive to ramdisk. Since this point you can modify disk data in QSINIT (for ex., edit config.sys in QSINIT`s text editor).

additional line into OS2LDR.INI
    [config]
    source=c

and additional line into CONFIG.SYS in zip, it must be ABOVE all storage drivers (danis, ahci, scsi) - to get priority in drive letter assignment (in case of conflicts).

    BASEDEV=HD4DISK.ADD

Put your FATOS2.ZIP to tftp and try.


Thanks. I have it working now. At least it boots up to a command prompt.
It's amazing to see it working.

I'll have to see if I can perform an installation using this method.

Greggory Shaw

  • Sr. Member
  • ****
  • Posts: 442
  • Karma: +0/-0
    • View Profile
Re: Need help with QSINIT
« Reply #22 on: June 05, 2016, 10:02:29 am »

Thanks. I have it working now. At least it boots up to a command prompt.
It's amazing to see it working.

I'll have to see if I can perform an installation using this method.

Could you list the steps, I would like to put together an article on my site ?

Greggory

karotlopj

  • Guest
Re: Need help with QSINIT
« Reply #23 on: June 05, 2016, 02:51:58 pm »

Thanks. I have it working now. At least it boots up to a command prompt.
It's amazing to see it working.

I'll have to see if I can perform an installation using this method.

Could you list the steps, I would like to put together an article on my site ?

Greggory

To be quite honest, the hardest part is getting the DHCP/PXE server environment setup especially when you don't really know how it all works and what to do when it doesn't work. A great deal of trial and even more error was involved before I got it working.

As for the capabilities of PXE booting Qsinit and installing OS/2 from scratch, that is something I will be exploring in the coming days and weeks. I've only just got it working and am finding my way around. I wouldn't have been able to do it without help from the good folks on this forum.

karotlopj

  • Guest
Re: Need help with QSINIT
« Reply #24 on: June 12, 2016, 04:46:09 pm »
I've been booting using PXE/QSINIT for about a week now and find it to be a really useful way of access the local hard disk without booting from it. I do have occasional problems though...

Is a local hard disk necessary to be able to boot? I thought that the ramdisk created would be sufficient.

Also what are the requirements for the local hard disk? If it is a brand new disk, unpartitioned and unformatted will QSINIT boot?

Just now, I've found that booting has stopped with...

Invaild primary partition type 00h
Fatal error: failed to read boot block
Press any keyto finish NBP

I am able to boot from the local hard disk so am somewhat confused by this message.

walking_x

  • Full Member
  • ***
  • Posts: 101
  • Karma: +0/-0
    • View Profile
Re: Need help with QSINIT
« Reply #25 on: June 13, 2016, 08:44:58 am »
This is PXEOS4 own handling, just comment it out with #, this should force it to ignore hard disk:

#device-id=128 # first HDD
#device-part=0 # 0 - non partitioned, 1-4 - primary, 5+ - extended
#drive=K # boot drive letter

And make sure you are using the latest PXEOS4 version (08.2013, probably) - in earlier versions disk was demanded in any way.
« Last Edit: June 13, 2016, 08:50:35 am by walking_x »

karotlopj

  • Guest
Re: Need help with QSINIT
« Reply #26 on: June 13, 2016, 11:20:11 am »
This is PXEOS4 own handling, just comment it out with #, this should force it to ignore hard disk:

#device-id=128 # first HDD
#device-part=0 # 0 - non partitioned, 1-4 - primary, 5+ - extended
#drive=K # boot drive letter

And make sure you are using the latest PXEOS4 version (08.2013, probably) - in earlier versions disk was demanded in any way.

What should I have in QSSETUP.CMD and OS2LDR.INI if I have no disk mounted?

Incidentally my PXE bootfile is gpxelinux.0 from SYSLINUX. That gives me the option of creating a nice boot menu where I can include numerous other progams such SystemRescue, PMagic, Clonezilla or boot a live Linux system among many other things.

walking_x

  • Full Member
  • ***
  • Posts: 101
  • Karma: +0/-0
    • View Profile
Re: Need help with QSINIT
« Reply #27 on: June 13, 2016, 12:09:36 pm »
Nothing special - QSINIT does not depend on disk presence.
At least itself, it requires a source to boot OS/2, of course - ramdisk or real disk.

karotlopj

  • Guest
Re: Need help with QSINIT
« Reply #28 on: June 13, 2016, 02:20:38 pm »
Just to let anyone know who is interested, I have now developed a minimal FATOS2.ZIP containing:-
Quote
\chkdsk.sys
\config.sys
\country.sys
\delivery.sys
\DLL
\dos.sys
\hd4disk.add
\isapnp.snp
\kbdbase.sys
\KEYBOARD.DCP
\mouse.sys
\OS2
\pmdd.sys
\pnp.sys
\pointdd.sys
\reserve.sys
\resource.sys
\testcfg.sys
\viotbl.dcp
\DLL\ansicall.dll
\DLL\bkscalls.dll
\DLL\bmscalls.dll
\DLL\bvhinit.dll
\DLL\bvhvga.dll
\DLL\bvscalls.dll
\DLL\chkdsk32.dll
\DLL\DOSCALL1.DLL
\DLL\kbdcalls.dll
\DLL\lvm.dll
\DLL\moucalls.dll
\DLL\msg.dll
\DLL\nampipes.dll
\DLL\nls.dll
\DLL\npxemltr.dll
\DLL\os2char.dll
\DLL\quecalls.dll
\DLL\sesmgr.dll
\DLL\uhpfs.dll
\DLL\ujfs.dll
\DLL\viocalls.dll
\OS2\BOOT
\OS2\CHKDSK.COM
\OS2\CHKDSK32.EXE
\OS2\cmd.exe
\OS2\harderr.exe
\OS2\BOOT\altf2on.$$$
\OS2\BOOT\clock01.sys
\OS2\BOOT\danis506.add
\OS2\BOOT\ibmkbd.sys
\OS2\BOOT\os2dasd.dmd
\OS2\BOOT\os2lvm.dmd
\OS2\BOOT\screen01.sys

Some of these files may well be redundant. Let me know if you think anything can be removed.

where CONFIG.SYS contains:-

Quote
BASEDEV=HD4DISK.ADD
basedev=ibmkbd.sys
basedev=danis506.add /v
basedev=os2dasd.dmd
basedev=os2lvm.dmd

buffers=32
iopl=yes

memman=noswap, protect
protshell=\os2\cmd.exe
set os2_shell=\os2\cmd.exe

protectonly=yes
libpath=.;\;\DLL;
set path=\;\os2
pauseonerror=no

COUNTRY=044,\COUNTRY.SYS
CODEPAGE=850,437
DEVINFO=KBD,UK166,\KEYBOARD.DCP
DEVINFO=SCR,VGA,\VIOTBL.DCP
set dpath=.;\OS2;\;
set keys=on

This boots up on an old Thinkpad T42 in around 9 secs. This only boots up to command prompt so isn't all that useful, but provides o good base on which to build.