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 ... 15 16 [17] 18 19 ... 24
241
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.

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

243
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:

Quote
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:

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

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

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

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

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

246
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

247
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!

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

Quote
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:

VIRTUALADDRESSLIMIT=3072
EARLYMEMINIT=TRUE
DLLBASING=OFF
PROCESSES=156
THREADS=511
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.

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

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

251
Applications / Re: VirtualBox v5.0.51 Testing
« on: April 10, 2018, 11:43:44 pm »
2Mark Szkolnicki: Changing JFS cache to a lesser value can only cause it to perform slower. So, I doubt that if will have catastrophic consequences ;) It if set too large, it can remain insufficient memory for other needs. But if set lo a lower value, then no harm. And with VAL=3072, and JFS cache not set explicitly, it will be, most probably, still insufficient memory for kernel and drivers, so, it may be some weird system behaviour. So, I don't expect anything better with VAL/PROCESSES/THREADS set, but JFS cache not set. Error -1018 will not go away until you use IBM's kernel, and I doubt that waiting 15 seconds would be of any help. Maybe, pressing "Cancel" or "Continue" will help temporarily, but I'm not sure, as I had no such error on my machines.

Available shared memory is memory in lower shared memory arena. It does not change when you change VAL. VAL can add more high shared or private memory to userland address space if VAL is moved up to the maximum of 3072 MB, so that, VBox can allocate more high private memory for VM's.

252
Applications / Re: VirtualBox v5.0.51 Testing
« on: April 10, 2018, 12:37:57 am »
2Mark Szkolnicki:

> Regarding physical media support - I have not ran into any difficulties at all at this testing phase - all files and installations proceeded without any errors, and I can only report that all physical optical media has booted correctly and flawlessly, as of now, for the optical drives tested.

Yes, reading the attached media from within the VM is good, once booted. But if you try to boot from a physical floppy, or physical CD, you can encounter some problems (possibly, VM will crash).

> The VirtualBox package I downloaded was vbox-os2-i386-v5.0.51.zip dated 22/3/2018 following the link Martin created. Might there be another package floating about or that you are using? Or perhaps a global setting that enables or disables this feature, causing what I have observed?

No newer version was released. so far. I'm not aware of any global version, which disables it for all VM's. Just disable it for every VM created for now. Possibly, I'll try to disable it globally if required features are missing on your kernel, in the future.

Quote
Regarding your P.S. question - The VBox topic has generated a lot of interest, based on the number of views.

I started the new thread as one of the big problems we always have in the OS/2 / eCS / ArcaOS community is getting people to test new items or contribute to the conversation. The focus should not only be on the problems which developers and the highly technical or experienced users discuss, but also how to use and test the software properly, to allow other useful or important feedback to be obtained.. Perhaps, with a little encouragement, especially with a lot of the new users coming on-board with the release of ArcaOS, We can get a lot more testing done, which would certainly help you and others advance development of what I personally consider an important piece of software that could help my business, as VirtualPC definitely needs a more robust and flexible follow-on for our community.

"Problems" in the title always get people to shy away from testing or even asking questions, thinking their questions may be dumb, untechnical or not pertinent. We will also seriously need some documentation for VirtualBox, as the solutions we are coming up with need to be captured to allow people to consistently install and use it successfully, especially if you or others coming up with new drops in future.

Hm, I don't think the word "Problems" will get people shy away from the thread. But indeed "Testing" is better name than "Problems", I agree.

PS: BTW, in the end of older thread I added some CONFIG.SYS options to try for you. You said that you had to close Seamonkey, to run VBox successfully. I'd suspect that if you try these options, you will be able to run both at the same time (if you'll make everything correctly)

Quote
Hi Valery!

I'm not sure how many in the community are using OS/4 consistently or not at the moment.

A big number, in fact.

Quote
I myself do not use it, and I suspect the majority of users here are using a version of the IBM kernel, especially with the ArcaOS release, so you may find many testing reports varying significantly from what you may see on OS/4.

