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 ... 24
1
Storage / Re: FAT32 - Netlabs or AN?
« on: March 16, 2021, 10:02:29 pm »
Found this thread a bit late, but I'll answer some points

2Doug Bissett:
> I don't even consider using anything except the AN FAT32 driver. It seems to have a problem, or two, but nothing as bad as what 9.13 has (I don't even remember what the problems were). I did try the other one (with ExFAT, and FAT16, support), but decided that it wasn't really any better, and the FAT16 was interfering with the old OS/2 FAT16 support (not to mention the questionable legality of using it). At the time, I had no need for ExFAT, and still don't. It seems that nobody is using ExFAT anymore, even Microsoft doesn't seem to be pushing it.

How could FAT12/16 support interfere with IBM's FAT support, interestingly? Is not that Lewis Rosenthal who said you that nonsense? (I heard such a statement from him, withou any proof). If you would understand how IFS works, you'd know that only one IFS can mount a partition at a time, so they cannot conflict in any way.  If one IFS has mounted a partition, anoyther one will fail. And you can choose, which IFS should mount a FAT partition. If /fat switch is not specified on fat32.ifs command line, then IBM's kernel driver is in  use. If /fat is specified, then FS is remounted with fat32.ifs.

Regarding the exFAT, it is very useful if you use digital cameras. The SDXC cards are formatted with exFAT by default. So, if you need to copy data from someone else' camera without a reformat, you can use the Netlabs driver. if it's your own camers, you can reformat the card, of course. But no guarantee that the camera will support FAT32. In fact, it shouldn't, as the SDXC spec requires only exFAT support and FAT32 is optional. Also, exFAT supports files bigger than 2 GB. If you use FAT32 on latest cameras, you couldn't be able to copy videos larger than 2 GB, which lasts, with good quality, is about half an hour. So, you decide which FS to use. SDXC spec mandates exFAT support, but FAT32 support is optional. So, you're wrong saying that exFAT is not needed and even MS does not use it.

> (not to mention the questionable legality of using it)
What's the rubbish is that? Why it's not legal? Because AN fears Microsoft? There are several exFAT drivers for Linux. Nobody proved so far that they are illegal, the same for our driver.

2Rich Walsh: The BASEDEV is optional feature. QEMUIMG.DLL is optional too. You can delete it if you wish. The BASEDEV was created to be able to mount disk images with FS other than FAT/FAT32/exFAT. For example, ISO9660/CDFS works fine. Originally, I created support for mounting a FAT/FAT32/exFAT images to a subdirectory on FAT/FAT32/exFAT serving as a mountpoint. This is done by fat32.ifs itself as OS/2 cannot mount a FS to a subdirectory (only to a drive letter). Later, I created a BASEDEV for mouning other FS'es at a drive letter. The cachef32.exe daemon runs a thread which loads a QEMUIMG.DLL, monitors the IFS with FSCTL for open/read/write/close commands, and executes these requests via QEMUIMG.DLL. For a BASEDEV, I just decided to create a second similar thread monitoring the BASEDEV with IOCTL's. They are similar, so, both were put into cachef32.exe. Of course, it is possible to create a separate small daemon, but I just decided to use cachef32.exe to run worker threads. At least, fat32.ifs and cachef32.exe are present in any system, so no need to run more daemons if you need a loopback device support. So, I don't see a problem with this.

Regarding software patents and other rubbish. exFAT and FAT12/16 support is not more patented than FAT32. So, if M$ didn't sued us for using FAT32, then we could sleep in peace with FAT and exFAT as well. Specially for AN, I did created a version without exFAT support with all exFAT code ifdef'ed. So, if you fear M$ so much you could compile it without exFAT support at zero effort. No need to fork the IFS. But you forked it, not me. If someone wants a crippled version without disk image support as well -- no problem, I could #ifdef that too, if needed. Or I can create disk image support as a standalone package, as a compilation option. Unfortunately, I see almost no feedback, so no wonder.

Regarding not having performance improvements. This is indeed planned in the future, but there are some problems on the way. fat32.ifs is a 16-bit driver and has problems with bigger cache sizes. It's good that AN repaired (almost) the cache code. In my latest versions, I even backported the AN changes. But that code is still buggy so it's disabled so far. Also, my version is made sector-size independent. I successfully tested 2048-byte sectors on CDRW's formatted with FAT/FAT32/exFAT. But the cache code has 512-byte sectors hardcoded, that's another problem. I'd like to support other sector sizes in the cache as well. But then, caches with size bigger than 2048 KB, is required. But for that, I probably, need to wait until I convert the IFS to a 32-bit version (this is planned, and not only because of cache, it's also because 64-bit seek required for large files support is not working on 16-bit IFS-es, so I need to port it to 32 bits anyway. I also plan to port fat32.ifs to osFree in the future, so this is another reason to create a 32-bit IFS. I'd probably find a way to create a 16-bit or 32-bit version via an #ifdef).

