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 - Rich Walsh

Pages: 1 2 [3] 4 5 ... 8
31
Applications / Re: XWP v1.0.13 Beta 1
« on: August 30, 2019, 07:04:38 pm »
So far it works ok, but graph in CPU pulse a little bit out of screen.
More than a little bit, over 50% pulse graph does'nt show at all.

The widget relies on XCenter to give it the dimensions of its window - and sometimes XCenter gets it wrong. If that's the case here, then you can easily fix this.

First, expand the width of the widget; the graph will redraw itself. Wait a moment, then restore it to your desired size; again, the graph will be redrawn. Does this fix the problem? If not, try increasing the height of XCenter. Let it reformat itself, then restore the original height.

One or the other of these resizing actions should cause the graph to be drawn correctly. If not, please let me know.

It also tracks a lot faster which seeks attention from ones eyeballs, the older and slower one you only looked at when you wished to.

The speed has been doubled from 1 sample per second to 2 samples per second. The slower speed hid a lot of the sub-second variations and gave some users the impression that it was grossly inaccurate. In fact, it was accurate but failed to provide any real-time indication of activity.

Personally, I consider the line graph to be totally worthless if you have more than 2 cores. It just devolves into a meaningless jumble of lines that tell you nothing about actual usage - particularly when running FF or SM. The new bar graph provides a far more coherent view of overall usage. If a mozapp has a core pegged, the bar graph tells you about it without letting that excess activity take over the entire display.

Quote
I still have a problem with cmd file icons vanishing from the Tray but I suspect it is likely to be none XWP related as cmd icon's change of there own volition sometimes

This is a fundamental flaw in PM that occurs when the WPS restarts. PM mistakenly thinks that the WPS is using is a copy of the system's VIO icon, so it destroys that copy when the WPS terminates. In fact, the WPS is using the original icon; destroying it leaves the system with no VIO icon at all.

There are two possible outcomes here. One possibility is that windowed text-mode apps (such as cmd.exe) have no icon at all. The other is that PM reuses the memory for some other icon, giving cmd.exe and friends a completely unrelated icon. What I see most often is a printer or printer-port icon.


32
Applications / Re: My experience with ArcaOS & problems I've faced etc.
« on: August 11, 2019, 10:35:42 pm »
when the update was done XCenter didn't start automatically during bootup. I had to finally manually create a shadow into the Startup folder to fix that.

This should not be necessary, nor is it a particularly desirable way to start XCenter.

The very first option on the first page of XCenter's Properties notebook is "Open XCenter automatically". If it isn't checked, please enable it, then remove that shadow from Startup. This way, XCenter will also reopen automatically if you restart the Desktop - that won't happen if it is started from Startup.

OTOH, if it is checked _and_ it consistently fails to open after a reboot or restart, please advise so I can investigate the problem.

33
Applications / Re: XWP v1.0.13 Beta 1
« on: August 06, 2019, 01:59:32 pm »
would it be possible to remove/avoid the entries for USB sticks/HDDs (that had been plugged in on system start) and only keep those for fixed disks ?

AirBoot doesn't know how a drive is attached, so nothing in its menu would enable USB drives to be filtered. XShutdown is in no position to do any filtering because it fetches the list immediately before showing the Shutdown dialog. If it takes more than 3 seconds to get the list, it abandons the effort and doesn't show any list. There just isn't time to probe multiple partitions to handle an edge case like this.

34
Applications / XWP v1.0.13 Beta 1
« on: August 04, 2019, 11:31:23 pm »

The first beta for XWP v1.0.13 is available for testing.

New Features
  • XShutdown now provides a live Reboot List taken from your AirBoot/BootManager's menu. It is always up to date and requires no configuration (IBM BM support requires LVM). XShutdown's page in the Desktop's notebook has also been updated.
  • The Pulse widget now offers two types of graph: the standard line graph, and a new color-coded moving bar graph that shows average load across all cores. Other improvements include a faster line graph and fixed-position display text that shows when a core is offline.
  • An ACPI-based CPU Temperature widget has been added to XCenter, courtesy of David Azarewicz.
