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

Pages: [1] 2 3 ... 57
1
Programming / Re: WinQuerySwitchList Dead Entries
« on: November 29, 2019, 12:59:52 am »
Hi Martin

As an "occasional programmer" who - mainly - enjoys using WDSibyl for building apps I am wondering if function WinRemoveSwitchEntry may be of help. Must admit to not having tried it myself...

Thanks for your continual input into WDSibyl  :-)


Regards

Pete

2
Utilities / Re: graphic interface for smartahci
« on: November 21, 2019, 06:43:31 pm »
Hi Doug

Well, smartahci works with the os2ahci v1.32 driver but locks the system solid when os2ahci v2.03 is installed - it is the same smartahci that you report as working with os2ahci v2.06. the difference between smartahci working and locking up the system seems to be reliant on the os2ahci version in use.

I suggest you try the later smartctl package as it is a much later version than that used by AN for smartahci just to see if the accuracy of data is improved.


Regards

Pete

3
Utilities / Re: graphic interface for smartahci
« on: November 21, 2019, 12:18:12 am »
Hi Doug

Thanks. Confirms that the problem I am seeing is with the os2ahci.add v2.03 driver.

And now I am wondering if smartctl v6.6 2017-04-23 r4424 - http://hobbes.nmsu.edu/download/pub/os2/util/disk/smartmontools-6.6-r4424.zip - is less misleading/wrong. Yes, this build works with ahci, uses ahci0 instead of hd0 to specify an ahci controlled disk.


Regards

Pete

4
Utilities / Re: graphic interface for smartahci
« on: November 20, 2019, 07:07:05 pm »
Hi Doug

I can see the smartctl (aka smartahci) version used but which os2ahci.add is in use?


Regards

Pete

5
Utilities / Re: graphic interface for smartahci
« on: November 20, 2019, 04:48:02 pm »
Hi Dave

So, os2ahci.add has been updated but smartahci is the same version.

Now all I need is someone to test whether smartahci works with the updated os2ahci... I suspect the result will be a system lockup requiring a reboot.


Regards

Pete

6
Utilities / Re: graphic interface for smartahci
« on: November 20, 2019, 04:03:52 am »
Hi All

I have to correct my above post as it only applies when os2ahci.add V1.32 is installed.

Neither smartahci.exe or smartctl.exe can be used with os2ahci.add V2.03 on 5 systems here as attempting to use either results in a locked system requiring the use of the Reset/Power Off button.

The version of smartahci is that supplied in the package with os2ahci.add V2.03 - would have been nice if AN had checked that it worked... Or is the problem just on my systems - same problem on 2 laptops and 3 desktops all running either eCS2.2b2+ or ArcaOSV5.02+.

Is os2ahci.add V2.03 the latest release of this driver? - If there is a later version what version of smartahci/smartctl is supplied?


Regards

Pete


7
Setup & Installation / Re: Trying to solve server crash
« on: November 13, 2019, 07:53:36 pm »
Hi Ben

Unlike ivan I find the main cause of instability to be power supply or cooling related - I have yet to have a system fall over due to bad ram.

I suggest a visual examination of power supply and cooling system, clean or replace as necessary.

Also worth unplugging all leads inside the case - 1 at a time - and reinserting which will make sure connections are clean.

If the problem still persists then it is time to start checking ram and other bits of hardware...


All the above presumes there were no changes in software just before the server started showing problems.


Hope the above is of help.

Pete


8
Hi Remy

Does RxLvmGetDisks also return the type of disks - PATA or SATA - and port numbers in use?


Regards

Pete



9
Hi Andreas

Yes, Sorry, my typo...


Regards

Pete

10
Hi All

Thanks for the suggestions.

In the end I went with querying the IBM1S506$ and OS2AHCI$ files as it seems to be the only way to ascertain how many of what type of ?ATA disks are attached and to which ports.


Regards

Pete


