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

Pages: [1] 2 3 ... 28
Hi, since it seems not clear how try to solve directly by fixing video driver side, it would then be the case trying to force the pointer not changing shape when pass onto the icon (that is the moment that the issue happens).
Does anybody knows how to ?
Thank you

Most probable reason for your issue is using an old BASEDEV=IBM1S506.ADD which had a small partition size limit. Later versions corrected this and Dani's driver always had no small drive limit

confirm this has fixed the issue in my case

not my case, desktop objects in DFSee 17 installation were correctly created on the desktop.
All I can say about is that I first provided the uninstallation of the previous version both by WarpIn and then deleting the DFSee directory in HOME:\TOOLS

Hi mauro

Copy danis506.add and daniatap.flt to [BootDrive]:\os2\boot

Open [BootDrive]:\config.sys and add the following 2 lines


then REM the start of these lines if they exist


Save config.sys


Test DFSee



Ok Pete, it has worked!  Now we know that DFSee 17 (guess other software as well) needs DANIS506.ADD and DANIATAP.FLT to replace IBM1S506.ADD and IBMATAPI.FLT .
Thank you much

It's a drop in replacement. Find your BASEDEV=IBM1S506.ADD, rem it and add a line right after BASEDEV=DANIS506.add along with any parameters that IBM1S506.ADD had.
I notice my config.sys has BASEDEV=DANIS506.ADD /!BIOS

ok, then it's only DANIS.506.ADD file to be placed in same directory where IBM1S506.ADD is ?
Do I ignore the other files in the decompressed directory?

Hi mauro,

One other thing you might try is to delete the DFSee partition then run xfix and or checkini with the parameters /C /H /T  Doing that will remove a lot of useless info from the ini files.

Hi Ivan, did everyting you wrote in this order:

-uninstalled previous DFsee by Warpin deinstaller
-deleted its previous working directory (C:/TOOLS)
-applied XFIX, removed all invalid entries and saved action on OS2.INI
-applied CHECKINI, went all at the end of items scanning and then confirmed end of session (is that what the way to apply the cleaning? No confirmation read about result)
-installed DFSee 17 free downloaded from ecsoft/2
-run DFSee 17
-uninstalled DFSee 17 by Warpin deinstaller
-deleted its previous working directory (C:/TOOLS)
-downloaded DFSee 17 beta from
-installed it
-run DFSee 17 beta

I think have followed slavishly all necessary steps to accomplish this attempts.

Thank you

Hi mauro

Might be worth simply deleting the contents of the dfsee directory and then unzipping(?) the latest version into that directory.

What the error seems to be saying is that the loaded disk driver IBM1S506.ADD does not understand whatever command from dfsee. When starting dfsee it seems that disk(s) get read for partition info so that is probably the failing bit. Strange...
What version (how old) is the IBM1S506.ADD in use? - might be worth trying danis506 as I recall that overcame some of the early IBM1S506 deficiencies.



ok Pete, I've downloaded the zip file who generate -as usual- a folder, but no explainations (no specific readme) on how proceed to replace the old IBM1S506.ADD

Hi mauro

Might be worth simply deleting the contents of the dfsee directory and then unzipping(?) the latest version into that directory.

Thank you Pete , it hasn't worked



Setup & Installation / Re: getting chkdsk fix errors on C (Vm Virtualbox)
« on: January 13, 2024, 09:50:53 pm »
If you're able to edit config.sys you could have chkdsk running on the next boot.
The following is from the IBM help-file:

The OS/2 operating system runs the CHKDSK program with the /F option to correct any problem caused by improper system shutdown. Each time you format a drive for the High Performance File System, the operating system updates the IFS statement in the CONFIG.SYS file with the appropriate AUTOCHECK parameter.

If you place a plus sign (+) in front of any drive letter, the drive will be checked every time the system is started.

Assume the following statement appears in the CONFIG.SYS file:


Each time it starts, the operating system checks drives D, E, and F. If necessary, it runs the CHKDSK program on drives D and F. CHKDSK will always be run on drive E.

Understand. What apply to a JFS filesystem in C: ?


is this the command to append in config.sys?

Did you totally remove the old version before you installed v17?  What you are describing sounds as if there are parts of the old version still around especially if you installed it in the previous dir.

I've uninstalled the old version through Warpin, which was the installation app used, believing it was safe enuogh

Delete the DFSee directory, run clean ini and or xfix, then install the new version.  That is what I do when installing newer versions of existing programs it prevents old information being carried over.

run clean ini and xfix are 3rd party utilities or available in the system?

no way to get out from there until I select End program/commad/operation

Setup & Installation / Re: getting chkdsk fix errors on C (Vm Virtualbox)
« on: January 13, 2024, 05:40:54 pm »
Hi Mauro

Hi Martin

I guess you can:
a) Get the CD-ROM images of Warp 4.52. Boot from the CD, press F3 on the installer and run checkdisk to the hard drive.

Have no boot CD of OS2, need to look around where to get one

b) Generate the maintenance images from you VirtualBox image. Mount a Disk1.img empty image as a diskettes and create the diskette from the Maintenance Tool, and go through all the disk. Then boot VBox with the DISK1.IMG mounted and got to the command propmt and checkdisk from there.  (Image attached)

Passages too tricky for me, will mess up the situation for sure

c) Mount the "dirty" vdi image on a different OS/2 VM as as secondary disk, boot the image and run checkdisk from there to the second hard drive.

mounting a .vdi file as secondary disk isn't allowed by Virtualbox, only .dmg, .cue, .viso, .iso, .cdr format are selectable

thank you anyway

Setup & Installation / Re: getting chkdsk fix errors on C (Vm Virtualbox)
« on: January 13, 2024, 05:28:37 pm »
Make a copy of the VDI using the host operating system.
Add the copy to your Virtual Machine
OS/2 will mount the 2nd C: drive, but LVM will assign another drive letter.
Chkdsk the second drive using the assigned letter.

Hi Neil, cannot import a .vdi file as an additional volume, .vdi format file is not allowed for this operation

Setup & Installation / getting chkdsk fix errors on C (Vm Virtualbox)
« on: January 13, 2024, 12:35:36 pm »
Hi, if I run chkdsk on C:\  from inside a OS2 open session, then the prompt warns that no fix actions will be possible as the disk remains in read-only mode, and that is fully understandable.
Could you suggest a way to make a chkdsk scanning that could fix the corrupted-bad sectors, that I guess could be performed from an external installation media, which I don't own  (I used a first-boot Warp 4.52 .vdi image to be directly imported in Virtualbox).
Thank you

Hi all, I'm finding this issue: my previous DFSee installation was the evaluation one, now asking for a valid key to run. I've found on the eCSoft/2 pages this version defined free-open source and installed it replacing the expired one, providing its uninstallation before.
In the new situation, running the object DFSOS2 returns an error window in the middle of a command-prompt window (see image). Also trying to start the RUN DFSee object returns same error alert, not specifying anything else than "IBMS506$ device does not recognize the command", which I cannot translate in something useful.
Is anyone aware of what can be done to run this DFSee ?
Thank you much

Pages: [1] 2 3 ... 28