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 - Valery Sedletski

Pages: [1] 2 3 ... 9
Setup & Installation / Re: RAM disk and temp folders...what else?
« on: April 20, 2018, 02:29:41 pm »

> The problem is that the OS4 components are spread across different places (there is no common zip, left alone an installation package). And it's unclear when and if you need ACPI4.BPD and OEMHLP.BPD.

All required components are in kernel archive. acpi4.bpd is not yet released, because something should be fixed until the release. But it is promised to be released soon. BTW, it should work ok without acpi4.bpd (or, with ACPI.PSD older than 3.23.01)

Setup & Installation / Re: RAM disk and temp folders...what else?
« on: April 19, 2018, 05:59:12 pm »
2Lars: Where to get??? On Hobbes. If the kernel is not properly work on your system, you should report that to the developers, so that they will fix it. But you don't want. So, who is guilty?

All available stuff is either on Hobbes, or at official webpage, All, who needs it, knows about it. os4apic.psd is documented in kernel readme's. At least, available command line switches. What else is needed? It is not ACPI implementation, because ACPI is separate from PSD. ACPI is available for interested testers (including me). It is a special kind of driver (a PDD, but it is loaded before PSD, and it communicates to PSD, so that PSD gets ACPI tables info from it. Alternatively, IRQ routing info can be get from MPTable). Drivers like CLOCK03c.SYS are mandatory, but they are loaded by kernel without the need to be written into CONFIG.SYS (the same way as CLOCK01.SYS. CLOCK03c.SYS is loaded instead of CLOCK01.SYS, and contains both CLOCK and TIMER drivers. Plus, it contains support for hi-res timer, based on HPET). The same for SCREEN03.SYS. There are also OEMHLP.BPD and ACPI4.BPD, which contain OEMHLP$ and ACPICA$ implementations. All these should be not written into CONFIG.SYS. Everything should be described in readme's, otherwise you can ask developers. They are responsive.

Setup & Installation / Re: RAM disk and temp folders...what else?
« on: April 19, 2018, 06:07:27 am »

> As to STRAT1 method: as far as I can remember from the OpenJFS code I think JFS.IFS will fall back to the STRAT1 method when it cannot find a STRAT3 (flat addressing) entry point. Of course that is irrelevant nowadays as the 32-bit (most recent) OS2DASD.DMD supports the STRAT3 entry point. But the old 16-bit version of OS2DASD.DMD did not.
On the other hand, I think that JFS.IFS will only work with the new OS2DASD.DMD + OS2LVM.DMD.

(Open)JFS will fall back to strat2, not strat1, if strat3 is not supported. JFS does not support strat1 (as well as HPFS386 does not).  JFS.IFS works fine with 16-bit OS2DASD.DMD form Merlin/Warp3 (and DANIDASD.DMD), because it falls back to Strat2, I think.

Also, this is not irrelevant now, as 16-bit OS2DASD/DANIDASD can still be used on the modern system. I use DANIDASD in my universal bootable OS/2 stick, for example.

> Also: VFDISK.SYS (the virtual floppy disk driver, a legacy block device driver) only supports the STRAT1 entry point. But given the fact that you can only format virtual floppies to FAT anyways that should not be a problem.