PS: disk image/loopback support is still unfinished alpha-quality feature. I'd like some feedback regarding the image mounting feature and exFAT, but none so far. I am not aware of someone using these features, except myself.

2
Programming / Re: Python 3.x?
« on: July 01, 2020, 05:48:50 am »
Paul, good luck with porting Python 3! I also would like to have Python 3 on OS/2, because I have some things I'd like
to have, like Electrum Bitcoin wallet, which requires a latest and greatest Python to work ok. I use it on Linux and it is good
to have on OS/2 too. Also, Web Automation tools, like Selenium, use Python 3 too. And many more programs written in
Python 3

PS: Electrum uses  PyQt for user interface, which is quite big. Though, we seem to already have PyQt4 for Python 2.x.

3
Programming / Re: Git : SVN plugin
« on: May 10, 2020, 09:11:23 pm »
git-svn is broken and never worked, so no way

4
Networking / Re: Virtualbox, NAT and using ICAT
« on: May 05, 2020, 11:47:58 pm »
Ah, so you need to run ICAT in a VirtualBox VM, not a MUT in VirtualBox. Sorry, didn't understood the question for the first time.

5
Networking / Re: Virtualbox, NAT and using ICAT
« on: May 05, 2020, 11:39:07 pm »
2Lars: Why do you try to debug OS/2 with ICAT and did not try usual debugging via a COM port and standard kernel debugger? It's easier to setup, and
I debug my drivers and IFS'es this way. It's possible to use standard terminal emulator like Putty in Windows, Minicom in Linux and DTerm in OS/2. These
terminal emulators support using a named pipe or a local socket instead of a usual COM port. And VirtualBox (including the OS/2 port of it) supports redirecting
a VM COM port to a host pipe/socket. I wrote (an unfinished) document about debugging of OS/2 drivers in VBox (and not only). It is included into my VBox
additions distribution (docs\debug.txt in the Additions ISO). If you have more questions, you can ask me here.

PS: For ICAT, you can do a portmapping with NAT in VirtualBox. It should be not very hard. Yes, TAP/TUN option may not work with some wifi
cards (though, it works fine with mine). But NAT option does not depend on it.

6
2Martin: Do you have llaecs.exe in mptstart.cmd? (or how it's called in ArcaOS, I don't know) If yes, please rem it out.
It can cause problems if VBoxService.exe is started via run=... statement in config.sys, and in some other cases. Or,
you can move VBoxService.exe to startup.cmd. This is a known problem of llaecs.exe. It interferes with PM programs
started from config.sys from run=... statement. Such programs are paused to load until PM is started. Otherwise, OS/2
may hang when a program tries to call PM API's. But llaecs.exe causes a glitch, so it seems, a PM program is not
paused loading until PM is started. So, better avoid to use llaecs.exe. It causes a lot of trouble.

PS: DId you read README? This problem is described there.

PPS: I looked into llaecs.exe, it's imported modules table contains pmshapi.dll. So, it is a PM program too. Maybe, the problem is because
it is started from a .CMD file, not directly as run=... so maybe, the problem should be fixed, if you move it to config.sys as a run=...

7
2FelixG: The Oracle version is different from ours, so it is of no help here. Though, good to know that you've repaired it. My congratulations!
Does all required tabs present in file properties notebooks (like "File" tab)? VBoxFS.ifs does not show it, currently.

8
2Martin: No, IFS has no control over any checkboxes. No idea yet, why WPS complains about EA's. Maybe, I just need to return proper
null EA's. At the moment, they are invalid. WPS accepts them when displaying a drive contents. But if you open a settings notebook of
a drive, you'll see that some tabs are missing (like File one). So, something seems to be wrong with EA's. For the same reason, it could
complain about EA's when copying. So, maybe, if I'll fix EA's, everything will be repaired. Need to try.

9
Setup & Installation / Re: command output redirection as input
« on: February 16, 2020, 08:05:43 pm »
You need to use UNIX shell for such commands. OS/2 shells like 4os2 cannot substitute result of one command into another.
Just start ash/dash and type the command as is. If

yum deplist $(rpm -q libaio)

does not work, you can try

yum deplist `rpm -q libaio`

Or, you can use a REXX script, like this:

/**/
'rpm -q libaio | rxqueue'
parse pull x
'yum deplist ' || x

PS: did you tried like this:

rpm -q libaio | yum deplist -

?

10
General Discussion / Re: OS/2 in VirtualBox
« on: February 16, 2020, 05:55:51 pm »
Hi, for VBox, instead of using ftp to transfer files, you can use shared folders. My "unofficial" version is here:

