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 - walking_x

Pages: 1 2 [3] 4 5 ... 7
31
Setup & Installation / Re: OS/4 Kernel and QSINIT - some more Questions
« 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

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

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

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

35
Setup & Installation / Re: Need help with QSINIT Loader - SUCCESS!!!!!!
« on: September 24, 2014, 12:23:28 am »
Yes, congratulations :)
But how you got this funny line number 4? I think - this must be fixed ;)

36
Setup & Installation / Re: Need help with QSINIT Loader
« on: September 23, 2014, 07:06:24 pm »
OS2CSM.BIN is "config.sys" editor implementation (like in eCS CD).
Why boot process ask for it? It was selected somewhere in setup?

37
Setup & Installation / Re: Need help with QSINIT Loader
« on: September 22, 2014, 12:48:11 pm »
In no-emulation-boot mode - both QSINIT (named as OS2LDR) and QSINIT.LDI must be in the root of memdisk (at least I made it this way in my test).
OS2LDR.INI is optional.

But, QSINIT has another one questionable feature ;) It detects "OS/2 boot mode" on FAT by presence of OS2BOOT file in the same root. If file missing - "QSINIT without OS/2" assumed (on FAT or FAT32) and own "Apps Menu" (green) will be opened.
So if OS2BOOT missing on ramdisk - you can create a small one in text editor (with some spaces inside) - it not required for boot, but acts as a "flag".

38
Setup & Installation / Re: Need help with QSINIT Loader
« on: September 20, 2014, 10:33:50 pm »
Here is the picture:
Hm, you use memboot, it creates "pseudo-hdd" and something going wrong...
I will try to make simple memboot disk and check what it is.

p.s. checked it and it works :)
You can try "3a.ISO" in public dir of QSINIT ftp - it creates 16Mb MEMDISK and boot to cmd.exe.
So, may be QSINIT.LDI is missing in script for memdisk archives?

39
Setup & Installation / Re: Need help with QSINIT Loader
« on: September 20, 2014, 06:30:49 pm »
Update: sorry, the same result with 289 and 291, same error message.
Is there some new lines on screen with verbose 289 build?
Or, can you send me image file of first diskette?

40
Setup & Installation / Re: Need help with QSINIT Loader
« on: September 20, 2014, 11:43:23 am »
Or you can try last (today's) version  - I made some fixes in floppy detection, to let it ignore errors in emulation :)

41
Setup & Installation / Re: Need help with QSINIT Loader
« on: September 20, 2014, 07:40:49 am »
EDIT: May it be that QSINIT.LDI is on the DVD a "Read only file" and can therefore not been unzipped during boot? Just a shot in the dark...
Something wrong with diskette access (emulated diskette, this can cause troubles :) ).
Can you try this OS2LDR build (same revision, as yours, but verbose) and post screen to somewhere.
(or just e-mail me to the address at the end of QSINIT readme ;) )

42
Programming / Re: kbhit C implementation for eCS GCC ?
« on: September 08, 2014, 04:51:04 pm »
Just copy it from Open Watcom runtime (bld\clib\conio\c\kbhitos2.c).
It looks like only KbdPeek is required for console app:

Code: [Select]
_WCRTLINK int kbhit( void ){
    KBDKEYINFO  info;

    if( _RWD_cbyte != 0 )
        return( 1 );
#ifdef DEFAULT_WINDOWING
    if( _WindowsKbhit != 0 ) {      // Default windowing
        LPWDATA     res;
        res = _WindowsIsWindowedHandle( (int) STDIN_FILENO );
        return( _WindowsKbhit( res ) );
    }
#endif
#if defined(__OS2_286__)
    if( _RWD_osmode == DOS_MODE ) {
        return( _os_kbhit() );
    }
    KbdPeek( &info, 0 );
    return( ( info.fbStatus & 0xe0 ) != 0 );
#else
    KbdPeek( &info, 0 );
    return( ( info.fbStatus & 0xe0 ) != 0 );
#endif
}

43
Be nice if the QSINIT people added some versioning info to the zip files
Actually, there is no reason to collect old versions, but "numbered" files available in ftp://212.12.30.18/public/QS/Archive directory.
Or you can use bldlevel on OS2LDR / QSINIT.LDI files in achive.

44
Programming / Re: New OS/4 kernel :: SVN4222
« on: August 22, 2014, 09:58:10 pm »
I can easily think of a scenario where use of MTRRs become a problem compared to PAT.
MTRR mem. type regions have to be of size "power of 2" and there are restrictions regarding overlapping regions. PAT is fine granular down to the 4 kByte memory page and it can"override" the underlying MTRR memory type to a certain extent.
There is no problems with MTRR usage, if do it right (not like it was done in panorama before PAT version).

In QSINIT - registers reprogrammed to entire address space of video card (get  it from PCI) for 1st CPU and these values copied to secondary CPUs on early init stage.

I have no any problems with such method. And no  requirements  in  "New And Special" version of panorama or new screen  driver  as  in  later  OS/4.  Even,  no  need of synchronization on multiple CPUs in code :)

45
Storage / Re: DFSee fixes problems with 32GB Flash drives
« on: June 21, 2014, 05:02:16 pm »
  You can try QSINIT for this task too ;)
  But it depends on BIOS - if BIOS shows connected USB devices as HDDs even if you booting from other device - QSINIT can manage it: wipe disk, create partition with LVM in mind and format to FAT32.
  Not sure about success, but who knows ;) I'm using QSINIT even for logical partition creation.

Pages: 1 2 [3] 4 5 ... 7