Updates and Bugfixes
  • NLS - Lite versions will use the "LANG" environment variable to determine which NLS version to load; the behavior of XWP-Full is unchanged. Language settings for all versions can be overridden by putting this in config.sys: "SET XWP_LANG=xxx" - where xxx is a 3-digit country code that XWP supports (e.g. 039)
  • XCenter - 'Create new widget' has been added to all XCenter menus
  • Install/Remove - after uninstalling XWP, the "System" object will be recreated in System Setup the next time the Desktop restarts
  • See XWP Help's "Version history" topic for additional update details.
Downloads
This beta is available in both Full and Lite versions for German, English, Spanish, Italian, Japanese, and Dutch.

XWP-FullXWP-Lite
German:fulllite
English:fulllite
Spanish:fulllite
Italian:fulllite
Japanese:fulllite
Dutch:fulllite

35
Events / Re: ArcaOS 5.0.4 is out!
« on: July 29, 2019, 06:29:50 pm »
I was wondering if the lastest fixes to XWP made it into this release?

The version in 5.0.4 is labelled v1.0.12+ and dates to April 6, 2019. It includes the fixes below. A beta of v1.0.13 will be out in a week or two containing these changes plus significant enhancements to XShutdown and the Pulse widget.
  • Pulse widget: the graph is faster and the text no longer moves as the numbers change. When a core goes offline, it now displays a dash '-' rather than a number.
  • CPU Temperature widget: this ACPI-based widget was provided by David Azarewicz.
  • XCenter: The 'Create new widget' option can now be accessed from all XCenter menus. Also, a font-size error in 'Diskfree (condensed)' widget has been fixed.
  • XView: Two fixes: Refresh/F5 failed to update Xview and all disks in any view; and, empty folders failed to display newly-added files.
  • Help: Lite builds now omit most pages that refer to features not included in LIte.
  • WPI: Changed default install directory to '$(WARPIN_DEFAULTTOOLSPATH)\xwps' from '$(WARPIN_DEFAULTTOOLSPATH)\WPS\XWorkplace'.

36
Programming / Re: Compiling PMMail with GCC 4.9.2
« on: July 08, 2019, 11:02:07 pm »
After building pmmail we discovered an odd issue with the gcc compilers. The popen function is hard coded to use sh as its shell which doesn't play well with path names containing back slashes and of course fails on systems where sh isn't installed.

I ran into this and got annoyed enough to write my own which doesn't use any shell at all. See the attachment.

While we're on the subject of annoyances... The file's extension should be '.c' but os2world won't allow me to attach something so dangerous, so I had to change it to '.txt'.

37
NDFS32 - 0

Valery, which NetDrive plugin were you using when you tested NDFS32?

My _guess_ is that the plugin, not the generic filesystem, supplies EA information. I know for certain that the ISO plugin returns '0' for DosQueryFile/PathInfo() (I never tested DosFindFirst()). It may be that other plugins return the correct value. I'm especially curious about the SMB plugin since that's the one that is most often used. I'd test it myself but I don't have a network set up right now.

38
It's hard to understand what good it does to return "4 Bytes" on a FIL_QUERYEASIZE if the return value is to serve as a measure of how many bytes you need to allocate when you want to actually request an EA. As I said, you need an FEALIST with at least one entry plus the extra space for the requested EA Name to return the result. even if the EA is empty/does not exist. That is most certainly more than 4 bytes.

How is the OS supposed to know that you're going to waste your time requesting some EA when it's telling you that there are NO EAs?? Returning '4' says "Ain't nothin' here, don't bother". If you're going to ignore what it says, then you'll just have to put forth some effort to calculate the appropriate size because it won't assist you in pursuing something that's pointless.

