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

Pages: 1 ... 53 54 [55] 56 57 ... 85
811
Utilities / Re: symbol file for kernel 14.106 or latest XR_C006
« on: January 31, 2020, 02:29:51 pm »
Hi Wim,

received it. Thanks ! I think that will do.

Lars

812
Utilities / symbol file for kernel 14.106 or latest XR_C006
« on: January 31, 2020, 08:29:30 am »
Can anyone provide me with the symbol file for OS2KRNL 14.106 or with the second release of the XR_C006 fixpak ?

I do have the first release of XR_C006 but XR_C006 fixpak was released twice, an initial release that contained OS2KRNL 14.105 (and the symbol file for it) and a second release that contained OS2KRNL 14.106 (and hopefully the symbol file for it). The contained file "README.1ST" will state that it is for 14.105 (for the initial release) or 14.106 (for the second release). Also file "README2" for the first release will show:
=============================
Convenience Package Release 1
V4.51 fixed APARs
Fix Pack Name= XR_C001
Build level = 14.072


where "README2" from the second release will show:
=====================================
Convenience Package Release 2 refresh
V4.52 fixed APARs
Fix Pack Name= XR_C006
Build level = 14.106
=====================================

Any help greatly appreciated.
Lars

813
Yes, "set default" view means RMB->Menu->Open as->Icon view

Valery, I have close to no time for this. I cannot support you any more than saying that EA support has a bug.
If you tell me where to look at the source for VBOXFS.IFS , I might find time to have a look at it but I cannot guarantee.

Lars

814
Valery,

please have a look at FS_FINDFIRST,FS_FINDNEXT,FS_FINDCLOSE,FS_FINDFROMNAME regarding EA support.
There must be something wrong in these routines.
Maybe you even want to look at all information levels: FIL_STANDARD,FIL_STANDARDL,FIL_QUERYEASIZE,FIL_QUERYEASIZEL,FIL_QUERYEASFROMLIST,FIL_QUERYEASFROMLISTL

815
r218:
1) I can now copy to and from shared folder from an OS/2 commandline.
2) EA support still broken: in WPS, I can only see folders, no files, the WPS crashes when browsing folder tree, I cannot set default view

Yes, I double checked, I have r218 installed.

816
No I am not using OS/4 kernel.
As I said, I had removed "read-only" on the shared folder. "WP ROOT. SF" was created.
I made it trap just by browsing in the tree via WPS.
I cannot copy files,even from a command line. I repeat,neither the shared folder nor the target directory is read-only. Yes,I am talking about DOS file/folder attributes.

There clearly was a problem with EAs. I'll try 218.

817
I have the same prob as Mauro: I cannot copy anything from the mounted folder to my OS/2 virtual guest drive.
I have removed the read-only bit from the mounted folder (which is an NTFS volume of my Windows Host) but it does not make a difference at all. The target directory is not marked as read-only. I get a SYS0003 on the attempt to copy.

Copying to/from the mounted volume works with the VirtualBox provided VBOXSF.IFS driver (but of course EA support is not implemented for that driver and therefore WPS behaves badly).

818
2Lars:

> It just does nothing. I meant CFG file and not INI File,sorry about the confusion. How do your tools find the CFG file?

The .cfg file should be located in \os2\boot. It only has influence to drive letter pinning. If .cfg file is not found, shared folders
will be mouned to first available drive letters. What do you mean by "it does nothing"? it should mount at some drive letter,
at least. Did some shared folders mounted? Is VBoxService.exe running? (see my answer to Mauro below)

Ok, now I got a little bit further. It now mounts and the command line view on files and folders is ok. But WPS only shows folders (from the mount point) but not the files. Also, funny enough but no changeable because of lack of EAs, the view always reverts to "Tree View", even if I select "Icon View" from the Properties->menu. Browsing around in the mounted directory tree traps the WPS but it recovers.
I am using r217.

Lars

819
2Lars:

> Can I also place all these files into another directory than \OS2 (and updating config.sys correspondingly) ? Or is this a problem for the .INI file ?

You can, if you wish, of course, but why? It does not use INI files.

> our package does not seem to work with VirtualBox 6.1.2 which is what I use. Too bad.

No, it works fine for me. Tested successfully with VBox 6.1.2 (Linux host). What is not working for you?
It just does nothing. I meant CFG file and not INI File,sorry about the confusion. How do your tools find the CFG file?

820
Programming / Re: Trim command
« on: January 28, 2020, 03:35:14 pm »
Maybe trimming support was introduced in NTFS and FAT32 with later WinXP service packs?
You cannot trim if you don't know what sectors are used or not.

821
Programming / Re: Trim command
« on: January 28, 2020, 09:17:56 am »
If you have an SSD with two partitions,say HPFS and JFS formatted,do you need to run fstrim separately on each partition? I assume so.

822
Programming / Re: Trim command
« on: January 28, 2020, 09:11:39 am »
If a tool is used,then the FS will still need explicit support for trimming (knowing or finding the blocks to trim). A tool just means an entry point into the IFS to perform the job on request.
Because FAT16 support is built into the Kernel, trimming support would require Kernel changes.
Or use Valerius Version of FAT32.IFS and have that handle all FAT16 partitions.

823
Programming / Re: Trim command
« on: January 28, 2020, 09:05:02 am »
Putting this all together:
Assuming the trim command needs a starting block and a length (or multiple of these) to do its job I would assume that every filesystem driver (IFS) needs an entry point into the disk driver (ADD) to tell it which blocks can be trimmed.
During operation the FS will be able to collect which areas can be trimmed.
Or did I misunderstand something?

824
Your package does not seem to work with VirtualBox 6.1.2 which is what I use. Too bad.

825
I never suggested to place my files in c:\programs\VBox. Thay always intended to be on c:\os2. Those versions which go into c:\programs\VBox were made by
Knut/Oracle.

Can I also place all these files into another directory than \OS2 (and updating config.sys correspondingly) ? Or is this a problem for the .INI file ?

Pages: 1 ... 53 54 [55] 56 57 ... 85