BTW, using SVDisk.sys, you can easily format virtual floppy as HPFS (with SVDisk own HPFS format tool), then you can take a floppy image with savedskf.exe, and restore it to a physical floppy, or VFDISK.SYS virtual floppy, using loaddskf.exe. Also, I was able to format floppies with Macintosh HFS file system, and use them with HFS.IFS on OS/2. (HFS hybrid CD's work fine too, BTW).

2Dariusz Piatkowski:

> Yup, similar configuration to what I currently have. My operating partitions are all HPFS386, the nightly backup partitions are HPFS386 as well but no CACHE on them. Neither is the RAMDISK, else it defeats the purpse.

You still use HPFS386 as your main file system? Why not JFS? HPFS386 has limitation of 64 GB max partition size, like ordinary HPFS driver. So, how do you use it with modern hard disks?

I moved to JFS 17 years ago, since my partitions are all bigger than 64 GB.

2all: BTW, why nobody here is mentioned emsFS.IFS ramdisk? It uses memory above 4 GB too, but uses PSE36, instead of PAE for accessing this memory. It maps a 4 MB pages above 4 GB limit to a 4 MB window below the 4 GB limit, without switching PAE on/off and copying data. PSE36 is enabled permanently, and no copying is done, only mapping. Also, emsFS.IFS is based on ramfs.ifs. So, it has all the benefits of ramfs.ifs, like absence of block layer. So, it is IFS-based, hence no block layer and caching overhead. So, according to my tests, it is about 5 times faster than PAE ramdisk from QSINIT.

The disadvantages of emsFS.ifs is that it requires the OS/4 kernel as it uses special KEE's for PSE36 access. Also, there is no support for restoring the disk contents like QSINIT does with its "unzip" command. On the other hand, QSINIT is significantly slower.

Also, QSINIT advantage is that it unzip's files at the early stage, and then you can boot from this ramdisk, like with Veit's Memdisk. So, you can create bootable flash sticks.

But you can create bootable flash stcks and boot from emsFS/RAMFS too, if using my FreeLDR boot loader, together with bootos2.mdl OS/2 booter. This is done in my universal OS/2 boot disk (which can boot from flash/CD/harddisk media).

So, did anybody tried emsFS.IFS here?

Applications / Re: OS/4 (technical details only)
« on: April 19, 2018, 02:49:23 am »
2Doug Clark: Does not Arca Noae supply the  build archive? I still have 3.23.01 from my previous eCS installation. These: are patches, but not the actual PSD.

Applications / Re: OS/4 (technical details only)
« on: April 19, 2018, 02:46:47 am »
Just tried to run reformat.exe on my Asus laptop with eCS 2.2 and OS/4 kernel -- it starts. But on this machine (MCP2 with OS/4 kernel) it does not start, though I put ecolange.dll and ecomedia.dll in program dir. So, something is indeed missing in this system. But it works fine on the previous system.

PS: Now tried to run reformat.exe on this machine, and it starts here too. Weird, as previously, it did not started. (I put the required DLL's: ecolange.dll, ecomedia.dll and progress.dll in the same dir as the program)

PPS: BTW, this program is not really needed, because there is native FORMAT from fat32.ifs which allows to format to FAT12/FAT16/FAT32/exFAT file systems. Required flash media preparations can be done with DFSee, without the need to reformat media. You usually only need to add the LVM info, which can be done non-destructive, without the need to repartition and reformat.

PPPS: Tried to press the "Format" button, it says "Your eCo software subscription has expired" :)))) Useless, indeed.

Applications / Re: VirtualBox v5.0.51 Testing
« on: April 18, 2018, 04:40:47 am »
2Mark Szkolnicki: Yes, I'm still working on a host-side shared clipboard DLL and guest-side shared folders IFS for OS/2. No work is done on drag-n-drop, yet. Actually, I have no idea how should it work, and what could be missing. It seems, I was able to drag files from OS/2 desktop to VM desktop, for WinXP guest (or vice versa). But I'm not sure how should it work. So, if you have an idea, what's not working, please share.

Applications / Re: OS/4 (technical details only)
« on: April 18, 2018, 04:21:33 am »
> ArcaOS with the IBM kernel and loader loads the RAM disk just fine.

ArcaOS does not use IBM os2ldr. It uses a "stripped-down" variant of QSINIT, with some features ripped-off (like the boot menu and some QSINIT apps which usually present on the ram disk). You see the ramdisk with OS/4 kernel and loader after warm reboot because the ramdisk remains in memory as RAM is refreshed. If you turn it off, and back on, the ram disk gets lost. So, it requires QSINIT, or Arca Noae loader for the ram disk to be created again. OS/4 os2ldr knows nothing about ram disks, the same way original IBM os2ldr does.

