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] 2 3 ... 10
1
Programming / Re: Non-yum/rpm vs. ordinary (?) eCS
« on: October 07, 2017, 09:10:52 am »
Even "arcview.exe" that comes with eComStation supports 7z files.
You just need to create an association. The easiest way is to use XWP to create a file type say "7z Archive", tie that to file extension .7z and then to select "arcview.exe" as the handling program.
That will at least allow you to view the file contents but I am pretty confident it will also support extraction.

2
Applications / Re: XWorkplace and missing folder contents...
« on: October 02, 2017, 03:31:30 pm »
Bull. I gave up complaining about this issue, years ago, because I "am the only one with the problem".

Thanks for advising. My apologies if I didn't recall that you bitched and moaned about this years ago - one rant tends to blend into another.

Happily, an unusual confluence of events today has opened a whole new avenue to explore - one that has nothing to do with XWP or the WPS. As you know, I got to see part of your config.sys today and the many, many filesystems you load. Perhaps that's where the problem lies. As I understand it, all filesystem requests go through the kernel's filesystem router, then out to the appropriate one. If something were to get messed up there, it's easy to see how some or all filesystem activity would grind to a halt.

Based on the excerpt of config.sys you posted, I see that you load:
  • JFS
  • HPFS
  • CDFS
  • FAT32
  • UDF
  • STUBFSD / AEFS
  • STUBFSD / ISOFS
  • NDFS
  • TONIGY
Dariusz, do you use any of the less common ones on this list?

Quote
The best that I can hope for, is that one of the main developers will see the problem, figure it out, and fix it.

That's pretty amusing...

Every volume ("drive letter") is presented to every IFS on the "FS_MOUNT" call to the IFS. Once an IFS claims responsibility for a volume ("drive letter") it does so for good (until next reboot, of course). From then on, the kernel knows what file system Driver (IFS) to invoke for any directory or file related access.

What is important to know is that the FAT32.IFS Version that delivered with AN was badly broken and far from being ready. It would be a good idea to pull the latest release from Netlabs.
Nonetheless, assuming that FS_MOUNT of FAT32.IFS is not doing something fundamentally wrong, only FAT32 partitions (and FAT12/FAT16 and exFAT if you enabled that in FAT32.IFS) should suffer from file system driver errors.

3
Storage / Re: About FAT32 and AN
« on: June 18, 2017, 10:09:39 pm »
Quote
Looks like quite a few people are having probs with FAT32 as it comes with AN:

I have had a problem with special characters in the folder, or file, names. They just don't match what the older FAT32 driver , or windows, uses. That can also result in a case where the files "disappear" while copying (they are still there).

Personally, I always turn off EAS. The file system, itself, doesn't support them, and you will have nothing but problems with them, if you try to use that feature (true for older FAT32 versions too).

The easy "fix" is to get FAT32 9.13, from HOBBES, and replace what comes with ArcaOS.. Eventually, somebody will listen to what i tell them, and the problem will be fixed.

Please open a problem report for this defect so that it does not get lost. With some luck, this project is going to pick up speed:

http://trac.netlabs.org/fat32/newticket


You will need to create an account with Netlabs but I think you have that already.

Lars

4
Setup & Installation / Re: format /fs:hpfs does not work
« on: June 18, 2017, 05:31:07 pm »
It,s rather UHPFS.DLL that is missing.

5
Setup & Installation / Re: ArcaOS keeps rebooting
« on: June 12, 2017, 06:08:42 pm »
Forgot to answer the other statement: the reason why nobody has yet written a utility for writing the DLAT sector is twofold: there are people who would jump into your face if say USBMSD.ADD would write something to their media without them knowing (large floppy support creates a fake  DLAT in memory therefore this is not a prob in this case) .And secondly it's damn difficult to say where the DLAT sector is supposed to go on the medium. I just say " disk geometry" and you will understand the problem.
The latter is also not easy for DFSEE to know reliably and I had quite a few email exchanges with Jan van Wijk about this problem. That's why DFSEE is a tool for people who know what they are doing.
It's not lack of skill.