Quote
Who is using HPFS (and therefore testing with it) these days ? Nobody.

What kind of excuse is that for not bothering to find out how things are supposed to work? I have no use for willful ignorance, so I *did* try to find out. These are the results I got from running a simple DosFindFirst() against files with no EAs on various filesystems. The number is the value of FILEFINDBUF4.cbList:

FAT - 4
HPFS - 4
CDFS - 4
ISOFS - 4
JFS - 0
FAT32 - 0

You know what this shows? JFS & FAT32 are BROKEN. There was a _reason_ I suggested using HPFS as a reference: "[it] has not been altered by well-meaning but potentially ill-informed third parties" the way bootable JFS has been.

39
Here is the back and forth discussion regarding FS_FINDFIRST/FS_FINDNEXT:
http://trac.netlabs.org/fat32/ticket/55

It's hard to understand why there should ever have been a "back and forth" in the first place: none of this is subject to debate.

You write a test program that incorporates the various scenarios, run it against one or more files on an *HPFS* formatted disk, then alter your own IFS to produce the same results as HPFS. Period, end of discussion. It doesn't matter if the results you get are good, bad, or just stupid - they are what the OS and programs like 'unpack.exe' were built to expect.

Note: I consider HPFS to be the reference IFS as it is the only filesystem that is pure IBM and has not been altered by well-meaning but potentially ill-informed third parties.

40
Quote from: Rich Walsh
Just to confirm: if your IFS receives a request for the total size of all EAs (FIL_QUERYEASIZE), and you want to indicate that their are no EAs, are you returning '4' (and not '0')? Returning zero is the most common coding error when handling EAs.

What do you mean? cbList field? It is always returned to be 0. (It is so in vboxfs.ifs, fat32.ifs and ramfs.ifs/emsfs.ifs). Why it should be 4?

First, I assume that the 'cbList' field you are referring to is the one at the end of the FILESTATUS4 structure. In a properly functioning IFS, the following call will return a value of 4 in 'cbList' if 'pFilename' refers to a file with no EAs:

DosQueryPathInfo(pFilename, FIL_QUERYEASIZE, &fs4, sizeof(FILESTATUS4));

The documentation for this function and DosQueryFileInfo() is misleading. You would think it says that the size of the EAs will be returned - but that is incorrect. It actually returns the size of the FEA2LIST structure that is needed to hold all EAs. That structure is the size of all EAs *PLUS* a ULONG (named 'cbList') that identifies the total size of the variable-length structure. Thus, the correct size of an FEA2LIST for a file with no EAs is 0 + 4.

I knew this is a common error because I had to fix it in ISOFS in order to install ArcaOS from an ISO image file. The problem showed up when the installer tried to run IBM's ancient 'unpack.exe'. Even though it knew a given pack file had no EAs, it still queried them using the undocumented Level 4 argument (FIL_QUERYALLEAS). It interpreted a value of zero as 65536 and complained that the EAs were too large (since they can be no more than 65535 bytes). I doubt anyone had ever seen this error before because I know of no other program stupid enough to ask for something it knows doesn't exist.

Quote
So, the problem is with something other.

That may be true, but returning 0 in cblist is still incorrect. Write a simple test program and point it to a file on a JFS, HPFS, or even FAT drive to confirm this. BTW... AN's version of FAT32 also returns 4.

41
I have mostly implemented returning empty EA list in some IFS functions, so, in theory, WPS should show a folder listing in "Drives" object. In practice, it shows it sometimes, and sometimes it shows a "No objects were found that  matched the specified match criteria" dialog. Some other problem occurs. No idea yet, why.

Just to confirm: if your IFS receives a request for the total size of all EAs (FIL_QUERYEASIZE), and you want to indicate that their are no EAs, are you returning '4' (and not '0')? Returning zero is the most common coding error when handling EAs.

