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 ... 6
Applications / Re: VirtualBox problems
« on: Today at 08:54:21 am »

I have not really used either of my eCS installations since installing ArcaOS but decided to try booting eCS2.1 with various ArcaOS Driver Pack updates. Boot stops with a SYS1201: vboxdrv.sys not installed.

The same problem with eCS2.2b2 - which surprised me as ecS2.2b2 is the system that was in use when I first installed and used VirtualBox successfully.

Both eCS installations are using acpi 3.23.05 and os2krnl 14_106 SMP

Hm, VBoxDrv.sys doesn't install? I can't imagine why this can happen. Tried many kernels and PSD drivers -- never seen this. Could
you try to help me to track why this happen? So, this happens with 14.106_SMP and ACPI.PSD 3.23.05? I tested this combination, and everything booted well. I tested it in MCP2 and eCS 2.2 beta II, on a single-core Athlon 64 machine and two Core2Duo machines -- all worked well. Can you give me more details? Did you installed any other updates except the kernel and ACPI.PSD? Are you sure it was ACPI 3.23.05? Maybe, it was some other version? (also, it's possible that AN has different builds having the same version number, which behave differently. We can exchange more bldlevel details. For example, the copy of ACPI.PSD 3.23.05 I have is built 1 Feb 2017 12:52:11. Does your copy differ?)

Failed to create the VirtualBoxClient COM object.
   The application will now terminate.

   Callee RC: NS_ERROR_ABORT (0x80004004)

This happens when VBox cannot load VBoxRT.dll or some other DLL. This is usually because some dependent DLL's installed via rpm packages are missing, or are different version. You could try to update, or better, remove the DLL's listed here: and install them over. This is basically the same problem as with newer versions of Mozilla, when some DLL's XUL.DLL depends on, are missing or incorrect version.

2Doug Bissett:

I run the old VBox 1.6.1, and the beta 5.0.6, under ArcaOS. No unexpected problems. The won't run OS/2, because you need VT-x/AMD-V enabled, and the OS/2 versions of VBox can't do that (be sure that the option is turned off). You can run a 64 bit OS, as a guest, but it will be dead slow, so don't bother even trying (like 12 hours to boot win 7 64 bit).

OS/2 versions of VBox since about r147 support hardware assisted virtualization. I was able to run OS/2 guest on OS/2 host successfully. 64-bit OS'es currently don't run ok. Most probably, you will get a hang. But it is still being worked on. Though, because of limitations of IBM kernels, this is currently supported on OS/4 kernels, only. They have some required mechanisms like API's for running some code on all CPU's in parallel, getting the current CPU number etc.

How did you managed to run a 64-bit OS? On which VBox version? I was unable to run a 64 bit OS neither in RAW mode, nor with HW virtualization.

2Dave Yeo: This error does nothing with NSPR. It is just a failed COM object initialization because it cannot load a DLL. NS_ERROR_ABORT seems to be an XPCOM error, not NSPR. Also, VBox doesn't use NSPR from yum repo. It carries its own version of NSPR based on VBox Runtime (IPRT, Innotek Portable RunTime) with itself.

BTW, about your ifx error. I saw dmt (the eCS version of ifx) hangs in the past with eCS but none with ArcaOS. Doug might have a point in the ordering in config.sys.

I never seen this in my eCS with DMT. Also, I have no idea how IFX/DMT can hang, or not, depending on VBoxDrv position in config.sys. I suspect this is some SMP-related problem, though.


The resolution to the "timing problem" with the vboxdrv.sys was to move the line higher up the config.sys file - no problem booting now, no need to use Shift as IFX is starting.

Probably, this is indeed some timing problem, so before VBoxDrv "settles a bit", i.e., finishes some activity, and activity done by IFX, should pass some time. An idea may be that VBoxDrv and IFX do something at the same time, but on different CPU's. This somehow leads to a hang. Currently SMP support in VBoxDrv is limited on IBM kernels. IBM kernels have no API returning the current CPU number. So, this is currently emulated with finding the current local APIC number. But LAPIC numbers are not guaraneteed to be consecutive. The may be "holes" between valid LAPIC numbers. So, if an attempt to use an invalid CPU number from the hole in the range 0..MaxCPUNumber is made, an unexpected result can happen, e. g., a hang. So, this currently works reliably only on OS/4 kernels, where an API exist returning a correct CPU number from a contiguous range. VBox assumes that the range 0..MaxCPUNumber should be contiguous.

PS: I never sort CONFIG.SYS automatically, because I prefer to edit it manually. So, I have it being sorted out logically, grouping related statements together. This is easier to support, with a little performance impact. I always placed the VBoxDrv.sys loading string at the end of CONFIG.SYS.

General Discussion / Re: 2ine - OS/2 on Linux
« on: February 24, 2018, 10:50:29 am »
2Sergey Posokhov: Hmm, where did you took this from? Man tries to write some funny things for fun, and wrote about that in his blog. A masterpiece? Do you mean resume? I don't think he will write about that in his resume. He seems to be experient in game development, mostly based on SDL. So, he took yet another toy project just for fun, just like any retro game simulator. He achieved a good progress with it. He has some good progress, compared to osFree. But looking at his sources at a glance, I now see that he did not advanced significantly, compared to osFree. He has a number of DOSCALLS functions implemented. Some of them are missing in osFree, but some functions we implemented are missing in 2ine. Implemented TCPIP32 API's are just small wrappers around Linux socket functions. VIOCALLS are simply implemented based on NCURSES, so no proper VIO lattice is implemented, yet. PMWIN functions include almost the same set as implemented by FreePM. FreePM has only WinBeginPaint and WinEndPaint missing. Drawing is implemented directly via SDL. No GPI is implemented, yet. Also, on FreePM only a message loop is working, but it does not draw anything on screen. 2ine draws a rectangle on screen, instead of a window. The same simpliest application, creating HAB, message queue, a window and running a message loop. DosExecPgm is implemented via fork(). So, these are only simpliest API's implemented, to almost the same degree as on osFree. The only significant advancement is thunking and 16-bit API wrappers. Also, he successfully runs EMX runtime, and even EMX GCC. osFree can't do that, because we still have no 16-bit functions implemented. But looking how it's implemented in 2ine, we could try implementing the them similar way on L4. Some ideas are very useful to get from 2ine sources. So, ATM these sources can't be directly reused by project like osFree. It directly uses some system functions, and required abstraction layers are missing yet. We hope that it will change in the future. Also, looking at last paragraph of his blog post, I see that he paused the work for another project. It looks like implementing PM API is too complex task for quick progress. But I hope that he will continue the development, so maybe the project will advance much further, who knows. I hope him good luck.

PS: His LX loader looks much cleaner that our LX loader written by Viking. Maybe, we can use it, instead of Viking's one.

General Discussion / Re: 2ine - OS/2 on Linux
« on: February 23, 2018, 09:18:41 pm »
2 Sergey Posokhov: You seems to confuse something. looks to be like a RISC-V software emulator. RISC-V is a new open source hardware architecture, not a bytecode. There are some development boards manufactured based on this architecture. It is intended as a future opensource replacement for Intel/AMD arch's. At least, I know it being supported by Genode, which is a project I follow too. Note that RISC-V is not yet complete. Genode supports compiling RISC-V binaries for this arch, and running them in another emulator I know, called Spike: is just another RISC-V emulator. I see nothing wrong with it. What is a symptome of illness of software industry?

Also, an author of is Michael J. Clark, whereas 2ine is written by Ryan C. Gordon. I see nothing common between them.

I am a bit sceptical about the idea to run OS/2 binaries on Linux too. But, for example, ReactOS can benefit from WINE. ReactOS has its own kernel, but the user mode DLL's are mostly shared with WINE (though, they need to add some manual modifications to WINE code for porting them to ReactOS. Also, they have an alternative win32 subsystem implementation, called arwinss, which can reuse WINE libraries almost as is).

We also can benefit from 2ine, like ReactOS does from WINE. We can port some code to osFree, and back, so both projects can benefit. ReactOS does contributions back to WINE code, and we can. Also, some ideas exchange would not hurt.

General Discussion / Re: 2ine - OS/2 on Linux
« on: February 23, 2018, 07:09:58 pm »
Yes. I knew about that from OSNews RSS feed. Very interesting. His approaches are very interesting. I can share some thoughts with him. Very interesting his attempts to implement 16-bit segments tiling, with covering only some areas (not the whole first 512 MB). Maybe, his approach is feasible on L4/Fiasco too. (on Fiasco, LDT is limited to cover only 32 MB, because LDT is limited to 4096 byte -- one page). Also, contrary to his case, I have an idea how I could implement TLMA (Thread Local Memory Area) on Fiasco. OS/2 kernel just does memcpy over TLMA from Thread Control Block (TCB) on each thread switch. This could be done from preempter thread on Fiasco, I think. Linux also seems to have something called Thread Context Hooks, it seems (I saw something like this in Linux-specific VBox sources). But on Linux kernel it requires to run in kernel. On Fiasco, it is easily done from userland.

Regarding that it's useless. Yes, it is not the whole OS/2 ecosystem reimplementation on top of Linux kernel, but still, a good progress. Maybe, it will evolve enough with some time. WINE even has it's own Explorer, I heard. So, maybe they could run WPS some time later ;)