6
Setup & Installation / Re: ArcaOS keeps rebooting
« on: June 12, 2017, 05:29:20 pm »
And then there is an updated USBMSD.ADD. It's not only updated to support "large floppy".
I also spent considerable time in making it work more reliably with USB mass storage devices. That includes USB floppy drives/CD-ROMs/memory sticks/hard drives. If you  need to use a floppy  drive it's the only driver that will work with more than just a few devices. I also improved copy performance and I fixed problems with data integrity.
It can be used with the AN stack without any problem or restrictions.

7
Setup & Installation / Re: ArcaOS keeps rebooting
« on: June 11, 2017, 04:32:24 pm »


I am using XWP "full" version (that is,not the lite version) 1.0.11 available on Hobbes. I would think that is about the version that AN delivers.

ANXWP is at version ..umm.. 1.0.11++. I've made about 10 changes since 1.0.11 and checked them in to the Netlabs repo but I haven't built a new generic version yet because all the NLS files need updating. I'll try to get that moving.(

I could help with the German translation if you'd send me the files to translate.
Or Andreas Buchinger would potentially volunteer.

8
Setup & Installation / Re: ArcaOS keeps rebooting
« on: June 11, 2017, 10:48:57 am »
"formatted as eFAT"
What is eFAT? I can say that exFAT is not supported. Only FAT16 and FAT32.

I know it's not the cure for every problem but regarding USB you could try my driver set.
Go to Hobbes.nmsu.edu and search for "usbdrv".

9
Storage / Re: About FAT32 and AN
« on: June 10, 2017, 10:51:26 pm »
Even if you dont intend to use extended attributes, the file system driver still has to support them.
If the file system does not support them the file system driver has to return some minimum response on a request for extended attributes. This has now been fixed for the /largefiles support.
It's more complicated as it seems ...

10
Setup & Installation / Re: ArcaOS keeps rebooting
« on: June 10, 2017, 04:35:16 pm »
I don't have AN installed but I do have the latest XWP installed.

For the record: which version? There are two versions per release. Which version is AN's?

I am using XWP "full" version (that is,not the lite version) 1.0.11 available on Hobbes. I would think that is about the version that AN delivers.

11
Setup & Installation / Re: ArcaOS keeps rebooting
« on: June 10, 2017, 11:30:59 am »
This is an interesting discussion:
I have sudden system reboots every now and then as soon as XCenter bar has completely built up. I don't have AN installed but I do have the latest XWP installed.
I have now removed the Window list widget. Let's see if that helps. Possibly need to remove additional widgets.

12
Storage / About FAT32 and AN
« on: June 10, 2017, 11:10:01 am »
Looks like quite a few people are having probs with FAT32 as it comes with AN:

the new version that is being worked on still needs some fixes. What I fixed with SVN revision 250 was some prob with extended attributes in conjunction with the /largefiles switch which would lead to a complete system hang when opening a FAT32 drive object. Currently we are working on a problem when double clicking on a file with a program association​ (say a zip file associated with the arcview.exe utility).
We know where the resulting system hang occurs but we don't yet know why ...

For the time being the solution is to revert back to version 0.9.13 which you will find at Hobbes.

To find out about what SVN revision is delivered with AN:
open a commandine, change to directory \os2\boot and do a "bldlevel FAT32.IFS" (without the quotes).
The returned info contains a 3-digit value (apart from other info) which is the SVN revision.

If it is older then 250 you can try newer version here (as I said:not yet ready for prime time):
trac.netlabs.org/FAT32




13
Storage / Re: HPFS and JFS internal definition specifications
« on: June 02, 2017, 02:47:48 pm »
There already exists a "large file" API and there also exists additional entry points and extensions for existing entry points for file system drivers to support these new APIs.
These APIs will use 64-bit signed values to deal with file size and seek offsets.