42
Applications / Re: XWP Dutch Translation
« on: June 21, 2019, 11:30:27 pm »
I do know that my version 1.0.8 did go deep into the system, had a lot of trouble after installation. Don't want that again. So how easy is it to install?

Since v1.0.8 was released on June 7, 2008, there have been 311 updates to XWP. Roughly 230 of those were bug fixes or enhancements. IMHO, XWP v1.0.12 is vastly more stable and somewhat more functional than 1.0.8.

This is particularly true if you use the Lite version. It was created to let eWP users enjoy these improvements without having to deal with the buggy, badly designed features that Mensys was wise to leave out of eWP. Since they probably removed too much, XWP-Lite restores a few stable features that users have asked for such as XWPStartup folders.

Installation is simple: download the file, double-click on it, let WarpIn install it and restart the Desktop. Unlike 10 years ago, you only need to d/l one file - your NLS version contains everything you need. If you are upgrading from eWP you're done. If you currently have the "full" version, be aware that you will have a few dead icons for stuff that isn't included such as the XWP Setup folder. You can either delete them yourself or you can run Checkini to do the cleanup for you.

43
Applications / Re: XWP Dutch Translation
« on: June 19, 2019, 05:41:12 pm »
André, thanks for your help! It looks like a lot of the items on my list didn't need to be translated after all, and the ones you did were the phrases I was most interested in. I recognize that translation can be difficult when you don't have a clear understanding of the context but in some cases that is impossible to provide. In particular, "any CPU @ 100%" is for a new feature no one has ever seen: an alternate graph for the Pulse CPU meter intended for multi-core systems.

BTW... if you are still running eWP, you should try XWP-Lite. Basically, it's the same as eWP but with a couple of useful features added back in and a HUGE number of bug fixes. And of course, it's available in Dutch:
http://hobbes.nmsu.edu/download/pub/os2/apps/wps/xworkplace/xwp-1-0-12-lite-nl.exe

44
Applications / XWP Dutch Translation
« on: June 16, 2019, 10:12:18 pm »
I'm (slowly) preparing for a new release of XWP and trying to get the various NLS versions updated. Unfortunately, I no longer have a Dutch translator, so I'd like to ask the Dutch speakers in this forum for some help.

I wrote a REXX script to compare the English and Dutch versions of the main language file and found that there were far more untranslated phrases in Dutch than any other language. I don't know if the translation work was never done, or if Dutch computer users have simply adopted more English phrases than other languages. I was able to get my list down to 92 items and have attached it to this posting.

What I'd like are translations that reflect contemporary Dutch computer usage. I'm definitely not looking for "linguistic purity" - if an "OK" button in English is labelled "OK" in Dutch, that's fine. When you're done, please attach the translated file to a post in this thread (please don't put its contents in the body of your posting). Also, feel free to review the work of other translators and suggest alternate translations if appropriate.

Thanks for your help.

BTW... I may have to ask for your help again after I review other language-specific files - I just haven't gotten that far yet and 92 phrases is more than enough for now :)

45
Utilities / Re: Create an ISO from a CD
« on: June 04, 2019, 08:18:43 am »
There are two ways to do this if you have DVD Tools installed: the "right" way and the quick-and-dirty way.

From a command prompt, run:  "readcd dev=0,1,0 -f=test.iso -retries=32"
Replace the 'dev' value with the SCSI bus address used by your drive, and change the filename ('-f') to whatever you want. If needed, run "readcd -scanbus" to get the SCSI address.

OR...

Run the "Copy Disk" app from DVD Tools to copy the disk. When it finishes reading, it will prompt you to replace the disk with a blank one. Instead, open your %TEMP% directory (usually 'x:\var\temp') where you will find a very large file whose name is all hex digits (i.e. 0-9 + A-F). Move this somewhere else and rename it, then cancel the copy.

FYI... if you do this the "right" way, Copy Disk is still helpful: it displays the SCSI bus address as part of the "Source Drive" identifier.

Pages: 1 2 [3] 4 5 ... 8