So, you have two oprions:

1) use QSINIT, which is more flexible and allows to boot multiple kernels from the menu, and which is compatible with OS/4 loader "os2ldr.ini" config file.
2) boot Arca Noae loader from OS/4 os2ldr with "restart" option, like this:

os2ldr.arc = Arca Noae loader, restart

-- where os2ldr.arc is your renamed version of Arca Noae loader. But it will boot kernel with fixed "os2krnl" name, only.

Applications / Re: OS/4 (technical details only)
« on: April 18, 2018, 04:02:02 am »
Also, I should note that I don't know, how does Arca Noae loader restores the ram disk. For QSINIT, it requires creating the qssetup.cmd file in the root directory, with the following lines:

ramdisk z:
unzip /boot /q qsinit.ldi c:\

-- This will create the single FAT/FAT32 z: disk under OS/2 (drive letter c: under QSINIT) and unzip the qsinit.ldi file to the ramdisk.

To get it formatted with HPFS, you should use qssetup.cmd with the following contents:

ramdisk z:
format c: /fs:hpfs
unzip /boot /q qsinit.ldi c:\

QSINIT supports multiple ramdisks with different FS-es, like this:

ramdisk z: q: div=565
format c: /fs:exfat /a:1k /q /wipe
mount d: hd3 1
unzip /boot /q qsinit.ldi c:\

-- This will create disk z: (c: or 0: under QSINIT) formatted as exFAT and extract qsinit.ldi to it, and disk q: (d: or 1: under QSINIT), 565 MB in size, formatted with FAT16 (empty). For more details, refer to QSINIT documentation. exFAT ramdisk can be mounted via fat32.ifs.
You can use exFAT or FAT32, or FAT16, or HPFS for your ram disks the same way.

Applications / Re: OS/4 (technical details only)
« on: April 18, 2018, 03:27:39 am »
2David Graser: I don't understand you. The ram disk disappears when the system is powered down, because power is switched off, and RAM is not refreshed, as Ivan said. This is what happens. Or, do you mean that the .ZIP file does not unzip to ramdisk? BTW, do you use QSINIT, or OS/4 os2ldr? The ram disk works only with QSINIT (or Arca Noae os2ldr, which is a crippled version of QSINIT). OS/4 os2ldr does not create the ram disk, possibly, that's because you lose your ramdisk. So, did you tried QSINIT, and does it change something?

PS: Note that you should disable the OS/4 logo, by adding "NOLOGO" to kernel parameters, or QSINIT will cause system to hang on VESA mode detect. This is unsolved problem, yet.

PPS: The ram disk is in fact created by QSINIT. hd4disk.add only allows this disk to be mounted under OS/2. So, hd4disk.add without QSINIT will not work. Arca Noae loader should work too, instead of QSINIT, theoretically, if you'll boot OS/4 kernel with it. But AFAIK, it does not support choosing multiple kernels from the menu. So, you'd better install QSINIT, instead.

Applications / Re: VirtualBox v5.0.51 Testing
« on: April 17, 2018, 03:29:33 am »
2Mark Szkolnicki: Updating WinXP to win7 is possible, but note that win7 will require significantly more resources than winxp. The bare minimum for Win7 is 768 MB of RAM, but in case you disabled all "bells and whistles" like Aero and visual effects, and enable VT-x/AMD-V. Otherwize, it will run too slow. WinXP with 512 MB of RAM is an optimal variant even without HW virtualization. So, I'd not recommend to upgrade it to Win7.

> I can say that they do open (a hopeful start) and that I can access files from the host computer and others, through my peer network. I did try enabling the "shared clipboard" in VBOX through SETTINGS | GENERAL then the Advanced Tab and found that attempting to cut and paste between the host and the VM locked things up. Only tried "Bidirectional" at the moment (also has a Host to VM or VM to Host option), but, I expect, this being a developmental version that some code linking the OS and the VM clipboards is still needed.