PS: I posted some notes in that blog' comments. More comments should follow soon.

Hardware / Re: Limitation on using an USB DVD and CD writer under ArcaOS
« on: February 15, 2018, 04:58:18 am »
2Rich Walsh: This works not only with arcaos, but with any OS/2 version. Also, arcanoae yum repository contains newer CDRTOOLS version, 3.01. Why it is not working for you?

2Andreas Kohl:

If it would use libscg properly, no warning text should be displayed. I'm using cdrecord for different Unices and even there the transport mechanisms can differ. And "unofficial" means undocumented resulting unreliable behaviour.

Warning is just because this libscg transport is unknown to CDRTOOLS build system. Unofficial means that Nickk and Froloff did not inform Joerg Schilling about the backend they wrote. It was tested many times by many people.

So it seems the ALPHA cdrtools fork shipped via ArcaNoae RPM is using a different approach. And the contained text file doesn't match with the output from:

Code: [Select]
cdrecord dev=help

Yes, they are different. Probably, arca did their own port from scratch, because Nick and Froloff did not published their patches.

Hardware / Re: Limitation on using an USB DVD and CD writer under ArcaOS
« on: February 13, 2018, 11:16:50 am »
2David Graser: Yes, it looks like DVD/CD Toys installs Froloff's version of OS2CDROM.DMD. And RSJ does not work with it. You can try install DVD Toys, and restore the original OS2CDROPM.DMD 10.163 which was installed before. It seems to be overwritten by DVD Toys. Maybe they will work after that.