The only problem is that the current HPFS.IFS was written at a point in time where these additional entry points where not yet defined.
If these additional entry Points were added to the existing HPFS.IFS then it would not be necessary to use the "DEADBEEF hack" and read in units of sectors instead of bytes.

As an example, there is an effort currently going on to add these additional "large file" entry points to the existing FAT32.IFS.
That will finally allow to deal with files up to 2^63 Bytes and likewise will allow byte granular accesses/seeks across disks up to a size of 2^63 bytes.


Lars


Draw backs of HPFS, long chkdsk time, hate to think how long a chdsk /f:3 on a 2TiB partition would take :) Lack of large file support, the 2GiB file size limit is a problem. It is possible to work around this with the DEADBEEF flag, which changes seeking from per byte to per sector with caller having to manage things.
I don't know much else about the structures.

I've been reading about this tonight.  It looks like large file support could be overcome, as the theoretical maximum is over 7+GB as is.  That 7+GB limitation could be defeated with a tweak it could be extended out as far as is needed.

It seems the only true limit right now to very large files in HPFS is in the legacy API, which only receives 32-bit value for file-related offsets.  That could also be defeated with our own open source kernel and new API which supports 64-bit file operations.

-----
If I had money, I would devote a team of developers to creating our own open source OS/2 clone from the ground up, kind of like what Mark Shuttleworth did with Ubuntu Linux, although he still built atop the community base, and ours would be a full ground-up replacement effort, but I would be supporting the full legacy OS/2 API so all of our code could be compiled on existing OS/2 code bases for testing, and would also compile on the new OS/2.

Ah to dream...

Thank you,
Rick C. Hodgin

14
Multimedia / Re: recent developments for USB audio
« on: May 16, 2017, 11:30:00 am »
I have installed this on my new laptop, and sound does work. For those who want to try.

1. If uniaud is installed, uninstall it. Use uninstal.exe from an older uniaud release to remove it. uninstal.exe is not in more recent releases. reboot.
2. install USB 10.217. reboot
3. install usbaudio and usbwav using minstall. reboot

At this point, sound worked for me. I'm using the Trond device https://www.newegg.com/Product/Product.aspx?Item=9SIA8583987106 I still see some drop outs, and lost frames/stopped video on YouTube. The sound is pretty good.

For the thread on the laptop, see http://www.os2world.com/forum/index.php/topic,1160.0.html

It would be interesting to know if These dropouts also occur with UNIAUD. I seem to remember that you still see the same Problem. I guess the DART subsystem (libkai uses DART) cannot keep up with the replay speed of the video (loss of synchronization).
One important thing: set the environment variable KAI_AUTOMODE=DART.
At least setting KAI_AUTOMODE=UNIAUD never worked for me.

15
Multimedia / Re: recent developments for USB audio
« on: May 14, 2017, 08:36:56 pm »
ok,

1) if you want to report bugs to AN regarding use of USB drivers then you have to use the AN USB drivers.
2) AN's code and my code was forked off the same basis which is the USB source code from the latest DDK. My changes are all visible to David as we have access to the same USB SVN repo at Netlabs. However I am not sure if David has checked in all his changes.
3) USBAUDIO changes (and the one necessary change to USBEHCD that was done in 10.217) are currently only in my drivers, I presume. At least I have seen no changes by David checked in. USBWAV is definitely only in my set of drivers.
4) I believe that USBMSD.ADD with "large floppy" support, fixes in device geometry computation etc. are only available in my package. Unfortunately, multi-LUN support (USB card readers for example) functionality is missing as it was not in the DDK source code. I would think that for the time being AN delivers the original USBMSD.ADD from IBM (version 10.162 I think that was).

Roughly spoken, if you don't need USB audio support (because you have a working UNIAUD for example) and if you are happy with the original USDMSD.ADD then you might as well use the AN drivers.

Lars


Pages: [1] 2 3 ... 10