Shared Folders should work with different guests (excluding OS/2 atm. I did not finished the shared folders IFS yet. But it currently allows navigating the file system and viewing the files. Though, it can crash the VM easily, so it is not stable yet, but partially working). So, host support for shared folders on OS/2 is working, but guest support is not yet.

Inversely, Shared clipboard host support is not yet finished, so it can easily hang your host system! So, beware. Support for shared folders on OS/2 guests should work, though.

2ivan: running two different VM's on top of OS/2 host is possible. At least, I ran two VM's, one with WinXP, another with Knoppix LiveCD (Linux). They are not prevent to run each other. Running a VBox inside VBox is not poossible, AFAIK, because VBox does not support nested virtualization. QEMU supports it. So, I was able to run VBox inside QEMU. It worked, but very slow. KolibriOS started for an hour, or so, in such VBox instance. (This is without HW virtualization/KVM. With KVM enabled, VBox runs relatively well inside QEMU).

Applications / Re: VirtualBox v5.0.51 Testing
« on: April 17, 2018, 03:10:36 am »
2David Graser: QSINIT is mostly compatible with os2ldr from OS/4, but it has more features

Applications / Re: VirtualBox problems
« on: April 15, 2018, 03:03:35 am »
2roberto: So, With VAL=2880 VBox starts ok, but you got error -1018? Unfortunately, no fix for this error, so far. On IBM kernels, CPU ID is got as Local APIC ID, which is not guaranteed to be in a contiguous range. So, when you got into the "hole", you got this error. The only means to get rid of this error is currently, install an OS/4 kernel. It can get CPU ID's reliably. (In the future, maybe, some workaround for IBM kernels is possible, but for now, use OS/4 kernel). Also note that if you'll get this error or not, depends on LAPIC ID's in your system. If they are contiguous, all is ok (like on all three of my machines). If not, you can get this error.

VT-x should be disabled in VBox settings, if you have IBM kernel!

Applications / Re: VirtualBox v5.0.51 Testing
« on: April 15, 2018, 02:24:56 am »
2Dave Yeo: Yes, good note! Modern videocards have too much on-board RAM. Mine, for example has 256 MB (it is Radeon 9600 XT), so I decreased memory mapping to 16 MB in SNAP, which is sufficient for 2D acceleration and my FullHD screen to work. This will greatly economize the kernel address space. The key for VBox to work is to get more available address space to userland (hence, increase VAL to 3072). But increasing VAL requires decreasing JFS cache, if it is too much, and THREADS (to e.g., 511)/PROCESSES (to e.g., 128). Also, you need to control how much free space remained in the kernel arena, with Theseus (see the end of System->Kernel Information->Kernel Memory usage report):

allocated committed   present  resident  Totals
 --------  --------  --------  --------
 38133000  12D93000  12D15000  111E3000  Total (in bytes)
   918732    308812    308308    280460  Total (in Kbytes)
  897.199   301.574   301.082   273.887  Total (in Mbytes)
< End of THESEUS4 (v 4.001.00) output @ 3:01:58 on 15/4/2018 >

You can see that here is 897.199 of 1024 MB is occupied. So, 100+ MB is free, which is sufficient. I have VAL=3072, PROCESSES=156, THREADS=511, and JFS cache set to 128 MB explicitly:

ifs=d:\os2\jfs.ifs /autocheck:* /cache:128000 /lazy:8,60,5 /p1

PS: Also, you can try to decrease Video memory used  by your video card in BIOS, if you have such setting (in case you have an integrated video card).

2Dariusz Piatkowski: Documentation is good enough, at least, most needed configuration options are described ok. You can ask develpers, if in troubles, they are on this forum and on IRC.