11
Setup & Installation / Re: Installing HPFS386 on ArcaOS
« on: November 07, 2019, 04:56:31 am »
Hi Glenn

From your missing IBMLAN directory I would guess that you opted for the samba networking setup instead of IBM File and Print Client.

I would not install File and Print Client but would follow the instructions from the Al Savage webpage that state:-

On the W4 box, if you do not have File & Print Services ("Peer Networking") installed, create:
    x:\IBMLAN
On the W4 box, create:
    x:\IBMLAN\NETPROG
Copy these files from WSA box's x:\IBMLAN\NETPROG dir to the W4 box:
    CACHE386.exe
    CACH.msg
    CAC.msg


Seems to me that the requirement for the IBMLAN directory could be simply a case of HPFS386 is hard-coded to find some files in that directory tree.

I think you have to "suck it and see" but Al Savage usually knows what he is talking about so follow the instructions carefully and all *should* work OK.


Have fun  :-)

Pete


12
Setup & Installation / Re: Installing HPFS386 on ArcaOS
« on: November 06, 2019, 08:23:16 am »
Hi Glenn

A copy'n'paste from the url above which may be of help:-

Edit CONFIG.sys:
    Place a 'REM' in front of IFS=E:\OS2\HPFS.IFS
    Add IFS=x:\IBM386FS\HPFS386.IFS /A:* /AU
    Add x:\IBMLAN\NETPROG; to LIBPATH
    Add x:\IBMLAN\NETPROG; to DPATH
    Add x:\IBMLAN\NETPROG; to HELP
    Add RUN=x:\ibmlan\netprog\cache386.exe