Hardware / Re: Limitation on using an USB DVD and CD writer under ArcaOS
« on: February 13, 2018, 11:06:08 am »

aspinkk.sys, which works fine on mys system. Why it could not load? Never seen this. "/RSJ" switch -- I never used it. Just commenting the lockcdr.flt out, with adding the set to config.sys like "SET CDR_DEVICE_NAME1=DVD_RW ND-3500AG" does the job. And finally, you'll need to add a line to cddrv.inf file, describing your CD-writer:

_NEC       "DVD_RW ND-3500AG"  N/A    "_NEC    DVD_RW ND-3500AG" N/A                      cdatapi   ATAPI      CUESHEET     N/A

So that, now RSJ does not lock the CDR, and does not detect it each time on boot. Instead, it uses description from cddrv.inf, pointed by "SET" in config.sys.

Regarding DANIATAPI, it seems to be not needed with newer Danis506.add (it includes DaniATAPI.flt). OS2AHCI.ADD seems to be including the same functionality, too. (Though, I never tried AHCI-attached CD-writers, as I haven't them).

USB CD writers only work via a drive letters. They cannot work via SCSI emulation. (I have an USB CD/DVD and USB BD writer)

2Dave Yeo: Indeed, I see CDRTOOLS 3.01 in arcanoae yum repository I have configured. It is available for download without any password. Strange, but good. :)