Installation is simple, as any other OS/2 kernel. You have to copy kernel and os2ldr instead IBM's ones, or install QSINIT, which is better to use. Both QSINIT and OS/4 os2ldr support multibooting several kernels. (But there is a number of drivers supplied with the kernel, which should be copied to \os2\boot. These drivers have no name conflicts with existing drivers. AlexT wrote a short HOWTO for quick setup, which is included in latest kernels. Also, there is doscalls1.dll which is optional. It is compatible with IBM's version). Also, there is a multibooting feature of OS/4 os2ldr (and QSINIT works the same time, I use it). So, you can boot multiple kernels from the os2ldr menu (it is better described in QSINIT documentation). Also, OS/4 has built-in CONFIG.SYS editor (activated with Alt-E in loader menu), which is handy if you need to REM out or add something temporarily. It has a good logging feature (a central system log, available for reading via a COM port, or via "copy KERNLOG$ kernlog.txt" after the system booted successfully). Very handy for developers, to debug drivers. Also, there are some enhancements, like hi-res HPET timer support (no hi-res timer bug in apps like Mozilla, like ACPI.PSD has), support for CPU rendez-vous (running the code on all CPU's in parallel), which is used in VBox for VT-x/AMD-V support etc., etc.

Regarding ACPI, yes, OS/4 devs got boring patching each time every new version of ACPI.PSD, so they gave up. But they created their own ACPI module (which is not yet released, it is available for testers, and those who is not too lazy to debug it to make it working, with devs' help). So, ACPI.PSD should be not a problem too.

Applications / Re: VirtualBox v5.0.51 Testing
« on: April 15, 2018, 01:48:46 am »
2Doug Clark: VAL=1536 or 2048 may be too small for running VBox! You need VAL=3072. Please reread what has been written in this thread (and another one VBox thread) carefully. You don't need to switch off AMD-V/VT-x in BIOS settings -- only in VBox settings! Your system supports VT-x/AMD-V, but your kernel is not. That's because it is enabled on your system. My system does not support AMD-V, because it is an early Athlon 64 system, so it is turned off by default on my system. So please, turn the checkbox off.

You'd better not start old VPC VM's in VBox, better create a new one, because it has different hardware emulated.

> Unable to allocate memory for mode info cache!
> Fatal error in driver. Use Alt-Ctrl-Del to reboot.

Never seen this. Looks like you have insufficient kernel memory. Are you sure you have correct VAL and decreased JFS cache and THREADS/PROCESSES accordingly? Do you have EARLYMEMINIT=TRUE in CONFIG.SYS BTW?

> I also experience an error after VirtualBox.exe is running, when I start the VM. If I wait the 15 seconds suggested by Mark (I believe) the VM will start.

Why do you need this? You have -1018 error too?

> Does networking work in Vbox?

It works, via NAT, and via OS2TAP driver (but the latter is broken). NAT should work ok. Yes, probably, you have some network configuration error in WinXP. If your OS/2 network connection works, then it should woork in VBox too.

Applications / Re: VirtualBox problems
« on: April 12, 2018, 12:28:59 am »
Maybe, it depends on the JFS version, I'm not sure, but my version had too big cache by default. (I have no Arcaos, eCS 2.2 only, but I needed to set explicit JFS cache to have my system stable) After setting an explicit value, it become ok.

> At that I remember trying to increase the cache size to 128 MBs and the system becoming very unstable.

Are you sure you did all at the same time: Set explicit JFS cache, Set VAL and THREADS/PROCESSES as I said? Also, you should look into Theseus, to be sure: System->Kernel Information->Kernel Memory Usage. I have VAL=3072, so it should be 1 GB of kernel memory. In the above report I see Allocated: 872 MB, Committed: 295 MB ("Totals" at the bottom). So, 128 MB must be free. You can check it yourself -- some space should be free.

I have 3500 MB of physical memory available to OS/2 on this system. Some systems have less than 3072 physical memory available to OS/2. If so, then it maybe less kernel memory available. So, you'll need to tailor it to your system further.

Pages: [1] 2 3 ... 9