I actually would like to test it (OS/4) at some point, but I suspect if something varies significantly from what you have experienced, testing on OS/4, the difference between kernels and structures is probably the culprit. (including the slowdowns I mentioned previously with AMD-V enabled on the IBM kernel or physical media being unstable).

That why wide testing could be very important, as this VirtualBox development continues.

Indeed, not so big difference. OS/4 kernels contain some enhancements. For example, consistent hi-res timer support, based on HPET timer; Special KEE's for consistently getting curent CPU number (no -1018 error), support for CPU rendez-vous (which allows to use HW virtualization, etc., etc.)

Quote
As I said in my previous post I think we in the community need some formalized "prototype" and "final" documentation to distribute out with the OS/2 VirtualBox even if it comes in two flavours - OS/2 / eCS / ArcaOS and another for OS/4, as YMMV.

I don't think that we need two separate documentation files. Only some special notes. I think, README.OS2 file is sufficient. It did not updated since version 5.0.6. It should be enhanced more, of course, and contain OS/2-specific notes. Otherwise, documentation from Sun/Oracle applies.

253
Applications / Re: VirtualBox v5.0.51 Testing
« on: April 09, 2018, 11:17:29 pm »
2Mark Szkolnicki:

Ah? Yes, just tried on an IBM kernel: It enables AMD-V/VT-x by default. Not sure why, but ok, just disable it for now.

254
Applications / Re: VirtualBox v5.0.51 Testing
« on: April 09, 2018, 10:38:43 pm »
> "PIIX3 cannot attach drive to Secondary Master VER_IO_NOT_READY".

Did you removed the CD from your CD/DVD drive? If so, insert it back, or detach from "Media" menu. Note that Physical media support is unstable, yet. For example, you can easily fail to boot from physical media.

> Also. as a test, created a VDI based Windows 2000 VM as I happened to have one lying around. The virtualization was extremely slow (took about 3 hours to install the OS, while I was doing other things. Again don't know if that is typical of installation on VBox or not, but worth noting.

You need to use HW virtualization, to run heavy-weight OS-es (but it currently does not work on IBM kernels, so OS/4 kernels only for now)

> It seems "enable VT-x / AMD-V" are enabled by default in the settings. I was not sure about that previously in my posts to Valery in the thread "VirtualBox Problems" as the original VM I had created (Windows XP) was done under Windows 7 and Windows VirtualBox v5.0.22, so I wasn't sure if I had fiddled with the settings at some point.

No, I just created the new VM from scratch, VT-x/AMD-V is disabled. In any case, disable it if it enabled, for some weird reason (unless you have one of the latest OS/4 kernels).

win2000 may run ok without VT-x enabled, but win7 or ubuntu are slow like hell, and work conveniently only with VT-x enabled

PS: Why did you created the second topic? Is not the previous one good enough?

255
Applications / Re: VirtualBox problems
« on: April 09, 2018, 09:54:17 pm »
2Dave Yeo:

> You can use http://www.gus.biysk.ru/os4/tools/highmem.exe to set (some) DLLs to load high and save on low memory. Works mostly well with the newest kernel included with ArcaOS. With SeaMonkey closed, try running himem -b *dll in the SM program directory and retest your shared memory use. Sometimes, especially with older kernels, your better to use himem -c to only load the code high. Run himem -? to see all options including how to unmark. Experiment, don't load system DLLs high and if things start crashing, unmark.

Yes, and I have a highmem.cmd script included in the VBox distribution, which starts highmem.exe whith required parameters, to load some segments into high memory. You can easily cause your system to hang, or some API's to fail if you try to load some DLL's both code and data segments to high memory, so, different DLL require different highmem.exe options.

For FireFox/Seamonkey it is sufficient to load only code segments of XUL.DLL high. No other DLL's are required to mark for SM/FF to be working ok.

Also, there is extpack.cmd which is useful to run if you need the VNC extpack to be working. OS/2 uses 8.3 DLL names, so, some DLL names should be shortened, that is what extpack.cmd is doing with VNC extpack DLL, and one more extpack, called DTrace.

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