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 ... 14 15 [16] 17 18 ... 24
226
Networking / Re: Rsync vs NetDrive
« on: May 13, 2018, 10:51:26 pm »
FC/2 displays .LONGNAME EA's too, BTW, so you can see "alternative" name too

227
Setup & Installation / Re: Panorama v Snap Video
« on: May 12, 2018, 07:33:51 pm »
2Dave Yeo: This is because of WC not being set with SNAP and unsupported card. But you can set it with pmddk.sys on OS/4 kernel, or with "vmtrr" command in QSINIT. (The 1st one being more correct, because it uses PAT, instead of MTRR, to set WC)

228
Setup & Installation / Re: Panorama v Snap Video
« on: May 10, 2018, 10:45:17 pm »
Yes, SNAP from 25 Sep 2006 (it seems this is 3.1.8, but I don't know for sure) works fine with by big FullHD monitor (1920x1080) and ATI 9600 XT video card. Panorama requires wide-screen activator from Robert Lalla. But this activator supports only ATI and Intel video cards. So, I was unable to use this monitor with Panorama and Matrox G400. As SNAP Matrox driver does not support FullHD resolution, and Panorama/Widescreen activator as well. Note that this wide screen activator now seems to be included into newer versions of Panorama, but I'm not sure as I don't have them.

229
Applications / Re: VirtualBox v5.0.51 Testing
« on: April 26, 2018, 04:51:21 pm »
2Mark Szkolnicki:

> In Virtual PC, we had to install the Innotek Virtual Switch between VPC and the host to access the network. It seems NAT does this automatically, with VBOX acting like a VPN, and NAT translating between the Host network and VBOX's internal network.

In VPC, there is NAT too (aka "Shared networking"), and Virtual Switch appeared not immediately. there were old times, when Virtual switch did not yet existed. There is Virtual switch analogue in VBox too, called TAP.OS2. It acts as a node of a virtual network too. (But it is non-functional, currently). NAT isn't a VPN analogue, it just translates IP addresses to a number of ports on NAT side. Each connection from vietual network is assigned a port on NAT side.

230
Applications / Re: VirtualBox v5.0.51 Testing
« on: April 26, 2018, 03:15:28 pm »
2Pete: VBox currently works via NAT (TAP.OS2 driver functionality is currently broken). So VBox guest is seen under host IP (from 192.168.x.x range). No special magic words are needed, I suppose.

231
Applications / Re: VirtualBox v5.0.51 Testing
« on: April 25, 2018, 03:25:17 pm »
2 Doug Clark: OS/2 has a 4 GB address space. If VAL=3 GB, then 4-3=1 GB remains in the kernel arena, which is above 3 GB.

232
Applications / Re: VirtualBox v5.0.51 Testing
« on: April 24, 2018, 10:33:00 pm »
2Mark Szkolnicki:

> One thing I haven't tried as of yet, is to see whether I can mount a USB stick to transfer data into the VM. Valery, if you're around, is that ability enabled, or  or is there still code to write, for that to work?

It requires the USB passthrough feature, which is not yet finished. But can mount the stick under host OS/2 and when the drive letter appears, try to start the VM with a .vmdk file added for that drive letter.

vmdk files can be created with VboxManage.exe like this:

Quote
VBoxManage internalcommands createrawvmdk -filename 1.vmdk" -rawdisk 1:

Where 1: is a 1st harddisk, and if you'll add the 1.vmdk file to your Media menu, VBox will access all physical 1st hard disk. If you'll create the x.vmdk file like this:

Quote
VBoxManage internalcommands createrawvmdk -filename x.vmdk" -rawdisk \\.\x:

And then add the resulted x.vmdk to Media menu, then only host drive letter x: will be attached to the VM. This way, you can theoretically add any drive, including the flash stick. But this disk should be ready when VM starts, otherwise VM will fail to start.

233
Applications / Re: VirtualBox v5.0.51 Testing
« on: April 24, 2018, 10:32:54 am »
2Doug Clark: You don't understand the word "allocated"? So, it your VAL=3072, then you have 1 GB of kernel virtual memory. Then 800 MB allocated means that 800 MB of kernel virtual memory is occupied, so 200 MB is free. So, you should orient on this number. I don't know how much memory VBox needs -- it depends on VM sizes. If you'll allocate 512 MB for a VM, then about 600 MB will be occupied. But for itself, VBox occupies not so much memory.

2roberto: Did you read the whole thread? If so, you should notice that such an error can occur in case you have newer libcx version installed. In this case, you need to try SET LIBCX_HIGHMEM=2.

234
Applications / Re: VirtualBox v5.0.51 Testing
« on: April 24, 2018, 02:30:43 am »
So, increase THREADS to say, 612, or 712. This depends on how much threads Netquestion needs. Usually I don't need so much threads.

> PIIX3 cannot attach to the primary slave (verr_io_not_ready)

Is this a physical CD? Probably, you extracted the CD from the drive, then that error is normal.

235
Applications / Re: OS/4 (technical details only)
« on: April 24, 2018, 02:28:10 am »
Styler/2 worked fine on my machine with OS/4 kernel, as well as REFORMAT. So, probably, you have problems with paths. Probably, LVM.DLL is not on LIBPATH.

PS: Do you have different CONFIG.SYS for OS/4 and IBM kernel? If so, you should compare them for any differences.

236
Setup & Installation / Re: RAM disk and temp folders...what else?
« on: April 20, 2018, 02:29:41 pm »
2Lars:

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

237
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, http://gus.biysk.ru/os4/. 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.

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

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

239
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: http://www.gus.biysk.ru/os4/Patches/AcpiPsdPatches.rar are patches, but not the actual PSD.

240
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.

Pages: 1 ... 14 15 [16] 17 18 ... 24