Hardware / Re: Limitation on using an USB DVD and CD writer under ArcaOS
« on: February 12, 2018, 10:42:39 pm »
2David Graser:

Given a choice between the newer version or the earlier version, at this moment I have go with the earlier version.  I want USB writer capability.

USB writers work with Froloff's cdrecord and OS2CDROM.DMD 10.163 on my machine. Did not tried CD/DVD Toys with it, though. I use CDRECORD directly from command line.

Can Froloff's driver be disassembled to possibly see what he added or changed?

I don't know. If someone has time and skills -- maybe.

2 Dave Yeo:

Cdrecord-ProDVD-ProBD 3.01 (i386-pc-os2-gnu) Copyright (C) 1995-2015 Joerg Schilling

Where did you took 3.01? Is this available from ArcaNoae repositories only? Access to non-arca users is closed?

Hardware / Re: Limitation on using an USB DVD and CD writer under ArcaOS
« on: February 12, 2018, 08:16:44 pm »
2ivan: SCSI descriptors like [bus,]id[,lun] helpful only for SCSI/ATAPI CD writers. They work via DaniS (or DaniATAPI? -- don't remember). For USB CD writers, you'll need OS2CDROM.DMD which works via drive letters, only. Interesting, does OS2AHCI supply a SCSI emulation, like DaniS does? So, SATA-atached writers will work too? Or, how else would SATA writers work? (I don't know as I haven't SATA CD writers)

Hardware / Re: Limitation on using an USB DVD and CD writer under ArcaOS
« on: February 12, 2018, 08:03:12 pm »
2Andreas Kohl: I don't know what is undocumented in OS/2 version of cdrtools. It works the same as UNIX versions. AFAIK, it uses libscg too (It wrote a string like "Unofficial libscg transport ..." to the screen when writing CD's) .

As long HBA support for OS/2 is existing there should not too much problems. That should set the limit to 10 year old workstation hardware in real life btw.

What is HBA?

    The custom version from Froloff is a bit older that that is offered in UDF package. So, it's better to install the version from UDF.

Does it mean that ArcaOS delivered an outdated or incapable version of OS2DASD.DMD?

No, as I checked in my arcaos copy, it has latest OS2CDROM.DMD v. 10.163, the same as supplied with UDF 2.16

