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 ... 7
16
Setup & Installation / Re: Need help with QSINIT
« on: May 31, 2016, 04:04:12 pm »
Oops, you are using OS/4 loader instead of QSINIT. Menu looks the same, except bottom part :)
I.e. you put wrong OS2LDR file - from OS/4 distribution.

17
Setup & Installation / Re: Need help with QSINIT
« on: May 31, 2016, 10:55:58 am »
If you look to the bottom of menu screen - you can see the hint line about available keys, where "[F3] - shell" is present ;) I.e. F3 in menu goes to shell. "Exit" in shell will return you to menu.

And about qssetup.cmd. Is your tftp server hosted on unix? Just try to lower case file name (i.e. qssetup.cmd, not QSSETUP.CMD).

18
Setup & Installation / Re: Need help with QSINIT
« on: May 30, 2016, 05:08:39 pm »
/boot - is a key, not directory. It means loading from boot device via OS/2 micro-FSD mechanism. This is tftp in PXE case.
Try unzip /? in QSINIT shell.

QSSETUP.CMD - is something like AUTOEXEC.BAT and it is optional. Just create a new one.

19
Setup & Installation / Re: Need help with QSINIT
« on: May 30, 2016, 12:55:56 pm »
Did you read ramdisk\paedisk.txt in QSINIT archive?

You need to create ram disk if you using PXEOS4, the way to do it - described in this file.

20
Programming / Re: Poll: Your favorite text editor
« on: April 21, 2016, 09:57:34 am »
   FED is not listed too.
   Console, but it's a matter of taste.
   It supports rectangular blocks, for example. Hotkeys are customizable and written on REXX :)
   Sources available.

21
Setup & Installation / Re: OS/4 Kernel and QSINIT - some more Questions
« on: November 18, 2015, 06:36:12 pm »
that is what it looks like if I do like you suggested.
No! :) On screenshot - dir a\*.cmd instead of a:\*.cmd, ":" missed ;)

Pattern match code seems a bit incorrect, but it shows all cmds in the current dir then, not in a:\

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

23
Programming / Re: building Fast Editor Lite
« on: March 23, 2015, 03:02:19 pm »
I builded it ages ago, now looking how:
* GNU make! NOT wmake!
* I used VAC 3.6.5 build. It was broken a bit (or just incompatible with my version - there is no .rsp file for ilib).
* tried it now with OW 1.7 - everything is fine (with gnu make, of course)

24
Article Discussions / Re: UEFI and GPT (GUID Partition Table)
« on: March 03, 2015, 08:45:05 am »
About UEFI:
  • on PC - it always 64-bit.
  • it uses own interrupt handling for various things (USB keyboard, SATA devices, etc).
  • it provides only graphic 32-bit modes, for all, including "console". Graphic functions are extremly slow. Modern graphic protocol can supply pointer to video memory, but this is optional.
  • OS/2 kernel protected mode environment is incompatible with UEFI ... Also, UEFI uses 1st MB for own needs (GDT/IDT/page tables, etc) - but this space required for kernel too.
This mean:
  • we cannot use UEFI from kernel
  • we cannot use any hardware until the end first boot stage (when our own BASEDEV drivers becomes ready).
  • we cannot use BIOS int 10h, generally. Now it still present, but this is not guaranteed in the future. QEMU with TianoCore UEFI have no BIOS at all, for example. Therefore, the native video driver is also required!
Boot process must be changed seriously:
  • UEFI app loads all files for 1st boot stage (basedev drivers). Now this feature known as "preload" (in OS/4 kernel).
  • exit from UEFI and switching PC back to real mode to start kernel.
  • start basedev drivers (by using copy of it, was cached above). This requires some changes in boot file system or in kernel.
  • there are a plenty of other problems, but main is video...
  GPT itself is easy to implement. But we have another one trouble here - sector number in all IOCTLs - 32-bit... I.e., disk i/o in OS/2 limited to 2Tb. There is no way to read data above this border.
  So, David must design new IOCTLs and implement it in Danis/AHCI, then add changes to all disk i/o staff (DASD/LVM).

  Even to implement huge disk splitting (3Tb -> 2Tb+1Tb) - like it was done in partflt - 1st stage still required (64-bit sector number in Danis).

  And, yes, hybrid table can be used too, but this is dangerous and this "hack" limited to max of 3 (primary) partitions.

  This is the picture - how I see it ;)