ftp://osfree.org/upload/vbox/additions/VBoxAdditions-os2-x86-5.0.51.r218.zip

The support topic in os2world forum is here:

https://www.os2world.com/forum/index.php/topic,1905.0.html

Also, there is official VBox additions by Knut/Oracle, which can be found on official additions CD. Both versions have some
defects atm. Knut's version doesn't work with WPS Drives folder. Mine almost works, but not fully correct, though, it mostly
working. The defect is that all files on the shared folder have only one "Icon" tab in properties notebook. (should be five tabs,
including "File" tab). But file browsing, copying files, starting .exe's mostly work. Also, there is an incompatibility with VBox
6.x: When doing operations with files, the current folder becomes read only (you can remove the readonly bit with e.g., FC/2).
This is observed only with VBox 6.x. No such problem with VBox 5.x (as my additions are built for version 5.x).

Regarding QEMU/KVM, OS/2 runs in QEMU mostly fine. Except the trap in os2lvm.dmd and non-working netbeui.os2 and
tcpbeui.os2. The problem with os2lvm.dmd is because QEMU closely follows the intel spec, which is incorrect. The spec says
that 16-bit SGDT instruction behaves the same like in i286 processor. But it's not true, it behaves like i386 instruction. So, QEMU
emulates SGDT 16-bit instruction incorrectly. OS2LVM.DMD uses 16-bit SGDT instruction and it hits the problem. But there's a
patched version of OS2LVM.DMD by _dixie_, you can change it to the patched version and everything will work. The link is:

ftp://212.12.30.18/public/OS2LVM_QEMU.ZIP

> I've tried loading OS 4.5 to run natively on a Dell Dimension 610. It loads and runs, but starting a DOS or WIN session crashes it.

On my ThinkPad T420 (model released in 2011, Sandy-bridge-based), DOS starts fine. I am able to run both DOS window and Win-OS/2.
With my OS/2 additions, it's possible to use shortened file names on a shared folder. Though, some DOS apps crash the VBox VM. E.g.,
Volkov Commander 4.99 crashes the VDM. But Notron Commander and DOS Navigator run well.

11
Applications / Re: Unofficial VBox Additions - vbxgradd.dll
« on: February 09, 2020, 01:56:12 pm »
2mauro: renmodul renames internal module name. As I said, it is internal, you can see it in a hex viewer inside the file (Look for "DOSCALLS"
string in a hex viewer. Before it, you will see "VBOXGRADD" name). After that, you need to rename the file from "GERGRADD.DLL" to
"VBXGRADD.DLL". Manually, of course.

12
Applications / Re: Unofficial VBox Additions - vbxgradd.dll
« on: February 09, 2020, 02:09:12 am »
2mauro: yes, Pete suggests correct thing: we omitted the module name here.

13
Applications / Re: Unofficial VBox Additions - vbxgradd.dll
« on: February 08, 2020, 07:39:08 pm »
2mauro:

> And of course in my case, what happens after this make even less sense: the OS2 guest machine starts in VGA-8bit screen!

Yes, as Dave said above, you need to rename the internal module name with e.g., renmodul utility. If you rename a file name
only, this will be insufficient, and OS/2 will fail to find VBXGRADD module, and fall back to VGAGRADD driver!

2Martin: Yes, probably, I need to update VBoxMouse.sys and VBXGRADD.DLL to newer versions -- didn't checked them
last times.

14
Applications / Re: Unofficial VBox Additions - vbxgradd.dll
« on: February 08, 2020, 07:34:46 pm »
2Sean Casey: You need to have VBoxService.exe running to have shared clipboard working. Shared folders have nothing to do with
shared clipboard. Shared folders are implemented as a VBoxFS.ifs IFS driver. Though, for automounting of shared folders, you need
an automount service in VBoxService.exe. Shared clipboard uses "shared clipboard" service, which is implemented in VBoxService.exe
too. So, both require a running VBoxService.exe instance.

AMOUSE.SYS is a different version of MOUSE.SYS, so in your case, you need to comment amouse.sys out.

PS: Read this topic for details:

https://www.os2world.com/forum/index.php?topic=1905.msg24939#msg24939

I mentioned an amouse case here.

15
Applications / Re: Unofficial VBox Additions - vbxgradd.dll
« on: February 08, 2020, 07:27:46 pm »
2Dave Yeo: Yes, you're right. You need e.g., a renmodul utility to change the internal module name to VBXGRADD, as I did.

https://hobbes.nmsu.edu/download/pub/os2/util/system/renmodul2_0_0.zip

renmodul /r GENGRADD VBXGRADD

Then it should work. This utility can also edit the imported modules table, changing these module names.

Pages: [1] 2 3 ... 24