That last line is absolutely required if you have Peer Networking installed.
(Reference: http://duanec.indelible-blue.com/wsonw4/0000c416.htm)

If you do not add this line to your CONFIG.SYS, you will get the following error whenever you start the File and Print server:

                   Net 3091: the CACHE386.exe is not running,
                   The server cannot be started.

You can start CACHE386.EXE manually from a command prompt. However, it is recommended that you edit the CONFIG.SYS and add the above statement.

Edit x:\IBM386FS\HPFS386.ini:
    Edit "lanroot = x:\IBMLAN" to match your install drive.
    Edit "cachesize = 32000" (or whatever the number is) to match your desires.
There are a bunch of other parameters you can reset as well.  Don't, unless you think you know what you're doing.


Regards

Pete



13
Hi ivan

I was looking to do this with some code.

On thinking a little more about the problem I realised I could simply check what the loaded driver shows. As I am only interested in PATA/SATA drives I can simply run

Copy IBM1S506$ PATA.txt

and

Copy OS2AHCI$ SATA.txt

Then parse the resulting files to find out what, if any, disks are controlled by the driver.


Still interested in knowing if there is a c/c++/pascal function that returns the number of disks attached rather than almost the number of partitions available to the system.


Regards

Pete

14
Hi All

I had a look at using DosPhysicalDisk but that seems to return almost the number of partitions available rather than disks.


Regards

Pete

15
Utilities / Re: graphic interface for smartahci
« on: November 01, 2019, 11:43:31 pm »
Hi All

I have both smartahci.exe - aka smartctl version 5.37 - and smartctl.exe 6.6 2017-04-23 r4424 installed. They simply seem to be different versions of smartmontools.

I can confirm grep works with both smartahci.exe and smartctl.exe:-

[M:\SYS\BIN]smartctl -A ahci0 | grep -i "temp"
194 Temperature_Celsius     0x0022   030   100   000    Old_age   Always       -
       30 (Min/Max 16/41)
231 Temperature_Celsius     0x0032   099   099   000    Old_age   Always       -
       1

[M:\SYS\BIN]smartahci -A hd0 | grep -i "temp"
194 Temperature_Celsius     0x0022   030   100   000    Old_age   Always       -
       30 (Lifetime Min/Max 16/41)
231 Temperature_Celsius     0x0032   099   099   000    Old_age   Always       -
       1


The smartctl.exe seems to be a later build than smartahci.exe and returns less "Unknown_Attribute" entries when run against my SSD:-

Output of smartahci -A hd0 > smartahci_hd0.txt

smartctl version 5.37 [i386-pc-ibmvac365] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF READ SMART DATA SECTION ===
SMART Attributes Data Structure revision number: 48
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   100   100   000    Pre-fail  Always       -       0
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       9786
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       1332
100 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       912496
101 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       132352
170 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       0
171 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       0
172 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       0
174 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       1331
175 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       0
176 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       0
177 Unknown_Attribute       0x0032   099   099   000    Old_age   Always       -       538
178 Unknown_Attribute       0x0002   100   100   000    Old_age   Always       -       0
180 Unknown_Attribute       0x0002   100   100   000    Old_age   Always       -       654
183 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       6
187 Reported_Uncorrect      0x0033   100   100   000    Pre-fail  Always       -       0
194 Temperature_Celsius     0x0022   029   100   000    Old_age   Always       -       29 (Lifetime Min/Max 16/41)
195 Hardware_ECC_Recovered  0x0032   100   100   000    Old_age   Always       -       0
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       0
199 UDMA_CRC_Error_Count    0x0012   100   100   000    Old_age   Always       -       0
201 Soft_Read_Error_Rate    0x0032   100   100   000    Old_age   Always       -       0
204 Shock_Count_Write_Opern 0x0032   100   100   000    Old_age   Always       -       0
231 Temperature_Celsius     0x0032   099   099   000    Old_age   Always       -       1
233 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       839
234 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       653
241 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       714
242 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       791
250 Read_Error_Retry_Rate   0x0032   100   100   000    Old_age   Always       -       0


Output of smartctl -A ahci0 > smartctl_ahci0.txt

smartctl 6.6 2017-04-23 r4424 [i386-pc-os2-emx] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART Attributes Data Structure revision number: 48
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   100   100   000    Pre-fail  Always       -       0
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       9790
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       1333
100 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       912640
101 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       132368
170 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       0
171 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       0
172 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       0
174 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       1332
175 Program_Fail_Count_Chip 0x0032   100   100   000    Old_age   Always       -       0
176 Erase_Fail_Count_Chip   0x0032   100   100   000    Old_age   Always       -       0
177 Wear_Leveling_Count     0x0032   099   099   000    Old_age   Always       -       538
178 Used_Rsvd_Blk_Cnt_Chip  0x0002   100   100   000    Old_age   Always       -       0
180 Unused_Rsvd_Blk_Cnt_Tot 0x0002   100   100   000    Old_age   Always       -       654
183 Runtime_Bad_Block       0x0032   100   100   000    Old_age   Always       -       6
187 Reported_Uncorrect      0x0033   100   100   000    Pre-fail  Always       -       0
194 Temperature_Celsius     0x0022   025   100   000    Old_age   Always       -       25 (Min/Max 16/41)
195 Hardware_ECC_Recovered  0x0032   100   100   000    Old_age   Always       -       0
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       0
199 UDMA_CRC_Error_Count    0x0012   100   100   000    Old_age   Always       -       0
201 Unknown_SSD_Attribute   0x0032   100   100   000    Old_age   Always       -       0
204 Soft_ECC_Correction     0x0032   100   100   000    Old_age   Always       -       0
231 Temperature_Celsius     0x0032   099   099   000    Old_age   Always       -       1
233 Media_Wearout_Indicator 0x0032   100   100   000    Old_age   Always       -       839
234 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       653
241 Total_LBAs_Written      0x0032   100   100   000    Old_age   Always       -       714
242 Total_LBAs_Read         0x0032   100   100   000    Old_age   Always       -       792
250 Read_Error_Retry_Rate   0x0032   100   100   000    Old_age   Always       -       0


Regards

Pete


Pages: [1] 2 3 ... 57