2David Graser:
Good that the version from cdrtools 2.01.01.a59 works for you. But v. 10.163 is newer and has more features. Some IOCTL's are missing from Froloff's version. RSJ may not work with it too. And UDF will not work with it, too. Did you checked, which CDRTOOLS version is supplied together with CD/DVD Toys? I'd suspect that this version work well with Froloff's version of OS2CDROM.DMD (because CD/DVD Toys uses Froloff's version of CDRTOOLS), but RSJ needs OS2CDROM.DMD from UDF distribution. This is only a hypothesis. Hm, looking into my version of DVD Toys, I don't see cdrecord in its installation directory. Where does it looks for it, interesting?

Yes, too bad that Nickk/Froloff disappeared both and did not left the sources.

Hardware / Re: Limitation on using an USB DVD and CD writer under ArcaOS
« on: February 12, 2018, 04:47:12 pm »
CD/DVD Toys are only a frontend for CDRTools, so you can use CDRECORD directly, so command line mode will be available. So, this is not a problem. No idea why it cannot work for newer machines. It should work the same.

The custom version from Froloff is a bit older that that is offered in UDF package. So, it's better to install the version from UDF.

Hardware / Re: Limitation on using an USB DVD and CD writer under ArcaOS
« on: February 12, 2018, 03:02:09 pm »
2David Graser: What is your os2cdrom.dmd version? You need a custom version from Froloff (cdrtools 2.01.01a59, or so), or from latest UDF 2.14-2.16. Older versions of OS2CDROM.DMD may not support ioctl's required to write CD's in packet mode. OS2CDROM.DMD 10.163 works for me.

Hardware / Re: Best FAT32 driver settings
« on: February 11, 2018, 10:28:36 am »
2David Graser: Ok, so it looks like the problem was with icons. Indeed, in FC/2, with no GUI, I don't observe any delays or waits to populate the directory.

BTW, I also uploaded new version r333, where I removed OBJ_ANY in DosAllocMem (which prevented CHKDSK to start), so now CHKDSK should work ok.

Also, in last versions (it was in November), I added new cool feature: now fat32.ifs can mount FS images, laying on any other file system. The images can be simple diskette images, RAW harddisk images (partition images, or whole hard disk images), VM images (e.g., VPC images, now readonly, yet). Supported VM image formats are Raw/bochs/cloop/dmg/vpc/vmdk/parallels/vvfat/qcow. I ported the image access library from QEMU, you just use the f32mount.exe utility, to mount them. Now cachef32.exe contains code to read sectors from VM images. The IFS calls cachef32.exe, to read sectors, so that, the code for reading images is run in a usermode process. You can mount images like this:

f32mount win98.dsk <directory on a FAT drive>

-- this will mount a diskette image, or,

f32mount win98.vhd dir1 /p:1

-- this will mount a win98.vhd VPC image to dir1 subdirectory, "/p:1" selects a primary partition in this HDD image. Numbers 1-4 specify primary partitions, 5-... specify logical partitions. Also, you can specify an optional header size as "/o:<size>", if your filesystem starts at offset <size> from the beginning of the image. "/p:..." and "/o:..." options can be combined, if you have a header before the partition table. Note that such way, you can mount any FAT12/FTA16/FAT32/exFAT partition image to a subdirectory on another FAT12/FAT16/FAT32/exFAT drive.

Also, (this feature is unfinished and alpha-quality, yet) you can mount an image to a subdirectory, and run CHKDSK/FORMAT against the mountpoint. To specify a mountpoint, you use the following syntax:

chkdsk d: /m:<path to mountpoint> [/f]

So, d: will be ignored, and <path to mountpoint> will be checked instead. It is done this way, because you cannot pass a directory to chkdsk/format (only a driveletter), so we pass a directory as a separate parameter, instead. And likewise, for format (the same "/m:..." parameter). But I don't recommend to use format on a mountpoint this time, yet, because this feature is not finished, and it can corrupt the image.

Does anybody want to try these features? ;)

Hardware / Re: Best FAT32 driver settings
« on: February 10, 2018, 10:52:25 am »
Strange. What filesystem has your disk C: ? It seems, it wrongly assumes this disk being FAT. The message

FAT32: Error: Sector 7 does not exist on drive C:

means that number of sectors on disk < 7 (usually 0). Also, please, check the newer version fat32.ifs, r332:, I made some additional checks in FS_MOUNT, so it should not wrongly mount other file systems, than FAT/FAT32/exFAT.

PS: No idea, why it is slower on a SMP machine. Maybe, it needs some SMP optimisations, I did none so far. Did not noticed such effects on my SMP machines.

Storage / Re: Low level format error with JFS
« on: February 10, 2018, 04:02:21 am »
Disks > 512 GB are officially not supported on eCS / ArcaOS. But unofficially, they work with some tricks. You need to use DFSee to create volumes on them, and assign drive letters. The reason is a non-standard geometry of such drives. DaniS506 and OS2AHCI on drives from 512 GB to 1 TB assign a geometry of 127 sectors per track, and for drives from 1 TB to 2 TB, a geometry of 255 sectors per track, instead of 63 standard sectors per track. Some tools like lvm.exe or IBM Boot manager, or AirBoot, may not like such drives. So, special tricks with DFSee are required. I'm using two 2 TB drives on two machines, successfully, but OS/2 Boot manager or AirBoot don't even boot a boot sector. I use my FreeLDR or _dixie_'s QSINIT instead, as they aren't so picky regarding the disk geometry.

PS: I observed JFS CHKDSK/FORMAT errors with such drives, too. Looks like in your case too.

Pages: [1] 2 3 ... 6