25
Hardware / Re: Any luck with Azarawicz's new NIC driver for RealTek?
« on: February 05, 2015, 09:57:34 pm »
There is another, older, driver rtgnda13.zip which will probably work, but I don't think it works with NETBIOS (I think it was okay with NETBIOS over TCPIP).
RTGNDA speed highly depends on CPU frequency...
I saw 40mb/s from w2k3 server with pure NETBEUI. NETBEUI works, but only as client.
Another (solvable) trouble - this driver often sets zero MAC. This can be fixed by manual setting of NETADDRESS option.

26
Applications / Re: No word from Mensys/XEU - Alternatives?
« on: January 15, 2015, 01:15:46 pm »
I suggest to produce a bootable USB stick, containing DFSEE, a universal clone, and some special files needed for special hardware (Stylus+Finger support i.e.).
You can use QSINIT`s ram drive for it, as one of variants ;)
I.e. it supports boot from own PAE ram disk.
There are two problems here: it is FAT only and unique drive letter selection.

Method is simple - QSINIT must be installed to USB stick (no matter - partitionized or big floppy, visible in OS/2 or not) in company with ZIPped OS/2 (small installation to fit on memory disk on PCs with low amount of memory (1-2Gb)).
BIOS starts QSINIT from USB stick, then OS/2 can be unzipped to ram disk (by internal QSINIT unzip) and boot process will switched to ram disk as "boot device". More details at the end of PAEDISK.TXT in archive.

It works, but with disadvantages: installation must be small, FAT only and without EA. But, as a bonus - the same installation without changes can be used for diskless PXE boot.

27
Programming / Re: New OS/4 kernel :: SVN4227
« on: December 07, 2014, 10:10:30 pm »
   Ok, I made changes in new revision, but with more strictive check.
   It must work until next "great changes".
   In addition VALIMIT key now supported too (but only for later OS/4 kernels, of course).

   And HD4DISK.ADD must be updated to one from this revision, older versions will have troubles in detection of disk with non-default parameters (sorry, OS4User infected me with his "traditional incompatibility" ;) ).

28
Setup & Installation / Re: Help for QSINIT Ram Disk appreciated...
« on: November 15, 2014, 08:16:38 am »
R6000
- stack overflow
Is it works on normal drives?
This can be wrong UCONV fix, for example (I had stack overflow in UDF format, with such UCONV).

29
Setup & Installation / Re: Help for QSINIT Ram Disk appreciated...
« on: November 14, 2014, 11:54:35 pm »
SYS0528: The specified disk did not finish formatting.
I think - this is one of FAT32.IFS surprises ;)
You can try to use NOFAT32 key in RAMDISK command line.

Quote
By manually building the ramdisk with the F3 (I think that is right) to get to the qsinit shell,  when I reboot and not create the ramdisk I find the ramdisk left in place with the files I copied to it.
And, yes - this funny data saving after reboot is a feature, not a bug ;)
Actually, without hardware reset/power off - BIOS leave memory above 4Gb untouched, and HD4DISK.ADD can discover such disk on next boot if it will not be overwritten by RAMDISK or someone else :)
But, there is no any real guarantee of data safeness in this case..

30
Setup & Installation / Re: OS/2 and the QSINIT Loader - Video Online!
« on: September 30, 2014, 01:52:20 pm »
Nice video :)
Actually, there is a strange moment when you exits from menu by ESC key to the pure shell and "press any key"...
There is nothing to stop execution in this moment....
Another good news is COM port presence :)

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